Storybook
The standard workshop for developing and documenting components in isolation.
Definition
A development environment where components are built and viewed independently of the application, with every state and variant addressable, plus accessibility and interaction testing addons.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
Good for
- Component development
- State and variant documentation
- Accessibility and visual testing
Watch out for
Storybook decays without ownership. Stories that drift from real usage are worse than none, because they document a component that no longer exists.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Often used with
These usually appear in the same screen or the same decision.
- Component API DesignDesign system
- Design System DocumentationDesign system
- ChromaticTool
- Visual StatesUI foundation
Nearby in the Atlas
Adjacent territory, found through shared tags rather than a stated link.