feat: Add tailwind for utility classes #562
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🎯 Changes
Tailwind offers utility classes which make complex styling extremely easy without writing raw CSS manually. In particular, the layout classes will be useful here as they prevent you from making very similar ".container" classes all over the place. The new site will also use a combination of tailwind + custom CSS.
There's plenty more that can be done, but this already fixes the footer not sticking to the bottom of the page, as well as removing the large spacing between the header and headings.
postcssalso reported some issues with CSS value browser support.✅ Checklist
pnpm run lintlocally on my changes