The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.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/Quinn, @yoroy
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/Z22Hbe3yQtg
Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-05-12.txt
We discussed the following issues:
- #3025384: Content translation overview should add destination query parameter
- #3318112: [PP1] Move "Block layout" from Structure to Appearance
NR and RTBC issues marked Needs usability review.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Drupal Usability Meeting - 2023-05-12.txt | 53.87 KB | benjifisher |
Comments
Comment #2
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 #3
aaronmchaleMaybe we should discuss #3318112: [PP1] Move "Block layout" from Structure to Appearance again, regarding the recent discussion of a "legacy link", see if we can get an agreement on how that should be approached.
Comment #6
benjifisherComment #7
rkolleri've added the two issues we've talked about today to the issue summary. not sure if #3278493: Make it easier for theme builders to enable Twig debugging and disable render cache should be added as well we've touched during the beginning of the meeting? and i will write up a comment for the translation issue after dinner.
Comment #8
benjifisherI do not think we need to add #3278493: Make it easier for theme builders to enable Twig debugging and disable render cache to the issue summary. We do not have any recommendations for that issue.
I am adding the other two issues as "related".
I previously added credits for this issue, and I already commented on #3318112: [PP1] Move "Block layout" from Structure to Appearance with a screenshot showing an icon instead of "(legacy link)".
To do: rough transcript, link to the recording, comment on #3025384: Content translation overview should add destination query parameter.
Comment #9
benjifisherI am adding a rough transcript and a link to the recording.
To do: comment on #3025384: Content translation overview should add destination query parameter.
Comment #11
rkollerLeft a the overdue comment(s) on the issue today: #3025384-38: Content translation overview should add destination query parameter and added an additional comment #3025384-39: Content translation overview should add destination query parameter about two details i came across during the write-up. Apologies but that summry was a head spinner getting all those loose ends into a more or less comprehensible form.
Comment #12
rkoller