How to Put Glossaries into a Responsive Project - Any Interesting Ideas/Best Practices

Will the glossary only be used to read something? Another approach that avoids a lot of navigation (which can be slow on not so powerful mobile devices) is to have that glossary ready in a 'popup' shape that you create on the first slide and time for the rest of the project, always on top. It can also be a group instead of a shape. Hide that popup initially either by changing its property 'Visible in Output' or by hiding it with the On Enter action of that same first slide. On the main master slide you create a shape button that can show the glossary, which will be visible on each slide that uses the objects of the main master slide. That is the case for most master slides with the exception of the Title master slide in some themes. (you can add the same shape button there). I would propose to use a hyperlink character (mostly I use a bit X) in the popup, to close the popup. Have a look at:

More is in a...hyperlink - Close button - Captivate blog

If you prefer a toggle shape button to open/close the glossary, you better have it also on the first slide, timed for the rest of the project because you'll need an ID for that button to be able to change its state. More info in this article:

1 action = 5 Toggle Buttons - Captivate blog

Forgot to add that you'll have to format the popup and its content for all breakpoint views.

I usually create a button on my first slide that displays for rest of project. That button will link to the glossary page. The glossary page will only have a single return to the previous slide for navigation and the glossary page resides outside the navigational path of the rest of the course (after the quiz results slide for example). If users don't need the glossary they never see it, however, it's available at all times throughout the course.