Forum Discussion
Bilingual Glossary
I needed to build a glossary for two products that shared similar content - one in English only, and one in both English and Spanish. The glossary contains both English and Spanish terms, cross-linked.
I used Storyline but took design elements from Rise so it would have a consistent look with our other training materials. Everything is contained in a single slide so the scrolling sidebar menu on the main layer remains consistent throughout the experience. Each term is its own layer, and a third lightbox layer shows a zoomed version of the image on click.
I created a custom lightbox so I could show images of different orientations and aspect ratios.
You can see the glossary here:
https://360.articulate.com/review/content/205f45ff-1eec-4c8a-b0a3-fe3672b2dc47/review
(I removed my company's content so the text is from wnyc studios, images from freepix and articulate, and spanish text from google translate.)
.story file is attached
6 Replies
Hey DeidreW! This is an awesome example, I especially appreciate how you went ahead and swapped out company content for lorem ipsum and scratch images so that this can easily be used as a template. You rock.
I went ahead and grabbed a screenshot from your preview link so that this will show up in our examples gallery with an image thumbnail, I find that when posts have an image thumbnail they end up getting more engagement, and this is an awesome example I want to make sure people don't scroll past!
Just curious, since you are working on this translation use case, have you played around with Articulate localization tools at all?We have! We use them regularly. However, with this use case we needed separate content for the bilingual option (referring/linking to different things) not straight translation.
Thank you for sharing the image!This is a super interesting use case, I'm so glad you shared.
Hi!
I downloaded the zip-file, but cant see a .story file?
Is there a way I can use this in my own rise course?Hey VildeAndrea ! I just downloaded the zip for this—you're right, it doesn't look like there's a .story file in this, rather some of the raw assets (images, js etc) that you would need to build this. Perhaps DeidreW can share the .story file so the project can really be opened and tweaked?
As one small point of clarification, this is a Storyline example so a .story file would let you use this as a "template" of sorts in Storyline, but not in Rise. Technically you can (and many do!) embed Storyline slides into Rise to integrate the tools, but it wouldn't be a case where you get the Storyline files and then open them to edit in Rise. However, if you wanted to re-build this in Rise, you could use the storyboard in the zip folder and the assets provided as a reference point!Yes, I would really like the .story file for this. I`m not so experienced in building things myself in storyline yet.
Thank you, I have embedded from storyline to block in rise. So thats what I mean :)
Hopefully he answers and want to share🤞
