Theme settings
Configure the global settings your theme exposes: the controls every page on your site inherits
Theme settings are the global controls your theme exposes: colours, fonts, header behaviour, footer content, and any other site-wide options the theme developer has surfaced. Settings here apply across your whole site. Individual pages can expose their own separate controls; see per-page theme settings.
The exact list of settings depends on your theme. Two sites running different themes will see different fields here.
Common settings exposed by themes
Most custom themes surface settings along these lines:
- Brand colours: primary, secondary, accent, text, background.
- Typography: heading and body fonts, font scale, line height defaults.
- Logo and favicon: uploaded once and used across the site.
- Header behaviour: sticky on scroll, transparent over hero, alignment.
- Navigation: which menus appear in the header and footer, and what's in them.
- Footer content: text, links, logos.
- Social links: URLs your theme uses to render social icons.
- Default theme settings for content: for example, the default header style for new pages.
Themes can also expose custom settings specific to your organisation: sponsor banners, accessibility statements, default ticketing CTAs, and so on.
Editing theme settings
Open Themes under Design in Basker. Find the Current theme section at the top and click Configure on the current theme. The theme settings appear as a series of fields grouped under tabs the theme developer has organised. Edit a value and save.
Saving keeps the change as a draft; it doesn't go live yet. To publish it, go back to Themes and click Deploy on the current theme, or use Publish changes from the Configure screen.
After you publish, Basker refreshes cached site content. A setting may appear quickly on the page you're viewing, while changes that affect several pages can take up to the broader refresh window. See Content updates and caching.
Theme settings versus per-page settings
Per-page theme settings are a separate set of controls: whatever fields the page's chosen template exposes, stored on that page. They aren't overrides of the settings on this screen, and there's no inheritance between the two. Changing a global theme setting doesn't change any page's settings, and a page's settings don't fall back to a matching global value if left blank; they fall back to the default the template defines for that field.