Skip to main content

Documentation project instructions

About this project

  • Mintlify docs site for StandIn, the hosted Teams media bridge by Komaa (docs.komaa.com).
  • Covers the Teams Voice Plugin for OpenClaw and Hermes Agent: install, configure, register a BYO Teams bot, and troubleshoot.
  • Pages are MDX with YAML frontmatter; site config lives in docs.json. Deploys on push to main.

Page inventory

  • Groups: Getting Started, Teams setup, Concepts, OpenClaw plugin, Hermes plugin, ElevenLabs bridge, LiveKit bridge, OpenAI bridge, Deepgram bridge.
  • New pages must be added to navigation.pages in docs.json or they will not appear.
  • Internal links are root-relative without extension, e.g. /teams/azure-bot#8-grant-graph-permissions.
  • /teams-app (the old single-page Teams setup) redirects to /teams/azure-bot via redirects in docs.json; do not recreate the page.

Style rules

  • No em dashes (the U+2014 character) anywhere. This is client-facing content: use ”-” or rewrite the sentence.
  • Casing: StandIn (capital S, capital I), never “Standin” or “standin” in prose. Also: OpenClaw, Hermes Agent, ClawHub, Komaa.
  • Use active voice and second person (“you”); sentence case for headings.
  • Bold for UI elements (Click Settings); code formatting for files, commands, paths, keys.

Single sources of truth

  • The Microsoft Graph permissions table lives ONLY in teams/azure-bot.mdx#8-grant-graph-permissions. Other pages (concepts/architecture.mdx, openclaw/configuration.mdx, hermes/configuration.mdx) link to it; do not re-add copies.
  • The example Teams manifest and placeholders table live ONLY in teams/app-package.mdx.
  • Screenshots in images/teams/ are pre-redacted (placeholder GUIDs, generic labels, no tenant or account info). Never add raw portal screenshots; regenerate redacted ones instead.
  • The quickstart.mdx#verify-optional section documents downloading install.sh / install.ps1 and reviewing them before running. It intentionally carries no SHA-256 checksums - a pinned hash goes stale on every installer change and silently breaks the documented verify step, so it was removed. Do not re-add checksums here.

Content boundaries

  • Do not document internal infrastructure (AKS cluster, MediaNode internals, portal admin APIs).
  • Never publish real GUIDs, secrets, or tenant IDs in examples; use obvious placeholders.