Storyline Standards/Best Practices

One of the things I do with any complicated branching is put it into story view and click on each slide. The blue arrows show where everything will go. I also insert variables rather than typing them out. I used to type them and one tiny spelling mistake would stuff me. Also I use the Storyline correct and incorrect layers - never delete them and create your own. They have lots of unseen automated stuff that comes with them which is hard to recreate perfectly. Change the feedback master instead. Oh and I name everything, layers, graphics, buttons. Then if something is not working it's easy to look at the triggers and see why. Hope this all helps.

Hello Michelle!

You may also want to post this in our Building Better Courses forum for some other suggestions.

This is one I use all the time now if i use javascript I add an alert in javascript on the first slide, this way I know my syntax is right and the code is working and that the reason why it doesnt work is my code.

Also test each javascript code separately rather than add huge chunks and not know which one is broken.  the way storyline loads the code means that any syntax errors will break the whole thing.