Site settings
/authoring/slate/settings
PreviewSlate previewslate
Site Settings — "Configure defaults, SEO, analytics and access control for site." — is the one Slate page whose values are stored: on the documentation site in the authoring service, read by both generators — "the hosted build worker and the ZIP the Export screen downloads". A project without a site reads "This project has no documentation site yet. Saving creates one named slug-docs…"; if the authoring service is unreachable, settings cannot be loaded or saved.
Code samples
Default language tab (the first tab, curl, or a language) and Remember a reader's language preference (kept in the reader's browser).
SEO and social sharing
| Field | Rule |
|---|---|
| Site title (meta title template) | Tokens {page_title} and {site_title}; default {page_title} · {site_title}; up to 200 characters |
| Meta description | "n of 160 characters shown in a search result"; up to 500 stored |
| Open Graph image URL | An absolute http(s) URL |
The Generated page head preview shows the result for an example "Getting started" page.
Analytics injection
A Google Analytics 4 Measurement ID (G-…) and an optional Segment write key. The scripts
load from Google Tag Manager and Segment's CDN; an offline copy of the site still renders without
them.
Access control
| Mode | What it means |
|---|---|
| None — public access | Anyone can read the hosted site |
| Password protected | One shared password of at least 12 characters, stored as a one-way hash and never shown again; 12-hour reader sessions. Replace the shared password, or leave blank to keep it |
| SSO (SAML / OIDC) — enterprise gate | Readers sign in with the suite; optional Allowed email domains |
"The gate applies to the hosted site. It is enforced by the authoring service on every request…" A downloaded ZIP cannot enforce it — see Export.
Search engine indexing
Allow — index all pages or Disallow — noindex all pages, with the Generated robots.txt preview. A gated site is forced to noindex: "The gate above publishes this site as … whatever is selected here…"
Save
Save settings (Saving…) stores the settings and the access policy; Reset discards the form. Errors block the save — "Fix the errors above to save — a value that would be dropped at build time is not stored as though it worked." — and the result says what happened: "Created documentation site "…" and saved its settings.", "Settings and access policy saved. The next build applies them.", or "Settings saved, but the access policy was not: …"