<div id="RTEContent">I have a few ideas for improving the handbook documentation and would like to volunteer for implementing them if the people on this list think they will help.<br> <br> These ideas are based on the tremendous difficulties I have had as a non-geek in understanding what a drupal core or contributed module does. The only way is to test each one out and this can be really time consuming when testing multiple modules.<br> <br> Current problems that newbies (and, I suspect, even others) have in understanding modules:<br> <br> 1.) Whether a module is dependent on another<br> 2.) Whether an sql table should be added to make it work<br> 3.) No idea about the different tables added by a module's sql file<br> 4.) No idea about the permissions implemented by a module. <br> 5.) No idea of what stuff a module adds to the navigation menu and UI.<br> 6.) Whether the module adds customs blocks that can then be enabled and configured.<br> <br> There may al
so be
other aspects that I have overlooked. <br> <br> I believe that documenting these would go a long way in helping people get up to speed on drupal very quickly. For example, until I got into the habit of visiting administer>>access control>>permissions>>module name>>permissions, I spent hours wondering why a module was not working. I bet many face the same problem.<br> <br> If this sounds useful, I am willing to do this work for 4.6 (as that has the largest user base at the moment), starting with each core module and moving on to the contribs. <br> <br> I also feel that if the handbook would allow screenshots, it would make for great documentation. As they say, a picture is worth a thousand words and all that.<br> <br> Thanks,<br> Ramdak </div><p>
                <hr size=1>Yahoo! Photos – Showcase holiday pictures in hardcover<br>
<a href="http://us.rd.yahoo.com/mail_us/taglines/photobooks/*http://pa.yahoo.com/*http://us.rd.yahoo.com/mail_us/taglines/photos/evt=38088/*http://pg.photos.yahoo.com/ph//page?.file=photobook_splash.html">Photo Books</a>. You design it and we’ll bind it!