Return-Path: 
 <cocoon-docs-return-77-apmail-xml-cocoon-docs-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-docs-archive@xml.apache.org
Received: (qmail 25291 invoked by uid 500); 5 Aug 2002 14:00:57 -0000
Mailing-List: contact cocoon-docs-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-docs-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-docs-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-docs@xml.apache.org>
Reply-To: cocoon-docs@xml.apache.org
Delivered-To: mailing list cocoon-docs@xml.apache.org
Received: (qmail 25282 invoked from network); 5 Aug 2002 14:00:57 -0000
Received: from mail.didax.com (216.5.214.162)
  by daedalus.apache.org with SMTP; 5 Aug 2002 14:00:57 -0000
Received: by cnmail with Internet Mail Service (5.5.2656.59)
	id <P066P1YQ>; Mon, 5 Aug 2002 10:02:15 -0400
Message-ID: <911C684A29ACD311921800508B7293BA0221DC85@cnmail>
From: Geoff Howard <ghoward@crosswalk.com>
To: "'cocoon-docs@xml.apache.org'" <cocoon-docs@xml.apache.org>
Subject: RE: Generator How-To
Date: Mon, 5 Aug 2002 10:02:12 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
Status: O
X-Status: 
X-Keywords: 

Thanks for the encouragement - I'll keep going on it as a Tutorial.  As
there is no How-To author a Tutorial, I assume that I can just sort of
follow the other examples as long as I validate against the DTD?  I have
been doing a build docs every few sections to see how things look.  

Geoff

> -----Original Message-----
> From: Diana Shannon [mailto:shannon@apache.org]
> Sent: Monday, August 05, 2002 9:10 AM
> To: cocoon-docs@xml.apache.org
> Subject: Re: Generator How-To
> 
> 
> 
> On Thursday, August 1, 2002, at 03:17  PM, Geoff Howard wrote:
> 
> > As I've begun work on this, I think I'm realizing that this 
> would be 
> > better
> > as a tutorial, or an addition
> > to the Extending Cocoon section of the existing docs.
> 
> I think your draft is *excellent*. I would classify it as a tutorial. 
> Clearly you appear to be taking the time/space to explain the 
> conceptual 
> issues behind the examples. In my opinion, How-Tos primarily 
> show "how" 
> to do something, as quickly and concisely as possible. Their primary 
> goal is expediency: to save users time, to help get the job done. 
> Tutorials, on the other hand, add in a teaching/concept component. In 
> other words, they provide the skills and knowledge to extend the 
> learning to solve other problems (extend other generators for other 
> problems). You are also providing multiple examples, from simple to 
> complex, building up a user's skill level. I'd classify that 
> as tutorial 
> material as well.
> 
> I prefer tutorials to new core docs. I'd like to keep 
> contributions as 
> granular as possible, so they can stand on their own (without 
> dependencies to other docs). That way, as time progresses, we 
> can build 
> meaningful learning trails to tie everything together in multiple, 
> useful ways. Instead of a single user guide and a side collection of 
> FAQs, How-Tos, Tutorials, we'd have many, many learning tracks, 
> depending on a user's background and existing skill set.
> 
> Thanks a lot Geoff. Can't wait to read the rest!
> 
> -- Diana
>