One thing that I would like to establish as part of this de-coupling is a way to have sort of Canary Pipelines in place wherein
- The monorepo always builds the website from latest for its deploy previews
- The website CI builds against the latest in the monorepo
Mainly, this is because having a full website application was extremely useful in identifying unexpected breaking changes, and so having a "real world" app to not only build against, but deploy and test a preview with, was incredibly valuable. So in the process of this new re-structuring, don't want to lose that feedback loop.
This would also encourage us to be eating our own dog food, as it were.
One thing that I would like to establish as part of this de-coupling is a way to have sort of Canary Pipelines in place wherein
Mainly, this is because having a full website application was extremely useful in identifying unexpected breaking changes, and so having a "real world" app to not only build against, but deploy and test a preview with, was incredibly valuable. So in the process of this new re-structuring, don't want to lose that feedback loop.
This would also encourage us to be eating our own dog food, as it were.