“A Working Theory of Components”
summary
Argues a component must be easy to reason about, context agnostic and independent and isolated, then gives a concrete checklist to enforce that: self‑documented props, unit and visual‑regression tests, single namespace for styles, no external layout, and accessible defaults. Describes implementing this across stacks — Sass + Handlebars for a PHP app, then Sass + React with Soy templates for Java — and reports the repo checklist and tests keep many teams using shared components reliably.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:56Evolution of front-end development
- 6:28Design systems promise
- 11:58Core principles of components
- 16:18Easy to reason about components
- 16:40Context agnostic components
- 19:52Independent isolated components
- 23:33Applying theory with legacy tools
- 26:45Component checklist
- 32:29Testing and refining theory
- 33:10Future of component design
- 33:54Q&A
related talks
24mA Working Theory Of Components
21mShared Components Beyond the Design System
44mA Practical Guide for Crafting Resilient UI Components
24mFrom Sketch to Code Designing a Component Kit
44mThe Future is in Pieces
25mBuilding a Design System as a team
26mComponents, Patterns and Other Not-So-Simple Things to Manage
44mWriting good components