oceanhackweek / oceanhackweek/oceanhackweek.github.io

Transition website away from Netlify and github pages

Open
#316 0 comments 0 reactions 2 assignees View on GitHub

@abkfenris is already working on this.

Since May 9, 2024.

Dominant language
CSS
Stars
12
Forks
49
Avg merge
19m
Merged PRs (30d)
1

Description

The Python 3.8 limitation with Netlify is untenable; among other things, 3.8 official support will end soon. Currently we use Netlify only for the website previews in PR's.

In addition, our pages are hosted on github pages using a scheme that allows us to host previously built pages (OHW19-21) together with newly built, Sphinx based pages. This, too, adds a burden.

See #249 and #237 for related, earlier discussions.

@abkfenris and I met a week ago to discuss this. The plan we came up with to move to ReadTheDocs for both website hosting and PR previews. It will entail:

  • Test moving the ohw19-21 built pages from the master (github pages) branch to source. #314
  • Move the ohw18 built pages from https://github.com/oceanhackweek/ohw2018 to source branch, like ohw19-21 pages.
  • Simplify the environment build process, possibly using pixi
  • Move to ReadTheDocs

We will not move the original Jekyll OHW18-21 files. We don't anticipate a need for editing those old files and rebuilding the pages with Jekyll. Future, occasional need for updating old pages (mainly fixing broken links, if at all) will be done directly on the built HTML pages.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.