Hi, Am 29.01.2013 um 16:57 schrieb Ian Boston:
> Thanks for the ponter. > Did you have any problems with the perl dependencies on OSX ? Hmm, good point. IIRC I had to install one or another perl module through CPAN. But to be honest, I do not remember ... Regards Felix > Ian > > On 30 January 2013 07:58, Felix Meschberger <fmesc...@adobe.com> wrote: >> Hi, >> >> You might want to look at [1] where I listed some quick tips. >> >> As for the bookmark: This can also be done without commit permissions: You >> can edit and save but not commit. But you can generate the DIFF which can be >> supplied to an issue. >> >> Regards >> Felix >> >> [1] http://sling.apache.org/documentation.html >> >> Am 28.01.2013 um 16:03 schrieb Ian Boston: >> >>> +1 to keeping /site for the moment. >>> >>> I did a bit of work last week and the /site version was very useful in >>> working out what was supposed to be there. >>> >>> As someone else noted, the confluence macros haven't been migrated >>> well so there are things like {note ..} and {warning ...} in the >>> mdtext markup. >>> >>> Also I found that external links appear something like >>> {{ref.http://www.google.com.page}} >>> >>> I suspect grep/sed will be able to correct most of these. >>> >>> For those that have svn commit permission the bookmark >>> >>> javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href)) >>> >>> will invoke the CMS editor in a browser, which is a little lower cost >>> than installing python and perl tools locally. >>> >>> I hope to do some more when I get a moment. >>> >>> Ian >>> >>> >>> >>> On 29 January 2013 08:16, Carsten Ziegeler <cziege...@apache.org> wrote: >>>> Sounds good to me : +1 >>>> >>>> Carsten >>>> >>>> 2013/1/25 Felix Meschberger <fmesc...@adobe.com>: >>>>> Hi, >>>>> >>>>> Am 25.01.2013 um 05:04 schrieb Bertrand Delacretaz: >>>>> >>>>>> Hi, >>>>>> >>>>>> Now that INFRA-5646 is fixed , http://sling.apache.org correctly shows >>>>>> the new site (same content but slightly different layout), but the old >>>>>> content under /site is still here, like >>>>>> http://sling.apache.org/site/index.html >>>>>> >>>>>> Can we get rid of that and replace with redirects to the new content? >>>>> >>>>> The /site is imported into the SVN and just transferred to publish. Maybe >>>>> we should keep it as a validation reference until we fully migrated. >>>>> >>>>> In Felix I have done it like this: >>>>> >>>>> * Defined a mdtext header field to indicate whether >>>>> a page is can be considered properly migrated or >>>>> not >>>>> * If a page is not properly migrated, a link at the >>>>> is shown indicating this state and linking to the >>>>> original page. >>>>> * When fixing a migrated page, this is the procedure: >>>>> * Remove the property from the headers >>>>> * Remove the old page >>>>> * Add a PermanentRedirect to the .htaccess file >>>>> in the site folder >>>>> >>>>> Maybe we can do something similar in Sling ? >>>>> >>>>> Regards >>>>> Felix >>>> >>>> >>>> >>>> -- >>>> Carsten Ziegeler >>>> cziege...@apache.org >>
