Hi, Shawn: There are several technologies that, once set up, make it remarkably easy to edit, expand, and publish your website. Infra uses Pelican and Buildbot, and I find 90% of the process invisible and almost instantaneous. Several projects use Hugo, with the same good usability. If your repository is on Git, there are good continuous-integration features Infra has put in place and will help you deploy.
Andrew <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Thu, Aug 6, 2020 at 10:19 AM Shawn McKinney <smckin...@apache.org> wrote: > > > On Aug 4, 2020, at 11:34 AM, Andrew Wetmore <cottag...@gmail.com> wrote: > > > > The first step for the PMC would be deciding on what replacement > technology to use. There are several available; we have listed some on the > pages I linked to in my first message, and of course there are many tools > that can reliably generate a static website. > > Hello Andrew, > > Thank you for this kind offer of help, we can certainly use it. > > My question, after the migration, how do we manage the new website? Will > it become easier or harder? > > For me that’s the key. As you know, we’re all volunteers, so time is > limited. Worse, we make changes maybe twice a year so it’s difficult to > master a complicated workflow when it’s seldom performed. > > So, I suppose that’s where the marker lies for me. Which of the choices > laid out will be easiest to manage in the future? > > What do you recommend we do? > > — > Shawn > > p.s. I am willing to help with this task once a decision has been made. > > -- Andrew Wetmore http://cottage14.blogspot.com/
