From ec3685bc149071ee60562a90a0dcaaa7ac39e3c7 Mon Sep 17 00:00:00 2001 From: Bryan Date: Tue, 11 Jan 2022 13:05:49 -0800 Subject: [PATCH] chore: Add documentation of our phased approach to the UX (#15) --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index e5efcd0897..2b841d4ae9 100644 --- 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).