chore(frontend): optimize tailwind v4 theme and move font variables t…#41
Merged
Merged
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
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.



Tailwind v4 Theme Optimization
Overview
This PR optimizes the frontend CSS layer by fully embracing the Tailwind CSS v4 "CSS-first" paradigm. Custom theme logic has been migrated from JS-style declarations into the main CSS entry point, and legacy Tailwind v3 compatibility hacks have been removed.
Changes
--font-sans,--font-handwritten) from:rootinto the@theme inlineblock inindex.css.--color-brandand--color-brand-foregroundaliases to the Tailwind theme, mapping them to the primary brand colors for better semantic usage..font-handwrittenclass declaration as it is now automatically handled by the Tailwind v4 theme engine.@custom-variant darkhack, relying on Tailwind v4's native dark mode support.@themeblock to ensure Shadcn-vue's CSS variables are properly integrated with the new Tailwind v4 engine, minimizing runtime overhead.Verification
npm run lintpasses.npm run buildcompletes successfully, confirming that Tailwind v4 correctly processes the updatedindex.css.