Skip to content

Feature: "Next steps" closing page for all tutorials. #129

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

Closed
mikeal opened this issue Jan 14, 2019 · 6 comments · Fixed by #226
Closed

Feature: "Next steps" closing page for all tutorials. #129

mikeal opened this issue Jan 14, 2019 · 6 comments · Fixed by #226
Assignees
Labels

Comments

@mikeal
Copy link
Member

mikeal commented Jan 14, 2019

At the end of a lesson we link back to the tutorials.

Instead, we should create a page full of potential next steps someone can take after learning what they've just learned. It could include:

  • Documentation and blog posts about creating things with what they've learned.
  • Entry points into relevant communities.
  • In more advanced tutorials it could even link into places where people are hiring developers in this particular area.
  • And of course, it should link in to places in the ProtoSchool project where they can contribute as well.
@mikeal mikeal added the enhancement New feature or request label Jan 14, 2019
@nuke-web3
Copy link
Contributor

Also consider:

@terichadbourne
Copy link
Member

@mkikeal Do we want this page accessible all the time from the main menu? So if a tutorial now has 3 lessons, it will instead have 4 and Lesson 4 will be "Next Steps," and it would be visible when you are viewing this type of listing?

image

The other option would be a top secret page that's not surfaced anywhere but linked to from the last publicly visible lesson as a sort of reward for finishing (in which case we'd have to decide whether you only have to have finished the last lesson in the tutorial or all of them, and build some new code if the latter.

I'm leaning toward making it accessible to navigate to in case anyone wants to jump right to recommendations for follow-up materials/projects.

Thoughts?

@mikeal
Copy link
Member Author

mikeal commented Jan 17, 2019

Since it isn't something you can "complete" I'm leaning towards saying no, the last page should be hidden from this particular view.

@terichadbourne
Copy link
Member

My concern with making a next steps page appear only after you've completed a full tutorial, rather than being a visible part of the curriculum, is that users won't be able to navigate back to it.

Per a discussion with @mikeal, we'll postpone addressing this issue until after making a decision on Vuepress (#141), which we'll be exploring the week of 2/11-2/15.

@terichadbourne
Copy link
Member

We'll be addressing this one in the near future, with @fsdiogo taking the first stab at it. Some of the goals we discussed today:

  • The "Next Steps" or "Resources" page will be visible from the main landing page for the tutorial, as the last lesson in the list (you will not have to complete the lessons to access it)
  • If the currently-last lesson is New Tutorial: The BORG #3, this new page will have a generic label like "Resources" or "Next Steps" as opposed to being "Lesson 4" (since you're not learning anything new there)
  • We'll supply some sort of structure via the components so that all of these pages take the same format, so that we don't end up with some authors using a bulleted list, some writing paragraphs, etc.
  • We might consider using either consistent headers or consistent tags to apply to the list of resources.

UX suggestions are welcome!

@fsdiogo
Copy link
Collaborator

fsdiogo commented May 13, 2019

For the tutorial's landing pages I have two proposals:

1


2

If you have suggestions about the copy, please fire away.

We should try to make the text concise and the same for different tutorials.

When the user enters that lesson, it is automatically passed just as the non-exercise lessons.

Check it in Figma.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants