I took an initial pass at it per the Style Guide on the MP site, and would like to get it going while I've got the motifvation and time.
As an example, there are a number of ways to do sessions, and most of those has a group of related modules as well as back-end options. I see this guide as providing logical groupings to help filter out all of the session options to discrete lists of modules that can be used as session mgmt. solutions, so instead of listing all of teh session-oriented modules, we could provide something like:
Apache::Session [Back-ends] - Apache::Session::MySQL - Apache::Session::DBI - Apache::Session::File - Apache::Session::Oracle - etc...
MasonX::Request::WithApache2Session ...
Apache::SessionX::Manager ...
Instead of duplicating the descriptions of each, I think we should provide links to the exsting information on each.
This will give users a domain to concentrate on so they can focus on the specific modules associated with one solution and ignore the others. I often spend a lot of time looking when I'm starting on a new area of knowledge looking at 5 different sets of options before I understand the groupings for each solution.
What's next? How can I get this set up as a project?
Thanks.
-Eric.
Eric Berg <[EMAIL PROTECTED]> http://www.bergbrains.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html