DROP Task: Review "Contribute" link and make recommendations
webchick - February 17, 2008 - 05:15
| Project: | Documentation |
| Component: | Misc |
| Category: | task |
| Priority: | normal |
| Assigned: | birdmanx35 |
| Status: | closed |
Description
This task is intended for a new contributor only! If you're on the documentation team, you roll/apply patches, etc. then please don't take this task. :)
I'd like someone with "new" eyes to look at our Contribute page and make recommendations on how it could be improved. Please specify:
* Parts you found confusing, with recommendations on how they could be made more clear.
* Stuff that's just plain wrong.
* An analysis of at least 2 other open source projects' "contribute" sections, and how Drupal's compares, and make further recommendations from that.
#1
#2
Here's the pdf I made for this task.
I realized only after that you wanted a new person- my level of contribution is debatable, but if you want, you can discount this task; I don't care, it was fun anyways :P.
#3
#4
Okay, needs work as per discussion with Webchick.
#5
Oh, right. Discussion. Here's the jist of what I said in #drupal:
webchick: birdmanx35: so regarding http://drupal.org/node/222761
webchick: birdmanx35: The first problem is that I asked for *new* contributors, rather than old contributors. But since you're still pretty new (not like a chx) then you will do. ;)
webchick: birdmanx35: I'd like to see a couple screenshots to illustrate the difference between Python/Joomla's contributor sections and Drupal's, preferably with little arrows or something to draw specific attention to areas that they're doing better than us.
webchick: birdmanx35: It would also be neat if you could mockup your new vision of the Contribute page, including *specific* icons, rather than just tossing a screenshot of all of them on there.
webchick: birdmanx35: The final piece of feedback I have is that you're focusing a lot on the *presentation* of content, which is good, but I'm also (and in fact more) interested in the *content* itself. Click on all the pages, read the text that's there. Do you now understand how to contribute documentation, or patches, or testing, or..?
webchick: birdmanx35: So ideally we end up with a set of issues that's like "fix this about this page, fix that about that page"
webchick: birdmanx35: The idea being, "Let's get this section in shape so that new contributors have some starting information out of the gate."
#6
Okay, this is the revised report. In the attached zip file, there are two files, the mockup html file and the report. I believe this incorporates all the suggestions mentioned in #5.
#7
Urgh, here goes the proper version.
#8
Wow, this looks completely awesome. Great job on this!!
Marking fixed. However, I'd recommend you propose and mentor some follow-up GHOP tasks to actually implement some of the changes you've suggested here: a contributor spotlight image, a redesign of the main contributor page, corrections/enhamcements to the text, etc.
#9
That sounds like a great idea... for DROP, not GHOP, though ;).
Just wondering though, enhancing the text requires more than the doc team status.... even adding the images requires more than that.
#10
Yes, making the actual edits would require someone with site maintainer status, but full HTML mock-ups of the content area of the page, as well as edits to text could be submitted as comments in issues, then taken care of by someone on the site maintainer team later.
#11
Okay, will do. Thanks for the bonus points, by the way!
#12
Automatically closed -- issue fixed for two weeks with no activity.