Templates

Templates are pre-built stages you can use as starting points. The plugin ships a handful of built-in templates (currently slider-type starters) and lets you save any of your stages as a custom template for reuse. Custom templates are saved in your store and can be reused at any time; applying one regenerates UUIDs so the resulting stage is completely independent from the source.

Browsing templates

From the Add stage create modal, click Browse templates…. The template browser opens with three things per template:

• Preview — thumbnail of the stage.
• Name — display name.
• Built-in badge — if it shipped with the plugin (e.g. rotating-cans, studio-edit, editorial-spotlight). Built-ins can’t be deleted.

Pick a template, configure the parameters (see below), click Use template. A new stage is created from it and you land in its editor.

Template parameters

When you apply a template, the modal offers parameters that get baked into the new stage:

• Stage name — what to call the new stage (e.g. Spring Sale Hero).
• Custom width (px) / Custom height (px) (optional) — override the template’s native canvas dimensions. When set and different from the template, layer positions and keyframes are rescaled proportionally.
• Slide count (slider templates only) — number of slides. Below the template’s native count, extra slides are truncated; above it, additional slides are cloned from existing ones so adjacent slides never repeat.
• Slide duration (s) (slider templates only) — seconds per slide. Recommended 5–7 s so visitors can read the headline; longer for content-heavy slides. Minimum 2 s. Scenes with intro / outro markers stretch the middle (loop) section while intro / outro stay intact; without markers, keyframes scale proportionally.

Click Use template to apply. You’ll see a toast: Stage created from template.

Saving a stage as a template

In the editor toolbar, click Save as template…. Fill in:

• Template name — required, must be unique. If the name clashes, you get “A template with this name already exists. Please choose a different name.”

Click Save template to persist. Future create flows now show this template in Browse templates. A toast confirms Template saved.

The snapshot captures the current stage state — layers, scenes, slides, animations, settings — in a JSON payload. It does not include the stage’s targeting / trigger / frequency / schedule / audience associations (those belong to the stage, not the template’s design).

Deleting a user template

In the template browser, custom templates have a Delete template action (built-ins don’t). Confirmation prompt: “Delete template ‘<name>’? This cannot be undone.”

Built-in templates

The plugin ships with at least these slider starters (loaded from disk under src/Resources/templates/<type>/):

• rotating-cans — animated product can carousel.
• studio-edit — editorial layout.
• editorial-spotlight — focused product spotlight.

All three are slider-type. Popup-type built-ins may be added over time — check the browser for what’s actually present in your installation.

How apply() works

Behind the scenes, the apply step:

1. Loads the saved template (or the built-in source from disk).
2. Generates fresh UUIDs for the stage, every layer, every keyframe, every slide, every M:N pivot.
3. Resolves media references — if a referenced media filename still exists in your library, it’s reused; missing references are dropped with a warning.
4. Optionally rescales layer positions + keyframes if you set Custom width / height.
5. Optionally truncates / clones slides if you set Slide count.
6. Persists the new stage and redirects you into its editor.

The resulting stage has no link back to the template — editing it doesn’t change the template.

Where to go next

• Drafts & revisions — autosave / snapshot / restore within a stage (orthogonal to templates).
• Stages → Slider — playback config for slider templates.
• Layers — what’s actually inside a template.