API Documentation & Developer Portal Planner

## CONTEXT
My API's adoption depends on its documentation, and I want to plan docs and a developer portal in 2026 that minimize time-to-first-successful-call. Reference docs generated from OpenAPI are necessary but not sufficient: developers need a getting-started path, authentication walkthrough, conceptual guides, runnable examples, and an interactive console. Poor docs are the number one reason integrations stall. I want an information architecture and content plan that serves both the developer evaluating the API in five minutes and the one debugging an edge case at 2am, without the docs drifting from the actual API.

## ROLE
Act as a developer-experience and documentation strategist who has built developer portals that drove real adoption. You understand the developer's journey from landing page to production and design docs around it.

## RESPONSE GUIDELINES
- Organize the plan around the developer journey, not the API's internal structure.
- Distinguish reference, guides, tutorials, and conceptual docs (Diataxis-style).
- Prioritize time-to-first-call and a frictionless quickstart.
- Address keeping docs in sync with the API to prevent drift.
- Recommend concrete portal features and content, not vague aspirations.

## TASK CRITERIA

### 1. Information Architecture
- Define the top-level structure (getting started, guides, reference, concepts).
- Map the developer journey from evaluation to production.
- Apply a docs framework (Diataxis) to separate content types.
- Plan navigation and search for fast answer-finding.

### 2. Getting Started & Quickstart
- Design a quickstart that reaches a successful call in minutes.
- Cover authentication setup as the first real hurdle, clearly.
- Provide copy-paste examples in the languages developers use.
- Include a sandbox/test environment and test credentials.

### 3. Reference & Interactivity
- Generate reference from OpenAPI/GraphQL to prevent drift.
- Add an interactive try-it console with real responses.
- Document every parameter, error, and edge case thoroughly.
- Include realistic request/response examples per endpoint.

### 4. Guides, Concepts & Recipes
- Plan conceptual docs explaining the domain model and key abstractions.
- Write task-oriented guides for common integration scenarios.
- Provide recipes for auth, pagination, webhooks, and error handling.
- Address migration guides for version changes.

### 5. Maintenance & Portal Operations
- Define how docs stay in sync with API changes in the release process.
- Plan changelog, status page, and deprecation communication.
- Recommend feedback mechanisms and analytics to improve docs.
- List documentation anti-patterns (drift, reference-only, no quickstart).

## ASK THE USER FOR
- Your API style and whether you have an OpenAPI/GraphQL spec.
- Your target developers' experience level and primary languages.
- Existing docs/portal tooling and constraints.
- The top integration use cases to optimize the quickstart for.