Yes, that would be it...
agreed.
On Tue, 2009-12-01 at 06:23 -0500, 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.
> > The cocoon community will be delighted at some good documentation.
> > Talking about community I fear such as an active community is to be
> > reestablished, so I think we'd better provide some sweet stuff.
> >
> > What would Reinhard think of starting with as a table of contents?
> > I will be glad to write some documentation as well. I have some goose
> > feathers available after Christmas, when I will be through the
> > experience of creating a first
> > How about you?
> > Jos
> >
> >
> > On Mon, 2009-11-30 at 08:07 -0500, Matt Whipple wrote:
> >
> >> I'm a recent transplant to Cocoon (and Java), in particular because
> >> Cocoon 3 appears as though it is/will be closely in line with my own
> >> perspective on web application development. I'm interested in
> >> contributing to the development of the framework itself, but likely
> >> won't be able to produce anything remotely useful for a couple months
> >> as I familiarize myself with all of the related technologies.
> >>
> >> I've just read some of the attacks on the poor documentation of the
> >> project and the resulting difficult entry for those unfamiliar. This
> >> is, of course, easily confirmed by the combination of woefully out of
> >> date references and dead links on the Web site (i.e. to the Daisy
> >> site). As I am (obviously) hopeful to see Cocoon succeed, I certainly
> >> don't want it to become mired in isolation like so many good projects.
> >>
> >> As such I'd like to try to contribute some documentation. Is there any
> >> idea among the community as to where documentation should end up, or
> >> should I just create a new site? Also, I'd lean towards focusing on
> >> Cocoon 3, as having documentation in place for a new release would
> >> likely have larger impact than attaching possibly overdue docs to an
> >> older, in the process of being superseded one. This would be premature
> >> if there's no foreseeable beta....
> >>
> >>
> >
> >
> >
>
>
