The Samples

Six complete pieces. Not excerpts.

Each of these is a finished system rather than a page pulled out of one: the reference and the ruleset that governs it, the release note and the migration guide it points to, the help article and the three others it is structurally bound to. Documentation is judged as a system, so it is shown as one.

Where the work I shipped is public it is linked directly, as with the Google Ads Help Center articles on the work page. The rest is client documentation under NDA, so what follows is built to the same standard on invented products.

• Spec-first API reference · billing

  Ledger API

  Twenty-seven governance rules run in CI, and a specification that breaks one of them does not merge.

  7 source files · OpenAPI 3.1.1

• Tutorial-first API docs · document extraction

  Sift API

  The quickstart returns a wrong answer in step 3, deliberately, before the reader has built anything on the right one.

  3 documents · Diátaxis

• Release notes · release history and migration

  Ledger API release notes

  A Latest releases index, a release history per package, and an archive topic for every version, with one breaking change and its migration guide.

  3 documents + 3 archive topics · Dated releases

• Help center suite · four linked articles

  Payments knowledge base

  One bad afternoon, answered four ways for four readers who each arrived at a different moment.

  4 documents · Diátaxis

• Technical manual · structured authoring

  Orchestrator installation and maintenance manual

  Eight writing rules stated in the front matter, and a manual that then obeys them.

  3 documents · ASD-STE100

• Docs-as-Code · automated editorial review

  Prose governance system

  Every rule names the defect it prevents. So does every rule that was rejected.

  3 documents · Vale