I built this blog to document the work behind the documentation.

Most writing about docs stays at the surface layer: style tips, templates, and tooling comparisons. That matters, but it skips the harder part of the job. Documentation teams do not just write pages. We build systems. We make information findable, structured, testable, reusable, and publishable across changing products and release cycles.

That is the lens for this site.

I write about documentation engineering, information architecture, API documentation, Docs-as-Code workflows, quality gates, and the operational problems that make documentation harder than it should be. Some posts will be build logs from things I am creating. Some will be field notes from enterprise documentation work. Some will be opinionated essays about what our tooling still gets wrong.

I am also using this space to connect writing with working artifacts. If I build a prototype, a doc workflow, a visual model, or a content system, I want the reasoning and the outcome to live together. The point is not just to publish posts. The point is to show the craft, the tradeoffs, and the infrastructure behind them.

If you work in documentation, developer experience, or product education, this blog is for you.