CSS as a Service: Maintaining Style
summary
Argues for a central CSS package that serves many codebases, implemented as a Node module (or gem) and documented in a separate style guide, with a master rolodex import, namespaced folders, normalize.css baseline, and Sass features like Sass maps and mixins to generate theme and utility classes. Claims modular single‑responsibility components cut duplication; measured results at two companies show substantially smaller CSS file size, fewer unique selectors, and overall improved maintainability.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:21The Problem
- 4:16ServiceOriented Architecture
- 5:26Design Concerns
- 6:06Agenda
- 6:44Working backwards
- 9:44Normalize CSS
- 9:58MasterRolodex
- 10:54Settings
- 12:04Components
- 12:54Component Example
- 13:34Implementation
- 18:20Naming
- 19:03Un unrecognizable class names
- 20:49predictable class names
- 21:43sass
- 22:46arguments
- 23:21maps
- 24:35functional CSS
- 25:38this is complicated
- 26:57find a sandbox
- 27:24internal feedback
- 27:42measure your improvements
- 28:24file size
- 28:56property counts
- 29:37Bootstrap themes
