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

Updated FAQ.md with the correct links (#1308)

Browse Source 
* Updated FAQ.md with the correct links

Two links regarding plugins were broken and now they have been fixed.

* Updated FAQ.md with correct links
This commit is contained in:
Nikki Beesetti
2020-06-17 03:30:39 -05:00
committed by GitHub
parent 4cc2e67e43
commit b073b610f4
1 changed files with 3 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/FAQ.md
+3 -15
View File
@@ -11,15 +11,11 @@ brand.
### Is Backstage a monitoring platform?
No, but it can be! Backstage is designed to be a developer portal for all your
infrastructure tooling, services, and documentation. So, it's not a monitoring
platform — but that doesn't mean you can't integrate a monitoring tool into
Backstage by writing
[a plugin](https://github.com/spotify/faq#what-is-a-plugin-in-backstage).
No, but it can be! Backstage is designed to be a developer portal for all your infrastructure tooling, services, and documentation. So, it's not a monitoring platform — but that doesn't mean you can't integrate a monitoring tool into Backstage by writing [a plugin](https://github.com/spotify/backstage/blob/master/docs/FAQ.md#what-is-a-plugin-in-backstage).
### How is Backstage licensed?
Backstage was released as free and open software by Spotify and is licensed
Backstage was released as open sourced software by Spotify and is licensed
under [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).
### Why did we open source Backstage?
@@ -99,15 +95,7 @@ plugins. ​
### What is a "plugin" in Backstage?
​ Plugins are what provide the feature functionality in Backstage. They are used
to integrate different systems into Backstage's frontend, so that the developer
gets a consistent UX, no matter what tool or service is being accessed on the
other side. ​ Each plugin is treated as a self-contained web app and can include
almost any type of content. Plugins all use a common set of platform APIs and
reusable UI components. Plugins can fetch data either from the backend or an API
exposed through the proxy. ​ Learn more about
[the different components](https://github.com/spotify/backstage#overview) that
make up Backstage. ​
By far, our most-used plugin is our TechDocs plugin, which we use for creating technical documentation. Our philosophy at Spotify is to treat "docs like code", where you write documentation using the same workflow as you write your code. This makes it easier to create, find, and update documentation. We hope to release [the open source version](https://github.com/spotify/backstage/issues/687) in the future. (See also: "[Will Spotify's internal plugins be open sourced, too?](https://github.com/spotify/backstage/blob/master/docs/FAQ.md#what-is-a-plugin-in-backstage)" above)
### Do I have to write plugins in TypeScript?