Mercurial
view design_system/THEMES.md @ 273:e02e2036ef84 default tip
add Layer 2 JRPG component system
Add reusable content and window modals, an isolated component sandbox, shared cyberpunk scroll areas, production-safe cache freshness, and server-rendered JRPG panel state.
Co-authored-by: Copilot <[email protected]>
| author | MrJuneJune <me@mrjunejune.com> |
|---|---|
| date | Sat, 08 Aug 2026 02:08:08 -0700 |
| parents | 667156fcd3e3 |
| children |
line wrap: on
line source
# Zenbu UI themes Themes are named token compositions, not separate component stylesheets. Applications select one with `data-zen-theme` on the document root: ```html <html data-zen-theme="paper"> ``` Built-in themes: - `paper`: warm neutral surfaces, restrained natural accents, editorial type; - `ink`: dark charcoal surfaces with paper-like text and softer status colors; - `playful`: brighter clay, persimmon, violet, and rounded shapes; - `cyberpunk`: midnight surfaces with neon cyan, magenta, violet, yellow, and mint roles; - no attribute: follow the operating-system light/dark preference. Applications can provide their own fonts without changing component CSS: ```css :root { --zenbu-font-editorial: "More Thin", sans-serif; --zenbu-font-playful: "More", sans-serif; } ``` Import `themes.css` after `tokens.css` and before component CSS. Components continue to consume semantic tokens, so every built-in and application theme inherits the same accessibility, motion, and native-HTML behavior.