comparison design_system/wiki/README.md @ 258:60a876c4587a

[ui] Add semantic primitive ownership Build a layered Zenbu token and sizing system, make authored controls use native-underneath primitives, migrate mrjunejune without imposing visual surfaces, and document/enforce HTML ownership in the catalog and wiki. Co-authored-by: Copilot <[email protected]>
author MrJuneJune <me@mrjunejune.com>
date Wed, 05 Aug 2026 05:25:40 -0700
parents
children
comparison
equal deleted inserted replaced
257:609d3c6aff4e 258:60a876c4587a
1 # Zenbu UI wiki
2
3 This wiki is the source of truth for future HTML and component work.
4
5 ## Pages
6
7 - [HTML authoring](HTML_AUTHORING.md): native-underneath markup and ownership.
8 - [Primitive map](PRIMITIVE_MAP.md): which primitive owns each native control.
9 - [Tokens and sizing](TOKENS_AND_SIZING.md): reference, semantic, local, theme,
10 density, and xs-xl contracts.
11 - [Review checklist](REVIEW_CHECKLIST.md): required searches, tests, and
12 accessibility checks.
13
14 ## Core rules
15
16 1. Keep browser semantics. A Zenbu control contains the appropriate native
17 element rather than replacing it.
18 2. Give every authored interactive control one owning primitive.
19 3. Use `appearance="plain"` when only behavior and scale are shared.
20 4. Consume `--zenbu-sys-*` intent in application/component CSS.
21 5. Use reference values only while defining semantic mappings.
22 6. Keep business state and workflows outside the design system.
23 7. Add catalog and browser evidence for every public primitive.