[documentation] A suggestion to improve drupal.org handbooks

[gunnar]

Laura - that (below) was exactly my point in my previous post.
A standard structure (maybe just guidelines) would help developers document
their modules. Also other document writers might have a better chance of
stepping in and "filling in the blanks".

So  - maybe not for now but for later - should we try and decide on a format?

best
Gunnar


> * Requirements (other modules)
> * Install requires
>     [ ] folder upload
>     [ ] database table insertion
>            ( ) sql script alters existing tables
>     [ ] other configuration ___________
> * Permissions available
> * Menu changes
> * Blocks available
> * Theming concerns
> * Known conflicts
> * Tarball last updated: _______________
> 
> ....or something like that? If there were a standard set of headings,
>  it might help make the modules documentation hold together.
> 
> Laura
> 
> --
> Pending work: http://drupal.org/project/issues/documentation/
> List archives: http://lists.drupal.org/pipermail/documentation/


Gunnar Langemark
gunnar at langemark.com