Public-Safe Knowledge Base Article Checklist

A public Rocky article should help a reader do safer, clearer work without exposing private context or promising features the system cannot support. Use this checklist before publishing a new wiki page.

Required metadata

• Unique slug.
• Clear title.
• Category and category slug.
• Summary between roughly one and two sentences.
• Tags that help search.
• Status that tells the reader whether it is a guide, checklist, pattern, or reference.

Body structure

• Start with a plain-English purpose.
• Include at least two meaningful sections.
• Add a checklist or sequence that a reader can follow.
• Add pitfalls so the page prevents common failures.
• End with verification steps.

Grounding rules

• Link to official Hermes documentation for Hermes-specific commands and features: https://hermes-agent.nousresearch.com/docs
• Avoid invented product guarantees.
• Keep examples generic and public-safe.
• Do not include real usernames, local private paths, tokens, customer details, or internal-only operational notes.

Visual and search QA

• Check that the title does not wrap awkwardly on mobile.
• Avoid duplicate hero images on adjacent pages.
• Search the wiki for likely reader queries and confirm this page appears when relevant.
• Verify sitemap coverage for indexable pages.

Verification steps

• Parse the content data as JSON.
• Check for duplicate slugs.
• Render the route locally.
• Capture desktop and mobile screenshots.
• After deployment, verify the live article URL and sitemap entry.