Introducing Quick Share: One-Click Publishing for Everyday Learning
We’re excited to share a brand-new way to get your Rise content out into the world: Quick Share! What Is Quick Share? Quick Share lets you publish Rise courses instantly and share them with a simple link, no LMS setup, no logins, no admin delays. You’ll also get light analytics so you can see how many people viewed your course (and, with the Guestbook enabled, who those learners are). It’s all about speed and simplicity, helping learners get the right information at the right time without barriers. When to Use Quick Share Quick Share is perfect for everyday learning content that needs to move fast: Job aids and quick reference materials Presentations or meeting resources Explainer modules and how-tos Operational updates or announcements Pre-boarding and onboarding refreshers It’s also a great way to share examples right here in the E-Learning Heroes community. It’s a fast way to showcase your creativity, get feedback, and inspire fellow creators. If you need deeper, learner-level analytics or advanced group management, that’s where Reach or your LMS comes in. Quick Share can live alongside those tools to give you flexibility. 🎥 Tip Video: Deploy Content Rapidly with Quick Share Community Use Cases We love seeing how community members are already using Quick Share: BradDameron uses it to share preview links and resources across departments. “The Guestbook gives us a general view of engagement — perfect for quick stakeholder visibility,” he shared. JeremyNash uses Quick Share to deliver client-specific training without needing an LMS: “It’s a great step between Preview and Review.” JessicaDecker found it helpful for external partners: “We need to share training with outside vendors who don’t have LMS access. The Guestbook is nice so we can still track who’s taken it.” Try It Out! Quick Share is automatically available for all Articulate 360 creators, no setup required and no extra cost. 💬 Have you tried Quick Share yet? How are you using it? Share your experiences (and any creative use cases) in the comments below!Storyline 360 Pros — What’s Your Favorite “Hidden Gem”? 💎
As someone who’s spent a lot of time working with (and on!) Storyline 360, I’ve come to appreciate the power in the little things — those lesser-known features that quietly make our lives easier. Here's one of my personal favorites: 🎧📽️ Cue Points with the “C” Key: I recently spoke with a customer who struggled to time trigger actions to audio and video media on their slides. They would preview the slide, make note of when a trigger should be fired, then return to slide authoring view to add a cue point to the timeline to tie into the trigger event. This would require a lot of manual back-and-forth between authoring and previewing. I often have to do the same thing, and there is an easier way. If you use stage preview (accessible via the "Play" icon" in the lower-left corner of the Timeline panel), Storyline will stay in the slide authoring view and play the timeline of the slide, including any audio or video media that's present. As it plays, you can press the "C" key on your keyboard to have cue points added to the current playback position. It’s a simple way to place cue points in real time, right where they’re needed — perfect for syncing trigger actions to specific moments in your media. cting Storyline 360's UI and using the "C" key to drop cue points on the timeline. Now I’m curious: What’s your favorite under-the-radar Storyline feature? Something small, subtle, maybe even a little obscure — but that you personally couldn’t live without. Drop it in the comments — I’d love to learn what little gems you rely on. 👇Teaser: Storyline "Chat To Animation"
🚀 Big things are coming to Storyline 360. Last month at the Articuland Summit in Boston, our COO Brian Gil gave a sneak peek at something our team’s been quietly working on: AI-powered animations inside Storyline. We've been calling this feature "chat to animation" internally. The idea is simple but powerful: talk to Storyline's AI Assistant about how you want your slide to animate, and it helps bring your vision to life. The attached video shows a little preview of this feature in a fun "Feline Overlord" themed Storyline course. 🐱👇 On the first slide, I entered this prompt into the AI Assistant chat: “Can you suggest an animation scheme for this slide?” It broke down the suggested animation effects for each object, then asked if I want to create a trigger for them. After responding, "yes", the AI Assistant wrote the JavaScript code to create the animations and automatically associated it with the "When timeline starts" event. It also surfaced a "Preview" button that jumps into Storyline's preview mode so I could see the animation in action. Notice that the AI Assistant window stays visible during preview. This means I can refine the animation while previewing to home in on the exact look and feel I want. In this case, I wanted to delay the slight "pulse" of the yellow next arrow to begin after the image and text animations completed, so I entered: “Great! Can you delay the animation on the next arrow a bit so that it starts after the other objects have animated in?” The AI revised the JavaScript in the trigger and immediately replayed the slide again so I could see the change and tweak further if needed. That ability to preview, refine, and replay instantly is what makes this experience feel so magical. If you'd like to see the published course in action, you can find it on Review 360: Chat To Animation Teaser | Review 360 This feature should land in private beta soon, and we'd love to get your feedback. If you want to help shape how this evolves, email [email protected] to get started!New in Storyline 360: Editing Images with AI Chat
Ever wish you could edit an image without starting over? Now you can! Just describe the changes you want in the chat box and watch your image update. Change the background, adjust clothing or appearance, add a new element, and more. Explore different ideas and variations while your original image stays unchanged. Here are some examples: To build out a scenario, I started with a Content Library image, then changed the actions (talking → drinking coffee → spilling it) to match my story I tried different background settings by generating an image in the chat and changing it until it looked right before inserting on the slide Instead of generating a brand new image, I asked AI to add, edit, and remove specific elements from an image already on my slide Learn more: AI Assistant in Storyline 360: Editing Images with AI Chat As you try the feature, tell us what’s working, what’s not, and what you’d like to see next. Share your feedback in the comments below or take our survey. We’d love to hear from you!Plans for Non-AI Storyline360 Updates?
I was looking through the recent Storyline 360 updates and the feature roadmap, and it feels like most of the new stuff lately is focused on AI features, with not much being added to the core functionality. Are there any plans to keep adding to or improving the standard features in Storyline, or is the main focus going to be AI moving forward? For a lot of us building internal or compliance-based courses, AI just isn’t something we can really use due to protected information. Often many scripts and images are already approved ahead of time, so those features don’t add much value to our process. It’s a little frustrating because there are some existing features that feel outdated and could really benefit from even small improvements, but they seem to be getting less attention.Behind the Scenes: Storyline’s Move to Modern .NET
We just wrapped a project that’s been hanging over Storyline for a long time: Moving from .NET Framework 4.8 to modern .NET (now .NET 10). This one goes deeper than it might sound. Back when Storyline was first built, choosing .NET Framework was the obvious call. This was 2010-ish. Windows dominated our space, and the .NET ecosystem gave us a lot of what we needed to move fast and build a really capable tool. That decision worked. For a long time. It also shaped some of the realities of the product today. Questions about platform support come up a lot, and early architectural choices like this are a big part of that story. They helped us move fast early on, but they also made certain paths more complex later. Fast forward to now… Microsoft has effectively stopped evolving .NET Framework and put their energy into modern .NET. Meanwhile, we were still running on a foundation that wasn’t keeping pace with where things were going. So we made the call to move. This wasn’t a simple upgrade. We relied on parts of .NET Framework that don’t exist anymore. AppDomains. Binary serialization. A handful of “seemed like a great idea at the time” features that modern .NET intentionally left behind. We had to rethink and rebuild some pretty fundamental parts of the product. So what did all of this actually get us? We’re now on a modern, actively supported runtime. It’s easier for us to keep improving performance, adopt new capabilities, and evolve the platform without constantly working around legacy constraints. We also retired some very old pieces of the system along the way, which… felt pretty great 😅 And then there's performance. Microsoft has invested heavily at performance improvements in modern .NET, and we're seeing that surface in Storyline. We ran benchmarks across 18 Storyline projects, measuring open, save, and publish times. Every single project got faster with improvements ranging from 0.4% to nearly 30%. The larger the project, the larger the improvement. In the animated gif below, I put .NET Framework (left) head-to-head with modern .NET publishing the same course. Neither project was pre-published to warm the cache, and I even gave .NET Framework a slight head start by clicking Publish there first. The gif is sped up for easier viewing, but the result is real: modern .NET finishes publishing well before .NET Framework. Big credit to the team that pulled this off. This was deep, risky work in some of the most critical parts of the product. Curious to hear from folks here: If you're on the latest Storyline 360, have you noticed any performance improvements when opening, saving, or publishing your projects?Storyline's Release Cadence
For almost ten years, Storyline 360 has shipped on a pretty steady rhythm: about every four weeks, usually lining up to one update per calendar month. It’s been reliable and predictable… but also a little slow for where we’re headed. So we’re changing that. Starting soon, we’ll be shipping more frequent Storyline 360 updates. Smaller releases, delivered more often, so new features and fixes get into your hands faster. Why the shift? Honestly, it comes down to value and momentum. When the team builds something useful, we don’t want it waiting in a queue for weeks before you can benefit from it. And with the pace of AI innovation across Articulate 360, our release schedule needs to match the speed at which we’re developing new capabilities. We’re also streamlining a lot of the behind-the-scenes work that goes into each release. The goal is simple: making shipping so routine for us so it can be a steady stream of improvements for you. We’ll learn and adjust as we go, but I’m excited about what this unlocks. Faster fixes, faster features, and a faster feedback loop with the talented people who rely on Storyline every day. Looking forward to sharing updates with you… well, more often.
