Recent changes
35934 changed pages · Atom feed · Recent comments · Recently added · Recent ratings
Wednesday November 04 2026
- Plan the content model before the layouts (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Layouts arrange content; the classes and fields come first. Check what the existing classes offer. - Plan your design extension (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
One extension for everything site-specific: templates, stylesheets, settings, translations - named, versioned and activated in the right place. - Plan the site's own documentation (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
For every list, decide manual collection (editors pick) or dynamic collection (a query) before building. - Plan the mapping priorities (Updated, Markdown page)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
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)
Markdown documentation (help center) · Two ways to build · Changed 01:08 pm
Build the layout in the editor, look at it, and throw it away with Discard: nothing is published until Publish layout.
