Forum Discussion
Landing page change when visiting other modules
Hi All,
I have a landing page which is a welcome to course. It has audio and some entrance animations. The page has 5 icons, all are buttons / hotspots that take users to 5 separate modules / scenes within this course and are basically 5 different subjects.
They go and do the subject they click on, and when they complete it, i want them to return to this page and for it to highlight that they've completed the module they did. I've tried this with states, variables and triggers together but it's not working. Could someone take me through step by step how to do this please? That would be super helpful.
2 Replies
Hello Joel1,
There are multiple ways you could consider this, so asking this question could yield several different but equal steps.
The easiest - "automatic" way would be using the Visited State.
When you say that you have tried this with States . . . are you using the built-in visited State on the buttons? The scenario you described should work with buttons and visited states as long as you are not adding any triggers to change states that could impact the built-in functionality. (The visited state happens on click, so if you need this state to change only after certain slides have been visited, you should consider Variables.)
If you are using HotSpots, they do not have States, so you would need to be a little more creative here.
If you could share your file so we could see what you have started, it would be easier to pinpoint the best solution.
As RonPrice said, you could use a Visited state if you have the user click an object (button, shape, picture, etc.) other than a hotspot.
Any object can be given a Visited state, and it will change to that state automatically as soon as it is clicked. You can also have a trigger run when an object is clicked, so you don't have to put a hotspot on top of an object to make it clickable.
If the user needs to click different parts of an image, instead of hotspots, you could use shapes that have a solid fill set to 100% transparency. That also allows you to track completion via the Visited state.
If there's a possibility that the user could return to the custom menu slide before completing a module they started, you need to use variables to track when a module is done. This post has a demo file and instructions for programming that: TIP: Create a Custom Menu Slide | Articulate - Community
The demo focuses on changing the Next button to Normal after all modules have been visited. The same programming could be use to adjust the menu buttons to a custom "Done" state.
For more info:
