Component Driven Development
Building interfaces from the bottom up, one component at a time in isolation, before assembling them into pages.
In more detail
CDD stands for Component Driven Development. Working in isolation forces components to take everything they need as props, which exposes hidden dependencies on global state or leaky styles. Each state is captured as a story that doubles as documentation and a test case.
Related terms
- Storybook — An open-source workshop where you develop, view and test components in isolation, one story per state.
- story — In Storybook, one saved example of a component in a particular state, such as Button in its primary or loading state.
- composition — Building a component out of smaller components that the consumer assembles, instead of configuring one big component with flags.
Taught in
- Storybook & Component Driven Development Workflows — Design Systems & Component Engineering