One layout for every entry

Updated 2026-08-13

A shared layout is one design that every entry of a table renders. Edit it once and all of them change.

It assumes you have a table with pages bound to it. If not, start with Tables and rows.

How the two halves fit

A bound page renders two things at once: the shared layout, and its own content flowing into the layout page content slot.

The shared layout is the template every entry renders. Wherever it puts a page-content slot, that one page's own blocks flow in. Blocks outside the slot belong to all entries; blocks inside it belong to this page alone.

Outside the slotThe template. Belongs to every entry.Put the design here.

Inside the slotThis page’s own content. Belongs to nobody else.Put a block here to keep it on one page.

That answers the question everybody asks first: to keep a block on this page only, put it inside the page-content slot.

The editor shows the composed page as one tree and takes it apart again when you save, so you drag a block into the slot the same way you drag anything anywhere. A layout can have more than one slot, each with a name.

Build one

The usual route is to design one page properly and then promote it:

Open a bound page and lay it out until it is the design you want for all of them.
Open the Binding panel.
Make this the shared layout for the table.

Blocks that read the row become the template. Blocks that are only about this entry stay with the page.

Or start from the template itself, at Media to Data to the table to Edit layout. Same editor, same blocks.

Place a page content block wherever the entries’ own writing should appear. A template without one leaves no room for it.

An existing page joins or leaves a shared layout from its Binding panel. Leaving keeps the page’s own content and drops the template around it.

Blocks that read the row

A template is mostly holes: it says “the name goes here”, not “Grunt goes here”. Blocks fill those holes by naming a column, and the picker offers them.

Anywhere a block asks which column to read, the picker lists them with what each one holds on the entry you are previewing - and for a picture column, the picture. You no longer have to remember the column's name or spell it right.

The list shows what each column holds on the entry you are previewing, and for a picture column it shows the picture. A name the editor cannot place is still accepted and flagged, because a few blocks legitimately read a different table.

Pair this with conditions and one template covers entries that are not all the same shape.

The entry it previews against

A template on its own would render as a skeleton. So the editor picks one real entry and previews against it: its values fill the blocks, its content sits in the slot, and conditions decide with its row.

Switch the previewed entry often. A template looks finished on a well-filled entry and full of holes on a sparse one, and the sparse one is the page you need to find.

Entries with no matching row are labelled in the picker, because a template that renders blank for one of those is telling you about the data, not about the layout.

Only the template is saved. The entry’s own content is borrowed for the preview and goes back where it came from.

Before you save

One save changes every page built from the table, so the editor states the number up front.

Check a sparse entrySwitch the preview to one with little data. Headings with nothing under them are the usual finding, and a condition is the usual fix.

Check the slotWith no page-content block, every entry’s own writing has nowhere to go. The editor marks orphaned content rather than dropping it.