Forum Discussion
Looking for feedback on Course Start Slide
How do you all introduce your courses? What do you communicate before getting into the course itself. Navigation etc. Here is a sample start slide. I'd like feedback on its features and function. I'...
It is helpful to indicate whether or not a course includes audio, since that might require action (e.g., plugging in headphones).
Your other instructions are nicely presented. I think it's good that they're optional. However, they're only available on the first slide. What if someone starts the course, and then realizes they need help?
- It might be better to lightbox a Help slide from a Player tab. That slide could be in a separate scene that isn't included in the menu.
- Or you could jump to a Help slide from a Player tab. Remove the NEXT button from the Slide Properties of the Help slide. In other words, have only the PREV button show. Since that goes to the previous slide, it would return to the slide the user was on when they clicked the Help tab.
- FYI: This post has info about adding custom Player tabs: https://community.articulate.com/discussions/articulate-storyline/tip-create-custom-player-tabs-for-your-resources-glossary-and-more
Re: using the PREV button to close a layer.
- That is possible. For example, you could use a T/F variable to track whether or not the user is on a layer. Then use a condition in the PREV-button trigger so it closes this layer if the variable = True, else it jumps to the previous slide.
- I recommend against doing that. The PREV button has a defined function: jumping to the previous slide. It goes against UI standards to use it for other purposes.
