I asked more than 1,000 existing Drupal users (not Drupal prospects) what they would like to see improved on drupal.org. A prioritized wish list is provided below.

Drupal org wishlist

We also created a drupal.org redesign group: if you are interested in collaborating on a drupal.org redesign or helping with the drupal.org infrastructure, you know where to start. We have work to do!


Sanjeev Jain (not verified):

Based on the above suggestions, I think we should move to the Wiki model for documentation, meaning any registered user can update the documentation without going through queue/issue process. I have seen so many other projects succeed through loosley controlled method of creating documentation like Wordpress, Gallery and even my webhost Dreamhost.

However, if the Drupal Handbook coordinators don't want to do it. I am willing to create a separate domain drupalwiki.com or something to start the documentation. I am willing to fund it too. I just really like Drupal, and I think a wiki style documentation will make it even better. I think Drupal itself can provide all the functionality to make that website.

Frequently updated material via wiki model is going to provide more benefits to users than any that we currently get by controlled/queued method of updating documentation. If a whole encyclopeida can be created using wiki model, then why is it so hard for Drupal Administrators to realize that Drupal documentation can be improved too using wiki model?

sepeck (not verified):

I have supplied you with this information before but you continue to choose to disbelieve.

We already have this model. Today.

  1. We do not moderate any handbook page. There is no moderation in Drupal core so the fundamental assumption you are working with is false.
  2. Any registered user can create a handbook page. Any.
  3. You can edit any page you create.
  4. For the simple process of asking, you can gain rights to edit almost any book page. All you have to do is ask. This is documented.
  5. There is almost no control on the documentation contribution.
  6. I did allow all registered users for a few days. Handbook page vandalism was overwhelming. Even with the current minimal restriction (you have to ask) the latest seven day statistics show: In the past week, a total of 29 handbook pages were created. Of those, 22 were spam. Of the 7 added, 5 were created by people not on the documentation team.

    We have tried the completely unrestricted model. I have told you this repeatedly, still you persist. It was a disaster. Instead, we have a marginally restricted model. Anyone can create a book page. You can edit any page you contribute. If you ask, you will be granted rights to edit almost all pages.

    There are 129 people who have requested this right. You can join them for the simple process of merely asking...

themegarden.org (not verified):

Idea: splitting documentation in two parts:

  1. Drupal.org official documentation - created by some "elected" Drupal.org users.
  2. User (community) contributed documentation - every Drupal.org user can create/modify a handbook page - moderated by Drupal.org webmasters (to prevent spam).
moshe weitzman (not verified):

Very well said, sepeck.

On a different note, it is a crime that regular users can't use the image-tag on drupal.org (editors don't count). That is the biggest reason why our site is so text heavy. I bet the documentation score would improve if we made this simple change.

sepeck (not verified):

Well, there are over 129 peole on the doc team that can upload images and use the img tag as announced on the docs list. This does not count the site maintainers who have this access as well. Not that it is much use considering that the right hand blocks slide over everything.

Not sure if you have reviewed the latest additions to the handbook which are image heavy. Start here and click next.

webchick (not verified):

Docs team members have access to post images. Yet another perk of joining the docs team, aside from the ability to edit other peoples' handbook pages.

The fact that there aren't more images in the handbook has nothing to do with the inability for all authenticated users to post images, and everything to do with the fact that we need more docs team members, and specifically, more who are willing to put in the time to make graphics and diagrams.

SanjeevJain (not verified):
  1. I will request to be added to the documentation maintainer list.
  2. For SPAM, has the Akistmet plugin from Wordpress.com been tried for Drupal.org? It works amazingly well on moderating comments on one of my website.
  3. Adding Images to the handbook will certainly help. As they say, an image is worth 1000 words.
  4. I think we should replace Drupal search by Google Custom Search. Maybe test it out for a week or two. I think it will reduce half the complaints that drupal users have.
PieterDC (not verified):

Just for your information: point 2 (anti-spam measures) and 4 (search-functionality on drupal.org) have already been discussed heavily... I bet you can find relevant threads within a minute.

Amanda (not verified):

I don't know about any past discussions you've had with Saneev, but it has never been quite clear to me how I'd go about editing handbook pages (editing, not adding).

If it is documented, it could be brought forward a bit so that longtime Drupal and drupal.org users are clear on what is going on.

amanda (not verified):

On the tippy top of my wishlist (not that you asked sweet lil ole me): a direct link to my own recent posts.

I'm a lot more interested in whether anyone has responded to a thread I started or commented in than I am in recent posts to the site, generally.

At the very least, sometimes when I visit Drupal.org, what I really want to know is "has anyone commented on my support forum post yet?"

There are too many steps to get there.

bengtan (not verified):

Amanda: There is a trick which I just found out recently myself. From drupal.org, goto My Account >> Track >> Track Posts. There you will see everything you have posted to. Hope it helps.

Shai (not verified):

Anybody thought about doing some serious branding work which might include a re-design of the Drupal logo.

Obviously one only changes a logo very rarely if ever. But I do think there could be a lot of benefit to updating the logo.

Regarding a new template for Drupal.org, isn't Garland the obvious choice?


Anonymous (not verified):

I recently came across a nice Druplet Site that provides the ranking of drupal modules based on the number of views/downloads. It also has the search capability which is not bad.

Steve Kessler … (not verified):

There needs to be a part of the site that is accessible to people looking to use Drupal for their website and may be very non-technical. This should gather things into it like the gallery of Drupal sites, contractors list, Drupal statistics, major mile stones of the project and other information that an interested marketing director, sales director, etc. could go to and say "I may not get the tech side of this but this Drupal thing is a must have."

There needs to be more content for beginners. Investing some time in creating content for beginners will raise the quality of discussion on the boards (hopefully) because there will be more resources availible. I am working (somewhat slowly) on www.welcometodrupal.com and a lot of this content will be there but it would be nice to see resources on D.O.

Maura (not verified):

I second that. Also, I'd like to see more resources on the skills used in working with Drupal.

The hardest part of using Drupal's documentation and support features is knowing where to start. I'd like to see a system where people could answer a series of questions, with each answer determining the next question, to try to determine the answer to their question or solution to their problem or as a way of categorizing requests for support or features or bug reports.

This "series of questions" idea could also be used to help people find Drupal services that meet their specific needs and budget and determine if Drupal is right for them or what modules to use.