Documentation surface

Write, organize, and publish technical truth in one platform.

Docs turns scattered knowledge into clear navigable reference pages. It supports product onboarding, API usage, architecture communication, and durable public explanation.

Published pages

1,284

Guides, references, and explainers

API sections

214

Contracts and endpoint references

Open drafts

Writing lanes in progress

Editorial pulse

Publishing snapshot

Keep the most important docs accurate, linked, and easy to discover from products and support surfaces.

Section update pendingOne product reference page needs a final fact pass before publish.

REVIEW

API examples refreshedRecent docs now match the current integration and auth flows.

LIVE

Cross-links improvedRoadBook and RoadSide now point cleanly into core documentation paths.

GOOD

Docs

Editor

Reference

Examples

Publish

Reader path

Docs should orient fast

The best documentation surfaces answer what this is, why it matters, and where to go next before they ask readers to absorb deep detail.

ENTRYCLEAR

System truth

Canonical pages need obvious weight

Operating-model, registry, and product-reference pages feel stronger when their authority is visually distinct from drafts and supporting guides.

CANONICALPINNED

Publish flow

Drafts become support content

Docs reads better as part of a pipeline too: write, review, publish, and route the best explanations into support and public discovery surfaces.

EDITORIALCONNECTED

Open document

BLACKROAD_OPERATING_MODEL.md

Section 301 — Product Services

The documentation platform makes canonical product descriptions readable, linkable, and easy to maintain. Readers should understand both individual product roles and the system-level relationships between them.

Docs acts as the publishing and editing layer that complements RoadBook reading flows, BlackBoard knowledge synthesis, and RoadSide public support needs.

Doc cards

Quickstart guides

Short paths for new users, contributors, and operators trying to get oriented fast.

ENTRY

Architecture references

Diagrams, registries, and system maps that explain how the stack hangs together.

CORE

API examples

Request and response patterns for product, memory, and platform integrations.

DEV

Publishing flows

Review, approval, and promotion paths for turning drafts into stable reference docs.

EDITORIAL