June 2026
"Content alchemy"
Raw information doesn't become documentation on its own. We're exploring what it takes for technical writers to transform the unrefined, the inconsistent, and the overwhelming into something a reader can actually use.
June 2026
Raw information doesn't become documentation on its own. We're exploring what it takes for technical writers to transform the unrefined, the inconsistent, and the overwhelming into something a reader can actually use.
In this issue
The authoritative doc, spec, or wiki page a writer is pointed to is often quietly out of date — and figuring out what to do when the source of truth has drifted from what's actually true.
Why starting from what a document needs to do (and not do) — rather than planning it perfectly from scratch — turns restrictions into a usable structure, with a DynamoDB docs example.
How to make an invisible, overloaded documentation queue visible to stakeholders, and build a system for managing what's realistically left after that.
A fable about a writer who applies schema markup indiscriminately to get cited by AI answer engines, without understanding the taxonomy underneath it.
Building AI-assisted documentation migration systems convinced him that automation doesn't shrink human judgment — it just moves where judgment is needed.