Drupal Usability Meeting 2023-03-24

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.
• 🐛 Accessibility bugs with vertical tabs Needs work
• ✨ 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
• 📌 Update UI text regarding weight so it's consistent and more helpful to new users Needs work raised in Slack by @smustgrave
• 📌 Content translation overview should add destination query parameter Needs work raised in Slack by @smustgrave

About 4 months back we've already briefly touched this issue when we ran into one out of the ten error messages in project browser when the user runs into a problem adding or installing a module #3319116: Drupal Usability Meeting 2022-11-11 → . Back then those messages weren't in shape yet and @benjifisher already left a few recommendations on the issue. over the course of the last few weeks there were several discussions and iterations. the messages are in better shape now and ready for review. Adding the issue 📌 Review all pop-up messages shown by the Svelte UI installer for user friendliness Needs work to the queue.

I would like to have a look at ✨ Provide better default configuration when re-using an existing field Fixed . It was just Fixed, so no action needed (except perhaps to create a follow-up issue), but I would like to celebrate a little.

@smustgrave has already split out the changes for the block module into an individual issue based on the recommendation in 📌 Drupal Usability Meeting 2023-03-10 Fixed . it would be good to finish the review of the permission names for the block module we've skipped the last time ✨ More granular permissions for block module Active

Added comment to 📌 Update UI text regarding weight so it's consistent and more helpful to new users Needs work , need to add list of participants, will do that once this issue has been updated with the list.

benjifisher → credited ckrina → .

benjifisher → credited simohell → .

benjifisher → credited smustgrave → .

I am adding issue credits, a rough transcript, and links to the issues we discussed.

Todo: link to the recording; comment on the issues.

I am adding a link to the recording.

Updated my comment with list of participants.

The comment on the more granular permissions issue was still missing. I've left a comment in #3347517-3: More granular permissions for block module → .Aaron left a comment on the other open issue and the reusing field issue got already merged. Since the link to the recording is in place as well as the transcript i'll set the issue to fixed.

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