How do I publish content entries?
3 min de lectureDébutant
Content entries start as drafts. Publishing makes them available through the Content API so your app can fetch and display them.
Draft vs. published
| Status | Visible in dashboard | Visible via API | Editable |
|---|---|---|---|
| Draft | Yes | No | Yes |
| Published | Yes | Yes | Yes |
Editing a published entry updates it immediately — there's no separate "re-publish" step for content entries (unlike translation keys which require explicit publishing to CDN).
Publishing a single entry
From the editor
- Open the content entry
- In the metadata sidebar, change Status from "Draft" to "Published"
- Click Save (or it auto-saves)
From the entry list
- Go to Integrations → Content CMS → your model
- Find the entry in the list
- Click the three-dot menu → Publish
Bulk publishing
To publish multiple entries at once:
- Go to your content model's overview
- Select the entries you want to publish
- Click Publish selected
This is useful when you've created a batch of content (e.g., all articles for a new help section) and want to make them all live at once.
Publishing via MCP
AI agents can publish entries programmatically:
"Publish the blog post 'my-first-post'"
→ publishContentEntry({ entryId: "...", project: "acme/dashboard" })
"Publish all draft help articles"
→ bulkPublishEntries({ entryIds: [...], project: "acme/dashboard" })
Unpublishing
To take an entry offline, change its status back to Draft. It will immediately become unavailable via the Content API, but the content is preserved — you can republish it later.
Content vs. translation publishing
| Translation publishing | Content publishing | |
|---|---|---|
| Mechanism | Explicit "Publish" button → CDN upload | Status change to "Published" |
| Propagation | ~60 seconds (CDN cache) | Immediate (API reads from DB) |
| Rollback | Publish snapshot restore | Change status back to Draft |
| Scope | All approved translations at once | Per-entry |
Next steps
Cet article vous a-t-il été utile ?