The spec, the format, the tooling.
A p2present talk is just files plus one small p2present.json manifest. Here's everything
that defines the format and the tools that write it for you.
The format
Manifest spec
The full p2present.json reference — deck, video sources, timing cues, subtitles, signatures, and persistence.
Authoring guide
Step-by-step: assemble slides + a recording, map slides to seconds, and ship a shareable link.
AUTHORING.md → 🧬JSON Schema
The machine-readable schema the Builder validates against. Wire it into your editor for autocompletion.
p2present.schema.json →Tools
Visual Builder
Build a manifest with a live preview and schema validation — no hand-editing JSON required.
Open the Builder → 📤Host assets
Push your slides and video to a hosting/persistence provider and get back content URLs.
Open Host → ▶️The player
Open any manifest in the player — paste a URL, a service id, or a deep-link to an exact moment.
Open the player →Going deeper
README
Project overview, architecture, and how to fork & self-host on your own domain.
README → 🌐Hosting guide
Hosting your assets across URLs, IPFS, WebTorrent, and pay-once persistence providers.
HOSTING.md → 🔗Sharing service
The optional pastebin-lite manifest service — paste a manifest, get a short shareable id back.
SERVICE.md → 🗺Roadmap
What's free forever vs. the optional paid persistence & verified-registry pieces, and why.
ROADMAP.md → ★Source
The whole thing is MIT-licensed and dependency-light. Read it, fork it, send a PR.
GitHub →