Drupal Usability Meeting 2024-10-11

Open on Drupal.org →

Created on 4 October 2024, 3 months ago

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: TODO

Rough transcript of this week's meeting: Drupal Usability Meeting - 2024-10-11.txt

We discussed the following issue:

TODO

NR and RTBC issues marked Needs usability review → .

The group is actively tracking progress on these issues:

🌱 [meta] Reorganize Block items in the administration menu Active
✨ [Meta] Appearance page is too long and confusing Active
✨ Allow media items to be edited in a modal when using the field widget Postponed 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.
✨ Provide Drupal root path on file system admin form Needs work
🐛 UX: Hide entity ID in autocomplete widget Needs work
✨ Allow hiding configured blocks in layout builder Needs work
✨ Add visibility control conditions to blocks within Layout Builder Needs work
🐛 Error message presented when a BrokenPostRequestException is fired on AJAX submission can be misleading Needs work
📌 Link field validation constraints don't give enough detail Needs work
✨ Use modals in field creation and field edit flow Needs work

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.

📌 Task

Status

Active

Version

11.0 🔥

Component

meetings

Created by

🇺🇸United States benjifisher Boston area

Live updates comments and jobs are added and updated live.

Usability
Makes Drupal easier to use. Preferred over UX, D7UX, etc.

Sign in to follow issues

Comments & Activities

Issue created by @benjifisher
Comment 3 months ago →
🇩🇪Germany rkoller Nürnberg, Germany
carried over from last week:
✨ Use data-* to check modules dependencies before submit Active
🐛 New User Logout confirm Form is misleading Needs work
Comment 2 months ago →
🇩🇪Germany rkoller Nürnberg, Germany
and another one raised by @smustgrave on the #ux channel yesterday:

🐛 Inconsistent use of language regarding plugins Active
Comment 2 months ago →
🇬🇧United Kingdom AaronMcHale Edinburgh, Scotland
benjifisher → credited aaronmchale → .
Comment 2 months ago →
🇺🇸United States amazingrando
benjifisher → credited amazingrando → .
Comment 2 months ago →
🇮🇳India Avani.Bhut India
benjifisher → credited avani.bhut → .
Comment 2 months ago →
🇫🇮Finland simohell
benjifisher → credited simohell → .
Comment 2 months ago →
🇺🇸United States worldlinemine
benjifisher → credited worldlinemine → .
Comment 2 months ago →
🇺🇸United States benjifisher Boston area
Comment 2 months ago →
🇺🇸United States benjifisher Boston area
At today's meeting, we discussed the general issue of how to document decisions.

In particular, when someone opens an issue with a suggestion that has already been considered and rejected, we should close the issue (works as designed). When we do that, we should thank the person who opened the issue for contributing to the discussion. We should also give them a link to an ongoing discussion, if there is one, or to some documentation of the decision.

Typically, the decision is made in the comments on an issue that is now closed. Closed issues are pretty bad for discoverability.

One option is to use change records for these decisions. The Coding Standards → group already does this: see https://www.drupal.org/list-changes/coding_standards → .

Since we did not discuss any particular issues in detail, I am marking some of the standard "Remaining tasks" as complete.
Comment 2 months ago →
🇺🇸United States benjifisher Boston area
Comment 2 months ago →
🇺🇸United States benjifisher Boston area
Comment about 2 months ago →
System Message
Automatically closed - issue fixed for 2 weeks with no activity.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024