Replies: 1 comment
-
|
Thanks for maintaining the project! If this direction makes sense, I would be happy to help propose a documentation update or draft wording for the installation page. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
While following the installation documentation, it may not be obvious to users coming from Tailwind v3 that the configuration and setup workflow has significantly changed in v4.
Migration information already exists in the upgrade guide, but users who start from the installation page may not realize they should review migration guidance first.
Expected behavior
The installation documentation should clearly indicate that Tailwind v4 introduces breaking workflow differences compared to v3 and guide migrating users to the upgrade guide before beginning setup.
Actual behavior
Users may attempt to apply v3 configuration patterns during installation, which can lead to confusion or failed setup before discovering migration differences.
Suggested improvement
Consider adding a short visible note near installation/setup sections indicating that:
Additional context
I searched existing open and closed issues related to Tailwind v4 migration and found they mainly address runtime or upgrade bugs, but not documentation expectations prior to installation.
Beta Was this translation helpful? Give feedback.
All reactions