Public Wiki Editorial QA Pipeline

A public wiki should compound trust. The goal is not to publish the most pages; it is to publish useful pages that are safe, searchable, and visually clean on the live site.

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

Content gates

• Pick topics that answer real operator questions instead of filling a quota.
• Use public-safe examples and official documentation links where feature behavior matters.
• Every article needs a title, unique slug, category, summary, tags, published status, and a polished body.
• Add checklists, pitfalls, and verification steps so the page is actionable.
• Reject generated images that show secrets, private paths, unwanted logos, or messy text.

QA gates

• Validate JSON before rendering.
• Check duplicate slugs and category counts.
• Run local search queries that should find the new material.
• Capture desktop and mobile screenshots for changed layouts or image-bearing pages.
• Verify the live mapped domain and sitemap after deployment.

Pitfalls

• Publishing filler pages that dilute the wiki.
• Copying private notes into a public article.
• Relying on a successful deploy command instead of live route checks.
• Leaving stale CSS or search data after adding new page classes.

Verification steps

• Open /wiki and at least two new article routes locally.
• Search for a multi-topic query and confirm relevant results appear.
• Check the sitemap for the new URLs.
• Review screenshots for clipped headings, awkward crops, and duplicate hero images.