New navigation architecture: separating menu and breadcrumb
We propose redesigning the navigation system in the frontend to make it more intuitive, scalable, and user-friendly. The goal is to clearly separate global site navigation, local process navigation, and contextual breadcrumb navigation, allowing users to better understand where they are and how to move through the platform.
Is your feature request related to a problem? Please describe.
The current frontend uses a mega-menu that combines multiple layers of navigation into a single component. This leads to confusion, and it is especially suboptimal on mobile devices, where the navigation becomes even harder to use due to the stacking of multiple navigation levels in one component.
Describe the solution you'd like
The proposal is to decouple the current mega-menu and introduce a clear, scalable navigation architecture that separates:
Menu: a persistent menu to access menu items such as Home, Processes, Assemblies, Initiatives, etc.
Breadcrumb: a contextual component that helps users understand where they are within the site’s structure.
We are currently exploring different solutions for in-space navigation (e.g. navigating within a participation space), and feedback and UI proposals are welcome! For the first iteration we'll keep the current content block.
Describe alternatives you've considered
We also evaluated keeping the global navigation always visible on desktop (without using a hamburger menu). However, after benchmarking with other platforms and testing with Decidim instances featuring complex structures, we believe the proposed solution -a consistent, responsive global navigation with a collapsible menu- offers the best user experience across all devices.
Additional context
Here is a high-level prototype for review and feedback:
💻 Desktop
Does this issue could impact on users private data?
No
Funded by
NGI
Liked by
Share