Form admin

[rdeutz]

Form Admin Meta Document

1. Summary

Joomla uses forms based on XML and rendered with the help of the Form class.

While this is a flexible way and the forms can be changed with plugins, it is limited and in some way hard coded. Database constraints are implemented through business logic within the models and not on the database level.

This specification aims to define an extension of the form building process. After implementation it allows site builder the change the core forms. Adding and removing fields should be possible and core form building and custom fields are merged.

2. Why Bother?

Hard coded forms are not state of the art. Joomla! allows today a lot of flexibility but it is up to developers to implement. If we can change the way we are creating forms we would allow site builders to change Joomla that it fulfils the needs of clients better.

3. Scope

Planned feature for Joomla5.

3.1 Goals

Having a core component that allows configuration of forms and views. This includes custom fields and a migration from Joomla4.

Respect versioning for custom fields.

Creating a API for 3rd part components to use the functionality.

3.2 Non-Goals

Migration of 3rd part components to the new way of form rendering.

[brianteeman]

It would be great if you included some accessibility requirements and recommendations in this RFC. As an example see the video and pdf linked to in the We4Authors Cluster final report

[rdeutz]

Intressing video, I think we have all information needed to make an accessible form. I will keep that in mind.

[brianteeman]

I just want to ensure that accessibility is considered by default at the beginning and not something that is added later.

[nibra]

While on forms, this might be relevant: Tripetto vs WPForms. Although it's about WordPress form plugins, we might have a look at the features.

[brianteeman]

I dont see how that has any relevance to what this RFC is about.

[Llewellynvdm]

Please continue discussions here: joomla/joomla-cms#39463