As I understand it, the new process is: 1) a user hits the website and is directed to a static version of the Confluence content.
2) if a user edits a document, he's redirected to the confluence version of the site. 3) After the document is edited, it's automatically converted into a static document on the static site. The goal is to keep the average user off Confluence since it dies under heavy load. On 4/11/06, Cris Daniluk <[EMAIL PROTECTED]> wrote: > Can you explain more about it? Confluence already has a pretty damn good > export function right now, and several projects are using it successfully. > > The only reason we are not is because the TOC generation is just not > suitable in Confluence (in fact, its essentially non-existant). I'd be > interested in anything that improves on this and saves me the work I'm doing > right now :) > > > On 4/11/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > > > > There's a "render to static file" process in testing for > > auto-converting Confluence documents into web pages as each web page > > is updated. > > > > This is an experiment to find a way for Confluence to be supported as > > a documentation system, without having end-viewers using confluence > > directly. If Cayene is interested in being a test case, someone > > volunteer, and I'll put you in contact with the appropriate people. > > > > They are looking for volunteers with experience in using Confluence > > and who have a well-established content-base that they can import. > > > >
