Drupal Usability Meeting 2022-12-02

The group is actively tracking progress on:

• #3318110: [meta] Reorganize Block items in the administration menu

Issues brought forward from the previous meeting:

• #2591323: Workflow and text for installing themes is confusing
• #2860419: [Meta] Appearance page is too long and confusing
• #2035079: [PP-1] Figure out what to do with the install/uninstall modules page 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.
• #2569785: Placement of batch progress messages with notes:
  • #3322499: Drupal Usability Meeting 2022-11-25: We started looking at the issue but ran out of time.
• #3081500: Accessibility bugs with vertical tabs
• #2862859: Create a top level, extendable, "Content" admin menu route that behaves like "Structure" with notes:
  • @benjifisher: Some people suggest fixing this before, or along with, #2862564: Move Custom block library to Content
• @AaronMcHale: I'd also like to discuss something which came up while presenting #3318110: [meta] Reorganize Block items in the administration menu to colleagues.

I'd like to discuss #296693: Restrict access to empty top level administration pages which I found after discussion at #3320757-4: Drupal Usability Meeting 2022-11-18.

As discussed in todays meeting i wanted to bring up the two feature ideas that spun out presenting the proposed changes for #3318110: [meta] Reorganize Block items in the administration menu to meetup groups and that might entail follow up issues for the parent issue.

First is about the current custom block library behavior only enlisting blocks that are created in admin/structure/block/block-content currently. Some even not realized that fact to the full extent. So the suggestion as outlined in the comment is to extend the types of blocks being displayed in the custom block library so people are control:
https://www.drupal.org/project/drupal/issues/2862564#comment-14789469

the other idea is related. it is about providing a similar overview page for layouts created for content types or nodes of content types in case the customize option is set. the idea is outlined in the last paragraph of the following comment:
https://www.drupal.org/project/drupal/issues/3318558#comment-14789485

or maybe it makes sense to have a discussion about the comment in general because the other detail that needs some thought is the wording for the button currently called create custom block. that button is already confusing in regards of its implications (currently those blocks are only available in layout builder - not reusable custom blocks) and with #2999491: Add reusable option to inline block creation we've already discussed in #3292468: Drupal Usability Meeting 2022-07-01 blocks created in layout builder could also become reusable custom blocks.

I came across #2317981: Move block content edit and delete routes under admin/content/block to improve IA for editors and fix breadcrumbs, which I'd like to discuss and is relevant to the work on #3318110: [meta] Reorganize Block items in the administration menu.

Filed #3325034: Providing additional methods of navigating the admin interface based on discussion at the meeting.

I've filed #3325029: Improve the overview of the list of available blocks based on the discussions about https://www.drupal.org/project/drupal/issues/2862564#comment-14789469 and #3325039: Improve the overview of the list of available content types with a layout and layout overrides for its nodes based on the discussions about https://www.drupal.org/project/drupal/issues/3318558#comment-14789485 .