Tailwind CSS v4 hands-on tutorial: from zero to your first runnable project
Step-by-step walkthrough of Tailwind CSS v4 with copy-paste commands, directory layout, and a first runnable artifact.
On this page
Quick answer
What is the biggest config difference between Tailwind v4 and v3?
v4 drops tailwind.config.js and declares themes entirely in CSS via @theme. Upgrading requires deleting the old config and installing @tailwindcss/vite — otherwise the build fails with a missing module.
Machine-readable page data: /data/tailwindcss-tutorial.json
In-depth analysis
Tailwind CSS v4 replaces the bulky JavaScript config file with a CSS-first @theme directive, improving both build speed and control. Going from zero to a first runnable project is about locking in the smallest end-to-end loop before you scale.
/* src/styles/global.css — Tailwind v4 CSS-first config, no tailwind.config.js needed */
@import 'tailwindcss';
@theme {
--color-brand: oklch(0.62 0.19 265);
--font-sans: 'Inter', system-ui, sans-serif;
}Tailwind CSS v4 Hands-on Tutorial · Key takeaways
- Project initialized with the official scaffold
- Dependencies pinned to a single pnpm lockfile
- Local dev server starts and first paint is reachable
- First runnable commit pushed
FAQ & pitfalls
Why are my Tailwind v4 custom brand colors not rendering?
Colors must be declared inside @theme (e.g. --color-brand). Forgetting @tailwindcss/vite, or still referencing the old config, makes bg-brand silently fail to render.
Explore the hub
See all 5 guides in Hands-onSame category as this article, sorted across the codebase.
Astro best practices: engineering conventions for production
Field-tested Astro practices from production, avoiding the common anti-patterns.
Astro deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven Astro deployment in practice: commit to build, atomic publish to every edge node.
Astro performance tuning: push first paint and edge response to the limit
Around Astro's real bottlenecks, an actionable LCP / INP / CLS checklist.
Astro hands-on tutorial: from zero to your first runnable project
Step-by-step walkthrough of Astro with copy-paste commands, directory layout, and a first runnable artifact.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide → - 02
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 03
Why are _headers / _redirects not taking effect?
Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.
See the full guide →