[documentation] Proposal for handbook maintenance automation

[Laura Scott]

On Aug 8, 2007, at 11:33 AM, Kieran Lal wrote:

> I think all the documentation should be a wiki.  Click here to  
> edit.  Give admins the ability to lock pages, were necessary.
>
> The current status of having 50 comments on a page for something as  
> critical how to upgrade your module to the next API version, is  
> completely unacceptable.  We are forcing companies and admins to  
> spend collectively millions of dollars on upgrading their sites  
> between versions with inconsistent and unclear documentation.

Agree on this 100%.

Something sepeck and I discussed at OSCMS was that all the versions  
are intermingled, and that ideally we would have handbook views by  
version number, and done in a way that avoids massive node  
duplication in order to effect hierarchy.

The handbooks are a particularly tough challenge. Wonder if what we  
really need are tabbed views for each page, with each tab offering  
potentially version-specific info. Even in a wiki, that approach  
might be helpful from a usability standpoint. The tagging alone gets  
us part of the way there.

Laura

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/documentation/attachments/20070808/870e6fa8/attachment.htm