From 2e63a0209470eacc7a99e7797b68e18ef41d104e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20=C3=85lund?= Date: Thu, 2 Apr 2020 20:05:00 +0200 Subject: [PATCH] Add question to FAQ --- docs/FAQ.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 01c3a4f473..5787a6a1f7 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -1,6 +1,6 @@ # FAQ -## Why Material-UI? +## Q: Why Material-UI? The short answer is that it's what we've been using in Backstage internally. @@ -13,7 +13,7 @@ focus of Backstage is to make plugin developers productive with as few hurdles a possible, material-ui lets plugin makers both get going easily with well-known tech and a large flora of components. -## Are you planning on having plugins cooked into the repo or should they be developed in separate repos? +## Q: Are you planning on having plugins cooked into the repo or should they be developed in separate repos? Additional open sourced plugins would be added to the `plugins` directory in this monorepo. @@ -21,7 +21,7 @@ While we encourage using the open soure model, integrators that want to experime Backstage internally may also choose to develop closed source plugins in a manner that suits them best, for example in their respective Backstage source repository. -## Any plans for integrating with other repository managers such as Gitlab or Bitbucket? +## Q: Any plans for integrating with other repository managers such as Gitlab or Bitbucket? We chose Github by the fact that it is the tool that we are most familiar with and that will naturally lead to integrations for Github specifically being developed in an early stage. @@ -32,7 +32,7 @@ as well. Hopefully contributed by the community. And note that implementations of Backstage can be hosted wherever you feel suits your needs best. -## Can Backstage by used for other things than developer portals? +## Q: Can Backstage by used for other things than developer portals? Yes. @@ -40,3 +40,7 @@ The core frontend framework could be used for building any large-scale web appli That being said, in [Phase 2](https://github.com/spotify/backstage#project-roadmap) of the project we will add features that are needed for developer portals and systems for managing software ecosystems. Our ambition will be to keep Backstage modular. +## Q: My company doesn't have thousands of developers. Is Backstage overkill? + +Sure, having something like Backstage gets more important as the number of developers in your company grows. One of the core reasons to adopt Backstage is to help standardise how software is built at your company. Setting guidelines and deciding on standards is easier when your company is smaller. +