Overloading

Hi Robbie. I can relate to what you are experiencing. I have seen Storyline and Studio become overloaded as projects increase in size. I too love the tool and hesitate to go for web only primarily because of the interactivity I usually require. So as a habit, I compress images and audio as much as I can before importing into Storyline so I start with smaller file sizes. Even though Storyline compresses at publish making smaller sizes at the user end, it can make for bloated production file sizes. I will also split a course into multiple courses and use a central menu. I did this with a large project that contains hundreds of video clips. Just too much to work with in a single Storyline file. Re-booting and flushing out memory often can also speed up previewing as Articulate products tend to consume more memory the longer you are working with them in a single session.

Overall, if your project doesn't require complex interactivity, you might want to consider a WordPress site as galleries and other widgets are easy to add in, design choices are abundant and administration is a breeze.

Stephanie, as a follow-up, I ended up making the whole thing without videos and then putting all the videos in as the final step before publishing.  When I originally had them in, each of them was trimmed for length.  When I brought them back, I didn't trim any of them, I had my wireless turned off, and all other programs were closed and it seemed to go much smoother.  Sure it took a while, but not as long as I thought it would have taken given its earlier pace with only a small portion of the videos included.  I'm not sure which of my methods made the biggest difference but doing all of those things certainly seemed to help.

Thanks for the update on this Robbie! Glad things went smoother for you.