Follow-up to the light-mode contrast fix; no visual change on the catalog. - Edit the existing light .heroEyebrow rule in place instead of shadowing it from the appended block (it was left dead at the old #a8860a). - One rule per component: .starPill, .capChip, .envChip, .copyBtn, .highlight, .versionPill/.platformPill and .categoryChip each had colour in one block and border/background in another; .categoryBtnActive set its colour twice; .docsLink:hover/.emptyCtaSecondary:hover got a colour that the later hover rule always overrode. - The amber was hardcoded ~20 times although it is the theme's own --ifm-color-primary-darker (the search icon's is --ifm-color-primary); use the variables, including for --plugin-catalog-official. - Share the light link blue between the list and detail pages via --plugin-catalog-link so the two can't drift. - Plugin detail/author pages used #8a6d00 for light star counts while the list now uses the darker amber; align them on the same variable. Verified: computed colour/background/border/shadow of every element on the catalog, a plugin page, an official plugin page, an author page and the empty state, in both themes plus hover on 19 controls, is identical to the contributor's head except the intended star colour on detail/author pages.
Website
This website is built using Docusaurus, a modern static website generator.
Reading the docs on GitHub? The Markdown under
docs/is authored for the rendered site at https://hermes-agent.nousresearch.com/docs/. Cross-page links are relative Markdown paths, so they follow through on GitHub's file viewer too. Every page on the site has an Edit this page link that opens the source file here.
Authoring links in docs/
- Link to another page with a relative Markdown path, anchors included:
[Profiles](../user-guide/profiles.md),[Bundles](../user-guide/features/skills.md#skill-bundles). Docusaurus turns the file path into the page route; GitHub follows the same path. Site routes (/user-guide/profiles,/docs/user-guide/profiles) only work on the rendered site — GitHub resolves them as repository paths and 404s, and the/docs/form also emits/docs/zh-Hans/docs/...404s in the zh-Hans build becausebaseUrlis already/docs/. python3 website/scripts/check_doc_links.pyfails on any route-style link in hand-authored pages (EN and the zh-Hans mirror);--fixrewrites them. It runs in theDocs Site Checksworkflow. Generated pages (user-guide/skills/{bundled,optional},reference/*skills-catalog.md) are produced byscripts/generate-skill-docs.py, which emits the same relative form.- Pin
{#anchor}on cross-linked headings so the zh-Hans mirror keeps the same id.
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.