- Plan a recipes section Recipes have their own layout (Full / Recipe, layout_4 with a sidebar) and their own mapping; plan the category page and its lists.
- Plan topic pages Topics (class Topic: Running, Workout, Health, HIIT) have the layout Full / Topic; plan what a topic page lists.
- Plan a video section Video content (NG Video) lives below Video (node 164) and gets Full / Video; plan the landing page's lists.
- Plan where galleries come from Gallery blocks read images from a folder; gallery content items (NG Gallery) are stories of their own. Plan which is which.
- Plan moving layouts from staging to production Build on a staging installation, then export and import the layouts; content is matched by remote ID and path.
- Plan a sandbox for risky changes Try changes that must be published to be seen on a copy of the installation, never on the live site.
- Plan to measure the work Count the steps and time the waiting parts of typical changes, as on these pages, to compare the two ways on your own site.
- Plan the footer links folder The footer's second line is the children of one folder (remote ID in menu.ini [SiteInfo] FooterLinksRemoteID); plan its items and their order.
- Plan who publishes layouts A layout is changed in a draft and published as a whole; plan who may publish shared layouts, as they change many pages at once.
- Plan the content model before the layouts Layouts arrange content; the classes and fields come first. Check what the existing classes offer.
- Plan for speed Cached pages answered in 22 to 102 ms on the test copy, a page after a full template clear in about 3 s; plan launches and cache clears with that in mind.
- Plan the site's own documentation Write down the layouts, mappings, menus and templates of the site in the same structure as these pages, so the next person can change them.
- Build examples, every page The 35 examples of the build phase of a site's life, each one task done in the Layouts editor and with templates. Make the blocks, lists, galleries, columns and templates of the pages.
- A hero banner at the top of a page A large image with a title, a sentence and a button: the Hero block with its six fields, or a template block with the same markup.
- An about-us section with picture and text Title, text, image and link side by side: the About block, or the same markup in a template block.
- A row of three features Three short selling points: the Features block, or a Three columns container with three Cards, or one template.
- A wall of partner logos from a folder The Logos block reads images from a parent node (Parent node ID, Limit, Class filter, Image attribute identifier, Thumbnail size alias); or a fetch in a template.
- A customer quote The Quote block with Quote text, Author, Source and Alignment, or the same in a template.
- A call-to-action button The Button / Link block (Text, Style, Target, Use link), or a link in a template.
- A section heading with the right level The Title block (Title, Heading level 1-6, HTML tag, Use link) for headings between blocks.
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