The Migration from CMS to ASF-Pelican is completed! https://flex.apache.org/ is ready.
https://github.com/apache/flex-site/ For information about ASF-Pelican: https://infra.apache.org/asf-pelican.html Enjoy! Dave > On Jun 14, 2021, at 11:08 AM, Dave Fisher <w...@apache.org> wrote: > > The migrated website may be viewed at https://flex.staged.apache.org/ > > The code is in https://github.com/apache/flex-site/tree/main > > See the README there for links to details about the migration and ASF pelican. > > The FlexUnit tutorials required the most work. > > Note the old cms git mirror (which is broken (that’s good)) of the CMS was > used. > > Please review, I would like to make this production in the next week. > > All The Best, > Dave > >> On Jun 9, 2021, at 11:30 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://github.com/apache/www-site/ >> >> 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 >
