Glossary placement in the reading order
Storyline 360: Would it be possible to move the Glossary (please add tech term for that optional static item) down the slide, right before the Prev. and Next buttons? Screen reader users currently have to navigate past the Prev. and Next buttons, and past the Menu button to reach the Glossary. This current placement creates confusion since users may believe they have reached the end of the "exporable" content when they get to the Next button.Export Recordings/Videos as GIFs in Replay
We use GIFs a lot to show navigation and functionality for different products. It would significantly improve the workflow if Replay could export recordings directly into a GIF format. Using other third-party software to convert the MP4 files is time consuming - especially when a lot of GIFs need to be created/updated. This feature could be as simplistic as an "Export GIF" button which prompts the user to crop the video, select a save destination, and then proceed with the export.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.PDF Reader or View PDF via Scrolling Panel
The ask: Could a PDF reader or an addition to the scrolling panel allowing PDFs be added to Storyline's functionality? Our team is required to present manual pages in our lessons, necessitating the use of a scrolling panels. To display manuals or textbook pages that are saved as PDFs in Storyline, you must process the conversion of the PDF in a third-party program. After the conversion, you must import the images and align each page individually in the scrolling panel. The pages must be grouped in a certain way for the scrolling panel to populate correctly. I’ve included a Review 360 link with an example of what the end results looks like: Review 360: PDF Scrolling Panel Example If a PDF reader was included in Storylines toolset, it would make life for designers much easier. Our team is looking for the following features: Allowing PDFs to be imported into Storyline without the need for conversion to JPEG or PNG Automated scrolling for multiple pages. Say the PDF has multiple pages, the user can either flip through the pages or scroll through them. How would it function?: Additional functionality to scrolling panels OR including a built in PDF reader to Storyline's toolset Additional Functionality: Zoom functions Enable PDF bookmarks We appreciate any updates or notice on building this functionality, if possible.Drag & Drop Questions in Rise Knowledge Checks
Hello Articulate: I love being able to add quick knowledge check questions to a rise presentation, but I miss the ability to add a drag and drop question where you have say four items that need to be dragged to only two targets. I know that Rise has matching questions and that Storyline can create a drag and drop learning object, but it would be great if such a question could be added in Rise itself. Please let me know if this is viable. Thanks and regards Alex YoungAuto-Create Captions from Audio Files
I would love if Articulate was able to auto-generate captions using audio files that we record or upload directly, both in Storyline and Rise. I know we can use text-to-speech with AI and generate AI audio, which will include the captions automatically, but if we record our own voices, I would love for it to generate captions without having to do them ourselves. It saves so much time on our end and allows for greater accessibility.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! RussThe 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.
