List view
## Description ### Vision Establish a "low-code" paradigm for content authors governed by "pro-code" developer guardrails, enabling single content items rendered in multiple visual variations without content duplication or hardcoded logic. Eliminate "container hell," reduce developer burden on trivial styling tasks, and enable rapid, brand-consistent content presentation across digital properties. ### Problem dotCMS enterprise customers face conflict between content reuse and presentational flexibility. Current methods force developers to create excessive single-use templates/containers ("container hell") or add presentational fields to content models, polluting data structure. Results: - **Content Authors**: Cannot make stylistic changes without developer tickets, cognitive overload from excessive container options, forced content duplication for different presentations - **Developers**: Spend significant time on low-value CSS changes instead of features, maintain brittle architectures with hundreds of containers, exponential scalability issues in multi-brand scenarios - **Brand Managers**: Cannot enforce consistent brand identity, slow time-to-market for campaigns blocked by development cycles ### Solution Developers create reusable frontend components in existing headless applications (Angular, Next.js, Vue, etc.) and use @dotcms/uve SDK to register style schemas programmatically. dotCMS backend dynamically generates Style Editor UI from these SDK registrations. Author styling selections stored as JSON in `multi_tree` table (not contentlets), preserving content purity while enabling context-specific presentation. System integrates with existing customer design systems (CSS variables, Tailwind, Bootstrap, etc.) to produce final HTML. ### Market Positioning Positions dotCMS as the only platform combining enterprise-grade CMS capabilities with modern visual building approaches, addressing complete spectrum from content strategy to presentation flexibility. **Core Differentiators:** - **Enterprise CMS Foundation**: Proven content management with visual building capabilities - **Framework-Agnostic Components**: Works with React, Vue, Angular, and any existing tech stack - **Customer-First Integration**: Leverages existing design systems rather than prescribing new ones - **Simplified Developer Experience**: @dotcms/uve SDK reduces setup complexity vs competitors - **Multi-Tenant Component Sharing**: Enterprise-grade component reuse across brand portals - **Cost-Effective Enterprise Scaling**: Competitive alternative to expensive solutions like Contentful ## Links - [Press Release](https://docs.google.com/document/d/1rDjmYk0L5dJZGmPH9xOG1NvYd8ov3IbZ/edit#heading=h.gjdgxs) - [PRD](https://docs.google.com/document/d/1X8V5zaMgg0XedmUg-YpGtPBAUNMULy0Y/edit) - [Problem Framing](https://drive.google.com/file/d/1r3IPgIKDQ-3Gorfi_nY4Z5m3W8DCXvDi/view) - [Ideation Document](https://docs.google.com/document/d/1wW0DhogH3uNVp6BCJBNa7QQSmMVw8DcF/edit) - [Prototype Video](https://drive.google.com/file/d/1Da8-4Ht843yWiZsqW_qYNWmgwXG3br1v/view?usp=drive_link) - [Prototype Playground](https://brilliant-klepon-b9bb49.netlify.app/) - [Competitive Analysis](https://docs.google.com/document/d/1x3PGtS-OdeyZyS9iu3WDg9wlCUG-hXf8T3U5zKd-T5w/edit?usp=sharing) - [Slack Channel: #feat-uve](slack://channel?team=T04NHDTJ2&id=feat-uve) - https://dotcms.airfocus.com/DOT-117
Due by December 29, 2025•0/11 issues closed- No due date
- No due date
- No due date
- No due date
- Overdue by 2 year(s)•Due by March 15, 2023•7/7 issues closed
- No due date•48/48 issues closed
- No due date•3/3 issues closed
- No due date
- No due date•7/7 issues closed
- No due date•1/1 issues closed
- No due date•2/2 issues closed
- No due date•4/4 issues closed