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:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina, @simohell, @gauravvv, @penyaskito, @Mike Gifford (CivicActions), @April, @Quynh, @yoroy, @EricRubino
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/PPD3bKtLaCI
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-09-29.txt
We discussed the following issues:
- #3389200: Field selection breaks conventions and increases cognitive load
- #3370326: Refine labels and descriptions for field types
Also some related issues, such as #3356894: Make field selection less overwhelming by introducing groups and #3346539: [Plan] Improve field creation experience.
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
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 |
|---|---|---|---|
| #10 | Drupal Usability Meeting - 2023-09-29.txt | 66.28 KB | benjifisher |
Comments
Comment #2
benjifisherComment #9
benjifisherI am adding issue credits and links to the issues that we discussed.
Comment #10
benjifisherI am adding a rough transcript.
Comment #11
benjifisherComment #12
benjifisherComment #13
rkollerwe havent commented on none of the two issues. but i guess the issue could be set to fixed anyway. the first issue we've dicussed in january again and it is in a good shape now while the second issue we've only touched during the second part of the meeting. just skimmed through and it sounds like the meeting was more about catching up on the field ux in general and we've covered a lot of ground. one or two details from the discussion relevant to the linked field descriptions issue back then i've added to a comment i've left on #3370326: Refine labels and descriptions for field types today. so i think it would be fine to set this issue to fixed?
Comment #14
benjifisher@rkoller:
Thanks for reminding me of this issue on Slack. I agree, we can consider this issue Fixed.