Categories
Storyline plugin

Storyline Translation Plugin

We saved one client 83% while developing screen simulations localised in three languages.

Textbook Approach

According to Articulate Storyline, the textbook approach is basically:

  1. Perform a screen recording
  2. Insert step by step slides for View mode
    1. Customise the slide captions
    2. Add information slides and captions
  3. Insert step by step slides as Test mode
    1. Customise the slide captions
    2. Add information slides and captions
  4. Export text for translation
  5. Duplicate course for each language
  6. Import translated text

Our Goal

We challenged ourselves to find a faster way to localise each course. Our goal was to:

  • Eliminate the need to duplicate the Storyline course for each language
  • Enable users to switch between languages within a course
  • Quickly and easily alter caption text without republishing
  • Reduce the number of simulation slides to build and maintain
  • Speed up development to meet short project timeframes between UAT and rollout.

Our Solution

Leveraging the success with our Storyline Screencast Plugin, we created a Storyline Translation Plugin that achieved all our goals and more:

  • Reduced the total number of simulation slides by 83% (from 1,800 to 300).
  • Reduced the number of Storyline files by 66% (from 3 to 1).
  • Reduced maintenance time by potentially 83%. Now, when a screen needs replacing it only needs to be changed in one location rather than 6 (1 x view + 1 x test for 3 x languages)

Elements

The solution comprised the following elements and deliverables:

  • Storyline template
    • Slide Master layouts & triggers
    • Feedback Master layouts & triggers
    • Reuse of common files
    • Minimal and simple triggers on slides
    • Variables
    • Just a few slides, like menu and simulation start, that are localised using layers
  • Screencast Plugin for Storyline
    • The controller for View and Test simulations. Built using custom external JavaScript
  • Translation Plugin for Storyline
    • The controller for presenting text in different languages. Built using custom external JavaScript
  • Language file
    • Caption text for all languages in one easy to edit and maintain JSON file
  • Language validator
    • To ensure language file matches required JSON schema
  • Quick Reference Guide / Translation Export / Storyboard
    • Dynamically generated view of simulation caption text
    • Select language/s to view
    • Download option
    • Link to Storyline simulation
  • User guide
    • Non LMS version of course for refresher training or reference
  • External Resources
    • Sounds
    • Images
  • Windows Batch file
    • To quickly merge external files with published course
Categories
Storyline plugin

Storyline Screencast Plugin

We saved one client 50% while developing elearning for a new touchscreen POS system for 15,000 staff across 4 counties in 1,500 stores.

Walkthrough

Textbook Approach

According to Articulate Storyline, the textbook approach is basically:

  1. Perform a screen recording
  2. Insert step by step slides for View mode
    1. Customise the slide captions
    2. Add information slides and captions
  3. Insert step by step slides as Test mode
    1. Customise the slide captions
    2. Add information slides and captions

Our Goal

We challenged ourselves to find a way to generate Test mode using just the View mode slides using intelligent triggers and external JavaScript. Our goal was to:

  • Reduce the number of simulation slides to build and maintain.
  • Speed up development to meet short project timeframes between UAT and rollout.

Our Solution

Our final solution was brilliant and achieved all our goals:

  • Reduced the total number of simulation slides by 50% (from 2,944 to 1,472).
  • Reduced the number of Storyline files by 50% (from 8 to 4). We found that a Storyline file with around 400 simulation slides was a good manageable size to work with. The total course was therefore spread across four Storyline files.
  • Reduced maintenance time by 50%.

Elements

The solution comprised the following elements:

  • Storyline template
    • Slide Master layouts & triggers
    • Feedback Master layouts & triggers
    • Reuse of common files
    • Minimal and simple triggers on slides
    • Variables
  • Simulation Plugin for Storyline
    • The controller for View and Test simulations. Built using custom external JavaScript
  • External Resources
    • Sounds
    • Images
  • Windows Batch file
    • To quickly merge external files with published course

Categories
Storyline plugin

Storyline Branching Plugin

Features:

  • almost infinite branching combinations
  • preset or user defined paths
  • dynamic menu
  • progress tracking
  • bookmarking

Introduction

For simple courses, creating a branch in Articulate Storyline is fairly easy. You just create a variable or button to allow navigation to the branching slides.

As branching becomes more complex with multiple paths, sequences and combinations, it becomes increasingly difficult in Articulate Storyline to create, test and manage the endless triggers needed.

Our solution is a branching plugin for Articulate Storyline that keeps the triggers to an absolute minimum whilst allowing almost infinite paths.

There is just a single trigger on each branching slide, which you can use to handle when slide is marked as complete (timeline ends/media completes etc).

Story view

The story view is also brilliantly simple, with all slides simply stacked together like playing cards. You can see the slides A-Z are grouped in a single scene. You could also stack the slides in multiple scenes. It doesn’t matter how you group the slides in Storyline, our branching plugin will easily handle any configuration.

Navigation

All the navigation is controlled from the jump slide using our branching plugin. As you can see, there is just one trigger for each slide.

Branching combinations

How many branching paths are possible in this demo course? Too many! For example, if the learner can select any of 26 slides in the demo, the following combinations are possible:

  • selection of 5 slides = 26 x 25 x 24 x 23 x 22 = 7,893,600
  • selection of 10 slides = 26 x 25 x 24 x 23 x 22 x 21 x 20 x 19 x 18 x 17 = 19,275,223,968,000

Wow! And these branching combinations are created using just 26 custom triggers.

Dynamic slide menu

With so many possible branching combinations, there is absolutely no way of creating a slide menu within Storyline. Our branching plugin solves this problem by creating a dynamic slide menu that:

  • marks slides with a tick when complete
  • show progress, which is this example is 38%
  • can be custom styled using css
  • automatically scrolls if there are more menu items than can fit in the visible area

Progress

When all slides are complete, the course will be marked as complete in the LMS.

Usage

We use the branching plugin when client’s want multiple courses built from a pool of topics. Rather than building multiple courses, we build one course with multiple paths. It saves development time, which makes our clients happier.

Elements

The solution includes the following elements:

  • Storyline template
    • Slide Master layouts & triggers
    • Minimal and simple slide triggers
    • Variables
  • Branching Plugin for Storyline
    • The controller for navigation, menu and progress. Built using custom external JavaScript.
  • Windows Batch file
    • To quickly merge plugin with published course