Workflow template

Content Calendar for Nextcloud Deck as a free board template.

An editorial board that tracks each page from idea through brief, draft, edit, and schedule to publication, then to Update Later with a refresh date.

Last verified

Board preview

Content Calendar

Ideas2

Capture support questions as page ideas

Every repeated support question can become a focused guide or FAQ.

Guide

Note which pages should ship a downloadable

A checklist or worksheet attached to a page gives the reader something to take away.

Template

Brief1

Map target query and internal links

Define search intent, screenshots needed, CTA, related pages, and refresh date.

  • Write the one question this page answers
  • Name the reader and what they already know
  • List the pages that will link to it
  • Decide the screenshots or diagrams needed
  • Set the date it should be reviewed again
Product Page

Draft1

Answer the question in the first paragraph

Readers who have to scroll for the answer leave before they find it.

Guidedue in 3 days

Edit1

Edit for one reader

Cut anything that is there to sound thorough rather than to help the reader act.

  • Remove every sentence that adds no instruction
  • Check each claim is true of the shipped product
  • Confirm headings match how people search
  • Read it once out loud
Guide

Scheduled1

Queue the page and its assets together

Images, alt text, and metadata ship with the page, not after it.

Product Pagedue in 5 days

Published1

Link to it from older pages

A new page with no inbound internal links is invisible to readers and to crawlers.

Product Pagedue in 7 days

Update Later1

Set a refresh date and what would trigger it

Name the change that would make this page wrong, so you know when to revisit it.

Refreshdue in 90 days
GuideProduct PageTemplateRefresh
View the portable v1 template JSON
{
  "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-marketing",
  "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": "ideas",
      "title": "Note which pages should ship a downloadable",
      "description": "A checklist or worksheet attached to a page gives the reader something to take away.",
      "labels": [
        "template"
      ]
    },
    {
      "stack": "brief",
      "title": "Map target query and internal links",
      "description": "Define search intent, screenshots needed, CTA, related pages, and refresh date.\n\n- [ ] Write the one question this page answers\n- [ ] Name the reader and what they already know\n- [ ] List the pages that will link to it\n- [ ] Decide the screenshots or diagrams needed\n- [ ] Set the date it should be reviewed again",
      "labels": [
        "product-page"
      ]
    },
    {
      "stack": "draft",
      "title": "Answer the question in the first paragraph",
      "description": "Readers who have to scroll for the answer leave before they find it.",
      "labels": [
        "guide"
      ],
      "dueOffsetDays": 3
    },
    {
      "stack": "edit",
      "title": "Edit for one reader",
      "description": "Cut anything that is there to sound thorough rather than to help the reader act.\n\n- [ ] Remove every sentence that adds no instruction\n- [ ] Check each claim is true of the shipped product\n- [ ] Confirm headings match how people search\n- [ ] Read it once out loud",
      "labels": [
        "guide"
      ]
    },
    {
      "stack": "scheduled",
      "title": "Queue the page and its assets together",
      "description": "Images, alt text, and metadata ship with the page, not after it.",
      "labels": [
        "product-page"
      ],
      "dueOffsetDays": 5
    },
    {
      "stack": "published",
      "title": "Link to it from older pages",
      "description": "A new page with no inbound internal links is invisible to readers and to crawlers.",
      "labels": [
        "product-page"
      ],
      "dueOffsetDays": 7
    },
    {
      "stack": "update-later",
      "title": "Set a refresh date and what would trigger it",
      "description": "Name the change that would make this page wrong, so you know when to revisit it.",
      "labels": [
        "refresh"
      ],
      "dueOffsetDays": 90
    }
  ]
}

01

When to use this board

For anyone publishing on a schedule who keeps losing ideas before they become pages.

02

How to run this board

  • Turn support questions into ideas.

    Add each repeated question to Ideas. Its brief names the target query and internal links.

  • Draft for one reader and edit hard.

    Answer the question in the first paragraph. Use the Edit checklist to cut what does not help.

  • Link it and set a refresh date.

    Link the new page from older ones. Move the card to Update Later with a review date and trigger.

03

What this creates

7 stacks, 4 labels, and 8 starter cards with 9 checklist steps.

04

Standard Deck objects only

The result is an ordinary Deck board that you edit like any other. With a Nextcloud account, Deckloud writes it straight to your server, with no relay.

05

Safe import rules

The file holds no server IDs. Due dates count from the day you create the board, and checklists are Markdown task lists in card descriptions.

FAQ

Practical questions

Does the template include comments or attachments?

No. Comments need an author, and attachments differ between servers and Deck versions, so v1 templates hold text only.

Why is Update Later a stack rather than a label?

A stack keeps published pages in view. A label on an archived card is a reminder nobody sees.

What belongs in the brief?

The one question the page answers, its reader, the pages linking to it, and its next review date.

Get Deckloud

Your Deck boards in a native app

Deckloud runs on iPhone, iPad, Android phones, Mac, Windows, and Linux. It connects to the Nextcloud server you already use.