Foundations
Implemented Material 3 foundations shared by every m3-ui component.
Implemented foundations
The public docs describe foundation contracts that are represented in canonical tokens or runtime behavior and have been audited against their Material sources.
- Color — semantic Material color roles, baseline schemes, dynamic color, and contrast level.
- Typography — the full Material type scale plus M3 Expressive emphasized roles.
- Shape — the Material shape scale, semantic corner roles, component token mapping, and expressive-shape provenance.
- Theming — how
ThemeProviderprojects supported foundations into an application and theme-aware portals.
Source of truth
Foundation values are not defined in the docs application. Canonical design values live in packages/tokens, while @m3-ui/ui exposes the runtime contracts that consumers actually import.
Shape follows the same rule: component tokens alias canonical shape roles instead of duplicating radius values in documentation or component prose.
Still tracked separately
Motion and elevation have dedicated documentation work tracked by the Material-first docs program. Their future guides should describe audited foundation contracts without inventing a global theme API that the public package does not expose.
Layout is separate
Adaptive window classes, pane directives, canonical scaffolds, hinge handling, and pane behavior belong to the dedicated @m3-ui/ui/layout subsystem rather than the visual foundation layer.