Documentation, published properly.
Pages is for writing and running a documentation website. You decide what documentation you need, write the articles and arrange them into sections. Pages gives your readers the navigation, search and long-form layout that real product documentation needs.
- Not a website builder. There are no layouts to design. You write; Pages handles the site.
- Structure that scales. Sections, categories and nested articles, reordered by dragging.
- Made for reading. A navigation tree, instant search, on-page contents and previous/next links on every article.
- Kept current. Edit a published article, preview the change and publish it when it’s ready.
The same documentation, from both sides.
Think about what readers need to know, not how the site is built.
A docs site is a tree. Sections group what belongs together; articles hold the content; some articles have children when a topic needs more depth. Pages turns that tree into the sidebar, the breadcrumbs, the search index and the links between articles.
Sections and categories
Getting started, Guides, API reference, Changelog. Add, rename and reorder them as the product grows.
Nested articles
Put “Verify signatures” under “Webhooks”. Readers see the hierarchy; you move it with a drag.
Navigation you don’t build
Sidebar, search, on-this-page contents, breadcrumbs and previous/next, generated from your structure.
Write in blocks, or in Markdown.
Headings, text, callouts, code with syntax highlighting, numbered steps, tables and images. Type Markdown and it becomes blocks as you go, or paste an existing Markdown file and keep working from there.
## Retry behaviour If your endpoint doesn't return a 2xx, Korapay retries with backoff for 3 days. > **Note** Return 200 quickly and > process the event in the background.
Retry behaviour
If your endpoint doesn’t return a 2xx, Korapay retries with backoff for 3 days.
Webhooks
Webhooks tell your server when something happens in your Korapay account, such as a payment succeeding or a refund completing.
Each event is sent as a POST request with a JSON body and a signature header you should verify.
Docs get read on phones more than you’d think.
On a small screen the tree folds into a menu, the current location stays visible at the top, and code blocks scroll sideways instead of breaking the page. Nothing to configure.
Browse it, search it, or ask it.
Connect your Pages site to an Ask assistant and your documentation becomes its knowledge. Readers can still use the tree and search; they also get an “Ask about these docs” button that answers with links back to the exact article. When you publish an update, Ask uses the new version.
Write the docs. We’ll publish the site.
Start with a structure, write your first articles and publish on your own domain.