Templates reduce setup time and improve consistency. Instead of beginning with an empty project or an empty page, you can start from a structure that already ref...
Templates reduce setup time and improve consistency. Instead of beginning with an empty project or an empty page, you can start from a structure that already ref...
Templates reduce setup time and improve consistency. Instead of beginning with an empty project or an empty page, you can start from a structure that already reflects a common documentation use case.
Doxbrix includes two template layers:
- project templates for the structure of an entire documentation site
- page templates for the shape of an individual page
Project templates
When you create a project, the first section is Start with a template. This is where you decide whether Doxbrix should seed the site with a ready-made structure.
A project template does more than create placeholder content. It can define:
- the initial set of spaces
- the starting page inventory
- the overall navigation pattern
- the content model expected for that use case
That makes templates useful for both evaluation and production. They help teams start from a known-good shape, then refine it instead of inventing everything at once.
The template gallery
Open Templates to browse the full catalog. The gallery is designed to help you compare starting points quickly and with enough detail to make a good decision.
Each template card shows:
- the template name and description
- category
- whether it is marked Popular
- counts for spaces and pages
- Open live demo
- Use this template
The gallery also includes:
- category filters
- sorting by Most popular, A → Z, or Most pages
- a count of how many templates are currently visible
Use Open live demo when you want to inspect the structure before committing to it. Use Use this template when you already know it matches the documentation you need to produce.
Available project templates
| Template | Best for |
|---|---|
| 📄 **Blank** | An empty project that you structure entirely yourself. |
| 🛟 **Help Center** | Support-led documentation with onboarding, feature help, FAQs, and support content. |
| 🔌 **API Documentation** | Reference-heavy developer documentation with authentication, endpoints, and examples. |
| 📦 **Product Documentation** | End-user and admin documentation with guides, features, tutorials, integrations, and help. |
| 🏢 **Internal Knowledge Base** | Private documentation for onboarding, operations, process, and internal standards. |
| 📋 **Release Notes & Changelog** | Versioned release communication, deprecations, and migration notes. |
| ⚡ **Developer Product Docs** | Docs for developer platforms that combine onboarding, concepts, and reference material. |
| 🎯 **Marketing Site** | Public-facing product and company pages. |
| 📦 **SDK Reference** | Language-specific SDK setup and usage documentation. |
| 🎨 **Design System** | Component, token, pattern, and accessibility documentation. |
| 💬 **Support FAQ** | Lightweight question-and-answer support documentation. |
| 🎓 **Education Course** | Structured lesson-based educational content. |
| 📟 **Runbooks & Playbooks** | Operational and incident-response documentation. |
Page templates
When you add a page from the content tree, Doxbrix opens Choose a template. This dialog gives you a structured starting point for the page itself.
| Template | Starts with |
|---|---|
| **Blank** | Start with an empty page. |
| **Guide** | Step-by-step walkthrough with prerequisites and next steps. |
| **API reference** | Endpoint documentation with parameters, responses, and examples. |
| **FAQ** | Question-and-answer accordion for common questions. |
The dialog explains the model clearly: you are picking a starting point, not locking the page into a rigid format. After creation, the page remains fully editable.
Page templates are especially useful when:
- several authors are contributing to the same section
- you want procedural pages to follow a shared rhythm
- you want every API page to begin with a predictable reference structure
- you want support content to feel consistent from article to article
Templates are starting points, not constraints
One of the strengths of Doxbrix templates is that they accelerate setup without locking teams into someone else’s structure.
After using a template, you can still:
- rename spaces and pages
- remove content you do not need
- add sections that are specific to your product
- reorganize the navigation entirely
- rewrite the seeded example content in your own voice
That makes templates valuable even for experienced teams. They do not replace planning. They reduce the amount of blank-page work required before planning becomes visible.