Jarek, I would highly suggest that we try and keep all the changes to the exporter together someplace (currently in CXF's repo, but we could move it, although since you are a committer there, likely not needed to move). If/when infrastructure updates the confluence version from 3.4 to 4.x, the exporter WILL need to be updated as the SOAP API's that we use have changed quite a bit in 4.x. If we keep all the changes together in one place, we'll only need to update it in one place instead of scattered throughout all the projects.
Dan On Dec 18, 2012, at 2:26 PM, Jarek Gawor <[email protected]> wrote: > I did some experiments with both approaches: 1) convert to Apache CMS, > and 2) use Dan's site-export tool. I got a lot further with Dan's > tool. I modified his code a bit so that it works with our existing > templates (no need to modify our templates). However, there are at > least two things that don't work right (yet): a) exporting news items > / blogs, and b) cross wiki space links. I think I can fix b) but I'm > not sure about a). > > Anyway, I just checked the wiki exporter code into > https://svn.apache.org/repos/asf/geronimo/site/trunk/wiki-export. > There is a README file that explains how to get things going. You will > also need the templates from > https://svn.apache.org/repos/asf/geronimo/site/trunk/template > > Jarek > > On Fri, Dec 14, 2012 at 10:16 AM, Jarek Gawor <[email protected]> wrote: >> I think we need a short and long term solution. For the short term solution >> let's try Dan's approach and see if that can work for us. Otherwise, we will >> loose web site updates on the 1st. For the long term solution we can >> consider switching to CMS or at least getting a clarification from the infra >> team if we can continue to use the cwiki for the website. We do have a lot >> of pages so switching to CMS might be challenging but we might have no >> choice (sooner or later). >> >> Jarek >> >> >> >> >> On Fri, Dec 14, 2012 at 2:37 AM, Mark Struberg <[email protected]> wrote: >>> >>> I suggest using the new CMS. You can still use svnpubsub for static >>> content. >>> There is now even a maven plugin in the making for automated svnpubsub. >>> >>> We've now moved over quite some pages using bootstrap. >>> >>> http://openwebbeans.staging.apache.org/ >>> http://bval.staging.apache.org/ >>> >>> http://incubator.apache.org/deltaspike/ >>> http://tomee.apache.org/ >>> >>> >>> Still trying to figure how doing things like 'News' teasers on the landing >>> page, etc... >>> >>> >>> LieGrue, >>> strub >>> >>>> ________________________________ >>>> From: Shawn Jiang <[email protected]> >>>> To: [email protected] >>>> Sent: Friday, December 14, 2012 3:46 AM >>>> Subject: Re: migration of web site to svnpubsub >>>> >>>> >>>> I would like to use method described here[1] to render the confluence >>>> pages locally and then publish them to svnpubsub . So that we can still >>>> work with confluence without learning a new CMS system. >>>> >>>> >>>> [1]http://www.dankulp.com/blog/2012/03/svnpubsub-for-confluence-sites/ >>>> >>>> >>>> >>>> On Mon, Dec 10, 2012 at 11:36 PM, Kevan Miller <[email protected]> >>>> wrote: >>>> >>>> All, >>>>> rsync-based updates of the geronimo web site will be frozen in January >>>>> (very soon). We must migrate to svnpubsub (and optionally CMS) in order to >>>>> have a website that we can change (seems like something we'd like to >>>>> have). >>>>> >>>>> For more information, see -- http://www.apache.org/dev/project-site.html >>>>> >>>>> I'm going to have very limited time to do any work on this. Any >>>>> volunteers? >>>>> >>>>> --kevan >>>> >>>> >>>> >>>> -- >>>> Shawn >>>> >>>> >>>> >> >> -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
