Site Settings
Ten tabs covering everything the whole site shares.
Settings is where you change things that belong to the site rather than to one page: how it looks, what its navigation says, how it identifies itself, and what it connects to.
The important property of this screen is that changes take effect when you save them. There is no publish step, because these settings are part of the shell every page is served inside. Save a navigation label and every page shows it immediately.
Capabilities
General
The site name, its language, whether search engines may index it, your default title, description and share image, your favicon, and your organisation details.
Design System
Colours, spacing, borders and button styling, with a contrast check. Also where you push a design change onto pages built before it.
Typography
Your font roles, the type scale, line heights and letter spacing.
Iconography
The icon family used across the site.
Header and Footer
Two tabs, each with a live preview, direct editing of navigation items, and the option to ask for design changes.
Backdrops
The background images available to sections across your site.
Injections
Code added to every page — header code, footer code, custom CSS and custom JavaScript.
Analytics Pixel
Visitor tracking, and the cookie banner that has to be in place before you can turn it on.
Live Chat
Put a chat widget on every page of the site.
Key Concepts
Everything the whole site shares — header, footer, design system, icons, injections. Settings changes it, and every page picks it up at once.
Unlike a page, a settings change is live when saved. There is no draft state to review first, so check the preview before you save on the header and footer tabs.
These settings belong to this site. A second site on the same brand has its own. Custom fonts are the exception — they are registered against the brand and available to every site on it.
How It All Fits Together
A useful way to decide where a change belongs: ask whether more than one page is affected.
If yes, it is a setting. A heading that is the wrong size everywhere is a design system problem; a menu item with the wrong label is a navigation problem; a tracking script that should be on every page is an injection.
If no, it belongs to the page — in the editor, under Settings, CSS or JS for that page alone.
Warning: A retired site's settings are readable so you can see how it was configured, but nothing can be saved or published. Its domain belongs to the site that replaced it.
