Styleguide-Driven Development
summary
Claims that moving from scattered hard‑coded styles to a system of reusable components and documented rules cuts maintenance and speeds delivery, shows a concrete migration path (hard‑coded → variables → components → external tokens → runtime theming) and demonstrates tooling: design tokens stored as JSON and auto‑exported with Style Dictionary. Gives a striking data point — 2449 unique hex codes on one UI — describes generating platform files (web, iOS, Android) and shows the system working while warning not to overbuild for throwaway prototypes.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:58Traditional process
- 7:14System of reusable components
- 17:04Design system
- 20:13Properties
- 26:32Implementation
- 31:41Design Tokens
related talks
01h 05mStyleguide-Driven Development
48mA practical guide to style guide driven development
37mThe ABC of Coded Style Guides
21mEstablishing the rules for a universal design system
28mThe Night of the Living Style Guides
28mScalable CSS Architecture with Design Tokens
35mDesign Tokens for Cross-platform Design Systems
29mCreating universal design systems across web and mobile with Utility First Styling
