Skip to content

The Layout tab vs "Design on site"

The admin Layout tab and the front-of-site "Design on site" overlay edit the same document through the same editor — only the canvas differs.

The Layout tab, in a page's admin form, and Design on site, the link that opens the same page in place on the live site, are two doors into one editor. Every drag, every add from the palette, every property you set behaves identically whichever door you came through, because it's the same component tree and the same undo history underneath both. (You may still see it called "Edit on site" somewhere — that's the old name for this same link.)

What actually differs

Not capability — render mode. The admin tab always shows the page as structure cards: regions, sections and modules labelled by name, with none of the site's own CSS or real components involved. Design on site shows the page as it actually renders, using the real components in the site's own stylesheet, with the editing controls layered on top. Both are looking at, and writing to, the identical layout document — structure view just trades fidelity for a canvas that never breaks no matter what the site's CSS does.

text
Layout tab (admin)     structure cards, no site CSS, always renders
Design on site         the real page, real components, real CSS

One save, either door

Saving from the Layout tab and saving from Design on site write to the same endpoint. There's no version that's "more live" than the other, and no sync step — editing from one and switching to the other picks up exactly what you left.

Leaving with unsaved changes

Switching away from the Layout tab, or out of the content form entirely, while an edit hasn't been saved opens a confirm dialog rather than discarding it. There's no quiet way to lose work by clicking somewhere else. See Saving and undoing in the layout editor for what undo does and doesn't remember across a save.