Tailwind CSS Handbook v4.3

Learning Path

A staged route through Tailwind CSS — what to learn, in what order, and how to tell when you are ready for the next step.

Tailwind is wide rather than deep. There are many utilities but few concepts, so the fastest route is to learn the concepts and look up the utilities. This page sequences them.

The path#

TEXT
  Beginner
     │
     ▼
  Installation ──▶ Utility classes ──▶ Layout ──▶ Responsive design
                                                        │
     ┌──────────────────────────────────────────────────┘
     ▼
  Components ──▶ Dark mode ──▶ States & variants ──▶ Theme / design tokens
                                                        │
     ┌──────────────────────────────────────────────────┘
     ▼
  Advanced customisation ──▶ Production optimisation

Stage 1 — Foundations#

Goal: compile Tailwind and style a static page.

StepPageWhy it matters
1IntroductionUnderstand what problem utilities solve
2InstallationGet a working build with the v4 packages
3Project SetupEditor tooling saves hours from day one
4Your First UtilitiesLearn to read a class name
5Utility-First CSSKnow when to stop adding utilities

You are ready to move on when you can build a static card without checking the docs for padding or text colour.

Stage 2 — Layout#

Goal: build any page skeleton without fighting CSS.

StepPageWhy it matters
6Displayblock, flex, grid, hidden — the starting point of every layout
7FlexboxOne dimension: toolbars, nav bars, button rows
8GridTwo dimensions: page shells, card galleries
9Spacing & SizingRhythm and constraint
10PositionOverlays, sticky headers, badges

You are ready to move on when you can build a header, sidebar and card grid from memory.

Stage 3 — Adaptation#

Goal: one markup tree that works on every screen.

StepPageWhy it matters
11Responsive DesignMobile-first breakpoints
12Container QueriesComponents that adapt to their slot, not the viewport
13States & Variantshover, focus, disabled, group-*, peer-*
14Dark ModeThe media strategy, then the class strategy

You are ready to move on when you stop writing media queries by hand.

Stage 4 — Systematising#

Goal: a codebase, not a collection of pages.

StepPageWhy it matters
15Theme & Design Tokens@theme replaces tailwind.config.js
16ColorsPalette, opacity modifier, contrast
17TypographyType scale and vertical rhythm
18ComponentsButtons, forms, cards, navigation, tables

You are ready to move on when new features reuse existing tokens instead of inventing values.

Stage 5 — Extending#

Goal: make Tailwind fit your product rather than the other way around.

StepPageWhy it matters
19Arbitrary ValuesThe escape hatch, used sparingly
20Custom Utilities@utility for project-specific classes
21Custom Variants@custom-variant for project-specific states
22Functions & DirectivesThe full CSS-side API
23PluginsTypography, forms, and writing your own

Stage 6 — Shipping#

Goal: fast, small, accessible production output.

StepPageWhy it matters
24Production BuildsMinification, caching, bundle budgets
25TroubleshootingDiagnose missing styles quickly
26v3 → v4 MigrationNeeded the moment you touch an older codebase

If you already know Tailwind v3#

Skip to the differences:

  1. v3 → v4 Migration — the upgrade tool and every renamed utility.
  2. Theme & Design Tokens — @theme instead of tailwind.config.js.
  3. Container Queries — built in, no plugin.
  4. Custom Utilities — @utility instead of plugin().
  5. Deprecated APIs — what stopped working and why.

Practice projects#

Each one forces a specific skill.

ProjectForces you to learn
Pricing tableGrid, responsive columns, borders, emphasis
Login formForms, focus-visible, validation states, accessibility
Dashboard shellSticky header, sidebar, overflow, stacking context
Blog post pageTypography scale, max-w-prose, the typography plugin
Product card gridContainer queries, group-hover, aspect ratio
Theme switcherDark mode, CSS variables, localStorage