Technical Writing
Docs systems, API references, tutorials, and developer marketing that people finish reading.
Playbook: Overhaul a neglected docs site
Sorted page types, working pipelines, and freshness signals readers trust again.
Documentation Systems
Tutorials vs how-tos vs reference vs explanation — separating modes ends most doc confusion.
Versioned markdown, PR reviews, link checks, and preview deploys keeping docs trustworthy.
API Reference & Guides
Every endpoint documented with working request, realistic response, and error table.
Fast first win, verifiable checkpoints, and failure exits keeping momentum.
Dev Content & Advocacy
Structure bug-hunt experiences into engaging technical posts that teach method, not just drama. Use when writing dev blogs, hackathon retrospectives, or 'how I
User-outcome phrasing, migration notes, and consistent categories building release trust.
Document Generation
Template-first structure, style hierarchy over direct formatting, and programmatic population patterns.
Assertion-per-slide structure, visual-first layouts, and appendix discipline for deck generation.
Journey Playbooks
Sorted page types, working pipelines, and freshness signals readers trust again.
Copy-paste-working references with tested examples and honest errors sections.
Story-driven posts and changelogs compounding into audience and trust.
DOCX reports and slide decks produced deterministically from content models.