Documentation guidebook

Understand how the Velocity docs are organised and pick the right guide for your role.

Last updated October 8, 2025View on GitHub

Choose your next read

Velocity has a compact library—use this page as your compass. Each guide is tailored to a specific moment in the adoption journey and calls out exactly who should keep reading.

Audience map

RoleStart withWhy it matters
Platform & SRE teamsOperator handbookDaily workflows, runbook snippets, and ready-to-ship checklists.
Infrastructure ownersDeployment playbookArchitecture patterns, automation hooks, and recovery drills.
Integrators & API teamsIntegration guideHow to weave Velocity alongside HTTP/3, gRPC, and service meshes.
Security reviewersSecurity overviewCryptographic posture, incident flow, and compliance notes.
Performance enthusiastsBenchmarking guideRepeatable measurements plus tips for sharing results.

How the docs are structured

  • Get started: quick wins to bootstrap a pilot and understand terminology.
  • Operate: everything you need once real traffic hits—deployment, integration, upgrades, KPIs.
  • Security: posture, hardening, and specialised playbooks like the SSH migration path.
  • Build: guidance for contributors working on Velocity itself.

Every page follows the same rhythm—context first, a concise action plan, then deep dives when you are ready. Key commands are copy-ready, tables summarise decisions, and “Next steps” links keep you moving.

Suggested reading arcs

  1. New adopter: Getting startedOperator handbookDeployment playbook.
  2. Integrator: Integration guideBenchmarking guide → Velocity release notes (coming soon).
  3. Security review: Security overviewExploit hardening checklistVelocity SSH migration.

Stay in the loop

  • Watch the docs label on GitHub for new content drops.
  • Attend monthly office hours—agendas and recordings land in the #velocity-ops Slack channel within 24 hours.
  • File documentation requests straight from any page; maintainers triage them weekly.