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

Update FAQ.md

Browse Source
This commit is contained in:
Stefan Ålund
2020-03-26 20:37:32 +01:00
committed by GitHub
parent 8c1a2765e0
commit abd3caf246
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/FAQ.md
+4 -2
View File
@@ -32,9 +32,11 @@ as well. Hopefully contributed by the community.
And note that implementations of Backstage can be hosted wherever you feel suits your needs best.
## Is Backstage only suitable for developer portals?
## Can Backstage by used for other things than developer portals?
No, not really. The core frontend framework could be used for building any large-scale web application where multiple teams are building separate parts of the app, but you want the overall experience to be consistent.
Yes.
The core frontend framework could be used for building any large-scale web application where multiple teams are building separate parts of the app, but you want the overall experience to be consistent.
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.