Tailwind CSS

Tailwind's premise offends people on sight. Instead of writing CSS in a stylesheet and giving your elements meaningful class names, you compose a long string of tiny utility classes directly in the markup. It looks like the inline styles everyone was taught to avoid, and the first reaction is usually that this is a step backwards.

The argument for it is worth hearing properly. Naming things is genuinely hard, and most of the time spent on a stylesheet goes into inventing class names that describe presentation badly, then maintaining a growing file nobody dares delete from. Tailwind removes that entire activity. It also removes the question of where a style lives, because it lives where it is used.

The practical case is stronger still: the design system is built in. Spacing, colour and type scales come from a shared config, so a team stops producing seventeen slightly different greys by accident. That constraint is most of the reason Tailwind projects tend to look coherent.

Under an hour required, with another twelve available in the optional lessons if you want a full course rather than a crash course. You should know CSS first. Tailwind is a faster way to write CSS you already understand; used as a substitute for learning it, it produces markup nobody can debug. Take the HTML & CSS course first if you need to.