Migrate Topgear challenge navigation and remove the legacy hero - #2426
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
1 participant
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.
Topgear's community-app migration now uses
/opportunities/challengeas its challenge listing and removes the large “Amazing platform” banner. The existing Topgear group filtering stays in place, and the Universal Navigation companion change supplies the Wipro, Topcoder, and Topgear logos with Home and Challenges.The Topgear root, older Opportunities category URLs, and legacy
/challengeslist resolve to the new path. Legacy list filters and fragments are preserved; challenge detail redirects keep their existing behavior. Other hosts retain their normal Opportunities masthead and routes.The checked-in shared CloudFront viewer-request function adds an uncached HTTP 302 only for
topgear.topcoder-dev.com/challenges(including a trailing slash), preserving repeated and encoded query parameters. Existing Contact/Accounts routing is covered by regressions. Dev DNS already points at Platform UI distributionEFA7R1KH3UX5M; no production DNS or redirect was changed. Deployment/rollback notes are included.Companion: topcoder-platform/universal-navigation#416 — deploy navigation first.
Validation: full lint; 20 focused application tests; three edge-routing tests; full dev build; AWS DEVELOPMENT-stage function checks for the Topgear redirect, production passthrough, challenge details, and Contact routing. Browser verification also confirmed the Topgear group parameter reaches the dev Challenge API with HTTP 200 anonymously. The supplied production JWT is rejected by the dev member API, so authenticated dev data could not be checked with that token.
Deployed and verified on dev on 2026-10-02 (Australia/Hobart). The live
/challengesresponse is an uncached HTTP 302 to/opportunities/challengewith its repeated query parameters intact. The deployed page passed desktop/mobile checks for the logos, links, absence of Leaderboard/hero, and group-filtered Challenge API HTTP 200 with no page errors. CDN invalidations completed, and the published edge function matches the checked-in source. Production/challengesstill serves community-app with HTTP 200.