We now have a block for quickly navigating to a given project. It provides a drop-down with the various projects listed, divided into modules, themes, etc. Select one and click a button to navigate to it. It solves a common need: I already know what project I want to get to (to submit an issue, or download a file).

Should we enable the block and give it a try?

Comments

Chris Johnson’s picture

Chris Johnson commented

Those are my most common two use cases, so I would like to see this navigation block.

Thanks for all the great work on project, Nedjo!

killes@www.drop.org’s picture

killes@www.drop.org commented

On which pages should the block be displayed?

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Good question.

If we had role-dependent block visibility, I'd say do so on the home page for logged-in users :).

I guess to start off we could just put this at project/*. Users have already had to load a projects page before seeing the block, but at least once they're in they have a shortcut.

Other suggestions?

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Component: web site » Site organization

We could enable this as a user-configurable block, off by default. It could go at the lowest weight of the left region. It's really of use to regular users rather than new ones.

A concern, though, is that it's a lot of content to load, now that we have so many projects.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

+1
but I'd like to propose to only load projects that a user participated in, i.e. depending on issue tracker as already provided here for CVS commits.

Another option I see would be to implement Favorite Nodes on D.org, so each user is able to build an own list of projects. The module is very lightweight, easy to use and understand and works very well.

Thought more about that, I'm preferring the latter way.

silverwing’s picture

silverwing commented

Two years old... methinks that things have changed a bit since it was first submitted and that the requested actions (in the OP) won't be part of the redesign.

Tempted to 'wont fix' this.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (won't fix)

There are already some project-related blocks that are visible on /project/*, but I think none of them are the navigation block the feature request is referring to.

If the feature has not been implemented in two years, I would rather think it will never be implemented, considering also what silverwing said in his comment.

I am marking this report as won't fix; feel free to re-open it if my conclusions are wrong.