Skip to content

SlideStage ecosystem · html-deck-to-pro-library

From HTML Deck to Pro Team Library

Mirrored docs keep the language used by their source repo. Site chrome stays in your selected language.

This tutorial shows the full SlideStage path: start with an HTML deck, package it as .stage, verify it in Lite, then upload it to Pro.

Prerequisites

You need:

  • An HTML deck.
  • Node.js and slidestage-pack.
  • Access to SlideStage Lite.
  • A deployed SlideStage Pro instance and a user account.

1. Prepare the source

Keep the deck in its own folder:

my-talk/
  index.html
  assets/
  speaker-notes/

Speaker notes should preferably live in sidecar Markdown files.

2. Detect the framework

node scripts/detect_framework.mjs ./my-talk

Check kind and recommendedMode.

Use wrap for reveal.js or impress.js when you need the original runtime. Use split for structured inline decks.

3. Pack the deck

node scripts/pack_stage.mjs \
  --src ./my-talk \
  --out ./my-talk.stage

4. Verify the package

node scripts/verify_stage.mjs ./my-talk.stage

Do not upload an unverified .stage file.

5. Check it in Lite

Open SlideStage Lite and drop in my-talk.stage.

Check slide order, assets, notes, presenter tools, and trust prompts.

6. Upload to Pro

Log in to SlideStage Pro and upload the same .stage file.

Pro validates the archive, computes its SHA-256, stores the blob, and creates deck/version records.

7. Team acceptance

Open the deck detail page and verify playback, notes, annotations, and permissions.

If the package changes, pack and verify it again before uploading a new version.