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.

ping:
@Gábor Hojtsy (he/him), @worldlinemine, @lauriii, @AaronMcHale, @anmolgoyal74, @Antoniya, @Ravi, @shaal, @ckrina, @simohell, @gauravvv

Go to the issue for the next meeting to add/remove yourself to/from the list.

Recording of this week's meeting: https://www.drupal.org/project/drupal/issues/3335028

Rough transcript of this week's meeting: Drupal Usability Meeting - 2023-01-20.txt

We discussed the following issues:

  • We reviewed the issues from our weekly meetings in Oct-Dec 2022. See Comment #6.
  • We looked at the draft Drupal user personas (Google doc).

NR and RTBC issues marked Needs usability review.

CommentFileSizeAuthor
#13 Drupal Usability Meeting - 2023-01-20.txt59.45 KBbenjifisher

Comments

benjifisher created an issue. See original summary.

aaronmchale’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

The group is actively tracking progress on:

Issues brought forward from the previous meeting:

aaronmchale’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

#2985168: [PP-1] Allow media items to be edited in a modal when using the field widget 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’s picture

aaronmchale
Primary language English
Location Edinburgh, Scotland
commented

On the theme of #3318110: [meta] Reorganize Block items in the administration menu, let's also look at #3325167: Revisit the redirect to 'add block' form in the 'add block content' form.

bhanu951’s picture

bhanu951 commented

May be this issue can be reviewed #1986330:When Batch ID doesn't exist, Drupal should emit a 404

It was reviewed earlier by UX team and changes were requested which were made.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

For this meeting (or maybe the next one) I would like to do a little retrospective: just read through the list of issues we considered in the last 3 months of 2022. We can celebrate the issues that have been fixed, and maybe we will be inspired to work on some that have been stalled.

#3312892: Drupal Usability Meeting 2022-10-07

#3314117: Drupal Usability Meeting 2022-10-14

#3315240: Drupal Usability Meeting 2022-10-21

#3316853: Drupal Usability Meeting 2022-10-28

#3318005: Drupal Usability Meeting 2022-11-04

#3319116: Drupal Usability Meeting 2022-11-11

#3320757: Drupal Usability Meeting 2022-11-18

#3322499: Drupal Usability Meeting 2022-11-25

#3323771: Drupal Usability Meeting 2022-12-02

#3324991: Drupal Usability Meeting 2022-12-09

#3326232: Drupal Usability Meeting 2022-12-16

#3327488: Drupal Usability Meeting 2022-12-23

#3327611: Drupal Usability Meeting 2022-12-30

There are also two Layout Builder issues that we discussed in June and July that I personally would like to see fixed: #2999491: Add reusable option to inline block creation and #3080606: [PP-1] Reorder Layout Builder sections.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented

@Bhanu951:

I looked at #1986330: When Batch ID doesn't exist, Drupal should emit a 404 and left a comment.

At this point, the issue needs code review and testing. It is more efficient for one person to do that, not a group of people in a Zoom meeting. In other words, the weekly usability meeting is not the right place to move this issue forward.

Since the issue is already tagged for the Bug Smash initiative, you might get some interest from the #bug-smash channel in Slack.

Tip: on this site, you can refer to an issue as [# 1986330] (without the space), and a custom text filter will convert it to a link as above. It is easier than making the link yourself, and it automatically adds the issue status (using color and hover text).

bhanu951’s picture

bhanu951 commented

@benjifisher Thanks for the comment and for the tip TIL.

ckrina’s picture

ckrina
she/her
Primary language Catalan
Location Barcelona
commented

I’d like to talk about the Drupal User personas I’m working on, needed for several initiatives.

benjifisher credited rkoller.

benjifisher credited shaal.

benjifisher credited simohell.

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Issue summary: View changes
Status: Active » Needs work
StatusFileSize
new Drupal Usability Meeting - 2023-01-20.txt59.45 KB

I am adding issue credits, a rough transcript, and a link to the recording.

I created a stub React.js slide deck to help publicize the personas. The source is in my Slide Decks repository (markdown, with support for image files).

benjifisher’s picture

benjifisher
he/him or they/them
Primary language English
Location Boston area
commented
Status: Needs work » Fixed

There is no issue yet for the Drupal personas. I think I will not wait for that: this issue is done.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.