| Summary: | [pmi] Project "homepage" should have prominent "download" link. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Denis Roy <denis.roy> | ||||||||
| Component: | Project Management & Portal | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | nathan, wayne.beaton | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Denis Roy
Created attachment 231120 [details]
Download section on project page
What do you think of this?
The project can provide:
* An optional "downloads" message
* A link to their main download page
* zero or more links to Marketplace
* zero or more links to update sites (p2)
* zero or more links to specific file downloads
The different headings only appear if there is content to display.
I decided to try putting a "copy to clipboard" link next to the update site URLs, since these URLs are rarely clickable.
I'm concerned that it's a little busy. Thoughts?
FWIW, I'm trying to decide whether or not this is a duplicate of Bug 207108. (In reply to comment #1) > I'm concerned that it's a little busy. Thoughts? When I imagine this in addition to the Truck Ton of Data (tm) we have on the page already, I think this is more than just a little busy. I think we need to take the same approach here that I mentioned in Bug 404861. We should provide the project a way to provide the "Just give me the download link", and an extra section for the rest of the stuff we need to show that could be collapsible. Created attachment 231126 [details] Tabs on the project page Ian and I discussed breaking the page into tabs (see Bug 402535). This may be the tipping point that motivates making this happen. The idea is that the "Discover" tab is the starting point that contains the sort of information that users/pure consumers care about. The "Engage" tab is more for adopters/committers; we move the scope, releases, reviews, contribution information, mailing lists, etc. there. It might make sense to break up the "Engage" tab a little. But this is probably a discussion best suited for Bug 402535. > When I imagine this in addition to the Truck Ton of Data (tm) we have on the
> page already, I think this is more than just a little busy. I think we need
> to take the same approach here that I mentioned in Bug 404861. We should
> provide the project a way to provide the "Just give me the download link",
> and an extra section for the rest of the stuff we need to show that could be
> collapsible.
I think it depends on how the projects page is used. In my case, the project was using it as their "home page" ... and for that it's definitely too busy, and missing/obfuscating the info that a casual user wants.
If it's being used as an "about this project" page then it's fine the way it is.
+1 on either collapsing sections, or using tabs.
Nathan's "truck 970 kg" (adjusted for metric) comment motivated me to take a first crack at factoring the page into tabs. Adding downloads, I think, was the trigger to get that work done (the proverbial straw). I've added in a "Big Button" download link along with the ability to specify the other information I specified in comment #1 > * An optional "downloads" message > * A link to their main download page > * zero or more links to Marketplace > * zero or more links to update sites (p2) > * zero or more links to specific file downloads For completeness, I'll attach a screenshot. Created attachment 231168 [details]
Big Button download
Note that I took the colour gradient from the work that Chris is doing with the main download page (at one point, he was highlighing the default package in gold; I'm not sure it survived).
When clicked, this button takes the user to whatever value is provided in the "Downloads URL" field. This can be a web page, or a direct link to a download. I leave that to the project's discretion.
I've documented this in the wiki: http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata#Downloads Declaring victory... Works for me, thanks! |