Gregor J. Rothfuss schrieb:
(...) how about:
* install a seperate lenya 1.4 on the zone, just for docs
* use the default publication for now
* give lenya logins to anyone who has a proven track record with docs ;)
seems clear so far ;)
* use wget for static export
* also install svn 1.2 with a private repo on the zone
* use http://wiki.apache.org/cocoon/ReadWriteToSVN to write to that
private repo
.. go from there.
Do you mean that we would edit content in Lenya, which stores it in the
filesystem, then do a static export of the "site", and store the
resulting html in the svn ? If so, I guess the Cocoon ReadWriteToSVN
wouldn't come into play ?
Or do you mean, the content we edit in Lenya is directly stored in SVN,
as described in the Cocoon Wiki ? In this case, do you know if it would
be enough for us to alter the publication's sitemap or would we need
some custom Java code as well ?
In this case IIUC the static export would happen e.g. once a day, and
access a running Lenya instance, which in turn accesses svn for content.
--
Wolfgang
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
