Skip to main content
This section documents Mzizi’s components: the registry and design system that support the language, served through api.mzizi.dev and browsable at mzizi.dev/components. It is not documentation for the language itself; the ecosystem page draws the line. Rust components (Mzizi Roots) lead. The React components are the React build: they keep working, but they are deprioritised.
Foundations are the decisions that shape every component and pattern in the design system. They define how tokens, typography, layout, motion, icons, accessibility and internationalisation are handled, and they are constraints rather than suggestions — N1 owning every CSS value is what makes the other seven nodes portable. The design system is also published on claude.ai as the Design System artifact, built file for file from the design-system/ folder in mzizi-dev/mzizi-registry (arriving with mzizi-registry#418), which is the copy to change.

Guiding philosophy

The design system is built for the reality of African infrastructure. A user on a 2G connection is not an edge case; it is the primary case. Four pillars shape the decisions:
  1. Local-first — data and UI work offline, syncing when connectivity returns.
  2. Mobile-first — most access is on mobile devices with constrained bandwidth and lower-end hardware.
  3. Open source and sovereign — no dependency on infrastructure the ecosystem does not control.
  4. Open data — transparent data pipelines.
Those translate into concrete constraints:
  • Language-inclusive — the font stack covers African languages with full diacritics. African languages are first-class, not localisations.
  • Accessible by default — WCAG 7:1, 4.5:1 and 3:1 contrast with APCA 3.0, 17px body text on touch (15px on a desktop), and a hit region on every control of 45px on touch and 24px on a desktop, with a spacing floor for each layer of a screen and a 1.5 line height. The owner set these on 19 November 2026. See the Bundu floor, the spacing layers and the standards comparison.
  • Performant on constrained devices — lazy loading, memory-pressure monitoring and sequential mount queues.
  • Offline-capable — components and patterns degrade gracefully.

Explore

Design tokens

The Seven African Minerals, the semantic status categories, and how a value flows from N1 to everything above it.

Typography

Font stack, type scale, heading hierarchy, and when serif rather than sans.

Layout

Breakpoints, the spacing scale, container patterns and grid shapes.

Motion

Timing, easing, enter and exit patterns, and reduced-motion behaviour.

Icons

Icon conventions, the size scale, and accessible icon-only controls.

Accessibility

WCAG and APCA contrast thresholds, hit regions, keyboard navigation, screen readers.

The Bundu floor

The minimums in two tiers: touch keeps 17px body and a 45px hit region, a desktop keeps 15px and 24px, captions are 14px on both, and how to migrate.

The spacing layers

The space each layer of a screen keeps: controls, cards, containers and page layout.

Standards comparison

The Bundu floor beside WCAG 2.2, Apple’s Human Interface Guidelines, Material 3 and Anthropic’s brand.

Internationalisation

Why Noto Sans, text direction, and locale-aware number and date formatting.