correlaid / correlaid-codes

https://codes.correlaid.org

My Blog

powered by fastpages

What To Do Next?

Great! You have setup your repo. Now its time to start writing content. Some helpful links:

• Writing Blogs With Jupyter

• Writing Blogs With Markdown

• Writing Blog Posts With Word

• (Optional) Preview Your Blog Locally

Note: you may want to remove example blog posts from the _posts, _notebooks or _word folders (but leave them empty, don't delete these folders) if you don't want these blog posts to appear on your site.

Please use the nbdev & blogging channel in the fastai forums for any questions or feature requests.

correlaid-codes's Issues

Improve R integration with new fastpages blog

From Frie:

work on improving R integration: there are some blog posts out there on this topic but this would require a deep dive into how the github actions of fastpages work and trying to expand them to work with output from rmarkdown and move the files where they’re supposed to be.

I think the priority would be:

1. make md with static plots work (e.g. work from this here: https://github.com/KonradUdoHannes/fastpages_tryout/blob/master/_posts/2020-01-07-rmarkdown_test.Rmd - you could copy paste that to the github repo)

2. make html output format work (that requires adding to the github action, i suppose) -> that should solve the interactive stuff

Links on tags page not working

On the blog the tags list the tagged posts correctly, but the hyperlinks to the individual posts are broken.

Analyze fastpages forking

Forking a fastpages repo does not work in the sense, that the fork will not be able to run the blog by itself.
The main reasons are probably

• Github actions don't have a deploy key that fits the fork
• URLs may mismatch

In order to make a workflow possible where users can fork the blog in order to contribute it would be good to understand everything that is required to change a fork into a working copy of the blog. This would benefit users that would allow users to contribute without having to use local docker/docker-compose tools.

The goal of this issue is to collect actions necessary to make a fork working.

In another issue we'll then look into automation (github actions) and documentation to make the gathered steps easier for users.

Missing colab and binder links (buttons) in Preprocessing Madrid Mobility Data blog post?

Are the links to colab and binder on this blog post https://codes.correlaid.org/mobility/preprocessing/2021/02/28/Preprocessing_Madrid_Mobility_Data.html missing on purpose or by mistake? Would love to see it in a colab-notebook and copy/download.

Support Forked Blog Creation and associated Pull Requests with Github Actions

In #14 we analyze how to create a fork of the blog in order to tryout changes on a personal github pages page, and then contribute the changes to the correlaid blog via a pull request. The motivation for this is twofold

• doesn't require the use of docker to deploy locally
• doesn't require write access to the correlaid-codes repository in order to contribute

In order to make the contribution as easy as possible we could try to create github actions to perform some of the steps that are being analyzed in #14. We'll probably not be able to remove manual steps entirely, but the more we can spare the better.

Addtional slash preventing my_icons image from rendering

For the mobility post it was encountered that the included screenshot under my_icons was first not displayed in the blog. The generated html source code contained and image tag of the form
<img src="//images/copied_from_nb/my_icons ...>
The double slash was the only systematic difference from the image embeddd in the fastpages sample post and changing the github pages html (gh-pages branch) manually to
<img src="/images/copied_from_nb/my_icons ...>
corrected the issue. If problems like this happen more systematically the github actions should be investigated. In this case the blog post was created via a pull request, which might be a starting point for investigating the actions.

Add contributing guide to README

step by step instructions for jupyter notebooks and R markdown (HTML output)

Breakthrough infections and Bayes’ Theorem | CorrelAid Code[s]

Breakthrough infections and Bayes’ Theorem | CorrelAid Code[s]

Application of conditional probabilities to vaccine efficiencies.

https://codes.correlaid.org/python/jupyter/covid/bayes/2021/11/28/bayes_vaccination.html

Blogs header bar could use a "How to contribute" section

The blogs header bar (currently containing about, tags, open source and search) Could use an additional section with instructions for how to contribute. It might make sense to include high level descriptions and links to the repository where the readme is intended to give a few more details.

The main goal is to offer an obvious starting point to people visiting the blog page.