Website › Web is the site's configuration (setup/web). Its Hosting and Cookie consent sections below are pages of their own in the Website area (Website › Hosting, Website › Cookie consent) over the same document.
Site#
The publish gate — an unpublished project answers 404 on every host — plus the site menu, the page list, the header, footer, 404 and maintenance documents and the shell settings the templates read.
Maintenance page. Pick (or Create new) a document as the Maintenance page to show a branded "under construction" page instead of the plain 404 while the site is unpublished: every address then serves that document — with your header, footer, design and head tags — answered 503 with Retry-After and noindex, so search engines wait instead of dropping or indexing the site. Design it like any page and check it in the Studio preview by opening its own address; forms and listings on it stay inert until you publish. Publishing switches it off; leave the field blank for the built-in 404.
Language in URL decides how a visitor's language reaches the site (needs at least two project languages):
- Cookie (the default) — one URL serves every language; the visitor's choice is remembered in the
drop_localecookie. - Path — every language has its own address:
/o-nasfor the first (default) language,/en/aboutfor the others. The card shows each language's URL code (cs,en,en-gb— Language / Region presets, or type your own) with an example URL; the codes are saved for every language, so adding a language later never moves them. The first language never takes a prefix —/cs/o-nasredirects to/o-nas— so reordering the languages changes which language your unprefixed URLs serve (the languages editor warns you).
Path mode saves only after its checks pass: each code is valid and unique and is not a platform path, a collection's URL segment or an existing page URL; and a warning reminds you that a cookie-based language switcher stops switching — use the Language switcher element instead. Old links keep working after the switch: an English slug opened without a prefix (/about) redirects to /en/about. Path mode also gives every page hreflang alternates and a canonical address and makes the sitemaps list every language (SEO). Switching back to Cookie keeps the codes.
Favicon#
The site icon; CRM & Studio compares the saved favicon with its own icon mirror and offers to resync when they differ.
Headers#
Response headers the render server adds to every page (security headers, caching hints).
Footer#
Footer tags — raw HTML added at the end of <body> on every page: after the site footer and the page globals, before the page and element scripts. The place for analytics, chat widgets and tracking pixels that should not hold up the first paint (a snippet that must run before first paint still belongs in Head tags). Same editor, lint chips and Insert asset link helper as the head tags, and gated by the cookie bar exactly like them.
Cookie consent#
The platform's cookie bar, off by default — switch it on here or keep it off and run your own solution. When on, the published pages ask visitors for consent before any non-essential third-party tag runs: the analytics, marketing and embed tags in Head tags and Footer tags are neutralized at render and revived only for the categories the visitor grants (your own site files are never touched). The tab has four cards: the switch and appearance (bar or box, position, the categories offered, the cookie-policy page, whether Head tags are gated, whether unknown services are gated, the consent version to bump when the declaration changes, an optional cookie domain for apex + www sites); Detected services — Rescan classifies everything the site loads (head tags, elements, templates, the design CSS) against the vendor catalog, lists each service's cookies and where it was found, lets you re-assign its category, and saves the snapshot as what the bar's settings panel shows visitors; the gating preview — exactly which head tags will wait for which category, with warnings for HTML the gate cannot parse (left as written); and Bar texts — the consent translation group (seed the built-in Czech / English defaults, then edit them under Localizations). There is no floating button: the "Cookie settings" link belongs in the site's footer — any element with a data-drop-consent-open attribute reopens the settings (write it empty and hidden: the bar un-hides it and fills in the consent.reopen text, so it stays invisible while the bar is off); page code can listen to the drop:consent event. The full guide is Cookie consent. Design record: .dev/plans/cookie-consent-bar.md.
Spam protection#
The project's own Google reCAPTCHA v3 key for its forms — the site key, the secret (never shown again), the domains to register on the key, the runtime switch and the badge. Forms are protected one by one in their access panel. The full guide is Spam protection.
Hosting#
The project's canonical hosts ({sid}.inbs.dev, demo-{sid}.inbs.dev) with live reachability, and the custom domain card: the exact DNS records to create, Connect to validate and issue the certificate, per-domain status. See Custom domains for the mechanism. Custom domains are a paid-plan feature.
Refresh site caches (managers only) drops everything the hosting servers hold for the project — rendered pages, documents, setup, templates, assets — on every server that serves it (the *.inbs.dev fleet and, on Production, the custom-domain server). You should rarely need it: every edit reaches the hosted site within seconds through the hook feed, and the servers keep what they have for up to 4 hours only because that feed tells them when something changes. Use it when a change did not show up (a lost push); the next visit renders fresh.
Needs the web capability.