Confidence Based Learning
Last February I attended a breakout session at the TrainingMag conference in Orlando that dealt with Confidence Based Learning. In this concept when a learner is asked a question they provide an answer, but before they find out if the answer they provided war right or wrong, they are asked about the confidence they have in the answer. Here is the breakdown. Right Answer: - High confidence, they are awarded 3 points - Somewhat Confident, they are awarded 2 points - No confidence, they are awarded no points (we do not reward guessing) Incorrect Answer: - High Confidence, we subtract three points from their score - Somewhat Confident, we subtract 2 points - No Confidence, we subtract no points (we do not punish guessing either) I found this intriguing and went to the Articulate Booth on the Expo Floor and asked if there was a Storyline Template that supported this concept. The rep could not find one in any of their libraries. So I decided to make one. The content in this example is not relevant With my military career as a backdrop I was having a little fun. Good Luck all!Big Dreams, Bare Feet – Learning with Tama
It's been awhile since I have been involved with design and development of eLearning, and what better way that to have a bit of fun on a side project to practice some skills and re-familiarize myself with StoryLine again. Inspired by the AI voice Hemi, available in Voices. This interactive module follows Tama, an 11-year-old boy from rural Aotearoa New Zealand, who lives with his Nan, his cheeky little brother Hemi, and a goat named Tina Turner (no relation — unless the original also eats curtains). The eLearning experience is framed through Tama’s eyes, using character-driven storytelling, playful animations, and narrative choice-making to guide learners through a world full of mischief, learning moments, and surprising emotional depth. Link: Articulate Review Note: Only the first two chapters are available at the moment.Immersive Phone Conversation in Storyline
Download this cool (FREE) Phone Conversation template for Storyline; perfect for any scenario with two characters talking. It’s layered with voiceovers, triggers, animations, and clean layouts. It also uses animated APNGs, which look way smoother than jagged GIFs that struggle with transparency. Preview it here: https://www.craftuxd.com/product-page/sellsmart-freebie Check out tutorial here: https://youtu.be/kMpUcYJRNnE?si=jON1XKQtA-4AsIRPGamified Onboarding
Collect the gems by exploring the office! This gamified eLearning was developed for team members to explore their workspace while getting some product knowledge. The process: Conducting a training needs analysis through discussions with leaders Building a learner persona using surveys and polls Planning the desired outcomes Create a fun course Explore the project.Unexpected Encounter Template
I was recently challenged to develop creative eLearning templates where content can be added around a fun adventure, designed to captivate and engage learners. The result is the "Unexpected Encounter", where instructors can seamlessly integrate custom content into an intriguing narrative structure, allowing participants to dive deeper into the material through scenario-based learning. This template follows the journey of Alex, whose routine conclusion to a training workshop unexpectedly shifts into a mysterious experience that he can only resolve by explaining what he just learned in the workshop. The template offers numerous possibilities, from knowledge checks and avatar selection to badge earning and more. You can be as creative as you want! Hopefully it will spark some ideas. To view the template, use this link: Link to Unexpected EncounterAnimated Rise course
In this project we used custom illustrations to bring life to graphics in Articulate Rise. The visuals were inspired by the animated movie "Spider Man Across the Spiderverse". Our challenge: create engagement about a theme considered boring for most of the learners. To do so we limited the usage of texts and paragraphs and used a infographic-like approach. The project contains a mix of Rise microlearning features with animated gifs and Storyline integration. Hope you like it! In the video below you can check the project in action.Popcorn Words Game (sight words)
My 5-year old is learning to read. He was struggling to focus on memorizing a list of sight words (which they call popcorn words). When he could focus, he would memorize the words in order and wasn't recognizing them outside of the context of the list. I created this game to make the learning more fun, and used a bit of Javascript (with help from my computer programmer husband) to randomize the list of words. The Javascript also makes it easier to add in new words each week. I used AI to create all the graphics and the audio, which made the job quicker. And honestly, the little popcorn characters turned out pretty great! Now he's recognizing popcorn words in bedtime stories, signs etc. I would welcome any advice for improvement. For example, I need a way to make the letter sounds come closer to natural letter sounds. (For letter N, "nnn" not "nuh".) You can check out the game on this website. Popcorn Words! 12/16/2024Customizable 3D Model Viewer in Storyline 360 Using Three.js
TLDR A 3D model viewer (GLB/GLTF and OBJ fiel formats) for Storyline 360 using Three.js. See the links below. Please check in the comments for additional updates. Updated (2025-03-08): Minor adjustments to model reloads and resource disposal. Use new project file. Demo: 3D Model Viewer https://360.articulate.com/review/content/87acc80c-2820-4182-b99b-db9e7fd60852/review Demo: 3D Model Display Customizer https://360.articulate.com/review/content/d740f374-c2ac-4ae0-92bc-255b7d35ee1a/review Introduction In my ongoing efforts to better my skills, I’ve been learning more about Three.js, a 3D animation and visualization library for the web. At its simplest, Three displays 3D models in a web browser. This is something that many Storyline users have expressed interest in but alas, it is not directly supported. Storyline actually does incorporate Three.js as its viewer for 360-degree images but otherwise does not include it as a part of its projects. This Project Since displaying graphics with Three is actually fairly easy, it seems like this is something that would have already been done. Since I couldn’t find much regarding integrating Three with Storyline however, I decided to use this as a test bed for my learning experience. As a disclaimer, I am not a programmer, so my code may be inelegant and inefficient in areas. I also know very little about 3D modeling. My design decisions were based upon what I found interesting or potentially useful and may overlook standard practices or some key features that one might expect. Feel free to comment. The Model Viewer I broke this project into two parts. Both are created within Storyline modules. One is a model viewer template that you can use to display two varieties of 3D model files (GL/GLTF and OBJ models). It accommodates a configuration option (list of variables in a trigger) which allows you to customize many aspects of how the model is displayed on your slide. You can include multiple models, each with their own configuration, and switch between them. The size of the model viewer matches the container object on your slide, so it can be sized to your needs. The template module is pretty simple, with a viewer container, some JavaScript, and a handful of triggers and variables. I’ve included the project file for the viewer. You should either be able to adapt it directly or incorporate its parts into your own projects. The Display Customizer The second part is another, more complicated Storyline module. This component can be used to customize how your model is visualized. I linked much of the viewer’s functionality to a collection of Storyline controls, spread across multiple slide layers. Once you have your model setup and adjusted to your liking, you can export a block of JavaScript that represents all of the settings used in the viewer’s configuration options. You will copy and paste this into one of your viewer’s project triggers. Combined with your model files, this enables the 3D viewer to reproduce what you designed for display on your slide. Of course, you can also manually edit the configuration options if you desire, but for anything more than minor edits, this is far easier. Due to its complexity (4000+ lines of script and several hundred variables and triggers), I have not shared the project file. I will, however, leave an active link to the published module that you can use to set up your models. The Details (for anyone who cares) Inspiration for this project came from the following sources: https://threejs.org/docs/ https://threejs-journey.com/ https://github.com/donmccurdy/three-gltf-viewer https://community.articulate.com/discussions/discuss/drag-and-drop-objects-into-storyline/994181 https://github.com/Sphinxxxx/vanilla-picker Model Viewer The viewer module consists of A web object containing your model files and some JavaScript A viewer rectangle on your slide with its accessibility text set to “glb” A few variables A few triggers, including a main JavaScript routine and some configuration options The Web Object We will use a web object to include your model files and the Three.js base code into your project. While Storyline can load a version of Three when needed, it is older and lacks many of the additional resources we need. The script in the web is a custom bundle of the current Three components we need in this project, along the js-beautify library. The functions and classes are made available as global variables under window. Using a static version ensures that everything works together even if Three issues updates that break interactions. You also will include copies of your model resources. The configuration script specifies the base model files for the viewer. Additional files are typically referenced from within the base files. It is easiest if you create a folder for each model, and place all of the related files inside that folder, inside the web object folder. The viewer supports GLB, GLTF, and OBJ models. GLB models are typically one file with everything embedded. GLTF models often have additional texture files associated with it. Preserve any file structure that came with your model (i.e., If your textures are in their own folder, leave them there. If they are at the same level as the model file, leave them there. Also don’t change any of their names. You can rename the GLTF or GLB files and their containing folder, but they must match what is listed in the configuration script. OBJ models usually require several files. Include them all unless you know they are not needed. Final renders and reference images are not normally needed. As with GLB and GLTF, OBJ model files can be renamed but must match the configuration script. There is also an MTL file that should use the same name as the OBJ file (this allows the script to find this file). Don’t rename the texture files unless you know they need to be changed. Note: If you download models from places like CG Trader, Turbo Squid, or Sketchfab then sometimes the textures are separate from the models, or the filenames don’t match what is specified within the GLTF or MTL files. You may have to manually locate and/or rename the texture files. Sometimes you might need to edit the texture specs inside MTL files as well. If you make your own models, then I’ll assume you have what you need. You can also include optional environmental textures, which can provide lighting information and visual backgrounds within the viewer. These are supported as EXR, HDR, JPEG, PNG, and GIF files. If you include these, create a folder inside your main model folder called myEnvMaps and put the required environmental texture files inside this folder. Finally, add an empty text file to the web object folder and rename it to index.html. Once the web object folder is ready, add it to your project in scene 2. Note: Anytime you change the contents of the web object folder, you need to follow ALL of the steps below. Delete the existing web object Insert the new web object (browser to the folder, set to open in new window) Move web object to bottom of timeline list Publish the single slide in scene 2. Click the Load Now button to open the web object page Copy the portion of the URL text matching story_content/WebObjects/[random characters]/ Make sure to include the trailing “/” Paste this value into the dataFolder variable The Viewer Rectangle Create a rectangle. Fill and outline don’t matter, as it will be removed when published. Right-click on the shape’s timeline entry, select accessibility, and edit the text to read glb. You can change this value in the tagViewerContainer variable. This rectangle can be any size or shape and placed wherever on the slide. Variables and Triggers Make sure all of the variables listed in the viewer template project are included in your project. There is one trigger on the slide master. It loads the JavaScript for Three (from the web object). On the base slide, there is one trigger for the main JavaScript viewer routine. For each model you wish to display, there is one additional JavaScript trigger that sets the configuration options. You can generate new text for these triggers using the display customization module. Display Customizer The viewer has many options. Most are built into the Three objects used to display the model. A few are specific to this viewer implementation. You can manually edit the configuration trigger for each model if desired, changing values to fine tune your viewer. For large scale changes or initial setup, you might want to use the display customizer module (linked above). Loading Models The interface consists of a viewport on the left and various controls on the right. To load a model, you can drag and drop one or more files or a folder onto the viewport (or drop new files later to change models). The viewer will try to find and load the model and all of it associated textures and environment files. Dropping the files is convenient as an interface, but it requires extra processing to access the files. Since some of the model files can be large, it might take several seconds before everything gets loaded. Also keep in mind that all of the processing is done in the browser on your computer. If your machine is not very robust, then processing times may be longer. If in doubt, open and watch the browser’s inspector panel console to see if there are errors related to loading the files; especially when trying to load new models. Sometimes you don’t have all the files you need or they’re in the wrong folder. You will see what files the viewer is looking for, and if they are found. If unexpected problems occur, try reloading the browser window. Feel free to comment here if you discover recurrent error conditions. Base settings The base settings panel provides the main interface. You can see and control key aspects of lighting, as well as environmental, animation, and shadow conditions. You can also adjust the viewport aspect ratio in case you need something that is not square. Lighting Unless you set up an environment to provide illumination, you will need some lights to see your model. There are four types of lighting available. Ambient is equivalent to overhead sunlight. The other three types offer up to four light sources each. The controls show the colors. The corners control specific features (see the Help button for details). Right click on each square to get additional options. Each light type has its own options. There is a color picker to set your desired color. Making changes will be immediately visible in the viewport. If you can’t see a change, you may need to adjust the intensity or the positioning of the light. There is an option for a helper, which is a visual representation of the light shape and position. Turn this on to help you set up the lights. Syncing Lights Since the viewer offers the ability to orbit the camera around your model, lighting usually remains static in relation to your model (i.e., the model and lights appear to rotate together in the viewer). A custom feature in this implementation is the ability to sync your lights to the camera so they also move around your model, creating interesting effects. This can be enabled for each individual light, in two different sync styles. Lights may be made relative to the camera position, so they appear to remain in one place in 3D space. They may also be synced in the direction of the camera, at a fixed distance. This is similar to having a flashlight trained on your model as you view it. You can also specify whether each light will generate shadows. This can add realism to your displays. Shadows require significant processing, so use them sparingly to prevent laggy performance. Other Settings Other settings, including rotation direction and speed, environment controls, intensities, and animations are available. Animations seem to work with GLB/GLTF models. OBJ models do not support animation directly. Try out the various controls on your model to see the effects. Export Settings When you have set up your model as desired, you can use the Loader Settings button to export a copy of the current settings snapshot. These include the model filenames and camera positions (like a snapshot). Make sure things are in the position that you want them to start before you click the button. You will see a long list of settings that can be highlighted and copied. This will get pasted into the options trigger in the Model Viewer module. See the triggers attached to the example buttons in the demo file. You can also load and save copies of settings as session data in your browser. This could be useful if you have commonly used settings you want to reuse, or if you want to pick up where you left off on the previous day. Note, these are local to your machine and browser. They will not be available elsewhere. You can also Apply the loaded or the default settings to the current model if desired. The Defaults when Drop Loading checkbox indicates if newly dropped model files will use the current settings or the default start-up settings, in case you prefer one over the other. Technical Notes (thanks for reading this far) Loading Files The Model Viewer uses physical model files included with your published project. This increases your project size but improves the loading speed of the models on the slide. The Display Customizer uses a file drop mechanism to make it easier to switch between random models. This works by parsing through the files or folders dropped and converting them into URL blobs. The blobs act like internal web addresses pointing to each of your files. Large files, especially environment textures or complex models, may take a bit to fully process and load (the Burger model for example). When you utilize the Model viewer for your final product, performance should be better since you only need a single set of files, and they are included locally. You could potentially modify the Viewer script to allow for loading from external URLs rather than local files, but I have not done that yet. Environments Environment textures are 360-degree images, similar to what you use in Storyline. The format can be EXR, HDR, JPEG, PNG, or GIF. This only supports equirectangular, 2:1 images. EXR and HDR files tend to be very large, so keep that in mind. When using an environment Three infers lighting information from the selected image, making external lights unnecessary. If you want to use additional lights, you will need to lower the Environment Intensity setting so the lights don’t get washed out. The environment does not need to be visible to have an effect. If you want it visualized, then the image will replace the background color. Since the focus is really on your model, it is normal for the environment background to be somewhat blurred. Using low resolution images as textures will make this much more pronounced. If you wanted to have crisp images in the background, I believe you would need to modify the script to project the image onto a sphere instead, as you would when displaying 360-degree images (maybe I’ll add this later). OBJ Models My understanding is limited, but environments don’t project properly (or at all) onto imported OBJ models. You can display them, but they provide no lighting effects. Supposedly you can apply the environment textures to the meshes within the model, but I couldn’t get that to work. My approach, awkward but I like the outcome, is to replace all of the meshes in the loaded OBJ model with new meshes, apply the existing settings, and make some adjustments to shine and gloss settings on the fly. This results in a final model that responds to your environment lighting. I found that the test models I downloaded all seemed to come out super glossy. I added a few simple steps to calculate relative gloss levels between the model components and applied an overall adjustment to set it to a reasonable level. I was happy with the test results. Your mileage may vary. If your OBJ models don’t come out as you expected, you may need to adjust the MTL file to fine tune the output. I’ve also found that many OBJ model files (the MTL in particular) contain erroneous paths or incorrect textures assigned to material properties. If your model looks all white, black, grey or some odd color, check the MTL file (it’s plain text) and verify the data. Fix any broken paths, check to see if textures are supposed to be in their own directory, and make sure the correct textures are assigned. Particularly the lines starting with “map_”. These assign the texture images to material properties. Look at the actual texture images, the MTL file, and the Wavefront reference linked below. Play around with different settings to see if you can get it to look like it’s supposed to. See this link for more information: https://en.wikipedia.org/wiki/Wavefront_.obj_file. Lastly, the OBJ models don’t support animations like GLB/GLTF models. Even if your source says the model is animated, that may only apply to other model formats. You may be able to convert another animated version to a GLB format online, or by using Blender. Performance Remember that JavaScript runs on the user’s machine. Everything that Three and this viewer script does happens locally. Don’t overburden your model viewer with an abundance of processing requirements if you don’t think the end users’ machine can handle it. Light syncing and shadow display require extra processing. If you use them, do so sparingly to make an impactful point. Not every light needs a shadow to look realistic. Also, only include the files that are really needed in the final product. Extra environment textures just take up room and slow down website loading times. Excessively high-resolution images do the same and may not be needed. Downloaded models may include extraneous files unrelated to display needs. If you’re not sure they are needed, try removing them and see if everything still works. Only include those that are required. Customization There is a Storyline variable in the project called viewer. This holds a reference to the model viewer. Many of the settings seen in the Display Customizer can be accessed and modified using this variable. If you desire, you could add your own script that loads this viewer object and allows you to directly change settings. Things like turning lights on or off, changing colors, changing positions, starting or stopping rotation or animation, and moving the camera are all easily modifiable, giving you extra control on how your model behaves. You will need to reference the configuration settings script, the main viewer JavaScript trigger, and the Three documentation website (linked above) to understand the possibilities. Limitations There are a lot of moving parts in this project (quite literally with the 3D models). The Display Customizer module is quite complicated, and building something like this inside Storyline is not recommended for the faint of heart. It required 4 weeks, on and off, from concept to this beta version. There are undoubtedly logic errors and code conflicts that I have not discovered yet. This project is provided as is, with no guarantees. If you experience an issue, post a comment. I will look into it eventually and fix it if I can. I may post updates if I fix bugs or add any features. The models included as examples were all available for free from the CG Trader, Turbo Squid, or Sketchfab websites. You can download others or use your own. I could not get FBX models to work properly and lost interest in them. THREE seems to work best with GLB/GLTF models. I like the OBJ models as well since they are easy to manually examine and modify. Additional FIles Web object used in project file (holds Three.js and the example models. https://paedagogus.org/3DModelViewer/Web_Object.zip Additional sample models to experiment with. https://paedagogus.org/3DModelViewer/Other_Sample_Models.zipPortfolio
Make the Moment This eLearning course was developed using Storyline 360 with a focus on interactive learning and accessibility. Key Features: Markers (Hotspots): Learners are guided through the basics of place setting using interactive hotspots. Drag-and-Drop Interaction: Learners actively engage by creating a formal table setting, reinforcing their understanding of the material. Guest-Employee Dialogues: Realistic conversations simulate on-the-job interactions, helping learners practice communication and decision-making skills. Accessibility Considerations: The course was designed with accessibility in mind, adhering to 508 compliance standards to ensure it’s accessible for all users. While I considered audio elements, I opted for a text-based course for better accessibility, with future plans to offer optional audio narration for a more flexible learning experience. Gamification and Storytelling: I implemented a badge system to reward learners, driving engagement throughout the course. Storytelling techniques were also incorporated through a relatable scenario, featuring a niece and aunt on a wedding day, to deepen emotional connection and contextual understanding. View the "Make the Moment" eLearning Course Acing Your Internship Interview This Storyline 360 course helps learners master the STAR method for interview success, utilizing interactive features to build skills progressively. Key Features: Drag-and-Drop Interactions: Learners start by identifying key story parts and work up to creating their own stories with feedback, applying the STAR method. Branching Scenarios: Tailored learning paths cater to specific career interests, enhancing relevance and engagement. The course combines interactive storytelling with practical skill-building to prepare learners for real-world interviews. View the "Acing Your Internship Interview" eLearning Course Luminex xMAP® Technology Overview I took full ownership of this explainer video, handling everything from start to finish—scriptwriting, graphic design, animation, and narration—using a variety of tools to bring the concept to life. Project Scope: Scriptwriting and Narration: I developed a clear, engaging script that simplifies the technology for a lay audience and recorded the narration. Graphic Design and Animation: I created all visuals using Microsoft PowerPoint, Photoshop, and After Effects. The animations were designed to visually complement the content and ensure a seamless learning experience. Collaboration with SMEs: Partnered with subject matter experts to ensure the content accurately represents the technology, making it both technically sound and accessible. Accessibility Considerations: The video was designed with 508 compliance in mind, ensuring that all content—including visuals, captions, and audio—meets accessibility standards. Features such as descriptive text, closed captions, and appropriate color contrast were incorporated to make the video accessible to all users. Watch the Luminex xMAP Technology Overview VideoInteractive video (award-winning project)
This project was designed to engage salespeople in using proper sales techniques and technical inspection skills. Check the demonstration. We employed an interactive first-person video approach. Instead of prioritizing clicks, we focused on a web series format, similar to Netflix episodes. To enhance realism, we simulated interactions with customers and products, and the use of video allowed us to showcase details of tools, environments, materials, and even appropriate body language. At the end, rather than completing a linear course, students will have tested their decisions and learned from successes and mistakes in a safe digital environment, enabling them to repeat the experience and make different choices while comparing the consequences of each action. The making of In this tutorial I explain my production process. Thank you!
