One layout for every entry

Updated 2026-10-03

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.

What it gives you

Design onceNo page to build by hand for each row. Every entry takes its design from the layout.

Change once, every page followsMove a block or add a stat and every entry changes with it. One edit, not one per page.

Always the current dataEntries show their row's values. Upload a new version of the table and every page shows it.

Each page keeps its own textThe page content slot holds writing for one entry only, such as where to find an item.

Search titles for every pageOne Page SEO template on the table gives each entry its own title and description from its row.

Translated onceThe layout's labels are translated one time and show in every entry's language.

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.

Choose where variables belong

This pageVariables saved with one entry's own content.Use for an input or script that belongs to one page.

Shared layoutVariables inherited by every page using this layout.Use for scripts that shared blocks need on every entry.

On a bound page, Variables & Scripts opens This page. Changing shared blocks on the canvas does not change where new variables are saved. Page variables appear in that page's history; shared layout history records the layout's own declarations.

Open View to Variables & Scripts.
Choose Shared layout. Its editor opens with the variables panel ready.
Add the variables and scripts your shared blocks read, then check several preview entries.
Save the shared layout. A reviewed account's changes appear as Submitted for review until accepted.

Pasting blocks does not add their variables. Add shared declarations in the shared layout editor. A page variable with the same name overrides the shared one on that page.

Build one

Open the table in Media & Datasets to Data and click its Shared layout tab. It reads Off on a table without pages: shared layouts are optional, and a table that only feeds lists, tables or maps does not need one.

Click Set up pages. The editor fills the layout with one of the table's rows, so blocks that read the row show real values while you work.
Lay it out the way every entry should look, then save.
Back on the Shared layout tab, click Create the pages. Every page uses the layout from the start.

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

Pages that already exist with their own design each? The Shared layout tab lists them at the top. With a shared layout in place, one button moves them onto it; without one, pick the page whose design should become the shared layout, and every page uses it from then on.

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

Start with a reusable base

In the shared-layout editor, open View to Page bases and data. Choose Dataset overview or Dataset detail to generate blocks from this dataset's fields. Both include a page-content slot for each entry's own writing.

To reuse another dataset's design, choose Copy an existing shared layout, select its dataset and click Load shared base. Match the source fields to compatible fields in this layout's dataset. The target stays fixed to the dataset whose layout you are editing.

Confirm replacement, read the formula and linked-row review steps, then apply to the editor. Check several sample entries before saving. This save changes the shared layout for all attached pages. To change only one page independently, duplicate that page first and use its normal editor.

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.