Layouts, field keys and the validator
A layout is a small template: HTML with keys in double braces, plus CSS. There are two kinds: a gallery layout (the list) and an article layout (one article's page).
The field key legend
Under the editor, grouped: hub and page, gallery, each article, article page, style, sections, and this hub's own template fields with their types. Click a key to insert it at the cursor. The legend is generated from the same list the validator checks, so it cannot offer a key that prints nothing.
The ones you will use most:
- Gallery:
{{#entries}} ... {{/entries}}loops over the page's articles; inside it,{{title}},{{summary}},{{image}},{{url}},{{date}},{{author_name}},{{category_label}}. - Article page:
{{{entry.body}}}prints the body. Three braces, because it is HTML. - Template fields:
{{entry.f.your_field}}for text,{{{entry.f.your_field}}}for rich text.
The validator
Layouts go live when saved, so the save is the gate. It refuses a layout that would break the page:
- an unclosed or mismatched section,
- a gallery with no article loop or no
{{url}}, - an article page with no body,
- an HTML field in two braces (it would print raw tags),
- a template that fails to render with sample articles.
Each error names the line. Unknown keys and very large CSS are warnings: the save goes through and the warning is shown, with the nearest real key suggested for a typo.
Live layouts are never blocked after the fact. The check runs when someone saves.