Authoring templates on Slidura

Variables and typed values

Mon, 01 Jan 0001 00:00:00 +0000

Variables and typed values

Annotation turns a raw catalog into a reusable product. Two tools drive that transformation: per-field typed values (defaults, choices, and a strict/suggestion flag) and head variables (catalog-level {{name}} placeholders interpolated once at submit).

Per-field defaults and choice lists

Every field in the Variables view of the template workspace can carry:

Default value — the text (or ref sentinel like @icon:starter/star) used when a caller omits that field from the fill. Explicit values always win; hidden fields never receive a default.
Choices — an ordered list of allowed values. Up to 50 choices, each non-empty and unique. When a caller sends a string value outside the list, the build is rejected with a validation error that names the field and its allowed values.
Strict vs suggestion — a field with choices either enforces the list strictly or treats it as a suggestion set for the fill builder UI.

In the fill builder, a choices-bearing field renders as a <select>. The first option is “use default” (or “keep template content”) with an empty value; omitting the field is equivalent to selecting the default. A text field with a default shows it as a placeholder.

Published fill endpoints

Mon, 01 Jan 0001 00:00:00 +0000

Published fill endpoints

A published fill endpoint lets an external system POST plain data and receive a finished deck — no Slidura account, no fill builder, no MCP client. You publish a draft from a template, receive a capability token, and hand the URL to whatever system produces the data.

How it works

In the template workspace, open the Usage tab and create an endpoint. Give it a name, optionally set a callback URL and a monthly build cap, then click Publish. Publishing snapshots your current draft — the slide selection, order, and any pre-filled values — as the endpoint’s default_fill. The token (sfe_…) is shown once; copy it.

Design palette

Mon, 01 Jan 0001 00:00:00 +0000

Design palette

Every .pptx embeds a PowerPoint theme: a color scheme of ten named slots and a major/minor font pair. Slidura reads this palette once at catalog time and uses it as the single source of truth for all auto-derived color schemes across your template.

What the palette contains

Slot	Role
`dk1`, `lt1`	Primary text / background pair
`dk2`, `lt2`	Secondary text / background pair
`accent1` – `accent6`	Brand accent colors

Plus major_font (headings) and minor_font (body text).