Drupal Usability Meeting 2023-04-28

I would like to put a topic onto the list that doesn't have a dedicated issue yet but needs a discussion. in the context of the same page preview module → there arose one tricky problem. currently you have preview window on the node edit form with a select form where you are able to switch in between the view modes for that nodes content type. an important and useful feature. the select form has the label view mode. problem is site builders and users with a role that has the permissions to administer content types are already familiar with the concept of view modes. but on the other hand a content editor role hasn't had a touch point with the concept of a view mode in the drupal admin interface yet. it would make sense to have a discussion how to best communicate the function of that select form.

If possible, I would like to rise issue #2985887 📌 Make core's structure descriptions more consistent Closed: won't fix .
It looks pretty solid and quite good to go for the next release.

@smustgrave brought up 📌 Content translation overview should add destination query parameter Needs work on Slack today

another issue brought up by @smustgrave ✨ Allow hiding configured blocks in layout builder Needs work . i would like to bring up the following issue ✨ Add visibility control conditions to blocks within Layout Builder Needs work alongside. it is not tagged for usability review yet but it is related and overlapping with the aforementioned plus it applies the negate pattern we previously discussed in the context with the block content visibility settings. it would make sense to discuss both issue in combination.

The group is actively tracking progress on:

• 🌱 [meta] Reorganize Block items in the administration menu Active

Issues brought forward from the previous meeting:

• ✨ [Meta] Appearance page is too long and confusing Active
• 📌 [PP-3] Figure out what to do with the install/uninstall modules page Postponed with notes:
  • #3307567: Drupal Usability Meeting 2022-09-09 → : started discussing the proposed options but ran out of time, possibly splitting the confirm form into its own issue (we may want to look at that for both modules and themes, standard pattern, consider implications of project browser), worth considering parity with Drush (and other extension/package managers).
  • #3310096: Drupal Usability Meeting 2022-09-23 → : @simohell presented the various proposals, but we again ran out of time to have a in-depth discussion, using the drop-button pattern on the module page for the existing links + Uninstall was suggested.
• 🐛 Placement of batch progress messages Active with notes:
  • #3322499: Drupal Usability Meeting 2022-11-25 → : We started looking at the issue but ran out of time.
• ✨ Allow media items to be edited in a modal when using the field widget Postponed with notes:
  • @AaronMcHale: Issue could use some guidance.
    In comment #109 the issue was marked as postponed for needing input from UX, accessibility and media initiative. Apparently there are some outstanding UX/accessibility questions (but I'm not sure what they are). This was echoed in comment #111.
    Comment #144 is asking what is needed to move the issue along (the postponed state seems to be causing some delays/confusion as to how to proceed).
    Perhaps we can at least take a look at what the issue is doing and provide some recommendations/guidance on how it could be implemented.
• ✨ Allow blocks to be configured to show/hide on 200/403/404 response pages Fixed : see comment #3335028-6: Drupal Usability Meeting 2023-01-27 → for more details on what a review should address.
• 🐛 Password suggestions are hidden from screenreaders Active
• 🌱 [Policy] Remove tour module from core Fixed with notes:
  • @xjm tagged for review and sign off from the usability group before it can go ahead, noting that Tour is seen as a usability module and the core committers were not able to reach a consensus.
• 📌 Make core's structure descriptions more consistent Closed: won't fix
• 📌 Creating a new workspace should also switch to it Needs work
• 📌 Content translation overview should add destination query parameter Needs work raised in Slack by @smustgrave
• ✨ Provide Drupal root path on file system admin form Needs work
• 📌 Improve search settings help text Fixed
• 📌 Add image preload option to help boost actual and perceived performance Needs work
• 📌 Add image preload option to help boost actual and perceived performance Needs work
• 🐛 Wrong message on cancelling account with e-mail confirmation request Needs work with notes:
  • Reviewed at #3244123: Drupal Usability Meeting 2021-10-22 → and we made a recommendation (in comment #13), but there was a good point made in comment #17 so in #18 I tagged it again for review.
• 📌 Remove "Please" from the codebase Fixed

thanks for updating the list aaron. two things i've noted 📌 Add image preload option to help boost actual and perceived performance Needs work is listed twice and 🐛 UX: Hide entity ID in autocomplete widget Needs work slipped through from last weeks issue you've brought up there in comment #2 📌 Drupal Usability Meeting 2023-04-21 Needs work

benjifisher → credited BlackBamboo → .

benjifisher → credited mgifford → .

I commented on 📌 Make core's structure descriptions more consistent Closed: won't fix and added 📌 Create two sections on /admin/structure Active .

@rkoller Thanks for flagging that, I have updated the list on this issue and the previous week's issue.

I am adding a rough transcript and a link to the recording. I am also adding 📌 Create two sections on /admin/structure Active to the issue description.

Previously, I added a link to 📌 Make core's structure descriptions more consistent Closed: won't fix and left a comment there. That issue is now Closed (won't fix). I also assigned issue credits here.

This issue is all done.

Automatically closed - issue fixed for 2 weeks with no activity.