[documentation] contrib module

[Laura Scott]

On Jan 12, 2007, at 8:52 PM, Steven Peck wrote:
> There are some empty contributed modules pages.  These were all  
> created as part of a bigger push to get things documented in the  
> handbook.  The hope at the time is that people would pick it up and  
> start adding pages/details to expand on these to help their  
> favorite contrib. module, etc.
>
>
> http://drupal.org/handbook/config/contribmodules
>
> I am going to start removing those pages I find that merely exist  
> as placeholders so if you are in love with a module now’s the time  
> to go update your page.  It’s been a year and many of the pages  
> haven’t been touched so I’d rather not have the placeholder if  
> there is no content.  This will allow for random people to add a  
> page if they are so moved in the future and less maintenance for  
> the rest of us.
Do we have a list of those empty pages?

(Other idea:) Better, if we drop the empties, is there a way we can  
somehow track modules that exist (and more important are branched for  
current releases) against modules that have pages describing them?  
While I or anyone may not go look to see if a given module has a  
documentation page, I probably would be more motivated to go post  
some instructions on using a module I'm familiar with. In other  
words, if I don't see the lack, I won't know that it's needed.

Do we want to explore establishing node relationships between  
projects and potential documentation pages. (In fact, if we could use  
node relation wildcard-type connections/links, we could add a lot of  
versatility for cross-linking through handbook pages, and linking to  
projects. Even a project-specific taxonomy for handbook pages and  
project pages could help achieve this.)

My goal in writing this isn't to throw work at someone, but rather to  
see if there's a setup we can pursue so that we aren't so dependent  
upon manual tracking of related content. If we can set up the  
structure well, our documentation and contributor community can more  
manage itself.

Is there any interest in pursuing something like this, anyone? It's a  
webmaster list topic as well, it seems. I'll raise my hand as someone  
interested and willing to participate in such an effort. It would be  
wonderful if we could more fully leverage Drupal's power on D.o,  
while at the same time not taxing server performance too much, given  
the realities we have today.

Laura


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