Page themes

A theme changes how a published page looks without you writing any CSS. Pick one and your headings, tables, buttons, forms and links all take on a coherent style.

Themes are Bootswatch themes, served from your own site — never fetched from anyone else's, so a visitor's browser makes no third-party requests and nothing breaks if an outside service goes down.

Choosing one

Per page — in the page editor, open the page's settings and pick a theme. It applies as soon as you save; you don't have to publish to see it.

For the whole site — set a default under Site. Every page uses it unless that page picks its own.

No theme is a real choice, and the default. A page with no theme renders exactly as pages did before themes existed: your own styling, nothing added.

Light and dark

The picker lists light themes first, then dark ones — that's usually the decision you're actually making. flatly, litera and lumen are quiet and readable; darkly, cyborg and slate are dark; sketchy and vapor are not subtle.

Color mode

Separate from the theme: Color mode chooses whether the theme shows in its light or dark form — Light, Dark, or Match the visitor's device, which follows each visitor's own light/dark setting. It sits in the Appearance card next to Theme, on pages and on forms, and the site default under Custom code covers both. A page or form with no choice of its own inherits the site's; with none there either, the theme looks the way it always did.

It needs a theme — a page with no theme has no Bootstrap to switch.

A form has its own Appearance card too. It governs the form's own hosted page; a form embedded in a page looks like that page.

Using it in your content

With a theme on, Bootstrap's classes work in the page editor's HTML. A table with class="table" becomes a styled table, class="btn btn-primary" makes a link look like a button, and so on.

Without a theme those classes do nothing — they're not an error, they just have no styling behind them.

Custom CSS still wins

The order is: theme, then the built-in page styles, then your site-wide custom CSS, then the page's own custom CSS. So anything you write yourself overrides the theme, and you can start from a theme and adjust rather than replacing it wholesale.

Themes and embeds

Embedded forms, data tables, charts and live experiences all pick up the page's theme, so they look like part of the page instead of something dropped onto it.