Who owns the docs? Splitting docs work between engineers and technical writers
How GitLab, Kubernetes and Google split docs work between engineers and writers, where each split breaks, and the rules that make one hold.
Read the postBlog
Notes on docs that keep up.
How API docs fall behind code, how teams catch it, and what we learn building DocFit.
How to document webhooks: what every webhook reference needs
The events, payloads, delivery rules and signature details a webhook reference needs, with a tested verification sample and a CI check that catches undocumented events.
Read the post
Setting up llms.txt and Markdown docs for AI agents
What to publish so coding agents can read your docs, how to switch it on in Mintlify, GitBook, ReadMe, Docusaurus and MkDocs, and how to check the result the way an agent sees it.
Read the post
Code samples that don't rot: testing the examples in your API docs
Run every curl example in your docs against a mock server built from your OpenAPI spec, on every pull request, and fail the build when one breaks. A tested script and GitHub Actions workflow.
Read the post
Writing changelogs developers actually read
What a useful API changelog entry answers, what the best public changelogs do, a template you can copy, and how to keep the changelog and the docs saying the same thing.
Read the post
How to audit your API docs for drift in an afternoon
Eight steps, real commands and about four hours to find where your API docs and your API disagree, with the results from running it on a real repository.
Read the post
The breaking changes nobody documents
A field guide to the quiet API changes that pass code review and leave the docs wrong, where each one hides in your docs, and how to catch it before your users do.
Read the post
Docs-as-code CI: lint, link-check and build your docs on every pull request
A hands-on guide with working config for Vale, markdownlint, lychee and Spectral, wired into GitHub Actions, so every docs pull request is checked before anyone reviews it.
Read the post
Your API docs are now read by AI agents: what stale docs cost you in 2026
Coding agents now read more docs pages than people do, and they write code from whatever the page says. Here's how they read your docs, and why an out-of-date page costs more than it used to.
Read the post
The best tools for keeping docs in sync with code in 2026
Ten tools that promise to update your docs when code changes, compared on what starts an update, where your docs can live, what gets checked, and what it costs.
Read the post
Why API docs drift after every merge
A small API change can make the docs wrong in ways no code reviewer looks for. Here is where the drift comes from, and what keeping up actually takes.
Read the post