Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <49940222.7050901@searchevent.co.uk>
Date: Thu, 12 Feb 2009 11:04:02 +0000
From: David Legg <david.legg@searchevent.co.uk>
Organization: SearchEvent
User-Agent: Thunderbird 2.0.0.19 (Windows/20081209)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Spring Configurator Docs
References: 
 <F71A3F85F026644687388710AF44A200050014BF@srv-corp-exmb5.ciber.cbr.inc>
 <4993E3B3.507@apache.org>
 <7C655C04B6F59643A1EF66056C0E095E01F90B29@eusex01.sweden.ecsoft>
 <4993F048.7000701@apache.org>
In-Reply-To: <4993F048.7000701@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: none (sphinx.mythic-beasts.com: domain of
 david.legg@searchevent.co.uk does not designate permitted sender hosts)
 client-ip=84.9.158.18 envelope-from=david.legg@searchevent.co.uk
 helo=[192.168.1.53]

I have to agree that the current documentation system is a bit of a 
nightmare.

As I see it there are too many hurdles that have to be passed through 
before documents become visible to the general public.  I had a go at 
updating a few pages using the Daisy system.  Editing an existing 
document is easy enough but I never had the time to learn how to drive 
the navigation sytem... and I suspect nobody else did either ;-)  This 
is why moving between docs is so difficult.

Also it might have seemed like a brilliant idea to extract documentation 
directly out of the code but that actually adds a further barrier to 
getting it done as you are then faced with updating the code when all 
you wanted to do was write about it.

The final hurdle is that even after you have edited the page and made it 
active it still isn't visible on the main Cocoon site until some arcane 
command line incantations are performed.

Bring back the wiki I say!

Regards,
David Legg