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, @gauravvv, @Quynh, @yoroy, @andrei.zvonkov, @Regu.pl, @amazingrando
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/JPxvcpNXY0Q
Rough transcript of this week's meeting: Drupal Usability Meeting - 2024-10-04.txt
We discussed the following issue:
- #2983456: Expose triggering update of media metadata + thumbnail to end users
- #3221259: Add permissions for optional modules to content editor role as they become enabled
- #3446753: Improve links on /admin/people/roles
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
- #2881892: UX: Hide entity ID in autocomplete widget
- #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
- #3386762: Use modals in field creation and field edit flow
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 |
|---|---|---|---|
| #11 | Drupal Usability Meeting - 2024-10-04.txt | 72.31 KB | benjifisher |
Comments
Comment #2
rkollercarried over from last week:
#1473760: Use data-* to check modules dependencies before submit
#3469116: Logout confirmation form shows inappropriate confirmation description
and another issue @smustgrave raised in the #ux channel before last weeks meeting:
#3446753: Improve links on /admin/people/roles
Comment #3
rkollerComment #4
rkollerComment #10
benjifisherComment #11
benjifisherComment #12
benjifisherComment #13
rkollerI've commented on the refresh media items issue: #2983456-166: Expose triggering update of media metadata + thumbnail to end users. Video and transcript are available and in place. But i've checked for comments to the other two issues for this meeting. benji commented on #3221259-28: Add permissions for optional modules to content editor role as they become enabled but #3446753: Improve links on /admin/people/roles which is also listed in the issue summary doesnt have a comment yet. i'll recheck the recording after dinner (cuz i cant remember your conclusion from back then).
Comment #14
smustgrave commented