Index / 6 projects
Each of these started as a pile of documents somebody could no longer maintain. What shipped was a system — a source of truth, a build, and a set of rules that hold without me in the room.
A documentation system that treats an OpenAPI spec as the single source of truth, then sculpts client-specific reference sites out of it without ever forking the master file.
Outcome
One spec, many audiences — no divergent copies to reconcile.
A navigable map of a large, multi-file OpenAPI surface — paths, schemas, components and their dependencies — so writers can see what a change actually touches before making it.
Outcome
Impact of a schema edit visible in seconds instead of guesswork.
Non-destructive decorators that generate customised OpenAPI views per client at bundle time, leaving the master specification untouched.
Outcome
Client-specific docs with zero manual spec surgery.
Style and terminology enforcement wired directly into the editor through VS Code tasks, so the linter runs against the file you are writing rather than in a separate tool.
Outcome
Style feedback at authoring time, not review time.
A full CI pipeline for product documentation — linting, link checking, build and deploy — giving docs the same release discipline as the code they describe.
Outcome
Broken links and style drift caught before merge.
A three-column, example-forward API reference built on open-source Docusaurus and Redoc — the Stripe reading experience without the Stripe budget.
Outcome
Reference docs developers actually finish reading.
Note
Client-confidential work is not listed here. If you need to see something closer to your own stack, ask me directly and I will walk you through what I can share.
Ask me →