Repository navigation
Conversation
chore: sync main back to develop
…rhaul feat(home): overhaul landing experience
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
Develop now contains the approved Dungeon Observatory landing overhaul from PR #173, while main still serves the previous marketing experience. The release needs to promote the tested develop state without introducing additional changes.
Solution
This promotes the canonical landing rebuild, consolidated tutorial and concepts deep links, game-route provider isolation, accessible entry navigation, and updated metadata and crawl assets to main. The release diff is identical to the feature tree reviewed and merged in PR #173.
Screenshots
Testing
The promoted tree passed the full local quality gate and the feature PR CI, including structure checks, typechecking, and 1,013 tests across 270 files. Production build and responsive browser verification passed from 360px through 1440px, and desktop and mobile Lighthouse audits scored 100 for accessibility, best practices, and SEO.