Slaide Language Reference Guide

The .slaide language reference: headmatter, slides, layout slots, builds, speaker notes, inline styling, and media, all in Markdown.

A deck is one .slaide file. It starts with a config block called headmatter. After that come the slides. The design lives in a separate, reusable master. You write Markdown. The master carries the look.

The rule: keep slide content in Markdown. Put config in the small fenced blocks. Reference layouts, colors, and fonts by name from the master. Only reach for manual positioning when a layout cannot do the job.

The pages below walk through the language one piece at a time.

File structure

Learn the .slaide file format: the headmatter block, slide separators, per-slide frontmatter, and placeholders like {{page}} and {{title}}.

Slots & layouts

Route Markdown into named layout regions with the :: name :: marker, then reuse Aurora's ten bundled layouts or define your own.

Inline styling

Style a span of text with chainable dot-classes for color, size, and gradient fills, right inside your Markdown - no CSS required.

Builds & notes

Reveal content step by step with build markers, attach speaker notes only the presenter sees, and animate between slides with transitions.

Media & embeds

Add images, video, audio, Mermaid and ECharts charts, tables, sandboxed embeds, themed widgets, and inline SVG to any Slaide deck.

Master file

The .slaide.yaml master is the YAML file that holds a deck's whole design - fonts, colors, gradients, layouts, and chrome, all reusable.