So what is the actual difference? I usually just use story.html and from what I can tell the only difference I notice is the html5 version seems to take a bit of a hit on resolution.
Hi Bruce! Your course will intuitively play the best version based on the browser folks are using to take your course. The requirements for viewing courses is here in our system requirements article.
More and more, as people are using mobile devices for their e-learning, course authors want to create the best experience for their learners. This article describes publishing your courses for mobile devices.
And as far as the resolution hit, while we are focused on ever-improving our HTML5 output, you can read more about that issue here.
Which link is best to share the story_html5 link or the story.html link? We are posting our content as continuing medical education and people may be viewing our content from different types of devices, OS and browsers.
Do people ever share both links so people can choose which one will be best for them?
In storyline 2 we have to use html 5. I am wondering what is the difference between story_html5.html" and "index_lms_html5.html". I know normally you link the index page and that is the default, but it was suggested to me that story_htm5 would allow it to work smoother. Is this true?
Good morning. I'm publishing for LMS and in my Storyline output folder, there is:
index_lms.html
index_lms_html5.html
story.html
story_html5.html
I believe that we would link the LMS to the index_lms.html file for LMS courses. My question is why are "story.html" and "story_html5.html" included in an LMS publish, since apparently they are not used when importing a course into an LMS?
Please straighten me out. Thanks for any info you can provide.
I have published and the folder is created. However, the folder only has the following: html5, mobile, story_content --> folders and analytics-frame, meta, story --> files. I am referring to a course which asks me to make changes to the story_html5.html which is missing. Mozilla Browser and Windows 7 SP2 is the configuration. What is going wrong here?
For anyone following along, we simplified the published output in Storyline 360 builds 3.35.20995.0 and later. When you publish HTML5-only or Flash-only courses, Storyline no longer generates the following files in your published output:
index_lms_flash.html
index_lms_html5.html
story_flash.html
story_html5.html
You'll only see the files above when you publish courses with both HTML5 and Flash formats.
11 Replies
So basically the flash version is the best and the others are alternates if that doesn't work right, yeah?
Hi Bruce! Your course will intuitively play the best version based on the browser folks are using to take your course. The requirements for viewing courses is here in our system requirements article.
More and more, as people are using mobile devices for their e-learning, course authors want to create the best experience for their learners. This article describes publishing your courses for mobile devices.
And as far as the resolution hit, while we are focused on ever-improving our HTML5 output, you can read more about that issue here.
Which link is best to share the story_html5 link or the story.html link? We are posting our content as continuing medical education and people may be viewing our content from different types of devices, OS and browsers.
Do people ever share both links so people can choose which one will be best for them?
Thank you,
Carolyn
Hi Carolyn!
We recommend sharing the story.html file. I'm attaching our documentation below that helps explain why.
Storyline 2 lets you publish courses for Flash, HTML5, and the Articulate Mobile Player app. To distribute your published content, upload it to your web server or LMS, then link to the story.html file in the published output. Here’s how Storyline determines which version of your content to display when learners view it.
In storyline 2 we have to use html 5. I am wondering what is the difference between story_html5.html" and "index_lms_html5.html". I know normally you link the index page and that is the default, but it was suggested to me that story_htm5 would allow it to work smoother. Is this true?
Hi Amy,
I will defer to the community on that question on best practices and experience, since it is not our recommendation.
Is that suggestion based on your particular LMS perhaps? Are you having a particular issue that you are expecting to work better?
Good morning. I'm publishing for LMS and in my Storyline output folder, there is:
I believe that we would link the LMS to the index_lms.html file for LMS courses. My question is why are "story.html" and "story_html5.html" included in an LMS publish, since apparently they are not used when importing a course into an LMS?
Please straighten me out. Thanks for any info you can provide.
Hi there, Paul. The story.html files are included as an option for folks who don't need to track their content but still wish to host it in the LMS.
Let me know if you're having any issues hosting your LMS output!
Hi,
I have published and the folder is created. However, the folder only has the following: html5, mobile, story_content --> folders and analytics-frame, meta, story --> files. I am referring to a course which asks me to make changes to the story_html5.html which is missing. Mozilla Browser and Windows 7 SP2 is the configuration. What is going wrong here?
Hi Gita,
I responded to a similar inquiry here.
For anyone following along, we simplified the published output in Storyline 360 builds 3.35.20995.0 and later. When you publish HTML5-only or Flash-only courses, Storyline no longer generates the following files in your published output:
You'll only see the files above when you publish courses with both HTML5 and Flash formats.
Thanks a bunch Leslie..let me find a go around for this,
Regards,
Gita G