Content types on Slidura

Charts

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

Charts

Place data-driven native charts into your PowerPoint slides. The template owns the chart type and styling; your fill supplies the data.

How charts work

When Slidura scans a template, any existing chart shape becomes a chart field in the catalog. The catalog records the chart type (bar, line, pie, …), the number of series, and the category labels — the shape signature. Your fill provides new categories and series values; the build patches the chart’s data caches and embedded workbook in-place without touching the template’s colours, data labels, or number formats.

Tables

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

Tables

Place tabular data into PowerPoint tables. The template owns the table style and banding; your fill drives the row and column count.

How tables work

When Slidura scans a template, any existing table shape becomes a table field in the catalog. The catalog records the current row count, column count, and the table style ID. At build time the engine reshapes the template table — adding or removing rows and columns to match your data — then writes cell content. The table’s style, banding, and header formatting are never touched, so the output stays on-brand regardless of how many rows your data has.

Images

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

Images

Upload a raster or vector image once; reference it from any fill. The build embeds it into image_N picture-frame fields in the finished deck.

How images work

Slidura’s scanner detects picture-frame shapes in a template and records them as image fields in the catalog. At build time the filler replaces the placeholder with your image, cropped and scaled to fill the frame exactly as PowerPoint would.

Supported formats: PNG, JPG, GIF, SVG. Each file is validated on confirm (magic-byte check, dimension cap, decompression-bomb guard) before being stored privately in object storage.

Icons

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

Icons

Replace template icon carriers with glyphs from any SVG icon pack. Icons land in the finished deck as native vector shapes — no raster fallback.

How icons work

The scanner detects three kinds of icon carrier in a template: SVG-picture shapes, textless autoshapes used as placeholder icons, and icon-font glyph runs. Each becomes an icon field in the catalog. At build time the filler swaps the carrier with the SVG geometry for the chosen glyph, placed through the same native-shape pipeline (svgdeck) that procedural arts use.

Diagrams

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

Diagrams

Place Mermaid diagrams into your slides in three modes: a static image, a step-by-step Morph animation, or fully editable native shapes.

Three modes

Mode	Sentinel	Output	Editable in PowerPoint
Static	`@diagram:<id>`	One PNG placed as a picture	No
Morph animation	`@diagram-morph:<id>`	One still slide per cumulative step, linked by a Morph transition	No (images)
Native shapes	`@diagram-native:<id>`	Autoshapes, connectors, and text transcoded from SVG	Yes

All three modes use the same domain/diagram feature and the same API/MCP surface; the mode is set when you create the diagram.

Code blocks

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

Code blocks

Place syntax-highlighted, animated code reveals into your slides. Syntax highlighting uses Pygments; animation uses PowerPoint Morph or native click builds.

Two animation engines

Engine	How it works	Slides produced
`morph` (default)	One slide per reveal step; identical code box, only highlight colours change; Morph cross-fades them	One per step
`native`	One slide; each step’s code box is revealed on click via a `<p:timing>` tree	One

Choose morph for smooth animated transitions between steps. Choose native for an in-slide, click-to-reveal build that keeps everything on one slide.

Procedural arts

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

Procedural arts

Procedural arts are Slidura’s replacement for SmartArt: structured data goes in, a native PowerPoint diagram comes out. No AI, no external render service — the geometry engine runs synchronously in pure Python.

How it works

The artdeck engine accepts a layout ID and a data payload, solves the geometry, and emits an SVG built from theme tokens (accent1, neutral, etc.) rather than literal colours. The svgdeck pipeline then converts that SVG into native PowerPoint shapes, picking up the template’s actual palette at build time. The round-trip budget is under 100 ms; failures surface as validation errors, not silently broken slides.