James Aindow — Technical Writer
Documentation Status: Production Ready | Last Updated: October 2025 | Version: 2.0
Meta Notice: Yes, this is a portfolio site disguised as documentation. Because the best way to demonstrate technical writing expertise is to document yourself. Everything here follows standard documentation practices—structure, clarity, component usage—just with the subject being me instead of an API.
Overview
Technical writer with 17 years of development experience spanning Web3, e-commerce, and enterprise systems. Previously led documentation for Starknet (Ethereum Layer 2) in the lead up to mainnet launch and TGE, contributed to Klevu's documentation suite, and spent over a decade building production systems before transitioning to documentation.
What makes this different: Most technical writers understand documentation. I understand the entire stack—from CI/CD pipelines to cryptographic primitives to production architecture. I can write your docs and build the documentation infrastructure.
Quick Links
Key Capabilities
- Documentation Engineering: Write docs + build docs infrastructure + maintain CI/CD pipelines
- Technical Depth: Work directly with cryptographers, protocol engineers, senior developers without translation layers
- Business Context: Understand what matters for GTM, developer adoption, and business outcomes
- Fast Execution: Thrive in fast-moving environments (mainnet launches, rapid iteration, ambiguous scopes)