This task is based on the findings shown at http://drupal.org/node/222761, where I reviewed our Contribute page and suggested improvements. One of the suggestions was to improve the content of the linked pages, so, based on that report (look at the final attached zip file), improve those pieces of documentation.
To get this task finished properly, you need to review the suggestions included in that report, improve the documentation (most of it is above doc-team status, so save it locally), copy it here, run it by me and others, and then get it fixed in the actual documentation. Follow the examples of the stuff I pointed out as excellent or on par, and use that for the sub-par documentation.
Comments
Comment #1
birdmanx35 commentedAlso, remember the icon/presentation is another task, just focus on the content.
Comment #2
birdmanx35 commentedAlright, I'm going to get a taste of my own medicine and sign up for this one.
Comment #3
birdmanx35 commentedUser Support:
Replace "Other tips.." with this:
<li><b>Keep in touch.</b> Say hello when you encounter them on IRC!</li>Documentation
In the "For Developers" section, please link to CVS and Doxygen, the latter of which should be capitalized while we're being nitpicky.
Translations
Add this introduction:
<p>Thanks for your interest in translating Drupal! Bringing Drupal to as many languages as possible is not only necessary for it's usefulness, it's also a highly valued and needed contribution.</p>Testing
Change "Yet to be written but here are a few tips that can help you." to:
The <a href="http://drupal.org/patch/review">existing documentation</a> on the proper process for reviewing patches is quite useful for new reviewers. Sign on to IRC if you have troubles!In the "Usability testing" section, link to the Usability contribution page. Here's the code:
If you are interesting in improving Drupal's usability, check out the <a href="http://drupal.org/contribute/usability">Usability contribution</a> documentation.Usability
Add this introduction:
Thanks for exploring the happy land of Usability. Here are some links to get you started:Donations
Fine.
Development
Fine.
Themes
Fine.
Marketing
Add this introduction:
Drupallers all want Drupal to spread, so if you are experienced in marketing or want to help, here's the place to get started:Comment #4
Barry Madore commentedchanging component
Comment #5
tgeller commentedbirdmanx35: This issue appears to have died. Should it be killed? If not, what steps need to be taken to keep it alive?
(One suggestion if you want to keep it alive: Break down the issue into smaller, more easy-to-attack tasks. Big, multistep jobs tend to intimidate people out of action.)
Comment #6
arianek commentedjust read through this (and the other thread at http://drupal.org/node/222761) and am totally unclear as to what needs to be done. can someone update what the outstanding work to be done here is?
Comment #7
arianek commentedlisarex updated a lot of the contribute page for the redesign, so this issue is fairly moot now. marking will not fix.