v4-compatible standalone blog post following the old v3 one

[rozsazoltan]

Fixes: #2213 and partially #2212

• v3-related: /blog/standalone-cli
• v4-related: /blog/2025-04-18-standalone-cli-for-v4

I didn't make many changes to the original standalone CLI post. I updated the installation steps, removed the init process, and added a note that the tailwind.config.js file is no longer necessary. I also included a link to the CSS-first configuration guide.

Additionally, I made a small update to the old post to reference the new one.

I added myself as the author, but I'm not sure what the usual convention is; feel free to change it.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
tailwindcss-com	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 18, 2025 0:25am

[philipp-spiess]

Hey! Thanks but I feel like a blog post is not a good spot to document the Standalone CLI, we should definitely have something in the docs that we keep updated, though.

Adding a blog post would indicate that something new has happened just now which I don't really think is the case beyond the v4 release that changed the CLI.

Maybe instead there could be a version of https://tailwindcss.com/docs/installation/tailwind-cli that talks about how to install the standalone build (rendered like e.g. https://tailwindcss.com/docs/installation/framework-guides/laravel/vite but not necessarily linked from anywhere but the link in https://tailwindcss.com/docs/installation/tailwind-cli)?