paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 48 Packages Projects Releases Wiki Activity

Merge pull request #324 from spotify/freben/faq

Browse Source 
Add FAQ entry for where to develop plugins
This commit is contained in:
Fredrik Adelöw
2020-03-19 16:16:23 +01:00
committed by GitHub
parent bccf62ee52 29ce113096
commit eca2fa04e9
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/FAQ.md
+8
View File
@@ -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.