Zetta v0.10

Resources

Known gaps

Where Zetta v0.10 is genuinely silent, build from the foundation tokens and the guardrails, and state your assumptions — don't invent a new token system. This is the consolidated, honest list of what the spec leaves open.

Genuinely unspecified

State assumptions and build conservatively from the foundation.

  • Motion application — motion tokens (durations / easings) exist, but per-component mapping is not defined.
  • Data-viz standards — chart colours exist (chart-1…5 + greyscale in Accessibility), but chart-type / axis / tooltip / legend / empty-state specs do not. Use the ramp plus non-colour separation (pattern, dash, label) in Accessibility.
  • Page-level states — empty / loading / error states; z-index / stacking-context management; form-validation UX; dark ↔ light transition behaviour; RTL / localization overrides.
  • Focus-trap — specified behaviourally for dialog / drawer, but not as component code.

Resolved recently — not gaps

These were once open but ship in v0.10. Don't treat them as missing.

  • Top / horizontal navigation — shipped in v0.10 as the header component.
  • Focus states and convention standardization — dropdown-item, sidebar-nav-item, pagination-item, accordion-trigger, toggle and table-row focus states are present in the v0.10 component files, even though the theme files’ "Deferred to v0.11+" prose still lists them. Trust the components over that stale prose.

Out of core by design

Product-specific concerns deliberately live in the consuming product's own token layer, never in Zetta core — so the system stays small and every project can extend it without forking.

  • Business / domain colours — lifecycle states, incident / category types, report / section accents.
  • Product compositions — card header / footer / action areas, session cards.

Intentional contrast trade-offs

Documented on purpose — don't "fix" these.

  • border-strong on canvas is intentionally below WCAG SC 1.4.11 (3:1) in the standard themes (Light ≈1.45:1, Dark ≈2.80:1) — chosen for visual density. The Accessibility theme overrides it to white for full compliance.
  • A few Dark semantic -text-on--bg pairs are "moderate" (e.g. danger-text ≈5.89:1) — accepted; AAA is enforced only in the Accessibility theme.
  • WCAG AAA is enforced exclusively in the Accessibility theme — Light / Dark contrast figures are informational.

Per-component gaps are also called out in each component's Known gaps section (see, for example, Chart and Calendar).