Appearance & site identity
Who: admins (Hub → Site). Editors usually do not see Site.
Site identity
Hub → Site opens the site form:
| Field | Meaning |
|---|---|
| Name | Site name (wordmark / title context). |
| Tagline | Short line under the name when the theme shows it. |
| Canonical host | Public host, e.g. example.com (no scheme). |
| Home slug | Which page is home. |
| Theme | Theme folder name for this site. |
| Live site | Production mode: default admin password refused; outbound mail must be deliverable (log-only is refused). Do not turn this on or off casually. |
| Enable grants | Turns on widget visibility controls (Public / Editors only / Admin only) on armed sections. Page visibility in Pages works either way. |
Save with Save at the bottom of the dialog.
Appearance
Below the identity fields, Appearance edits theme colours, fonts, spacing, and content width. Changes write into the site’s user CSS (same tokens themes already define). CMS chrome stays kernel-styled.
| Group | What you set |
|---|---|
| Brand | Primary, accent, wordmark |
| Page | Background, text, muted, border, surface |
| Chrome | Header and hero colours |
| Content panel | Panel background, text, headings |
| Links & nav | Link and nav text colours |
| Type & measure | Body / UI fonts (or a Font preset), content max width, spacing, corner radius |
Pick colours with the swatch or type a value. Fonts accept a CSS stack (placeholders show examples). Save on the Site form applies Appearance with the rest of Site.
Tips
- Take a checkpoint before a large colour/font experiment.
- Page and widget visibility are separate — see Pages & navigation.
- Packs and mail From address live on the same Site dialog — Packs & capabilities.