-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detailing the Tour functionality #1764
Comments
@vijayee this is great! So we really should just brainstorm, design, and write the tour chapters. we can likely design them in this repo, or in a note at https://github.com/ipfs/notes/ or even in the tour repo you have. Also, we do not have to fit to the original chapters. highly encouraged to branch out and try different things. ideally we would have a flavor storyline, that helps motivate the user. (stories always help go through these things). |
So I guess let's start from the Top. Small attempt at story........ Chapter 1: Hello Mars ipfs init | ./tourguide |
duplicate of #171 ? either one of these issues can probably be closed |
Fair enough. |
https://github.com/vijayee/tourguide
Exists a prototype for the tour. It features the same tour data structure definitions as the internal package with some additional interfaces to make it work with the terminal menu system. It also features an additional fields for determining each chapter's completion ie:
This setup allows you to pipe your ipfs commands into the tour and have their output verified. This may or may not be sufficient for verification. Some chapters may need to actually interact with the ipfs node to verify completion but the tour is not using the ipfs-api yet.
What I'd like to determine is what the chapters' instructions should be for the tour and then start planning what the verification for each should be and whether or not they need to interface with the api directly. There are many chapters in the data structure conceptually but many have no valid fields or instructions. Many may not be needed in my opinion.
The text was updated successfully, but these errors were encountered: