Skip to main content
This section documents patterns for applications built on the Mzizi registry — the shipping design system — not Mzizi-lang, the Phase 0 research language the rest of this site covers. The ecosystem page draws the line.
These patterns are what keeps a family of applications consistent, resilient and maintainable. Each is tested against the same four commitments as the rest of the system: sovereignty, resilience, accessibility, and infrastructure that assumes an African network rather than a Californian one.

​
Architecture and composition

Application layers

The five-layer component hierarchy an application enforces, and why imports only flow downward.

Component patterns

CVA variants, Radix primitives, cn() composition and data attributes — the mandatory stack for every component.

​
Resilience and observability

Error boundaries

Three layers of isolation, so one failing section never takes the page with it.

Observability

Structured logging, performance measurement and error tracking behind one grep-able prefix.

Lazy loading

Sequential mounting through a FIFO queue, with memory-pressure monitoring.

Mobile-first

Constrained bandwidth and lower-end hardware as the primary case, not an edge case.

​
Page shapes

Dashboard

Stats, charts, sidebar and data tables composed into one consistent layout.

Authentication

Sign in, sign up and password reset, with validation and accessible error handling.

Resource index

List and table views with filtering, sorting, pagination and a useful empty state.

Resource detail

Single-item pages, with a sidebar that becomes a stack on mobile.
Install components from the registry rather than copy-pasting them or starting a parallel library. See consuming the registry.