This meeting takes place every Friday at 14:00 UTC (currently 7:00am PT, 10:00am ET). See Time.is to see what that is in your timezone.
The meetings are held using Zoom, and a link is posted in the #ux Slack channel 10 minutes before the meeting. Agenda is first come, first serve and set by attendees. Use the Needs usability review issue tag for issues that need review and/or suggest issues in comments here.
List of Slack users to ping 10 minutes before the meeting:
@worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Ravi, @shaal, @ckrina, @simohell, @Quynh, @yoroy, @Regu.pl, @Gareth - (the_g_bomb), @sahil, @Pallavi Singh
This list gets copied to the issue for the next meeting. If that has already happened, then go to that issue to add/remove yourself to/from the list.
Recording of this week's meeting: https://www.youtube.com/watch?v=6iNOdKq7Sdw
Rough transcript of this week's meeting: Drupal Usability Meeting - 2026-07-31.txt
We discussed the following issue:
NR and RTBC issues marked Needs usability review.
The group is actively tracking progress on these issues:
- #2860419: [Meta] Appearance page is too long and confusing
- #2985168: [PP-1] Allow media items to be edited in a modal when using the field widget 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. - For an overall summary of the problem space see the videos in #3534039: Drupal Usability Meeting 2025-07-11 and #3535491: Drupal Usability Meeting 2025-07-18
- @AaronMcHale: Issue could use some guidance.
- #3163197: Allow hiding configured blocks in layout builder
- #2916876: Add visibility control conditions to blocks within Layout Builder
- #3247064: Error message presented when a BrokenPostRequestException is fired on AJAX submission can be misleading
- #3262935: Link field validation constraints don't give enough detail
Remaining tasks
-
Add issue credits for the participants. -
Add the issue(s) we discussed to the issue summary and as related issues. -
Add a rough transcript. -
Add a link to the recording on YouTube. -
Comment on the issue(s) we discussed.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Drupal Usability Meeting - 2026-07-31.txt | 65.78 KB | benjifisher |
Comments
Comment #2
rkollerive already removed the root path issue from the short list we are tracking from the issue from last week and do so for this week as well. due to the fact that from our point of view there isnt much feedback left to give (and we already did four round of reviews and the current state looks solid)
Comment #3
gábor hojtsyIs it possible to jump the queue somehow? :) #3590882: Standard profile should not include Olivero anymore, should provide guidance on how to get started is a key part of implementing the core product strategy (removing Olivero and making people install modern component based solutions themselves). This issue itself is not that complicated actually but it changes both the default Drupal frontpage and the welcome message so it is something ALL future Drupal users would face :)
On the other hand Layout Builder is on its way to be removed from core, so if I were you I would not spend time on reviewing issues for it :) See #3521159: Remove Layout Builder dependency for the config and rendering of the Navigation sidebar for example.
Comment #4
benjifisherComment #5
benjifisherComment #6
benjifisherComment #7
rkollerdirect link to the meeting summary : #3590882-22: Standard profile should not include Olivero anymore, should provide guidance on how to get started (thanks benji!), and ive added the link to the recording to the issue summary.
Comment #9
rkollerforgot to strike comment on the issue from the remaining taks list in the issue summary