I love reading blogs about technical documentation, so much so that I created a collection and aggregated feed of them plus podcasts and newsletters. Here’s how I did it (and how you can contribute).
automation
blogging
announcements
docs-as-code
YAML
Jekyll
If the best way to maintain accurate documentation is to draw canonical data from the product source code, how does one get started moving from having duplicate or triplicate sources of truth to a truly single source?
docs-as-code
single-sourcing
automation
YAML
programming
Vibe coding has its place, but as of now I am not among the developers who think good software can be reliably produced when “nobody touches the code”.
AI
programming
From work-ticket creation to release notes, DocOps Lab has you covered with two new apps that assist the bulk posting of issues and later generate precisely formatted release histories from them.
projects
automation
YAML
GitHub
announcements
LLMs still produce frustrating slop unless they are reined in by techniques that revolve around good documentation. Here’s how to train your agents to be good to your code and docs.
AI
single-sourcing
AsciiDoc
writing
Today I release a major update to the DocOps Lab website, reporting for the first time on all the projects underway or planned, including their statuses.
projects
announcements
Jekyll
YAML
AI
single-sourcing
AsciiDoc
Markdown
Sourcing complex profile metadata from YAML and rendering it with Liquid templates.
Jekyll
YAML
Liquid
single-sourcing
metadata
open-source
policy
projects
GitHub
open-source
docs-as-code
policy
This post is an ongoing experiment demonstrating the “front end” output produced by various expressions of AsciiDoc syntax, and it will show off some of the CSS and JavaScript work I’ve done in this area.
AsciiDoc
blogging
writing
Documentation and application should derive all key data from a true single source of truth (TSST) defined once and conveyed across all product and documentation builds.
single-sourcing
YAML
AsciiDoc
docs-as-code
writing
metadata