The Rules feature in Elucidat allows you to customize a learning experience for your audience based on the actions they take within the content, e.g. what pages they have viewed or how they respond to questions.
This feature allows you to configure a tailored experience for your users and make it personal. However, adding rules can add a level of complexity when authoring.
To help you get the most out of this feature and avoid any authoring headaches, here are our top tips for using rules effectively:
1. Map out your rules before building
If you’re planning on adding rules to your learning content it can be helpful to map out the structure on paper first so you have a plan for your project build. This can then be referred back to when testing that everything is set up correctly. Our Conceptualize guide will help you plot out a structure for your learning experience.
2. Use rules only when necessary
There are other ways to hand small content differences for different audiences that might not require rules. Could you use an interaction to break up or nest content for different user groups? Or add additional information for specific users in hotspot callouts?
3. Apply rules to chapters
You can apply a rule to a whole chapter in Elucidat to hide/show a group of pages. This is what you should do when you want to show or hide whole topics for different learners and is more efficient and more manageable than applying individual rules across multiple pages. Watch our webinar that walks through how to do this (from 18 minutes onwards).
4. Check all routes are covered
When introducing rules, ensure all outcomes are covered. For example, if you have results pages that are shown based on the learner’s score, ensure that there is one available for all possible scores.
5. Make time for testing
If you are branching learners off in different directions or down personalized pathways, consider the route they might take if they want to move back through the content. Test your project thoroughly. Take a look at our Masterclass module on How to really QA your project.