Your deck belongs beside your code

A product launch usually has code, a plan and a presentation. The presentation should be reviewable alongside the other two.

An OPF deck is plain text. Store the file in Git and review the actual content changes. A teammate can see that “Launch on Monday” changed to “Launch after the pilot” without opening two presentations side by side.

{
  "slides": [
    {
      "title": "Launch readiness",
      "bullets": ["Pilot complete", "Launch on Monday"]
    }
  ]
}

Prefer prose? Author in Markdown or YAML and convert to the same canonical JSON format.

opf convert notes.md update.opf.json
opf validate update.opf.json

Why it matters: clearer reviews, recoverable history and fewer mysterious “final-v7” files. Git tracks your source; preview the slides to check the visual result.

Markdown authoring · YAML authoring · CLI guide

Download the complete example. All names and figures in these examples are illustrative.