Forum Discussion
Publishing to our Intranet (SharePoint)
Hi everyone
I have recently purchased Articulate Storyline (which I love) however I am trying to publish content to our intranet which is a SharePoint site. When I had Articulate Studio, I published using the web option which produced a player.html file which our guys used to upload the content. I have repeated this operation in Articulate Storyline but can't see a player.html file. Am I going mad or is there something different I should be doing in Storyline? Any help anyone can give would be much appreciated.
Thanks
Lorna
Shalla Rogers said:
.Hi all, I'm having the same problem, kinda new to Storyline and was wondering if you can you be more specific when you say 'link the story.html to launch'? I've attempted to load the files to the SharePoint and it either loads the individually or with the zip? Thanks
Maybe this can help:1) Create a document library (name it "Storyline" or something memorable)
2) Open that document library in Windows Explorer view
3) Copy all of the Storyline files and folders from your PC into that document library.
4) Right-click on the story.html file in the document library to get the link
5) On your Sharepoint page, add a new web part, "Page Viewer Web Part". In the tool pane, you paste the link to your story.html file. If you're proficient in HTML, you could also embed the code in a Content Editor Web Part
You're not going mad. Storyline creates a "story.html" file that is used to launch the module instead of a player.html file. Just upload everything like you did with Articulate Studio, i.e. all of the output folders and files into a single SharePoint directory, and link the story.html to launch.
I do not see any player.html generated. Can any say if this was replaced by presentation.html. It doesn't work in sharepoint.
Thanks Leslie and trust me if I encounter any further difficulties I'll be back on this forum!!. Great to know there is such a fantatstic support network I can reach out to.
THANK YOU Brett. MUCH APPRECIATED.
Hi Lorna! Looks like Brett was able to help you out here, just let us know if you need anything further.
Hi Leslie,
This method worked for me on SharePoint Foundation 2010, but my org recently moved to SharePoint Foundation 2013. Now, when I click the link to the story.html file, SharePoint asks me if I want to save the file. Before it just opened the presentation and all ran smoothly. Thoughts?
Glad to hear it
Brett Rockwood said:
You're not going mad. Storyline creates a "story.html" file that is used to launch the module instead of a player.html file. Just upload everything like you did with Articulate Studio, i.e. all of the output folders and files into a single SharePoint directory, and link the story.html to launch.
Hi all, I'm having the same problem, kinda new to Storyline and was wondering if you can you be more specific when you say 'link the story.html to launch'? I've attempted to load the files to the SharePoint and it either loads the individually or with the zip? ThanksHi Shalla and welcome to the community!
If I'm understanding correctly (I don't personally use SharePoint, but I believe the structure for files is similar), you need to upload all of your content to the server and then find the story.html file that's been uploaded. Find the URL for that specific file and share it with others. They should be able to enter that URL into their web browser and access the course using that link.
I'm afraid I'm not able to share any screenshots or walk you through the process for copying/finding the URL - if you're unable to find it, hopefully the original posters here can help :)
Thanks and good luck, Shalla!
Quick thought, just be careful when you're grabbing that URL for the specific story.html file you don't accidentally copy a network drive in the folder address...for example, it should NOT say the first part of the URL is a single letter like Z://. The files may be located on a shared networked drive that you named, "Z", but you need the stand alone URL for it to correctly link, (hope that makes sense).
