#108182Modern color system for TYPO3 v14 backend
Description
This epic evolves the TYPO3 v14 backend color system to better support the new look & feel, accessibility requirements, and long-term maintainability.
The current backend colors have grown organically over time and successfully give TYPO3 a strong, recognizable character. As usage patterns, devices and surrounding tools (Slack, Teams, GitHub/GitLab, Google Docs, modern OS UIs, other CMS/DXPs) have evolved, new needs have emerged: clearer separation between chrome and content, more consistent state and semantic colors, and a color model that works reliably in both light and dark mode.
To address this, this epic introduce a modern color system for the backend, to consolidate it into a clearer, more systematic foundation that TYPO3 can build on for the next years.
This epic will:
- Define a new primary color (and its scale) for backend chrome and active states, with accessible variants for hover, active and focus in both light and dark mode.
- Introduce a consistent neutral palette (backgrounds, surfaces, borders, text, disabled) that works across modules and views and keeps content in focus.
- Clarify and standardize semantic colors (success, warning, error, info) and reserve them for statuses, validation and alerts instead of decoration.
- Reduce the “multi-color” impression in the module bar and iconography by using neutral + primary by default, while keeping strong semantic colors where they communicate meaning.
- Harmonize light and dark mode color roles so the same tokens/roles exist in both modes, tuned for contrast, comfort and readability.
- Initiate usage guidelines for core components (navigation, buttons, tables, lists, badges, notifications, modals, etc.), so future work and extensions can rely on a shared color language.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.