Stages and zone keys

Earlier builds placed content with stages, frames, presets and one key per zone. The zone rework replaced the stages and frames and, for a time, the zone keys; zone keys are back. This page says what the upgrade did to your content and how to move a page that still uses the old markup.

How it works now

• A zone is one spot with at most one display (a bar or a banner).
• A template sets a new zone's display once, when you create it.
• A page shows a zone with the zone's own zone key, issued on the zone's Install tab.

What the upgrade did to stages and frames

The upgrade turned every stage, and every frame beyond a zone's first, into a zone of its own with one display. No content and no placement was lost:

• A zone with stages kept its id and became the zone of its oldest stage: the stage's name, its key as the slug, and the stage's frame as the display. Every further stage became a new zone in the same way.
• A frame that no stage showed, and every frame after the first of a zone without stages, became a new zone named "<zone name> – <Type> <n>", such as "Home – Bar 2", with that frame as its display. n counts the original zone's frames of that type, oldest first, including the frames its stages showed.
• Such a zone's slug is the original zone's new slug, then -<type>-<n>: when "Home" became "Top" (top), its second bar became top-bar-2.
• Every new zone got a copy of the original zone's tale groups, in the same order.
• A zone that had no frame stayed one zone, with no display.
• Other slugs came from the stage key, or from the zone's name when there was none. A slug another zone of the project already had got -2, -3 and so on, oldest zone first, so a stage key can have changed: check the slug on the zone page.

Each zone made from "Home" shows Home's tale groups, in Home's order; the same for "Shop".

Frames and presets

A frame is now called the zone's display, and there is one per zone. The presets that set up several frames at once (playbooks) are gone: they became templates you pick when creating a zone. A zone made from one keeps only a "created from template" note.

Zone keys are back; the stage attribute stays removed

The zone rework briefly removed zone keys (owner decision, 2026-10-22). They return, as one key per zone: a tak_… key names its zone, so an element needs only zone-key. The stage attribute stays removed, and so do the site-key and zone attributes of the interim builds. A page that still uses a site key with zone= must move to a zone key from the zone's Install tab. An element placed the old way renders nothing, and the site-key attribute logs one console warning per element.

Replace markup like this:

<taleart-view api-url="https://api.example.com" zone-key="tak_…" stage="top"></taleart-view>
<taleart-view api-url="https://api.example.com" site-key="tas_…" zone="home-top"></taleart-view>

with the snippet from the zone's Install tab:

<script type="module" src="https://api.example.com/sdk/v1/taleart.js"></script>
<!-- Optional, once per page: <script>Taleart.init({ locale: "en" })</script> -->
<taleart-view zone-key="YOUR_ZONE_KEY"></taleart-view>

1. Open the zone that came from the stage (or zone) the page used.
2. On its Install tab, an admin issues the zone's key, and you copy the snippet.
3. Replace the old element with the new one. If the page set a theme, pass the zone's slug to configureZone.

See Install a zone for the details.