Clarify ToolHive onboarding and navigation#800
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
Improves the ToolHive docs “first hop” experience by making /toolhive the clearer entry point, clarifying how ToolHive components relate (UI/CLI/Operator, vMCP, Registry Server, built-in registry), and adjusting navigation behavior/presentation to better match the new framing.
Changes:
- Adds sidebar section headers and reorganizes the ToolHive sidebar to better reflect “run” vs “platform services” vs “shared guides” vs “reference/help”.
- Updates
/toolhivelanding content and multiple guide intros/quickstarts to clarify platform components and onboarding flows. - Changes docs sidebar behavior to auto-collapse categories; removes the navbar “Integrations” entry.
Reviewed changes
Copilot reviewed 16 out of 16 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/css/custom.css | Adds styling for new non-clickable sidebar section headers. |
| sidebars.ts | Inserts HTML-based section headers and refactors the reference/help grouping in the ToolHive sidebar. |
| docusaurus.config.ts | Enables auto-collapsing doc categories; removes “Integrations” from the navbar dropdown. |
| docs/toolhive/index.mdx | Adds a platform overview section and simplifies source/contribution links. |
| docs/toolhive/guides-vmcp/quickstart.mdx | Clarifies prerequisites and next steps; adds related info and UI tip. |
| docs/toolhive/guides-vmcp/index.mdx | Reframes vMCP intro in platform terms and adds local-eval guidance. |
| docs/toolhive/guides-ui/registry.mdx | Renames the page title to “Use the registry”. |
| docs/toolhive/guides-ui/quickstart.mdx | Clarifies “built-in registry” wording; adds related info section. |
| docs/toolhive/guides-ui/index.mdx | Reframes UI as the fastest local start and positions it within the platform. |
| docs/toolhive/guides-registry/intro.mdx | Expands intro to explain “why” and clarifies Registry Server vs built-in registry. |
| docs/toolhive/guides-registry/index.mdx | Reframes Registry Server overview and clarifies when you do/don’t need it. |
| docs/toolhive/guides-k8s/quickstart.mdx | Renames “What’s next?” to “Next steps” and adds related info links. |
| docs/toolhive/guides-k8s/index.mdx | Reframes operator intro in platform terms (team/production-style deployments). |
| docs/toolhive/guides-cli/registry.mdx | Renames the page title to “Use the registry”. |
| docs/toolhive/guides-cli/quickstart.mdx | Makes client setup explicitly optional and reorders steps; adds related info. |
| docs/toolhive/guides-cli/index.mdx | Reframes CLI positioning and adds a pointer to browsing the built-in registry. |
Comments suppressed due to low confidence (1)
docs/toolhive/guides-cli/quickstart.mdx:242
- Step 5 is explicitly optional, but Step 6 is written as the next required step and assumes the client is already configured via
thv client setup. Consider making Step 6 optional as well (or gating it with “If you completed Step 5…”) and/or adding a short pointer to manual client configuration for readers who skip Step 5.
## Step 6: Use the MCP server with your AI client
Now that your MCP server is running, you can use it with your AI client
application. Open your supported client (VS Code, Cursor, etc.) and ask the AI
to fetch content from a website. Note that you might need to restart your client
for the changes to take effect.
danbarr
force-pushed
the
toolhive-onboarding-cleanup-main
branch
from
cebbb8a to
70dabce
Compare
rdimitrov
approved these changes
Apr 23, 2026
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.
Description
This PR improves the first-hop ToolHive docs experience, mainly around
/toolhiveas the primary entry point for new readers.The main goal is to make ToolHive read more clearly as a platform, not just a collection of components. The changes clarify how the UI, CLI, Kubernetes Operator, vMCP, Registry Server, and the built-in registry fit together, while keeping the existing product-area information architecture intact.
This PR also simplifies a few navigation and onboarding rough edges:
/toolhive, including redundant visuals and the inline repo laundry listA few specific areas to review:
/toolhiveType of change
Related issues/PRs
Screenshots
Submitter checklist
Content and formatting
Navigation
sidebars.ts) updated for added, deleted, reordered, or renamed filesvercel.jsonfor moved, renamed, or deleted pages (i.e., if the URL slug changed)Reviewer checklist
Content