hepabolu wrote:
I've turned PDF's off for now. Currently the Forrest plugin does not
support Daisy Books, but it should. In the meantime we can pull the
published book from Daisy. This is not a problem as long as we are not
trying to integrate content from different sources into the book
(which at present we are not doing).
No, I don't think integration is necessary. As stated in a previous post
I'm thinking about a few relatively static pages with the most prominent
info on Cocoon and a link to the Daisy book(s) for the actual
documentation.
Since Cocoon 2.2-dev switched to Maven2 for the build I figured we might
as well use a part of the site building functionality in Maven.
I'm currently filling in the blanks for the "project info" and some of
the "project reports", i.e. only the info that is part of the main pom.xml.
That will give enough information to users and potential contributers to
get up and running and after that there's the Daisy documentation.
This information is almost static and answers a lot of the FAQs I've
seen lately (i.e. SVN address, mailing lists etc.).
agreed, make things as simple as possible. We have M2 and Daisy books - that's
all that we need, isn't it?
--
Reinhard Pötz Independent Consultant, Trainer & (IT)-Coach
{Software Engineering, Open Source, Web Applications, Apache Cocoon}
web(log): http://www.poetz.cc
--------------------------------------------------------------------
