The translation step between storyboard and Rise
Hi everyone, I wanted to share an idea and sanity-check something with this community. One friction point I keep running into in Rise isn’t design or content creation, it’s the time it takes to "translate" an approved storyboard into a build that still makes instructional sense. Not rewriting anything. Not rethinking the learning. Just deciding how each piece of an already-approved storyboard should actually live in Rise. Which block type fits best? What order supports the learning objectives? What needs to be split, grouped, or signposted so the experience still works for learners? That translation step is where I see a lot of hours disappear. It’s also where instructional intent can quietly drift, simply because there are so many small judgment calls to make along the way. Lately I’ve been thinking about how that step could be faster and more consistent, without turning it into a push-button conversion or removing instructional judgment. I’ve seen a few options popping up, but they don’t really consider the instructional angle, or the pros and cons of different Rise block types from a learning perspective. I’m curious: How much time do you typically spend translating storyboards into Rise? Where do you feel the most drag or rework? What parts of that step feel most repetitive or manual? I’m pressure-testing a concept around this (while keeping instructional intent intact) and would love to exchange perspectives with anyone who’s felt this friction too. Thanks.Give triggers names to help remember what they are for
Hi, Ever wondered what a trigger was for? I have a few in a project that are JS triggers and I can never remember which is which if I want to copy and paste to another slide. We need the ability to add a name or a description to a trigger. The name can be added in the Triggers panel when creating it. Perhaps the name/description can be hidden in an icon in the triggers side panel so to not take up room, but if you roll over it the name/description appears? I created a quick example to help get my idea across. Thanks for your consideration! RussSpecify an object's end with a time or cue point
Currently, there doesn't seem to be a way to align an object's end point to a certain time or cue point. I see align object to playhead, align playhead to object start, and align playhead to object end. I would like to see align object end to playhead to cue point Thanks! Maurice OliverEnhancing Review 360 Feedback Management with Categorization Tags
Currently, in Review 360, feedback and comments provided during reviews are captured in a generic format without any structured categorization. This often leads to ambiguity when interpreting feedback, as reviewers and developers must manually infer whether a comment refers to an error, an enhancement suggestion, or a query. The lack of classification makes prioritization and resolution time-consuming, especially when handling large volumes of feedback across multiple stakeholders. Post-implementation of the proposed feature—a dropdown selection allowing users to tag feedback as Error, Enhancement, Query or Not applicable—the process becomes significantly more streamlined. Categorization at the point of entry ensures clarity, enabling teams to filter and sort feedback based on type, prioritize critical issues, and allocate resources effectively. This structured approach not only improves communication between reviewers and developers but also accelerates decision-making and enhances overall productivity by reducing misinterpretation and manual effort. This categorization should also be reflected in the generated reports.WEBM Encoding in the background
Hi all, some nice new features and fixes implemented today. Regarding adding MP4 videos, I think it'd be helpful for users to be aware from this page that the WEBM encoding process happening in the background will prevent editing of that video in Storyline until the encoding process is complete; and that users can track the encoding progress by clicking the new (?) Processing button at the bottom right of their Status bar.Ability to make text elements selectable
Allow storyline course developers choose if users can select text on specific elements, i.e., When in the "Format Shape" dialog, on the "Text Box" tab, if there could be a simple Radio button for "Selectable Text". With this switched on, users could select the text on screen to perform a copy paste, they could then use their assistive technology to read out the selection. Would be also good if there was a global setting that simply made any and all text elements in the course have "Selectable Text", i.e., switch the "Selectable Text" radio button on for all text elements in a course. Finally, this request stems from a user’s inability to use Mac VoiceOver in Safari (or any browser for that matter) to Select the Text in a course and have it read aloud to them. It is possibly for Mac VoiceOver to access the text elements via key commands (however, very clunky compared with other screen readers on the market). Using a screen reader isn’t always done via keyboard commands as this user clearly shows. Some (like this case) prefer to select text on screen and then have it read aloud rather than using key commands to navigate the Storyline screens. Accessibility requirement.Auto Play Audio
It has been mentioned a few times but I think this is a bigger issue than the developers realize. I am the lead on a major project and we are converting all of our safety training videos and on the job training courses through Rise 360. We have over 300 employees in our facility and well over 50% are English as a second language team members. Having an auto play feature in rise 360 is crucial for our success. It ensures that every employee—regardless of reading level or language proficiency—receives the full content of each lesson without missing critical information. Instead of relying on individuals to manually activate audio or navigate complex menus, the Auto Play function would deliver a consistent and accessible learning experience for everyone. This not only improves comprehension for our ESL team members but also reduces confusion, minimizes repeated training sessions, and ensures that all safety messages are communicated clearly and effectively. I really hope the developers come up with something soon, as I see this has been the concern of many since the start.
