Deck-As-Code For Prox OS

Role

Deck-as-code is the path for keeping product narrative, launch assets, investor stories, and internal strategy close to source-controlled product knowledge.

This is not a mandate to generate every deck from code. It is a staged doctrine: write the narrative in Markdown first, polish in specialist tools when needed, and avoid letting decks become isolated truth.

Candidate Tools

Tool	Best for	Notes
Marp	Fast Markdown decks, PDF, HTML, PowerPoint-oriented exports	Good for simple narrative decks and internal briefings.
Slidev	Developer-facing interactive decks, code demos, Mermaid, animation	Good for technical launches and demos.
Quarto	Research-heavy reports, data-backed presentations, PowerPoint output	Useful when evidence, tables, and repeatable reports matter.
reveal.js	Web-native interactive presentations	Useful when the deck should behave like a web artifact.
PptxGenJS	Programmatic editable `.pptx` generation from JavaScript or TypeScript	Useful for future automation, not a first-step requirement.
PowerPoint	Formal commercial delivery	Use when the recipient expects an editable business artifact.
Canva	External launch and social visuals	Use for visual polish, not runtime UI truth.

Recommended Repository Shape

Future deck work can use this shape when the project needs it:

docs/go-to-market/decks/
  product-hunt.deck.md
  investor-intro.deck.md
  community-launch.deck.md

scripts/decks/
  generate-product-hunt.mjs
  generate-investor-intro.mjs

Generated PDFs, images, or .pptx files should be treated as build artifacts unless the team intentionally commits a dated export for review, launch, or evidence.

When To Use Markdown Decks

Use Markdown-first decks when:

the message is still changing quickly;
the deck should stay close to docs, roadmap, or growth thesis;
AI tools need to review or rewrite the narrative;
slides need version control and diff review;
the deck is an internal operating artifact.

Use Canva, Figma Slides, Gamma, or PowerPoint when:

visual polish is the primary value;
a customer, investor, or partner expects a traditional artifact;
brand, motion, or layout craft is the bottleneck;
the deck needs fast external-facing presentation quality.

Roadmap

Stage	Capability	Status
Now	Document the deck doctrine and keep deck outlines linked to strategy docs.	Active
Next	Add one Markdown `.deck.md` experiment for launch or investor narrative.	Planned
Later	Add optional scripts for generating PDF, HTML, or `.pptx` from source decks.	Exploring
Long-term	Treat decks, launch rooms, and investor rooms as OS-native artifacts.	Future