> OK, the dev list sounds just fine! What do you think about the 
> refactoring I'm suggesting? I can do it over the next few 
> hours if you 
> are agreeable. You are editor-in-chief, so I don't want to start 
> without your approval!

:-)

> Getting started with Cocoon
> + Installing the prerequisites
>    + Java
> + Getting the latest release of Cocoon
>    + Downloading a Cocoon release

Fine. I've already thought about the length of the pages currently in
the tutorial, but I'd rather get the stuff in first and refactor later.
Mind you, I don't like pages that consist of a header and one paragraph.

Note that I've added the section about Eclipse and Subclipse to:
- provide an IDE environment that makes working with Cocoon files easier
- try to "educate" them to use a code versioning system from the
beginning, although I've also talked about using CVSNT for that.


> + Getting Cocoon from the source repository
>    + Installing and configuring your IDE
>      + Eclipse
>        + Subclipse
>    + Checking out Cocoon
>      + Using the command line
>      + Using Subclipse

As Sylvain pointed out, this might be scary for "newbies", but it can
still be added and marked 'advanced'.

> Contributing to Cocoon
> + Getting Cocoon from the source repository
>    + Installing and configuring your IDE
>      + Eclipse
>        + Subclipse
>    + Checking out Cocoon
>      + Using the command line
>      + Using Subclipse
> + Building and running Cocoon
>    + From the command line
>    + From within Eclipse

Sounds ok. But, as Steven already pointed out the navigation is no big
deal and can be changed any "minute".

> + Building and running Cocoon
>    + From the command line
>    + From within Eclipse
> + Configuring Cocoon
>    + What's in cocoon.xconf?
>      + ...
>    + What's in web.xml?
>      + ...
>    + Logging
> 

Ok, advanced topics as well.

Have you looked at http://wiki.apache.org/cocoon/Cocoon215TOC ?

> Also, it occurred to me that perhaps we should delete pages 
> out of the 
> wiki once they become Daisy-ised. Otherwise we have two scratchpads. 
> What do you think?

I've brought this up earlier. General idea was to mark each wiki page.

Now that I'm in charge :-) I propose to mark each wiki page that is
moved over, with the URL of the Daisy page.

Bye, Helma

Reply via email to