How do I share a Slidev deck?

Run `npx slidev build`, which writes an SPA to `dist/`, then drag that folder into Comma. `index.html` becomes the report body and the bundles upload alongside it with references rewritten — a URL that keeps the deck interactive.

Should I export to PDF instead?

Only if the audience needs to print it. A PDF flattens the click-through animations, the live code highlighting and the embedded diagrams — which are the reasons to write the deck in Slidev in the first place.

Do slide transitions and code animations work at the URL?

Yes. Report HTML renders with scripts enabled inside a sandboxed iframe, so the Vue-driven transitions, click-through steps and Shiki highlighting behave as they do locally.

Can reviewers leave feedback on a specific slide?

Yes. Anchored threads sit on the rendered content, so "this slide needs the revenue number updated" lands on the slide rather than arriving as "slide 14ish" in a chat message.

How do I keep one link while I keep editing?

PATCH the same report id after each rebuild. The URL you sent stays valid and every version is kept as a revision, so a reviewer can see what changed since their last pass.

Share a Slidev deck

Slidev decks are written by developers for the specific reason that a deck built in Markdown with real syntax highlighting, live components and click-through code walkthroughs is better than the slide software equivalent.

Then it gets shared as a PDF and every one of those properties is discarded.

Build

npx slidev build          # → dist/

That is a static SPA — no server-side rendering, no runtime dependency. If it will live under a subpath, tell the build:

npx slidev build --base /decks/q3/

Publish dist/

Drag dist/ (or a zip of it) into the app:

index.html becomes the report body.
The JS and CSS bundles, fonts, images and any embedded assets upload alongside it, and their references are rewritten to the uploaded copies.
Scripts run inside a sandboxed iframe (allow-scripts, no allow-same-origin), so transitions, click-through steps, Shiki highlighting and Mermaid diagrams all still work.

The person who opens the link gets the deck, not a flattened print-out of it.

Rebuild, same link

npx slidev build

curl -fsS -X PATCH "https://commareports.com/api/v1/reports/$REPORT_ID" \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html dist/index.html \
        --arg title "Deck — $TALK_TITLE" '{title: $title, html: $html}')"

PATCH the same report id every time you rebuild. The link you sent to a reviewer, a conference organizer or the whole company stays valid, and each build is kept as a revision.

What review adds

Anchored threads on a slide — dry-run feedback attached to the slide it is about. See commenting on HTML.
Revisions, so a reviewer coming back after your edits can see what moved.
Access per report — private for an internal readout, opened up after the talk. See the sharing model.

Limits

Entry HTML: 5 MB. Assets: 25 MB per file, 250 MB and 500 files total. Video backgrounds are the thing that gets close to the per-file cap.
60 requests/minute per token.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Publish a deck →