Building Reusable Components ... That Are Actually Reusable
summary
Explains why reusable component libraries require dedicated staff and concrete choices: started from open‑source (Material UI / React Bootstrap / Ant Design), wrote custom docs instead of vanilla Storybook, use TypeScript to enforce mutually exclusive props and reduce runtime errors, publish semantic release notes, and saw value at scale — one codebase supports 100 React applications after growing to a 7-person team and surviving 5 breaking releases. Shows docs, prop tables, demo copy/paste snippets, and API patterns (rigid-first, then extend).
AI-written summary · about
chapters (15)
- 0:00Introduction and speaker background
- 3:15Why reusable components are hard
- 5:24The need for dedicated teams
- 7:08Real-world component library example
- 9:35Reusable components are never done
- 11:23Power of abstraction in component libraries
- 14:53Documentation essentials for component libraries
- 19:26TypeScript and API design
- 27:17Starting with an audience of one
- 30:08Balancing rigidity and flexibility
- 33:37Enforcing prop combinations with TypeScript
- 37:10Grouping related props for clarity
- 40:37Programmatically generated docs
- 42:05Styling flexibility in component libraries
- 44:33Wrap-up and resources
related talks
23mBest Practices for reusable UI components
30mReusability: Sharing Components
24mCase Study: Creating a Component Library in React JS
43mHow to build your reusable UI component library like a pro
24mDesigning Components for Fun, Profit and Sanity
44mWriting good components
07mReact components, atomic design and storybook
25mFrom Design Systems to Component Libraries