0 of 2 done
Start hereSass

~1,250 words across 2 notes. [reference].

The concepts — cascade, specificity, tokens, modern CSS — are in 04-styling. This is how specific tools do it.

Files

  • Tailwind CSS — [Intermediate] — the utility-first argument and the honest objection, v4’s move into CSS, cn(), and the dynamic-class-name bug that fails silently
  • Sass — [Intermediate] — what it gave CSS, how much is now native, what it still does better, and whether to start a new project with it

Choosing

Use when
TailwindApplication UI, a component layer, consistency without a CSS review culture
CSS ModulesYou want scoping and plain CSS. The boring correct answer for a lot of projects
SassMaintaining existing Sass, or you genuinely need loops to generate scales
CSS-in-JSHighly dynamic styling — and mind the runtime cost and RSC fit
vanilla-extract / PandaTypes and zero runtime

Whatever you choose, choose one. The bad outcome is Tailwind and styled-components and three global stylesheets — at which point nobody can predict what a change does → CSS architecture.

↑ Back to frontend/frameworks/ — The Implementations