Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/UX Design Foundations/Atomic Design by Brad Frost
Level 4 · Principles of Design

Atomic Design by Brad Frost

14 min read
6 exercises
250 XP
Start lesson

Ready to test what you learned?

Complete the lesson quiz and earn 250 XP.

Start quiz

Topics in this lesson

The Chemistry Metaphor in UI ArchitectureLevel 1: Atoms — The Indivisible Building BlocksLevel 2: Molecules — Purpose-Built Functional UnitsLevel 3: Organisms — Complex Standalone Interface SectionsLevel 4: Templates — Content-Agnostic Layout SkeletonsLevel 5: Pages — Concrete Instances with Real-World Data

From Course

📘
UX Design FoundationsBeginner · 25 lessons
Atomic Design by Brad Frost

Lesson

Atomic Design by Brad Frost

The Chemistry Metaphor in UI ArchitectureLevel 1: Atoms — The Indivisible Building BlocksLevel 2: Molecules — Purpose-Built Functional UnitsLevel 3: Organisms — Complex Standalone Interface SectionsLevel 4: Templates — Content-Agnostic Layout SkeletonsLevel 5: Pages — Concrete Instances with Real-World Data
Start lesson
Complete lesson and earn 250 PX
Exercise #1

The Chemistry Metaphor in UI Architecture

In 2013, web designer Brad Frost introduced Atomic Design, a mental model and structural methodology for crafting scalable design systems inspired by natural chemistry.

In the physical world, all matter is composed of atoms that bond together into molecules, which combine into complex organisms. Similarly, digital user interfaces are constructed from a hierarchical taxonomy of modular components:

  1. Atoms
  2. Molecules
  3. Organisms
  4. Templates
  5. Pages

Atomic Design bridges the gap between abstract design tokens and concrete production applications, establishing a shared language for designers and software engineers.

Exercise #2

Level 1: Atoms — The Indivisible Building Blocks

Atoms are the foundational, indivisible elements of a user interface. They cannot be broken down further without losing their functional identity:

  • Examples: HTML tags, color tokens (#3B82F6), typography styles, raw input fields, buttons, icons, avatars, and labels.
  • Characteristics: In isolation, an atom is abstract and carries little context. A button atom sitting alone on a canvas communicates interactivity, but achieves no product goal until combined with other elements.
Exercise #3

Level 2: Molecules — Purpose-Built Functional Units

Molecules are relatively simple groups of UI atoms bonded together to function as a single unit:

The Classic Search Molecule

Combine three distinct atoms:

  1. A text label atom ('Search our docs')
  2. An input field atom (<input type="text">)
  3. A button atom with magnifying glass icon (<button>)

Individually, these atoms are inert. Bonded together, they form a Search Form Molecule with a clear, single purpose: submitting a search query.

Molecules are designed for high reusability across headers, footers, sidebars, and empty states.

Exercise #4

Level 3: Organisms — Complex Standalone Interface Sections

Organisms are relatively complex, distinct UI sections composed of groups of molecules, atoms, and sometimes other organisms:

  • Examples: Global navigation headers, product overview cards, comment threads, checkout summary bars, and multi-column data tables.
  • Behavior: An organism forms a discrete, recognizable section of an application. For example, a Global Header Organism might contain a logo atom, primary navigation link molecules, a search molecule, and a user profile avatar organism.
Exercise #5

Level 4: Templates — Content-Agnostic Layout Skeletons

With templates, Atomic Design shifts from the chemistry metaphor to page construction:

  • Definition: A template is a wireframe-like structural skeleton that arranges organisms, molecules, and atoms into an overarching page layout.
  • Content-Agnostic Nature: Templates define the spatial blueprint, responsive grid columns, and container constraints, but contain placeholder content rather than production data.
  • UX Value: Templates demonstrate how components adapt across breakpoints and define where dynamic modules live.
Exercise #6

Level 5: Pages — Concrete Instances with Real-World Data

Pages are specific, concrete instances of templates populated with authentic production text, images, and live data feeds:

The Stress-Testing Role of Pages

Pages test the structural integrity of the design system under realistic edge cases:

  • What happens to the article card organism when a headline is 140 characters long?
  • How does the layout respond when a user has no profile photo?
  • What does the dashboard look like in German or Japanese, where word lengths expand by 30%?

By populating templates with real data, teams validate whether the underlying atoms and molecules hold up in the real world.