Currently we have a monorepo based on related modeling work. We organize everything like a blog. There are pros and cons:
Pros:
We can easily create integrate interactive visualization for each model, which makes it easier to compare them.
We can easily filter the blog to only see the relevant projects.
Cons:
Can be confusing at first. There are many files in the repo that are necessary for CI but are junk for most of us.
It is less self-contained. If we publish a paper, and we want people to replicate our code, they'll need to clone everything. This issue is bad (maybe there is a workaround?)
Ofc, we might think of a way to keep both. But I'm not sure how without starting to copy-paste stuff from the project repo back to blog and vice versa.
Currently we have a monorepo based on related modeling work. We organize everything like a blog. There are pros and cons:
Pros:
Cons:
Here is a link to the repo and the blog.
Ofc, we might think of a way to keep both. But I'm not sure how without starting to copy-paste stuff from the project repo back to blog and vice versa.