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:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina, @simohell, @gauravvv, @penyaskito, @Mike Gifford (CivicActions), @April, @Quynh/Quinn
Go to the issue for the next meeting to add/remove yourself to/from the list.
Recording of this week's meeting: https://youtu.be/GIZd31DYW34
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-04-28.txt
We discussed the following issues:
- #2985887: Make core's structure descriptions more consistent
- #3357211: Create two sections on /admin/structure
NR and RTBC issues marked Needs usability review.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | Drupal Usability Meeting - 2023-04-28.txt | 58.18 KB | benjifisher |
| #2 | spp.jpg | 248.27 KB | rkoller |
Comments
Comment #2
rkollerI would like to put a topic onto the list that doesn't have a dedicated issue yet but needs a discussion. in the context of the same page preview module there arose one tricky problem. currently you have preview window on the node edit form with a select form where you are able to switch in between the view modes for that nodes content type. an important and useful feature. the select form has the label view mode. problem is site builders and users with a role that has the permissions to administer content types are already familiar with the concept of view modes. but on the other hand a content editor role hasn't had a touch point with the concept of a view mode in the drupal admin interface yet. it would make sense to have a discussion how to best communicate the function of that select form.
Comment #3
diego_mow commentedIf possible, I would like to rise issue #2985887.
It looks pretty solid and quite good to go for the next release.
Comment #4
rkoller@smustgrave brought up #3025384: Content translation overview should add destination query parameter on Slack today
Comment #5
rkolleranother issue brought up by @smustgrave #3163197: Allow hiding configured blocks in layout builder. i would like to bring up the following issue #2916876: Add visibility control conditions to blocks within Layout Builder alongside. it is not tagged for usability review yet but it is related and overlapping with the aforementioned plus it applies the negate pattern we previously discussed in the context with the block content visibility settings. it would make sense to discuss both issue in combination.
Comment #6
aaronmchaleThe group is actively tracking progress on:
Issues brought forward from the previous meeting:
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.
Comment #7
rkollerthanks for updating the list aaron. two things i've noted #3309016: Add image preload option to help boost actual and perceived performance is listed twice and #2881892: UX: Hide entity ID in autocomplete widget slipped through from last weeks issue you've brought up there in comment #2
Comment #8
rkollerComment #11
benjifisherComment #12
benjifisherI commented on #2985887: Make core's structure descriptions more consistent and added #3357211: Create two sections on /admin/structure.
Comment #13
aaronmchale@rkoller Thanks for flagging that, I have updated the list on this issue and the previous week's issue.
Comment #14
benjifisherI am adding a rough transcript and a link to the recording. I am also adding #3357211: Create two sections on /admin/structure to the issue description.
Previously, I added a link to #2985887: Make core's structure descriptions more consistent and left a comment there. That issue is now Closed (won't fix). I also assigned issue credits here.
This issue is all done.