It’s all about components
summary
Argues components must be designed as versioned, isolated products with their own build pipelines and tests, not just renamed UI bits; demonstrates a working e‑commerce demo where a product card composed of smaller components is themeable, versioned, and shows passing tests, a live Figma embed and dependency graph. Uses concrete tools: Bit (bit.dev) for component hosting and composition, React + TypeScript, CSS vars and design tokens exported as design tokens as JSON, mentions an internal visual CI called Ripple CI visual diff for impact checks.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:59Why talk about components
- 8:16Themeable composable components
- 15:55Build or reuse components
- 17:37Design tokens for design system
- 23:11Designer collaboration on components
- 28:24Component library from scratch
- 30:27Configurations as components
- 32:09Component-driven development principles
- 36:19Q&A
- 38:49Q&A versioning dependencies
- 41:37Q&A file structure
related talks
20mTaking Component Driven One Step Further
39mDesigning with Components
22mArchitecting Subcomponents
57mComponent Driven Repo for a Component Driven World
55mComponent Driven Repo for a Component Driven World
27mUp and Running with Universal Components
24mDesigning Components for Fun, Profit and Sanity
35mDesign system - From a Developer Point-of-View