https://www.mediawiki.org/wiki/Extension:GuidedTour/Write_an_on-wiki_tour
Description
As a new Mentor, I want to understand how to navigate to my Mentor dashboard and receive a basic dashboard orientation.
- An user signs up as a mentor
- A guided tour starts. The dialog thanks the user for signing up, informs them that a dashboard is available via the user menu. The wording may need to be different skin-to-skin. We will also need a generic one as a fallback [in case a new skin gets added].
- User is redirected to their dashboard.
- A quick tour over the dashboard is presented
As an existing Mentor, I want a reminder about visiting my Mentor dashboard and receive a basic dashboard orientation as page has many improvements since I last visited.
- Once we have a "new mentor" guided tour, we should consider repurposing it as reminder for existing Mentors to visit their dashboard and check out the new features. This could simply be the same Guided Tour, simply starting at step 3.
For the first tour, the starting point is clear (enrollment success message).
For the reminder tour for existing Mentors, that's a bit challenging. Possibilities include:
- Send a message to all mentors on their talk page, re-informing them about the dashboard, and giving them a link to the tour. That'd be reasonably easy, as Benoit/CRS has tooling for mass-messaging. It'd be also an acceptable use of human time, since the reminder is likely only needed now (or would it be shown more often?).
- Build a "News for mentors" module on the dashboard. This would be populated by both the Growth team and the community (and/or the local chapter). This obviously wouldn't help with discovering the dashboard, but it can notify the mentors about new features.
- Trigger a notification. This is a bit challenging, from both technical and community perspective. Personally, I receive a couple of notifications per day, and they're mostly about "do this now" (such as, someone talking to me or replying in a thread I participated in). This would be a Someday/Maybe kind of notification. I think long-term, this decreases the power of notifications. Technically, it'd require writing some one-time code (unlike talk page messages, we don't have any tooling for triggering notifications). It's possible, but not ideal.
Questions:
- For the reminder tour for existing Mentors, do we want to wait until Personalized Praise changes are made? (And include info about that in the tour?)
Standard Questions for Designing a Guided Tour:
- Choose a primary goal for the tour. What do you want users to learn by the end?
- Know who your audience is before you start, and what their goals and experiences are. What knowledge about a process do they have before starting your tour?
- Plot the necessary steps, focusing on the one action or key takeaway for each step. Less is more. The more steps in your tour, the more likely a user is to abandon your tour in the middle.
- Tours can be started via a link or button within a page, or automatically via a cookie. How you start a tour has a big impact on the potential for delivering tours that interrupt or annoy users, so choose carefully.
- Let the steps and their associated actions guide the design of the tour. For example, if you want users to edit as one step, pointing directly to the edit button is the obvious and efficient thing to do. A poor alternative would be to have a center-aligned window with an image and description of the edit tab. The strength of tooltip-based tours is that you can show users what to do, instead of simply describing it.
- Choose titles, body text, and images only after you have plotted all steps in your tour.
Acceptance Criteria
Given I'm an Engineer creating a guided tour,
Then I have clear copy for each stage of the tour, and an understanding about how the tour is triggered, where the tour is pointing, and the buttons included.
Guided tour should follow best practices and recommendations about how to write an on-wiki tour:
https://www.mediawiki.org/wiki/Extension:GuidedTour/Write_an_on-wiki_tour
Tour needs to consider the various desktop skins.