Closed sandreae closed 4 years ago
Thinking about this enhancement again. It could be quite a useful feature as more organizations start using the platform, each needing different form data for their events, users, resources and venues.
I added one field to the create event form #62 which will probably be useful in some other cases. However, I want to add several more fields specific to my use case (Antiuniversity Now 2020) which probably won't be needed by other festivals. Am I right thinking this would need to be a fork of the project then?
Instead of doing this, would it be better to add this feature to the platform, making form fields editable by admin users? Or maybe within a config file which can be edited before initiating the festival?
What form fields are concretly needed and how does the process for AU look like? Not sure if I understand yet what is missing in the current application.
But yes, generally forking is an option or not trying to cram everything into one code but using side-channels to organize some other parts of the process (external forms / email etc.).
For our use (Antiuni) this issue is resolved, but for the future it could be useful for others to have a simple add / edit form fields interface in the admin area. Closing for now though!
There are several areas where it would be useful to be able to add to/edit form fields and their descriptions, would it be possible to add this as an admin option?
Specific instances where it would be useful to add remove fields: