Content & Publishing · Blueprint
Documentation
A documentation model built for product teams: articles organized into ordered sections, with review dates, related links, and a clear lifecycle from draft to deprecated. Ship a docs site that stays accurate as your product evolves.
- content types
- 2
- fields
- 16
- sample records
- 3
Schema
What's inside
Every content type ships pre-configured with typed fields, validation and relationships.
Article
A single documentation page with ordering, lifecycle status, and cross-references.
11 fields
| title | Text | Page title shown in navigation and at the top of the article |
| slug | Slug | URL segment, nested under the section path |
| summary | Text | One-line description used in search results and section indexes |
| body | RichText | Article content with headings, code blocks, images, and callouts |
| section | Reference | Reference to the Section this article lives in |
| order | Text | Numeric sort key within the section, e.g. 10, 20, 30 |
| status | Enum | Lifecycle state: draft, published, or deprecated |
| last_reviewed | Date | When the content was last verified against the product |
| related_article | Reference | Reference to another Article shown as further reading |
| attachment | File | Downloadable asset such as a sample config or spec sheet |
| hide_from_nav | Boolean | Keeps the page reachable by URL but out of the sidebar |
Section
A top-level grouping that drives the docs sidebar and section landing pages.
5 fields
| name | Text | Section label shown in the sidebar, e.g. Getting Started |
| slug | Slug | URL segment that prefixes article paths in this section |
| description | Text | Intro sentence shown on the section landing page |
| order | Text | Numeric sort key controlling sidebar position |
| icon | Image | Small icon displayed next to the section name |
REST API
Article, as JSON.
Each content type of the blueprint is served by the REST API, with filtering, sorting, search and pagination.
Explore the API docs{
"id": 1,
"status": "published",
"data": {
"title": "Quickstart",
"slug": "quickstart",
"summary": "…",
"body": "<p>…</p>",
"section": { "id": 1 },
"order": "…",
"status": "…",
"last_reviewed": "2026-09-22",
"related_article": { "id": 1 }
}
}Sample data
Ships with sample data
Install the blueprint and explore it with realistic example records.
- Sample
Quickstart
A published article in the Getting Started section with code blocks and a related link
- Sample
Getting Started
The first sidebar section, ordered ahead of Guides and Reference
- Sample
Authentication
A reference article with an attached sample config and a recent review date
Features
Why this blueprint
- Navigation from content Sections and ordered articles generate the sidebar automatically, so restructuring docs never requires a code change.
- Freshness you can audit Status and last-reviewed fields make stale pages easy to find and give readers confidence the docs match the product.
- Connected knowledge Related-article references and downloadable attachments turn isolated pages into a browsable knowledge base.
Use cases
Built for
- A product team maintaining user guides that must track every release
- A platform team publishing API and integration docs alongside sample files
- A support organization moving tribal knowledge into a searchable public knowledge base
- An open source project structuring guides, references, and tutorials in one place
Related
More in Content & Publishing
Start with the Documentation blueprint
Install it in one click, explore the sample data, then adapt every field to your needs.
No credit card required · 3 months free trial · Cancel anytime