Part of #1921152: META: Start providing tour tips for other core modules.

Problem/Motivation

Write tour integration for People admin page

Proposed resolution

Create tour yml files for required admin screens in admin/people.

Remaining tasks

Create patch for tour integration for primary People page

User interface changes

New tours

API changes

None

Technical pointers when creating tour tips

See: https://drupal.org/node/1921152#tour-tips-tech-note for tech notes on making tour tips.

Comments

StatusFileSize
new1.02 KB
PASSED: [[SimpleTest]]: [MySQL] 56,619 pass(es).
[ View ]

Content written and edited by colleagues :)

Status:Active» Needs review
StatusFileSize
new2.38 KB
PASSED: [[SimpleTest]]: [MySQL] 57,150 pass(es).
[ View ]

Ignore previous. This patch contains two yml files

Re the image, I don't think 'any site visitor' is true, I think 'approved users' would be more correct, as it's permission based.

Issue tags:+Needs tests

Tour needs tests since we now have #2028535

StatusFileSize
new2.03 KB
new3.93 KB
FAILED: [[SimpleTest]]: [MySQL] 58,844 pass(es), 1 fail(s), and 2 exception(s).
[ View ]

Updated the patch to add UserAdminTourTest.php and fix a couple of whitespace issues in the yml file.

One of the tests fails because it can't find an element with class .action-links, which the second tip is attached to. However I can see such an item in the verbose testing output:

<nav class="action-links">
<li>
<a class="button button-action" href="/d8/admin/people/create">Add user</a>
</li>
</nav>

If I attach the second tour tip to class "button-action" the test passes. Does SimpleTest not handle the html 5 nav element?

Status:Needs review» Needs work

The last submitted patch, tour-people-2040845-5.patch, failed testing.

Assigned:lisarex» Unassigned

unassigning myself

StatusFileSize
new2.37 KB
new5.78 KB
PASSED: [[SimpleTest]]: [MySQL] 58,437 pass(es).
[ View ]

Updated patch that adds the test for the /user/*/edit tour. It also modifies the user admin tour test to no longer test for nav class="action-links", which I mentioned in comment #5 I could not get to pass and which I suspect has to do with it being an html5 nav element. Only a guess though.

Status:Needs work» Needs review

Changing status to needs review.

StatusFileSize
new3.13 KB
new2.66 KB
PASSED: [[SimpleTest]]: [MySQL] 58,451 pass(es).
[ View ]

Just noticed issue #2044399: Write tour integration for user edit page exists for the /user/*/edit tour and that that tour appears more complete, so I am rerolling this patch to remove the tour and test for /user/*/edit.

Issue summary:View changes
Status:Needs review» Reviewed & tested by the community
Issue tags:-Needs tests

Works for me. Marking this as RTBC.

Status:Reviewed & tested by the community» Needs review

The code may work but the content & wording needs a proper review first

Assigned:Unassigned» nielsonm
Status:Needs review» Needs work
Issue tags:+Tour Content Review

Needs content review and new router system based update

Status:Needs work» Needs review
StatusFileSize
new3.09 KB
new2.23 KB
FAILED: [[SimpleTest]]: [MySQL] 63,678 pass(es), 2 fail(s), and 0 exception(s).
[ View ]

This patch updates the path to a route and updates the test coverage.

Status:Needs review» Needs work

The last submitted patch, 14: tour-people-2040845-14.patch, failed testing.

The last submitted patch, 14: tour-people-2040845-14.patch, failed testing.

StatusFileSize
new389 bytes
new2.24 KB
FAILED: [[SimpleTest]]: [MySQL] 63,404 pass(es), 1 fail(s), and 0 exception(s).
[ View ]

Fixes yml format issue.

Status:Needs work» Needs review

StatusFileSize
new2.24 KB
FAILED: [[SimpleTest]]: [MySQL] 63,368 pass(es), 1 fail(s), and 0 exception(s).
[ View ]
new389 bytes

Reuploading for tests to run.

Status:Needs review» Needs work

The last submitted patch, 19: tour-people-2040845-17.patch, failed testing.

The last submitted patch, 17: tour-people-2040845-17.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new2.22 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch tour-people-2040845-22.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Status:Needs review» Needs work

The last submitted patch, 22: tour-people-2040845-22.patch, failed testing.

Assigned:nielsonm» Unassigned

Status:Needs work» Needs review
StatusFileSize
new2.22 KB
PASSED: [[SimpleTest]]: [MySQL] 63,377 pass(es).
[ View ]
new378 bytes

Time for some green!

StatusFileSize
new2.58 KB
PASSED: [[SimpleTest]]: [MySQL] 64,331 pass(es).
[ View ]
new1.8 KB

Updates content to better align with guidelines.

This comment raises architectural design concerns and is not meant to discredit the work that went into this particular issue and patch.

+    label: 'Managing users'
+    body: 'View and edit user accounts.'
...
+    label: 'Add a user'
+    body: 'Create a new user account.'
...
+    label: 'Search for users'
+    body: 'Find users by applying filters.'
...
+    label: 'Update accounts'
+    body: 'Select one or more users via the checkboxes to apply changes to the accounts.'
...
+    label: 'Edit user account'
+    body: 'Make changes to one user account.'

Hrm. — Do we really want to explain every possible UI interaction in tour tips?

If we do, what kind of "tip" or explanation is "Create a new user account." meant to give that wouldn't be obvious by the UI already?

I was under the assumption we introduced Tour tips to explain non-obvious things in the user interface only?

→ If we need to provide hints for the most fundamental/basic operations, then our UI/UX must be seriously flawed? (which I don't think it is)

I'm afraid, this makes little sense to me. These kind of Tour tips will only make people avoid Tour module whenever possible.

Introducing any kind of such "tips" presents a major disrespect and discredit for the hard work of Drupal's Usability and Design teams, because the mere fact of pointing out the most basic user interface operations via Tour tips would mean that the entire user interface design is a utter #FAIL.

Or to put that in reverse, because it might not be obvious:

The user interface design is solely responsible for making obvious things obvious. User interface design enables end-users to use Drupal intuitively. A well-designed user interface needs absolutely zero explanation; every human immediately understands how to use it. That is the one and only goal of user interface design.

This patch (and likely others) introduces tips for the most obvious operations in the user interface. These operations should not need any kind of explanation in the first place. IF they do, then the solution is NOT to explain to the user how to use the interface. — The only acceptable solution is to fix the user interface design.

In short, if there is a problem with any of these basic operations, then we need to fix the UI. Tour tips should be reserved for non-obvious interactions.

A non-obvious interaction would be to point out that it is possible to add fields to users. Or to add view modes. Or that you can change the administrative user listing/view to customize it to your needs. Or that you can leverage the "Reset password" functionality to temporarily grant someone else access to a user account without sharing the password. — All of that is not obvious, and cannot be solved by user interface design.

Some background discussion about the role of tours can be found in #1921152: META: Start providing tour tips for other core modules.

sun, I could not possibly agree more. I think there has been some motivation to get more tours in and that has resulted in trying to create ones for a lot of admin pages that don't really need them. Or maybe this page should have one but as you said, it should point out the less obvious things.

There should probably be some more discussion about this sooner than later, to avoid unnecessary work.