Style Documentation for the Resource-Limited
summary
Argues a concrete, incremental method that avoids stop-the-world rewrites: a three-step cycle to identify, codify, document UI components, refactor into Rails helpers or component builders, use SCSS class-extends to consolidate classes, and test output with Nokogiri. Recommends living docs generated with Hologram + KSS and embedding examples so the style guide auto-updates from real code. Claims this is practical for resource-limited teams and notes ActBlue raised $1.1 billion total and about $0.1 billion in the last month or two.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:14you have an accidental styleguide
- 5:42look and feel of individual widgets
- 14:31step 1: identify
- 25:41step 3: document
- 29:56document helpers, not just markup
- 35:30questions?
related talks
45mMaintainable Style Guides
42mThe Dream of Styleguide Driven Development
34mCreating Living Style Guides
37mThe ABC of Coded Style Guides
46mInclusive Development: Using Style Guides to Improve Website Accessibility
42mDesigning Inspired Style Guides
01h 05mStyleguide-Driven Development
34mThe Dream of Styleguide Driven Development
