FYI: In the past, those files were used to launch Flash-based versions or redirect to HTML5. But re-directing isn't necessary for courses published to HTML5 only. That's why the files you mentioned aren't there.
In Updates 35 and later, the published output only includes these files when you choose to include both HTML5 and Flash formats. We made this change to simplify the published output.
To distribute a published course:
Upload the course to your web server or LMS, then link to the story.html file in the published output. If your LMS requires you to identify a file, point to index_lms.html for SCORM/AICC content.
2 Replies
Use the story.html and index_lms.html files.
FYI: In the past, those files were used to launch Flash-based versions or redirect to HTML5. But re-directing isn't necessary for courses published to HTML5 only. That's why the files you mentioned aren't there.
Hi Charlie. Happy to help, and Judy is spot-on!
Background:
In Storyline 360 Updates 34 and earlier, the published output always included these
_flash
and/or_html5
files:• index_lms_flash.html
• index_lms_html5.html
• story_flash.html
• story_html5.html
In Updates 35 and later, the published output only includes these files when you choose to include both HTML5 and Flash formats. We made this change to simplify the published output.
To distribute a published course:
Upload the course to your web server or LMS, then link to the
story.html
file in the published output. If your LMS requires you to identify a file, point toindex_lms.html
for SCORM/AICC content.• For more details, check out this resource!
This discussion is closed. You can start a new discussion or contact Articulate Support.