Community Meeting 3: Navigation Systems and menus (Redesign Process)
We invite the entire MetaDecidim community to this meeting to get to know the first results of the work done so far for the Redesign Process. We will present the first design proposals, which will serve as a starting point to discuss navigation systems and menus.
Retrive the video of the meeting:
Attached is a presentation explaining the analysis made and the reasons that structure the proposal.
The team behind this redesign will present the mockup:
- Álvaro Ortiz (Founder of Populate)
- Rober González (Lead product designer at Populate)
We'll also invite the following UX experts to help us address the debate and analyze the proposals:
- Stiliana Mitzeva (Freelance illustrator and graphic designer based in Barcelona.)
- Laura Vidal (Designer, engineer & founder of Atelier Gelb, studio specialised in UI/UX design for digital products.)
- Nadia Nadesan (Experienced freelance writer, researcher, and digital engagement coordinator. Skilled in Report and Research Writing, Digital Narrative Creation and Social Media. Member of Platoniq foundation)
- Judith Membrives. (She has a studied communication, multimedia and philosophy. She is an expert in UX and has worked as a researcher in user experience. She is currently a digitalisation technician at LaFede.cat.)
- Ana Pina Bello (UX writer / Content writer de Prodigioso Volcán)
The community will also be able to give feedback and participate in the debate)
Sesion held in English
⏩ The debate continues in the redesign process, participate!
Structure of the meeting
1. Introduction [ 16:00 - 16:10]
2. Mockup presentation [ 16:10 - 16:30]
The Redesign team will first explain the analysis done and then elaborate on the concrete redesign proposals.
3. Dialogue with the experts [ 16:30 - 17:00]
4. Group work [ 17:00 - 17:45]
Discussions in groups of 8-5 people
5. Conclusions [ 17:45 - 18:00]
Notes from Group 3 (Carol's group) — our group notes got lost but here's an attempt to recap from memory :)
- Eero, Javier and Torben are quite new to the community, so they don't have any strong opinion about the current design.
- Nadia was asking how many sections would be ideal to deal with at once? How does a participant find out which options are available for participation?
- Having simultaneaous actions might make times sometimes, some other times not.
- So it might make sense to be able to hide actions depending on the instance.
- Mobile navigation: when the menu is unfolded the background color changes, so it might appear that there's a disconnect.
Breadcrumbs menu: people like it
Notes from Group 1 (Arnau):
Attendees: Virgile, Antti, Anthony, Arnau, Alma,...
- Anthony (Switzerland): When the design will be implemented? Concerned about costumization possibilities from the admin side like we can do with Decidim Awesome using CSS.
- Virgile (OSP): Were the changes based on user research ? Is that research publicly available ?
- Arnau: Populate conducted some based on meta.decidim.
- álvaro: actually it was over decidim.barcelona
- How to involve the community in these ?
Main pain point regarding navigation :
- User can't grasped the complexity behing processes / assemblies
- Solution have a homepage block that explains what are the different participatory spaces
- Navigation inside processes, user are not sure what they have to do or can do
- Solution using content blocks for process page so you can build a landing page with a call to action, a description etc.
- Antti : points out the need of costumization of main manu for instance that have lower complexity (only one active process).
- Importance to focus on accessibility on hover navigation menu to enable navigation by tab, careful about hover for mobile and tablet navigation.
Worried about language selection at the bottom of the page.
- álvaro: the trade off we are thinking about is having an option that is rarely used taking too much and too important space, or moving it elsewhere. We also are evaluating having it on the dropdown (when the user is logged in). I agree that paricipatory concepts will need to accompany non-technical people to make them feel comfortable when they land on the page. For me the solution is to have the contextual help present from the beginning.
- Virgile: What happens with hover menu when you are in a participatory space https://i.imgur.com/HMx9d3N.png
- álvaro: No. The idea is that this is a static intro to the space. Actually, in the very last version, the side menu is in the other side, so this confusion goes away and it's clearer is just a menu.
- virgile : it looks cool but I'm unsure how it will behave in real conditions. I feel it's a bit redundant with the content of the page
- álvaro: it will be redundant if you are in the home of the space, not so much if you are in any other page (if you have arrived to a proposal with a direct link, we think it gives you a nice map of the process)
- The future pages won't display any header banner (they contained the steps, the cta, the title the subtext) ? We'll see... :)
Notes from Group 2 (Andrés):
Attendees: Andrés, Pauline (OSP), Michele (Milano), Paolo, Ruben, Dani (aLabs), Tayrine, Stiliana
- There are doubts regarding how the user profile would behave in the header.
- Icons should always have supporting text, except when they're really recoginsable (like maybe "home" and "search")
- Should "Meetings" and "Activity" be in the main navigation mobile header?
- How about the "Help"/"FAQs" pages, if the person doesn't know what's a process/initiative/etc. Would we add another help section (taking care that it doesn't pollute the page too much).
- It'd be nice to reserve some space in the header menu to add a support chat
- We generally like the breadcrumb change, but there are doubts about the hover behaviour in the breadcrumb (the fact that sometimes you have submenu on the hover, sometimes not)
- What happens when a space doesn't have any component, for instance an assembly with only subassemblies? How ther breadcrumb would behave?
- The "New proposal" button: is the idea to have it customized in the admin as it's now? Would it also be in the process homepage?
- Regarding the components order, it's important to have this feature as an administrator, to be able to sort the components
Report inappropriate content
Is this content inappropriate?
You are seeing a single comment
View all comments
Conversation with Carol Romero
Hi Vera, regarding your questions:
👉 Will you use View Components? (viewcomponent.org)
Yep, we will migrate from Cells to View Component :)
👉 Will each tenant be customisable independently?
Yes, each tenant will be customizable. In fact this is already the case now (leaving aside some CSS customizations at the instance level), changes to the general appearance are made from the admin of each tenant, and this should not change.
👉 Which of the elements shown in this design could be customizable by admins?
Right now we are just tinkering with the design and have yet to figure out how it translates into implementation. It will be something we'll address later on.
👉 How will accessibilty concerns be implemented?
- Will menus be navigable by keyboard?
- Will elements have "aria" attributes for screen-readers?
- Could the admin have a color contrast analiser tool? (e.g. "Please choose a different secondary color to improve readability")
Correct, the idea is to extend and improve the accessibility aspects, some of which are already implemented (ARIA labels, keyboard navigation).
Overall, some of these issues are not yet clear, and we'll address them as we move forward.
Sooo many thanks for taking the time to answer my questions 💜 heheh I think I'm so excited about this new design that I already want to dig deep into the implementation details 🤓 😌 but I understand this is not the current phase of the process ;)
Ahahah we all are! I think as a community we have been waiting for this moment for a long time 💫
Loading comments ...