My apologies if my question has been asked before. I have tried searching but that seems to come up blank no matter what I type in.
I have a course I am developing in Storyline and would like to take what I have done and hand it off to another designer, how do I send this so he can continue in where I left off?
Also, in regards to the search feature - our team is aware that it's not working as expected and they're working on some updates to our site. In the meantime, you may want to use a site like Articusearch.
That helps somewhat. We are not on the same network so I am not sure how to get the files to them.
1) I need to know what file(s) send the entire project so other developers not on the same network can finish up their part. Do I sent just the name.story file or is there a process to follow.
2) How do I get the file(s) to them. Email may not work due to the file size and I am not able to do FTP and do not have a CD drive or USB drive.
You might want to consider signing up for a dropbox account. This allows you to share / sync files as well as share in a permissions controlled or public environment. The added bonus of a tool like dropbox is versioned backups of your work. I work directly in a Dropbox flagged folder. My work is backed up constantly and I can get to it from anywhere at any time.
The basic account is free and includes a few Gigs of space. They give you free space as well. If you have a Google account you can do similar things with Google Drive.
Or, if you'd like quick and easy, something like https://www.wetransfer.com/ might be just the ticket for delivering a large file or archive of files for free.
I'd also agree with Steve's suggestions for other ways to share files.
Also, if you're sharing with another developer who has Storyline, you'll share the .story file so that they can edit it and update. They'll want to be sure they download the file to their local drive to make and updates or changes.
Are you sending the published output or a .story file for someone else to edit?
I don't use WeTransfer, but if you only need to share the file for editing you'll want to use the .story file. If you need to share the published output, once you publish I would use the Zip option on the Publish Successful Window and then bring that entire folder into the WeTransfer setup.
If it's your web published output you'll need all the contents in that folder in your image. I recorded a quick screen recording on just that piece, and then once you have it zipped that's what you'll share via WeTransfer.
The .story file is only for pre-publishing, if they needed to edit the course. That's also not included in the published output.
If I want to share my .story file with this community to have someone look at what I am doing wrong to try to help me fix things, do I publish to HTML and only share the story file?
You can publish a course for the web, upload the files to any web server, and then give folks the URL to the story.html file. That will let them view the published project.
This method doesn't provide users to enter comments.
This method won't track or save their progress. (Neither does Review 360.) That means they'll have to start from scratch if they exit before finishing.
If you want to track people completing the published course, publish it for an LMS.
When you visit a given web site, its files are "served" to you from software and equipment that is linked to the internet. A link's address (aka universal resource locator, or URL) is based on the domain name. Companies typically have their own domains, such as articulate.com.
Big companies may have their own servers. But a lot of companies get a domain name and access to a web server by paying a company that provides those services. For example: A Small Orange, GoDaddy, etc.
Review 360 is part of Articulate's web server. Storyline and Rise are programmed to be able to publish files directly to that location.
As I said above, if you don't want to use Review 360, you'd have to upload a published course to another server.
I'm sure you can find more details by searching the web. I suggest you start with Wikipedia or TechTerms.com to focus on getting info (rather than sales pitches).
Is there an easier way to share files rather than having to zip the file and share the .story file? I am not the owner of the file, rather, I just need to provide input and help with triggers/course set up.
The story file is the file you work with every day. To find it, open it like usual, using SL. Then go to File and choose Save As. The system will attempt to save the file in its original location, enabling you to find it. You will recognize the name. it will end in .story, which you may or may not see, depending on the settings of your computer.
If it is a project you did not create, you need to get the creator to send it to you.
Publishing it changes it to a form that you cannot change, which is why you need the working file before it is published.
20 Replies
Hi Julie and welcome to Heroes!
You'll want to share the .story file with the other designer, and you can share it via email, on a network drive, etc. but the important factor is that you both download it to your local drive and open, edit it from there as described in this collaborative work flow. Not working off a local drive has been known to cause corruption issues previously.
Also, in regards to the search feature - our team is aware that it's not working as expected and they're working on some updates to our site. In the meantime, you may want to use a site like Articusearch.
Hope that helps!
That helps somewhat. We are not on the same network so I am not sure how to get the files to them.
1) I need to know what file(s) send the entire project so other developers not on the same network can finish up their part. Do I sent just the name.story file or is there a process to follow.
2) How do I get the file(s) to them. Email may not work due to the file size and I am not able to do FTP and do not have a CD drive or USB drive.
Hi Julie,
You might want to consider signing up for a dropbox account. This allows you to share / sync files as well as share in a permissions controlled or public environment. The added bonus of a tool like dropbox is versioned backups of your work. I work directly in a Dropbox flagged folder. My work is backed up constantly and I can get to it from anywhere at any time.
The basic account is free and includes a few Gigs of space. They give you free space as well. If you have a Google account you can do similar things with Google Drive.
Or, if you'd like quick and easy, something like https://www.wetransfer.com/ might be just the ticket for delivering a large file or archive of files for free.
Hi Emily,
I'd also agree with Steve's suggestions for other ways to share files.
Also, if you're sharing with another developer who has Storyline, you'll share the .story file so that they can edit it and update. They'll want to be sure they download the file to their local drive to make and updates or changes.
Is there a step by step video or article for this type of transfer? What should I drag and drop in the WeTransfer platform?
I always seem to forget what to attach and instructions to give to the person I am sending it too.
Any Hero or staff willing to do that for us?
Hi Marie-Pierre,
Are you sending the published output or a .story file for someone else to edit?
I don't use WeTransfer, but if you only need to share the file for editing you'll want to use the .story file. If you need to share the published output, once you publish I would use the Zip option on the Publish Successful Window and then bring that entire folder into the WeTransfer setup.
Hope that helps!
Hi there Ashley, thanks for the reply. I always struggle when it's time to share files.
No not for editing, just a WEB published file.
.story file where is it? In the zip version? in the Storyline output folder?
Is this the one file you are talking about?
Hi Marie-Pierre,
If it's your web published output you'll need all the contents in that folder in your image. I recorded a quick screen recording on just that piece, and then once you have it zipped that's what you'll share via WeTransfer.
The .story file is only for pre-publishing, if they needed to edit the course. That's also not included in the published output.
If I want to share my .story file with this community to have someone look at what I am doing wrong to try to help me fix things, do I publish to HTML and only share the story file?
Hi Lea,
You actually do not need to publish the file at all if you'd like us to take a look at your project.
You can share the .story file that you are working on within the software and directly attach it to your reply.
Is there a way to send a link for your audience to view the completed/published project other than Review360?
You can publish a course for the web, upload the files to any web server, and then give folks the URL to the story.html file. That will let them view the published project.
If you want to track people completing the published course, publish it for an LMS.
Here's more info:
I'm going to show my naiveté and ask - what is a web server? Could you give me an example?
When you visit a given web site, its files are "served" to you from software and equipment that is linked to the internet. A link's address (aka universal resource locator, or URL) is based on the domain name. Companies typically have their own domains, such as articulate.com.
Big companies may have their own servers. But a lot of companies get a domain name and access to a web server by paying a company that provides those services. For example: A Small Orange, GoDaddy, etc.
Review 360 is part of Articulate's web server. Storyline and Rise are programmed to be able to publish files directly to that location.
As I said above, if you don't want to use Review 360, you'd have to upload a published course to another server.
I'm sure you can find more details by searching the web. I suggest you start with Wikipedia or TechTerms.com to focus on getting info (rather than sales pitches).
I have found that wetransfer affects the .story file's Java Script.
Is there an easier way to share files rather than having to zip the file and share the .story file? I am not the owner of the file, rather, I just need to provide input and help with triggers/course set up.
If you just want to look at the project in action, have the owner publish to Review 360.
If you want to actually make changes to it, or read the triggers, you have to have Storyline and the .story file.
How do I get the .story file? Do I have to publish? I read you don't but not seeing what to do if I won't publish.
The story file is the file you work with every day. To find it, open it like usual, using SL. Then go to File and choose Save As. The system will attempt to save the file in its original location, enabling you to find it. You will recognize the name. it will end in .story, which you may or may not see, depending on the settings of your computer.
If it is a project you did not create, you need to get the creator to send it to you.
Publishing it changes it to a form that you cannot change, which is why you need the working file before it is published.