Implement responsive landing page and restructure explorer - #34
Merged
priscaenoch merged 1 commit intoJul 29, 2026
Merged
Conversation
- Move existing explorer functionality to `/explorer` - Create new responsive landing page at root (`/`) featuring a hero, features grid, and live testnet contract links - Update navigation and routing for the new application structure - Add unit tests for the new landing page - Fix pre-existing test timeouts in BackendStatusBanner by removing fake timers that stalled React Query - Fix EventPage test asserting against undefined instead of null - Run format and lint fixes across the codebase
|
@jrcity is attempting to deploy a commit to the Prisca's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
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
2 participants
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.
This PR introduces a dedicated, responsive landing page for the Octraban Frontend and formally separates the core explorer functionality into its own route.
Changes Included
Home.tsxhas been renamed toExplorer.tsxand moved to/explorer. The application root (/) now serves the newLanding.tsxcomponent./) featuring:stellar.expertlinks.Nav.tsxnow prominently features an "Explorer" link to clearly direct users.Landingcomponent intest/Landing.test.tsxverifying tagline rendering, correct CTA routing, and correct Stellar Expert href links.test/Home.test.tsxtotest/Explorer.test.tsxto maintain parity.test/BackendStatusBanner.test.tsxthat were stalling due to incorrect NodeAbortSignaland fake timer interactions.test/EventPage.test.tsxfailure by correctly asserting againstnullinstead ofundefinedAPI responses to align with React Query v5 default behavior.npm run format:fixandnpm run lint:fix.Motivation
Providing an introductory landing page gives new users immediate context about what Octraban is and what it does before throwing them into a wall of technical data. Separating the explorer into its own route provides a cleaner structure as the app grows.
Verification
npm testpasses successfully.npm run buildsucceeds cleanly.npm run lintpasses successfully.Closes #6