Guys, When the navigation is a matter of creating a query and/or a hand-picked outline, I really don't think it is THAT important to decide now. When writing the tutorial I found it practical to keep the various steps/documents together so I could better focus on what to write and what was done. But the ultimate form will probably be different.
I myself like documentation based on a growing example with background information woven into it, but once I get the idea I like an extensive index for quick access to the various details. Maybe, we can ultimately decide that there are various sites, all handling the same documentation, but with different navigational setups. That way each can choose his/her own preferred way of diving into the matter. AFAIU Daisy is capable of doing this, so let's focus on content first with a preliminary navigation. Bye, Helma > -----Original Message----- > From: Bruno Dumon [mailto:[EMAIL PROTECTED] > Sent: Friday, 17 June 2005 17:46 > To: dev@cocoon.apache.org > Subject: Re: [docs] old docs import done > > > On Fri, 2005-06-17 at 14:54 +0100, Mark Leicester wrote: > > Hi Bruno, > > > > Great! I've done a fair amount of work on the Cocoon In > Action section. > > Should we look at merging the two, or do they have sufficiently > > distinct purposes to keep them separated? > > This is just IMHO... > > The parts of Cocoon In Action that talk about the build system and > getting the code from SVN certainly belong in the documentation. > > The rest... I'm undecided yet. I have some preference to keep > tutorials > separate. > > -- > Bruno Dumon http://outerthought.org/ > Outerthought - Open Source, Java & XML Competence Support Center > [EMAIL PROTECTED] [EMAIL PROTECTED] > >
