[FEATURE] Style Editor: Schema Registration and Form Generation

Problem

Problem
Developers currently have no way to programmatically define which style properties should be configurable for their components, and content authors need an intuitive form interface to modify styles within brand guardrails. The @dotcms/uve SDK needs extension for schema registration, and the Style Editor needs dynamic form generation.

Goal

Goal
Enable developers to register style schemas programmatically using familiar @dotcms/uve patterns, with the Style Editor automatically generating appropriate form controls. This includes supporting select, text, checkbox, radio button, and color picker field types, demonstrating brand guardrails in action.

Personas
Developer teams: Need intuitive API for defining configurable style options
Content teams: Need generated forms that respect brand guardrails

Target Personas

• Developer teams
• Content teams
• DevOps teams
• System administrators (dotCMS)

Demo Expectations

Working code example showing style schema registration for a sample component
Style Editor panel appears when clicking "edit style" button in a contentlet
UI dynamically generates appropriate controls (dropdowns, checkboxes, text inputs) based on registered schemas
Multiple field types supported (select, text, checkbox, radio button, color picker) with default values
Clear demonstration of brand guardrails (author only sees developer-defined options)
Integration with framework examples (CSS variables, Tailwind, Bootstrap)

Acceptance Criteria

No response

User Stories

No response

Links

No response

The payload names no files, tests, or entry points; start by locating the @dotcms/uve SDK schema-registration code and the Style Editor panel. Define completion against the listed demo expectations: registered schemas, generated controls for all named field types, default values, brand guardrails, and framework examples.