On 04/20/2013 03:45 PM, Les Hazlewood wrote:
2)
First thing's first: Apache has shut down the Confluence -> HTML ->
prod server deployment pipeline, so we currently have *no* way to ship
edited or new content to our website at the moment. That means we
need to put something in place asap. We can't effectively release
1.2.2 without updating site content to indicate it has been released.
Now, I know that Apache has created their new CMS, but I've found it a
bear to work with. Here's an example: have fun setting up/modifying
our site's templates when you have to deal with stuff like this:
http://svn.apache.org/repos/asf/zookeeper/site/trunk/lib/view.pm
I can't make sense of this stuff at all, nor do I want to dust off
Perl, which I haven't touched in 10 years - to do it.
You might not have to deal with such a file, as OOTB setup files such as
view.pm might be useable as-is (and are probably copied as-is across
most Apache CMS sites, with only a few bothering to make modifications
to it.) I converted Apache Roller to the new CMS and have updated
incubating JSPWiki's as well, IIRC just keeping the .pm files as-is.
Only issue is that the Apache CMS's default templates do make the
website look *very* simple (http://roller.apache.org/) and perhaps not
the most attractive on mobile devices.
The SCMS proposal (as well as the Camel/CXF Confluence method) also seem
good, I'm just wanted to mention that the presence of ugly/scary Perl
scripts shouldn't necessarily disqualify the Apache CMS.
Regards,
Glen
