How to share Storyline projects internally with those do not have the software

When I complete a project in storyline, I can only share it internally with co-workers and SME's through the LMS.  I possess only one of 3 licenses for using Storyline. This becomes an issue if changes need to be made, then re-publish, creating another version in LMS for them to view.   

There has to be a better way.  Any help from the community would be helpful.

16 Replies
Glenn Jones

Hi Glen

In the first instance, I would use Articulate Tempshare: http://tempshare.articulate.com/ 

This gives you a link that is active for 10 days, then the course is automatically deleted.  All you do is publish, zip it and drag the zip file on to the box as shown on the page.

Failing that, I've had no problem sharing a published course over something like SharePoint.  You can either upload the zipped version and give them instructions on how to download and view, or uploaded the unzipped version and share the link to the launch html file.

Melanie Sobie

Another thing we've done here is publish to CD and place that published folder on a network group drive that is accessible to all our reviewers. Then you just direct them to the location of the file folder and to click on the exe file to launch the course.

The only drawbacks we've discovered so far:

  • You cannot insert a link to the file path within an email (Outlook). They can launch the course from within the email using the link, but then they cannot play any embedded videos.
  • Resource links (top right side of player) seem to always open up behind the course.

 

Leslie McKerchie

Hi Cheryl!

Does your co-worker have Storyline as well? You mention editing and they will not be able to edit the published file.

When working on an Articulate Storyline project in a collaborative environment with other developers, use the following workflow:

  1. After creating, editing, or publishing a Storyline project on your local hard drive, copy the project file to your network drive for storage and sharing.
  2. When you need to edit or publish the story again, copy it back to your local hard drive.
  3. Edit and publish as necessary.
  4. Repeat steps 1-3.

By working with the project files on your local hard drive, you'll prevent loss of resources, file corruption, and other erratic behavior that can occur due to network latency.

Also, check out this article by Tom Kuhlmann for information and video instructions on using a couple of free applications that'll synchronize your local files with a network drive.

If you truly were asking for a way to share the published output, I invite you to check out this article.