The banner that asks a visitor which cookies they allow, and the preferences dialog behind it. Site-wide, worded once.
What it is
The cookie banner is what a visitor meets before this site sets any cookie beyond the ones it cannot work without. It asks once, remembers the answer, and then stays out of the way.
It is site chrome, not a page block: one configuration appears on every page, and it lives in the footer layout — the same place the footer itself is edited. The design system builds the banner and the preferences dialog in JavaScript, so there is nothing on the page to click into; every word lives in the sidebar.
It is already on every page, so there is nothing to add — what you change is its wording. In the editor, scroll to the bar below the footer, unlock the footer layout, and the block's fields open in the sidebar. The bar's two buttons summon the banner and the preferences dialog, which matters because a visitor who has already chosen never sees the banner again — and neither do you.
Change the banner's wording once, for every page
A visitor who has already chosen never sees the banner again, so give them a way back: add a Cookie settings link block to a page, which is what the manage cookies page is built from.
Add a cookie settings link so people can change their mind
Configure it
There are two kinds of thing here, and only one of them is yours to write. The banner message is the sentence naming what this site sets and pointing at the cookies page — write it for someone who has not thought about cookies today.
The descriptions are the rest: what each category is for, and what each cookie does. They are edited in the preferences dialog itself, beside the tick box or in the row they belong to, so the words sit where they are read.
Which categories exist, which cookies they cover, their names and how long they last are set in code, not here — because refusing a category has to actually delete its cookies, and the code is what deletes them. A list you could edit separately could only ever disagree with what is really removed.
What a visitor sees: the banner, the preferences dialog, and their choice being kept
So the site's wording and the site's behaviour come from one place each, and the dialog shows both: the tick boxes and the table are built from the same declaration the clearing logic reads.
Tips
Analytics runs only once a visitor accepts the category named analytics, so that entry has to exist in the list above under that name. Removing the banner stops measurement too, rather than leaving it running with nowhere to object.
One page, one consent configuration. Adding a second consent block to a page is ignored: the design system would otherwise build a second preferences dialog with the same id as the first, and the link would open the wrong one.
Write the message for someone who has not thought about cookies today. Say what is set, why, and where to change it — and keep the link to the cookies page in the sentence, not only in the buttons.
Related pages
The manage cookies page is where a visitor changes an answer they have already given. For a site-wide message that is not about consent, use a global alert; for a message inside a page, an in-page alert.
