Cody Anthony
I design the content infrastructure for complex software products, moving documentation out of silos and into the core product lifecycle to ensure long-term accuracy and scalability.
The Core Philosophy
Documentation belongs in the engineering loop.
I bridge the gap between software engineering and developer experience. I author developer documentation and architect the docs-as-code infrastructure, content strategies, and agentic AI workflows that scale it with the software.
This approach is built on three principles:
- Docs-as-Product: Engaging with UX and engineering during design shapes the interface itself, so the product is intuitive before docs ship. By the time I write, I've already helped shape the thing I'm writing about.
- Docs-as-Data: Documentation engineered as structured, reusable data. I componentize content into self-contained chunks that LLMs, AI agents, and human readers can each consume on their own terms.
- Jobs-to-Be-Done & Instructional Design: Content structured around the jobs developers are trying to do. Learning theory and user-centered design cut friction and shorten time-to-first-success.
Core Capabilities
What I deliver across the product lifecycle.
Technical Authoring & DX
Developer guides, API references, UX copy, and cross-functional standards
I partner with Product, Engineering, and UX from the design phase forward, shaping documentation standards before they're written and the product itself before it ships. I build and validate every configuration I document in test environments before publishing.
Content Infrastructure
Platform-scale architecture, legacy migrations, and self-service governance
I migrate enterprise documentation off legacy XML into decoupled, component-based formats. Then I write the contribution runbooks and structural guardrails that keep the system intact long after the migration ships.
AI Engineering & Automation
Agentic workflows, automated content pipelines, and AI-assisted development
I integrate LLMs like Claude into agentic workflows that compress technical research and drafting timelines from days to hours. Documentation ships at engineering velocity instead of accumulating as the debt that drags legacy platforms down.
Information Scaffolding & Onboarding
Console microcopy, task sequencing, and cognitive load reduction
I sequence each technical workflow so developers meet the right information when they need it, applying instructional design to both the prose and the console microcopy. Each page is designed for the moment the developer reaches it.
Featured Work
Selected case studies.
EVS Day 1 Deployment Experience
Console microcopy, 28 help panels, and deployment documentation designed together as a unified Day 1 experience for Amazon EVS, shipped on schedule with general availability.
EVS CreateEnvironment API Reference
Production API reference for Amazon EVS CreateEnvironment. Parameter constraints, validation rules, and error responses, each example verified by hand against the live API.
AsciiDoc Modernization Program
Migrating AWS service documentation off legacy XML to AsciiDoc, unblocking engineering contributors and AI workflows. Started at ROSA, expanded across EKS, SAP on AWS, and high-compliance regions.