- Give the home page its layout A Location mapping to the site root node: on Fit & Healthy, Landing Page / Home on Location 89 at priority 210.
- Give every article the article layout A Subtree mapping with a Class condition: Full / Article on Subtree 89 for ng_article, ng_blog_post, ng_news at priority 130.
- Give one page its own layout A Location (or Path) mapping with a high priority beats the class mapping for one page.
- A plain layout for the legal pages Privacy Policy and Cookie Policy are articles but use Full / Article (Plain): a mapping with two Location targets and the article class condition at priority 150.
- A layout for every other page Default Layout catches the rest: a Path prefix "/" mapping at priority 10, and [ResolverSettings] DefaultLayout as the fallback.
- Check that every layout links the header and footer Before launch, each page layout's header and footer zones must link to Header / Footer; exp:layouts list shows it.
- Fill the header menu for launch Write the final MainMenuID[] list in one edit (administration) or a clear plus adds (console).
- Fill both footer lines for launch FooterMenuID[] for the first line, Menu items in the Footer links folder for the second.
- Set the social media links The footer's social icons come from the fields facebook, twitter, instagram and linkedin of the site info object; each icon shows only when its field has content.
- Fill the prefooter for launch Pick the launch articles of the shared Prefooter in the Layouts editor; it shows on articles and recipes.
- Check every page type by its markup Layouts and templates leave markers in the HTML (zone sections, ngl-block classes, menu item IDs) that a script can check before launch.
- Clear the caches once before launch After the last template and settings changes, one Template & content clear, then a warm-up of the main pages.
- Take a baseline export at launch Export every layout, shared layout and mapping on launch day, to compare and restore later.
- Make sure no draft is left open Unpublished drafts are invisible to visitors but confuse the next editor; list them before launch.
- Check that pages come from the page cache The response header X-Exp-Cache tells HIT, MISS or MISS (purged); check the main pages after launch.
- The header menu of a second language A German siteaccess (bold_ger, starter_ger on this installation) has its own menu.ini; write its list in its own scope.
- A different layout for one language A mapping with a Siteaccess condition gives the German version of a page type its own layout.
- The contact page Contact (node 185, class Contact form) is a form page; give it a layout with a map and text around the form.
- Launch the blog list page A landing page with a dynamic List of NG Blog posts, mapped by Location; the posts use the article layout already.
- The Layouts part of a launch checklist Mappings, links, drafts, shared layouts, export: the five checks of the Layouts side before go-live.
Documentation license
This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.
Exponential Copyright © 1998-2026 Exponential Foundation and 7x