Open futuresoup opened 1 year ago
Created a branch to handle my documentation changes
Merged first set of documentation changes, will merge more when done
@ArLough are we still going with the plan to replace this with a new repo instead?
@futuresoup After considering it a bit more, I think we should try making it work as a single repo and just make a prod branch when we deploy.
I think your point from our convo about it being harder to manage issues wise is a good one. Also we plan on eventually integrating it all eventually anyways so it does make sense to keep them in one repo even though they're rn not integrated
If we run into issues, we can always try turning it into a separate repo.
@ArLough I agree - let's try a monorepo!
Here's a summary of the pros & cons if you're curious.
cough cough Just gonna leave this here. I don't mind monorepos
https://medium.com/bitsrc/managing-large-web-applications-with-monorepos-and-workspaces-b12dc11e720b
Start using our Wiki to document what "Data Magic" is and how contributors can quickly get started