Hi Stephan,
...See http://vern.chem.tu-berlin.de/~stephan/cocoon/index.html
Looks good!
There seems to be a problem with images however, for example in
http://vern.chem.tu-berlin.de/~stephan/cocoon/userdocs/concepts/ index.html
I found images references like <img src="images/pyramid-model.gif.html">, which do not work.
....1. Should Cocoon any longer produce his own docs? This mean that we must include stuff from forrest....
I think the original idea was to keep both the existing docs generation mechanism *and* Forrest, but this would be a pain IMHO. See http://marc.theaimsgroup.com/?l=xml-cocoon-docs&m=104563976028968&w=2.
Other projects use Forrest in binary form to generate their docs, I think that's what we should do to avoid the circular references problem between cocoon and forrest.
In order for everyone to use the same version of Forrest when generating the docs, I'd suggest creating a new "cocoon-tools" CVS module and check in there the version of Forrest that is currently used. In this way our main CVS won't get bigger and we'd have a well-known version of Forrest to build on.
...2. Which skin should be used?
As Forrest is based on Cocoon it makes sense IMHO to use the same skin for the Cocoon site as Forrest is using for its site, to show that they're part of the same family.
...3. Can we use something like a forrest cent?
I should go to bed and I have no idea what a Forrest cent is so I'll pass on this one ;-)
...4. I cut the build.xml into several fragments to increase the clearness.
It's okay? ...
Talking of the main cocoon build.xml, right? Splitting it makes sense IMHO but I think you should ask on cocoon-dev.
thanks for your work!
-Bertrand
