I've been looking at an alternative to the long list of links at the bottom of project nodes. A lot of them seem to be linking to the same or similar pages:

out of 18 possible links that I saw:
5 linked to the issues page
2 linked to the issues submission page
2 linked to a list of releases
1 was an irrelevent link to a forum that probably doesn't exist on most installations.

for me the important thing is to be able to quickly find the issues page and the list of alternative releases, so I've tried putting them as tabs at the top. The list of links can then be shortened to a few relevent ones.

My work in progress can be seen here. There's still a lot of code tidying to do but you can see what I'm trying to do.

any comments anyone?

Comments

nedjo’s picture

Thanks for noting this issue and making suggestions. Your points are good. At the lease, the current links given are fairly drupal.org-specific and not necessarily wanted on other installs. Just what to include or leave out of a reorg, and what to leave to configuration options, might take some discussion.

dries’s picture

Your work in progress looks good to me. Two suggestions:
1. Add a 'subscribe' tab.
2. I'd consider renaming 'releases' to 'downloads'; it's less technical and therefore more accessible to the average user.

moggy’s picture

Status: Active » Needs review
StatusFileSize
new17.04 KB

I think I'd better stop now before this gets too big.

the patch covers the revised project node page, tabs to navigate round the project, and a couple of required tweeks to the breadcrumbs.

I think it keeps the current functionality of Project while making it slightly easier to navigate.

I keep finding little things wrong or that could be better, but I think a lot of them existed in the module before. Barring any major problems I think we could go with this and open new issues for each of the little things to be fixed as we find them.

Tobias Maier’s picture

+1 (just tested it on your testsite)
looks great and makes everything easier.

moggy’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new17.1 KB

updated to work with latest cvs

pfaocle’s picture

Title: declutering the project node page » De-cluttering the project node page
Status: Reviewed & tested by the community » Needs review

Didn't work on a test install of HEAD for me: must be a syntax error somewhere? I receive no output in my browser.

pfaocle’s picture

+!

Oops, forgot to say that I like the look of this from your demo. Makes going from project page <-> project issues much easier, and a tad less confusing.

pfaocle’s picture

StatusFileSize
new17.64 KB

Working now, another patch attached. Note I've not included some of moggy's comments/unfinished bits.

There is one slight amendment on line 236 of the patch: to provide a message (and therefore output and tabs) when there are no releases for a project. Without this, the releases tab returns no output if there are no releases returned from project_release_list().

pfaocle’s picture

StatusFileSize
new17.56 KB

Apologies for all these replies. Another slightly different patch (line 126 of patch) - breadcrumb item set as '/project', this won't work for sites in a subdirectory (as I've just discovered). Changed to simply 'project'.

drewish’s picture

Couple of things I noticed:
* Not sure if it was already mentioned, but the issue tab (http://test.xai-corp.net/node/28/issues) still isn't displaying any output.
* On the downloads/release tab (http://test.xai-corp.net/node/28/release) it seems like you could avoid the duplication of the "Test Project" on the title and then in the release name.

pfaocle’s picture

Status: Needs review » Needs work

Patch no longer applies...

agentrickard’s picture

Status: Needs work » Postponed

Consider this 'postponed,' since it is at least two versions old and no longer in active development.

senpai’s picture

Status: Postponed » Closed (duplicate)

The 'demo' link in the issue summary is a 404, and none of these patches will apply without being 100% re-written, so I'm closing this issue and pointing people to the work that's currently going on at #1545922: [META] Issue page redesign