Writing and automating since 2012
techwriter.ai began as one technical writer's homepage: a photo, a tagline, and a very good tray of lasagna. The writing got automated. The lasagna became the logo.
For years the writing was done by hand — manuals, specs, release notes, the careful unglamorous work of explaining systems to the people who depend on them. The automating crept in around the edges: scripts that checked the docs, pipelines that built them, bots that nagged when they drifted out of date.
Eventually the edges met in the middle. techwriter.ai is what that turned into: a documentation engine that reads a code repository, writes the knowledge base, and keeps it in sync from inside GitHub Actions — the same loop a good staff writer runs, minus the burnout. The five knowledge bases on this site are its public portfolio, regenerated as the projects they document evolve.
The mascot — our chef, rendered in instrument-panel amber — is the photo from the original site, run through the same block-by-block treatment we apply to everything else: take something handmade, keep what matters, make it machine-legible. Documentation, like lasagna, is layers.
Writing and automating since 2012
You found the easter egg. This is a faithful restoration of the page that lived at techwriter.ai before the machines took over the writing.