Frontmatter

Place YAML frontmatter at the beginning of a single-file deck or in _presentation.md for a multi-file project.

---
remarp: true
version: 1
title: "Architecture review"
speaker:
  name: "Alex Morgan"
  title: "Engineer"
  company: "Example team"
audience: "Platform engineers"
level: "300"
quiz: true
duration: 30
lang: en
blocks:
  - name: fundamentals
    title: "Fundamentals"
    duration: 15
  - name: patterns
    title: "Patterns"
    duration: 15
theme:
  source: "./company-template.pptx"
  footer: auto
  pagination: true
  logo: auto
transition:
  default: slide
  duration: 400
---

Metadata

remarp: true identifies source. title, speaker, audience, level, quiz, and duration describe the talk and its planning requirements. version, date, event, and lang carry optional format/event metadata. Use the speaker object; legacy author is only a fallback where supported.

Blocks

Block metadata can supply a name, title, and duration. The builder discovers marked .md files and legacy .remarp.md files in the project directory by filename stem; a block metadata entry does not select an arbitrary source file. Local block frontmatter supplies remarp: true, block, and an optional title. Keep the block name consistent with the global list and total duration consistent with the plan.

Theme

theme supports source, primary/accent/font/codeTheme, footer, pagination, and logo settings. A source can be a PPTX path or an extracted theme directory. PDF paths are recognized, but PDF extraction is currently unimplemented. Brand CSS uses --pptx-* input variables; semantic surface/text roles belong to the framework's light/dark scopes.

Transitions and keys

Transition metadata supplies a default effect and duration. Key configuration is passed to the runtime as a key-to-action map, for example:

keys:
  n: next
  p: presenter

Use actual keyboard event keys and runtime actions; action-to-array examples are not the current runtime contract. Keyboard reference lists supported defaults.