Documentation templates

Using OpenDocs, build a help center for [product].
1. Create a public space called "Help Center".
2. Add three categories: Getting Started, Account & Billing, Troubleshooting.
3. Under Getting Started, create "Welcome to [product]" from the getting-started template, and a "Set up your account" page.
4. Under Account & Billing, create "Manage your plan" and "Invoices and payments".
5. Under Troubleshooting, create "Common issues" from the troubleshooting template.
6. At the top level, create an "FAQ" page from the faq template.
Fill every page from these notes: [paste notes or your top support tickets].
Leave the space unpublished and show me the page tree when you are done.

Using OpenDocs, create API documentation for [API name].
1. Create a public space called "[API name] API".
2. Add two categories: Getting Started and Endpoints.
3. Under Getting Started, create "Quickstart" from the getting-started template, and an "Authentication" page that explains [auth method].
4. Under Endpoints, create one page per endpoint from the api-reference template: [GET /v1/..., POST /v1/...]. Fill in each one's parameters, example response and error codes from [spec or notes].
5. At the top level, create an "Errors" page and a "Changelog" page from the changelog template.
Leave the space unpublished until I have reviewed it.

Using OpenDocs, set up our employee handbook.
1. Create a private space called "Company Handbook".
2. Add three categories: Company, Onboarding, Policies.
3. Under Company, create "Mission and values" and "Teams and who to ask".
4. Under Onboarding, create "Your first week" from the getting-started template, and a "Tools and accounts" page.
5. Under Policies, create one page per policy: [Time off, Expenses, Remote work]. Write them only from the policy text I paste, and mark anything I have not confirmed as "To confirm".
6. At the top level, create a "People FAQ" page from the faq template.
Policy text: [paste]
Leave the space unpublished until I have reviewed it.

Using OpenDocs, set up an SOP library.
1. Create a private space called "SOP Library".
2. Add a category for each department: [Operations, Finance, Customer Support].
3. Interview me about [process], one question at a time. Then write it as an SOP page under [department] with these sections: Purpose, Scope, Roles, Procedure (numbered steps), Records, Revision history.
4. Mark anything I have not confirmed as "To confirm".
5. At the top level, create "Known issues and escalation" from the troubleshooting template.
Leave the space unpublished until I approve it.

Using OpenDocs, create a release notes site for [product].
1. Create a public space called "Release Notes".
2. Add a category for each year: [2026, 2025].
3. For each release below, create a page named after the version, under its year, from the changelog template. Fill in the date and the Added, Changed and Fixed sections, and remove any section that has nothing in it.
Releases: [paste release notes, merged changes or tickets]
Leave the space unpublished until I have reviewed it.

Using OpenDocs, create product documentation for [product].
1. Create a public space called "[Product] Docs".
2. Add three categories: Getting Started, Features, Administration.
3. Under Getting Started, create "Introduction" from the getting-started template, and a "Quick setup" page.
4. Under Features, create one page per feature: [list features].
5. Under Administration, create "Users and roles" and "Settings".
6. At the top level, create "Troubleshooting" from the troubleshooting template, "FAQ" from the faq template and "Release notes" from the changelog template.
Write every page from [paste product notes, specs or help articles].
Leave the space unpublished and show me the page tree when you are done.