Teknium
61afcde8f9
Plugins were split across two pages that each showed half the picture: Settings → Plugins listed desktop plugins plus "Install from Git" and a pointer saying agent plugins live elsewhere; Capabilities → Plugins listed agent plugins plus the catalog picker but knew nothing about desktop plugins. A user asking "what extends my Hermes and where do I add more?" had to visit both and still could not see the whole set in one place. Capabilities → Plugins is now THE plugins page: - Agent plugins section (scoped to the profile selector) with the "Install from Git" button in its header — installs target the scoped profile, not whichever one is active. - Desktop plugins section beneath it (same for every profile), with the folder/rescan controls and the "agent half missing here" drift chip, whose repair also lands in the SCOPED profile. - The catalog picker underneath, unchanged. Settings → Plugins is removed. `/settings?tab=plugins[&plugin=…]` and the existing `?tab=mcp` redirect share one table (`settings/moved-tabs.ts`) so old bookmarks and palette links land on the same row on the new page. Command palette: plugins moved from the Settings group to the Capabilities group; installed-plugin rows deep-link to `/skills?tab=plugins&plugin=…`. Dead `settings.plugins.agent.*` and `settings.nav.plugins` i18n keys dropped; docs and in-code pointers say Capabilities → Plugins.
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.