By nicolash on

I've only recently started to delve into Drupal and made extensive use of the documentation. One thing I noticed is that there are often crucial errors - either simple tiny syntax errors that make people look for far more fundamental flaws or outdated approaches that result from Drupal updates without being reflected in the docs.

The comments are usually a great way to get corrected information, but it quite often takes a while.

When I finally get something working I would like to update the documentation so the next person doesn't have to go through the same motions. I'm sure this has been discussed before, but why doesn't the documentation follow a Wiki approach with people being able to add revisions instantly? They could require approval by the original author or authors could choose to release it completely.

Or is there such an approach and I'm missing something? If the answer is to file a "documentation bug", is this really the best way of doing this?

Thanks in advance for your replies...

Comments

abhigupta’s picture

abhigupta commented

I don't think filing a bug is the most convenient way to go for handbook ... I think a wiki would dramatically raise the standard and volume of the Drupal Help Pages ... Maybe it is time for a useful Wiki module to accomplish this task.

sepeck’s picture

sepeck commented

All you need to do is join the docs team and ask to help out.

You too can become a handbook maintainer today. The only barrier is you have to ask. One way to find this out is to click the contribute link on the top and read up on helping out the documentation effort.

Look forward to processing your requests. :)

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide