Leveraging Storybook for Component Driven Development outside of your classic Component Library.
How can you combine visual documentation, interaction simulation, and unit testing all in the same file? Learn how to unify your component workflow with Storybook.
#1about 2 minutes
Addressing the challenges of scaling large web applications
Large applications often suffer from duplicated work and hard-to-reuse components, which component-driven development helps to solve.
#2about 5 minutes
Best practices for designing flexible and reusable component APIs
Adopt principles like single responsibility, composition, and render props to create modular and maintainable component APIs from the start.
#3about 6 minutes
Getting started with Storybook for isolated component development
Use Storybook to build UI components in isolation, write stories to document different states, and get auto-generated documentation.
#4about 2 minutes
Handling complex components with state and API calls
Replicate complex component behaviors in Storybook by mocking API calls with MSW and managing global state with decorators.
#5about 3 minutes
Integrating user interactions and Figma designs into Storybook
Use the play method to script user interactions within stories and integrate Figma designs directly for better design-to-code consistency.
#6about 2 minutes
Leveraging stories for UI and visual regression testing
Import stories directly into React Testing Library for UI-driven testing and use Chromatic for automated visual regression testing.
#7about 2 minutes
Using Storybook to build and maintain shared libraries
Well-documented components in Storybook make it easier to identify reusable patterns and extract them into a shared component library.
Related jobs
Jobs that call for the skills explored in this talk.
Micro Components - a different approach to a simpler component-based webThere has been a lot of heated discussion lately in the web community about component based development. One side argued that Web Components are a standard we should follow whereas others complained that they still lag behind in what frameworks offer...
Christina Schaireiter
Why Attend a Developer Event?Modern software engineering moves too fast for documentation alone. Attending a world-class event is about shifting from tactical execution to strategic leadership.
Skill Diversification: Break out of your specific tech stack to see how the industry...
Daniel Cranney, Chris Heilmann
Dev Digest 215: Agent Memory, JS2026, Googlebot Analysis & Canvas❤️HTMLInside last week’s Dev Digest 215 .
🗿 Make AI talk like a caveman
🧠 A guide to context engineering for LLMs
🤖 Simon Willison on agentic engineering
🔐 Axios supply chain attack post mortem
🛡️ Designing AI agents to resist prompt injection
🎨 HTML in c...