Thorsten Scherler wrote:
On Thu, 2007-01-04 at 10:49 +0100, Joern Nettingsmeier wrote:
Andreas Hartmann wrote:
Doug Chestnut schrieb:
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.
i see. sorry for guessing wrong.
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.
certainly, but i'm still waiting for the "hey, cool!" moment regarding
forrest. i got that very quickly when i first saw daisy or blueprint,
and i even had it with lenya :-D, but i seem to be missing the point of
forrest, at least when considering the needs of the lenya website.
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
hmm. in my world, when i want to change web content, there are 2 options:
a) i don't care much for looks and want it really simple: i use a wiki,
click edit, click save, done.
b) i want consistent look-and-feel and enforce structure: i edit some
xml source document, run a generator script over it and the stuff is online.
what benefits does forrest bring that could make me unpack a huge
project on my harddisk, learn to install and run it and then follow a
ten-step process each time i want to do a minor update?
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.
<snip>
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.
ok. i can identify two sources of content on the lenya website:
* our javadocs (would be nice if they were kept up-to-date automagically)
* the rest. hand-written or cut-and-pasted from the wiki.
we don't really need any other output formats than html.
sounds like a job for a couple of xslts and a small zoo of bash scripts.
but then i read about "dispatchers", "plugins", "proxies", "compile",
"locationmaps" and a friendly "forrestbot" that rebuilds content every
night that gets updated once per decade. whoa. i've been to some weird
places before, but all this sounds a little intimidating ;)
as doug said, it would certainly be good to use lenya for the lenya
website. this would accomplish a number of important things:
* we have a constant mission-critical testbed that needs looking after
and has to work
* this testbed is in a non-root context and thus helps finding bugs
* we have to keep our static exporter in good shape
* ultimately, i would like to see lenya evolve so that automatically
generated and dynamic content can be easily integrated, while retaining
the nice "click to edit" approach that the lenya default publication has.
regards,
jörn
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
