On Thu, 2007-01-04 at 10:49 +0100, Joern Nettingsmeier wrote: > Andreas Hartmann wrote: > > Doug Chestnut schrieb: > >> Hi Devs, > >> Looks like a file is missing somewhere in the documentation process. > >> > >> I just looked over the docs at > >> http://lenya.apache.org/docs/website-update.html and all I have to say > >> is Wow. > >> > >> Makes me wonder how hard it would be to just run documentation > >> publication in our zone and do a wget to get the static lenya website, > >> at least we would be sort of eating our own dog food. > > > > That sounds really appealing. > > +1 > > > Does someone remember why we moved from our own documentation > > publication to Forrest? > > my guess is that thorsten came up with it to help with continuous > integration between lenya and forrest and to reap some cross-pollination > benefits... - thorsten, can you comment?
nupp, when I got active lenya committer we had a forrest documentation and I just updated it since around 2003. The forrest publication did not work when I updated forrest so we just used a plain forrest doc one. Regarding cross-pollination, I see so many features in lenya and forrest duplicated and both communities are very small, I think it would help both to cooperate. > > as it is now, i can't be bothered to take care of the website, because > it is just to complicated for my taste and i refuse to set up a forrest > environment just to be able to do minor doc updates. Hmm, without forrest set up it is hard to follow the update process. If you set up forrest you can publish the docu with a couple of comments http://lenya.apache.org/docs/website-update.html#Let+forrestbot+help+you > but maybe that is only because i don't understand the benefits of the > current system - my understanding of forrest concepts and goals is vague > at best. http://forrest.apache.org/ "Apache Forrest is a publishing framework that transforms input from various sources into a unified presentation in one or more output formats. The modular and extensible plugin architecture is based on Apache Cocoon and relevant standards, which separates presentation from content. Forrest can generate static documents, or be used as a dynamic server, or be deployed by its automated facility." The benefit of forrest is that you have a publishing environment for pdf, html, odt, ... out of the box. It is normally very easy to set up and use. > perhaps someone (thorsten?) could educate us about why forrest is cool > for our particular usage scenario, and then we can decide whether to > move to lenya/wget or stick to the current method. see above. x input format will be generated into one internal format and from there to x different output formats (out of the box). I like the concept, but if the community would like something different I am not standing in the way. Like said above I just helped out updating the docu. > however we decide, it's clear that the website needs more attention. it > is also clear that this burden is not evenly distributed among lenya > contributors, but at least imho that's because it is too much of a > hassle atm. Not sure why, but docu contributions are very rare that is true. Not sure of changing the tool will increase this but we can try. salu2 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
