Skip to content

Docs Workflow

Use this workflow when adding or updating documentation.

English docs are the source of truth until another locale is intentionally added. Write pages in src/content/docs/.

Use this structure for walkthroughs:

  1. Goal
  2. Before you start
  3. Steps
  4. Verify it worked
  5. Troubleshooting
  6. Related guides
  • Inspect the product behavior before writing procedural docs.
  • Keep docs customer-facing and avoid implementation details.
  • Do not import from the WebinarStack application repo.
  • Do not reference secrets, private IDs, or internal-only runbooks.
  • Prefer screenshots or short videos when a workflow has important visual state.
  • The guide matches the current product UI.
  • Links resolve.
  • Images have useful alt text.
  • Videos have descriptive titles.
  • The page builds with pnpm build.