npiyush97
@@ -0,0 +1,19 @@
|
||||
---
|
||||
id: FAQ
|
||||
title: FAQ
|
||||
description: All FAQ related to Questions
|
||||
---
|
||||
|
||||
## FAQS
|
||||
|
||||
[Product FAQS](../faq/product-faq.md)
|
||||
|
||||
[Technical FAQS](../faq/technical.md)
|
||||
|
||||
[Adoption FAQS](../faq/adoption.md)
|
||||
|
||||
[Deployment FAQS](../faq/deployment.md)
|
||||
|
||||
[Framework FAQS](../faq/framework.md)
|
||||
|
||||
[Core features FAQS](../faq/corefeatures.md)
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
id: Adoption FAQs
|
||||
title: Adoption FAQs
|
||||
description: All FAQs related to Adoption
|
||||
---
|
||||
|
||||
## ADOPTION FAQ
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
id: CORE FEATURES FAQs
|
||||
title: Core Features FAQs
|
||||
description: All FAQs related to Core Features
|
||||
---
|
||||
|
||||
## Core Features FAQs
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
id: DEPLOYMENT FAQs
|
||||
title: Deployment FAQs
|
||||
description: All FAQs related to DEPLOYMENT
|
||||
---
|
||||
|
||||
## Deployment FAQs
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
id: FRAMEWORK FAQs
|
||||
title: Framework FAQs
|
||||
description: All FAQ related to FRAMEWORK
|
||||
---
|
||||
|
||||
## FRAMEWORK FAQs
|
||||
@@ -0,0 +1,68 @@
|
||||
---
|
||||
id: Product FAQs
|
||||
title: Product FAQs
|
||||
description: All FAQs related to Product
|
||||
---
|
||||
|
||||
## Product FAQs
|
||||
|
||||
### Can we call Backstage something different? So that it fits our company better?
|
||||
|
||||
Yes, Backstage is just a platform for building your own developer portal. We
|
||||
happen to call our internal version Backstage, as well, as a reference to our
|
||||
music roots. You can call your version whatever suits your team, company, or
|
||||
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](#what-is-a-plugin-in-backstage).
|
||||
|
||||
### How is Backstage licensed?
|
||||
|
||||
Backstage was released as open source 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?
|
||||
|
||||
We hope to see Backstage become the infrastructure standard everywhere. When we
|
||||
saw how much Backstage improved developer experience and productivity
|
||||
internally, we wanted to share those gains. After all, if Backstage can create
|
||||
order in an engineering environment as open and diverse as ours, then we're
|
||||
pretty sure it can create order (and boost productivity) anywhere. To learn
|
||||
more, read our blog post,
|
||||
"[What the heck is Backstage anyway?](https://backstage.io/blog/2020/03/18/what-is-backstage)"
|
||||
|
||||
### Will Spotify's internal plugins be open sourced, too?
|
||||
|
||||
Yes, we've already started releasing open source versions of some of the plugins
|
||||
we use here, and we'll continue to do so.
|
||||
[Plugins](#what-is-a-plugin-in-backstage) are the building blocks of
|
||||
functionality in Backstage. We have over 120 plugins inside Spotify — many of
|
||||
those are specialized for our use, so will remain internal and proprietary to
|
||||
us. But we estimate that about a third of our existing plugins make good open
|
||||
source candidates. (And we'll probably end up writing some brand new ones, too.)
|
||||
|
||||
### What's the roadmap for Backstage?
|
||||
|
||||
We envision three phases, which you can learn about in
|
||||
[our project roadmap](overview/roadmap.md). Even though the open source version
|
||||
of Backstage is relatively new compared to our internal version, we have already
|
||||
begun work on various aspects of all three phases. Looking at the
|
||||
[milestones for active issues](https://github.com/backstage/backstage/milestones)
|
||||
will also give you a sense of our progress.
|
||||
|
||||
### My company doesn't have thousands of developers or services. Is using Backstage excessive for our needs?
|
||||
|
||||
Not at all! A core reason to adopt Backstage is to standardize how software is
|
||||
built at your company. It's easier to decide on those standards as a small
|
||||
company, and grows in importance as the company grows. Backstage sets a
|
||||
foundation, and an early investment in your infrastructure becomes even more
|
||||
valuable as you grow.
|
||||
|
||||
### Our company has a strong design language system/brand that we want to incorporate. Does Backstage support this?
|
||||
|
||||
Yes! The Backstage UI is built using Material UI. With the theming capabilities
|
||||
of Material UI, you are able to adapt the interface to your brand guidelines.
|
||||
@@ -1,73 +1,10 @@
|
||||
---
|
||||
id: FAQ
|
||||
title: FAQ
|
||||
description: All FAQ related to Backstage
|
||||
id: Technical FAQs
|
||||
title: Technical FAQs
|
||||
description: All FAQs related to Technical
|
||||
---
|
||||
|
||||
## Product FAQ
|
||||
|
||||
### Can we call Backstage something different? So that it fits our company better?
|
||||
|
||||
Yes, Backstage is just a platform for building your own developer portal. We
|
||||
happen to call our internal version Backstage, as well, as a reference to our
|
||||
music roots. You can call your version whatever suits your team, company, or
|
||||
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](#what-is-a-plugin-in-backstage).
|
||||
|
||||
### How is Backstage licensed?
|
||||
|
||||
Backstage was released as open source 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?
|
||||
|
||||
We hope to see Backstage become the infrastructure standard everywhere. When we
|
||||
saw how much Backstage improved developer experience and productivity
|
||||
internally, we wanted to share those gains. After all, if Backstage can create
|
||||
order in an engineering environment as open and diverse as ours, then we're
|
||||
pretty sure it can create order (and boost productivity) anywhere. To learn
|
||||
more, read our blog post,
|
||||
"[What the heck is Backstage anyway?](https://backstage.io/blog/2020/03/18/what-is-backstage)"
|
||||
|
||||
### Will Spotify's internal plugins be open sourced, too?
|
||||
|
||||
Yes, we've already started releasing open source versions of some of the plugins
|
||||
we use here, and we'll continue to do so.
|
||||
[Plugins](#what-is-a-plugin-in-backstage) are the building blocks of
|
||||
functionality in Backstage. We have over 120 plugins inside Spotify — many of
|
||||
those are specialized for our use, so will remain internal and proprietary to
|
||||
us. But we estimate that about a third of our existing plugins make good open
|
||||
source candidates. (And we'll probably end up writing some brand new ones, too.)
|
||||
|
||||
### What's the roadmap for Backstage?
|
||||
|
||||
We envision three phases, which you can learn about in
|
||||
[our project roadmap](overview/roadmap.md). Even though the open source version
|
||||
of Backstage is relatively new compared to our internal version, we have already
|
||||
begun work on various aspects of all three phases. Looking at the
|
||||
[milestones for active issues](https://github.com/backstage/backstage/milestones)
|
||||
will also give you a sense of our progress.
|
||||
|
||||
### My company doesn't have thousands of developers or services. Is using Backstage excessive for our needs?
|
||||
|
||||
Not at all! A core reason to adopt Backstage is to standardize how software is
|
||||
built at your company. It's easier to decide on those standards as a small
|
||||
company, and grows in importance as the company grows. Backstage sets a
|
||||
foundation, and an early investment in your infrastructure becomes even more
|
||||
valuable as you grow.
|
||||
|
||||
### Our company has a strong design language system/brand that we want to incorporate. Does Backstage support this?
|
||||
|
||||
Yes! The Backstage UI is built using Material UI. With the theming capabilities
|
||||
of Material UI, you are able to adapt the interface to your brand guidelines.
|
||||
|
||||
## Technical FAQ
|
||||
## Technical FAQs
|
||||
|
||||
### What technology does Backstage use?
|
||||
|
||||
@@ -472,7 +472,15 @@
|
||||
"architecture-decisions/adrs-adr012",
|
||||
"architecture-decisions/adrs-adr013"
|
||||
],
|
||||
"FAQ": ["FAQ"],
|
||||
"FAQ": [
|
||||
"faq/FAQ",
|
||||
"faq/Product FAQs",
|
||||
"faq/Technical FAQs",
|
||||
"faq/Adoption FAQs",
|
||||
"faq/DEPLOYMENT FAQs",
|
||||
"faq/FRAMEWORK FAQs",
|
||||
"faq/CORE FEATURES FAQs"
|
||||
],
|
||||
"Accessibility": ["accessibility/index"]
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user