Design Systems
Glossary
139 terms defined in this course's lessons, A to Z.
The general glossary has the terms of every course, with a filter.
A
- Accessibility contract
- What a component guarantees, and what the product using it still owns In Accessible components
- Accessible name
- What a screen reader calls a control, usually from its label In Accessible components
- What a screen reader calls a control; for icon-only buttons, an
aria-labelIn Icons and illustration in the system - Adoption
- Teams actually using the system in what they ship In Bringing teams onto the system
- How much of what ships is built with the system, and whether people choose it In Measuring adoption
- Alias
- A variable whose value is another variable In Building a Figma library
- A token whose value is another token In Token tiers
- Anatomy
- The named parts of a component, and which are required In Anatomy and API of a component
- APG
- The WAI-ARIA Authoring Practices Guide: W3C's patterns for keyboard and roles In Accessible components
- API
- What a user of the component can change: props in code, properties in Figma In Anatomy and API of a component
- Args
- Storybook's word for a component's props In Storybook and living documentation
- ARIA
- Attributes that tell assistive technology what an element is and what state it's in In Accessible components
aria-describedby- Links extra text, like a hint or an error, to a control In Accessible components
aria-disabled- Tells assistive technology a control is unavailable, without removing it from the Tab order In States and edge cases
- Autodocs
- A doc page Storybook generates from the stories and props In Storybook and living documentation
- Axis
- One independent kind of mode: colour mode, density, brand In Themes and modes
B
- Backlog
- The ordered list of work that comes out of the inventory In The interface inventory
- Boolean property
- An on or off switch, usually showing or hiding a layer In Variants, properties and slots
- Brand layer
- The tokens that change per brand: values, families, radius options In Multi-brand and multi-product systems
- Breaking change
- A change that makes a working product fail or change without its team choosing it In Deprecation and breaking changes
- A change that makes something that worked stop working, or look different, without anyone touching it In Versioning and releases
- Build tool
- A program, like Style Dictionary, that turns token files into platform code In Tokens from Figma to code
C
- Category
- The kind of value: colour, space, radius, font In Naming tokens
- A family of parts: buttons, forms, colours, messages In The interface inventory
- Changelog
- A list of notable changes per version, newest first In Versioning and releases
children- In React, the content placed between a component's tags; its "hole" In Composition over configuration
- Code Connect
- Figma's way of showing real design-system code for a component in Dev Mode In Code Connect and the design-code bridge
- Code syntax
- The name a variable has in code, shown in Dev Mode In Building a Figma library
- The code name of a Figma variable, shown in Dev Mode In Tokens from Figma to code
- Codemod
- A script that rewrites code automatically, for mechanical changes In Deprecation and breaking changes
- Collection
- A set of variables and the modes they share In Building a Figma library
- A Figma set of variables that share modes In Tokens from Figma to code
- Colour pair
- A foreground token and the background it's tested on In Colour, type and spacing as tokens
- Component
- A reusable piece of interface, designed and built once In What a design system solves
- Component property
- Figma's version of a prop: Boolean, instance swap, text, variant or slot In Anatomy and API of a component
- Component set
- In Figma, all the variants of one component, grouped In Variants, properties and slots
- Component state
- A state the product sets through a prop: disabled, loading, selected In States and edge cases
- Component token
- A slot in one component:
button.primary.backgroundIn Token tiers - Composite token
- A token made of several values, like a typography style In Colour, type and spacing as tokens
- Composition
- Building a component from smaller ones placed inside each other In Composition over configuration
- Concept
- The job a semantic token does: action, text, surface, feedback In Naming tokens
- Configuration
- Changing a component through props, from a list the component knows In Composition over configuration
- Content rule
- A written rule for the words in a component, with examples In Content and voice in the system
- Contribution
- A change to the system made by someone outside the core team In Contribution models
- Controls
- The panel where you change args and watch the component update In Storybook and living documentation
- Core
- The parts shared across the whole organisation In Anatomy of a design system
- The part of the system every product shares In Multi-brand and multi-product systems
- Coverage
- The share of screens or components in a product that come from the system In Measuring adoption
D
- Decorative icon
- An icon that repeats what the text says; hidden from screen readers In Icons and illustration in the system
- Default
- The value a prop has when nobody sets it; the most common case In Anatomy and API of a component
- Default library
- A Figma library switched on automatically for a team or organisation In Bringing teams onto the system
- Density
- How tightly a layout is spaced, such as comfortable or compact In Colour, type and spacing as tokens
- A spacing context, like comfortable or compact In Themes and modes
- Deprecated
- Still there and working, no longer recommended, and scheduled to go In Deprecation and breaking changes
- Deprecation
- Marking something as going away, while it still works In Versioning and releases
- Design system
- Shared decisions (tokens, components, patterns, guidelines) and the people and process that keep them alive In What a design system solves
- Detach
- Breaking an instance's link to its main component, so it stops getting updates In Measuring adoption
- Dev Mode
- Figma's workspace for developers to inspect designs In Code Connect and the design-code bridge
- Do and don't
- A pair of examples that shows the right and the wrong use In Component docs people use
- Doc page
- The page that explains one component: purpose, usage, code, accessibility In Component docs people use
- Drift
- The Figma and code versions of a component slowly becoming different In Code Connect and the design-code bridge
- The slow spread of near-copies of the same decision In What a design system solves
- DTCG format
- The Design Tokens Community Group's JSON format for tokens, stable since 2025.10 In Tokens from Figma to code
E
- Edge case
- Content or conditions at the limits: very long, missing, failed, zoomed In States and edge cases
- Evidence
- Research, data or support findings that show why a pattern works In From components to patterns
F
- Fork
- A local copy of a component that drifts away from the system In Contribution models
- A copy of the system, or of a component, that drifts away from it In Multi-brand and multi-product systems
G
- Governance
- The rules for who changes the system, how, and how changes are announced In Contribution models
H
- Hide when publishing
- Keeping an asset in the library file but out of other people's assets panel In Building a Figma library
I
- Icon grid
- The square every icon is drawn on, like 24 by 24 px In Icons and illustration in the system
- Insert
- Placing a library component into a file In Measuring adoption
- Inset, stack, inline
- Space inside a container, between items vertically, between items in a row In Colour, type and spacing as tokens
- Instance swap
- A property that swaps one nested component for another, like the icon In Variants, properties and slots
- Interaction state
- A state the browser sets: hover, focus, pressed In States and edge cases
- Interface inventory
- A collection of every unique version of each interface part, grouped by category In The interface inventory
L
- Layer
- One level of a system: tokens, components, patterns, guidelines In Anatomy of a design system
- Length budget
- The maximum length a layout is designed and tested for In Content and voice in the system
- Library
- A Figma file whose components, styles and variables other files can use In Building a Figma library
- Library analytics
- Figma's usage data for a published library In Measuring adoption
- Live area
- The part of the grid where the drawing sits, inside the padding In Icons and illustration in the system
- Living documentation
- Docs that render the real component, so they change when it changes In Storybook and living documentation
- Locale
- Language and region together, like pt-BR, which set formats for dates and numbers In Content and voice in the system
M
- Major, minor, patch
- The three numbers of a version: breaking, new and compatible, fix In Deprecation and breaking changes
- MCP server
- The interface through which AI coding tools read Figma files In Code Connect and the design-code bridge
- Migration
- Moving existing screens from old components to the system In Bringing teams onto the system
- Migration guide
- Before-and-after instructions for moving from the old thing to the new In Deprecation and breaking changes
- Step-by-step instructions to move from one major to the next In Versioning and releases
- Mode
- One set of values for a collection, such as Light or Compact In Building a Figma library
- A context with its own token values, like light, dark or high contrast In Themes and modes
- Modifier
- The DTCG resolver's name for an axis, with one context per value In Themes and modes
- Modifier, context
- In the DTCG resolver: an axis such as brand, and its options such as Tidewater or Skiff In Multi-brand and multi-product systems
N
- Namespace
- A prefix that marks a system's names, like
hb-In Naming tokens - Near-duplicate
- Two values so close nobody chose the difference, like two blues a few hex digits apart In The interface inventory
- Nested component
- A component inside another, like the Button in the Ticket card In Anatomy and API of a component
O
- Office hours
- A regular, open slot where anyone can bring questions or screens In Bringing teams onto the system
- Open-source design system
- A public system others can use and adapt, like Carbon or Material In When you don't need one yet
- Optical size
- Adjusting an icon's stroke to its size, so it looks the same small and large In Icons and illustration in the system
- Owner
- The person accountable for the system, even part-time In When you don't need one yet
P
- Page type
- A kind of page with a known job: empty state, error page, confirmation In From components to patterns
- Path
- The groups a token sits in, written with dots In Naming tokens
- Pattern
- Components put together to solve a recurring task In Anatomy of a design system
- A reusable solution to a task or a page type, built from components In From components to patterns
- Pilot
- One team using the system on one real flow, with close support In Bringing teams onto the system
- Preferred instances
- The components Figma suggests for a slot or a swap In Variants, properties and slots
- prefers-color-scheme
- The CSS media feature that reads the system's light or dark setting In Themes and modes
- Primitive token
- A raw value with a neutral name:
color.blue.600 = #1F5FAEIn Token tiers - Product layer
- Parts owned by one product, built with the core In Multi-brand and multi-product systems
- Proof of concept
- A quick build to test an idea, likely to change In When you don't need one yet
- Prop
- One input of a coded component, with a name, a type and a default In Anatomy and API of a component
- Prop explosion
- A component with so many props that nobody knows which combinations work In Composition over configuration
- Property mapping
- The table that says which Figma property becomes which code prop In Code Connect and the design-code bridge
R
- Recipe
- A composition shared within one product or family, not the whole company (Frost) In Anatomy of a design system
- A fixed arrangement of system components that a product reuses In Composition over configuration
- A fixed arrangement of components in one product (see Composition over configuration) In From components to patterns
- Reference website
- The documentation site where the system is explained In Anatomy of a design system
- Release notes
- The message for one release: what changed, who needs to act, how In Versioning and releases
- rem
- A CSS unit relative to the root font size, which follows the user's settings In Colour, type and spacing as tokens
- Retired, removed
- Deleted from the system In Deprecation and breaking changes
- ROI
- Return on investment: what you get back for what you spend In When you don't need one yet
- Role
- What an element is to assistive technology: button, dialog, combobox In Accessible components
S
- Scoping
- Limiting which properties a variable can be applied to In Building a Figma library
- Limiting which properties a Figma variable can be applied to In Tokens from Figma to code
- Semantic token
- A purpose that points at a primitive:
color.action.primaryIn Token tiers - Semantic Versioning (SemVer)
- MAJOR.MINOR.PATCH, where each number says what kind of change it is In Versioning and releases
- Single source
- Each fact written in one place, linked from the others In Component docs people use
- Skeleton
- A grey placeholder in the shape of the content that's loading In States and edge cases
- Slot
- An open area in a component that accepts other content In Variants, properties and slots
- Smart component
- A component with logic built in, like validation (Frost) In Anatomy of a design system
- Snowflake
- A one-off component for one screen, not meant for reuse In Composition over configuration
- Solitary, centralised, federated
- Three team models: one product owns it, a dedicated team owns it, product teams own it together In Contribution models
- Source of truth
- The one place a token is edited; everything else is generated In Tokens from Figma to code
- The one place a decision lives; everything else points to it In What a design system solves
- Spot illustration
- A small illustration for one moment, like an empty state In Icons and illustration in the system
- Starter kit
- A ready file or app with the system already set up In Bringing teams onto the system
- State
- An interaction condition: hover, pressed, disabled In Naming tokens
- Status
- How settled a component is: experimental, stable, deprecated In Component docs people use
- Status message
- A change announced by a screen reader without moving focus, often with
role="status"In States and edge cases - Story
- One rendered state of a component, defined by its args In Storybook and living documentation
- Storybook
- A workshop for building and viewing UI components outside the app In Storybook and living documentation
- String
- A piece of interface text, stored with a key In Content and voice in the system
T
- Task pattern
- A pattern for something people do: book, pay, sign in In From components to patterns
- Template
- A page layout with components placed, without real content In From components to patterns
- Template file
- A
.figma.tsfile that defines the code snippet for one Figma component In Code Connect and the design-code bridge - Theme
- A full set of values for the same token names; often brand × mode In Multi-brand and multi-product systems
- A full set of values for a product or brand In Themes and modes
- Theming
- Changing a system's look through its tokens, without rebuilding components In When you don't need one yet
- Tier
- One level of the chain from raw value to component In Token tiers
- Token
- A named design decision, like
color.action.primaryIn What a design system solves - Tone
- How the voice adapts to the person's situation In Content and voice in the system
- Triage
- The first check of a request: is it useful and not already there? In Contribution models
- Type scale
- The fixed set of font sizes a system allows In Colour, type and spacing as tokens
U
- Unique version
- A variant that looks or behaves differently, captured once In The interface inventory
- Usage guidance
- When to use, when not to, and how to use it well In Component docs people use
V
- Variable
- A named, reusable value in Figma: colour, number, string, boolean, timing or easing In Building a Figma library
- Variant
- Which one of the concept: primary, subtle, danger, md In Naming tokens
- One designed version from a fixed list, like
variant=dangerIn Variants, properties and slots - Version lag
- How far behind the latest release a product is In Measuring adoption
- Visual test
- A snapshot of a story compared against an approved baseline In Storybook and living documentation
- Voice
- The personality of the product's words; stays the same everywhere In Content and voice in the system
Saved only on this device.