David/HERMES-GIELIE
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(extensions): link EXTENSIONS.md to the vetted extension library repo

Browse source 
EXTENSIONS.md documented the WebUI-side extension infrastructure (loader, manifest,
capabilities incl. settings_schema / skin scheme / TTS engine, install client) but
never linked to hermes-webui/hermes-webui-extensions — the public repo where the
vetted, one-click-installable gallery entries actually live and where new extensions
are contributed.

Adds two cross-links, no behavior change:
- intro callout: points to the library repo + its docs/extension-entry.md, framing
  this doc as the infrastructure side and the library repo as where entries live.
- a 'Contributing to the extension library' pointer at the end of the authoring
  guidance, describing the entry-PR + CI-safety-gate + registry-publish flow.

Docs-only.
This commit is contained in:
nesquena-hermes 2026-07-01 07:11:16 +00:00
parent 056cd4ad5d
commit 159ede9276
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
docs/EXTENSIONS.md
View file

@ -17,6 +17,15 @@ This is intentionally not a plugin marketplace or dependency system. It is a
safe escape hatch for local dashboards, internal tooling, and workflow-specific
panels that should not live in core Hermes WebUI.
> **The vetted extension library.** The curated, one-click-installable extensions
> that appear in the gallery live in a separate public repo:
> **[hermes-webui/hermes-webui-extensions](https://github.com/hermes-webui/hermes-webui-extensions)**.
> "In the registry == vetted." That repo holds the entries, the authoring
> conventions ([`docs/extension-entry.md`](https://github.com/hermes-webui/hermes-webui-extensions/blob/main/docs/extension-entry.md)),
> the JSON schema, and the CI safety gates. This document covers the WebUI-side
> *infrastructure* (loader, manifest contract, capabilities, install client);
> see the library repo to browse existing extensions or contribute a new one.
## What extensions can do
Extensions can:
@ -533,6 +542,16 @@ If host CSS overrides `[hidden]`, add an extension-scoped rule such as:
}
```
### Contributing to the extension library
To publish an extension in the vetted gallery, open a PR against
**[hermes-webui/hermes-webui-extensions](https://github.com/hermes-webui/hermes-webui-extensions)**
following [`docs/extension-entry.md`](https://github.com/hermes-webui/hermes-webui-extensions/blob/main/docs/extension-entry.md)
(entry layout, `extension.json`/`manifest.json` shape, and the capability +
best-practice conventions). Every entry PR runs the repo's CI validators and
safety scan before it can merge, and merged entries are published to the registry
that powers Settings → Extensions.
## Minimal example
Create a local extension directory: