From b840db3026e8d365c4e3162c54615788caa1512a Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Tue, 17 Mar 2020 10:54:24 +0100 Subject: [PATCH 1/2] Create FAQ.md --- FAQ.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 FAQ.md diff --git a/FAQ.md b/FAQ.md new file mode 100644 index 0000000000..c9eaa6109f --- /dev/null +++ b/FAQ.md @@ -0,0 +1,14 @@ +# FAQ + +## Why Material-UI? + +The short answer is that it's what we've been using in Backstage internally. + +The original choice is based on Google's material design being a thorough and well +thought out full design system, with many of mature and powerful libraries implementing +both the system itself and auxiliary components that we knew that we would like to use. + +It strikes a good balance between power, customisability, and ease of use. Since a core +focus of Backstage is to make plugin developers productive with as few hurdles as +possible, material-ui lets plugin makers both get going easily with well-known tech +and a large flora of components. From 8aca4ed9f64b27cac19fabffacb35c8e30e891f7 Mon Sep 17 00:00:00 2001 From: Patrik Oldsberg Date: Tue, 17 Mar 2020 12:21:37 +0100 Subject: [PATCH 2/2] Update FAQ.md --- FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/FAQ.md b/FAQ.md index c9eaa6109f..84312a5202 100644 --- a/FAQ.md +++ b/FAQ.md @@ -5,7 +5,7 @@ The short answer is that it's what we've been using in Backstage internally. The original choice is based on Google's material design being a thorough and well -thought out full design system, with many of mature and powerful libraries implementing +thought out full design system, with many mature and powerful libraries implementing both the system itself and auxiliary components that we knew that we would like to use. It strikes a good balance between power, customisability, and ease of use. Since a core