From 1f2670990f97cc1fe51d4b596e8d5ba471976d28 Mon Sep 17 00:00:00 2001 From: Niklas Date: Mon, 16 Mar 2020 15:10:35 +0100 Subject: [PATCH] Rephrasing sentences about concepts --- docs/architecture-terminology.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/architecture-terminology.md b/docs/architecture-terminology.md index 89801f11e62cc..15706078964aa 100644 --- a/docs/architecture-terminology.md +++ b/docs/architecture-terminology.md @@ -1,9 +1,9 @@ # Architecture and Terminology -Backstage is constructed out of three parts. We separate Backstage in this way because we see three groups of contributors to make an instance of Backstage a success. +Backstage is constructed out of three parts. We separate Backstage in this way because we see three groups of contributors that work with Backstage in three different ways. -- Core - Base functionality - built by core devs in the open source project -- App - The app is an instance of a Backstage app that is deployed and tweaked. The app ties together core functionality with additional plugins - built and maintained by app developers, usually a productivity team within a company. -- Plugins - Additional functionality to make your Backstage app useful for your company. Plugins can be specific to a company or open sourced and reusable. At Spotify we have over 100 plugins built by over 50 different teams. It is very powerful to have contributions from various infrastructure teams into a single unified developer experience. +- Core - Base functionality built by core devs in the open source project. +- App - The app is an instance of a Backstage app that is deployed and tweaked. The app ties together core functionality with additional plugins. The app is built and maintained by app developers, usually a productivity team within a company. +- Plugins - Additional functionality to make your Backstage app useful for your company. Plugins can be specific to a company or open sourced and reusable. At Spotify we have over 100 plugins built by over 50 different teams. It has been very powerful to get contributions from various infrastructure teams added into a single unified developer experience. [Back to Docs](README.md)