Thanks for working on this Dave!

-Alex

On 6/9/21, 11:32 AM, "Dave Fisher" <w...@apache.org> wrote:

    As you may recall the Apache CMS has been deprecated for over five years 
now and will be decommissioned
    by July 31, 2021.

    I’ve been tasked with moving OpenWebBeans's website away from the Apache 
CMS.
    I will migrate your website to a Pelican build with GitHub Flavored 
Markdown (GFM).
    For your reference the already migrated www-site is here 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fwww-site%2F&amp;data=04%7C01%7Caharui%40adobe.com%7C0899ec288d52434074a608d92b74ce48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637588603544156091%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&amp;sdata=Lj%2F1L6vI9aqYGqRDH9NC9lW6YNJl8SAJx0kH2NBzvNI%3D&amp;reserved=0

    The following will occur.
    - flex-site git repository is already a mirror of the CMS content. We’ll 
create a main branch.
    - CMS mdtext and Cmspage files are converted to md and stored in the 
content tree.
    - Page templates will be converted essentially as is with some minor 
improvements.
    - HTML files (apidocs) built separately are copied into the content tree. 

    The Apache CMS had a cumbersome process of individual checkouts -> staging 
-> publishing.
    The new branching strategy is as follows:
    - main will have the site content sources and any additional docs (like api 
docs).
    - asf-site will have the production website which is automatically deployed 
to flex.apache.org.
    During the migration we will deploy to flex.staged.apache.org
    - preview/release will have the website prepared for the next release. You 
will add release specific docs to this branch
    - preview/release-staging will have the built preview website which is 
automatically deployed to flex-release.staged.apache.org

    This new plan allows for a redesign of your site without danger of 
premature deployment.
    If you decide that GFM is not for flex then you can switch to a different 
process within a preview branch.

    Release steps for the website could be:
    - Branch main as preview/release
    - Make your updates to preview/release
    - Confirm your changes on flex-release.staged.apache.org
    - Pull your changes from preview/release to main. flex.apache.org is 
automatically updated.

    All The Best,
    Dave Fisher

Reply via email to