The help experience should teach people how to choose the right publish path, what the billing model actually means, and how the workflow behaves after they click publish.
Launch checklist
Quick start
The fastest path is not always the same path. The docs surface should help customers decide between native adapters, secure webhooks, and future rebuild or repo modes.
Billing and credits
Subscriptions grant entitlements, extra purchases mint immutable records, and backlink failures can trigger refunds through the same ledger model.
Publishing ops
The docs should set expectations around validation, retries, destination IDs, and how live versus draft publishing differs across adapters.
Start with opinionated setup guides for CMS and TypeScript-site teams before expanding into a full docs IA.
Explain retries, verification, idempotency, and credit grants in plain language so customers know what the automation is doing.
The best docs reduce misconfigured integrations by helping teams choose the correct lane before they ever paste a token.