From 0bd3ed28be5c236dbc3c5c3b8912536c30aee7ec Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Sun, 28 May 2017 12:46:24 +0200 Subject: [PATCH 1/5] [docs] Add a VISION.md file --- VISION.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 VISION.md diff --git a/VISION.md b/VISION.md new file mode 100644 index 00000000000000..5c2df63d446d56 --- /dev/null +++ b/VISION.md @@ -0,0 +1,17 @@ +# Material UI’s Philosophy + +We are on a mission to provide an elegant implementation of the Material Design Specification. +But we believe we can do more. + +We want Material-UI to become whatever is generally useful for application development in the spirit of the Material Design spec. +This means Material Design with a general use UI library of components that are needed by many. This general use doesn't imply any other design methodology. +It also means we will have components or combinations that are simply not addressed in the spec. + +We also focus on providing all the low-level tools needed to build a rich user-interface with React. +Once you solve the Material design specification (that put the bar very high), +you should be able to take advantage of it for you own business custom style. +We want to see companies succeeding making Material UI matches their brand. We don't want them to feel that their UI looks like another Google product. + +From a user point of view, we want Material UI to be a pleasure to work with. +We want to deliver on fully encapsulated react components. +We want as much developer joy as possible. From 216b0c1978a517150b3fdef212998180ee3529d2 Mon Sep 17 00:00:00 2001 From: Kevin Ross Date: Mon, 29 May 2017 15:14:21 -0500 Subject: [PATCH 2/5] revision for flow of text and intent --- VISION.md | 23 ++++++++++------------- 1 file changed, 10 insertions(+), 13 deletions(-) diff --git a/VISION.md b/VISION.md index 5c2df63d446d56..b9dda7ee04b3ac 100644 --- a/VISION.md +++ b/VISION.md @@ -1,17 +1,14 @@ -# Material UI’s Philosophy +# Material UI’s Vision -We are on a mission to provide an elegant implementation of the Material Design Specification. -But we believe we can do more. +Our vision is to provide an elegant implementation of the [Material Design guidelines](https://material.io/guidelines/) and more. -We want Material-UI to become whatever is generally useful for application development in the spirit of the Material Design spec. -This means Material Design with a general use UI library of components that are needed by many. This general use doesn't imply any other design methodology. -It also means we will have components or combinations that are simply not addressed in the spec. +The Material Design guidelines are an incredible starting point, but they do not provide guidance on all aspects or needs of an application. In addition to the guidelines-specific implementation, we want Material-UI to become whatever is generally useful for application development, all in the spirit of the Material Design guidelines. -We also focus on providing all the low-level tools needed to build a rich user-interface with React. -Once you solve the Material design specification (that put the bar very high), -you should be able to take advantage of it for you own business custom style. -We want to see companies succeeding making Material UI matches their brand. We don't want them to feel that their UI looks like another Google product. +Therefore, Material-UI will be not only an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. This generalized use doesn't imply any other design methodology. It also means we will have components or combinations that are simply not addressed in the design guidelines. -From a user point of view, we want Material UI to be a pleasure to work with. -We want to deliver on fully encapsulated react components. -We want as much developer joy as possible. +We will focus on providing all the low-level tools needed to build a rich user-interface with React. Once we implement the Material design specification (which is a bar set quite high), you should be able to take advantage of it for you own business with any style customization needed. We want to see companies succeeding using Material-UI in a way that matches their brand. We don't want them to feel that their UI simply looks like another Google product. + +From a user point of view, we want Material-UI +- to deliver on fully encapsulated/composable react components +- to be themable/customizable +- to promote developer joy From fdccae370e723087ab8f41a6fd895ebf5e22455e Mon Sep 17 00:00:00 2001 From: Kevin Ross Date: Mon, 29 May 2017 15:15:43 -0500 Subject: [PATCH 3/5] grammar --- VISION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VISION.md b/VISION.md index b9dda7ee04b3ac..17ad060a37caa2 100644 --- a/VISION.md +++ b/VISION.md @@ -4,7 +4,7 @@ Our vision is to provide an elegant implementation of the [Material Design guide The Material Design guidelines are an incredible starting point, but they do not provide guidance on all aspects or needs of an application. In addition to the guidelines-specific implementation, we want Material-UI to become whatever is generally useful for application development, all in the spirit of the Material Design guidelines. -Therefore, Material-UI will be not only an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. This generalized use doesn't imply any other design methodology. It also means we will have components or combinations that are simply not addressed in the design guidelines. +Therefore, Material-UI will be not only be an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. This generalized use doesn't imply any other design methodology. It also means we will have components or combinations that are simply not addressed in the design guidelines. We will focus on providing all the low-level tools needed to build a rich user-interface with React. Once we implement the Material design specification (which is a bar set quite high), you should be able to take advantage of it for you own business with any style customization needed. We want to see companies succeeding using Material-UI in a way that matches their brand. We don't want them to feel that their UI simply looks like another Google product. From 5f6dc72ccebd58161e60d6c965267a96d2a12241 Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Mon, 29 May 2017 22:27:12 +0200 Subject: [PATCH 4/5] Double space --- VISION.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VISION.md b/VISION.md index 17ad060a37caa2..8050bdc097332b 100644 --- a/VISION.md +++ b/VISION.md @@ -6,7 +6,7 @@ The Material Design guidelines are an incredible starting point, but they do not Therefore, Material-UI will be not only be an implementation of the Material Design guidelines, but a general use UI library of components that are needed by many. This generalized use doesn't imply any other design methodology. It also means we will have components or combinations that are simply not addressed in the design guidelines. -We will focus on providing all the low-level tools needed to build a rich user-interface with React. Once we implement the Material design specification (which is a bar set quite high), you should be able to take advantage of it for you own business with any style customization needed. We want to see companies succeeding using Material-UI in a way that matches their brand. We don't want them to feel that their UI simply looks like another Google product. +We will focus on providing all the low-level tools needed to build a rich user-interface with React. Once we implement the Material design specification (which is a bar set quite high), you should be able to take advantage of it for you own business with any style customization needed. We want to see companies succeeding using Material-UI in a way that matches their brand. We don't want them to feel that their UI simply looks like another Google product. From a user point of view, we want Material-UI - to deliver on fully encapsulated/composable react components From e3133cb572e49c2c83506c043fd9c99628fa9e6b Mon Sep 17 00:00:00 2001 From: Olivier Tassinari Date: Wed, 31 May 2017 13:31:46 +0200 Subject: [PATCH 5/5] Take @hei-cea feedback into account --- VISION.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/VISION.md b/VISION.md index 8050bdc097332b..952afd737ba88a 100644 --- a/VISION.md +++ b/VISION.md @@ -11,4 +11,5 @@ We will focus on providing all the low-level tools needed to build a rich user-i From a user point of view, we want Material-UI - to deliver on fully encapsulated/composable react components - to be themable/customizable -- to promote developer joy +- to be cross browser compatible and accessible +- to promote developer joy, a sense of community, and an environment where new and experienced developers can learn from each other