Hi everyone. I've developed a support tool using Storyline 360 that is going to be hosted on a web server. I've published for web, using the HTML5 output, and the developer who manages the website has asked me whether we can change the 'story.html' file name within the zip file to 'index.html' to make it easier to upload updated zip files in future.
Anyone have any ideas on whether this is doable and how much effort/skill this would require?
The only place where I see that I can change the filename is after it's been zipped. Would it work if I extracted the files, renamed the story.html file to index.html file and then re-zipped the folder?
We have a review tool we are looking at the requires the html be renamed to index.html, that is what made me question the second html file. Thanks for the response!
If you do not want to touch your published content each time, you could ask your developer to just drop a redirect into each main course folder. This is just a shortcut to changing any file names.
What I mean is a file called "index.html" that only has one job; send you to "story.html" automatically. It does this with one single important tag.
I have attached an example that you are free to use. This way you can give it to your developer once, and then they can use it over and over since it never needs to change.
11 Replies
You can certainly change "story.html" to "index.html" but you would have to do that before you zip up the published content.
The only place where I see that I can change the filename is after it's been zipped. Would it work if I extracted the files, renamed the story.html file to index.html file and then re-zipped the folder?
Yes, you can do that. You can also publish (to Web, LMS, etc), change the filename and then manually zip the published content.
Thanks so much for the quick reply!
Does anyone know why it produces the second story.html file when publishing is set to html5 only? legacy code?
Hey Curtis,
Great question and you made me second think it as well.
We've always instructed customers to utilize the story.html file, so while we probably could have removed it, why confuse things?!
No one wants to have to remember what file to point to when they are publishing, so we just let Storyline do the work for us :)
We have a review tool we are looking at the requires the html be renamed to index.html, that is what made me question the second html file. Thanks for the response!
Sounds like another great use for the consistency in the output :)
Glad I was able to help you out, Curtis.
Hi,
If you do not want to touch your published content each time, you could ask your developer to just drop a redirect into each main course folder. This is just a shortcut to changing any file names.
What I mean is a file called "index.html" that only has one job; send you to "story.html" automatically. It does this with one single important tag.
I have attached an example that you are free to use. This way you can give it to your developer once, and then they can use it over and over since it never needs to change.
Just a suggestion. I hope that helps.
Russ
That was one of the solutions I presented here. :) The developer could just drop that file in pre-zip.
Agreed!
This discussion is closed. You can start a new discussion or contact Articulate Support.