Atomic Design: atoms, molecules, organisms, templates, pages

Atomic Design (Atomic Design) is methodology developed by Brad Frost for building design systems. Its essence is breaking interface into five abstraction levels, starting from simplest elements (atoms) and ending with full pages. This facilitates reuse and scaling of interface components.

Main Atomic Design Levels

Atoms

Basic interface elements: buttons, links, inputs, headings, color and typography variables.

Don't contain business logic and usually only responsible for display.
Are foundation of design system.

Molecules

Groups of atoms collectively solving small interface task.

Molecules still don't include complex business logic.
Example: login form (input + button), profile card (icon + text).

Organisms

Larger and more complex UI parts consisting of several molecules (and/or atoms).

Can contain first signs of business logic, but overall focused on UI.
Example: navigation panel (with nested items, search forms, buttons).

Templates

Skeleton page layouts defining placement of organisms, molecules and atoms.

Don't contain specific content, but set structure.
Example: home page layout with header, content block and footer.

Atomic Design Advantages

Clear Organization
Each component has its place in hierarchy: atom, molecule, organism, template or page.
Reuse
Atom or molecule needs to describe styles and behavior once. Then they can be reused in various places of application.
Consistency
All UI elements are united by unified visual style and principles. Change in atom (e.g., color) automatically applies to all molecules and organisms where it's used.
Faster Development
Thanks to ready set of "building blocks" (atoms, molecules, organisms), you can quickly assemble new pages and templates.

Atomic Design Disadvantages

Not Suitable for All Project Types
Works great for design systems and UI libraries, but can be excessive for large business applications where complex logic and structure are important.
Blurred Boundary Between Levels
In real projects it's sometimes hard to determine what belongs to molecules and what to organisms. Disputes and confusion arise.
Lack of Business Orientation
Approach primarily solves UI questions; it doesn't address business logic organization in project.

When to Use Atomic Design

Creating or Developing UI Kit
Atomic Design serves as ideal foundation for design system, where uniform styling and component reusability are important.
Projects with High Change Frequency
If interface is frequently redesigned and updated, methodology helps quickly make edits by changing atoms and molecules.
Team Work
With large number of developers and designers unified UI architecture speeds up communication and reduces risk of duplication.

Summary:

Atomic Design is powerful methodology for structuring components and simplifying UI element reuse. It's ideal for forming design systems and speeds up product creation process. However, if your project contains extensive business logic or doesn't need such detailed interface division, Atomic Design may be excessive. In such cases it can be combined with other architectural approaches (e.g., FSD or modular structure) for more complete business requirement implementation.