Source-to-Sitemap Publication Flow

A public knowledge-base page is more than a markdown body. It needs grounded source material, safe copy, search visibility, canonical metadata, and sitemap coverage.

Official Hermes Agent docs: https://hermes-agent.nousresearch.com/docs

Publication flow

1. Choose a public-safe topic with a real operator use case.
2. Ground commands and feature names in official docs or verified project source.
3. Write a complete article with headings, checklists, pitfalls, and verification steps.
4. Add metadata: slug, title, category, category slug, summary, tags, status, and body.
5. Recompute category counts from the article list.
6. Verify local rendering and search results.
7. Deploy only after visual and route checks pass.
8. Verify the live article URL and sitemap entry.

Canonical requirements

• Each article should resolve at one stable /wiki/<slug> URL.
• Canonical metadata should point to the article route, not the home page.
• The sitemap should include the new URL after deployment.
• Search result cards should use the same title and summary as the article metadata.

Public-safety checklist

• No real home-directory paths, tokens, customer names, orders, or private repo details.
• No copied private notes unless they have been rewritten as generic guidance.
• No generated hero image with readable fake labels or accidental logos.
• No unsupported promise that Rocky can do something without setup or verification.

Common pitfalls

• Adding a valid JSON entry that is not linked by the public renderer.
• Forgetting to bump or refresh search assets when the site uses static search data.
• Assuming the sitemap changed without fetching it live.
• Letting a broad query return no results because search requires every term to appear in one page.

Verification steps

• Fetch /wiki/<slug> locally and live.
• Search for a unique phrase from the article.
• Inspect page title, canonical link, and robots behavior.
• Fetch /sitemap.xml and confirm the exact article URL appears.