So, today I’m talking about the session I gave at DevLearn 2016. It was my first Bring Your Own Laptop (BYOL) session, and there were a few hiccups, but I would definitely revise the delivery and give it again! In this session, I showed participants how to use variables in Articulate Storyline to create a closed captioning effect, and to create a very basic progress meter.
Closed Captioning Effect
The technique for this effect was first shown to me by Nancy Woinoski at an Articulate Community Roadshow in Toronto a few years ago. I liked the clean effect, and thought it would be a great one to share with the greater commonwealth of e-learning developers! There are many other ways that you can create this sort of effect, and perhaps one day, you will no longer need a workaround for closed captioning in Storyline (pleeeeease, Articulate?!). Until then, we have workarounds. David Lindeberg actually drafted a great post on how he approaches closed captioning in Storyline – you can read it here.
Download this Participant File, and this Completed File. You can use the participant file to walkthrough the steps with me, and you can use the completed file to reverse engineer the programming and figure it out on your own!
Here’s the video walkthrough:
Next, I showed participants how to create a very simple progress meter to track learner progress through a course. I can’t remember exactly where I saw this method, but I know it was via Articulate, and it was a long time ago (I think it was in Storyline 1). If you know which post I’m referencing, please link it in the comments below, because I scoured the community but I’m coming up short and would love to provide attribution.
After running into David Anderson on my coffee run the morning of my session, I was told doing both closed captioning and progress meters was ambitious for a 1-hour session, so I was a bit nervous, but I think this example is easy enough that most folks were able to follow along.