m3-ui documentation
Build Material 3 React interfaces with public m3-ui components, theming, and explicit web conformance guidance.
Build with m3-ui from the public API outward: install the package, mount a theme, render a component, then use the Material-led guides for the behavior and fidelity details you need.
Get started
- Introduction — what
m3-uiis, what it is not, and which contract to rely on. - Installation — current workspace installation and public CSS entrypoints.
- Quick start —
ThemeProviderplus a publicButton. - Browser support — tested surfaces and modern-browser assumptions.
- Material conformance — source hierarchy, web mappings, adaptations, and gaps.
- Public docs and Storybook — which surface to use for guidance versus exhaustive implementation review.
Then choose the guide you need
- Foundations for reusable Material color and typography contracts.
- Theming for
ThemeProvider, dynamic color, typeface roles, ripple focus, and theme-aware portals. - Layout for the dedicated Material adaptive-layout subsystem.
- Components for Material-led component usage and public API examples.
- Parity catalog for structured provenance, fidelity dimensions, adaptations, and known gaps.
Material 3 is the normative design source
Material Design 3 defines the design intent. AndroidX Compose Material3 provides current Material API vocabulary and implementation evidence. Browser semantics and React Aria Components provide the web interaction and accessibility mapping. The m3-ui public implementation is the API that consumers can actually import today.
That hierarchy means a correct web adaptation is not automatically a parity failure, and an implementation detail from Compose is not automatically a public React API requirement. These docs call out adaptations and known gaps explicitly rather than claiming complete Material parity globally.
Documentation boundary
Public docs are curated developer guidance. Storybook remains the exhaustive component visual-review and regression surface. Fumadocs supplies the content/page-tree/search pipeline, while the visible documentation product is rendered with m3-ui itself.