Changes at "Let's go impulse shopping for budgeting projects"

**Is your feature request related to a problem? Please describe.**

The budgeting part of a PB process seems to be very specific to each municipality. Some want to divide the budgets by area, some want to divide it by theme, some want budgeting voting, some want project based voting. It is great that now we can configure the budgeting component to answer these needs.

The problem dividing the budgets raises to some users (this is an actual user feedback) is that the don't necessarily know in which budget they want to vote. It is not always e.g. the area they are living in. They are also more interested in the projects themselves, not the area or theme they belong to.

The user feedback states that some users would like to \"go shopping\" for the projects, which means that they would see all the projects in one view where they could already start picking interesting ones to their \"wish list\" if you would compare this to a normal online shopping experience. Then, they would pick the actual projects to be voted on based on their wish list.

**Describe the solution you'd like**

To solve the problem, there would need to be two different \"modes\" for the budgets component:

• Browsing mode where you would see all the projects from all budgets and be able to filter them using the filtering options. Here you could potentially also filter by budget if you'd like to. In the browsing mode you would have a separate button that would allow entering the voting mode.
• Voting mode where you would actually cast the vote, almost as if you would do right now. Some changes would be needed in order to take the projects in the \"wish list\" into consideration during the voting. These are the projects the user would primarily want to vote on.

**Describe alternatives you've considered**

The behavior of the UI is still being planned currently so there may be some alternative ideas that come to this. Regarding the need itself, I don't see currently options in Decidim to answer these needs.

**Additional context**

This idea comes from the collected actual user feedback that states some of the users had a hard time finding projects they like.

This proposal is more of a starting point for discussion as I didn't find any better place to put it to. The idea is to see if there is some interest in the community for this kind of feature, so we could collectively think how something like this could be incorporated into the core features.

**Does this issue could impact on users private data?**

No.

**Funded by**

Possibly funded, depending on the direction. We will need to implement it based on the client needs but if it resonates with what the community wants, we could incorporate parts of that back to the core if there's a good way to do it.