Settings

Site Settings & Design Tokens (Blocks)

Site Settings holds your global design tokens — brand colours, typography, headings and buttons — so every block draws from one consistent palette. Change a token once and the whole site re-skins. Where: WP Admin → Tiger Blocks → Settings → Site Settings. What you can brand Colours — Primary, Secondary, Text and Accent, plus any […]

2 min read Updated July 14, 2026

Site Settings holds your global design tokens — brand colours, typography, headings and buttons — so every block draws from one consistent palette. Change a token once and the whole site re-skins.

Where: WP Admin → Tiger BlocksSettingsSite Settings.

What you can brand

  • Colours — Primary, Secondary, Text and Accent, plus any number of named custom colours.
  • Typography — Primary, Secondary, Text and Accent font families with weight, size and line-height.
  • Headings — per-level settings for H1 through H6 (family, weight, size, colour).
  • Buttons — a global button style (font, weight, size, colours).
  • Image defaults used across blocks.

How tokens reach your blocks

On save, Tiger Blocks writes a static tiger-tokens.css file into your uploads folder containing :root { --tiger-* } custom properties, and enqueues it (plus a utility-classes stylesheet) on both the front end and inside the block editor. Blocks reference those tokens — pick Primary or Accent in a colour control rather than a raw hex — so a single change here cascades everywhere. The token file regenerates automatically each time you save.

Shared surface with Tiger Elements

Tiger Blocks emits the same --tiger-* token names Tiger Elements uses, so a block styled against those tokens renders identically under either plugin. When both are active, one plugin owns the global design surface to prevent duplicate settings — if Tiger Elements is active, configure tokens there.

Troubleshooting

My token change did not take effect on the front end

The tokens live in a generated CSS file. Saving Site Settings rewrites it, but a full-page cache or CDN may still serve the old copy — clear those caches and hard-refresh. Also confirm the block in question uses a token (Primary/Accent) rather than a hard-coded colour.

The Site Settings screen is not available

It only appears when Tiger Blocks owns the data/design surface. If Tiger Elements is active it owns the tokens, so set them there; if the Dynamic Content module is off, the screen is hidden until you re-enable it.

Still stuck?

We’re here to help

Can’t find what you’re looking for, or hit something that looks like a bug? Reach the support team or ask the community.