Skip to content

Test Sidebar-Nav vs. Top-Nav

As a visitor, I need a clear and simple way to navigate so that I can discover and access all content.

As an author, I want a direct, declarative interface to manage navigation points so that I can adapt to content changes and user needs.

As a developer, I need the navigation functionality to be as local, declarative and uncoupled as possible to ensure long-term maintainability.

blocks #115

Acceptance criteria

  • Discoverability: Users can easily find out what content the site has to offer.
  • Accessibility: Users can access and operate the navigation(s).
  • Simplicity: Navigation is not unnecessarily complex or cumbersome.
  • Comprehensiveness: Navigation includes all relevant pages.
  • Delight: Users enjoy navigating.
  • Consistency: Users can develop a mental model of navigation and the site always matches the model.
  • Maintainability: Authors can easily manage the navigation options declaratively, and the functionality has a high code locality and low coupling.

Implementation

  • Two ways of displaying the main navigation have been designed and implemented already.

    • Flupsi designed and implemented the navbar on top of the page. It can hold up to 7 items (less is better). Portal-style pages such as an "articles portal" or "project portal" will be needed for visitors to discover and access all nested pages. The main motivation was to keep the Ui as frugal and static as possible, and to let authors design portals for the different realms of the site as they develop and grow. The main way to find content directly would be the global search function.
    • Francesca designed a collapsible sidebar which offers 10-30 items. The idea was to expose more of the breadth and depth of the activity in the association.

  • Add a feature flag

    • The most accessible would be a URL flag such as ?sidebar which would activate the sidebar instead of the top-nav. It will take 1h to implement.

  • Carry out supervised tests

Edited by Flupsi