Create a Dynamic Menu Slide in Adobe Captivate

Have you ever wanted to add more interactivity to your e-learning course by including a Dynamic Menu Slide with links to sections of your content? You would not normally use this type of navigation for strictly linear e-learning modules.  But if the course module has several content sections and they can be done in any order, a menu slide makes good sense.  

Well in these video tutorials I show you how to do just that with several progressively more complex examples, starting from a bare bones simple example, up to menu slides that include visual feedback to indicate which items a user has interacted with, and finally to a very complex menu slide that is built into the Infosemantics project template that you can download for FREE from this website.

Start with simple examples first!

The first video below explains how to create very simple menu slides that require only interactive objects. Then it moves on to two more complex examples that require custom User Variables and Conditional Advanced Actions. Don't worry if yiou are unfamiliar with these concepts as I explain how everything works from the ground up.  

Watch the first YouTube video below to see how all of this is done!

Taking things to the next level

The Infosemantics template for Adobe Captivate has a built-in Dynamic Menu slide that is far more complex than the simple examples explained in the video above. The next video below builds on the concepts explained above and showcases how to use the dynamic slide from the Infosemantics project template. 

(If you don't already have the Infosemantics template, download links are provided on this earlier blog post.)

If you want to post a comment or question about these video tutorials, you'll need to be logged in as an authorised user of the Infosemantics website.  If you've already purchased any of our products you'll already have a valid login set up.  If you're not a current customer but would still like to post comments, just send me a message on the contact form and I'll set you up with a user account.


Thanks for the tutorial, Rod, especially the information about hiding the play bar and TOC. I often forget that step.

One idea I'd like to add is to be careful of where you put the action to update the completion variable for the subsection. If I have a challenge or knowledge check in the subsection, I update the variable when the user has passed it.

Thanks again for all the information you share with us!


Rod -- You're explanations are crystal clear. Thank you for taking the time to shed light on this useful topic. I'm looking forward to your next installment.

Hello Rod - thank you so much for a very clear tutorial. This is one functionality which is very useful. Good to have these videos and see the face behind the great name. It is very much appreciated.

Hello Rod - thank you so much for a very clear tutorial. This is one functionality which is very useful. Good to have these videos and see the face behind the great name. It is very much appreciated.

Thank you for so generously sharing your template, your Captivate knowledge and creative ideas. Having a copy of your template was critical for me to follow along.
I'd love to put this information to use in a project, but most of the people I've worked with request that each section be a separate Captivate project for two main reasons: to reduce per project file size and to chunk the information because it is not likely that a person would finish all sections in one sitting. In that case it wouldn't be possible to use the Main Menu slide. If you have run into this type of request to split up the sections, I'd be interested in knowing how you handled it.
Looking forward to your future tutorials.

Rod Ward's picture


Perhaps I should clarify here....It sounds like your colleagues are talking about entire Units or Modules within a course.  In which case I would agree with them that it is better to build those modules in separate Captivate project files and then bundle them together into a course using either the Aggregator (if not using an LMS) or the Multi-SCORM Pacakager tool (if using an LMS).

The dynamic menu slides that I am describing in these tutorials are only meant to be used for accessing sections of content WITHIN a single course module or unit.  Those sections would only usually be between one to ten slides in length, which would mean the entire module they belong to would probably be somewhere around 20-100 slides in length..  

In my experience, if your project file has become somewhere between 100-200 slides then it's VERY likely you should be considering breaking it up into smaller projects.  But that decision should rest on the demands of the content, not just on how many slides were involved.

For what it's worth, I try to keep all of my course modules under 10 minutes duration.  I prefer them to be somewhere between 5-7 minutes duration.  Once the modules exceed 10 minutes I always recommend to the client that we should be splitting them up.  But they don't always agree.

Thanks, Rod! I love how a bit of scripting can make a course so much more intuitive and user engaging. Great idea about not deleting the extra objects: no sense in making oneself a mess to deal with later.

Hi Rod, Absolutely brilliant. Thank you so much
Alison McLeavy

Many thanks for this tutorial Rod. I really appreciate all you and Tristan do for the Captivate community.
I'm looking forward to further tutorials on the use of your template, especially the degugging
Regards Mina

Thanks for sharing your knowledge Rod, I love the Template and the Tutorials about the Template!

Just wanted to thank you for these two videos. I am new to Captivate and your wealth of knowledge and clarity in presentation is both inspiring and very helpful. I will be checking back to more learning in the future. Thank again Rod.
Ben Waller


Join more than 2500 other Adobe Captivate users just like yourself and receive regular troubleshooting tips, illustrated tutorials, technical information, and creative solutions to real-world e-learning development issues. (See an example here.) Click the button below to join our community.  It's completely FREE!