Building a Page
A page is built from widgets arranged into a structure, saved as a revision.
Where to find it
Architect Panel → Layout & Pages:
- Page Builder — documents, revisions and publishing
- Pages — the site’s page structure
Start from a template
Templates supply a starting arrangement by category and kind. Starting from one is faster than an empty page and produces something consistent with the rest of the site.
Presets capture your own patterns
A preset is a saved arrangement you can reuse. Once your site has a way of doing a two-column feature block, save it — the alternative is rebuilding it slightly differently every time.
Widgets have responsive settings
Each can behave differently at different widths, with per-breakpoint sizing. That is what makes a page work on a phone rather than being a desktop page squeezed.
Check every page at a narrow width. It is the most common thing left undone.
Design in blocks
A page is a stack of sections, each doing one thing. Thinking in blocks rather than in individual elements produces pages that are quicker to build and much easier to rearrange.
Reuse rather than rebuild
If a block appears on more than two pages it should be a global widget. The threshold is lower than people expect, and the cost of getting it wrong is a site that cannot be updated in one place.
Watch the accessibility settings
Widgets carry things like alternative text and whether an image is decorative. Filling those in as you build is a minute; retrofitting them across a finished site is a project.
And for some organisations it is a legal requirement rather than good practice.
Keep custom CSS in the kit
Rather than on individual widgets. Styling scattered across pages is styling nobody can change, and it is how a site drifts away from its own design.
Preview at both widths before publishing
Desktop and phone. A page that is fine on one and broken on the other is the normal outcome of building on a wide monitor.
Worked example
A team built its pages from three templates, saved two of its own arrangements as presets, and kept all custom styling in the kit. Alternative text was written as images were added rather than afterwards. Every page is checked at a narrow width before publishing.
Recommendations
- Start from a template, save your own as presets.
- Global widget anything appearing on three pages.
- Write alternative text as you build.
- Check every page narrow before publishing.