Contrib.social

META: Start providing tour tips for other core modules.

Open on Drupal.org →
Created on 19 February 2013, almost 12 years ago
Updated 5 June 2024, 6 months ago

Follow up for 📌 Write tour integration for the first page after install showing extend and other things Postponed

Problem/Motivation

The Tour module is in Core, but we have very few tours in Core that use it.

Note: We actually are unsure whether Tours are actually beneficial -- Tour hasn't been usability tested (see comment #141).

Proposed resolution

* Decide what tours would be beneficial.
* Agree upon standards for tours.
* Create tours.
* Commit them to Core.

Remaining tasks

Task A: Decide what tours would be beneficial

Some ideas for tours:

  1. Initial Experience 📌 Write tour integration for the first page after install showing extend and other things Postponed
  2. Blocks 📌 Write tour integration for block_content.module Postponed
  3. Fields 📌 Write tour integration for Field UI module Postponed
  4. Views - some done in #1809352: Write tour.module and add it to core → (needs an issue to finish/polish the views part)
  5. Multilingual 📌 META: Write a multipage multilingual tour Postponed (broken out into sub-issues for different module features)
  6. Appearance 📌 Write tour integration for Appearance pages Postponed
  7. Structure #2040791: Write tour integration for Structure page →
  8. Content 📌 Write tour integration for admin/content Postponed
  9. Add/edit content 📌 Write tour integration to add/edit content UI Postponed
  10. Menu 📌 Add tour integration for Menu admin page Postponed
  11. Reports 📌 Write tour integration for Dblog page Postponed
  12. People 📌 Write tour integration for People page Postponed
  13. Extend 📌 Write tour integration for Extend (Modules) admin page Postponed
  14. Edit user 📌 Write tour integration for user edit page Postponed
  15. Shortcuts 📌 Write tour integration for shortcuts page Postponed
  16. Forums 📌 Write tour integration for forum.module Postponed

From comment #130 -- @xjm's idea: Some obvious candidates for tours:

  • Each tab of the Field UI (and explanation of the tabs themselves).
  • The Extend page.
  • The Block UI (although the work on Layouts might eventually deprecate this page).
  • The Workflow UI.
  • The Appearance page.

Other thoughts on what tours to create:

  • Modules that implement hook_help(). Can some/all of the content be converted to tips? 📌 Find out how help and tour can work together Postponed
  • Modules with routes. If it implements a page then there is a good chance it will also want to provide tips.
  • Some pages may just need a hook_help() text (which goes in the Help block) rather than a full tour -- the help block doesn't require you to click on a Tour button to get the help displayed.
  • Creating a tour for an admin page should not be a substitute for fixing usability problems on the page
  • @yoroy's list of "conceptual criticals": http://yoroy.com/pieces/drupal-ux-conceptual-criticals

Check for
- open issues tagged with tour
- Tour module issues

B: Create tours

Each tour that we want to create should be given an issue (if it doesn't already have one; or un-postpone existing issues).

Here are some links about creating tours:

C: Update the standards for tours

We currently have 3 pages that talk about standards for tours. They haven't been reviewed recently, and should be:

🌱 Plan
Status

Fixed

Version

2.0

Component
Tour  →

Last updated 3 days ago

Created by

🇦🇺Australia nick_schuch

Live updates comments and jobs are added and updated live.
  • D8MI

    (Drupal 8 Multilingual Initiative) is the tag used by the multilingual initiative to mark core issues (and some contributed module issues). For versions other than Drupal 8, use the i18n (Internationalization) tag on issues which involve or affect multilingual / multinational support. That is preferred over Translation.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024