How-to guides

Hands-on guides for contributors: from a first local run to shipping an endpoint and updating docs. Use this page as the main entry for the recommended onboarding path and for the doc authoring checklist.

Overview

Use this index when you want steps for a task, not only policy text. For decisions, see ADRs. For detailed specs, see RFCs. For writing rules and audits, see Documentation style guide and audit standard.

Golden onboarding path (recommended sequence)

If you are new here, follow this order. It takes you from setup to a PR that is ready for review.

  1. Run full onboarding guide: Onboarding from zero to endpoint and docs.
  2. Use the concrete endpoint implementation example: Add POST /api/v1/contract (beginner walkthrough).
  3. Update internal service docs structure and navigation: Internal service docs layout and how to add pages.
  4. Validate writing style and structure against: Documentation style guide and audit standard.

Documentation authoring path (create and format docs)

Use this list when you change behavior and need to update the docs to match.

  1. Define document type and target location (internal API page, how-to, runbook, ADR, RFC).
  2. Create or update page content using the required section structure from document-type matrix.
  3. For internal service pages, keep navigation and shell consistent with internal docs layout guide.
  4. Update links on hub pages (this index, internal indexes, ADR/RFC/runbook lists) when a new page is part of the official flow.
  5. Run documentation build and normalization:
    make docs-fix
  6. Run checks and drift validation before push:
    make docs-check

Guides catalog

Guide When to use it
Onboarding: from zero to endpoint and docs First-time path from setup to quality gates.
Internal service docs layout and how to add pages Add or change pages under docs/internal/, sidebar, and layout.
Beginner walkthrough: add POST /api/v1/contract Example endpoint wired through all service layers.

Page history

Date Change Author
Added Page history section (repository baseline). Ivan Boyarkin