Recent changes
Wednesday November 04 2026
-
Rename layouts without breaking imports Updated Markdown page
Imports match layouts by identifier; keep identifiers stable and change names freely.
-
Rescue a layout broken by an import Updated Markdown page
Import the previous export with overwrite and publish; the import purges the page cache itself.
-
Move a site's settings into its extension Updated Markdown page
exp:ini move / move-all move blocks or whole siteaccess scopes into an extension (--create-extension --activate), with a dry run.
-
Change the settings files of another root Updated Markdown page
exp:ini --root=<dir> works on the settings tree of another root (a copy of the installation); the INI cache there is not cleared, and the scope must exist there.
-
Split one installation into two sites Updated Markdown page
Export the layouts of the site's subtree, import them on the new installation after its content.
-
Different node IDs on staging and production Updated Markdown page
Node IDs differ between installations; menus (MainMenuID) need the target's IDs, layouts are matched by remote ID and path.
-
Check your template overrides after an upgrade Updated Markdown page
Your copies of theme templates do not get the theme's fixes; compare them with the new theme versions.
-
Migrate a template-built site to Layouts Updated Markdown page
Keep the design; turn the page layout's parts into template blocks of a shared Header / Footer; add page layouts per class; map them.
-
Rehearse the migration on a copy Updated Markdown page
Run every command against a copy first; the dry runs on live then hold no surprises.
-
Check layouts after an upgrade Updated Markdown page
After upgrading Exponential, export, list, open the main layouts in the editor and compare the pages.
-
Velocity after a migration Updated Markdown page
On a site served by Exponential Velocity, settings changes need exp:velocity restart, as exp:ini says.
-
Plan examples, every page Updated Markdown page
The 35 examples of the plan phase of a site's life, each one task done in the Layouts editor and with templates. Decide page types, layouts, menus, languages and who changes what, before building.
-
Plan A/B variants of a page Updated Markdown page
A Query parameter condition gives one address a second layout: since explayouts 1.4.42 /showcase and /showcase?variant=b each get their own layout on every request.
-
Plan accessibility into the blocks Updated Markdown page
Use the fields the blocks have for it - Image alt text, Heading level, link texts - and keep one h1 per page.
-
Plan a blog section Updated Markdown page
Blog posts (class NG Blog post) already share the article mapping on Fit & Healthy; plan the listing page and its lists.
-
Plan which cache each change needs Updated Markdown page
Write down per kind of change which cache to clear, so launches and updates do not end in "it does not show".
-
Plan campaigns with start and end dates Updated Markdown page
A mapping can have a Time condition (from, to); plan campaign layouts with it: since explayouts 1.4.42 the layout switches at the start and the end, without lag.
-
Choose the layout type for a page type Updated Markdown page
The layout type fixes the zones: Header / Main / Footer (layout_2) for most Fit & Healthy pages, Header / Left / Right / Footer (layout_4) for a sidebar.
-
Plan the content model before the layouts Updated Markdown page
Layouts arrange content; the classes and fields come first. Check what the existing classes offer.
-
Plan your design extension Updated Markdown page
One extension for everything site-specific: templates, stylesheets, settings, translations - named, versioned and activated in the right place.