Summary
Nathan Curtis's foundational text on building design systems before "design systems" was common vocabulary. Focuses on breaking interfaces into reusable components and documenting them for team adoption.
Core Concepts
- Component breakdown - Decomposing pages into atomic, reusable pieces
- Pattern libraries - Organizing and documenting components
- Design + code alignment - Bridging design specs and implementation
- Governance models - Who owns what in a component system
Application to Digital Garden
| Concept | UXLab Application |
|---|---|
| Component catalogs | /examples pages, component catalog slideover |
| Documentation patterns | templates/ collection for reusable structures |
| Naming conventions | kebab-case for slugs, Title Case for display |
| Token systems | CSS custom properties in themes |
Key Takeaways
- Start with inventory - Audit existing UI before building system
- Document usage, not just specs - Show when/why to use each component
- Plan for variation - Components need flexibility without chaos
- Governance is culture - Systems need ongoing stewardship