What NOT to Do in CSS
summary
Advocates Mobile First design (start styles for phone and progressively enhance) and cites mobile traffic and Chrome 74 usage; recommends structuring components (example Card split into Card, Card-image, Card-title, Card-content in one file) and using Sass or PostCSS plus a component file structure. Warns against using !important and id selectors, promotes SVG/Canvas for animated landing visuals, and suggests automated QA, peer review, and linters to keep CSS rules consistent.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 3:45Team communication
- 5:51Mobile First responsive
- 8:40Scalable CSS structure
- 10:25Avoid cascade misuse
- 12:56Avoid !important IDs
- 14:01Refactor components
- 15:46Cross-browser testing
- 17:09Document solutions
related talks
40mThe ABC's of Architecting Better CSS
37mFuture-Proof CSS
31mIn Defence of CSS and the Cascade
29mCSS Architecture for Modern Web Applications
36m10 Commandments for Efficient CSS Architecture
49mBuild Scalable, Automated CSS
39mWhat about CSS? Progressive Enhancement and CSS
30mWriting CSS with Accessibility in Mind