mockup: developer.drupal.org

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
webchick's picture

If we decide to go with the concept of 'landing pages' for each target audience, here's an idea of what the developer.drupal.org portal might look like. You'll notice that it's missing stuff like "latest project releases", but that's because those are going to go in something like download.drupal.org. ;)

developer.drupal.org landing page concept

AttachmentSize
developer-portal.jpg260.24 KB

Comments

Looks great! :)

Dries's picture

Looks great! :)

Latest Project Releases

Jon Pugh's picture

While obviously, latest project releases should be on download.drupal.org, I think it would be quite helpful to be able to browse the latest project releases on developer.* as well. Perhaps a bit more fine tuned, so that we can find pre-release versions, find out what milestones have been reached in each new version, etc.

Since we're already seeing the latest individual CVS messages, and we now have sweet version releases for projects, do you think it would be helpful to see all the latest version releases? (even if they are not official releases destined for download.drupal.org)

As a side note, I know that the initial drupal user is as overwhelmed as I was at first at the sheer number of available contrib modules. I think we should implement some kind of system (perhaps based on drupal.module install counts plus some voting/moderation) that puts extremely useful or commonly used contrib modules on more up front display for the more general public to find. I know this topic has been discussed before, but now that a redesign of drupal.org is in order, perhaps its time to have that discussion more seriously.

I know that even now, it can be time consuming to visit each section to just pull down the latest version of views, cck, cck field modules, image modules, etc., which is something I try to do everytime i start a new site, just to stay up to date.

Having all of the primary contrib modules that virtually everyone uses on display up front on download.drupal.org would not only be helpful for regular drupal site devs, but it would cut down on all "What module should I use for this?" questions.

my $.02

g


Jon Pugh
Founder & CEO
THINKDROP
open source consulting
http://thinkdrop.net

My issues

ChrisKennedy's picture

As a marginally related comment, imo "My issues" should be moved from the contributor block to the navigation block. It relevant to many people who are not contributors but who have filed bugs or support requests into issue queues. It is also much more useful than "My projects", for example, which I think should be moved to the contributor block.

Disagree

dwees's picture

I Disagree, I always click on 'My Projects' before I click on 'My Issues'. I prefer to know what work I have ahead of me, rather than what work people have done for me.

Dave

Let's measure the links and reduce the unpopular ones

Amazon's picture

Hello, a classic approach to solve this problem is to identify only the most used links and then make use of information discovery or gradual disclosure.

I count about 50 links on the home page for anonymous viewers and about 70 links for authenticated users. I could make a list of AWSTATs URLs on Drupal.org available to someone they wanted to make measure and categorize the use of those links to better design IA. I assume this take 2-4 hours to compute and report back in a way that people could understand. This is a manual way of doing a heatmap.

Cheers,
Kieran

To seek, to strive, to find, and not to yield

New Drupal career! Drupal profile builders.
Try pre-configured and updatable profiles on CivicSpaceOnDemand

My issues

pnm's picture

I agree that "My issues" doesn't belong in the "Contributor links" block. My "My projects" is empty. It explains, "You have no project," which doesn't help.

Here's my story: I want to work on documentation. I'd like to be a contributor but not a developer. I don't commit CVS. I try to read the documentation queue. I also read individual issues, but mostly through searches or links. I'm interested in three things: (1) items of interest to users, (2) documentation team related items, and (3) general items of interest to Drupal users and developers.

I'd suggest renaming the block to "Developer links." Then, keep links there that are geared toward developers and move links that are geared toward users, documenters, and people who might submit a patch or two — or more precisely, Drupal.org users in general — to a different block.

planet for devs

moshe weitzman's picture

i'd like to see some way for developers to be able to post into a box on this page. we should have a developer aggregation like planet which routes into a box here. same for other wireframe sections ... looking good.

Thank you for the great work!

Thomas_Zahreddin's picture

Hi webchick,

I like your work and your structured style.

For the blocks Latest Core CVS Messages, Latest contrib CVS Messages and Latest support requests - who will realy need that data ? For the most developers these aren't interesting. So give these date a place where they are informative for the persons interested in.

What is more interessting (in my opinion) for all developers is Information about
- new modules
- Changes In Drupal API
- Requests for new features for Drupal

in the block 8 , my personal stuff
here I'm interested in
- latest cvs - changes on moduls i contribute or I use (like i subcribed)
- latest support requests to modules I contribut or i use
- latest patches and bugs of modules i contribut

this I would prefere for the most right colums.

Best
Thomas

I don't think CVS messages work for that

Chris Charlton's picture

A block for tutorials, or latest themes, or latest modules would probably be better content choices than the CVS messages but the overall layout seems nice. :)

Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant

I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us

profile-driven blocks

Chris Charlton's picture

Just realized the note on Jeff Eaton's idea of profile-driven blocks. I totally agree. Maybe users would like to mark themselves as "Developer", "Designer", and contributors can get a "Contributor" flag.

Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant

I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us

Jumping area to area

Chris Charlton's picture

I'm suggesting direct jump links to the Modules area from dev, same with the API search/docs, and "handbook" documentation. Section-specific or similar.

How about an API search block/option on the home of dev.d.o?

Chris Charlton, Author & Drupal Community Leader, Enterprise Level Consultant

I teach you how to build Drupal Themes http://tinyurl.com/theme-drupal and provide add-on software at http://xtnd.us

DEV == Queues -> Progress

sun's picture

I like that "Latest support requests" block, and we should think about possible ways to mash-up more of such queue contents (think Views 2 UI for example).

Since I maintain and co-maintain a bunch of projects in contrib, and also trying to follow and participate in core development, I needed to setup several bookmarks that allow me to access all of those queues:

My projects w/o fixed: http://drupal.org/project/user/sun?states=1,16,8,13,14,15,4
My projects: PNR+RTBC: http://drupal.org/project/user?states=8,14
My projects: PNW: http://drupal.org/project/user?states=13
My projects: support issues: http://drupal.org/project/user?categories=support
My projects: needs more info: http://drupal.org/project/user?states=16
My projects (co-maintained): http://drupal.org/project/issues?projects=260942,74958,3254 [,...]
My issues: http://drupal.org/project/issues/user
My issues w/o fixed: http://drupal.org/project/issues/user?states=1,16,8,13,14,15,4
Drupal w/ sun: http://drupal.org/project/issues?projects=3060&participated=sun&states=1...
Drupal RTBC: http://drupal.org/project/issues/drupal?states=14
Submitted by sun: http://drupal.org/project/issues?states=1,16,8,13,14,15,2,4&submitted=sun
Assigned to sun: http://drupal.org/project/issues?states=1,16,8,13,14,15,2,4&assigned=sun
Issues w/ unleashed mind (all projects, all states): http://drupal.org/project/issues?states=1,16,8,13,14,15,2,3,4,5,6,7&part... [,...]

You probably can imagine that it's a pain to go through all of these lists separately all over again. I'd love to see those queue links directly on drupal.org. Even better would be direct views output, but I fear that's out of scope for the re-design...

Also, not really a "queue", but related: "Latest development list posts" along with a link to the archive would be a very interesting content, since the mailing list is also a very valuable resource.

Daniel F. Kudwien
unleashed mind

Daniel F. Kudwien
netzstrategen

It's not really out of scope

catch's picture

It's not really out of scope - while MBD is only dealing with high-level stuff, everything past PSDs has to be done by us, so anything like this can be factored in somehow. Clearly having easy access to the various issues we might be interested in is important to save developer time being wasted, so needs to be thought about.