Skip to content

docs(site): tighten documentation prose and state each rule once - #408

Merged
vishr merged 1 commit into
mainfrom
docs/editorial
Oct 30, 2026
Merged

vishr merged 1 commit into
mainfrom
docs/editorial

Conversation

@vishr

@vishr vishr commented Oct 30, 2026

Copy link
Copy Markdown
Member

What changed

An editorial pass over fanout.run's documentation, from a site-wide review against Diátaxis and a writing-style checklist. URLs, slugs, page structure and code examples are unchanged.

  • Removes contrasts and closing lines that restated the sentence before them, provenance narration in generated reference pages, the contributor naming policy from the configuration pages, prose em dashes and curly quotes.
  • States the namespace access rule in full on Capabilities and links to it from Overview, Send telemetry, Architecture, Authentication and Roles. The MCP public-origin requirement lives in the MCP guide, linked from TLS.
  • Install keeps its steps; its lookup tables move intact to the configuration reference.
  • Generated text is changed at its source (cmd/fanout-docgen, internal/config) and regenerated.

Verification

  • just check
  • just test-race when auth, API, ingest, query, MCP, or agent paths changed (not applicable: documentation strings only)
  • User-facing behavior and configuration docs are current (just docs-generate-check)
  • No credentials, private telemetry, host details, or enterprise-only source are included
  • API, migration, ingest, MCP/AG-UI, or release-contract changes are called out (none)

Also: just site-build with all site checks, lychee over the built site (2,315 links and anchors, 0 errors), and a Codex review of the diff (no findings).

An editorial pass over the docs site removes contrasts and closing lines
that restated the sentence before them, provenance narration in the
generated reference pages, the contributor naming policy from the
configuration pages, prose em dashes and curly quotes. The namespace
access rule is stated in full on the capabilities page and linked from
the pages that repeated it, and the MCP public-origin requirement lives
in the MCP guide with a link from TLS.

The install page keeps its steps and moves its lookup tables to the
configuration reference. Generated text is changed at its source in
cmd/fanout-docgen and internal/config, and the pages are regenerated.
@vishr
vishr merged commit 906df1c into main Oct 30, 2026
17 checks passed
@vishr
vishr deleted the docs/editorial branch October 30, 2026 14:36
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