> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fanfare.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Brand, templates, and designs

> Understand how brand settings, templates, and experience overrides layer together—which edits go live immediately and when publishing freezes during a drop.

Set your brand once, create reusable templates for drops, and customize individual launches when you want a release to feel distinct. Some design layers stay linked to every experience that uses them—so edits go live everywhere—while others are copied when you apply them. Knowing which layers stay linked, which colors take priority, and when publishing pauses helps you update designs safely before and during a drop.

> [!NOTE]
>
> The template library and hosted pages are available on Growth and above. Brand settings are available on every plan.

On Starter, selecting **Design Studio** opens the brand editor directly.

## The layers

| Layer | What it controls | Where you set it | Scope |
| - | - | - | - |
| **Brand** | Your **Logo**, six color roles (**Primary**, **Secondary**, **Background**, **Surface**, **Text**, **Muted**), **Body Font**, and **Heading Font**. | **Design Studio → Edit brand** | One per organization; applies across all experiences. |
| **Templates** | Reusable hosted-page templates, widget designs, announcement templates (email, SMS, social), and wallet pass designs. Each is **Draft** or **Live**. | **Design Studio** | Unlimited, with one **Default** per type (except social templates). |
| **Experience hosted page** | The hosted web page for a single experience, created as a copy of a page template or Fanfare starter. | Experience **Design** tab → **Page** card | One hosted page per experience. |
| **Experience colours** | Per-experience color overrides for that drop's widget and hosted page. | Experience **Design** tab | One set per experience. |

Customers interact with your entry widget and—if you publish one—your hosted page. Automated emails sent during the drop are listed under the experience's **Design → Emails** section and use built-in layouts styled with your brand.

