From fd6a6fbf2eba1bee716a4b81f886a0a8cf40ea44 Mon Sep 17 00:00:00 2001 From: teknium1 <127238744+teknium1@users.noreply.github.com> Date: Thu, 1 Oct 2026 17:39:34 -0700 Subject: [PATCH] docs: relative links in the catalog submission pages (docs-site link check) --- .../docs/developer-guide/plugins/catalog-submission.md | 8 ++++---- website/docs/user-guide/features/plugin-catalog.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/docs/developer-guide/plugins/catalog-submission.md b/website/docs/developer-guide/plugins/catalog-submission.md index f31f026ad3..05943bf1dd 100644 --- a/website/docs/developer-guide/plugins/catalog-submission.md +++ b/website/docs/developer-guide/plugins/catalog-submission.md @@ -6,7 +6,7 @@ description: "The full admission guidelines for the Hermes plugin catalog: what # Submitting to the Plugin Catalog -The [plugin catalog](/user-guide/features/plugin-catalog) is a human-reviewed +The [plugin catalog](../../user-guide/features/plugin-catalog.md) is a human-reviewed directory of Hermes plugins. Being listed is the trust signal: users install a catalog plugin by name, at the exact commit a maintainer read. This page holds the complete guidelines for getting a plugin in and keeping it there. @@ -25,10 +25,10 @@ for word, and a test fails the build if the two drift apart. `desktop/plugin.js` (Desktop), `plugin.json` (portable Agent Plugin) or `dashboard/manifest.json` (web dashboard). If the plugin lives in a monorepo, point `subdir` at its directory. The - [plugin developer guide](/developer-guide/plugins) covers the layout. + [plugin developer guide](./index.md) covers the layout. - **Public surfaces only.** Extend Hermes through hooks, middleware, the `ctx.register_*` APIs, provider plugins and the - [Desktop plugin SDK](/developer-guide/desktop-plugin-sdk). Never patch Hermes + [Desktop plugin SDK](../desktop-plugin-sdk.md). Never patch Hermes code or Desktop markup at runtime. If the hook you need is missing, see [Asking for a hook](#asking-for-a-hook). - **Validation passes locally.** Run the same check catalog CI runs, against a @@ -51,7 +51,7 @@ for word, and a test fails the build if the two drift apart. [`NousResearch/hermes-agent`](https://github.com/NousResearch/hermes-agent). The fields are documented in the README's [entry schema](https://github.com/NousResearch/hermes-agent/blob/main/plugin-catalog/README.md#entry-schema) - and in [What's in an entry](/user-guide/features/plugin-catalog#whats-in-an-entry). + and in [What's in an entry](../../user-guide/features/plugin-catalog.md#whats-in-an-entry). Pin `sha` to a full 40-character commit, and quote `version`. 2. In the PR description, say what the plugin does, which Hermes surfaces it uses, and everything rule 13 asks you to disclose. Add screenshots for diff --git a/website/docs/user-guide/features/plugin-catalog.md b/website/docs/user-guide/features/plugin-catalog.md index 595b84dff5..04fc8a853b 100644 --- a/website/docs/user-guide/features/plugin-catalog.md +++ b/website/docs/user-guide/features/plugin-catalog.md @@ -274,7 +274,7 @@ catalog for discovery. Submissions are pull requests that add one `plugin-catalog/.yaml` file. The complete guidelines live in -**[Submitting to the plugin catalog](/developer-guide/plugins/catalog-submission)**: +**[Submitting to the plugin catalog](../../developer-guide/plugins/catalog-submission.md)**: what to check before you submit, how the PR and review work, every admission rule, and how pin updates, delisting and removal work. That page mirrors the canonical rules in the