One s. Anissa makes it something vaguely snakelike out of a Eddings
novel. ;)
I don't think the handbook titles should be soo long, and, in general,
the word Drupal, except for the About Drupal section, is probably
unnecessary.
Anisa.
bryan kennedy wrote:
>Ok based on Judah, Anissa, Ron, Charlie, and Vlado's comments I think
>we can see that we need something for beginner users on how to use a
>drupal website, not just administer it. I think we should concentrate
>on developing a task based documentation. So how about this:
>
>-Getting Started and Using a Drupal Website (yes these should be ONE
>book)
> *Sys Req. and Installing and stuff
> *The basics of using a drupal site (adding content, creating a log in)
>-- stuff that is being discussed as end-end user docs
>
>-Administering a Drupal Website
> *Configuration and all the other admin good stuff
>
>-Developing for Drupal
> *CVS, modules, themes and other nerdy stuff
>
>-About Drupal
> * general info (history, marketing, conference slides) This is not
>the main focus of the handbook and so it should not be first in the
>list
>
>-About the Handbook
> *handbook stuff (authors, workflow, style guide)
> * we can promote this in a block, it just needs a structural home
> *as long as it says handbook in the top nav of drupal.org we should
>always refer to it as the handbook, if the top nav changes to
>documentation then we can change this here
>
>That get's us down to 5 sections and little ambiguity about where you
>might go for the information you might want which is the main problem
>right now.
>
>thoughts?
>bryan
>
>
>
|
