Building a component library with React, Vue, Angular or WebComponents
summary
Compares rolling a bespoke style guide versus using existing tools and shows working demos of Storybook and UI Engine, arguing that building your own often becomes deprecated and costly while extensions of OSS scale better. Demonstrates that Storybook renders components in an iframe so media queries and devtools behave, supports React Vue Angular WebComponents and more, and can show multiple previews / viewports of one component simultaneously. Notes the Storybook manager written in React so add-ons require some React knowledge and maintenance effort.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:48Isolated Component Driven Development
- 3:04Features
- 6:02Do-It-Yourself Approach and the Pros and Cons
- 7:27Should You Be Writing Your Own Style Guide
- 8:33Ui Engine
- 9:21React Style Guide Test
related talks
34mComponent Documentation Made Easy
24mCase Study: Creating a Component Library in React JS
27mThe story of storybook
07mReact components, atomic design and storybook
32mThe Modern Way of Making Websites in React
15mOnce Upon a Time Storybook
24mA Short Synopsis of Vue Storybook
46mBuilding Reusable Components ... That Are Actually Reusable