User Details
- User Since
- Jan 6 2023, 2:02 PM (110 w, 4 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- JSengupta-WMF [ Global Accounts ]
Fri, Feb 14
Tue, Feb 11
I would hold off from making any changes for the time being. With the updated table design, some more space would free up. But yes finally the bullets should be within the cell and not extend beyond them. To get more space, you can manually set lower width to Timestamp, Expiry and Block admin columns and increase width of Block details and reasons columns.
Mon, Feb 10
Thu, Jan 30
Sun, Jan 26
Yes the block type heading needs to have more padding. Regarding the Cancel button, it's a quiet button that clears and hides the form. It will be great to have as per UX best practice. However, if this delays the release then we can get back to it later.
Jan 14 2025
Jan 13 2025
Yes you can make them progressive quiet buttons and remove the pipe separator.
<cdx-button action="progressive" weight="quiet">Click me</cdx-button>
Jan 9 2025
Based on the video walkthrough, the current design/implementation doesn't look weird at all to me. When user click "Edit" in a multiblock situation, please keep the row highlighted while the user is working on the form.
Jan 8 2025
Updated the design in the description. @TheresNoTime
Jan 6 2025
Let's keep the destructive button without icon in that case.
Dec 19 2024
It should be called "Unblock target" to be consistent with Special:Block page
Dec 16 2024
Dec 13 2024
Yeah the link to the design page wasn't updated in the story. I have updated it now. There's a pipe in my design. https://www.figma.com/design/3PthdmimQ8FiuhGIsLhmZi/Multiblock?node-id=2523-35313&t=h9iau9dZCnnUcmOm-1
Dec 11 2024
No concerns. Let's proceed with blank cell and keep an eye out for any feedback on this post launch.
Dec 10 2024
The UI copy "Add block" is used to make this CTA future proof when layering of blocks is enabled. Even when no block is present, Add block is not a wrong CTA cause it is, in essence adding a block. We are avoiding words like "user", "account" etc because it can be an IP address or IP range and not a specific user.
Dec 4 2024
Hide it.
Got it. I am updating the designs as per our discussion and will also update any copy that says account.
Dec 2 2024
@MusikAnimal I thought we were going with the hyphen (-) to avoid translation. See example on 3rd and 5th column.
Nov 26 2024
Nov 25 2024
- As the event will be based in several timezones across East and West Africa, I would say staff in CET or UTC time zone might find it more convenient. The Codex presentation session is planned at the beginning of the day on 12.12.2024
@MusikAnimal on your last question, yes a white background on the table makes sense.
Nov 12 2024
@dmaza You can use the yellow warning sign when there is a block and no icon when there is zero block. Grey denotes disabled.
Oct 23 2024
As per Barbara's comment earlier, accordion should have the same width of the form. Would that solve this problem?
Oct 18 2024
Oct 4 2024
@MusikAnimal leaving the cell blank makes sense in both cases. Alternately we could use a "-" hyphen to show it's intentionally blank and not due to some error in the table.
Sep 18 2024
@Samwilson as per our discussion here is a modified banner to address your questions.
Aug 26 2024
@Samwilson @MusikAnimal it shouldn't look cluttered cause the number of columns is same. Can you reduce the width of the Projects column?
Aug 19 2024
As per @Samwilson's rationale, we don't need to protect the page for the time being. If we see the page is being vandalized, can take this call later.
Aug 1 2024
Editing shouldn't be possible for any of the staff created pages. But I guess this is one of the limitation of building the pages in wiki?
Jul 26 2024
@GMikesell-WMF @Samwilson the design does look different from the Figma file. Is it something we can align?
https://www.figma.com/design/JcTMFwbEJPpCKBiZ16Jkel/Future-of-the-Wishlist?node-id=2179-73651&t=VlFzwG3BWS1iOSs0-1
Jul 24 2024
@MusikAnimal 1 column checkboxes look nice on mobile. This is what I would have proposed too.
Yes last updated will be more important that creation date in most cases so would make more sense to appear on top. If it's a small fix and easier to address under this task then let it be here.
Jul 16 2024
Good catch @dom_walden! I didn't create an error state for that. It should be a standard error state with all the fields and submit button enabled again with error text "Looks like you don't have internet connection. Please connect to the internet and try submitting the form again"
Jul 12 2024
@Samwilson I'm. not able to visualise how it will look and if it will add any extra benefit to the user. Would it be able to see a sample screenshot to understand where the ToC is required?
Also, can the last updated date be placed before the created date on the wish detail page? I feel this is more important than creation date.
@MusikAnimal @GMikesell-WMF thanks for the detailed explanation. Agreed after seeing the use case that the link can stay. When I tested it earlier, the link wasn't showing up from anywhere else except from the wish detail normal view. An I feel in that view it's least important cause advanced editors will probably not use the form anyways to edit. I was going with the UX best practice of not having the same entry points multiple times on a page. If you think strongly it will help users access the form from different views, it can stay.
Jul 11 2024
Jul 10 2024
Jul 8 2024
Looks good now @MusikAnimal! Thanks. The rest of your points make sense.
Jul 5 2024
Jul 4 2024
I would say in this case we can add a disclaimer/banner on the form that says you can submit wish in any language and not add another form field that user needs to select.
Jul 3 2024
@MusikAnimal yes disabling the fields and the button while the form is submitting is fine. Do we have an existing loading state or do you need a design for that?
Looks good to me! Also, whoever fixed the spacing in the form, thanks to them!
Jul 1 2024
The table looks good overall. Here are some minor comments:
Jun 25 2024
@Samwilson @tstarling as far as I understood, we are going with the Meta style search for MVP, i.e. the search results are shown on a separate page and user can search based on wish title or description. Am I correct?
We can keep it "Publish" and "Save changes" respectively for submission and edit.
Jun 24 2024
Also, button text should be "Publish wish". Field level validation shouldn't happen when a user jumps to the next field but only after clicking the Publish wish button.
Jun 19 2024
Yes let's keep it all sortable in that case.
Jun 13 2024
Jun 12 2024
Jun 11 2024
Jun 7 2024
@JWheeler-WMF I am sitting with our DST designer Sarai and we discussed many scenarios. The more I tried to add different scenarios on the table the more I feel only sort option won't be enough. We will need a filter for at least project and status. For an even better and scalable UX we will need a filter on Focus area as well.
This is the first exploration of wish index.
Jun 5 2024
Assigned this task to me as I will start exploring some design with the new table component which is now ready by Codex design team. I will assign it back to @MusikAnimal once the design is final.
@JWheeler-WMF We dropped aggregate rating from the focus area. The description should be updated I think.