cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jos Snellings <Jos.Snelli...@pandora.be>
Subject Re: Cocoon documentation
Date Fri, 04 Dec 2009 10:45:34 GMT
Currently there is an initialisation problem. 
Anyway, Reinhard, you had a great table of contents. That is a good way
to get started: what nodes are missing? That way, we may fill in the
gaps, whilst trying our best to preserve unity of presentation & writing
style
All docbook, I guess?

Jos


On Fri, 2009-12-04 at 10:15 +0100, Reinhard Pötz wrote:
> Matt Whipple wrote:
> > Reinhard Pötz wrote:
> >> Matt Whipple wrote:
> >>   
> >>> Jos Snellings wrote:
> >>>     
> >>>> The documentation of cocoon-3 can be checked out as:
> >>>> svn co http://svn.apache.org/repos/asf/cocoon/cocoon3/trunk/cocoon-docs\
> >>>>   
> >>>>       
> >>> I stumbled upon the HTML deliverable of that on
> >>> http://people.apache.org/~reinhard/c3-ref/html/ after sending my email.

> >>> I'd think it would be best if the official documentation focused on
> >>> being primarily a comprehensive reference with a quick bootstrap guide.

> >>> A community documentation site could then supplement that with all the
> >>> typical tutorials/how-to's and tips & tricks which gets the reader where
> >>> he wants to be with a straightforward, minimalist approach which then
> >>> references the official docs and other more enlightening sources. 
> >>> Regular articles/blog entries could then highlight the activity in the
> >>> community, and the possibilities of various Cocoon components could be
> >>> showcased.  Guides to all of the overlapping processes which can be
> >>> [easily] extrapolated from existing material can be given a home so that
> >>> a potential new developer with a specific need is provided with an
> >>> apparent foot in the door.  Basically a site which presents a welcoming,
> >>> active community rather than seemingly a group of scattered people
> >>> developing in Cocoons and enabling me to make bad wordplay (such is the
> >>> price).  To that end, an agreed upon forum would be ideal. 
> >>>     
> >> Agreed. When I started to write the C3 documentation, I had the Spring
> >> reference documentation in mind. I think it's one of the best examples
> >> because it focuses on describing the technology and the concepts.
> >>
> >> As a forum for everything beyond reference docs we could either use
> >> Daisy or the Apache Wiki. (http://wiki.apache.org/cocoon)
> >>
> >>   
> > My thought would be Daisy (cocoondev.org?) so the site itself can be
> > Cocoon powered and then the wiki can remain legacy docs.
> 
> The Cocoon project runs its own Daisy instance at
> http://cocoon.zones.apache.org/daisy/
> 
> We could setup a Cocoon 3 wiki site there.
> 



Mime
View raw message