Using Fork
Overview
Features and terminology for Fork projects.
Fork centers on branching video: each node in a story can play media and offer choices that lead to other nodes. You design that flow in the editor; viewers use the published player or an embedded player on your site.
Capabilities
- Story editor — Node graph, hotspots on video, project branding, and reusable style templates.
- Player — Full-page playback and an embeddable player for iframes.
- Workspaces — Personal and organization workspaces so the right people can edit and manage assets.
- Assets — Video, image, audio, and font assets stored for your workspace and referenced by projects.
- Viewer access — Projects can be public or protected with an access code, depending on how you publish.
- Analytics — Playback and interaction events can be recorded per project for insights in the app.
Mental model
- Workspace — Where your team and media library live.
- Project — A branching story: graph structure, media, and publish settings.
- Player — What viewers use: it loads your published project and plays the story.
Next
- Story editor — graph, hotspots, templates, branding.
- Player & embed — sharing, links, and access.
- Workspaces & assets — collaboration and uploads.