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, @Mike Gifford (CivicActions), @Quynh, @yoroy, @EricRubino
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/S2oVmkWippQ
Rough transcript of this week's meeting: Drupal Usability Meeting - 2024-02-02.txt
We discussed the following issue:
- #3370326: Refine labels and descriptions for field types
- #1562776: Edit Summary label is unclear to users
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-02-02.txt | 57.72 KB | benjifisher |
Comments
Comment #2
rkollerMoving over my suggestion from last week:
I would like to put three issues onto the list. first the issue i've also posted on slack #3389317: Differentiate visually dragging with and without hierarchy (about some word smithing of two titles). second in the context of the field ui i would like to bring up #3370326: Refine labels and descriptions for field types. i've created a google sheet a few weeks ago and revisited the issue starting to work on a draft as well as discussed the topic and got some feedback during the last two drupal dojos. And i wanted to revisit #3344498: Improve the manage form display page by untwining field widgets that belong to the main content and sidebar. We've discussed it already in august, but i've stumbled across #3007167: [policy] Deprecate field_layout module and move it to contrib and noticed that field layout is gonna be deprecated and that parts of it should still go into core #2844302: Move Field Layout data model and API directly into \Drupal\Core\Entity\EntityDisplayBase. that overlaps with the issue to revisit and i think it would make sense to have a coordinated approach.
Comment #3
rkollerand @larowlan raised https://www.drupal.org/node/1562776 in the #ux channel
Comment #4
rkollerComment #5
rkollerComment #6
rkollerLeft a comment at: #3370326-9: Refine labels and descriptions for field types
Comment #11
benjifisherComment #12
benjifisherComment #13
simohell commentedI commented the issue on long text summary https://www.drupal.org/project/drupal/issues/1562776#comment-15427067
Comment #14
benjifisher@simohell:
Thanks. With that and the link to the recording that I am posting now, this issue is done.
Comment #16
simohell commented