Skip to content

docs: split the user guide into per-topic pages under docs/ - #415

Draft
shimib wants to merge 1 commit into
mainfrom
docs-split
Draft

docs: split the user guide into per-topic pages under docs/#415
shimib wants to merge 1 commit into
mainfrom
docs-split

Conversation

@shimib

@shimib shimib commented Aug 27, 2026

Copy link
Copy Markdown
Member

What does this PR do?

Draft — for structure review. Splits the (restructured) user guide into one page per topic under docs/ and shrinks the README to a hub: overview, concepts, deployment quickstart, and a documentation map.

Content is moved verbatim — headings re-leveled, intra-document anchors rewritten to cross-file links. The only prose edit is the one line that described the old single-file layout. Review is best done page-by-page rather than via the diff (the diff is dominated by the moves):

Page Contents
README overview, concepts, deployment, docs map (~190 lines, was 1055)
docs/transports.md transport config, queue/topic entry fields, backend compatibility, per-implementation reference
docs/gates.md dispatch gate reference
docs/worker-pools.md pool config + merge policy reference
docs/requests-and-results.md message formats, wire envelope, body transforms
docs/observability.md Prometheus + PromQL cookbook, OTel tracing
docs/reference/cli.md flag reference

docs/guides/ is untouched and remains the home for task-oriented guides.

Notes for review

  • All cross-file anchors were mechanically verified to resolve (headings → GitHub anchor rules).
  • Inbound links from elsewhere in the repo (docs/dispatch-budget.mdREADME.md#dispatch-gates) still resolve: the concepts sections keep their anchors in the README.
  • External deep links into the reference sections of the old README will break when this lands; if we want, a follow-up can add a short "moved" map or we keep anchor stubs for the top-linked sections.
  • Follow-up candidates (not in this PR): a markdown link checker in CI; folding the README Deployment section into a guide.

Rebased onto main after the restructure (#411) merged.

@shimib shimib mentioned this pull request Aug 27, 2026
@shimib
shimib changed the base branch from readme-restructure to main August 27, 2026 20:51
The README had grown past 1000 lines and serves four different readers at
once (evaluator, operator, developer, SRE). Split it into one page per
topic and shrink the README to a hub: overview, concepts, deployment
quickstart, and a documentation map.

Content is moved verbatim (headings re-leveled, intra-document anchors
rewritten to cross-file links); no prose changes beyond the one line that
described the old single-file layout.

New pages:
- docs/transports.md          transport config, queue/topic entry fields,
                              backend compatibility, per-implementation reference
- docs/gates.md               dispatch gate reference
- docs/worker-pools.md        pool config + merge policy reference
- docs/requests-and-results.md message formats, wire envelope, body transforms
- docs/observability.md       Prometheus + PromQL cookbook, OTel tracing
- docs/reference/cli.md       command line parameters

All cross-file anchors verified to resolve; existing inbound links to the
README anchors that remain (concepts, deployment, development) are
unaffected.

Signed-off-by: Shimi Bandiel <shimib@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant