Transform Documentation into a Developer Acquisition Channel

This skill treats documentation as a marketing channel that acquires developers through search, activates them through fast quickstarts, retains them through comprehensive references, and earns referrals through docs developers actually want to share. It structures documentation around four types developers need - tutorials for learning, how-to guides for task-solving, reference for information accuracy, and explanation for conceptual understanding - each mapped to a distinct marketing function such as building confidence or proving product depth. It contrasts good navigation, organized around getting-started, guides, API reference, and resources, against bad navigation organized as generic numbered chapters, and prescribes a fixed per-page information hierarchy: what this is in one sentence, why to use it, how to use it as the bulk of the page, and clear next steps.

Quickstart optimization follows a five-minute rule, since developers should reach a meaningful success moment within five minutes or the quickstart is losing them, measured by time to first successful call, drop-off points, and completion rate, using a fixed structure of prerequisites, install, configure, run, what-you-built, and next steps. A worked good-quickstart example sends an SMS via the Twilio SDK in four short steps, contrasted with a bad quickstart that buries the same task under hundreds of words of architecture background before reaching a single line of working code. API reference guidance requires every endpoint to document a one-sentence description, authentication requirements, request and response formats with real examples, common error responses, and copy-paste code confirmed to actually work, illustrated with a full curl request, JSON response, and error-code table versus a bad example that only lists bare parameter names, and recommends providing examples in cURL plus whichever specific languages developers actually use.

Search optimization for docs targets problem queries, comparison queries, integration queries, and exact error-message queries, with good-versus-bad examples for page titles, meta descriptions, and URL structure, plus internal linking to build a documentation web connecting tutorials and reference rather than isolated silos. Effectiveness is measured through quickstart time and completion rate, search-to-signup rate, support-ticket deflection, page ratings, and internal search queries revealing content gaps, supported by feedback loops like page helpfulness ratings, internal search analytics, support-ticket analysis, and developer interviews. Five named anti-patterns - wall of text, assumed knowledge, the everything page, outdated quickstart code, and hidden prerequisites - each pair a problem with a concrete fix.

Use it when writing or restructuring developer documentation meant to both educate and convert - quickstarts, API reference, and information architecture. Review the developer-audience-context skill first to ground the strategy in who is actually reading.

Given a documentation set or page, it produces an information architecture plan, an optimized quickstart following the five-minute rule, API reference formatting with working copy-paste examples, and an SEO and internal-linking checklist.

Documentation platforms including GitBook, ReadMe, Mintlify, and Docusaurus; code-sample testing via Doctest, mdx-js, or custom CI; search and analytics via Algolia DocSearch, Google Analytics, and session-recording tools. Related skills cover API onboarding, SDK developer experience, developer sandboxes, and broader content strategy.

Developer marketing and technical writing teams who want documentation that functions as an acquisition, activation, and retention channel rather than passive reference material.