Migrate presentation layer to Tailwind and retire the ported global stylesheet - #62
Open
hta218 wants to merge 27 commits into
Open
Migrate presentation layer to Tailwind and retire the ported global stylesheet#62hta218 wants to merge 27 commits into
hta218 wants to merge 27 commits into
Conversation
Define the issue #61 architecture, phase gates, protected runtime contracts, and verification matrix before implementation.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Summary
@themetokens without redesigning shopper behaviorcva, colocate route-owned Cart/Account/PDP presentation, and add durable architecture guards against legacy selectors and ownership regressionsparse5AST parsercanonical-source.css,site-header.css, andproduction-polish.css; keepglobals.csslimited to Tailwind, semantic tokens, document policy, and the three shell keyframesVerification
bun run check: 372 node tests, 66 DOM tests, GraphQL, 42-page production build, 202 exact compiled theme-token values, and route contract passedbun audit --production: no vulnerabilitiesDecisions and risk
Closes #61
Related to Weaverse/builder#2663