CSS for Software Engineers for CSS Developers
summary
Argues for stealing classical SE patterns for CSS and gives concrete techniques: use preprocessors and mixins to enforce a single source of truth (e.g., $unit variable instead of repeated 12px), split components by single responsibility into base, modifier and utility classes (BEM-style), preserve immutability by avoiding nested selectors, using modifier classes and responsive suffixes instead of context-sensitive mutations, use !important only on utilities, and keep things open for extension closed for modification by adding new classes rather than changing existing ones to avoid regressions.
AI-written summary · about
chapters (6)
- 0:00Intro
- 5:35Don't Repeat Yourself
- 10:46The Single Responsibility Principle
- 15:31The Separation of Concerns
- 21:24Immutability
- 27:25The Open/Closed Principle
