Mastering GitHub Pages (Jekyll and GitHub Pages)

I'm currently teaching a computational linguistics course, and for just the second time, I'm using Github Classroom to manage assignments. I might make a few posts about what I've learned in the process, but for now, I think I'll focus on what's gone right, and what's been more challenging in using Github Codespaces. Github Codespaces A Github Codespace is basically a virtual machine hosted by Github with VS Code as the default interface.

Playing with my eLife Lens-inspired article viewer and some recent articles from ZooKeys I regularly come across articles that are incorrectly marked up. As a quick reminder, my viewer takes the DOI for a ZooKeys article (just append it to http://bionames.org/labs/zookeys-viewer/?doi=, e.g. http://bionames.org/labs/zookeys-viewer/?doi=10.3897/zookeys.316.5132), fetches the corresponding XML and displays the article.Taking the article

The science blog archive Rogue Scholar depends heavily on GitHub Actions. They are used to trigger content and metadata extraction of new blog posts and to register DOIs for these posts with Crossref. More recently they have also been used to push this content and metadata to the new InvenioRDM-based Rogue Scholar platform. GitHub Actions are workflows that typically operate on the command line.

I'm teaching a class on quantitative methods in linguistics, and after getting tired, over the years, of debugging everyone's computer before we could get to the content of learning R (much less quantitative methods), I decided to seize control. I'm running the course through GitHub Classroom which comes with an educational allowance for using GitHub codespaces.