From 29ce113096b7c549826562afa8a787696ddff9b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fredrik=20Adel=C3=B6w?= Date: Thu, 19 Mar 2020 15:30:22 +0100 Subject: [PATCH] Add FAQ entry for where to develop plugins --- docs/FAQ.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/FAQ.md b/docs/FAQ.md index 84312a5202..3e0093355e 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -12,3 +12,11 @@ It strikes a good balance between power, customisability, and ease of use. Since 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. + +## 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. + +While we encourage using the open soure model, integrators that want to experiment with +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.