Previously the Ideas where sorted under the modifications, but i think they deserve their own category. Not all ideas are modifications, but also not questions or troubleshooting. Maybe even include feature requests?
I really like the voting possibility on the old ideas posts, maybe thats possible with discourse as well?
Edit: I see voting is possible since theres a voting box above 
This is an interesting one, something I had already raised for discussion.
The challenge is that there usually arenāt that many requests and they tend to be posted across the various sections and languages.
We also donāt want to overly fragment posts by having too many categories.
It is probably more necessary to tag them properly - not sure if we have a feature request tag.
This isnāt currently on the rollout todo list, but adding a tag is easy enough.
Voting isnāt enabled on all sections just beta and the feedback section.
We will also need to check if we have enabled polls, which is a completely different mechanism.
Hi @chrigu,
I agree with Nick that there isnāt enough traffic to warrant its own category yet.
I do think itās important to easily be able to find them, so Iāve added a feature_request tag.
Also important to include the tag for the product so that the right R&D team can find it.
I tried one
why there is no Vote-button?
Like Nick said:
Thatās a bit contradicting, that feature suggestion has to be already in Beta-testing to be voted for implementation by the community.
Everyone knows the best source for new/great ideas comes from people who actually use the product everyday. No ācommunityā forum is complete without one central repository for them.
Hi @XFaktor
For now we have a tag that can be used - Topics tagged feature_request
There hasnāt been an overwhelming number that it has demanded its own category (which is how all the others have emerged).
Itās not easy to find that tagā¦
Itās way easier to find the category.
I would suggest to just create it and see what happensā¦ 
If no new features are requested just remove or merge it again.
I think I can predict what would happen,
People would post into it, and Victron would be perceived as not responding and implementing the requests in a timely manner.
Maybe some good ones come from it, but many will not, and we will also not be spending much time explaining why not, so then it looks like it is ignored.
And I donāt want to have a main category that is showcasing us apparently ignoring requests after it looks like we are inviting them by creating a special category for them.
There are a lot of really great things about Victron, but we donāt have lots of spare capacity for implementing end-user feature requests. Rather already we have a very large list of our own from our internal product directions, and some from our other channels such as commercial demand from our dealers and distributors.
I like that feature requests emerge from this community, and there are many very smart people here with lots of good ideas, but there is no process for me to be doing any kind of management of their implementation, nor for the R&D teams.
Itās already a pretty careful balance that is geared towards identifying bugs and issues, either in hardware, software, firmware, documentation and training. In that area where I think this community is really exceptional because they are very timely and experienced in the field by individuals, and then its super useful to have a fast and direct line of communication.
But that is already a lot for me to manage.
There is one or two exceptions, for example in VRM, where I have a lot more direct contact with the development team, and feel a lot more connected to the product (I am a daily active user), and the priorities. There I can be more receptive to feature requests, but I donāt expect there are more than the current structure can handle.