Exporting
Every export format, what it is for, and what it cannot do. The arrow beside Export zip lists them all.
Which one?
| Export | Use it for |
|---|---|
| Export zip for Mighty | A new Mighty interactive, or a new draft of the Storyblock template, with your scenes as its starting content. |
| Project file for Mighty (.json) | Updating an existing Storyblock block in Mighty: upload it in the block's form. |
| Standalone | A web page that plays anywhere: a website, an intranet, an email attachment. |
| Rise code block | A Rise lesson without Mighty. |
| SCORM | Any LMS, as SCORM 2004 or 1.2. |
| PDF storyboard | Reviewing the content with someone else: not for learners. |
The warning badge's checks run before every export; you can export anyway.
Mighty zip
index.html and mighty-form-config.json, ready to import into Mighty Studio. Mighty uses the scenes as default content, which only fills blocks with no saved content yet, so import it as a new interactive or block. Library images go inside it; library video and audio become placeholders to upload in Mighty, and the export lists them.
Project file for Mighty
A .mighty.json for the Storyblock project file upload at the top of the block's form. When a file is uploaded, the block plays its scenes and settings instead of the form's, so you can update a block without recreating it: download the file, edit it here, save, and replace it. See Playing in Mighty.
Standalone
A single index.html (plus a media folder) that runs anywhere, with no Mighty and no LMS. Tracking is off. Completion raises an event a host page can listen for. The learner's place and flags last for the browser session.
Rise code block
A zip to upload into a Rise Code block (Upload project). Completion sends Rise's own completion message, so turn on the block's Set completion requirements to use it with a continue block. Things to check in Rise:
- Rise sets the block's height; set its maximum height if needed.
- Images, video and embeds given by URL must be reachable from the course; library files travel inside the zip.
- Full screen is usually unavailable inside a code block, so its buttons hide themselves.
SCORM
A package for any LMS. The player works with either version; the choice only changes the manifest the LMS reads.
- It looks for a SCORM 2004 LMS first, then 1.2, and runs without errors when there is none.
- It sets incomplete on launch and completed on completion, records scenes and button choices as interactions (if turned on in Completion and tracking), and resumes at the learner's scene with their flags until they complete.
- Media from the library is included and listed in the manifest.
PDF storyboard
A review document printed through your browser: choose Save as PDF in the Print dialog.
- A cover page lists the settings, every scene, any flags, and anything to check.
- Each scene gets a page with its picture (numbered markers optional) and a table of its elements in the order they appear: their content, timing, rules, and what each button does.
- Choose whether pictures show elements that wait to appear, and all scenes or just this one.
Turn on Background graphics in the Print dialog if colours are missing.