1. I agree with you about the need for improved documentation.<br>2. Totally agree that the book module (the hierarchy that you refer to) doesn't facilitate good documentation. I may have a different reason for feeling that: It's not the hierarchy that I object to: it's just that it is EXTREMELY time-consuming to use the drop-down to enter an item into the hierarchy. I think it's a huge barrier to adding content.<br>
3. That said, I'm fairly well-resigned that the powers-that-be will almost never cede the book module model for doing this in favor of a wiki. I've seen it discussed on IRC, and the idea of using a wiki was met with such snideness that I basically resigned myself to living with incomplete documentation forevermore. I wasn't a participant in that conversation, but the tone of it seemed to be: this is how we do things, it isn't going to change.<br>
4.I don't agree with you about the word "documentation" I think it's a great word. <br>5. Great idea on drupal documentation day. Would be great if you could facilitate it. There was one at DrupalCon, which I was unable to attend, unfortunately.<br>
<br>Those are my thoughts for the moment,<br><br>Margie<br><br><div class="gmail_quote">On Wed, Mar 19, 2008 at 4:13 PM, Nick <<a href="mailto:nickchris@gmail.com">nickchris@gmail.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;">
First, a little background: I've been lurking on the Drupal boards and on this mailing list for some time now. I work for a newspaper in the developing world, and in the near term we will be moving a portion of our online media onto Drupal as a test pilot. For some weeks I had been toying with various CMS, and after settling on Drupal, had to climb up the learning curve from a point where I knew very little about PHP and even CSS, to a point where I can now make my own themes and (very basic) modules from scratch. Throughout this I have become fairly familiar with Drupal's documentation, especially as it relates to a self-starters with a deep interest in Drupal but who lack the immediate technical skills to grasp it immediately. Despite my frustrations with the learning curve, I've become yet another starry-eyed Drupal fanatic, and have big plans for contributing, especially in the area of (translating) documentation.<br>
<br>So with that all said: <a href="http://Drupal.org" target="_blank">Drupal.org</a>'s documentation page needs a lot of reorganization. In fact, right now, it seems like a kind of Achilles heel to certain aspects of its development (theming, translations), despite the fact that developers are flocking to it.<br>
<br>I posted an issue that I think really captures what I'd like to suggest. You can check it out here:<br><br><a href="http://drupal.org/node/236444" target="_blank">http://drupal.org/node/236444</a><br><br>So what do people think? If not this, what direction will the Drupal documentation take in the future? <br>
<br>Last question: if a group of people raised their hands and said that they loved this idea and would do this, what would the next step be?<br>
<br>--<br>
Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>
List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br></blockquote></div><br>