I published the new Antora site and requested via INFRA-21832 - Decommission 
Aries CMS website <https://issues.apache.org/jira/browse/INFRA-21832> that the 
CMS stuff be removed.

I’m going to finish the initial Felix site migration and then should have some 
suggestions about bringing the doc sources closer to the code.

David Jencks

> On May 2, 2021, at 6:56 PM, Raymond Augé <[email protected]> 
> wrote:
> 
> +1
> 
> Thanks for your hard work on this
> 
> - Ray
> 
> On Sun., May 2, 2021, 2:34 p.m. David Jencks, <[email protected]>
> wrote:
> 
>> At long last I’ve succeeded in automating the proposed Antora website
>> build, using the Apache Jenkins CI.
>> 
>> Changes to https://github.com/apache/aries-antora-site.git are picked up
>> with a GitHub trigger and in turn trigger the website build on https://
>> <https://github.com:apache/aries-antora.git>github.com:apache/aries-antora.git
>> <https://github.com:apache/aries-antora.git> with the new content
>> published to the asf-site branch on
>> https://gitbox.apache.org/repos/asf/aries-site-pub.git <
>> https://gitbox.apache.org/repos/asf/aries-site-pub.git> which is
>> currently visible at
>> https://aries-beta.staged.apache.org/documentation/index.html <
>> https://aries-beta.staged.apache.org/documentation/index.html>.
>> 
>> To switch the production site to this, we need to change the .asf.yaml
>> file to have
>> 
>> publish:
>>  whoami:  asf-site
>> 
>> and (I think) tell infra to turn off the CMS machinery.
>> 
>> I suggest we do this and then discuss how to bring the documentation
>> sources closer to the code.
>> 
>> Thoughts?
>> 
>> Thanks,
>> David Jencks

Reply via email to