Content & Publishing · Blueprint
Newsletter
A model for teams that treat their newsletter like a product: issues with subject lines, preview text, and send scheduling, built from ordered story blocks. Every issue doubles as a web archive page, so past editions keep earning traffic.
- content types
- 2
- fields
- 17
- sample records
- 3
Schema
What's inside
Every content type ships pre-configured with typed fields, validation and relationships.
Issue
One edition of the newsletter, from draft through send to public archive.
9 fields
| subject | Text | Email subject line, also the archive page title |
| slug | Slug | URL segment for the web archive version |
| issue_number | Text | Sequential label shown in the header, e.g. #42 |
| preview_text | Text | Inbox preview snippet shown after the subject line |
| intro | RichText | Editor's note that opens the issue before the stories |
| hero_image | Image | Banner image at the top of the email and archive page |
| send_date | DateTime | Scheduled or actual send time, used to order the archive |
| status | Enum | One of: draft, scheduled, sent |
| show_in_archive | Boolean | Includes the issue in the public web archive |
Story
A single item within an issue: a headline, a blurb, and a link out.
8 fields
| headline | Text | Story title rendered as the block heading |
| issue | Reference | Reference to the Issue this story appears in |
| summary | Text | One or two sentence blurb under the headline |
| body | RichText | Longer content when the story is written in full |
| image | Image | Thumbnail or illustration for the story block |
| link | Link | Destination the story points readers to |
| cta_label | Text | Link text, e.g. Read the full post |
| order | Text | Numeric sort key controlling story position in the issue |
REST API
Issue, 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": {
"subject": "Issue #42: The state of shipping fast",
"slug": "issue-42-the-state-of-shipping-fast",
"issue_number": "…",
"preview_text": "…",
"intro": "<p>…</p>",
"hero_image": { "url": "…" },
"send_date": "2026-09-22T09:00:00Z",
"status": "…",
"show_in_archive": true
}
}Sample data
Ships with sample data
Install the blueprint and explore it with realistic example records.
- Sample
Issue #42: The state of shipping fast
A sent issue with intro, hero image, and four ordered stories
- Sample
Why we rewrote our billing stack
The lead story in issue 42, linking to the full blog post
- Sample
Community picks of the month
A curated roundup story with a thumbnail and outbound links
Features
Why this blueprint
- Issues built from blocks Ordered story records make each edition easy to assemble, rearrange, and reuse across email and web.
- Inbox details modeled Subject, preview text, and send scheduling live as fields, so the whole team reviews the email before it ships.
- An archive that compounds Every sent issue becomes a public page, turning your back catalog into evergreen, linkable content.
Use cases
Built for
- A content team curating a weekly industry digest with linked stories
- A startup sending monthly product updates that mirror a public archive
- A media creator running a paid newsletter with a browsable free archive
- A community manager assembling member roundups from recurring story blocks
Related
More in Content & Publishing
Start with the Newsletter 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