Pages: Documentation Site
Guides documentation site structure, navigation, and content organization. Typically hosted on docs.* or help.* subdomain. Includes Getting Started, guides, tutorials, API Reference (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for product marketing context first: If .claude/product-marketing-context.md or .cursor/product-marketing-context.md exists, read it for product, audience, and use cases.
Identify:
- Product type: Software, API, hardware, service
- Audience: End users, developers, admins
- Content sources: Markdown, MDX, Git, CMS
- Subdomain: docs., help., or path (/docs)
Documentation Structure
| Section |
Purpose |
Typical Content |
| Getting Started |
Onboarding, first steps |
Quick start, installation, first task |
| Guides / Tutorials |
Step-by-step learning |
How-to articles, workflows |
| Concepts |
Background, architecture |
Key concepts, glossary links |
| API Reference |
Endpoint docs |
Auth, request/response, examples; part of docs, not separate page |
| Troubleshooting |
Problem solving |
FAQ, common errors, support links |
Best Practices
Information Architecture
- Progressive disclosure: Start simple, link to depth
- Sidebar navigation: Hierarchical, collapsible sections
- Search: Full-text search for long doc sets
- Breadcrumbs: For deep hierarchies
API Reference (within Docs)
API Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request/response schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI/Swagger for consistency.
Content
- Task-oriented: "How to X" not "X feature"
- Code examples: Copy-paste ready, multiple languages if relevant
- Screenshots/videos: For UI-heavy products
- Versioning: Document product/API version when applicable
SEO and Discovery
- Index docs: Unless internal-only; use robots if needed
- Internal links: Cross-link related articles, link to main site
- Schema: TechArticle, HowTo for guides
Output Format
- Structure (sections, hierarchy)
- Navigation design (sidebar, top-level)
- Getting Started outline
- Content checklist per section
- Subdomain/path recommendation
Related Skills
- api-page-generator: API intro page links to docs
- sidebar-generator: Docs sidebar design
- faq-page-generator: FAQ can live in docs or main site
- content-strategy: Doc content planning
1---2name: docs-page-generator3description: When the user wants to create, optimize, or structure a documentation site. Also use when the user mentions "docs," "documentation site," "docs subdomain," "docs.yourdomain.com," "help center," "knowledge base," "Getting Started," "API Reference," "user guides," or "tutorials."4---56# Pages: Documentation Site78Guides documentation site structure, navigation, and content organization. Typically hosted on `docs.*` or `help.*` subdomain. Includes Getting Started, guides, tutorials, **API Reference** (endpoint docs), and troubleshooting. Distinct from API introduction page (api-page-generator).910**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.1112## Initial Assessment1314**Check for product marketing context first:** If `.claude/product-marketing-context.md` or `.cursor/product-marketing-context.md` exists, read it for product, audience, and use cases.1516Identify:171. **Product type**: Software, API, hardware, service182. **Audience**: End users, developers, admins193. **Content sources**: Markdown, MDX, Git, CMS204. **Subdomain**: docs.*, help.*, or path (/docs)2122## Documentation Structure2324| Section | Purpose | Typical Content |25|---------|---------|-----------------|26| **Getting Started** | Onboarding, first steps | Quick start, installation, first task |27| **Guides / Tutorials** | Step-by-step learning | How-to articles, workflows |28| **Concepts** | Background, architecture | Key concepts, glossary links |29| **API Reference** | Endpoint docs | Auth, request/response, examples; part of docs, not separate page |30| **Troubleshooting** | Problem solving | FAQ, common errors, support links |3132## Best Practices3334### Information Architecture3536- **Progressive disclosure**: Start simple, link to depth37- **Sidebar navigation**: Hierarchical, collapsible sections38- **Search**: Full-text search for long doc sets39- **Breadcrumbs**: For deep hierarchies4041### API Reference (within Docs)4243API Reference is a section of docs, not a standalone page. Include: endpoints by resource, auth, request/response schemas, error codes, rate limits, code examples (cURL, SDKs). Use OpenAPI/Swagger for consistency.4445### Content4647- **Task-oriented**: "How to X" not "X feature"48- **Code examples**: Copy-paste ready, multiple languages if relevant49- **Screenshots/videos**: For UI-heavy products50- **Versioning**: Document product/API version when applicable5152### SEO and Discovery5354- **Index docs**: Unless internal-only; use robots if needed55- **Internal links**: Cross-link related articles, link to main site56- **Schema**: TechArticle, HowTo for guides5758## Output Format5960- **Structure** (sections, hierarchy)61- **Navigation** design (sidebar, top-level)62- **Getting Started** outline63- **Content** checklist per section64- **Subdomain/path** recommendation6566## Related Skills6768- **api-page-generator**: API intro page links to docs69- **sidebar-generator**: Docs sidebar design70- **faq-page-generator**: FAQ can live in docs or main site71- **content-strategy**: Doc content planning
ulpi-io