Keep Calm and Write Sass
summary
Gives concrete rules: avoid deep selector nesting, keep small, readable APIs, and don’t reimplement postprocessing (use an autoprefixer and a rem tool instead of baking hacks into Sass). Recommends documenting with SassDoc, testing public utilities with bootcamp and true, and cites a real case of 3,000 lines removed from a codebase after switching to a rem postprocessor. Emphasizes comments for odd hacks and automated linting.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:43Your CSS is a mess.
- 1:19Broken from the start?
- 1:44Sass to the rescue!
- 2:20Complexity, maintainability scary code...
- 3:24KISS Keep It Simple, Stupid!
- 3:51Write simple APIs
- 5:08Beware of selector nesting
- 5:37Don't do everything in Sass
- 5:51Rethinking Atwood's law
- 6:42Some things shouldn't be done
- 7:44Less code Up-to-date
- 7:56REM? Think twice.
- 8:26Less code Easier
- 9:11Clean your code
- 10:29Document your code
- 11:33Document your Sass
- 13:04Test your code
- 13:56Bootcamp
- 14:36KISS - KYSS clean, test, document
