Categorization of Work on the proposals page

[CharpentierLucas]

@tkrieck

This discussion started originally about how to see all available proposals about UI/UX (or that are in the stage of UI/UX definition). A “Master” page was originally proposed, but that would lead to some problems, specially duplication of work to keep the page updated.

So, what would be needed is a way of filtering the proposals page to only show UI/UX ones.

We have the “Design” type, but it is not about UI/UX and more about Architecture. Now, when discussing this in the XS chat it was pointed out to me that “Type” should be a progress indicator, meaning that a proposal is evolving during its lifecycle.

AFAIU after looking a bit more at the proposal object, we should already have a way to filter given the info is up to date, but those filters are far from quick to figure out and not very reliable if we don’t keep all the proposals updated.

My idea on what we discussed yesterday was to have a page with pre-filled out filters for the few use case we have frequently. It would definitely not need to be a landing page but it would be a good util to avoid losing time finding filters (or the favourite you spent time to setup with the right query)

With Add a new "Accepted" xproperty on design.xwiki.org we added the accepted field but it’s not always used:

https://design.xwiki.org/xwiki/bin/view/Main/WebHome#

I’ll try to come up with a personal checklist of things to do when starting the implementation of an agreed UI/UX update so that I don’t forget any info to add and it’s easy to follow where the implementation is.

Thanks Thiago!