Lee and Jennifer and all,<br><br>I agree with Jennifer that the online handbook is the best way to go. This current effort will make Drupal look slicker and it will be of some marginal help, but it doesn't tackle the bigger issue.<br>
<br>For D8 I think we should advocate for A LOT more references within the Drupal install to d.o. handbook pages. That gives people good references inside the ap, but allows the info to be current since handbook pages are constantly up-datable, and there is no technical barrier to entry.<br>
<br>Something I thought of in the shower last night..<br><br>I love Mac OS X... terrible built-in help system<br>I hate MS Office... probably the best built-in help system I've seen.<br>I love Drupal... I've attempted a few times to use the built-in help system and found it unsatisfying. Maybe three times in 3 years, and I'm probably seeking Drupal info every single one of those days.<br>
<br>In short, I think the handbook is the way to go...<br><br>And that's not to minimize this push to do a modest improvement to the built in help system. I'm just alerting non-coders that I don't think this is really where the action is.<br>
<br>Shai<br><br><div class="gmail_quote">On Sun, Nov 15, 2009 at 10:37 AM, Jennifer Hodgdon <span dir="ltr"><<a href="mailto:yahgrp@poplarware.com">yahgrp@poplarware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Lee Hunter wrote:<br>
> We're calling this a "help" system but that's not at all what's being<br>
> written. It would be much more accurate to call it a "Module Reference".<br>
><br>
> Help system content is normally all about the user - what the user wants to<br>
</div>> achieve and the tasks that they want to perform [...]<br>
<br>
I agree, Lee: Definitely the main module pages that we are editing are<br>
a module reference and not a user guide. The other entries in<br>
hook_help() implementations (which are help text that can be displayed<br>
on individual screens the module provides) are more in the line of<br>
"user guide", but they certainly don't constitute a full user guide.<br>
And hook_help() is never going to be a good vehicle for creating a<br>
full user guide.<br>
<br>
I will just note that the effort to revamp the current Drupal help<br>
system (perhaps in line with the Advanced Help contrib module) failed<br>
for D7 (I'm not familiar with exactly why)... and now is definitely<br>
the time to start thinking about what architecture would make sense<br>
for D8.<br>
<br>
But I am not sure we want to ship a user guide with Drupal at all,<br>
really -- maybe we should stick with the on-line Handbook (or some<br>
small, official subset) as the official user guide. This would have<br>
several advantages:<br>
- Non-coders can edit.<br>
- Few barriers to doc writers to contribute.<br>
- Much more dynamic than Drupal releases. Anything distributed with<br>
Drupal has to be translated into many languages, which pretty much<br>
means it is set in stone once a major release is out, and cannot<br>
(except for major bugs) be revised for minor Drupal versions.<br>
- Searchable via search on d.o as well as web search engines.<br>
- Can recommend contrib modules to achieve goals that are<br>
difficult/impossible with just core Drupal.<br>
<br>
Thoughts?<br>
<font color="#888888"><br>
--Jennifer<br>
</font><div><div></div><div class="h5"><br>
--<br>
Jennifer Hodgdon * Poplar ProductivityWare<br>
<a href="http://www.poplarware.com" target="_blank">www.poplarware.com</a><br>
Drupal, WordPress, and custom Web programming<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>
</div></div></blockquote></div><br>