Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance the configurability of the top bar navigation #3074

Open
Cutuchiqueno opened this issue Sep 7, 2021 · 1 comment
Open

Enhance the configurability of the top bar navigation #3074

Cutuchiqueno opened this issue Sep 7, 2021 · 1 comment
Labels
Status: Accepted Reviewed by Manifold Team. In scope for project. We could complete this under existing funding. Type: Enhancement Issue represents new feature or expanded functionality.

Comments

@Cutuchiqueno
Copy link

As our press grows bigger we create more and more static pages, like pages for series and journals, FAQ, our Open Access policy, a website for the team of our press etc. We really would like to make most of these pages accessible from the top navigation. Unfortunately, this is extremely hard to realize, considering the limited configurability of the top navigation at the moment.

There are several issues which I would like to present as features for future development:

  • For us it seems most crucial to add the possibility to nest navigation points. As I outlined above a bigger press has many important pages. Just adding 3 points to the default set of 3 points already fills up the layout on lower-resolution screens (see screenshot of our navigation). Furthermore, the points are not semantically "on the same level". We would, for instance, like to hide "Commitment" and "FAQ" together with other pages under a navigation point "About". Neither can we do this at the moment nor can we add ohter points to the navigation, because it is just full. The only way to nest navigation at the moment would be to create a page that serves as a second navigation. This, however, is really intransparent and lacks usability.
  • Also important is the possibility to order navigation points. Since we can not control the order of navigation points at the moment it does not make much sense in our case. Having "Series" behind "Projects", although it is the more general navigation point, and, additionally, having it detached from each other due to the interfering "Following" and "Commitment" points in between, is not very intuitive.
  • Finally - this is not crucial but nice to have - it would be good to have the option to deactivate or at least rename the default navigation points "Home", "Projects", "Following". We, for instance, would really favour the term "Publication" over "Project" (especially in conjunction with our use of the term series). We would also like to hide the "Home" point, because a click on the logo just next to it already brings the user "home", and this is a common way of going back to the homepage.

I hope the request is convincing because we are about to misuse pages just to make accessible other pages and in order to facilitate deeper navigation.

image

@zdavis zdavis added Type: Enhancement Issue represents new feature or expanded functionality. Status: Accepted Reviewed by Manifold Team. In scope for project. We could complete this under existing funding. labels Dec 21, 2021
@zdavis
Copy link
Member

zdavis commented Dec 21, 2021

Thank you for taking the time to open this feature request. The Manifold team reviewed this issue during our bi-weekly meeting and the consensus is that this feature makes sense and is in keeping with our overall vision for the platform. Moreover, we see this request as a viable candidate for development under our current available funding. We’re adding an “accepted” label to this request to indicate that it’s within scope and possibly within budget.

The next step is for us to estimate the work involved with this and add it to our feature backlog. Our acceptance of the issue is not a promise that it will be implemented. We will balance this request against the other accepted requests and do our best to implement it within our current available funding.

This was an automated message, but please don't hesitate to reply. Our team watches these issues closely and will respond as soon as we're able to!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Accepted Reviewed by Manifold Team. In scope for project. We could complete this under existing funding. Type: Enhancement Issue represents new feature or expanded functionality.
Projects
None yet
Development

No branches or pull requests

2 participants