Forum Discussion
Glossary In Articulate Rise?
I work on some pretty technical pieces and I'd love to see an interactive glossary feature in Rise so a user can click or hover on a word and a description of the term/ concept comes up. I know we can do this in SL, and can obviously put this in as interactions, but it would be so useful for us to have this as a standard feature!
Has anyone created this or something similar?
Currently, we use accordions, downloadable glossaries, carouse swipe type features- but it means the user must go into a separate block or lesson to access them. Personally, I find it breaks my learning and train of thought- so I assume it would do for my learners too!
Ideas on how to better do this would be greatly appreciated!
3 Replies
That’s a great callout, VivBrown, and I can see why this would be especially useful for more technical content.
I also appreciate HoneyTurner sharing those examples. Those are creative ways to handle similar needs in Storyline, especially with tooltips and lightboxes, though I understand that doesn’t quite translate to the same in-context experience you’re looking for in Rise.
Right now, there isn’t a built-in way in Rise 360 to display inline glossary definitions (like hover or click-to-reveal text) directly within a lesson. As you mentioned, the available options tend to rely on separate blocks or resources, which can interrupt the learning flow.
Your use case around keeping learners in context without breaking their train of thought makes a lot of sense, especially when dealing with dense or unfamiliar terminology. I’ve included both your and Honey’s use cases when sharing this with our product team so they have a fuller picture of how this could be used.
2 of my projects have included a component with similarities to this.
- I had a project with a lot of math and complex ideas.
- I used hover tips throughout the project to breakdown the math into samples or simpler terms. My content was primarily video, so I created hotspots, but you could use whatever is the best choice for your project.
- I created a Tooltip layer that had each tip in a different state.
- This is the choice I'd use if I wanted to point to a word on the screen and have the info available only while on that screen.
- I had another project where we were teaching keyboard shortcuts and how to navigate their software. Lots of memory work.
- This one I made a full reference guide that I displayed in a lightbox.
- It was context sensitive, using variables; so it knew if you'd opened the guide before and what progress you'd made through the course. It opened to the most relevant content, but allowed for exploration of all topics previously covered and disabled any content that was not yet taught.
- This is the choice I'd use if I wanted to have a help button in the same location on each page, that gave all the terms on the page. Especially if I wanted to be able to provide an alternate view with the full glossary.
In both cases, I introduced learners to the help tool before they needed it so they felt confident before becoming overwhelmed or confused.
And I just realized that you mentioned SL, but were looking for an answer in Rise. I'm still on my first Rise project, so I haven't ventured into custom content and don't know how far that can take you. I guess I'll be watching along with you.
- I had a project with a lot of math and complex ideas.