![The Design tab of an experience, with cards for Experience colours, Page, Widget and Emails; the Widget card shows the widget design following the organization default.](https://mintcdn.com/fanfare/1LIsN6sNCEZdXydH/images/guide/concepts-design-experience-tab.webp?fit=max\&auto=format\&n=1LIsN6sNCEZdXydH\&q=85\&s=8920298dd612868256229cd3faa7e87b)

Each experience's Design tab shows the design layers shaping what customers see.

## Hosted page vs. entry widget

* **Entry widget** — The interactive component where shoppers join a queue, enter a draw, place bids, book appointments, or buy in a timed release. The same widget design renders whether you embed it on your own site or run it on a hosted page.
* **Hosted page** — A full standalone drop page hosted by Fanfare for a single experience. It's optional—you can run drops using only the embedded widget on your website. See [Build and publish the hosted page](https://docs.fanfare.io/guide/create/hosted-page.md) and [Run it on your own site](https://docs.fanfare.io/guide/create/your-own-site.md).

## Copied vs. linked layers

Whether an edit updates a live drop depends on how that layer attaches to an experience:

* **Copied when used** — Page templates and announcement templates (email, SMS, and social). Applying a page template creates an independent copy for that experience, and composing an announcement snapshots the template. Editing or unpublishing the template later affects only new pages and messages created afterward.
* **Linked live** — Your brand, widget designs, and wallet pass designs. Every experience or pass referencing them reflects the latest saved version automatically.

> [!WARNING]
>
> Editing a **Live** widget design updates every experience using it—including drops running right now—just like editing your brand. Editing a **Live** wallet pass design also rebuilds existing passes that use it. To restyle a single drop without touching others, use **Experience colours** or assign a separate widget design to that experience.

![A diagram showing the brand and widget designs linked live to every experience, page and announcement templates copied into each experience, and Experience colours applying to one experience's widget and hosted page only.](https://mintcdn.com/fanfare/1LIsN6sNCEZdXydH/images/guide/concepts-design-layers.webp?fit=max\&auto=format\&n=1LIsN6sNCEZdXydH\&q=85\&s=df3250d361ba51577881c3b3a29eb9a2)

Linked layers update every experience on save; copied layers apply only to pages and announcements created afterward.

## How Fanfare chooses a widget design

For each experience, Fanfare selects the widget design in this order:

1. The design chosen specifically for that experience, as long as it's **Live**.
2. Otherwise, your organization's default widget design.
3. Otherwise, the built-in **Kinetic** style.

The **Widget** card on the experience's **Design** tab shows which design is active (*"Chosen for this experience: \[design name]"* or *"Org default: \[design name]"*, falling back to *"Org default: Kinetic"*). Clearing your organization's default widget design switches every experience following the default back to Kinetic—see [Templates and widget designs](https://docs.fanfare.io/guide/create/templates.md) before making that change.

## Color and font priority

On the **entry widget**, colors cascade from lowest to highest priority:

1. Built-in widget style defaults
2. **Brand** colors
3. Widget design colors
4. **Experience colours**

If you embed the widget on your own website, theme settings passed by your developer sit above all four. A widget's structural styling—corners, borders, depth, and motion—always comes from the widget design rather than your brand.

On a **hosted page**, page templates inherit only your brand's **Primary** color as an accent (while the embedded entry widget on that page inherits your full brand). Colors set directly on the page override **Experience colours**, which override **Brand**. Unset colors fall back to your brand or the template's default.

**Automated emails** always use your **Brand** and ignore **Experience colours**.

**Fonts and logo:** Widget fonts and logos always come from **Brand**—neither widget designs nor **Experience colours** change them. On your own site, brand fonts display when loaded by your page or configured to load through the widget (see [Run it on your own site](https://docs.fanfare.io/guide/create/your-own-site.md)). Hosted page templates use their own fonts rather than your brand fonts.

## Changes that go live without publishing

Hosted page layout and copy changes stay in draft until you publish, with four exceptions that update live experiences as soon as they're saved:

* **Brand edits** — Brand settings auto-save as you edit. Hosted pages update within about a minute, and widgets and future emails pick up changes automatically (emails already sent aren't affected). See [Set your brand](https://docs.fanfare.io/guide/create/brand.md).
* **Experience colours** — Apply immediately to that experience's widget and hosted page. See [Set your brand](https://docs.fanfare.io/guide/create/brand.md).
* **Widget design updates** — Saving a **Live** widget design, selecting **Change design** or **Reset to org default**, or changing/clearing the organization default immediately restyles every affected widget on both hosted pages and embedded sites. See [Templates and widget designs](https://docs.fanfare.io/guide/create/templates.md).
* **Linked fields on published pages** — Fields bound to source data (product name, description, and image; experience name and schedule; organization name, logo, address, and support email) sync automatically when the source updates, sometimes after a brief delay. See [Build and publish the hosted page](https://docs.fanfare.io/guide/create/hosted-page.md).

## The publish freeze

To prevent accidental page edits while shoppers are entering, Fanfare freezes publishing on an already-published hosted page starting **15 minutes before** any distribution in the experience opens until it closes:

* A distribution with no close time freezes publishing until **30 minutes after** it opens.
* A distribution with a close time but no open time freezes publishing until it closes.
* Deleted distributions never trigger a freeze.
* Your **first publish** is never frozen, and you can still save drafts during a freeze.

If you need to push an urgent update to a published page during a freeze, an organization admin can confirm **Override freeze and publish**.

The freeze doesn't block brand edits, widget design edits, or **Experience colours**—instead, Fanfare asks you to confirm before saving (and saving a **Live** widget design always confirms how many experiences will update, including any in a freeze). See [Build and publish the hosted page](https://docs.fanfare.io/guide/create/hosted-page.md) for override details.

## Draft, Live, and Default templates

* Only **Live** templates appear when selecting designs for an experience.
* Publish a template before selecting **Make default**.
* You can't unpublish or delete a default template until you **Clear default**—and you can't unpublish or delete a widget design or wallet pass design while any experience or loyalty audience still uses it.

See [Templates and widget designs](https://docs.fanfare.io/guide/create/templates.md) for creating, publishing, and managing defaults.

## Plans and downgrades

If you downgrade to a lower plan, existing designs and published hosted pages keep serving customers normally—you just can't edit, publish, clone, or set defaults on templates. On Starter, the template library is unavailable, so you won't be able to unpublish, delete, or **Clear default** on existing templates. Wallet pass designs require **Pro** or above; moving from Pro to Growth still lets you unpublish, delete, and **Clear default** on existing wallet pass designs.

## Example: making changes during a live queue

Suppose Northbound Supply Co.'s "Phantom Stitch Anorak Drop" has a published hosted page made from a template, and its "Inner Circle Early Access" queue is open—putting the experience inside its publish freeze:

| Change | What customers see |
| - | - |
| Update **Brand → Primary** color | Fanfare prompts to confirm; after **Save anyway**, the hosted page restyles within about a minute and widgets and future emails follow. Every other experience updates too. |
| Edit the original page template | Nothing changes on this drop—the hosted page is an independent copy. Only new pages created from the template later pick up the edit. |
| Edit the hosted page itself | Your draft saves, but publishing is paused during the freeze unless an admin confirms **Override freeze and publish**. |
| Update **Experience colours** | After confirming **Save anyway**, this drop's widget and hosted page update immediately. Emails keep your brand colors, and no other experience changes. |

## On Shopify

Design Studio and the experience **Design** tab work the same way in the Fanfare app in Shopify. On your Shopify storefront, the widget's colors, fonts, and wording come from **Design Studio** rather than the Shopify theme editor—if you haven't set a brand font, the widget inherits your theme's font.

In the Shopify app, any staff member with app access can save, publish (including overriding a publish freeze), and archive hosted pages; in the standalone Fanfare admin, those actions require an organization admin. See [Build and publish the hosted page](https://docs.fanfare.io/guide/create/hosted-page.md).

## Related

> [card] [Set your brand](https://docs.fanfare.io/guide/create/brand.md)
>
> Configure your logo, colors, and fonts across every experience.

> [card] [Templates and widget designs](https://docs.fanfare.io/guide/create/templates.md)
>
> Create, publish, and set default templates in Design Studio.

> [card] [Build and publish the hosted page](https://docs.fanfare.io/guide/create/hosted-page.md)
>
> Customize your drop page, publish updates, and override a freeze.

> [card] [Run it on your own site](https://docs.fanfare.io/guide/create/your-own-site.md)
>
> Embed the Fanfare widget on your own website.

> [card] [Announcements](https://docs.fanfare.io/guide/create/announcements.md)
>
> Create email, SMS, and social announcements from templates.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.