What front-of-site editing can't do
The overlay edits layout only — menus, the media library, SEO fields and new pages stay in the admin, and an unpublished page can’t be opened here at all.
The front-of-site editor is a full layout editor, not a cut-down one — every section, module and component tool the admin’s Layout tab has is here too. What it doesn’t have is anything outside layout: this is a boundary of scope, not of what you’re allowed to do with a section once you’re editing one.
Site-wide structure stays in the admin
Menus are a separate admin surface entirely, not something the overlay reaches into — there’s no path from an open section to editing navigation. See Menus for where that lives.
Images come from what’s already there
Swapping an image here opens a picker scoped to one prop field — pick from existing media, nothing more. There’s no library view with folders, search across the whole site, or a “replace everywhere this image is used” action; that’s Media, in the admin.
Page settings stay in the full editor
Slug, parent, status and SEO fields don’t appear anywhere in this editor — it’s layout only. Changing where a page lives or what its URL is is Slugs, paths, and moving a page; scheduling and expiry is Publishing, scheduling and expiry; everything else about a content type’s fields is Fields, the body, and the rich-text editor.
It can’t create a page
One link out
The toolbar that appears while you’re browsing (not yet editing) offers a single way out to the rest of admin: a plain “Go to admin” link into the full content editor for the page you’re looking at. Nothing routes you there automatically — see Finding your way around the admin for what’s on the other side of it.
Some modules never show up here at all
A handful of module types are withheld from the palette below site-admin, in the overlay the same as in the admin editor — the gap is shaped by role as well as by surface. See Roles and the capability matrix for what each role can place.