[drupal-docs] Administrator's guide - Make Task Orientated

[Michael Rasmussen]

Boris Mann wrote:
> Agreed. I've always thought there should be a features section
> (covering core Drupal) and then contrib features or something like
> that -- basically the project description, but perhaps with more
> detail, and then how-tos underneath each module.
> 
> Frick. We need some way of nailing up some of this stuff as to-dos,
> but basically the only way to do it is to start messing with the
> structure of the handbook. But we need some sort of consensus (or
> close to it) on what the structure of the hand book should be.
> 
> Anyone have suggestions about process? Our style guide is excellent
> first step, but somehow I think we need some other process as well.

Process suggestion, what about putting up a documentation mirror, a DOC
CVS if you will, where we work this stuff out and then migrate it to
the main Drupal site when it's ready for mass consumption?  We could
also announce it as alpha level documentation and allow end users to
comment on it, ask questions, to help ensure we're saying what needs said.

As to the structure of the handbook, I'm a big fan of the tiered 
Feature -> Quick Start / Related Modules -> Deeper Details -> 
Really Detailed howtos  sturcture.  One can read the outline/feature
level when that suits the needs and drill down when desired.

Michael "yeah, I'm new around here" R
-- 
    Michael Rasmussen, Portland Oregon  
  Be appropriate && Follow your curiosity
 http://meme.patch.com/memes/BicycleRiding
   Get Fixed:  http://www.dampfixie.org
  The fortune cookie says:
Marriage, in life, is like a duel in the midst of a battle.
		-- Edmond About