When you publish a .story file, there is a certain amount of compression that occurs no matter what - and it's also driven by the quality settings you choose when publishing.
There aren't any additional methods to compress the file. Is the client having difficulty uploading the published output folder onto their FTP or something else?
It may be due to their overall bandwidth or hosting platform - have you tried uploading it in a few different places to help them determine if there is one element that could be contributing? You may want to check out a few of the free web server options in this article or test on SCORM Cloud which is an industry standard for LMS content.
3 Replies
Hi Derrick and welcome to Heroes,
When you publish a .story file, there is a certain amount of compression that occurs no matter what - and it's also driven by the quality settings you choose when publishing.
There aren't any additional methods to compress the file. Is the client having difficulty uploading the published output folder onto their FTP or something else?
It takes quite awhile for it to upload and for them to download more than anything else.
Hi Derrick,
It may be due to their overall bandwidth or hosting platform - have you tried uploading it in a few different places to help them determine if there is one element that could be contributing? You may want to check out a few of the free web server options in this article or test on SCORM Cloud which is an industry standard for LMS content.
This discussion is closed. You can start a new discussion or contact Articulate Support.