8b89b68fb4
Brings the onboarding branch up to main0c2ff854a5. Where a Wave A PR already landed a reviewed version of a piece of this branch (free tier #134049, keyless web #134048, app resolver #134050, bundle and uninstall #134051, catalog card and toolsets #134052, built-in tour #134054, stdin guard #134055, retired key #126146), main's version wins. The PM long-path files also take main's version: that work lands through #130430. Kept from the branch on top of main: - the setup and start_chat toolsets, declared with main's platforms key (desktop only), and the setup_choose server request contract; - the setup-profile marker file (.setup-profile.json) instead of the profile.yaml role, asc3f85bc54fdecided; - the first-contact note's message argument beside main's internal flag; - the setup-profile gate on the shared-metrics consent dialog; - window sizing (window-growth) in place of chat-onboarding-window. Desktop i18n follows main's per-section sibling files. The onboarding strings go into them (modelMenu.localSetup, handoffTour.localTitle and localText) and setupChoose/startChat stay in en.ts. guidedGreeting is gone. The shared-metrics copy uses the branch's rewrite in English, with the pre-opt-in sentence corrected for the fresh-install note (d3674513c8); locales keep main's translations, with installId and consentWindow folded into the new sending key. The built-in tour reads local-model eligibility from the local-setup offer store, the one place that rule lives on this branch. The gateway contract and the onboarding skill docs pages are regenerated.
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.