From c55fe1fce745ad5f8953fe607cb34440db652848 Mon Sep 17 00:00:00 2001 From: astridx Date: Sun, 19 Jan 2020 19:39:55 +0100 Subject: [PATCH 1/2] wip --- ...X-easier-Onboarding-more-consistent-UI .md | 85 +++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 proposed/Better-UX-easier-Onboarding-more-consistent-UI .md diff --git a/proposed/Better-UX-easier-Onboarding-more-consistent-UI .md b/proposed/Better-UX-easier-Onboarding-more-consistent-UI .md new file mode 100644 index 0000000..dc15477 --- /dev/null +++ b/proposed/Better-UX-easier-Onboarding-more-consistent-UI .md @@ -0,0 +1,85 @@ +# Better UX, easier Onboarding, more consistent UI + +## 1. Summary + +This specification aims to define a more intuitive Backend for output. + +In the *basic mode* the backend will show only important options. +It is going to add a switch for enable a advanced mode. +The *advanced mode* shows all possible options. + + +## 2. Why Bother? + +A good start is essential! + +Most desicions for using or not using a CMS are made during the probation period, +making the first tests with a CMS crucial for ensuring that useres get off to a flying start. + +This in turn is essential for promoting long-term user loyalty. + +A successful user onboarding process helps us increase the user engagement. + +## 3. Scope + +### 3.1 Goals + +This specification aims to provide a clear backend: +A *view* that depends on the needs of the user. + +By default, a simple, clear backend is offered with few but important options. +If a user has more experience, he can switch to advanced mode. +Then he will be offered all possible options. + +### 3.2 Non-Goals + +This specification does not seek to make it possible, that a user can choose +which options he like to see, because this will make everything more complex. +We would like to simplify the backend! + +## 4. Approaches + +### 4.1 Dashboard + +#### System + +In the system dashboard I would suggest to display the red marked areas +in the standard view and the others in the advanced view. + +![System Dashboard Test Administration](https://user-images.githubusercontent.com/9974686/72686157-e4e58d80-3af1-11ea-95a0-405aebfa8570.png) + + +### 4.2 Chosen Approach + +This specification defines Content Elements using the [Composite Pattern][]. + +## 5. Design Decisions + +## 6. People + +### 6.1 Editor(s) + +* This proposal is a result of the *Forum for the Future* and was proposed by Elisa Foltyn. +Editor of this text is Astrid Günther, + + +### 6.2 Sponsors + +* N/A + +### 6.3 Contributors + +* N/A + +## 7. Votes + +* **Entrance Vote:** _(not yet taken)_ +* **Acceptance Vote:** _(not yet taken)_ + +## 8. Relevant Links + +_**Note:** Order descending chronologically._ + +## 9. Errata + +... From 73d7ac1d94a330449ab5cd30453b1e06977a8dbd Mon Sep 17 00:00:00 2001 From: Niels Braczek Date: Wed, 22 Jan 2020 12:45:19 +0100 Subject: [PATCH 2/2] Moved some paragraphs to their right place, fixed typo --- ...nsistent-UI .md => simplify-admin-meta.md} | 26 +++++++++---------- 1 file changed, 12 insertions(+), 14 deletions(-) rename proposed/{Better-UX-easier-Onboarding-more-consistent-UI .md => simplify-admin-meta.md} (88%) diff --git a/proposed/Better-UX-easier-Onboarding-more-consistent-UI .md b/proposed/simplify-admin-meta.md similarity index 88% rename from proposed/Better-UX-easier-Onboarding-more-consistent-UI .md rename to proposed/simplify-admin-meta.md index dc15477..756912e 100644 --- a/proposed/Better-UX-easier-Onboarding-more-consistent-UI .md +++ b/proposed/simplify-admin-meta.md @@ -3,18 +3,14 @@ ## 1. Summary This specification aims to define a more intuitive Backend for output. - -In the *basic mode* the backend will show only important options. -It is going to add a switch for enable a advanced mode. -The *advanced mode* shows all possible options. - +* This proposal is a result of the *Forum for the Future* and was proposed by Elisa Foltyn. ## 2. Why Bother? A good start is essential! -Most desicions for using or not using a CMS are made during the probation period, -making the first tests with a CMS crucial for ensuring that useres get off to a flying start. +Most decisions for using or not using a CMS are made during the probation period, +making the first tests with a CMS crucial for ensuring that users get off to a flying start. This in turn is essential for promoting long-term user loyalty. @@ -27,10 +23,6 @@ A successful user onboarding process helps us increase the user engagement. This specification aims to provide a clear backend: A *view* that depends on the needs of the user. -By default, a simple, clear backend is offered with few but important options. -If a user has more experience, he can switch to advanced mode. -Then he will be offered all possible options. - ### 3.2 Non-Goals This specification does not seek to make it possible, that a user can choose @@ -41,6 +33,14 @@ We would like to simplify the backend! ### 4.1 Dashboard +By default, a simple, clear backend is offered with few but important options. +If a user has more experience, he can switch to advanced mode. +Then he will be offered all possible options. + +In the *basic mode* the backend will show only important options. +It is going to add a switch for enable a advanced mode. +The *advanced mode* shows all possible options. + #### System In the system dashboard I would suggest to display the red marked areas @@ -51,7 +51,6 @@ in the standard view and the others in the advanced view. ### 4.2 Chosen Approach -This specification defines Content Elements using the [Composite Pattern][]. ## 5. Design Decisions @@ -59,8 +58,7 @@ This specification defines Content Elements using the [Composite Pattern][]. ### 6.1 Editor(s) -* This proposal is a result of the *Forum for the Future* and was proposed by Elisa Foltyn. -Editor of this text is Astrid Günther, +Astrid Günther, ### 6.2 Sponsors