Tailwind CSS v4 architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Tailwind CSS v4's layering and data flow.
On this page
Quick answer
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.
Machine-readable page data: /data/tailwindcss-architecture.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. Architecture should be edge-first — static pre-render sinks to the edge, dynamic capability falls back to functions with circuit breakers.
/* 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 Architecture · Key takeaways
- Static and dynamic boundaries defined
- Third-party calls wrapped in circuit breakers
- Environment config separated from code
- Boundary contracts documented
FAQ & pitfalls
How do I long-cache Tailwind v4 build output at the edge?
The compiled CSS uses content-hashed filenames with immutable long cache. HTML references the new hash automatically, so no manual cache busting is required.
Explore the hub
See all 5 guides in FrontendSame category as this article, sorted across the codebase.
AI Search architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of AI Search's layering and data flow.
Astro architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Astro's layering and data flow.
Cloudflare Pages architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Cloudflare Pages's layering and data flow.
GEO architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of GEO's layering and data flow.
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 →