[FEATURE] Style Editor: Real-time Preview and Save Integration
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem
Problem
Content authors need to see immediate visual feedback when making style changes and reliably save their modifications. The Style Editor form exists but lacks real-time preview and save functionality integration.
Goal
Goal
Complete the Style Editor experience by adding real-time preview that shows style changes immediately in the component, and robust save integration that persists changes through the backend API and updates the live page.
Personas
Content teams: Primary users who need immediate visual feedback and reliable saving
Developer teams: Benefit from complete Style Editor workflow reducing support tickets
Target Personas
- Developer teams
- Content teams
- DevOps teams
- System administrators (dotCMS)
Demo Expectations
Demo Expectations
Form changes trigger real-time preview showing style updates in the component inside UVE
Save functionality persists changes through backend API to multi_tree table
Live page updates reflect saved style changes immediately
Error handling provides clear feedback for failed save operations
Seamless integration between form, preview, and save workflow
Acceptance Criteria
No response
User Stories
No response
Links
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by locating the existing Style Editor form and its integration with UVE, then trace the backend API path to the multi_tree table. Done means real-time component preview, persisted saves, immediate live-page updates, and clear failed-save feedback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, database, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100