I have not learned how to use the export/conversion tool for the CMS, and I don't have time to take this on.
On Thu, Apr 7, 2011 at 4:36 PM, Sean Owen <[email protected]> wrote: > I think 1) is just fine, personally, for these pages which are by nature > quite static and infrequently changing anyway. It sounds easier. Do you or > Robin have the mojo to make the files? I don't mind taking care of the rest. > > On Thu, Apr 7, 2011 at 9:34 PM, Benson Margulies <[email protected]> > wrote: >> >> On Thu, Apr 7, 2011 at 4:23 PM, Sean Owen <[email protected]> wrote: >> > Is it... >> > 1) Export all of those confluence pages to some reasonable HTML form >> > 2) Commit and link to the HTML files >> > 3) Delete wikis? >> > If 1) is easy, then the whole thing is easy. We have a tool that makes >> > 1) >> > easy? >> >> Choice 1: preferred by Joe: >> >> Use a conversion tool to convert the confluence content to his >> html+markdown format, check that into svn, delete confluence. Edit his >> format ever afterwards. >> >> Choice 2: preferred by Dan and other aficionados of Confluence as a CMS: >> >> Install Dan's tool that runs every night and create a static HTML >> version of the confluence content, sticking it into svn where the >> infra tools know to pull it out. >> >> >> >> >> >> > >> > On Thu, Apr 7, 2011 at 4:24 PM, Robin Anil <[email protected]> wrote: >> >> >> >> Is this discussion on the infra list. >> >> >> >> sent from handheld device excuse typos >> >> On Apr 7, 2011 8:51 PM, "Benson Margulies" <[email protected]> >> >> wrote: >> >> > You should really read all of JoeS's writing on this topic, but, in >> >> > short: >> >> > >> >> > Infrastructure draws a sharp distinction between 'the web site' and >> >> > 'the wiki' for a project. They want 'the web site' to be published, >> >> > via svn, as static HTML. No Confluence, no PHP, no nothing. >> >> > >> >> > To that end, Joe built a new CMS from scratch. Its uses markdown to >> >> > ease the markup process, and it operates on files stored in svn. >> >> > There >> >> > are apparently javascript scriptlets to give you some level of >> >> > convenience in editing in it. I haven't use it yet, myself. >> >> > >> >> > The original position of infra was that all use of confluence for >> >> > 'the >> >> > web site' would cease at Apache. Confluence would remain in use only >> >> > for 'the wiki'. >> >> > >> >> > Dan Kulp of CXF and other projects really, really, didn't want to >> >> > give >> >> > up the convenience and expressive range of Confluence as a CMS for >> >> > 'the web site'. So, he built a brand new static export tool for >> >> > confluence that meets the stated requirements of the infrastructure >> >> > team, and deployed it for CXF. >> >> > >> >> > Infrastructure will insist that Mahout achieve static publication >> >> > *somehow*. The simplest thing we can do is adopt Dan's technology to >> >> > render the confluence content into static HTML. >> > >> > > >
