Notes
Tailwind v4 migration notes
What changed moving from config files to CSS-first tokens, and what we'd do differently.
We moved Makershot to Tailwind v4's CSS-first config. Notes from the migration.
What changed
tailwind.config.js → @theme inline in globals.css
Plugins configured differently in PostCSS
@import "tailwindcss" replaces @tailwind directives
What we'd do again
Define semantic tokens in :root and .dark before building components. Migrating colors after the fact is painful.
What surprised us
Custom utilities (ds-display, etc.) are easier in v4. Just add classes in CSS with @layer utilities.
Tooling
shadcn v4 works well with the new setup. Run their CLI against the CSS variable mode.
Related
- 01
AtroUI SEO Master Plan — what we shipped
Summary of the Identity Kit, JSON-LD, sitemap optimization, IndexNow integration, and OG watermarking implemented for AtroUI.
Essay · 3 min read - 02
AtroUI is now in the official shadcn registry directory. Here is why that matters for SaaS builders.
The shadcn registry directory merged @atroui. That means the production sections we use on SaaS MVPs can be installed without a custom registry URL. Lower friction, same ownership.
Essay · 7 min read
Want this built for you?
Fixed-scope MVP sprints and AI integrations. Same stack as this guide.