e-learning development
1852 Topics20+ Examples of Meet the Team Interactions
View the examples If you’re looking for fresh ideas for introducing your team in an onboarding course (or any e-learning project), you should check out the examples from a recent e-learning challenge. Community members shared 23 different approaches to this common interaction so you’ll find lots of inspiration for visual and interactive design. You’ll even find some free downloads folks shared. Huge thanks to everyone who shared their examples, downloads, and feedback in the challenge: Jayashree_Ravi, JodiSansone, Jonathan_Hill, AutumnWright-77, larryvanwave-ff, Montsea, OwenHolt, SyedAmjad-Ali, AsweniGD , BrilliantTeams , Kate_Golomshtok , David_LeFevre , GolfPrincess , Soumya_Puli_95 , EQ23 , Charlottie , BethanyMavro59819Views0likes0CommentsError while uploading SCORM file with translation to the LMS
I translated a course into 3 other languages using Storyline360. While uploading the translated SCORM files to the LMS, I am encountering an error with the error codes 43073 and 43269. It is a single file with 3 different languages. I used the same file and exported each language separately. The course has unique LMS Course Information identifier. Has anyone encountered this issue before? I have raised a case with Articulate and waiting for a response.114Views0likes2CommentsFreeze a block?
We are creating a RISE with a lot of content and the client does not want to use the menu as it appears on the side. They want the title of each section to remain at the top of the screen as you scroll down (kind of like you freeze the top row of an Excel spreadsheet). Has anyone found a way to make this work?33Views0likes1CommentPart 1: AI Voices in eLearning
➡️ View the post and tutorial 👋Hi everyone! A few of you reached out after the Build-a-Thon submission asking how the audio elements were built — so I put together a full teardown video. This is part 1 of a 3-part series I'm doing on AI coding in Rise and Storyline. Part 1 covers how I added AI audio to the flashcards, configured the settings for different purposes, set up the voice agent in Storyline, and what's possible when you go directly into ElevenLabs. Building the Rise code blocks used in this post are covered in Part 2 — that one's about the Rise Code Block Library. 👉 Part 1 - AI Voices in eLearning 👉 Part 2 - Building Rise Code Blocks 👉 Part 2 - Follow Up: Rise Build System in Action 👉 Part 2 - Follow Up: Protoyping with Intent 👉 Part 3 - AI Javascript in Storyline (coming soon) 👉 Browse the Rise Code Block Library Have fun with this series and let me know if you have any questions. Stephanie444Views2likes3CommentsPart 2: Building Rise Code Blocks
➡️ View the post and tutorial 👋Hi everyone! Part 2 of the series is up — and this one is about how the code blocks in the Rise Code Block Library get built, and how you can do the same. I've developed a workflow system — the Rise Build System — that uses Claude to take you from idea to finished, tested, Rise-compatible code block without needing to know JavaScript or HTML. The tutorial walks through a real build: a row sorting interaction that came directly from the suggestion box in the code library. The full Rise Build System — master prompt, intake prompt, revision prompt and setup instructions is free for all, but I'm asking for your email in exchange so I can keep you updated on new tutorials. You can subscribe over in the post and if you already have, you'll receive an email with the build system. Start with Part 1 if you haven't already Browse the Rise Code Block Library 👉 Enjoy Part 2: From Idea to Interation Here are two additional tutorials related to Part 2: Rise Build System in Action This post demonstrates two more examples of working with the Rise Build System, including revising existing code snippets. Prototyping with Intent This post demonstrates how you can use Claude's visualization feature to rapidly create code widgets, and how Claude Design can make code snippet interfaces look awesome. The final part of this series will drop in a couple of weeks and shifts focus from Rise to Storyline. We’ll look at the new AI JavaScript coding feature, similar to Rise Code Blocks, but different in many ways. I'll also have a follow up for this final part discussing options for organizing your snippets. Have fun with this series and let me know if you have any questions. Stephanie271Views2likes0CommentsPart 2 Follow Up: Rise Build System in Action
➡️ View the post and tutorial 👋Hi everyone! The first follow up from Part 2 of the series is up — and this one demonstrates to examples of using the Rise Build System for a new build and a revision. The first demo walks through building an interactive display cards snippet using the intake and master prompts from the Rise Build System. The second demo shows how to use the Revision Prompt to make 3 changes (that were requested by users of the Rise Code Block Library) to the existing glossary code snippet. The resulting code can be downloaded in the code library. Part 1 - AI Voices in eLearning Part 2 - Building Rise Code Blocks 👉 Part 2 Follow Up: Rise Build System in Action Part 2 Follow Up: Prototyping with Intent Browse the Rise Code Block Library The final part of this series will drop in a couple of weeks and shifts focus from Rise to Storyline. We’ll look at the new AI JavaScript coding feature, similar to Rise Code Blocks, but different in many ways. I'll also have a follow up for this final part discussing options for organizing your snippets. Have fun with this series and let me know if you have any questions. Stephanie126Views3likes1CommentPart 2: Follow Up - Prototype with Intent
➡️ View the post and tutorial 👋Hi everyone! The second follow up from Part 2 of the series is up — and this one demonstrates how you can use Claude's visualization feature to prototype code widgets, and how Claude Design can make code snippet interfaces look awesome. The first uses Claude's visualization feature. Ask it to show you how compound interest works and you get an interactive widget with sliders right in the chat window. Stay in the same chat and convert it to a Rise code block using the Intake and Master prompts. The second uses Claude Design. I built a fire triangle simulator — adjust fuel, oxygen, and heat and watch the ignition threshold respond. That prototype fed into the Rise Build System and came out as a fully compliant code block. The resulting code snippets can be downloaded in the Rise Code Block Library. Part 1 - AI Voices in eLearning Part 2 - Building Rise Code Blocks Part 2 Follow Up: Rise Build System in Action 👉 Part 2 Follow Up: Prototyping with Intent Browse the Rise Code Block Library The final part of this series will drop in a couple of weeks and shifts focus from Rise to Storyline. We’ll look at the new AI JavaScript coding feature, similar to Rise Code Blocks, but different in many ways. I'll also have a follow up for this final part discussing options for organizing your snippets. Have fun with this series and let me know if you have any questions. Stephanie5Views0likes0CommentsIssue with resizing rectangles less than 50px high?
I've never got round to posting this but it's started irritating me now so worth an ask. Is there a setting I've missed that would cause me to struggle very much to resize any rectangle to less than 50px height? It keeps snapping back to 50px. I usually get there after threatening the computer and trying a few times (usually having to type the exact height, but often I don't know the exact height I want as I use it for things like highlighting or covering parts of software screens), but this is very annoying. It has persisted for me over several versions of SL. I'm not on the latest version but I don't update during a long project precisely because strange things happen when we update. Recording of a small amount of my screen included for illustration - you'll notice it snapping back to 50 multiple times.42Views0likes10CommentsRise Quiz Answers Cannot Have Punctuation?
My Exported Rise SCORM 1.2 file hosted on the Docebo eLearning platform fails to be marked as "completed" even though it says 100%. Instead, it stays marked as "In Progress". I am not sure if this is an Articulate or Docebo (my lms) issue, but I narrowed down the problem to the fact that quiz answers cannot have punctuation (commas). If they do, the course never gets marked as completed even though it passes on SCORM Cloud. Anyone experience a similar issue where adding punctuation to quiz answers breaks their exported module? I appreciate any feedback. Thanks! More info below. Example 1 - Fails - Module containing quiz question WITH answers containing commas. - User goes through module, fails/passes quiz, module marked as 100% and exits course, but the exit screen hangs and the LMS marks module as "in progress" Example 2 - Works - Module containing quiz question WITHOUT answers containing commas. - same module - user goes through same process. Exits and the exit screen closes successfully. The module gets correctly marked as "Completed". Looking at the SCORM Cloud log, there seems to be an error in how the system decodes , into --. I think this is where the LMS is hanging, but this can't be an issue right...? Otherwise, someone else must have come across it. Marked Log Page Raw Log Page + [13:46:01.899] LMSSetValue('cmi.interactions.1.id', 'Quiz_What_is_the_correct_order_of_data_transmission._0') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.type', 'choice') returned 'true' in 0 seconds - [13:46:01.899] LMSSetValue('cmi.interactions.1.student_response', 'Transaction-Layer--Data-Link-Layer--Physical-Layer--Application-Layer') returned 'false' in 0 seconds [13:46:01.899] CheckForSetValueError (cmi.interactions.1.student_response, Transaction-Layer--Data-Link-Layer--Physical-Layer--Application-Layer, cmi.interactions.n.student_response, 1, ) [13:46:01.899] Element is: interactions.student_response [13:46:01.899] SCORM ERROR FOUND - Set Error State: 405 - cmi.interactions.n.student_response must be a valid CMIFeedback - value must be consistent with interaction type. Your value is: Transaction-Layer--Data-Link-Layer--Physical-Layer--Application-Layer [13:46:01.899] LMSGetLastError() returned '405' in 0 seconds [13:46:01.899] LMSGetErrorString('405') returned 'Incorrect Data Type' in 0 seconds [13:46:01.899] LMSGetDiagnostic('') returned 'cmi.interactions.n.student_response must be a valid CMIFeedback - value must be consistent with interaction type. Your value is: Transaction-Layer--Data-Link-Layer--Physical-Layer--Application-Layer' in 0 seconds - [13:46:01.899] LMSSetValue('cmi.interactions.1.student_response', 't') returned 'true' in 0 seconds [13:46:01.899] CheckForSetValueError (cmi.interactions.1.student_response, t, cmi.interactions.n.student_response, 1, ) [13:46:01.899] Element is: interactions.student_response [13:46:01.899] Call is error free. [13:46:01.899] StoreValue (cmi.interactions.1.student_response, t, cmi.interactions.n.student_response, 1, ) [13:46:01.899] Element is: interactions.student_response + [13:46:01.899] LMSSetValue('cmi.interactions.1.correct_responses.0.pattern', 'Application-layer--Transaction-Layer--Data-Link-Layer--Physical-Layer') returned 'false' in 0 seconds [13:46:01.899] LMSGetLastError() returned '405' in 0 seconds [13:46:01.899] LMSGetErrorString('405') returned 'Incorrect Data Type' in 0 seconds [13:46:01.899] LMSGetDiagnostic('') returned 'cmi.interactions.n.correct_responses.n.pattern must be a valid CMIFeedback - value must be consistent with interaction type. Your value is: Application-layer--Transaction-Layer--Data-Link-Layer--Physical-Layer' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.correct_responses.0.pattern', 'a') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.result', 'wrong') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.weighting', '1') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.latency', '0000:00:02.0') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.objectives.0.id', '0') returned 'true' in 0 seconds + [13:46:01.899] LMSSetValue('cmi.interactions.1.time', '13:46:01') returned 'true' in 0 seconds + [13:46:01.899] LMSCommit('') returned 'true' in 0 seconds + [13:46:02.007] LMSSetValue('cmi.suspend_data', '{"v":2,"d":35Views0likes2CommentsURGENT: Systematic Memory Leak & DOM Node Explosion - Multiple Projects Affected
Hello Articulate Support & Community, I am reporting a critical, project-breaking performance issue that is now affecting multiple recent modules that causes browser crashes, particularly on mobile devices. This is an urgent matter as our clients are experiencing frequent crashes, particularly on mobile devices, and our production is at a standstill. I have already opened a technical support case (# 01272139) regarding this, but I have not received a resolution yet. I am providing full technical data here to expedite a fix. The Issue: In our latest builds using the most recent version of Storyline 360, we are seeing a massive, uncontrollable accumulation of resources that the engine fails to purge: DOM Nodes: Over 70,000 nodes for a simple 11-slide project. JS Heap Size: Reaches 2.4 GB rapidly, leading to "Out of Memory" crashes. CPU Usage: Constant saturation at 99.4%, even when the slide is idle. Cross-Environment Testing: We have verified that this behavior is NOT related to a specific hosting platform. The same leak occurs across: Articulate Review 360. LMS environments (SCORM 1.2 and 2004). Local standalone web server (No LMS/No SCORM). The Issue: The Storyline runtime appears unable to perform effective Garbage Collection. Even though I am not using complex media, the DOM tree continues to grow indefinitely. It seems the engine is "stacking" every object from previous slides without ever purging them from the browser's memory. Troubleshooting Steps Taken: To isolate the cause, I have stripped the project down to its bare essentials: Slide Master: Completely deleted the Slide Master for testing—the leak persists. Slide/Layer Properties: Every slide and layer is set to "Reset to initial state". Animations/Media: Removed all videos, Move Paths, and Emphasis Effects. New Project: Imported slides into a brand-new .story file—no change. Logic: Replaced Project.Progress with custom JS to reduce CPU overhead. Conclusion: This appears to be a systemic failure in the Modern Player's Garbage Collection mechanism in recent builds. Since this is affecting multiple projects, we suspect a regression in how the engine handles object destruction. I am ready to provide the .story file immediately to any staff member who can investigate this. Our clients are extremely dissatisfied, and we need an urgent technical review. Technical Context: Storyline 360 Version: Latest Build (January 2026). Player: Modern Player. Browser: Chrome, Edge, and Firefox (All show the same 70k node retention). Thank you for your immediate attention to this case.410Views0likes17Comments