This sounds like an excellent, however most of what you're describing as top-level subsections seem to be fairly trivial (i.e. not enough content for a top level subsection) and the one that is really substantial (Contribute Code) would be a better fit for the developer guide.<br>
<br>I would suggest rather than think of this as a whole new "book", that it be done more along the lines of a white paper with no more than a page for each of the subsections. Where there's a more lengthy discussion and a number of procedures (Contribute Code) just provide links to other sections.<br>
<br>Lee H.<br><br><br><div class="gmail_quote">On Fri, Mar 7, 2008 at 7:00 PM, Mike Booth <<a href="mailto:mike@michaelfbooth.com" target="_blank">mike@michaelfbooth.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
We propose that there be a new handbook section, titled "Contributing<br>
to Drupal", with the following top-level subsections:<br>
Get an Account<br>
Talk With The Community<br>
Use the Issue Queue<br>
<br>
Report a Problem<br>
Suggest Features<br>
<br>
Write Documentation<br>
Test New Features<br>
<br>
Contribute Themes<br>
Contribute Code<br>
<br>
(These titles are tentative and may not be quite what we want. Feel<br>
free to suggest more alternatives and to point out what we missed.)<br>
<br>
<br></blockquote></div><br>