Context
CarTrawler’s partner integration documentation ran on an ageing Sphinx toolchain. The authoring workflow was fragile enough that developers couldn’t reliably stand it up locally, so in practice only the Director of Engineering could publish changes. That single-person dependency meant updates stalled, the content drifted out of date, and partners were left navigating a site that was visually dated and hard to use.
Challenge
Earlier migration attempts had all failed. The docs relied on custom Sphinx extensions and hand-maintained tables that didn’t map cleanly onto any modern static-site generator, and each attempt stalled on the manual effort of reconciling that content page by page.
Approach
I used AI agents to build a repeatable migration workflow: convert the reStructuredText source into the new Astro docs framework, translate the custom directives and tables into supported equivalents, and surface the small content changes that needed a human decision rather than a blind port. I reviewed those diffs, brought every relevant page up to date, and rebuilt the authoring setup so any developer could run and contribute to the docs.
Outcome
The documentation now lives on a modern Astro framework that’s faster and cleaner for partners to use, with a local workflow any engineer can run. Ownership of the pages is distributed across the product squads that actually own the underlying integrations, removing the bottleneck and keeping the content close to the teams responsible for it.