Edit Tailwind style section to change links and wording

[anaxite]

Description

In the Tailwind section of the docs, add a link to the part of the Tailwind website that talks about the Vite plugin.

(Discussed in Talking and Doc'ing)

Related PR

Relates to PR withastro/astro#13471

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/concepts/why-astro.mdx	Source changed, localizations will be marked as outdated.
en/getting-started.mdx	Source changed, localizations will be marked as outdated.
en/guides/integrations-guide/index.mdx	Source changed, localizations will be marked as outdated.
en/guides/migrate-to-astro/from-create-react-app.mdx	Source changed, localizations will be marked as outdated.
en/guides/styling.mdx	Source changed, localizations will be marked as outdated.
en/install-and-setup.mdx	Source changed, localizations will be marked as outdated.
en/reference/integrations-reference.mdx	Source changed, localizations will be marked as outdated.
en/reference/programmatic-reference.mdx	Source changed, localizations will be marked as outdated.
en/upgrade-astro.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	9fb9977
🔍 Latest deploy log	https://app.netlify.com/sites/astro-docs-2/deploys/67ee88a12ba43900089272e8
😎 Deploy Preview	https://deploy-preview-11279--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Adammatthiesen]

🐢 📚

[Fryuni]

T&D observation squad

[JusticeMatthew]

T&D Squad reporting in

[sarah11918]

Adding a comment from a maintainer's discussion (still not sure whether we're going to deprecate the integration or not, so we can't have definitive docs yet!) re: what the new docs should account for:

OK, so it seems like we can prioritize the likelihood here:

a. I am starting a new project fresh (I'm not suddenly adding Tailwind to a 2 yr old project)

• You are getting an updated version of Astro, and you astro add tailwind and you get Tailwind 4
• The escape hatch is I want to install Tailwind 3 with this new project, because I'm not prepared to use Tailwind 4 yet

b. I have a project already, where I already added Tailwind (again, most people don't decide months later to add tailwind)

• I want to upgrade to Tailwind 4 (default path/assumption)
• I want to upgrade all other dependencies but stay on Tailwind 3 for now

I think framing it as new vs existing projects makes sense, because in a new project, we can be (relatively) assured that they're at least getting the new version of Astro where the CLI command installs the vite plugin

[sarah11918]

OK! Made a big commit that we can go over on Talking and Doc'ing tomorrow!

[florian-lefebvre]

However, you may see a message in your terminal with instructions for upgrading to Tailwind 4

What is this referring to? Is it supposed to be the deprecation NPM package for the day we deprecate?

[trueberryless]

Hi!