Skip to content
Documentation

Build, pack, present.

Everything you need to know about the .stage container, the SlideStageLite runtime, the self-hosted Pro platform, and the slidestage-pack CLI — in one place.

Quick start

Follow the new docs path: choose the right product, create a .stage file, then present or upload it.

  1. step 01

    Choose your path

    Start with the ecosystem guide if you are deciding between Lite, Pro, and Pack.

    # Read: /docs/ecosystem/lite-vs-pro-vs-pack
  2. step 02

    Create a .stage file

    Use the new tutorial path for CLI packing or the Lite browser converter.

    $ node pack_stage.mjs --src ./my-deck --out ./my-deck.stage
  3. step 03

    Present or upload

    Open the deck in Lite for local playback, then upload the same .stage file to Pro when your team needs a shared library.

    # Read: /docs/ecosystem/html-deck-to-pro-library

Product documentation

Each product has its own focused docs set. Start from the role you need.

.stage container — at a glance

A signed, byte-reproducible zip with a strict manifest. The same file plays identically in Lite, Pro, and the desktop app.

FieldRequiredDescription
schemayesAlways "slidestage@1.0". Pins the manifest contract.
idyesStable, URL-safe identifier. Forbids /, \, .., NUL, control chars.
versionyesSemantic version of the deck content, not the runtime.
createdAt / updatedAtyesDrives the byte-reproducible mtime stamp on every zip entry.
architectureyesmulti-file | multi-file-flat | single-file-deckstage | single-file-html.
slides[]yesOrdered slide list — each entry references a HTML file inside the zip.
compat.requiresCapabilities the deck needs (same-origin-storage, broadcast-channel, window-open). Gated by trust prompt.
offlineSet when pnpm mirror has folded external assets — proves the deck plays without network.