Docs: Add link to v4 docs in content-configuration.mdx #2152
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For folks very stuck on content configuration who might be using tailwind v4, add mention of the new docs and clarify that v3 config does not work. A lot of Q/A sites / online resources still only talk about v3 config without mentioning it is for v3 only and v4 docs aren't highly ranked, and attempting to use v3 config does not cause any error. I updated a few questions on stackoverflow as well after spending several hours trying various tooling, path patterns and options to build my packages.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
alexsapps
changed the title
Author
|
@philipp-spiess just letting you know i sent this PR. no worries if you want to make any edits or close it. i figure the v3 and v4 docs should generally be separate but perhaps adding this in the last-ditch troubleshooting section wouldn't hurt. |
Member
|
Hey Alex! Sorry for the super late response but agree that it's probably too much to add to the old v3 docs for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For folks very stuck on content configuration who might be using tailwind v4, add mention of the new docs and clarify that v3 config does not work. A lot of Q/A sites / online resources still only talk about v3 config without mentioning it is for v3 only and v4 docs aren't highly ranked, and attempting to use v3 config does not cause any error. I updated a few questions on stackoverflow as well after spending several hours trying various tooling, path patterns and options to build my packages.