opsinjs
Foundations
The token families and system-wide rules every opsinjs component obeys, one page each.
Foundations decide once what a colour, a size, a corner or a state means, so every component gives the same answer. Each page states the rules a component follows, and each token family ends in a table generated from tokens/*.json. Change a value in Theming, and see every token in one list in Tokens.
| Page | What it covers |
|---|---|
| Accessibility | WCAG 2.2 AA, what components guarantee, and the limits of an author-run audit |
| Colour | Category and status as two axes, the derivation engine and the contrast floor the build measures |
| Typography | The platform UI font, a type scale named for jobs, and the reader's own text size |
| Space and layout | The 4px spacing scale, the 44pt touch floor, responsive modes and the page shell |
| Shape | The radius ladder, concentric nesting and squircle corners |
| Motion | Springs as tokens, motion chosen by its job, and reduced motion |
| Materials | The surface ladder, its rung names, and the contrast floor for translucent rungs |
| Iconography | One icon library, and glyphs that never carry status on their own |
| Imagery | Illustration, photography, skin-tone representation, avatars and body diagrams |
| Data visualisation | Chart colour, chart anatomy and accessible charts |
| States | Interaction states, and the loading, empty, error, stale and partial data states |
| Writing | Voice and tone, health literacy, and the words for status, alerts and errors |