Design Systems
Tokens, Handoff, Component Design, Case Studies
Design Systems Fundamentals
What a design system actually is and how to build one.
Design Tokens & Variables
The atomic layer of a design system, values, not decisions.
Component Design Patterns
Recurring solutions to recurring UI problems.
Design System Case Studies
Material Design, Polaris, Atlassian, how real systems work.
About the Design Systems silo
The Design Systems silo teaches how organisations keep interfaces consistent at scale. It covers what a system is, how tokens and variables encode decisions, how components are designed and governed, and what can be learned from public systems such as Material, Polaris and Atlassian.
A design system is a product used by other designers and engineers, so it needs documentation, versioning and a contribution process, not only a component library. The courses emphasise these organisational aspects alongside the craft of building components.
Suggested learning path
- Design Systems Fundamentals. A design system is the most leveraged investment a product team can make. Covers what is a design system?, atomic design methodology, design tokens, the foundation and more.
- Design Tokens & Variables. Design tokens store visual decisions such as colour, spacing and type as named values. Covers what tokens are, token tiers, naming conventions and more.
- Component Design Patterns. Component design patterns are reusable solutions to common interface problems. Covers anatomy of a component, states and behaviour, variants and composition and more.
- Design System Case Studies. Design system case studies examine well-known systems such as Material Design, Polaris and Atlassian. Covers why study existing systems, material design, polaris and product-focused systems and more.
What you will be able to do
- Explain the difference between a library and a system
- Structure and name design tokens
- Design components with states and accessibility
- Define governance and contribution
How to study this
Read Design Systems Fundamentals first, then Design Tokens and Variables. Use the case studies to compare your approach with established systems.
Who it is for
Interface designers on growing teams, design leads setting up shared libraries, and engineers who maintain component code.
Frequently asked questions
- Do I need a large team to need a design system?
- No. A small team benefits from shared tokens and a few documented components, and can grow the system as needs appear.
- Are tokens only for developers?
- No. Designers define tokens in tools such as Figma variables, and developers consume them in code.
- Which public systems are covered?
- The case studies compare Material Design, Shopify Polaris and the Atlassian Design System.