Production notes

From plan to readable handoff.

1. Replace the fictional sample with your event name and talks. Keep each talk ID stable across revisions.
2. Enter venue-local dates and 24-hour times. Split any session crossing midnight into separate records.
3. Optionally select a presentation file. The browser calculates its fingerprint; no file is uploaded.
4. Check the schedule. Resolve same-room overlaps.
5. Download both the run sheet and manifest. Closing or refreshing the page clears unsaved edits.
6. For a later revision, restore its manifest, edit it and load the earlier manifest as a baseline.

Build a rehearsal ZIP

Select a current original for every talk, then choose Download rehearsal ZIP. The browser rechecks each hash and packages the originals with manifest.json, run-sheet.txt, package-index.json and a read-me. Restored manifests require original files to be reselected. There is no automatic collection of linked media or verification of playback.

Read the rehearsal handoff checklist →

What a fingerprint tells you

A matching SHA-256 value identifies matching file bytes. It does not verify that slides render, videos play, the speaker approved the version or a room computer received it. Perform those checks in your existing event workflow.

Formats and limits

The web manifest uses schema 2, stores metadata only and accepts up to 100 talks. Import files must be smaller than 500 KB. Local selection allows non-empty files up to 20 MB each and 50 MB total. Python experiment manifests use a different schema and are not interchangeable.