Aquest lloc web fa servir cookies pròpies i de tercers per millorar l’experiència de navegació, i oferir continguts i serveis d’interès. En continuar la navegació entenem que acceptes la nostra política de cookies. Per a més informació consulta aquí.
13 comentaris
Conversa amb Virgile Deville
This is crucial for mobile navigation. I fully support this proposal
The browser's back button, or mobile, is not doing this job? as it should return you back to the page
Hi @agustibr, not necessarily, you can click on the link of a proposal (on social media or on the homepage), so you would return where you came from.
The goal here is to be able to get directly on the index from a proposal/result or else.
Conversa amb Carol Romero
Hi, thank you for the proposal!
From @product we see the need that in a platform with a navigation as rich and complex as Decidim, the participant can be situated at any time. That's why we think that a solution would be to use breadcrumbs, not only for the components browser, but in all pages. This way, either because you get directly to a content through an external link, or because you have been navigating through the menus, you know exactly where you are and you also understand the structure faster.
A mockup exampe on desktop would be something like this:
https://imgur.com/nOCN32X
As in mobile breadcrumbs can be quickly wrapped in several lines and occupy valuable space on a mobile screen we could opt for one of the 2 most common solutions:
- Shorten the intermediate items of the breadcrumb, as in rei.com, which has a rich hierarchy of content on desktop, but trims the intermediate items for mobile ( m.rei.com ) while still presenting a full featured breadcrumb.
Mockup exemple: https://imgur.com/7fDqYlT
- A single breadcrumb pointing up a level.
Mockup example: https://imgur.com/ICxFItZ
Hey guys thanks for reply,
We brainstormed about this with @Pops , a breadcrump should definitily be implement as it is an accessibility practice from WGAC.
BUT, the breadcrump and the return to the list button have 2 different user stories :
- Return to list user story : I've visited a proposal (project / blog / meeting / debate) page and I want to return to the list
- Breadcrump user story : As a user I want to know where I am in the decidim arborescence (I might want to go back to the process list page but my clicking.
My opinion is, these are two different features that are compatible.
To go more in details, Decidim is great you give a specific name to your features, a breadcrump that prompts me a link "proprose new feature" will make no sense if as I a user what I want is "go back to the list" furthermore in the mockups the redondancy of "propose new features" in the menu and on the return link is very confusing.
Also on the module, "Accountability" there already is a breadcrump (we decided not to implement the return to index button on this one because of this) adding another would be weird.
Lastly, we are ready to make a PR with the spec outlined above 😅
Hey, guys, sorry I couldn't answer before. Regarding what you're saying @virgile_deville, I think that would be solved by changing the name of the menu items. If instead of "propose new features" you use "proposals", the breadcrumb would be: Home > Processes > Propose new features > Proposals. I'd say that this leaves little room for confusion, whether you come from outside or inside.
Since we didn't have a call to action from the process header before, in this process we used the menu item as a CTA, but actually it would be more appropriate to use "proposals" or "features", just as we have "debates" or "meetings".
Having said that, I fully understand that this may exceed the scope of this proposal. But I sincerely think that this would be a better solution because it improves the whole navigation system on the platform and not for a specific case of returning to an index.
And since this is not a question of faith either 😜, it would be good to be able to do some tests with participants. We are thinking about developing self-testing kits with a researcher in user experience, so that we can make some decisions based on data.
Hi @carol thanks for the reply.
I rest my case though "Return to index" is a user story in itself.
Until a breadcrump is implemented would you accept our PR for the return button ?
Well, if you're asking me :D it is true that without being the optimal solution, it partially solves the problem, so I'd say yes to PR, and in the medium term let's address the implementation of breadcrumbs in a homogeneous way throughout the platform, including the accountability module.
However, please take as a reference the same style that we are already using in participatory texts, here is an example: Article 2. Finalitat
(I'll confirm you tomorrow after the product meeting)
Hi @carol,
This is the PR: https://github.com/decidim/decidim/pull/5591
Do you approve?
Hi there, I've checked the PR. This is approved by Product. Thanks!
Deixa el teu comentari
Inicia la sessió amb el teu compte o registra't per afegir el teu comentari.
Carregant els comentaris ...