Themes & Theme Settings
Two related but different things share the word "theme":
- A theme (in the dashboard's Themes page) is an installable site-wide design — pages, sections, navbar, footer, and settings as a package.
- Theme settings (in the builder's panel) are your store-wide design tokens — colors, fonts, buttons, spacing — that every section reads.
Installing a theme
Applying a theme from the dashboard stages it on a draft — it does not touch your live store. You review it in the builder, adjust, and publish when ready; discard it and live was never affected. Pages you created yourself survive a theme change: a theme replaces the structural pages it ships, never your custom landing pages.
Theme settings
Theme settings are organized into groups — the important ones:
| Group | Controls |
|---|---|
| Colors & schemes | Named color schemes (background, text, buttons…) that sections reference. Change a scheme once, every section using it follows. |
| Typography | Body, heading, subheading and accent fonts, sizes, line heights, per-heading overrides. |
| Buttons & inputs | Corner radius, borders, text case, which font preset buttons use. |
| Page layout | Content width (fixed / full / custom), for desktop and mobile separately. |
| Logo | Store logo (overrides the navbar's own), favicon, and the default product image used when a product has no photo. |
| Cart, Search, Animations… | Behavioral choices: drawer vs. page cart, search empty-state collection, card hover effects. |
Theme settings are edits like any other: they land on your draft on Save and reach shoppers on Publish.
Color schemes, not colors
Sections don't carry raw colors — they reference a scheme. That's what keeps a storefront coherent: a section moved from one store area to another picks up the right palette automatically, and a rebrand is one edit per scheme rather than one per section.
Any Google Font
The font pickers offer a curated set, but typography accepts any Google Fonts family by name — set "Playfair Display" and the storefront loads it automatically, at all common weights. Fonts are served from your own store's domain, not from Google: shopper browsers never contact Google's servers (relevant for GDPR), and font files are cached at the edge like any other asset. A misspelled family name simply falls back to the default — nothing breaks.
Per-page theme overrides
Custom pages (landing pages) can override the store scheme, background, and fonts for that page only — the campaign page can go dark-mode while the rest of the store stays light. Core pages always follow the global settings.
History
Publishing keeps a history of prior live states on the dashboard's Themes page, so a publish that went wrong can be rolled back. History restores stage onto a draft like everything else — you review the restored state before it goes live again.