Write Less CSS
summary
Claim: writing less CSS reduces bugs, inconsistency, and developer friction. Concrete moves: adopt utility classes with a predictable breakpoint/property signature so small sharp tools replace bespoke rules, avoid cascades that produce a specificity of 131 and rampant !important, and generate tokens and docs from source with Style Dictionary. Meetup reports switching to this approach two years ago and it works exceptionally well for rapid prototyping, fewer stylesheet edits, and always-accurate documentation.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:32A hammer, in CSS
- 2:41CSS is a render blocking resource.
- 3:45technical problems
- 3:59Conway's Law
- 6:21Breaking the cycle
- 6:31Utility classes to the rescue
- 8:02Benefits of utility classes
- 8:51Presentational classes are scary
- 10:40Level of abstraction
- 11:28Foster a good relationship between engineering and design
- 14:11To write less CSS...
related talks
18mIn Defense of Utility-First CSS
01h 04mCSS for Software Engineers for CSS Developers
40mThe ABC's of Architecting Better CSS
49mBuild Scalable, Automated CSS
31mIn Defence of CSS and the Cascade
55mRefactoring CSS
33mCSS for Software Engineers for CSS Developers
36m10 Commandments for Efficient CSS Architecture