Choosing a Theme¶
Admin → Settings → Theme is where a site admin picks the look of the storefront. (Platform staff can also set a site's theme under System → Tenants → {site} → Theme.)
Changing the theme takes effect for every visitor immediately, so the page asks you to confirm before it saves. To try a theme first, press Preview instead: your shop opens in a new tab with that theme, visible only to people with the preview link, until you publish or discard it (see Theme and Style Preview).
The page¶
| Section | What it shows |
|---|---|
| Your storefront theme | The live theme: thumbnail, name, a one-line description and a Best for line. |
| Modern themes | The current designs, all layered on Nova: Nova, Brock, Depot, Pop, Atelier, Spec, Ridge, Bistro, Diorama and Tend. Shown as large cards with a description and a Best for line. |
| Bespoke themes | Themes built for one kind of shop and not based on Nova. None ship with the platform, so this section only appears when a tenant-authored one exists. |
| Navigation Style | Header and footer options for the live theme. |
To change theme, tick a card (its border turns green and it is marked Selected), then press Preview to try it or Change Theme. A dialog confirms that the change goes live now; Change theme now saves it. The button stays disabled while the live theme is the one selected.
The page works without JavaScript (the radios and the button still submit the form, the confirmation dialog is skipped) and every card can be reached and chosen with the keyboard: Tab to the group, arrow keys to move, Space to select.
Things worth knowing¶
- Each theme changes the layout, not just the colours. Every modern theme redesigns the collection, product and search pages. New sites start on Nova.
- Your brand settings carry across the modern themes (brand colour, font, corner radius, image shape).
- A missing thumbnail shows a plain tile with the theme's initial. It never shows a broken image.
- If the live theme has been removed from the platform's theme list, the page says so and shows the copy the site holds. The storefront keeps working; pick any listed theme to move off it.
- Preview before you switch. Preview shows the whole shop in the new theme, privately, with your brief and CSS as they are (or as previewed). Publish it from the bar or Settings → Preview.
Navigation Style¶
These options are stored on the site and read by the theme's templates. Not every theme reads every option, so the page shows only the ones your live theme uses and says which theme it is talking about. Options a theme ignores keep their stored value, so switching back to a theme that uses them restores your earlier choice.
| Option | Nova | Brock, Depot, Pop, Atelier, Spec, Ridge, Bistro, Diorama, Tend |
|---|---|---|
| Fixed or static header | ✓ | |
| Hide site name with logo | ✓ | ✓ |
| Sticky footer | ✓ | ✓ |
A theme the platform does not know about (a tenant-authored one) is assumed to honour everything, so all options are shown.
For platform operators: theme records¶
Themes are themeContext documents (ThemeContext). Besides the template and asset paths, three optional fields drive this page:
| Field | Meaning | Default when absent |
|---|---|---|
family |
MODERN or BESPOKE |
Derived: nova, or based on nova (directly or through another theme), is modern; anything else is bespoke. An unknown stored value (such as the retired CLASSIC) is ignored and the family is derived |
sortOrder |
Position within the family, lowest first | Nova 10, Brock 20, Depot 30, Pop 40, Atelier 50, Spec 60, Ridge 70, Bistro 80, Diorama 90, Tend 100, all others 1000 (ties alphabetical) |
The description and Best for text are messages, so they can be reworded or translated like any other platform text:
admin.theme.<lower-cased theme name>.description=...
admin.theme.<lower-cased theme name>.bestFor=...
A theme with no messages simply shows its name and thumbnail. Avoid apostrophes and curly braces in these messages, because they pass through MessageFormat.
System update 91.json (BackfillThemeSelectorFields) writes family and sortOrder onto existing records. It only fills fields that are missing, so it is safe to re-run and never overwrites a hand-set value. initialisation/templates.json carries the same values for new installs.
Adding a theme: add its themeContext record (an InsertIfAbsent system update, as for Atelier and Spec), add the two messages, and drop <lower-cased name>.png into web-mvc/.../themes/admin/images/themeThumbnail/. It appears in the right family with no template change.