Templates

Start with a useful shape.

A template should ask the questions the finished documentation must answer. It should never be filler with nicer headings.

01

Product documentation

Guide customers from first success through everyday workflows, integrations, and recovery.

  • Overview
  • Quickstart
  • Core concepts
  • Workflows
02

API documentation

Give developers a working first request, then the reference and failure modes they need.

  • Introduction
  • Authentication
  • Quickstart
  • Endpoints
03

Help center

Organize answers around customer tasks instead of the structure of your own company.

  • Start here
  • Account
  • Using the product
  • Billing

Start with the docs you already have

Beautiful docs are easy.
Keeping them accurate is the hard part.