Polish Home particle first frame and navigation - #4
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.
Summary
Root cause
The previous client engine began from a scatter state and retired a solid-text fallback only after asynchronous Three.js and font initialization. That made the initial render visibly different from the stable particle state. Window-based geometry also left resize and context-loss edge cases.
Impact
The Home page now opens directly into the intended particle visual, remains legible at desktop and mobile breakpoints, and avoids unnecessary animation work when hidden or offscreen. Education, Past Experience, and Current Chapter source content is unchanged.
Validation
npm run check— static export plus 16/16 artifact tests passednpm audit --omit=dev --audit-level=moderate— 0 vulnerabilitiesgit diff --check— passedorigin/main