Importing and exporting templates

A layout is a JSON file. That single fact is what makes the template library useful and what makes a small rollout possible without fleet management.

Importing

Download any board from the gallery and use Layouts → Import. It arrives as a draft, so nothing changes on the wall until you publish.

What is inside a template

The grid, the widgets and their positions, the theme, and references to media. The bundled photographs are placeholders so a board is not empty on first run — replace them before a board faces customers.

Calendar widgets in the templates point at sample ICS feeds with several events in them, so you can see the agenda rendering properly before you point it at your own.

Exporting

Layouts → Export gives you the JSON. Use it to:

• Back up a board you spent an afternoon on.
• Move a design between panels.
• Keep a version in your own version control alongside everything else you look after.

Rolling one design out to many panels

Until fleet management ships, this is the workflow:

1. Build and publish the board on one panel until it is right.
2. Export it.
3. On each other panel, import it, adjust anything site-specific — a branch name, a phone number — and publish.

For a handful of screens it takes a minute each. For fifty it is an afternoon, which is the honest limit of the current design; see the roadmap.

Naming

Name layouts for where they go and what they show, not for when you made them: branch-window-portrait, not layout-final-v3. You will have several, and the console lists them alphabetically.

Version control

Because layouts are plain JSON, keeping them in a git repository works and is worth doing for anything you would be annoyed to rebuild. Twenty revisions on the device is a safety net, not an archive.