Closed johnpapa closed 3 years ago
@johnpapa Currently, you could create multiple tours and let the user decide which one they want based on title/description. That said, I agree that enabling a "choose your own adventure" experience could be cool as well. I think there's a bunch of work left to do in order to solidify the current "guided path" experience, so I might explore this enhancement later.
Now that CodeTour supports linking tours, and adding links to other tours, I'm going to close this as resolved. In this case, the “tour path” can be defined by breaking up a tour into numerous other tours, and then linking them together.
Beyond that, I think we’ll want to allow better organization of tours, and so we can track that enhancement via #50. Let me know if this doesn't accurately reflect your thoughts here, and we can reopen the issue. Thanks!
Wicked cool feature ideas ... imagine being able to ask the user where they want to go next?
We could provide paths on the tour to do this. Tour contains paths, paths contain steps
So there would be a hierarchy of these. For example ...
I wan to start by showing the
index.html
, then steps in themain.js
, then theApp.svelte
component (in a svelte app). At this point I can ask the user if they want to go to the path for building and running the app in thepackage.json
or the path to see the code in the main components.Paths:
A simpler version of this would be to simply allow grouping of steps into a path, so a set of steps can be visually broken out and rearranged.