Overview
One or two sentences on what this site is for.A B2B logistics platform selling to operations managers at mid-size distributors. Buyers are sceptical, time-poor, and comparing us against incumbents they already dislike.This is context, not instruction. It is what lets generated copy be about your actual business instead of a generic version of your category.
Tone
How the writing should sound.Direct and concrete. Short sentences. No exclamation marks, no “revolutionary”, no “seamless”. British spelling.Tone rules that name things to avoid tend to work better than adjectives. “Professional” means very little; “no exclamation marks” is unambiguous.
Constraints
Hard rules, one per line. These are the things that must not happen, rather than preferences about style.Templates
Reusable page structures, each with a name and a description of what sections it contains, in what order, with what content focus. Add one with + Add template.Campaign landing page — hero with a single offer, three proof points as cards, one testimonial, FAQ of five entries, closing CTA. No navigation to other products.Once a template exists you can name it when creating a page:
“Create a /spring-sale page from the Campaign landing page template”
Where the brief applies
The brief is part of the site’s configuration, so it is shared: every person editing this site works against the same standing instructions, and updating it updates it for everyone. It is context rather than a filter. It steers what gets generated; it is not a compliance gate, and it does not retroactively check content that is already on the page. For the checks that do look at what is actually published — missing metadata, broken links, images with no alt text — see site health.Also in Site settings
The same drawer, titled Site Config, holds the rest of a site’s configuration, most of which is set once by whoever wired the site up:
Published snapshots, and their Restore button, are on the Sites page
instead — see review and undo.