Update sidebar and add references to JSON schema

Signed-off-by: Dan Barr <[email protected]>

Author: danbarr

docs/toolhive/guides-cli/registry.md

@@ -132,6 +132,15 @@ By default, ToolHive uses a built-in registry of verified MCP servers. You can
 configure ToolHive to use a custom registry instead. This is useful for
 organizations that want to maintain their own private registry of MCP servers.
 
+The registry is a JSON file that follows the
+[ToolHive registry schema](../reference/registry-schema.mdx). Once you configure
+a custom registry, ToolHive uses it for all commands that interact with the
+registry, such as `thv registry list`, `thv registry info`, and `thv run`.
+
+Refer to the
+[built-in registry file](https://github.com/stacklok/toolhive/blob/main/pkg/registry/data/registry.json)
+for examples of MCP server entries.
+
 ### Set a remote registry URL
 
 To configure ToolHive to use a remote registry, set the registry URL:
@@ -154,14 +163,6 @@ To configure ToolHive to use a local registry, set the registry file:
 thv config set-registry <PATH>
 ```
 
-The registry must be a JSON file that follows the same format as the
-[built-in registry](https://github.com/stacklok/toolhive/blob/main/pkg/registry/data/registry.json).
-Once you configure a remote registry, all registry commands
-([`thv registry list`](../reference/cli/thv_registry_list.md),
-[`thv registry info`](../reference/cli/thv_registry_info.md),
-[`thv search`](../reference/cli/thv_search.md)) will use the remote registry
-instead of the built-in one.
-
 ### Check the current registry location
 
 To see which registry (URL or path) is currently configured:
@@ -189,6 +190,8 @@ This restores the default behavior of using ToolHive's built-in registry.
 See [Run MCP servers](./run-mcp-servers.mdx) to run an MCP server from the
 registry.
 
+Learn how to [create a custom MCP registry](../tutorials/custom-registry.mdx).
+
 ## Related information
 
 - [`thv registry` command reference](../reference/cli/thv_registry.md)

docs/toolhive/reference/registry-schema.mdx

@@ -1,6 +1,7 @@
 ---
 title: ToolHive registry JSON schema
 description: The JSON schema for the ToolHive registry.
+displayed_sidebar: toolhiveSidebar
 ---
 
 import JSONSchemaViewer from '@theme/JSONSchemaViewer';
@@ -11,7 +12,7 @@ constraints for the registry entries, ensuring that all entries conform to a
 consistent format.
 
 To use this schema in your own custom registry file, add a `$schema` property at
-the top of your JSON file, like this:
+the top of your JSON file:
 
 ```json
 {

docs/toolhive/tutorials/custom-registry.mdx

@@ -3,8 +3,6 @@ title: Create a custom MCP registry
 description: Learn how to create a custom MCP registry for ToolHive.
 ---
 
-import JSONSchemaViewer from '@theme/JSONSchemaViewer';
-import Schema from '@site/static/api-specs/toolhive-registry-schema.json';
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
@@ -270,8 +268,8 @@ container registries and private servers hosted within your organization.
 
 ## Next steps
 
-- Explore the full [schema reference](#schema-reference) below to understand all
-  available configuration options
+- Explore the full [schema reference](../reference/registry-schema.mdx) to
+  understand all available configuration options
 - Learn about [custom permissions](../guides-cli/custom-permissions.mdx) for
   fine-grained security control
 - Set up [secrets management](../guides-cli/secrets-management.mdx) for servers
@@ -318,21 +316,3 @@ After reverting, all registry commands
 [`thv registry info`](../reference/cli/thv_registry_info.md),
 [`thv search`](../reference/cli/thv_search.md)) will use ToolHive's built-in
 registry instead of your custom one.
-
-## Schema reference
-
-This is the JSON schema for the ToolHive registry. It defines the structure and
-constraints for the registry entries, ensuring that all entries conform to a
-consistent format.
-
-To use this schema in your own custom registry file, add a `$schema` property at
-the top of your JSON file, like this:
-
-```json
-{
-  "$schema": "https://raw.githubusercontent.com/stacklok/toolhive/main/pkg/registry/data/schema.json",
-  ...
-}
-```
-
-<JSONSchemaViewer schema={Schema} />

sidebars.ts

@@ -19,13 +19,13 @@ const sidebars: SidebarsConfig = {
 
     {
       type: 'category',
-      label: 'Quickstarts',
+      label: 'Get started',
       description: 'Step-by-step guides to get started with ToolHive',
       link: {
         type: 'generated-index',
         slug: 'toolhive/quickstart',
         description:
-          'Learn how to use ToolHive with these step-by-step tutorials',
+          'Learn how to use ToolHive with these step-by-step tutorials.',
       },
       collapsed: false,
       items: [
@@ -129,7 +129,7 @@ const sidebars: SidebarsConfig = {
         type: 'generated-index',
         slug: 'toolhive/concepts',
         description:
-          'Learn about the key concepts behind ToolHive and the Model Context Protocol (MCP)',
+          'Learn about the key concepts behind ToolHive and the Model Context Protocol (MCP).',
       },
       items: [
         'toolhive/concepts/mcp-primer',
@@ -146,10 +146,17 @@ const sidebars: SidebarsConfig = {
         type: 'generated-index',
         slug: 'toolhive/tutorials',
         description:
-          'Learn how to use ToolHive with these step-by-step tutorials',
+          'Learn how to use ToolHive with these step-by-step tutorials.',
       },
       collapsed: false,
-      items: ['toolhive/tutorials/custom-registry'],
+      items: [
+        {
+          type: 'link',
+          href: '/toolhive/quickstart',
+          label: 'Quickstart guides',
+        },
+        'toolhive/tutorials/custom-registry',
+      ],
     },
 
     'toolhive/faq',