Case Study: Creating a Component Library in React JS
summary
Builds an internal React component library called Milan component library for three web apps used by a six–seven person engineering team and ships it as a private package. Chooses Storybook + Rollup for documentation and bundling, uses GreenSock for animation and CSS variables for theming. Starts with 8–10 starter components, iterates monthly for over a year, improves accessibility and consistency, and finds opportunistic maintenance and flexible components actually lead to company-wide adoption.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:34The Problem
- 8:40Choosing Components
- 12:45Implementation
- 18:28Maintenance
- 19:31Missteps
- 19:45Keep it Simple
- 21:27Keep Unfinished Components
- 22:55Accessibility
related talks
43mBuilding a component based library with React
46mBuilding Reusable Components ... That Are Actually Reusable
33mKickstarting a library of internal React components for multiple teams
32mKickstarting libraries of shared React components for multiple teams
54mCase sudy: Lucentum, creating our own React component library
44mBest Practices on building a UI component library for your company
14mBuilding a component library with React, Vue, Angular or WebComponents
07mBuilding Component Libraries for Cross Team Use with React