-
Notifications
You must be signed in to change notification settings - Fork 1
Home
AysArt • Aysu İğdi edited this page Aug 20, 2026
·
5 revisions
Use the public documentation site when building an app with Mantı UI. The files in this folder describe the repository and its stable design contracts.
| Document | Use it for |
|---|---|
| Vision | Product principles and current scope |
| Architecture | Package ownership and component structure |
| Design system | Visual foundations and public theme controls |
| Styling | CSS, tokens, variants, Tailwind, and motion |
| Component tokens | Generated per-component token reference |
| Zag.js coverage | Adapter status and backlog rules |
For coding agents, start with the docs site's static
llms.txt.
Mantı UI should feel simple, adaptable, and calm.
- Adaptable: components compose without forcing a product style.
- Content-friendly: components accept varied content without brittle layout assumptions.
- Smooth: state changes are responsive, predictable, and quiet.
- Distinct but familiar: the system has a recognizable material without inventing unfamiliar interaction patterns.
- Accessible by default: public components target WCAG 2.2 AA and include keyboard, focus, and screen-reader behavior.
Mantı UI currently ships a React renderer over framework-agnostic tokens, CSS, and behavior. The component catalog covers common actions, forms, navigation, overlays, feedback, data display, and layout.
Future framework renderers may reuse the same lower-level contracts. Iconography remains application-owned.