Content Calendar for Nextcloud Deck
as a normal Nextcloud Deck board.
Download the JSON, preview the stacks/cards, or use Deckloud's template flow when it is available. The created result is a regular board on your own Nextcloud server.
Board preview
Content Calendar
Ideas
Brief
Draft
Edit
Scheduled
Published
Update Later
JSON
Portable v1 template schema
{
"schema": "deckloud-template-v1",
"schemaVersion": 1,
"slug": "content-calendar-nextcloud-deck",
"locale": "en",
"title": "Content Calendar for Nextcloud Deck",
"description": "A publishing workflow for ideas, briefs, drafts, edits, scheduled work, published pages, and future refreshes.",
"category": "content",
"tags": [
"content",
"calendar",
"publishing"
],
"quickCreateStackKey": "ideas",
"compatibility": {
"requiresBoardCreate": true,
"includesAttachments": false,
"includesComments": false
},
"board": {
"title": "Content Calendar",
"color": "0EA5E9"
},
"labels": [
{
"key": "guide",
"title": "Guide",
"color": "3B82F6"
},
{
"key": "product-page",
"title": "Product Page",
"color": "10B981"
},
{
"key": "template",
"title": "Template",
"color": "8B5CF6"
},
{
"key": "refresh",
"title": "Refresh",
"color": "F59E0B"
}
],
"stacks": [
{
"key": "ideas",
"title": "Ideas",
"order": 1
},
{
"key": "brief",
"title": "Brief",
"order": 2
},
{
"key": "draft",
"title": "Draft",
"order": 3
},
{
"key": "edit",
"title": "Edit",
"order": 4
},
{
"key": "scheduled",
"title": "Scheduled",
"order": 5
},
{
"key": "published",
"title": "Published",
"order": 6
},
{
"key": "update-later",
"title": "Update Later",
"order": 7
}
],
"cards": [
{
"stack": "ideas",
"title": "Capture support questions as page ideas",
"description": "Every repeated support question can become a focused guide or FAQ.",
"labels": [
"guide"
]
},
{
"stack": "brief",
"title": "Map target query and internal links",
"description": "Define search intent, screenshots needed, CTA, related pages, and refresh date.",
"labels": [
"product-page"
]
}
]
}01
What this creates
7 stacks, 4 board labels, and 2 starter cards. Attachments and comments are intentionally omitted so the template stays portable.
02
Why it fits Deckloud
The template is just a recipe for standard Deck objects. No hosted workflow account, no relay backend, and no Deckloud-only object model.
03
Safe import rules
IDs are not stored. Stack and label keys are remapped at creation time, and due dates use relative offsets instead of stale fixed dates.
FAQ
Practical questions
Does this change my Nextcloud server schema?
Does the template include comments or attachments?
Can I edit the board after creating it?
Related
Nextcloud Deck templates, made for real boards.
Download practical Nextcloud Deck templates for kanban, GTD review, releases, bug triage, content calendars, meetings, offline work, and SEO sprints.
OpenBuild a Nextcloud Deck template without sending server data anywhere.
Build a simple Deckloud template JSON in your browser for a Nextcloud Deck board. No account, no upload, no server credentials.
OpenCreate templates that stay portable.
Create portable Nextcloud Deck board templates with stack keys, label keys, starter cards, and relative due dates.
Open