Yes, you'll still want to zip the .story file and upload to a server or network drive and advise the other users to download the file and open it locally before working on the file.
Yes, you'll still want to zip the .story file and upload to a server or network drive and advise the other users to download the file and open it locally before working on the file.
Is this still what the software developer suggests 4 years later, or is Storyline now stable enough to have sourcefiles stored on a cloud server and worked on over a network connection, or does it still need to be saved locally and worked on that way?
10 Replies
I generally zip them and share them on a cloud service, like Dropbox. All pics, movies, etc. should carry over with the .story file.
Hi XAn, you don't need to package storyline. You can just share the .story file as is.
Yup. Having it all attached to the .story file certainly makes life easier. I still generally zip it to cut the file size by about 20%.
Yes, zipping is a good idea. The story files can get rather large.
Thanks Nancy & Mathew. Love it when it's easier...
I'm bumping this old post to see if there's any new best practices for sharing files between developers who work remotely.
Is zipping them to a cloud service still the best method?
Thanks!
Hi Laurel,
Yes, you'll still want to zip the .story file and upload to a server or network drive and advise the other users to download the file and open it locally before working on the file.
.story files are already in zip format - no need to zip them again.
Is this still what the software developer suggests 4 years later, or is Storyline now stable enough to have sourcefiles stored on a cloud server and worked on over a network connection, or does it still need to be saved locally and worked on that way?
Hi Joshua,
We still have the same recommendation because we do recommend working locally.
Storyline: Recommended Workflow for Collaborative Network Environments
Storyline: Create, Edit, and Publish Courses on Your Local Hard Drive
This discussion is closed. You can start a new discussion or contact Articulate Support.