Maintainable Style Guides
summary
A concrete approach: stop copying HTML between docs and apps and serve UI modules from a versioned pattern API. Work involves Node, Angular, React, Sass (Libsass), generators like hologram and middleman and integration with toolkits such as Telerik or Rails engines. A client effort produces 30–40 custom modules that function locally but decay when ownership lapses; another project accumulates 300+ gem dependencies showing brittle governance. Modules must ship HTML, CSS, JS and unit tests and be versioned to be maintainable.
AI-written summary · about
chapters (18)
- 0:00Intro
- 1:15Maintainable Style Guides
- 2:28Patterns
- 3:22Benefits
- 4:59Collaboration
- 7:18Iteration
- 9:34Improved Maintainability
- 10:24Static Style Guides
- 13:18Living Style Guides
- 15:46Challenges
- 18:44Adoption
- 20:43Governance
- 24:49Application
- 25:54Modules
- 28:53Pattern API
- 31:17Pattern API Benefits
- 34:28Pages
- 36:28Conclusion
