Best practice for versioning .story files


I am new to Articulate 360 and wondering how your organization is maintaining the revisions to the .store files. I have reservations on making users create a different file with a different name every time they edit it. Similar to how MS-Office files are versioned.

For example:

Tempest In a Hot Tea Cup Production Release 12312016.story

Tempest In a Hot Tea Cup 02152017 KP Edits.story

Tempest In a Hot Tea Cup 02162017 JC Edits.story


One option is to utilize a tool like sharepoint/document management system or version control system etc. Are there better solutions for this?

How are you managing this problem? Please share.

1 Reply
Leslie McKerchie

Hi KP! I cannot wait to see how your fellow Articulate 360 users are handling this.

I did want to share some documentation on what we recommend:

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.