From ea0a6436b6fe9038255b0cac16e0e725c6535e51 Mon Sep 17 00:00:00 2001 From: Bryan Phelps Date: Tue, 11 Jan 2022 04:11:46 +0000 Subject: [PATCH 1/3] Add documentation of our phased approach to the UX --- README.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/README.md b/README.md index e5efcd0897f8d..49b485427371b 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 v2 prototyping, we're planning on 2 phases: + +### 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). \ No newline at end of file From 537a696a0872266b0408b94859ef9b0887aab7ce Mon Sep 17 00:00:00 2001 From: Bryan Phelps Date: Tue, 11 Jan 2022 04:12:33 +0000 Subject: [PATCH 2/3] Remove prototyping --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 49b485427371b..69f2106d0cb85 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ This repository contains source code for Coder V2. Additional documentation: ## Front-End Plan -For the v2 prototyping, we're planning on 2 phases: +For the front-end team, we're planning on 2 phases to the 'v2' work: ### Phase 1 ### From 9fdea066ca46db91e6c59ac71dddbb9bc39804d5 Mon Sep 17 00:00:00 2001 From: Bryan Phelps Date: Tue, 11 Jan 2022 04:14:39 +0000 Subject: [PATCH 3/3] Formatting --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 69f2106d0cb85..2b841d4ae953c 100644 --- a/README.md +++ b/README.md @@ -16,12 +16,12 @@ This repository contains source code for Coder V2. Additional documentation: For the front-end team, we're planning on 2 phases to the 'v2' work: -### Phase 1 ### +### 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 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). \ No newline at end of file +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).