Currently, the deployed site is a 'forrest' antique.

We have some pretty reasonable content sitting in Confluence. As you
may know, in general, intrastructure@apache is pushing projects from
Confluence to their new Markdown+svn CMS. The reason is their problems
with the generic export technology used historically with Confluence.

Some of us are not really thrilled at editing Markdown in a text
editor or web browser.

Dan Kulp has gone and created an alternative Confluence export device.
It meets the strictures of infrastructure@ and it allows site
maintenance in Confluence.

I'd like to make ws.apache.org use Confluence (with some maven site
output as appropriate), using Dan's technology. Anybody object?

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to