feat: give the Registry a dedicated page, top-level nav, and footer link - #46
Merged
Conversation
Previously the registry was only a single dropdown item and one paragraph on /agents.html — every other pillar (Platforms, System, Compare) gets a top-level nav item, a footer link, and its own page. /registry.html covers what's actually in it (11 capabilities, 38 published versions across 5 namespaces — counted directly from contract.json files, not estimated), how the live static catalog at registry.traverse-framework.com actually works (list/search/inspect/ verify, backed by a Rust/WASM catalog-builder step), and the real git-based PR-review publishing flow from CONTRIBUTING.md. Nav: promoted to a top-level item next to Platforms/Agents, removed from the Developers dropdown to avoid duplication. agents.html's mention now points to the internal page instead of jumping straight to the external catalog. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
Follow-up to #44 — the registry was only in a dropdown item + one paragraph on
/agents.html. Every other pillar (Platforms, System, Compare) gets full treatment: a top-level nav item, a footer link, and its own page. This closes that gap./registry.html: what's actually in the registry (11 capabilities, 38 published versions across 5 namespaces — counted directly fromcontract.jsonfiles intraverse-framework/registry, not estimated), how the live catalog at registry.traverse-framework.com actually works (list/search/inspect/verify, backed by a Rust/WASMcatalog-builderstep), and the real git-based PR-review publishing flow (fromCONTRIBUTING.md)./agents.html's mention now links to the internal page instead of jumping straight to the external catalog.Test plan
npm run build— 87 pages (up from 86), no errors/registry.html; footer has it; dropdown no longer duplicates it;CONTRIBUTING.mdlink resolves to a real file (confirmed viagh api)display: gridwith all 5 namespace cards