Data

Site Options (Blocks)

Site Options are global content fields — the values you reuse across a site, such as phone, address, tagline and social links — defined once and bound into blocks everywhere. There is exactly one value per option, for the whole site. Where: WP Admin → Tiger Blocks → Data → Site Options. Enable the engine under […]

2 min read Updated July 14, 2026

Site Options are global content fields — the values you reuse across a site, such as phone, address, tagline and social links — defined once and bound into blocks everywhere. There is exactly one value per option, for the whole site.

Where: WP Admin → Tiger BlocksDataSite Options. Enable the engine under Modules & WidgetsDynamic Content.

Define once

  1. Add a field, choosing a type — Text, Textarea, Number, Email, URL, Phone, Date, Color, Select or Image (media).
  2. Give it a label and a key (letters, numbers and underscores).
  3. Set its value and save. Definitions and values are stored separately, so the schema is stable even as you update the content.

Bind anywhere

Reference an option with a site.<key> binding on any block — a heading, a link, an image. Update the value in Site Options and every place that binds it changes at once. This is the site-wide layer of Tiger’s dynamic content: where User Fields resolve as author.<key> for the current post’s author, Site Options resolve as site.<key> for the whole site.

Why use it

Put your business phone and address in Site Options so a number change is a one-field edit rather than a site-wide find-and-replace. Social links, a tagline, or a shared brochure URL are all natural fits — anything that appears in many places but has a single source of truth.

Troubleshooting

My site.key binding shows nothing

Check that the key in the binding matches the field key exactly (they are lowercase with underscores) and that the field actually has a value saved. A binding to an undefined or empty option renders as blank.

Can an option hold more than one value?

No — Site Options are single-value, global fields. For per-record data, use a Custom Content Type or a CPT with custom fields; for per-user data, use User Fields.

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.