This meeting takes place every Friday at 14:00 UTC (currently 6:00am PT, 9: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
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://youtu.be/bJMTfbJSHk8
Rough transcript of this week's meeting: Drupal Usability Meeting - 2025-07-04.txt
We discussed the following issues:
- #3528251: Layout Builder "Discard changes" confirmation form is destructive and does not communicate consequences to the user
- #3528494: Layout Builder "Revert to defaults" confirmation form (and similar forms) do not nearly explain how destructive the operation is
NR and RTBC issues marked Needs usability review.
The group is actively tracking progress on these issues:
- #3318110: [meta] Reorganize Block items in the administration menu
- #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.
- @AaronMcHale: Issue could use some guidance.
- #2704931: Provide Drupal root path on file system admin form
- #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 |
|---|---|---|---|
| #8 | Drupal Usability Meeting - 2025-07-04.txt | 36.28 KB | benjifisher |
Comments
Comment #2
benjifisherOn Slack, @DanielVesa suggested these issues for the next meeting:
Comment #5
benjifisherComment #6
benjifisherComment #7
benjifisherI added a comment to #3528494: Layout Builder "Revert to defaults" confirmation form (and similar forms) do not nearly explain how destructive the operation is, even though one of the points I made is that we think that issue should be closed and combined with #3528251: Layout Builder "Discard changes" confirmation form is destructive and does not communicate consequences to the user.
Comment #8
benjifisherComment #9
benjifisher