Performing a detailed analysis of some twig templates of the Admin plugin, I detected the following, regarding the attributes common to all form fields:
The labelclasses attribute is documented in the Grav documentation, however it is not being used in these templates.
The wrapper_classes attribute is used in some templates to wrap the field description, however it is not in the Grav documentation.
Some fields use the sublabel attribute, which also does not appear in the Grav documentation.
Field classes (field.classes) are applied in some templates to both the label and the field, so it would be better to differentiate the classes that are applied to these elements.
The grav-admin plugin allows, in its customization tab, to create classes that can be applied to these fields, so I decided to create some examples and be able to use the classes that I mentioned, to see the result.
For all the above, I will propose a series of modifications, through a Pull Request, so that the Grav team can analyze them and see their viability for the next version of the plugin.
Performing a detailed analysis of some twig templates of the Admin plugin, I detected the following, regarding the attributes common to all form fields:
labelclassesattribute is documented in the Grav documentation, however it is not being used in these templates.wrapper_classesattribute is used in some templates to wrap the field description, however it is not in the Grav documentation.sublabelattribute, which also does not appear in the Grav documentation.field.classes) are applied in some templates to both the label and the field, so it would be better to differentiate the classes that are applied to these elements.The grav-admin plugin allows, in its customization tab, to create classes that can be applied to these fields, so I decided to create some examples and be able to use the classes that I mentioned, to see the result.
For all the above, I will propose a series of modifications, through a Pull Request, so that the Grav team can analyze them and see their viability for the next version of the plugin.