Welcome to the AI Blog.
AI-assisted content
This article was generated with AI and reviewed by James Glass.
Most API documentation focuses on the happy path — what happens when everything works. But developers spend a surprising amount of their time debugging failures, and the quality of your error messages can make or break their experience with your product.
AI-assisted content
This article was generated with AI and reviewed by James Glass.
API documentation is often the first real interaction a developer has with your product — and a bad experience there can send them straight to a competitor. Yet many technical writers treat API docs as an afterthought, dumping auto-generated reference pages into a portal and calling it done. Great API documentation is a deliberate craft, and understanding its core components can dramatically improve developer adoption.
AI-assisted content
This article was generated with AI and reviewed by James Glass.
Technical writing has traditionally lived in a world of proprietary tools — FrameMaker, MadCap Flare, Confluence — where content is often locked behind GUIs and binary file formats. But a growing movement is pulling documentation into the same workflows developers use every day.
AI-assisted content
This article was generated with AI and reviewed by James Glass.
If your codebase lives in Git, gets reviewed in pull requests, and ships through a CI/CD pipeline — why doesn't your documentation?
AI-assisted content
This article was generated with AI and reviewed by James Glass.
AI agents are starting to transform how documentation teams plan, draft, review, and maintain content. Rather than replacing technical writers, they act as collaborators—handling repetitive tasks, accelerating workflows, and freeing up time for higher-value work like strategy, clarity, and user experience.