chore: Add documentation of our phased approach to the UX (#15)

bryphe-coder · web-flow · commit ec3685bc1490 · 2022-01-11T13:05:49.000-08:00
diff --git a/README.md b/README.md
@@ -11,3 +11,17 @@ This repository contains source code for Coder V2. Additional documentation:
 
 - `.github/`: Settings for [Dependabot for updating dependencies](https://docs.github.com/en/code-security/supply-chain-security/customizing-dependency-updates) and [build/deploy pipelines with GitHub Actions](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions).
   - [`semantic.yaml`](./github/semantic.yaml): Configuration for [semantic pull requests](https://github.com/apps/semantic-pull-requests)
+
+## Front-End Plan
+
+For the front-end team, we're planning on 2 phases to the 'v2' work:
+
+### Phase 1
+
+Phase 1 is the 'new-wine-in-an-old-bottle' approach - we want to preserve the look and feel (UX) of v1, while testing and validating the market fit of our new v2 provisioner model. This means that we'll preserve Material UI and re-use components from v1 (porting them over to the v2 codebase).
+
+### Phase 2
+
+Phase 2 is the 'new-wine-in-a-new-bottle' - which we can do once we've successfully packaged the new wine in the old bottle.
+
+In other words, once we've validated that the new strategy fits and is desirable for our customers, we'd like to build a new, v2-native UI (leveraging designers on the team to build a first-class experience around the new provisioner model).
