Canary Pipelines / Ecosystem CI

[thescientist13]

Kind of coming off #560 , it might be good to set up some project configurations such that each time a merge lands on master, we build projects of different configurations. This would be a good way to get an understanding if any changes would potentially break users unexpectedly.

So creating like 2 - 3 repos:

• SPA
• MPA
• etc

---

One motivation behind this is that it might become practical to move the website repo out of the monorepo because we easily find ourselves get into "traffic jams" where we have docs that should accompany a feature, which is great, but then when we merge those docs are live instantaneously, so we more or less have to publish a new version right around there, to avoid docs and npm going out of sync.

In the new workflow

1. PRs would have to happen in both repos
2. Docs would get merged all at once as soon a Greenwood is ready to be made

We might have a next <> master branch sync process so we can merge PRs and then just make one merge into master?