Skip to main content
These standards keep iHub useful as it grows.

Write for the reader

  • Start with the outcome or purpose.
  • Prefer short sentences, plain language, and concrete steps.
  • Expand acronyms on first use.
  • Use headings that help someone scan the page.
  • Link to the source of truth instead of maintaining duplicate copies.

Make ownership visible

Add this block to process, policy, system, and reference pages:
Choose a review interval based on risk: monthly for fast-changing operational material, quarterly for active processes, and annually for stable reference material.

Separate durable knowledge from conversation

iHub should capture conclusions and repeatable knowledge. Chat messages, tickets, and meeting recordings can provide context, but a maintained page should contain the durable answer.

Use predictable page names

  • Use sentence case for titles.
  • Name procedures with an action, such as “Approve an instructor payout.”
  • Name reference pages with the subject, such as “Course lifecycle.”
  • Avoid dates in filenames unless the document is inherently date-specific.

Handle stale content

If a page is questionable, mark it clearly and notify its owner. Correct, archive, or replace it rather than silently duplicating it. Preserve useful decision history in a decision record.

Protect information

Follow Information safety. Internal visibility does not make iHub appropriate for secrets or unrestricted personal data.