> given the refactoring to static site was complete and there didn't seem
> anything necessitating a rollback, I'd propose to move it under the main
> web server.

Thank you for the continued work on it.

Moving is fine. There's 4 GiB free disk space.

> Building and deploying is handled through github CI, if that's fine,
> then all that is left is configuring another ansible host at
> https://github.com/schemeorg-community/index.scheme.org/blob/master/deploy/hosts and creating + setting ssh key secret in https://github.com/schemeorg-community/index.scheme.org/blob/c8f7d9bf347d6a718c015bcc7e2362bfa901c68f/.github/workflows/master.yml#L35 <https://github.com/schemeorg-community/index.scheme.org/blob/c8f7d9bf347d6a718c015bcc7e2362bfa901c68f/.github/workflows/master.yml#L35> . Alternatively I could have a go at setting up a Jenkins pipeline for the new proposed instance I saw floating around.

It would be good to come up with a standard way to build and deploy
static sites.

I think the ideal build is a Docker container that outputs a tar file.
Containers are standardized so they can easily be run on different
platforms, and the tarballs can be easily archived and shipped around
for examination if needed.

Deploys are an open question. We use Ansible to configure servers, but
not to upload sites. Perhaps we should use it for uploads too. Most
deploys have been done with old school shell scripts and rsync so far.
Is there an easy way to trigger Jenkins from GitHub?

Simplicity is an important concern. But not being tied to commercial
platforms is important, too.