Convert chrisproject.org from jekyll to gatsby

We have started using asciidoc rather than markdown for website content and documentation.

Right now chrisproject.org uses jekyll, which is markdown first although we have an asciidoc plugin for it configured. jekyll has a number of problems, it has some technical debt and is a little hard for new contributors to approach, and it has some security issues too.

A pie-in-the-sky idea we had was to use asciidoc-formatted content for multiple outputs - e.g., one adoc file could output a README into a repo, a static HTML page for the website, and a static HTML page for a documentation site.

I investigated using antora and I believe it doesn't support this "multiple output targets per one file" idea, but Gatsby does. It would be very helpful for someone to fork this website repo and investigate converting it to Gatsby.

The ideal outcome of this ticket:
- An assessment of how realistic it might be to convert this website repo from jekyll to gatsby
- A list of tasks that will need to be completed into order to complete said conversion (if it is possible)