UPDATE: New version of demo to accommodate Articulate’s altered way of treating lesson IDs.
First, take a look at this “fake branching” demo. The story is somewhat whimsical and it “feels like” it’s personal, as it provides choices and responses. In reality, there’s no real branching.
Out-of-the-box, Articulate Rise (at least at this point) does not provide branching. You can, however, add stacked buttons as a choice to make. The problem is that every lesson shows up in the menu, and that kind of kills the thrill of a choose your linear adventure.
Branches are hidden in the menu.
1. Lesson ID (the long text ID from the URL) 2. Branches (lessons to hide that belongs to this scenario. Use comma to separate them) 3. Status. This is the only number you pass: 0 - Not visible, 1 - Visible You need to show the first one at least. 4. Next Branch ID. If you do multiple fake branching, add the next ID here. 5. Previous Branch ID. If this is the first branch, set it to "0" since there's no previous branching. Otherwise, set it to the previous branch ID.
Example: you set up one scenario with three branches and an end page. You check the menu and the ids are the following (I’m using just three letters for ID to make it easier, in real life it’s a long text):
Scenario -> abc
Branch 1 -> vbn
Branch 2 -> nmk
Branch 3 -> rty
End Page -> iop
You would add the following one line (after removing the existing setBranchData lines):
“abc” is the ID of the scenario lesson
“vbn,nmk,rty” are the IDs of the three branches you want to hide
1 is a status to show the scenario (if you had another scenario in the same lesson, you would give a 0 to hide it but the first scenario you want to show)
“iop” is the next lesson ID. Currently, it points to the end page. If you have more than one scenario, it would point to the next one.
0 is the previous scenario as this is the opening one. If you had multiple ones, you would add the previous lesson id here.
TIP: don’t forget to show the developer window in your browser to see if there’s any red errors (Ctr+Shift+I in chrome). It also clears your cache every time you refresh your screen when testing.
Consideration: this can be used for creating an experience rather than actually hiding content. Articulate’s search feature will find the hidden content, so it’s not like your audience would never be able to see it.