Redesign Decidim
🎨 Community participatory process for contributing to the Decidim redesign
In your experience, what are the 3 most important UX pain points that you detect in Decidim?
We begin the participatory redesign process by making a general diagnosis of the main UX pain points in Decidim.
The debate was closed on 11/01/2022 18:03 with these conclusions:
Thank you all for your contributions!
It has become clear that the challenges to improve Decidim's usability are many and we must face them in order to make a qualitative leap. The team in charge of the redesign has been following the debate and has taken into account the contributions to start working. As a result we have the first Mockup where the navigation system and menus are redefined.
Please focus on naming 3 pain points to narrow down the debate.
✨Participate and help us make Decidim more user friendly!
List of Endorsements
Report inappropriate content
Is this content inappropriate?
Close debate
What is the summary or conclusion of this debate?
Comment details
You are seeing a single comment
View all comments
Conversation with Nil Homedes
I would just like to add two points that weren't mentioned
1) Success and error messages:
Participants usually don't see the error/succes messages that now appear below the navigation menu. So they don't know why they are not moving forward and this could be frustrating. Some questions to adress that problem are: How can we use callouts effectively to improve PX? Should succesfull and error messages be displayed as a pop-up?
2) Admin dashboard:
- Acceptation of the Terms and Conditions in the admin panel. 80% of the time new admins didn't see where to accept the Terms and Conditions.
- Child assemblies. The button to access child assemblies is confusing. Maybe a good solution could be display a drop-down list of child assemblies.
i would say 99% hahahah
Loading comments ...