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

Taught in

References