Design update

Final mockups have been attached to the Sub Epic

Design update

Below are the hand-off designs for Google Pay (Figma)

Here is the Figma file I am working in.

thanks @Dbrant -- do you know where I can get the GPay button asset? I couldn't find it in the Android Figma library and poked around the web trying to find something to download. No luck so far.

We are testing three different tones of copy in Userlytics -- strict, neutral, and welcoming. The copy we're testing is for two scenarios:

@HMonroy changing the copy to "user" is fine but the term "account" is used in multiple places so let's make sure we maintain consistency in swapping "account" for "user". I'll update Figma.

We're also planning on using the date input for the Multiblock project, on the Special: Block user page. This is for the Community Tech team.

Work updates

• You can see a comparative analysis in Figma and in Miro
• Here is the Figma file, for the latest Automoderator wireframes
• We are working closing with the Growth team who are building Community Configuration, which will be a template we will use for the Automoderator configuration UI
• Since we are using CC, it's confirmed that we will be working with Codex on this project
• We are getting ready to user test the wireframes and some UX copy

@dmaza From the Special: Block page if we're linking the user/Admin to the Block log to view active and past blocks, do we still need the above feature? I'm asking because the user/Admin can edit or remove block (currently called "change block" and "unblock") from the Block log.

Here is an interactive Figma prototype of the macro user flow I propose for when an Admin wants to investigate the active/past blocks on a target. This prototype is a first draft.

This is nearly finished. Currently working on:

1. As discussed in Slack, there is no design work needed for this ticket.
2. A UX note for the engineers: Clicking “unblock/change block” should navigate the Admin to the Special: Block page with the correct corresponding block.

@KSiebert @dmaza I'm curious if we can use more consistent language in this ticket to create more clarity? I assume "unblock" and "delete block" are the same. Can we use the same language throughout the ticket to prevent any confusion? The title of the ticket is "Delete existing blocks on Special:Block" and the "Benefits" section mentions "deletion" again, but the description talks about unblocking and so does the user story.

Suggestion: "As an admin of the wikis, I want to be able to create new sitewide or partial blocks and state the reason for the block based on observed behaviour, even if a block for the target already exists."

@KSiebert I reworked the user story a bit. Let me know what you think?

An outcome of the sense-making is this design brief(currently a work in progress but viewable to the public)

Currently working on the following:

@kostajh it should be a "destructive" delete per Codex / DS guidelines which I agree with it's a major action that we want to effectively communicate to the user. This pop up only shows when the user has made it to the step with the form which auto-populates with information. Even if we're not saving anything in the back-end, this experience still gives the impression that we've saved some possibly sensitive information so, after back and forth with DS, we went with the copy "Delete".

Per Codex, there's no border below the title ("Report Incident") on the desktop dialog component. There is for mobile.

@kostajh just jumping in here hope that's alright!

@JSengupta-WMF Some ongoing conversations I want to point you to:

• The user flow diagram in Figma and Abigail's comment on how do we decide where to route reports.
• Also in the user flow diagram, another important discussion on routing
• In Slack we have a thread going regarding @dchen 's research report on Indonesian Wikipedia

thanks @kostajh I like your recommendation. Let's streamline the information on the page and go with what you've suggested. Meanwhile I'll update Figma and Gdrive.

hey @kostajh yup that's the correct drive! I actually wasn't sure when and in what capacity you're back and working so my bad for not communicating that to you sooner :)

thanks for explanation @Mooeypoo !!!

hi all, the page titled "Spec (08/23/23)" in this Figma file is the latest copy of the design yes.

Great QAing Derrick. Love how detailed you're being.

I don't fully understand what a user will see if we do a byte limit. Otherwise, Kosta's suggestions sound good to me.

I made this ticket T344639 yesterday on this very subject and assigned it to @eigyan