Recurly documentation design system
I built 57 reusable guide component classes, used on 141 of 146 Engage guide pages, customized ReadMe’s interface, and developed AI-assisted authoring workflows for five product documentation hubs.
Christian Arango
Great product + nice docs = good money
Technical writer & documentation engineer
I design documentation systems that make complex software easier to understand, integrate, and maintain.
Open to work: contractor or employee
Documentation systems in practice
Task-based documentation for mobohubb
I organized and wrote task-based help for four apps, with 86 guides, 941 step-by-step screenshots, and six onboarding paths for administrators, desk staff, and field employees.
Priority Commerce SMB documentation system
I designed one shared ReadMe authoring system that identifies the product, loads the matching one of four reference packages, and turns rough drafts into review-ready MDX without erasing product-specific decisions.
45% fewer support tickets after an API documentation audit and redesign
Recurly
56→92% user-reported documentation satisfaction after consolidating three hubs
Recurly · ReadMe Enterprise
7+ years in API and developer documentation
Since 2018
2025 Technology Impact Award, presented by the CTO
Recurly
How I approach documentation
- Technical depth. API references, webhooks, and docs-as-code, reviewed like the product.
- Systems thinking. Information architecture and reusable components that keep documentation consistent as products change.
- Product judgment. Connecting documentation decisions to adoption, support load, and maintainability.
Outdated docs
Broken link
Missing guide