Recent changes
Wednesday November 04 2026
-
Plan the site's own documentation Updated Markdown page
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.
-
Plan the footer links folder Updated Markdown page
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 the forms Updated Markdown page
Forms on Fit & Healthy are content (Contact form, Feedback form, Lead form classes), shown by their full views; layouts place them.
-
Plan where galleries come from Updated Markdown page
Gallery blocks read images from a folder; gallery content items (NG Gallery) are stories of their own. Plan which is which.
-
Plan image sizes Updated Markdown page
Galleries take a thumbnail size alias, templates an image class; plan which sizes the design needs.
-
Inventory layouts and settings from the console Updated Markdown page
exp:layouts list and exp:ini where give a complete, scriptable picture of an installation's layouts and menu settings.
-
Make an inventory of the page types Updated Markdown page
Before building, list which kinds of pages the site has and which layout each gets: the content classes in the tree and the layout mappings.
-
Plan how items look in lists Updated Markdown page
Item view types (Standard, Overlay, Card, Line, Mini, List item, with or without intro) decide each item's look; plan them per list.
-
Plan a second language Updated Markdown page
Each language version is a siteaccess with its own settings (menus) and can get its own layouts through a Siteaccess condition.
-
Plan how layouts are kept and versioned Updated Markdown page
Layouts live in the database; plan regular exports (exp:layouts export) so they can be compared, restored and moved.
-
Plan which lists are hand-picked and which fill themselves Updated Markdown page
For every list, decide manual collection (editors pick) or dynamic collection (a query) before building.
-
Plan the mapping priorities Updated Markdown page
The first enabled mapping by priority whose targets and conditions match wins; plan priorities so specific mappings come first.
-
Plan to measure the work Updated Markdown page
Count the steps and time the waiting parts of typical changes, as on these pages, to compare the two ways on your own site.
-
List the block types you will need Updated Markdown page
Compare the page designs with the block types the editor offers; plan new block types only for what is missing.
-
Collect the node IDs the menus will use Updated Markdown page
Menus and manual collections refer to node IDs; collect them (and their remote IDs) when the tree is built.
-
Plan for speed Updated Markdown page
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 header and footer menus Updated Markdown page
On the Fit & Healthy theme the header menu and the footer's first line are menu.ini lists and the footer's second line is content; plan who maintains which.
-
Prototype a page in a draft Updated Markdown page
Build the layout in the editor, look at it, and throw it away with Discard: nothing is published until Publish layout.
-
Plan who publishes layouts Updated Markdown page
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 a recipes section Updated Markdown page
Recipes have their own layout (Full / Recipe, layout_4 with a sidebar) and their own mapping; plan the category page and its lists.