bval-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Fisher <>
Subject Re: CMS Migration for BVal
Date Tue, 01 Jun 2021 20:08:55 GMT
Hi -

Please find your staged site at

The repository is at

Note the mvn generated content should now be committed to GitHub here:

I’ll be updating the files in the next day or two including notes on the migration.

All The Best,

> On May 30, 2021, at 9:54 AM, Matt Benson <> 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 <> 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
>> 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
>> During the migration we will deploy to
>> - 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
>> 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
>> - Pull your changes from preview/release to main. is
>> automatically updated.
>> All The Best,
>> Dave Fisher

View raw message