Hi Matt, The site is ready to go.
The README on https://github.com/apache/bval-site has a pointer to the Infra documentation and to migration notes which includes a diff on the markdown. I would like to make this migration live in 72 hours. All The Best, Dave > On Jun 2, 2021, at 5:14 AM, Matt Benson <[email protected]> wrote: > > Hi Dave, > Site looks good. Thanks again for taking this off our plate. I have a few > questions but likely they'll be answered when you fill out the README. What > is next for the project team to do? > > Matt > > On Tue, Jun 1, 2021 at 3:09 PM Dave Fisher <[email protected]> wrote: > >> Hi - >> >> Please find your staged site at https://bval.staged.apache.org >> >> The repository is at https://github.com/apache/bval-site >> >> Note the mvn generated content should now be committed to GitHub here: >> https://github.com/apache/bval-site/tree/main/content/mvnsite >> >> I’ll be updating the README.md files in the next day or two including >> notes on the migration. >> >> All The Best, >> Dave >> >>> On May 30, 2021, at 9:54 AM, Matt Benson <[email protected]> wrote: >>> >>> Hi Dave, >>> I made an attempt some time back at a conversion using Hugo, but >>> encountered some issues and never got a chance to work through these. Our >>> project would definitely appreciate your assistance! >>> >>> Matt >>> >>> On Sat, May 29, 2021, 11:31 AM Dave Fisher <[email protected]> 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 bval'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. bval-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 bval.apache.org. >>>> During the migration we will deploy to bval.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 bval-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 bval 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 bval-release.staged.apache.org >>>> - Pull your changes from preview/release to main. bval.apache.org is >>>> automatically updated. >>>> >>>> All The Best, >>>> Dave Fisher >> >>
