feat(web): refine project proof grid and scroll reveal - #11
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.
Problem / Goal
The production-baseline homepage had a proof section that rendered real project evidence as an undifferentiated vertical stack, while the first scroll reveal was too subtle to observe reliably. Make the evidence scannable and make the reveal visibly communicate project proof without replacing the existing cosmic hero.
Change
Non-goals
Verification
pnpm --filter @weapp.dev/web check— 0 errors, warnings, or hints.pnpm --filter @weapp.dev/web lint:styles— pass.pnpm --filter @weapp.dev/web build— 28 pages; 29 required outputs/internal links validated.git diff --check— pass.Compatibility / Risk
The scroll synchronizer is inline and dependency-free, throttled to one update per 16ms, and fully disabled/reset when reduced motion is enabled. Existing static content remains available without JavaScript. Responsive breakpoints are covered by browser assertions.
Rollback
Revert the single commit on this PR. No data migration or deployment-side state is introduced.
Issue linkage
None.