Technical writing on docs-specific CI, API drift detection, and developer documentation quality.
How DocsCI integrates axe-core and structural validation rules to catch accessibility issues in API documentation — missing alt text, heading hierarchy, color contrast, and ARIA violations — in CI.
A technical deep-dive into how DocsCI diffs your OpenAPI spec against your documentation to detect parameter drift, schema mismatches, and deprecated endpoints before they reach your users.
How DocsCI runs documentation code examples safely at scale — V8 isolates for JavaScript/TypeScript, Pyodide WebAssembly for Python, and ephemeral network allowlists for curl examples.
We analyzed support ticket data from 12 API-first companies and found that a single broken code example costs $47K per quarter in developer time, support overhead, and churn. Here's how we calculated it and what you can do about it.
API drift — when your documentation diverges from your actual API — is silent until a developer hits a 404 or a parameter mismatch. This post explains the architecture behind DocsCI's drift detection engine and how to catch it in CI.
A step-by-step guide to running automated documentation tests in GitHub Actions. Covers basic setup, advanced monorepo workflows, PR comment integration, and scheduled drift detection.