Mercurial
view design_system/wiki/README.md @ 263:ee04e4e69fed
Add functional JRPG frame and tools
Add full-screen background_2 apertures, functional frame chrome, card-driven details, dual-window tools, live conversion workflows, and bounded cleanup for generated downloads.
Co-authored-by: Copilot <[email protected]>
| author | MrJuneJune <mrjunejune@users.noreply.github.com> |
|---|---|
| date | Thu, 06 Aug 2026 11:31:30 -0700 |
| parents | 60a876c4587a |
| children |
line wrap: on
line source
# Zenbu UI wiki This wiki is the source of truth for future HTML and component work. ## Pages - [HTML authoring](HTML_AUTHORING.md): native-underneath markup and ownership. - [Primitive map](PRIMITIVE_MAP.md): which primitive owns each native control. - [Tokens and sizing](TOKENS_AND_SIZING.md): reference, semantic, local, theme, density, and xs-xl contracts. - [Review checklist](REVIEW_CHECKLIST.md): required searches, tests, and accessibility checks. ## Core rules 1. Keep browser semantics. A Zenbu control contains the appropriate native element rather than replacing it. 2. Give every authored interactive control one owning primitive. 3. Use `appearance="plain"` when only behavior and scale are shared. 4. Consume `--zenbu-sys-*` intent in application/component CSS. 5. Use reference values only while defining semantic mappings. 6. Keep business state and workflows outside the design system. 7. Add catalog and browser evidence for every public primitive.