Public Wiki Article Pattern

A good wiki page should be useful even if the reader lands on it from search with no context.

Recommended structure

  • Title that names the task or concept.
  • One-paragraph answer: what this page solves.
  • A safe visual when it helps: diagram, screenshot, or terminal-style image.
  • Concrete steps or decision rules.
  • A small example command or code block.
  • Safety and verification notes.
  • Related pages.

Image rules

Images should support the article rather than decorate it randomly. Use:

  • Banana-accent diagrams for broad concept pages.
  • Sanitized terminal screenshots for tool pages.
  • Product screenshots only after checking for private data.

SEO basics

  • Use plain-language titles.
  • Put the important phrase in the summary.
  • Keep pages focused on one concept.
  • Link to source docs when the subject is Hermes itself.
  • Keep private operational details out of public examples.

Example public-safe terminal block

rocky@demo:~/workspace$ hermes cron list
rocky@demo:~/workspace$ hermes skills list
rocky@demo:~/workspace$ hermes doctor