[TASK] Render Style Editor Form Based on Configuration from @dotcms/uve

[KevinDavilaDotCMS]

Description

Currently, the Style Editor does not dynamically render forms based on project-specific configurations defined in @dotcms/uve.
Developers should be able to define custom style configurations for each Content Type, and those configurations must dictate the structure and behavior of the Style Editor form.

This feature impacts all developers who want to customize style configurations per content type within UVE. Without this, the Style Editor cannot adapt to project-specific style definitions, limiting flexibility and scalability for headless implementations.5

Acceptance Criteria

• The system must read a form configuration from the libraries in @dotcms/uve when activating the Style Editor for a Contentlet.

• The form must be rendered dynamically according to the structure defined in the configuration.

• The following field types must be supported:

  • Dropdown
  • Radio button
  • Checkbox
  • Input

• The system must load existing values and populate the corresponding form fields.

• The UI must match the design specified in Figma, including proper spacing, alignment, and scroll behavior for large forms.

• (Nice-to-have) Support layout features such as columns within a form section to improve usability.

• The final output should correctly render sections and their corresponding fields based on the configuration sent from a headless project.

• All form fields should display their selected or saved values when available.

Priority

High

Additional Context

No response

[github-actions]

PRs linked to this issue

• 33810 task render style editor form based on configuration from dotcmsuve by @KevinDavilaDotCMS

PRs linked to this issue

• 33810 task render style editor form based on configuration from dotcmsuve by @KevinDavilaDotCMS
• chore(style-editor): Refactor style editor components for improved configuration and typing. by @KevinDavilaDotCMS