Based on these projects, I tried to find examples in svn but haven't
had any luck :-<

D.

On Sun, Jan 16, 2011 at 6:28 PM, Richard Hirsch <[email protected]> wrote:
> These are the current projects that are using cms - https://cms.apache.org/.
>
> D.
>
> On Sun, Jan 16, 2011 at 6:27 PM, Richard Hirsch <[email protected]> wrote:
>> I'd try it and see if it works.
>>
>> D.
>>
>> On Sun, Jan 16, 2011 at 6:20 PM, Anne Kathrine Petterøe
>> <[email protected]> wrote:
>>> That was what I was thinking too, but I am not sure if the @pattern arrays 
>>> and the values are generic and can be used in any project or not.
>>>
>>> /Anne
>>>
>>>
>>> On 16. jan. 2011, at 18.18, Richard Hirsch wrote:
>>>
>>>> Have you tried to take the two files and just substitute "ESME" for 
>>>> "stanbol"?
>>>>
>>>> D.
>>>>
>>>> On Sun, Jan 16, 2011 at 6:09 PM, Anne Kathrine Petterøe
>>>> <[email protected]> wrote:
>>>>> Link to Stanbol's two files: 
>>>>> http://svn.apache.org/repos/asf/incubator/stanbol/site/tags/initial-site-content/lib/
>>>>>
>>>>> On 16. jan. 2011, at 16.59, Joe Schaefer wrote:
>>>>>
>>>>>> Commit it to:
>>>>>>
>>>>>> http://svn.apache.org/repos/asf/esme/site
>>>>>>
>>>>>>
>>>>>> Once there's a skeleton layout in place, file an INFRA
>>>>>> jira and I will bring the CMS and staging sites up for esme.
>>>>>>
>>>>>> We can flip the switch on the production site once the staging
>>>>>> site meets your needs.
>>>>>>
>>>>>>
>>>>>> ----- Original Message ----
>>>>>>> From: Anne Kathrine Petterøe <[email protected]>
>>>>>>> To: [email protected]
>>>>>>> Sent: Sun, January 16, 2011 10:45:04 AM
>>>>>>> Subject: Re: Migrate website from Confluence to ASF CMS
>>>>>>>
>>>>>>> Hmm sorry for all the questions, but I am still not quite sure where I 
>>>>>>> should
>>>>>>> commit (the layout) to.
>>>>>>> Here? https://svn.apache.org/repos/infra/websites/
>>>>>>>
>>>>>>> It would also be great  if we could set up the CMS before we are going 
>>>>>>> live
>>>>>>> with the final content as we  have decided to build the site from 
>>>>>>> scratch
>>>>>>> instead of migrating the content  from the old Confluence site.
>>>>>>>
>>>>>>>
>>>>>>> On 16. jan. 2011, at 14.39, Joe  Schaefer wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original  Message ----
>>>>>>>>> From: Anne Kathrine Petterøe <[email protected]>
>>>>>>>>> To: [email protected]
>>>>>>>>> Sent: Sun,  January 16, 2011 8:34:38 AM
>>>>>>>>> Subject: Re: Migrate website from  Confluence to ASF CMS
>>>>>>>>>
>>>>>>>>> So how do I browse the ESME  site?
>>>>>>>>> http://esme.apache.org/
>>>>>>>>>
>>>>>>>>> Do we need to open an  INFRA  ticket to move the site first?
>>>>>>>>
>>>>>>>> At some point I will  need to add ESME to the cms.  What I need
>>>>>>>> for that is a conforming  svn layout: see
>>>>>>>>
>>>>>>>> http://www.apache.org/dev/cms.html#layout
>>>>>>>>
>>>>>>>> We can setup the  CMS and staging site *before* you are ready
>>>>>>>> to make the final content  live (thereby replacing the Confluence-
>>>>>>>> backed site).
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 16. jan. 2011, at 14.26, Joe   Schaefer wrote:
>>>>>>>>>
>>>>>>>>>> I was tailing the logs as you  browsed the site, and  added
>>>>>>>>>> some explanatory text on the  bookmarklet to the cms home  page.
>>>>>>>>>>
>>>>>>>>>> The way  you use the bookmarklet is to visit a live  production
>>>>>>>>>> website like http://www.apache.org/ , locate a page you'd like
>>>>>>>>>> to edit,  and then  click on the bookmarklet.  Obviously this  will
>>>>>>>>>> only work for  websites which use the cms  currently.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -----  Original Message ----
>>>>>>>>>>> From: Anne Kathrine  Petterøe <[email protected]>
>>>>>>>>>>> To: [email protected]
>>>>>>>>>>> Sent: Sun,  January 16, 2011 8:22:54 AM
>>>>>>>>>>> Subject: Re:  Migrate website from  Confluence to ASF CMS
>>>>>>>>>>>
>>>>>>>>>>> I have one question  already.
>>>>>>>>>>> I  have installed the ASF CMS bookmarklet, but  get a  404 (The 
>>>>>>>>>>> requested
>>>>>>> URL
>>>>>>>
>>>>>>>>>
>>>>>>>>>>> /redirect was not found on this  server.)  when  clicking it. I 
>>>>>>>>>>> tried to
>>>>>>>>> manually
>>>>>>>>>
>>>>>>>>>>> enter this
>>>>>>>>>>>
>>>>>>>>>
>>>>>>> javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))
>>>>>>>
>>>>>>>>>
>>>>>>>>>>> in  the URL  field of the bookmarklet, but still  get a 404.
>>>>>>>>>>>
>>>>>>>>>>> Am I doing something   wrong?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On 16. jan.  2011, at 13.14, Joe Schaefer wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Sounds great.  If you have any questions   don't
>>>>>>>>>>>> hesitate to  ask.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> -----  Original Message  ----
>>>>>>>>>>>>> From: Anne Kathrine  Petterøe <[email protected]>
>>>>>>>>>>>>> To: [email protected]
>>>>>>>>>>>>> Sent: Sun,  January 16, 2011 7:01:04 AM
>>>>>>>>>>>>> Subject: Re:  Migrate website from  Confluence to ASF  CMS
>>>>>>>>>>>>>
>>>>>>>>>>>>> Hi  Joe,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I just   wanted to let  you know that I am starting the  process 
>>>>>>>>>>>>> to
>>>>>>> move
>>>>>>>
>>>>>>>>> to
>>>>>>>>>
>>>>>>>>>>> the
>>>>>>>>>>>
>>>>>>>>>>>>> new CMS system   now.
>>>>>>>>>>>>> (will have to do some  reading   first  though)
>>>>>>>>>>>>>
>>>>>>>>>>>>> /Anne
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On 5. jan. 2011, at 18.29, Joe  Schaefer    wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> -----   Original Message ----
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> From:  Richard Hirsch <[email protected]>
>>>>>>>>>>>>>>> To: [email protected]
>>>>>>>>>>>>>>> Sent: Wed,  January 5, 2011 12:19:06  PM
>>>>>>>>>>>>>>> Subject: Re:  Migrate website  from  Confluence to ASF  CMS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Jan 5, 2011  at 5:26 PM,   Joe Schaefer
>>>>>>> <[email protected]>
>>>>>>>
>>>>>>>>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>> Now that ESME is a   top-level  project, it'd be a   good
>>>>>>>>>>>>>>>> time  to migrate the   esme website from Confluence   to
>>>>>>>>>>>>>>>> the new ASF  CMS.  The org  is  phasing out   Confluence
>>>>>>>>>>>>>>>> backed websites as   unsupportable and the      infrastructure
>>>>>>>>>>>>>>>> team is now requesting  that all  new  TLPs  migrate   off
>>>>>>>>>>>>>>>> Confluence as part of their   transition   effort.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Details  on the cms are  available  at:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> https://blogs.apache.org/infra/entry/the_asf_cms
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> There are  conversion  utilities  available.   Let me   know
>>>>>>>>>>>>>>>> when you'd  like to  start  the  process.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We could start with the  conversion  ASAP. I've  noticed that   
>>>>>>>>>>>>>>> the
>>>>>>>>> current
>>>>>>>>>>>>>>> export  from  Confluence  isn't functioning well and I was  
>>>>>>>>>>>>>>> thinking
>>>>>>
>>>>>>>>>> about
>>>>>>>>>>>>>>> starting a deeper analysis of the  problems.  A   transition to 
>>>>>>>>>>>>>>> CMS
>>>>>>>>> would
>>>>>>>>>>>>>>> hopefully  solve these    problems.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> We also use Gliffy in  our   current  wiki.  How does the 
>>>>>>>>>>>>>>> conversion
>>>>>>>> deal
>>>>>>>>>>>>>>> with  such   content?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> AFAICT  Gliffy just  generates images.  Those should be copied  
>>>>>>>>>>>>>> over
>>>>>>> by
>>>>>>>>>>>>>> the  conversion utils.   Obviously the CMS  doesn't have a Gliffy
>>>>>>>> plugin
>>>>>>>>>>>>>> so you'd have to  generate the  images on your workstation  and
>>>>>>> upload
>>>>>>>>>>>>>> them to the CMS, perhaps to an  attachment   directory.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The conversion utils  are   at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>
>>>>>> https://svn.apache.org/repos/infra/websites/cms/conversion-utilities/cwiki/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The build system is  at
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> https://svn.apache.org/repos/infra/websites/cms/build/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Note there some python prereqs for the build  system as  it  
>>>>>>>>>>>>>> relates
>>>>>> to
>>>>>>>>>>>>>> markdown.  For details  see
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> http://wiki.apache.org/general/ApacheCms2010
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>

Reply via email to