On 19/10/06, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
All,
What is the future of our website in relation to content management?
With that I mean do we:
1 - continue generating our sites using maven, and put them on Apache turf
To do this, I /think/ it's just a matter of checking in the built
site into a portion of our SVN, and checking it out in the correct
portion of the apache web infrastructure. To update, it's be the same
as the incubator main website, i.e. edit source, build, commit source
& built files, ssh to apache shell, cd to appropriate directory & svn
update.
2 - use confluence and export it into some static format and put them
on Apache turf
The export from this seems rapid, and it looks like it can be all
setup with redirects (see the OpenEJB site as an example), so this
seems easy enough once the initial setup's done. Downside is that
you're not generating the site from the pom, but not sure if that's
really an issue, as it applies to all other than (1).
3 - use joomla and export it into some static format and put them on Apache turf
4 - use joomla and host it on our servoy server, and use that as our
main site (forward from wicket.apache.org)?
5 - some other option?
I think my preference would be (2) followed by (1), as I'm not
convinced that (3/4/5) would gain us enough in return for the
requirement to have to manage the 'non-standard' (to Apache, at least)
tools.
/Gwyn
--
Download Wicket 1.2.2 now! - http://wicketframework.org
