CMS Migration for River
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 River'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. - A new git repository is created. river-site is preferred. - CMS mdtext files are converted to md and stored in the content tree. - Permalinks are created in the same manner. - Page templates will be converted essentially as is with some minor improvements. - Site data feeds are analyzed. If required a data model will be created. - HTML files (apidocs) built separately are copied into the content tree. I’ll make a judgement call on if these can be wrapped into the template. 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 river.apache.org. During the migration we will deploy to river.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 river-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 river 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 river-release.staged.apache.org - Pull your changes from preview/release to main. river.apache.org is automatically updated. All The Best, Dave Fisher
Re: CMS Migration for River
Thanks Dave. Do you need anything from the River team for this process? On Sat, May 29, 2021 at 11:43 AM Dave Fisher 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 River'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. > - A new git repository is created. river-site is preferred. > - CMS mdtext files are converted to md and stored in the content tree. > - Permalinks are created in the same manner. > - Page templates will be converted essentially as is with some minor > improvements. > - Site data feeds are analyzed. If required a data model will be created. > - HTML files (apidocs) built separately are copied into the content tree. > I’ll make a judgement call on > if these can be wrapped into the template. > > 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 river.apache.org. > During the migration we will deploy to river.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 river-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 river 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 river-release.staged.apache.org > - Pull your changes from preview/release to main. river.apache.org is > automatically updated. > > All The Best, > Dave Fisher -- Jeremy R. Easton-Marks "être fort pour être utile"
Re: CMS Migration for River
I may have questions once the migration is started. I’ll definitely need review once the new repository with the migrated content is ready. > On May 29, 2021, at 11:28 AM, Jeremy R. Easton-Marks > wrote: > > Thanks Dave. Do you need anything from the River team for this process? > > On Sat, May 29, 2021 at 11:43 AM Dave Fisher 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 River'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. >> - A new git repository is created. river-site is preferred. >> - CMS mdtext files are converted to md and stored in the content tree. >> - Permalinks are created in the same manner. >> - Page templates will be converted essentially as is with some minor >> improvements. >> - Site data feeds are analyzed. If required a data model will be created. >> - HTML files (apidocs) built separately are copied into the content tree. >> I’ll make a judgement call on >> if these can be wrapped into the template. >> >> 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 river.apache.org. >> During the migration we will deploy to river.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 river-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 river 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 river-release.staged.apache.org >> - Pull your changes from preview/release to main. river.apache.org is >> automatically updated. >> >> All The Best, >> Dave Fisher > > > > -- > Jeremy R. Easton-Marks > > "être fort pour être utile"
