Contributing to the handbook¶

Anyone in the team can add to or fix this handbook. Changes go live about a minute after they're saved, and every change is recorded, so nothing is ever lost.

With an AI tool¶

Claude, GitHub Copilot and Codex (GPT) can all edit the handbook. Make sure your tool is connected to your own GitHub account, then ask it in plain language, for example:

Add a page to the RHQ Handbook under Calendar explaining how to create a booking. Here's how it works: …

The tool reads the repo's shared instructions (AGENTS.md), so it knows where pages go and the house style.

By hand on GitHub¶

1. Go to the repository and open the docs/ folder for the section you want.
2. Open a page and click the pencil icon, or Add file → Create new file for a new page.
3. Click Commit changes, write a short message saying what you changed, and choose Commit directly to the main branch.
4. For a new page, also edit zensical.toml and add the page under the right tab in nav.
5. Check the site about a minute later.

Seeing what's changed¶

• Recent changes lists every change: who made it, when, and which pages.
• The bottom of each page shows when it was last updated and by whom. Its History link lists every change to that page on GitHub.

Undoing a change¶

• Ask your AI tool, e.g. "Undo the last change to the Inventory page". It reverses the change and republishes.
• In an emergency, an admin can roll the whole site back to any earlier version from the Cloudflare Pages dashboard. The change should still be undone in the handbook afterwards, or it will come back with the next edit.

Rules for every change¶

• One topic per change, with a clear description: it's shown on Recent changes.
• Never include passwords, keys or client personal data. Those belong in the password manager or in RHQ itself.
• Use the section that matches where the feature lives in RHQ. If nothing fits, use Other.

Last updated 28 October 2026 by Tom Cousins · History