Recent changes
35934 changed pages · Atom feed · Recent comments · Recently added · Recent ratings
Wednesday November 04 2026
- One image with a link (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Image block (Image URL, Alt text, Link URL), or an image attribute printed in a template. - A slider of images (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Slider block, with the same image source fields as the Gallery. - Space and a line between sections (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Spacer (Height in pixels, default 32) and Divider (Style, Margin) blocks, or vertical whitespace on the blocks themselves. - A horizontally scrolling strip of images (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Sushi bar block: a strip that scrolls sideways. - Tabs with short texts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Tabs block (Tabs "Title|Content" per line, Active tab index). - A gallery with thumbnails (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Thumb gallery block: a large image with thumbnails below. - A two-thirds and one-third split (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Two columns container in view two_columns_66_33 (or 33_66) with blocks in left and right. - Alternating image and text rows (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The Zig-Zag (List) block, or the List block in view list_zigzag. - Launch examples, every page (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The 33 examples of the launch phase of a site's life, each one task done in the Layouts editor and with templates. Map every page type, fill the menus, check the pages and the caches, keep a baseline. - Take a baseline export at launch (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Export every layout, shared layout and mapping on launch day, to compare and restore later. - A layout for every other page (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Default Layout catches the rest: a Path prefix "/" mapping at priority 10, and [ResolverSettings] DefaultLayout as the fallback. - Check every page type by its markup (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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 (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
After the last template and settings changes, one Template & content clear, then a warm-up of the main pages. - The contact page (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Contact (node 185, class Contact form) is a form page; give it a layout with a map and text around the form. - Prepare a mapping and switch it on at launch (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Create the launch mapping with Enabled off, then tick Enabled at go-live. - Hand the site over to the editors (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Show editors the three places they work: the content tree, the Layouts editor and the footer links folder. - Fill both footer lines for launch (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
FooterMenuID[] for the first line, Menu items in the Footer links folder for the second. - Fill the header menu for launch (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Write the final MainMenuID[] list in one edit (administration) or a clear plus adds (console). - Tell editors what changed at launch (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
List what moved from templates to Layouts (or back), so editors know where to change things after go-live. - Check that pages come from the page cache (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
The response header X-Exp-Cache tells HIT, MISS or MISS (purged); check the main pages after launch.
