Maintaining and Modernising CSS
summary
Practical, measurable items decide: running Project Wallace and Chrome coverage finds a surprising 64% unused CSS on a homepage; Puppeteer or CSSstats help bulk-audit. Propose tickets for quick wins (replacing grimy cabinet handles analogy — small change that visibly works), log tech debt, measure before/after file size and developer time, use Google’s baseline checker to set safe feature targets, and follow refactoring tunnels to update components incrementally.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 5:22Legacy CSS importance
- 14:52CSS audit tools
- 20:33CSS pain points
- 24:23Convincing stakeholders
- 31:26CSS refactoring steps
- 37:49Progress over perfection








