Tag 2023 materials, mint doi, attach html pages as assets to release? about bio_mobilization_workshop HOT 6 CLOSED

Published new release! https://github.com/ioos/bio_mobilization_workshop/releases/tag/2023

https://doi.org/10.5281/zenodo.7401979 - cite all versions
https://doi.org/10.5281/zenodo.7401980 - cite just 2022
https://doi.org/10.5281/zenodo.7896606 - cite just 2023

from bio_mobilization_workshop.

For the later piece, it might be too tricky to do. All the html files will reference local server address http://127.0.0.1:4000 and need to be served via jekyll to link between everything. Having the standalone html files will be less than helpful.

I tried to do it locally by building and serving the website with bundle exec jekyll serve. That created _site/ with all the html for the page. However, when I terminate bundle exec jekyll serve the page no longer resolves. If I pull up the index.html file, it looks like the .css file doesn't read properly either and all the hyperlinks to lesson pages don't resolve to the correct place.

So, after some sleuthing, I don't think it's worth figuring out how to make the standalone html useful.

But, I did find this if someone really wants to go down that road:
https://stackoverflow.com/questions/26778329/running-jekyll-generated-files-without-jekyll-local-server

Additionally, it looks like zenodo does not pull over release artifacts zenodo/zenodo#1235

from bio_mobilization_workshop.

Draft release https://github.com/ioos/bio_mobilization_workshop/releases/edit/untagged-60b7a58a12739cf2ddea

from bio_mobilization_workshop.

updated https://github.com/ioos/bio_mobilization_workshop/releases/edit/untagged-bc205b0defeb08eb2497

from bio_mobilization_workshop.

I think github automatically creates a .zip archive of all files in the repo at the tagged release commit, so everything needed to create the html using jekyll will be there. The site won't be hosted anywhere, but we will be able to revisit that later if we want to.

from bio_mobilization_workshop.

Guess I was wondering what happens when jekyll disappears/breaks? It would be nice to have the html files that any browser could open.

For now, we can leave it as is and think about a path for doing something like this. We can go back to a release and add an asset later, I think.

from bio_mobilization_workshop.