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.
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
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.