Using Storybook to Maintain Components and RedwoodJS
summary
RedwoodJS ships Storybook integration so a generated component already includes a .stories.js file and a test, and the demo uses the CLI commands yarn create redwood app and yarn redwood storybook to start Storybook. The demo builds a Button component with primary/secondary/dark buttons implemented via styled-components, documents each variant in the story, and shows a transient dependency hiccup resolved by reinstalling node_modules so the component and its stories run successfully.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:30COMPONENT-DRIVEN DEVELOPMENT
- 24:57ADDING STORYBOOK TO AN EXISTING PROJECT
- 26:45KEY TAKEAWAYS
related talks
39mUsing Storybook to Maintain Components in Redwood
19mIntroducing RedwoodJS: Level Up Your Full-Stack Game
29mRedwoodJS: The Full-Stack React App Framework
07mReact components, atomic design and storybook
38mThinking in Stories: Component-First
31mA Beginner’s Guide To Storybook
24mReact-Storybook"Design, Develop, Document and Debug your React UI components"
37mBridging the gap between UX and development – A Storybook