Repository navigation
feat(home): overhaul landing experience - #173
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
The marketing experience split the product story across separate home, tutorial, and concepts pages without clearly showing how the running dungeon maps to executable logic. Marketing routes also initialized game-only providers, while mobile navigation and entry flows needed a more deliberate accessible handoff.
Solution
This rebuilds the canonical home page as a Dungeon Observatory with synchronized runtime proof, an execution path, machine reference, and desktop/touch controls. Tutorial and concepts now redirect to landing deep links, game-only providers load behind the game route, and entry navigation restores focus predictably. Metadata, crawl assets, self-hosted typography, and an optimized product image round out the experience.
Screenshots
Testing
The full local quality gate passes, including structure checks, typechecking, and 1,013 tests across 270 files. Production build and responsive browser verification passed from 360px through 1440px with no horizontal overflow or console errors; desktop and mobile Lighthouse audits scored 100 for accessibility, best practices, and SEO.