(Engineering notes)

This seems tantamount to the "Results" or "Tracking" pages, so I think the bot would be managing this page.

I should be able to paginate wishes (30)

That wouldn't work with a normal wiki page, but once the "dashboard" software is built we could certainly add pagination.

I should be able to search by title

One could utilize Ctrl+F for this, but for T363241: Wishlist Dashboard page v1 or T363240: Focus area index page we can add a "search proposals" box like we do at https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2023/Proposals

musikanimal opened https://gitlab.wikimedia.org/repos/commtech/wishlist-intake/-/merge_requests/22

Draft: Add more wishlist pages, templates and basic bot run

tstarling merged https://gitlab.wikimedia.org/repos/commtech/wishlist-intake/-/merge_requests/22

Add more wishlist pages, templates and basic bot run

@JSengupta-WMF the requirements here suggest adding project + category/type, etc, though the designs don't include this. How do you feel about this vs the table width tradeoffs?

I will update the table. Do we need all of the fields on the table though? It might reduce readability of the table.

Once "Focus ares" are a thing, we won't have much room for any other fields. Maybe we squeeze in "Type", but I don't "Projects" will fit, nor is it that useful to know from this page. At a later time, we'll have interactive filters and such that can filter by "Projects" or any criteria, regardless if they have a column in the table.

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.

This is the first exploration of wish index.

My thoughts on sorting columns:

• Title shouldn't be sortable cause it's not going to bring any extra value if people can sort wishes alphabetically
• Although focus are and type has sort options, I feel that filter will be a better feature in this case if somebody wants to see wishes by type or focus area. I also feel that Focus area sort is not so important cause if the user clicks on a focus area on the table, they essentially see another table with wishes within that focus area
• Project is a better candidate for filter than sort I feel again and so is status.

@JWheeler-WMF let's discuss

@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.

musikanimal opened https://gitlab.wikimedia.org/repos/commtech/wishlist-intake/-/merge_requests/82

Add template for wish type; update row template per designs

samwilson merged https://gitlab.wikimedia.org/repos/commtech/wishlist-intake/-/merge_requests/82

Add template for wish type; update row template per designs