It will make life much easier if we push generated markdown to a different repo rather than keeping in this repo with all the code.
Chris suggests on the gatsby side to continuing using a "local" source for site build and cloning the markdown content repo in when the site is built. This seems like a decent idea to me.
I'll need to update the build-missing-docs.bash script to use a remote repo rather than this repo. That's a bit more git magic that I don't remember how to do but have done elsewhere before and will find an example that I've done in the past to get it done.
It will make life much easier if we push generated markdown to a different repo rather than keeping in this repo with all the code.
Chris suggests on the gatsby side to continuing using a "local" source for site build and cloning the markdown content repo in when the site is built. This seems like a decent idea to me.
I'll need to update the build-missing-docs.bash script to use a remote repo rather than this repo. That's a bit more git magic that I don't remember how to do but have done elsewhere before and will find an example that I've done in the past to get it done.