Marcus Andrey Study
Ler em português Library

Design Systems

Frameworks

15 frameworks and techniques this course's lessons use, by area.

Each card opens the full framework: when to use it, the steps, an example, pitfalls and a template. The frameworks of every course are in one list, with a filter.

Design systems

Atomic design
Brad Frost's five stages (atoms, molecules, organisms, templates, pages) for thinking about an interface as parts and wholes, so you can see what to build once, what to combine, and where real content tests the system. In From components to patterns
Component accessibility checklist
The WCAG 2.2 success criteria a single component can meet or fail, grouped by the four principles, so every component ships with a tested accessibility contract instead of waiting for a screen-by-screen audit. In Accessible components
Component API checklist
Six questions to answer in plain words before you draw a component (its job, parts, what changes, what never changes, its states and what it is not), then three checks that turn each answer into a variant, a property, a slot or a token. In Anatomy and API of a component, Variants, properties and slots
Component doc template
A component page in the order people ask: name and status, one sentence, a live example, when to use and when not, how it works, accessibility, content, research and changelog, with each fact kept in one place and linked from the others. In Component docs people use, Write a component doc page
Component state matrix
A grid of every state a component must ship (interaction states the browser sets, component states the product sets, data states the content brings) against what each needs: a design, the right attribute, a measured contrast and an edge-case test. In States and edge cases
Contribution process
A lightweight path from a domain need to a released pattern (check existing, propose, council review, build, document, announce) that lets many teams grow the design system without you reviewing everything. In Contribution models
Deprecation lifecycle
Five stages for taking a component, token or property out of a design system (decide, deprecate in a minor, help people move, remove in a major, support the old major for a while), so nothing disappears by surprise. In Deprecation and breaking changes
Design system adoption playbook
Seven moves that get teams to adopt the design system without policing: involve early, make the right way easy, show the benefit, pilot, migrate incrementally, listen to rejection, escalate rarely. In Bringing teams onto the system
Design system governance models
Four ways to own a design system (solitary, centralised, federated, hybrid) and how to pick the one that fits your organisation. Federated or hybrid usually fits distributed enterprise teams. In Contribution models, Funding and staffing a design system team
Design system metrics
Six signals that show whether the design system works (adoption and coverage, detach rate, delivery time, consistency defects, satisfaction, contribution health), so you can report on it like a product. In Measuring adoption, Showing the value of a design system
Design system ROI estimate
A sum a finance partner can check line by line: the hours product teams get back from the system, minus the time they spend on it, next to what the system team costs, so you can say whether the system pays for itself and from what volume. In Funding and staffing a design system team, Showing the value of a design system
Pattern tiers
Four tiers for design-system patterns (core, recommended, domain-specific, experimental) that make it explicit where teams must be consistent and where they are free to differ. In From components to patterns
Semantic versioning for design systems
MAJOR.MINOR.PATCH applied to a design system, where the API includes names, defaults, layout and behaviour, so every release number tells product teams how carefully to update. In Versioning and releases
Three-tier token model
Primitive tokens hold raw values, semantic tokens name what a value is for, component tokens name one slot in one component, and aliases link them in one direction, so a mode, a rebrand or a second brand moves one link instead of every component. In Token tiers
Token naming formula
A fixed order for building token names from general to specific (category, concept, variant, state), with a list of allowed words for each part, so every name tells people when to use it and new names stay consistent. In Naming tokens
Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close