Search
Documentation

← Getting started

First deck in 10 minutes

The fastest path through the whole Slidura loop: sign in → upload → catalog → fill → build → download.

Before you start

Slidura is in private beta. If you don’t have access yet, email hello@slidura.com to request it. Once accepted, sign in at app.slidura.com/login via email magic-link or Google.

You’ll also need a .pptx template to try. If you don’t have one, starter templates are available in the templates home — no upload required.

1 · Upload your template

From the templates home at /templates, click Upload template. Drag in your .pptx. Optionally attach a PDF export in the same step — this enables real-slide previews in the fill builder (the SVG wireframe is the fallback when no PDF is present).

A background job scans the file for fillable fields. It usually completes in a few seconds.

2 · Explore the template workspace

Once the catalog job finishes, click the template card to open the template workspace at /templates/{id}. The tabs are:

  • Slides — per-slide field locator; click a shape to bind it to a field.
  • Variables — head variables ({{name}} interpolated at submit) and per-field defaults, types, and choice lists.
  • Designs — theme palette.
  • Builds — all builds for this template.
  • Usage — published fill endpoints and the downloadable agent skill.
  • Overview — catalog metadata and enrichment controls.

Optional: run vision enrichment from the Overview tab. A Gemini pass proposes field names and descriptions from the slide visuals. You can accept, edit, or ignore the suggestions.

3 · Annotate (optional)

On the catalog editor, add names, descriptions, and allowed values to fields. Set per-field defaults and choice lists, or define head variables for template-level substitution. Builds work without annotation; annotation makes them noticeably better.

4 · Fill and build

Choose the path that fits how you work.

Path A — web fill builder (main path, ~5 minutes)

  1. From the Builds tab, click New build. This creates a durable build object in the created state.
  2. The fill builder opens at /builds/{id}. Use the Values tab to fill fields: the ref picker searches your media library, typed widgets enforce field types, and the Slides tab shows a live slide preview — click a shape to jump to its field.
  3. When the fill looks right, click Start build. The job runs in the background; the status page polls until done.
  4. Download the finished .pptx from the build page.

Failed attempts are refunded. You can reopen or copy any build.

Path B — your own agent over MCP

Download the agent skill from the template workspace’s Usage tab (/templates/{id}/skill.md). Drop it into your agent’s skills folder. The skill wraps the MCP flow for this specific template — your agent calls create_build, update_build_fill, start_build, and get_build_status without needing to know the catalog structure.

See Connect Claude Desktop for the one-paste MCP config.

Path C — hosted build assistant

Open the Assistant tab on the fill builder (/builds/{id}). A Gemini agent reads your brief, searches the ref library, and writes the working fill through structured questions rendered as inline forms. Requires a GOOGLE_API_KEY on the Slidura instance; availability varies.

5 · Download

The finished .pptx is available on the build page once the status is built. The original template is untouched; only the filled values are new.

Next