Assembling a Publication

Bind navigation trees, choose a rendering per type, and write the landing page.

A publication is the thing you publish: which pages exist, how they are presented, and what the landing page says.

Create one

1. In the Model Navigator, click + and choose New Publication.
2. Name it, and give it a URL slug — the short lowercase word that appears in its address, such as handbook.

Navigation — what becomes a page

Under Navigation, use Add tree… to bind one of your navigation trees. The tree decides everything: the elements it reaches become the pages, and its structure becomes the site map.

Bind it to the Sidebar (the usual choice) or the Top menu. You can bind more than one tree.

A branch with a label is itself a page. It shows the branch's own description as an introduction, tiles for its sub-branches, and a sortable index of the elements beneath it — so a branch description is worth writing.

Per-type renderings

Under Per-type renderings, choose which rendering presents each type. Any type you leave alone uses its first rendering, shown as (default).

The homepage

Homepage is the landing page. It is written in the same language as a rendering, but it has no subject — so instead of "this element's related items" it works across the whole model: a welcome paragraph, a headline number, a linked list of sections.

Diagnostics

The Diagnostics section is your health check. It lists the bound trees and, per type, how many pages it produces and which rendering they use. It answers "did that element actually make it in?" at a glance — and anything amber needs attention, usually a rendering selection that could not be resolved.

Look before you publish

Preview publication opens the homepage as readers will see it. Open live view opens the whole site against the current state of the model, before anything is published.