Form Builder

[tisto]

We need a form builder (like PFG/c.easyform) for Volto. We can already auto-generate forms from json schema. We need a backend implementation for the content type, the data-adapters, and the actions.

Design decisions (RFC):

1. Forms should be a block element.
2. User adds a form block that renders the default form (subject, email, message) with the default email action
3. User can add/edit/reorder form fields in the sidebar
4. We store the json-schema of the form as a block
5. email actions (one or more) can use the existing p.restapi email endpoint to send emails

Benefits:

• Allows multiple forms on a single page
• Keeps content area clean

Future enhancements:

• Store form data as CSV/JSON in a content object within the folderish page

[tisto]

PoC code: https://github.com/kitconcept/kitconcept.formgen/blob/master/src/kitconcept/formgen/interfaces.py

[tisto]

Notes Discussion with @robgietema:

• we need a submit form endpoint
• naming is hard (plone. / collective. / volto.)?
• Rob wrote a widget that we can use anywhere, in a content object view or a block. It would be similar to the table block
• Timo will continue with his prototype and give it to Rob, we need to further prototype before we can settle on how to do things

[tisto]

@iFlameing implemented a working prototype for a form builder in Volto:

https://github.com/kitconcept/volto-form-builder

All the basic fields are in place.

We also have a prototype for a backend:

https://github.com/kitconcept/kitconcept.voltoformbuilder

@wkbkhard worked on another prototype that uses a full form block (instead of individual input field blocks)

[sneridagh]

Update 26.13.2022: https://github.com/collective/volto-form-block is the standard "de facto" solution for Plone 6/Volto.

[sneridagh]

Closing as the existing solution is good enough. We will open another PLIP in case we want to improve it or enhance it. For now there are no plans about any of it.