.STORY template

If you're starting your project from scratch, you can download the .story file from Github by clicking on the button below.

.STORY Template file

As the Nuggets integration process has not changed, the template file is offered as is: structure and triggers are ready to use.

However, the version of Nuggets may not be recent. Make sure you always have the latest version of the library. For more informations, refer to the section "Update Nuggets".

Structure of the source file

To keep the source file clean in which Nuggets is implemented, scenes and slides are structured as follows:

Scene and slides reserved

• An entire scene named Nuggets reserved for the library in which is locate
  • A slide containing ^{1. 2.}
    • the library as a Web Object and
    • several triggers, one of which executes JavaScript code. ^3.

1. The slide is named by the version number of the current library.
   
2. A Nuggets loader Slide Master is applied.
   
3. The JS trigger is called Main initialization trigger in Nuggets terminology.
   This is where 95% of Nuggets functionality is set up.

Dedicated variables

There are two Boolean variables in the source file: nuggetsLoaded and isOnline.

• nuggetsLoaded is reserved for loading the library and will be used in your triggers to ensure that the library is present..

• isOnline is used to enable/disable loading of the Nuggets library for testing and execution respectively, either in a browser or in Storyline's preview interface.

Storyline Trigger

When the timeline starts on 'this slide'
- Execute 'JavaScript'
    If 'isOnline' = value 'True'
        and 'nuggetsLoaded' = value 'False'

Scene and slides "project

All the other scenes, including the start-up scene, and all the slides in them, will make up your project. Make sure that all the slides have the layout that makes it possible to check for the presence of Nuggets in the player.