Template schema

Create templates that stay portable.

A good template keeps a board's reusable structure and leaves out server IDs and private history.

Last verified

01

Start from a board that worked

Take a board that carried a real project to the end. Keep your stacks, the labels you filter by, and a few cards written as instructions.

02

Portable fields

These import on any server.

  • Stack and label keys.

    Readable keys instead of server IDs, remapped at import.

  • Plain card descriptions.

    Markdown imports everywhere. Put checklists, links, and instructions here, not in comments.

  • Relative due offsets.

    Due in N days, so the timing fits whenever the template is used.

03

Fields to omit

Leave out remote IDs, private comments, attachments, fixed due dates, and server user IDs. Each one breaks on another server or leaks private context.

04

Test it like a stranger

Import it yourself before you share it, and read it as a newcomer. If a card needs insider knowledge, rewrite its description.

FAQ

Practical questions

Is the template schema documented?

Yes. The template hub links the portable v1 schema, and every downloadable template is a working example.

Can I write a template by hand?

Yes, it is plain JSON. The browser builder just removes the risk of syntax errors.

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.