refactor(sponsors): replace sass with Tailwind#8118
Open
rolandixor wants to merge 4 commits intowebpack:mainfrom
Open
refactor(sponsors): replace sass with Tailwind#8118rolandixor wants to merge 4 commits intowebpack:mainfrom
rolandixor wants to merge 4 commits intowebpack:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
rolandixor
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
This expands on the work to deprecate SASS (see #8047) by updating
Sponsors.jsxto use Tailwind. It also removesSponsors.scss.What kind of change does this PR introduce?
In
Sponsors.jsxI made the following changes:Sponsors.scssstyles/partials/_vars.scssto ensure visual consistency across the board and that no custom properties were required.Sponsors.scsswas progressively cleaned up and eventually removed.Did you add tests for your changes?
No.
Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
N/A - nothing changes visually since all styles were preserved through Tailwind.
Use of AI
I used AI to identify which files needing to be changed initially, and in tandem with Talwind docs, to assist with identifying some of the correct Tailwind classes to use, and to assist with compilation errors from my mistakes along the way. I also used AI to create the dark mode function. All other code changes are solely the result of manual effort. I take full responsibility for all changes introduced in this PR.