Saltar al contenido principal

Configuración de cookies

Utilizamos cookies para asegurar las funcionalidades básicas del sitio web y para mejorar tu experiencia en línea. Puedes configurar y aceptar el uso de las cookies, y modificar tus opciones de consentimiento en cualquier momento.

Esenciales

Preferencias

Analíticas y estadísticas

Marketing

Community Meeting 3: Sistemas de navegación y menús (Proceso de Rediseño)

Avatar: Encuentro oficial
Encuentro oficial

Invitamos a toda la comunidad MetaDecidim a este encuentro para conocer los primeros resultados del trabajo hecho hasta ahora para el Proceso de Rediseño. Presentaremos las primeras propuestas de diseño, que servirán como punto de partida para debatir sobre sistemas de navegación y menús.

Recupera el vídeo del encuentro:

Adjuntamos una presentación donde se explica el análisis hecho y los motivos que estructuran la propuesta. 

🖼 Mira la presentación del mockup en Figma

El equipo encargado del rediseño presentará el mockup:

  • Álvaro Ortiz (Fundador de Populate)
  • Rober González (Diseñador de producto en Populate)

En este encuentro contaremos con una fila zero de expertas en UX para que nos ayuden a abordar el debate y analizar las propuestas. La comunidad también podrá dar su feedback y participar del debate.

Las personas que conformaran la fila zero son:

  • Stiliana Mitzeva. (Ilustradora y diseñadora gráfica freelance)
  • Laura Vidal. (Diseñadora, ingeniera y fundadora de Atelier Gelb, estudio especializado en el diseño UI/UX para productos digitales).
  • Nadia Nadesan (Investigadora y coordinadora de interacción digital. Experta en redacción de informes e investigaciones, creación de narrativas digitales y redes sociales. Trabaja en la fundación Platoniq)
  • Judith Membrives. (Formación en comunicación, multimèdia y filosofia. Es experta en UX y ha trabajado como investigadora en experiencia de la persona usuaria. Actualmente es tecnica de digitalización en LaFede.cat)
  • Ana Pina Bello (UX writer / Content writer de Prodigioso Volcán)

La sesión será en inglés.

(Sessión online)

⏩ El debate continua abierto en el proceso de rediseño, participa!

Estructura de la sessión

1. Introducción [16:00 - 16:10]

2. Presentació del mockup [16:10 - 16:30]

El equipo de rediseño explicará primero el análisis hecho para después profundizar en las propuestas concretas de rediseño.

3. Feedback fila zero [16:30 - 17:00]

4. Trabajo en grupos [17:00 - 17:45]

Debates en grupos de 8-5 personas

5. Conclusiones [17:45 - 18:00]

Acta del encuentro

/Group work

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

Header

  • 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

Breadcrumb

  • 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

Confirmar

Por favor, inicia la sesión

La contraseña es demasiado corta.

Compartir