feat(header): add Catalog link to the top nav#36
Merged
Conversation
Link the main site to the MCP catalog so visitors can discover it and navigation reads as one site. Same-tab hard nav (like Dashboard) styled with the standard nav underline. URL derived from the apex per environment (catalog.<fqdn>/mcp).
|
✅ CI - Verify PASSED Commit:
|
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.
What
Adds a Catalog item to the main-site top nav, linking to the MCP catalog (
catalog.<fqdn>/mcp). Closes the discovery loop: visitors on agentage.io can now reach the catalog, and moving between the two reads as one site.Details
header.tsx- new nav entryCatalogbetween Blog and Dashboard,hard: trueso it's a same-tab full-page nav (the catalog is a separate host) with the standard nav-underline styling - identical treatment to the existing Dashboard link.site.ts-CATALOG_URLderived from the apex origin, build-baked per environment (prod ->catalog.agentage.io/mcp, dev ->catalog.dev.agentage.io/mcp).@agentage/sharedhas nocatalogorigin yet, so it's derived locally rather than adding a cross-repo dependency.Verified
npm run verifygreen: build:libs, type-check, lint, prettier, 16 tests, build.Note
The catalog's own header mirrors this nav (Home/Docs/Blog/Dashboard/GitHub). To keep both perfectly in sync, the catalog header should get the matching Catalog item (active on the catalog) - a small follow-up in the mcp-catalog repo.