Merge pull request #3213 from backstage/rugvip/url-rewrite

rewrite repo location urls
2020-11-03 11:39:19 +01:00
parent 7450c5eabb af141c0766
commit 606625d672
170 changed files with 549 additions and 542 deletions
@@ -6,7 +6,7 @@ Filters passed to the `/entities` endpoint of the catalog has changed format.

 The old way was to pass things on the form `?a=b&c=d`; the new way is to pass
 things on the form `?filter=a=b,c=d`. See discussion in
-[#2910](https://github.com/spotify/backstage/issues/2910) for details.
+[#2910](https://github.com/backstage/backstage/issues/2910) for details.

 The comma separated items within a single filter have an AND between them. If
 multiple such filters are passed, they have an OR between those item groups.
@@ -7,7 +7,7 @@

 <!--- Please include the following in your Pull Request when applicable: -->

- [ ] A changeset describing the change and affected packages. ([more info](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md#creating-changesets))
+- [ ] A changeset describing the change and affected packages. ([more info](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md#creating-changesets))
 - [ ] Added or updated documentation
 - [ ] Tests for new functionality and regression tests for bug fixes
 - [ ] Screenshots attached (for UI changes)
@@ -1,5 +1,5 @@
 name: Automatically add new TechDocs Issues and PRs to the GitHub project board
-# Development of TechDocs in Backstage is managed by this Kanban board - https://github.com/spotify/backstage/projects/5
+# Development of TechDocs in Backstage is managed by this Kanban board - https://github.com/backstage/backstage/projects/5
 # New issues with TechDocs in their title or docs-like-code label will be added to the board.

 on:
@@ -23,7 +23,7 @@ jobs:
          contains(github.event.issue.title, 'techdocs') ||
          contains(github.event.issue.title, 'Techdocs')
        with:
-          project: 'https://github.com/spotify/backstage/projects/5'
+          project: 'https://github.com/backstage/backstage/projects/5'
          column_name: 'Incoming'

      - name: Assign new issue to Incoming based on its label.
@@ -31,7 +31,7 @@ jobs:
        if: |
          contains(github.event.issue.labels.*.name, 'docs-like-code')
        with:
-          project: 'https://github.com/spotify/backstage/projects/5'
+          project: 'https://github.com/backstage/backstage/projects/5'
          column_name: 'Incoming'

      - name: Assign new PR to Incoming based on its title.
@@ -41,7 +41,7 @@ jobs:
          contains(github.event.pull_request.title, 'techdocs') ||
          contains(github.event.pull_request.title, 'Techdocs')
        with:
-          project: 'https://github.com/spotify/backstage/projects/5'
+          project: 'https://github.com/backstage/backstage/projects/5'
          column_name: 'Incoming'

      - name: Assign new PR to Incoming based on its label.
@@ -49,5 +49,5 @@ jobs:
        if: |
          contains(github.event.pull_request.labels.*.name, 'docs-like-code')
        with:
-          project: 'https://github.com/spotify/backstage/projects/5'
+          project: 'https://github.com/backstage/backstage/projects/5'
          column_name: 'Incoming'
@@ -2,7 +2,7 @@

 This is a best-effort changelog where we manually collect breaking changes. It is not an exhaustive list of all changes or even features added.

-If you encounter issues while upgrading to a newer version, don't hesitate to reach out on [Discord](https://discord.gg/EBHEGzX) or [open an issue](https://github.com/spotify/backstage/issues/new/choose)!
+If you encounter issues while upgrading to a newer version, don't hesitate to reach out on [Discord](https://discord.gg/EBHEGzX) or [open an issue](https://github.com/backstage/backstage/issues/new/choose)!

 ## Next Release

@@ -26,18 +26,18 @@ If you encounter issues while upgrading to a newer version, don't hesitate to re

 ### Backend (example-backend, or backends created with @backstage/create-app)

- A plugin database manager has been created, and plugins can now accept that interface as an argument during initialisation. Notably, the `auth` plugin has a [`createRouter` signature change](./plugins/auth-backend/src/service/router.ts). See [packages/backend/src/index.ts](./packages/backend/src/index.ts) on how to set it up. [#2697](https://github.com/spotify/backstage/pull/2697)
+- A plugin database manager has been created, and plugins can now accept that interface as an argument during initialisation. Notably, the `auth` plugin has a [`createRouter` signature change](./plugins/auth-backend/src/service/router.ts). See [packages/backend/src/index.ts](./packages/backend/src/index.ts) on how to set it up. [#2697](https://github.com/backstage/backstage/pull/2697)

 ## v0.1.1-alpha.24

 ### Backend (example-backend, or backends created with @backstage/create-app)

- The default mount point for backend plugins have been changed to `/api`. These changes are done in the backend package itself, so it is recommended that you sync up existing backend packages with this new pattern. [#2562](https://github.com/spotify/backstage/pull/2562)
- A service discovery mechanism for backend plugins has been added, and is now a requirement for several backend plugins. See [packages/backend/src/index.ts](./packages/backend/src/index.ts) for how to set it up using `SingleHostDiscovery` from `@backstage/backend-common`. Note that the default base path for plugins is set to `/api` to that change, but it can be set to use the old behavior via the `basePath` option. [#2600](https://github.com/spotify/backstage/pull/2600)
+- The default mount point for backend plugins have been changed to `/api`. These changes are done in the backend package itself, so it is recommended that you sync up existing backend packages with this new pattern. [#2562](https://github.com/backstage/backstage/pull/2562)
+- A service discovery mechanism for backend plugins has been added, and is now a requirement for several backend plugins. See [packages/backend/src/index.ts](./packages/backend/src/index.ts) for how to set it up using `SingleHostDiscovery` from `@backstage/backend-common`. Note that the default base path for plugins is set to `/api` to that change, but it can be set to use the old behavior via the `basePath` option. [#2600](https://github.com/backstage/backstage/pull/2600)

 ### @backstage/auth-backend

- The default mount path of backend plugins was changed to `/api/:pluginId`, and as part of that it was needed to enable configuration of the base path of the auth backend, so that it can construct redirect URLs correctly. Note that you will also need to reconfigure any allowed redirect URLs to include `/api` if you switch to the new recommended pattern. [#2562](https://github.com/spotify/backstage/pull/2562)
+- The default mount path of backend plugins was changed to `/api/:pluginId`, and as part of that it was needed to enable configuration of the base path of the auth backend, so that it can construct redirect URLs correctly. Note that you will also need to reconfigure any allowed redirect URLs to include `/api` if you switch to the new recommended pattern. [#2562](https://github.com/backstage/backstage/pull/2562)
 - The auth backend now requires an implementation of `PluginEndpointDiscovery` from `@backstage/backend-common` to be passed in as `discovery`. See the changes to `@backstage/backend`.

 ### @backstage/proxy-backend
@@ -50,28 +50,28 @@ If you encounter issues while upgrading to a newer version, don't hesitate to re

 ### @backstage/plugin-identity-backend

- This plugin was removed, remove it from your backend if it's there. [#2616](https://github.com/spotify/backstage/pull/2616)
+- This plugin was removed, remove it from your backend if it's there. [#2616](https://github.com/backstage/backstage/pull/2616)

 ## v0.1.1-alpha.23

 ### @backstage/core

- Renamed `SessionStateApi` to `SessionApi` and `logout` to `signOut`. Custom implementations of the `SingInPage` app-component will need to rename their `logout` function. The different auth provider items for the `UserSettingsMenu` have been consolidated into a single `ProviderSettingsItem`, meaning you need to replace existing usages of `OAuthProviderSettings` and `OIDCProviderSettings`. [#2555](https://github.com/spotify/backstage/pull/2555).
+- Renamed `SessionStateApi` to `SessionApi` and `logout` to `signOut`. Custom implementations of the `SingInPage` app-component will need to rename their `logout` function. The different auth provider items for the `UserSettingsMenu` have been consolidated into a single `ProviderSettingsItem`, meaning you need to replace existing usages of `OAuthProviderSettings` and `OIDCProviderSettings`. [#2555](https://github.com/backstage/backstage/pull/2555).

 ## v0.1.1-alpha.22

 ### @backstage/core

- Introduced initial version of an inverted app/plugin relationship, where plugins export components for apps to use, instead registering themselves directly into the app. This enables more fine-grained control of plugin features, and also composition of plugins such as catalog pages with additional cards and tabs. This breaks the use of `RouteRef`s, and there will be more changes related to this in the future, but this change lays the initial foundation. See `packages/app` and followup PRs for how to update plugins for this change. [#2076](https://github.com/spotify/backstage/pull/2076)
- Switch to an automatic dependency injection mechanism for all Utility APIs, allowing plugins to ship default implementations of their APIs. See [https://backstage.io/docs/api/utility-apis](https://backstage.io/docs/api/utility-apis). [#2285](https://github.com/spotify/backstage/pull/2285)
+- Introduced initial version of an inverted app/plugin relationship, where plugins export components for apps to use, instead registering themselves directly into the app. This enables more fine-grained control of plugin features, and also composition of plugins such as catalog pages with additional cards and tabs. This breaks the use of `RouteRef`s, and there will be more changes related to this in the future, but this change lays the initial foundation. See `packages/app` and followup PRs for how to update plugins for this change. [#2076](https://github.com/backstage/backstage/pull/2076)
+- Switch to an automatic dependency injection mechanism for all Utility APIs, allowing plugins to ship default implementations of their APIs. See [https://backstage.io/docs/api/utility-apis](https://backstage.io/docs/api/utility-apis). [#2285](https://github.com/backstage/backstage/pull/2285)

 ### @backstage/cli

- Change `backstage-cli backend:build-image` to forward all args to `docker image build`, instead of just tag. Also add `--build` flag for building all dependent packages before packaging the workspace for the docker build. [#2299](https://github.com/spotify/backstage/pull/2299)
+- Change `backstage-cli backend:build-image` to forward all args to `docker image build`, instead of just tag. Also add `--build` flag for building all dependent packages before packaging the workspace for the docker build. [#2299](https://github.com/backstage/backstage/pull/2299)

 ### @backstage/create-app

- Change root `tsc` output dir to `dist-types`, in order to allow for standalone plugin repos. [#2278](https://github.com/spotify/backstage/pull/2278)
+- Change root `tsc` output dir to `dist-types`, in order to allow for standalone plugin repos. [#2278](https://github.com/backstage/backstage/pull/2278)

 ### @backstage/catalog-backend

@@ -79,7 +79,7 @@ If you encounter issues while upgrading to a newer version, don't hesitate to re

 ## v0.1.1-alpha.21

- Added many more frontend plugins to the template along with the sidebar. [#1942](https://github.com/spotify/backstage/pull/1942), [#2084](https://github.com/spotify/backstage/pull/2084)
+- Added many more frontend plugins to the template along with the sidebar. [#1942](https://github.com/backstage/backstage/pull/1942), [#2084](https://github.com/backstage/backstage/pull/2084)

 ### @backstage/core

@@ -90,14 +90,14 @@ If you encounter issues while upgrading to a newer version, don't hesitate to re

 ### @backstage/cli

- Set `NODE_ENV` to `test` when running test. [#2214](https://github.com/spotify/backstage/pull/2214)
+- Set `NODE_ENV` to `test` when running test. [#2214](https://github.com/backstage/backstage/pull/2214)

- Fix for backend plugins names requiring to be prefixed with `@backstage` to build. [#2224](https://github.com/spotify/backstage/pull/2224)
+- Fix for backend plugins names requiring to be prefixed with `@backstage` to build. [#2224](https://github.com/backstage/backstage/pull/2224)

 ### @backstage/backend-common

 - The backend plugin
-  [service builder](https://github.com/spotify/backstage/blob/master/packages/backend-common/src/service/lib/ServiceBuilderImpl.ts)
+  [service builder](https://github.com/backstage/backstage/blob/master/packages/backend-common/src/service/lib/ServiceBuilderImpl.ts)
  no longer adds `express.json()` automatically to all routes. While convenient
  in a lot of cases, it also led to problems where for example the proxy
  middleware could hang because the body had already been altered and could not
@@ -107,61 +107,61 @@ If you encounter issues while upgrading to a newer version, don't hesitate to re

 ### @backstage/catalog-backend

- Add rules configuration for catalog location and entity kinds. The default rules should cover most use-cases, but you may need to allow specific entity kinds when using things like Template or Group entities. [#2118](https://github.com/spotify/backstage/pull/2118)
+- Add rules configuration for catalog location and entity kinds. The default rules should cover most use-cases, but you may need to allow specific entity kinds when using things like Template or Group entities. [#2118](https://github.com/backstage/backstage/pull/2118)

 ## v0.1.1-alpha.20

 ### @backstage/cli

- Use config files according to `NODE_ENV` when serving and building frontend packages. [#2077](https://github.com/spotify/backstage/pull/2077)
+- Use config files according to `NODE_ENV` when serving and building frontend packages. [#2077](https://github.com/backstage/backstage/pull/2077)

- Pin `rollup-plugin-dts` to avoid a later broken version. [#2097](https://github.com/spotify/backstage/pull/2097)
+- Pin `rollup-plugin-dts` to avoid a later broken version. [#2097](https://github.com/backstage/backstage/pull/2097)

 ## v0.1.1-alpha.19

 ### @backstage/backend-common

- Allow listen host and port to be configured separately, in order to support PORT environment variables. [#1950](https://github.com/spotify/backstage/pull/1950)
+- Allow listen host and port to be configured separately, in order to support PORT environment variables. [#1950](https://github.com/backstage/backstage/pull/1950)

 ### @backstage/core

- Added new `DiscoveryApi` for discovering backend endpoint in the frontend, and use in most plugins. See [packages/app/src/apis.ts](https://github.com/spotify/backstage/blob/master/packages/app/src/apis.ts) for how to register in your app. [#2074](https://github.com/spotify/backstage/pull/2074)
+- Added new `DiscoveryApi` for discovering backend endpoint in the frontend, and use in most plugins. See [packages/app/src/apis.ts](https://github.com/backstage/backstage/blob/master/packages/app/src/apis.ts) for how to register in your app. [#2074](https://github.com/backstage/backstage/pull/2074)

 ### @backstage/create-app

- Added catalog and scaffolder frontend plugins to the template along with the sidebar. [#1942](https://github.com/spotify/backstage/pull/1942), [#2084](https://github.com/spotify/backstage/pull/2084)
- Many plugins have been added to the catalog and will for now be required to be added to separate apps as well. This will be solved as [#1536](https://github.com/spotify/backstage/issues/1536) gets sorted out, but for now you may need to install some plugins just to get pages to work.
+- Added catalog and scaffolder frontend plugins to the template along with the sidebar. [#1942](https://github.com/backstage/backstage/pull/1942), [#2084](https://github.com/backstage/backstage/pull/2084)
+- Many plugins have been added to the catalog and will for now be required to be added to separate apps as well. This will be solved as [#1536](https://github.com/backstage/backstage/issues/1536) gets sorted out, but for now you may need to install some plugins just to get pages to work.

 ### @backstage/catalog-backend

- Added the possibility to add static locations via `app-config.yaml`. This changed the signature of `new LocationReaders(logger)` inside `packages/backend/src/plugins/catalog.ts` to `new LocationReaders({config, logger})`. [#1890](https://github.com/spotify/backstage/pull/1890)
+- Added the possibility to add static locations via `app-config.yaml`. This changed the signature of `new LocationReaders(logger)` inside `packages/backend/src/plugins/catalog.ts` to `new LocationReaders({config, logger})`. [#1890](https://github.com/backstage/backstage/pull/1890)

 ### @backstage/theme

- Changed the type signature of the palette, removing `sidebar: string` and adding `navigation: { background: string; indicator: string}`. [#1880](https://github.com/spotify/backstage/pull/1880)
+- Changed the type signature of the palette, removing `sidebar: string` and adding `navigation: { background: string; indicator: string}`. [#1880](https://github.com/backstage/backstage/pull/1880)

 ## v0.1.1-alpha.18

 ### @backstage/catalog-backend

- Fixed an issue with duplicated location logs. Applying the database migrations from this fix will clear the existing migration logs. [#1836](https://github.com/spotify/backstage/pull/1836)
+- Fixed an issue with duplicated location logs. Applying the database migrations from this fix will clear the existing migration logs. [#1836](https://github.com/backstage/backstage/pull/1836)

 ### @backstage/auth-backend

 This version fixes a breakage in CSP policies set by the auth backend. If you're facing trouble with auth in alpha.17, upgrade to alpha.18.

- OAuth redirect URLs no longer receive the `env` parameter, as it is now passed through state instead. This will likely require a reconfiguration of the OAuth app, where a redirect URL like `http://localhost:7000/auth/google/handler/frame?env=development` should now be configured as `http://localhost:7000/auth/google/handler/frame`. [#1812](https://github.com/spotify/backstage/pull/1812)
+- OAuth redirect URLs no longer receive the `env` parameter, as it is now passed through state instead. This will likely require a reconfiguration of the OAuth app, where a redirect URL like `http://localhost:7000/auth/google/handler/frame?env=development` should now be configured as `http://localhost:7000/auth/google/handler/frame`. [#1812](https://github.com/backstage/backstage/pull/1812)

 ### @backstage/core

- `SignInPage` props have been changed to receive a list of provider objects instead of simple string identifiers for all but the `'guest'` and `'custom'` providers. This opens up for configuration of custom providers, but may break existing configurations. See [packages/app/src/App.tsx](https://github.com/spotify/backstage/blob/032ba401af36a760efdac41668d7000ccf09bc57/packages/app/src/App.tsx#L36) and [packages/app/src/identityProviders.ts](https://github.com/spotify/backstage/blob/032ba401af36a760efdac41668d7000ccf09bc57/packages/app/src/identityProviders.ts#L24) for how to bring back the existing providers. [#1816](https://github.com/spotify/backstage/pull/1816)
+- `SignInPage` props have been changed to receive a list of provider objects instead of simple string identifiers for all but the `'guest'` and `'custom'` providers. This opens up for configuration of custom providers, but may break existing configurations. See [packages/app/src/App.tsx](https://github.com/backstage/backstage/blob/032ba401af36a760efdac41668d7000ccf09bc57/packages/app/src/App.tsx#L36) and [packages/app/src/identityProviders.ts](https://github.com/backstage/backstage/blob/032ba401af36a760efdac41668d7000ccf09bc57/packages/app/src/identityProviders.ts#L24) for how to bring back the existing providers. [#1816](https://github.com/backstage/backstage/pull/1816)

 ## v0.1.1-alpha.17

 ### @backstage/techdocs-backend

- The techdocs backend now requires more configuration to be supplied when creating the router. See [packages/backend/src/plugins/techdocs.ts](https://github.com/spotify/backstage/blob/0201fd9b4a52429519dd59e9184106ba69456deb/packages/backend/src/plugins/techdocs.ts#L42) for an example. [#1736](https://github.com/spotify/backstage/pull/1736)
+- The techdocs backend now requires more configuration to be supplied when creating the router. See [packages/backend/src/plugins/techdocs.ts](https://github.com/backstage/backstage/blob/0201fd9b4a52429519dd59e9184106ba69456deb/packages/backend/src/plugins/techdocs.ts#L42) for an example. [#1736](https://github.com/backstage/backstage/pull/1736)

 ### @backstage/cli

- The `create-app` command was moved out from the CLI to a standalone package. It's now invoked with `npx @backstage/create-app` instead. [#1745](https://github.com/spotify/backstage/pull/1745)
+- The `create-app` command was moved out from the CLI to a standalone package. It's now invoked with `npx @backstage/create-app` instead. [#1745](https://github.com/backstage/backstage/pull/1745)
@@ -12,11 +12,11 @@ Backstage is released under the Apache2.0 License, and original creations contri

 ## Report bugs

-No one likes bugs. Report bugs as an issue [here](https://github.com/spotify/backstage/issues/new?template=bug_template.md).
+No one likes bugs. Report bugs as an issue [here](https://github.com/backstage/backstage/issues/new?template=bug_template.md).

 ## Fix bugs or build new features

-Look through the GitHub issues for [bugs](https://github.com/spotify/backstage/labels/bugs), [good first issues](https://github.com/spotify/backstage/labels/good%20first%20issue) or [help wanted](https://github.com/spotify/backstage/labels/help%20wanted).
+Look through the GitHub issues for [bugs](https://github.com/backstage/backstage/labels/bugs), [good first issues](https://github.com/backstage/backstage/labels/good%20first%20issue) or [help wanted](https://github.com/backstage/backstage/labels/help%20wanted).

 ## Build a plugin

@@ -24,17 +24,17 @@ The value of Backstage grows with every new plugin that gets added. Wouldn't it

 A great reference example of a plugin can be found on [our blog](https://backstage.io/blog/2020/04/06/lighthouse-plugin) (thanks [@fastfrwrd](https://github.com/fastfrwrd)!)

-What kind of plugins should/could be created? Some inspiration from the 120+ plugins that we have developed inside Spotify can be found [here](https://backstage.io/demos), but we will keep a running list of suggestions labeled with [[plugin]](https://github.com/spotify/backstage/labels/plugin).
+What kind of plugins should/could be created? Some inspiration from the 120+ plugins that we have developed inside Spotify can be found [here](https://backstage.io/demos), but we will keep a running list of suggestions labeled with [[plugin]](https://github.com/backstage/backstage/labels/plugin).

 ## Suggesting a plugin

-If you start developing a plugin that you aim to release as open source, we suggest that you create a [new Issue](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME). This helps the community know what plugins are in development.
+If you start developing a plugin that you aim to release as open source, we suggest that you create a [new Issue](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME). This helps the community know what plugins are in development.

 You can also use this process if you have an idea for a good plugin but you hope that someone else will pick up the work.

 ## Adding Non-code Contributions

-Since there is such a large landscape of possible development, build, and deployment environments, we welcome community contributions in these areas in the [`/contrib`](https://github.com/spotify/backstage/tree/master/contrib) folder of the project. This is an excellent place to put things that help out the community at large, but which may not fit within the scope of the core product to support natively. Here, you will find Helm charts, alternative Docker images, and much more.
+Since there is such a large landscape of possible development, build, and deployment environments, we welcome community contributions in these areas in the [`/contrib`](https://github.com/backstage/backstage/tree/master/contrib) folder of the project. This is an excellent place to put things that help out the community at large, but which may not fit within the scope of the core product to support natively. Here, you will find Helm charts, alternative Docker images, and much more.

 ## Write Documentation

@@ -44,11 +44,11 @@ The current documentation is very limited. Help us make the `/docs` folder come

 We think the best way to ensure different plugins provide a consistent experience is through a solid set of reusable UI/UX components. Backstage uses [Storybook](http://backstage.io/storybook).

-Either help us [create new components](https://github.com/spotify/backstage/labels/help%20wanted) or improve stories for the existing ones (look for files with `*.stories.tsx`).
+Either help us [create new components](https://github.com/backstage/backstage/labels/help%20wanted) or improve stories for the existing ones (look for files with `*.stories.tsx`).

 ## Submit Feedback

-The best way to send feedback is to file [an issue](https://github.com/spotify/backstage/issues).
+The best way to send feedback is to file [an issue](https://github.com/backstage/backstage/issues).

 If you are proposing a feature:

@@ -74,7 +74,7 @@ All code is formatted with `prettier` using the configuration in the repo. If po

 If you're contributing to the backend or CLI tooling, be mindful of cross-platform support. [This](https://shapeshed.com/writing-cross-platform-node/) blog post is a good guide of what to keep in mind when writing cross-platform NodeJS.

-Also be sure to skim through our [ADRs](https://github.com/spotify/backstage/tree/master/docs/architecture-decisions) to see if they cover what you're working on. In particular [ADR006: Avoid React.FC and React.SFC](https://github.com/spotify/backstage/blob/master/docs/architecture-decisions/adr006-avoid-react-fc.md) is one to look out for.
+Also be sure to skim through our [ADRs](https://github.com/backstage/backstage/tree/master/docs/architecture-decisions) to see if they cover what you're working on. In particular [ADR006: Avoid React.FC and React.SFC](https://github.com/backstage/backstage/blob/master/docs/architecture-decisions/adr006-avoid-react-fc.md) is one to look out for.

 If there are any updates in `markdown` file please make sure to run `yarn run lint:docs`. Though it is checked on `lint-staged`. It is required to install [vale](https://docs.errata.ai/vale/install) separately and make sure it is accessed by global command.

@@ -97,7 +97,7 @@ For more information, checkout [adding a changeset](https://github.com/atlassian

 This project adheres to the [Spotify FOSS Code of Conduct][code-of-conduct]. By participating, you are expected to honor this code.

-[code-of-conduct]: https://github.com/spotify/backstage/blob/master/CODE_OF_CONDUCT.md
+[code-of-conduct]: https://github.com/backstage/backstage/blob/master/CODE_OF_CONDUCT.md

 # Security Issues?

@@ -4,11 +4,11 @@

 [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
 [![CNCF Status](https://img.shields.io/badge/cncf%20status-sandbox-blue.svg)](https://www.cncf.io/projects)
-[![Main CI Build](https://github.com/spotify/backstage/workflows/Main%20Master%20Build/badge.svg)](https://github.com/spotify/backstage/actions?query=workflow%3A%22Main+Master+Build%22)
+[![Main CI Build](https://github.com/backstage/backstage/workflows/Main%20Master%20Build/badge.svg)](https://github.com/backstage/backstage/actions?query=workflow%3A%22Main+Master+Build%22)
 [![Discord](https://img.shields.io/discord/687207715902193673)](https://discord.gg/EBHEGzX)
 ![Code style](https://img.shields.io/badge/code_style-prettier-ff69b4.svg)
 [![Codecov](https://img.shields.io/codecov/c/github/spotify/backstage)](https://codecov.io/gh/spotify/backstage)
-[![](https://img.shields.io/npm/v/@backstage/core?label=Version)](https://github.com/spotify/backstage/releases)
+[![](https://img.shields.io/npm/v/@backstage/core?label=Version)](https://github.com/backstage/backstage/releases)

 ## What is Backstage?

@@ -23,7 +23,7 @@ Out of the box, Backstage includes:
 - [Backstage Service Catalog](https://backstage.io/docs/features/software-catalog/software-catalog-overview) for managing all your software (microservices, libraries, data pipelines, websites, ML models, etc.)
 - [Backstage Software Templates](https://backstage.io/docs/features/software-templates/software-templates-index) for quickly spinning up new projects and standardizing your tooling with your organization’s best practices
 - [Backstage TechDocs](https://backstage.io/docs/features/techdocs/techdocs-overview) for making it easy to create, maintain, find, and use technical documentation, using a "docs like code" approach
- Plus, a growing ecosystem of [open source plugins](https://github.com/spotify/backstage/tree/master/plugins) that further expand Backstage’s customizability and functionality
+- Plus, a growing ecosystem of [open source plugins](https://github.com/backstage/backstage/tree/master/plugins) that further expand Backstage’s customizability and functionality

 Backstage was created by Spotify but is now hosted by the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io) as a Sandbox level project. Read the announcement [here](https://backstage.io/blog/2020/09/23/backstage-cncf-sandbox).

@@ -46,8 +46,8 @@ Check out [the documentation](https://backstage.io/docs/getting-started) on how
 ## Community

 - [Discord chatroom](https://discord.gg/MUpMjP2) - Get support or discuss the project
- [Good First Issues](https://github.com/spotify/backstage/contribute) - Start here if you want to contribute
- [RFCs](https://github.com/spotify/backstage/labels/rfc) - Help shape the technical direction
+- [Good First Issues](https://github.com/backstage/backstage/contribute) - Start here if you want to contribute
+- [RFCs](https://github.com/backstage/backstage/labels/rfc) - Help shape the technical direction
 - [FAQ](https://backstage.io/docs/FAQ) - Frequently Asked Questions
 - [Code of Conduct](CODE_OF_CONDUCT.md) - This is how we roll
 - [Adopters](ADOPTERS.md) - Companies already using Backstage
@@ -138,22 +138,22 @@ catalog:
  locations:
    # Backstage example components
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/all-components.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all-components.yaml
    # Example component for github-actions
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/github-actions/examples/sample.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/github-actions/examples/sample.yaml
    # Example component for techdocs
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/techdocs-backend/examples/documented-component/documented-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/techdocs-backend/examples/documented-component/documented-component.yaml
    # Backstage example APIs
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/all-apis.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all-apis.yaml
    # Backstage example templates
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/sample-templates/all-templates.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/sample-templates/all-templates.yaml
    # Backstage example groups and users
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/acme-corp.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/acme-corp.yaml

 scaffolder:
  github:
@@ -6,7 +6,7 @@ metadata:
    Backstage is an open-source developer portal that puts the developer experience first.
  annotations:
    github.com/project-slug: spotify/backstage
-    backstage.io/techdocs-ref: github:https://github.com/spotify/backstage.git
+    backstage.io/techdocs-ref: github:https://github.com/backstage/backstage.git
    lighthouse.com/website-url: https://backstage.io
 spec:
  type: library
@@ -12,7 +12,7 @@ version: 0.1.1
 appVersion: v0.1.1-alpha.23

 sources:
-  - https://github.com/spotify/backstage
+  - https://github.com/backstage/backstage
  - https://github.com/spotify/lighthouse-audit-service

 dependencies:
@@ -36,7 +36,7 @@ appConfig:
 Then use it to run:

 ```
-git clone https://github.com/spotify/backstage.git
+git clone https://github.com/backstage/backstage.git
 cd contrib/chart/backstage
 helm dependency update
 helm install -f backstage-mydomain.yaml backstage .
@@ -18,19 +18,19 @@ catalog:
  locations:
    # Backstage example components
    - type: github
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/all-components.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all-components.yaml
    # Example component for github-actions
    - type: github
-      target: https://github.com/spotify/backstage/blob/master/plugins/github-actions/examples/sample.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/github-actions/examples/sample.yaml
    # Example component for techdocs
    - type: github
-      target: https://github.com/spotify/backstage/blob/master/plugins/techdocs-backend/examples/documented-component/documented-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/techdocs-backend/examples/documented-component/documented-component.yaml
    # Backstage example APIs
    - type: github
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/all-apis.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all-apis.yaml
    # Backstage example templates
    - type: github
-      target: https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/sample-templates/all-templates.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/sample-templates/all-templates.yaml
 {{- else }}
  locations: []
 {{- end }}
@@ -48,11 +48,11 @@ 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](https://github.com/spotify/backstage#project-roadmap).
+[our project roadmap](https://github.com/backstage/backstage#project-roadmap).
 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/spotify/backstage/milestones)
+[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 Backstage overkill?
@@ -87,8 +87,8 @@ well-known tech and a large flora of components.
 ### What technology does Backstage use?

 The codebase is a large-scale React application that uses TypeScript. For
-[Phase 2](https://github.com/spotify/backstage#project-roadmap), we plan to use
-Node.js and GraphQL.
+[Phase 2](https://github.com/backstage/backstage#project-roadmap), we plan to
+use Node.js and GraphQL.

 ### What is the end-to-end user flow? The happy path story.

@@ -116,7 +116,7 @@ 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
+[the different components](https://github.com/backstage/backstage#overview) that
 make up Backstage.

 ### Do I have to write plugins in TypeScript?
@@ -127,10 +127,10 @@ APIs in TypeScript, but aren't forcing it on individual plugins.
 ### How do I find out if a plugin already exists?

 Before you write a plugin,
-[search the plugin issues](https://github.com/spotify/backstage/issues?q=is%3Aissue+label%3Aplugin+)
+[search the plugin issues](https://github.com/backstage/backstage/issues?q=is%3Aissue+label%3Aplugin+)
 to see if it already exists or is in the works. If no one's thought of it yet,
 great! Open a new issue as
-[a plugin suggestion](https://github.com/spotify/backstage/issues/new/choose)
+[a plugin suggestion](https://github.com/backstage/backstage/issues/new/choose)
 and describe what your plugin will do. This will help coordinate our
 contributors' efforts and avoid duplicating existing functionality.

@@ -151,7 +151,7 @@ above)
 ### Are you planning to have plugins baked into the repo? Or should they be developed in separate repos?

 Contributors can add open source plugins to the plugins directory in
-[this monorepo](https://github.com/spotify/backstage). Integrators can then
+[this monorepo](https://github.com/backstage/backstage). Integrators can then
 configure which open source plugins are available to use in their instance of
 the app. Open source plugins are downloaded as npm packages published in the
 open source repository. While we encourage using the open source model, we know
@@ -166,7 +166,7 @@ We chose GitHub because it is the tool that we are most familiar with, so that
 will naturally lead to integrations for GitHub being developed at an early
 stage. Hosting this project on GitHub does not exclude integrations with
 alternatives, such as
-[GitLab](https://github.com/spotify/backstage/issues?q=is%3Aissue+is%3Aopen+GitLab)
+[GitLab](https://github.com/backstage/backstage/issues?q=is%3Aissue+is%3Aopen+GitLab)
 or Bitbucket. We believe that in time there will be plugins that will provide
 functionality for these tools as well. Hopefully, contributed by the community!
 Also note, implementations of Backstage can be hosted wherever you feel suits
@@ -215,17 +215,17 @@ data is shared with.
 Yes. The core frontend framework could be used for building any large-scale web
 application where (1) multiple teams are building separate parts of the app, and
 (2) you want the overall experience to be consistent. That being said, in
-[Phase 2](https://github.com/spotify/backstage#project-roadmap) of the project
+[Phase 2](https://github.com/backstage/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.

 ### How can I get involved?

 Jump right in! Come help us fix some of the
-[early bugs and first issues](https://github.com/spotify/backstage/labels/good%20first%20issue)
-or reach [a new milestone](https://github.com/spotify/backstage/milestones). Or
-write an open source plugin for Backstage, like this
-[Lighthouse plugin](https://github.com/spotify/backstage/tree/master/plugins/lighthouse).
+[early bugs and first issues](https://github.com/backstage/backstage/labels/good%20first%20issue)
+or reach [a new milestone](https://github.com/backstage/backstage/milestones).
+Or write an open source plugin for Backstage, like this
+[Lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse).
 See all the ways you can
-[contribute here](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md).
+[contribute here](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md).
 We'd love to have you as part of the community.
@@ -39,7 +39,7 @@ inside Backstage, or by push events from a CI/CD pipelines, or by webhook
 triggers from the version control system, etc.

 Each file describes one or more entities in accordance with the
-[Backstage System Model](https://github.com/spotify/backstage/issues/390). All
+[Backstage System Model](https://github.com/backstage/backstage/issues/390). All
 of these entities have a common structure and nomenclature, and they are stored
 in the software catalog from which they then can be queried.

@@ -87,7 +87,7 @@ The root envelope object has the following structure.
 ### `apiVersion` and `kind`

 The `kind` is the high level entity type being described, typically from the
-[Backstage system model](https://github.com/spotify/backstage/issues/390). The
+[Backstage system model](https://github.com/backstage/backstage/issues/390). The
 first versions of the catalog will focus on the `Component` kind.

 The `apiVersion`is the version of specification format for that particular
@@ -41,7 +41,7 @@ worker.start();
 ```

 and in a more real life scenario, taken from
-[CatalogClient.test.ts](https://github.com/spotify/backstage/blob/f3245c4f8f0b6b2625c4a6d5d50161b612fb4757/plugins/catalog/src/api/CatalogClient.test.ts)
+[CatalogClient.test.ts](https://github.com/backstage/backstage/blob/f3245c4f8f0b6b2625c4a6d5d50161b612fb4757/plugins/catalog/src/api/CatalogClient.test.ts)

 ```ts
 beforeEach(() => {
@@ -11,7 +11,7 @@ While the spec for the catalog file format is well described in
 to the name of the catalog file.

 Following discussion in
-[Issue 1822](https://github.com/spotify/backstage/pull/1822#pullrequestreview-461253670),
+[Issue 1822](https://github.com/backstage/backstage/pull/1822#pullrequestreview-461253670),
 a decision was made.

 ## Name
@@ -13,7 +13,7 @@ There was also some confusion on how to reference entities in URLs in the
 Backstage frontend.

 Following discussion in
-[Issue 1947](https://github.com/spotify/backstage/issues/1947), a decision was
+[Issue 1947](https://github.com/backstage/backstage/issues/1947), a decision was
 made.

 ## Entity References in YAML files
@@ -25,9 +25,9 @@ Records should be stored under the `architecture-decisions` directory.
 - Address and integrate feedback from the community
 - Eventually, assign a number
 - Add the path of the ADR to the microsite sidebar in
-  [`sidebars.json`](https://github.com/spotify/backstage/blob/master/microsite/sidebars.json)
+  [`sidebars.json`](https://github.com/backstage/backstage/blob/master/microsite/sidebars.json)
 - Add the path of the ADR to the
-  [`mkdocs.yml`](https://github.com/spotify/backstage/blob/master/mkdocs.yml)
+  [`mkdocs.yml`](https://github.com/backstage/backstage/blob/master/mkdocs.yml)
 - Merge the pull request

 ## Superseding an ADR
@@ -58,7 +58,7 @@ token used to make authenticated calls within Backstage.
 The middleware that will be provided by `@backstage/backend-common` allows
 verification of Backstage ID tokens, and optionally loading additional
 information about the user. The progress is tracked in
-https://github.com/spotify/backstage/issues/1435.
+https://github.com/backstage/backstage/issues/1435.

 #### Identity for App Developers

@@ -15,10 +15,10 @@ to various third party APIs.
 There are occasions when the user wants to perform actions towards third party
 services that require authorization via OAuth. Backstage provides standardized
 [Utility APIs](../api/utility-apis.md) such as the
-[GoogleAuthApi](https://github.com/spotify/backstage/blob/master/packages/core-api/src/apis/definitions/auth.ts)
+[GoogleAuthApi](https://github.com/backstage/backstage/blob/master/packages/core-api/src/apis/definitions/auth.ts)
 for that use-case. Backstage also includes a set of implementations of these
 APIs that integrate with the
-[auth-backend](https://github.com/spotify/backstage/tree/master/plugins/auth-backend)
+[auth-backend](https://github.com/backstage/backstage/tree/master/plugins/auth-backend)
 plugin to provide a popup-based OAuth flow.

 ## Background
@@ -58,9 +58,9 @@ easier to make authenticated requests inside a plugin.
 ## OAuth Flow

 The following describes the OAuth flow implemented by the
-[auth-backend](https://github.com/spotify/backstage/tree/master/plugins/auth-backend)
+[auth-backend](https://github.com/backstage/backstage/tree/master/plugins/auth-backend)
 and
-[DefaultAuthConnector](https://github.com/spotify/backstage/blob/master/packages/core-api/src/lib/AuthConnector/DefaultAuthConnector.ts)
+[DefaultAuthConnector](https://github.com/backstage/backstage/blob/master/packages/core-api/src/lib/AuthConnector/DefaultAuthConnector.ts)
 in `@backstage/core-api`.

 Component and APIs can request Access or ID Tokens from any available Auth
@@ -117,7 +117,7 @@ The [ConfigApi](../reference/utility-apis/Config.md) in the frontend is a
 Depending on the config api in another API is slightly different though, as the
 `ConfigApi` implementation is supplied via the App itself and not instantiated
 like other APIs. See
-[packages/app/src/apis.ts](https://github.com/spotify/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/app/src/apis.ts#L66)
+[packages/app/src/apis.ts](https://github.com/backstage/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/app/src/apis.ts#L66)
 for an example of how this wiring is done.

 For standalone plugin setups in `dev/index.ts`, register a factory with a
@@ -129,4 +129,4 @@ from `@backstage/core`.

 In backend plugins the configuration is passed in via options from the main
 backend package. See for example
-[packages/backend/src/plugins/auth.ts](https://github.com/spotify/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/backend/src/plugins/auth.ts#L23).
+[packages/backend/src/plugins/auth.ts](https://github.com/backstage/backstage/blob/244eef851f5aa19f91c7c9b5c12d5df95cf482ca/packages/backend/src/plugins/auth.ts#L23).
@@ -89,7 +89,7 @@ the catalog under the `catalog.locations` key, for example:
 catalog:
  locations:
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
 ```

 The locations added through static configuration can not be removed through the
@@ -36,6 +36,6 @@ through plugins. Different plugins are used for managing different types of
 components.

 For example, the
-[Lighthouse plugin](https://github.com/spotify/backstage/tree/master/plugins/lighthouse)
+[Lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse)
 only makes sense for Websites. The more specific you can be in how you model
 your software, the easier it is to provide plugins that are contextual.
@@ -62,11 +62,11 @@ Users can register new components by going to `/create` and clicking the
 Backstage expects the full URL to the YAML in your source control. Example:

 ```bash
-https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
+https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
 ```

 _More examples can be found
-[here](https://github.com/spotify/backstage/tree/master/packages/catalog-model/examples)._
+[here](https://github.com/backstage/backstage/tree/master/packages/catalog-model/examples)._

 ![](../../assets/software-catalog/bsc-register-2.png)

@@ -91,7 +91,7 @@ above example can be added using the following configuration:
 catalog:
  locations:
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
 ```

 More information about catalog configuration can be found
@@ -135,7 +135,7 @@ in the catalog.
 ![tools](https://backstage.io/blog/assets/20-05-20/tabs.png)

 The Backstage platform can be customized by incorporating
-[existing open source plugins](https://github.com/spotify/backstage/tree/master/plugins),
+[existing open source plugins](https://github.com/backstage/backstage/tree/master/plugins),
 or by [building your own](../../plugins/index.md).

 ## Links
@@ -56,7 +56,7 @@ The catalog components depend on a number of other
 [Utility APIs](../../api/utility-apis.md) to function, including at least the
 `ErrorApi` and `StorageApi`. You can find an example of how to install these in
 your app
-[here](https://github.com/spotify/backstage/blob/61c3a7e5b750dc7c059ef16b188594d31b2c04c2/packages/app/src/apis.ts#L80).
+[here](https://github.com/backstage/backstage/blob/61c3a7e5b750dc7c059ef16b188594d31b2c04c2/packages/app/src/apis.ts#L80).

 ## Gotchas that we will fix

@@ -168,21 +168,21 @@ catalog:
  locations:
    # Backstage Example Component
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/artist-lookup-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/playback-order-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/playback-order-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/podcast-api-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/podcast-api-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/queue-proxy-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/queue-proxy-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/searcher-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/searcher-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/playback-lib-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/playback-lib-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/www-artist-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/www-artist-component.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/packages/catalog-model/examples/shuffle-api-component.yaml
+      target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/shuffle-api-component.yaml
 ```

 ### Running the Backend
@@ -8,7 +8,7 @@ We believe that a strong shared understanding and terminology around software
 and resources leads to a better Backstage experience.

 _This description originates from
-[this RFC](https://github.com/spotify/backstage/issues/390). Note that some of
+[this RFC](https://github.com/backstage/backstage/issues/390). Note that some of
 the concepts are not yet supported in Backstage._

 ## Core Entities
@@ -113,5 +113,5 @@ Backstage currently supports Components and APIs.

 ## Links

- [Original RFC](https://github.com/spotify/backstage/issues/390)
+- [Original RFC](https://github.com/backstage/backstage/issues/390)
 - [YAML file format](../../architecture-decisions/adr002-default-catalog-file-format.md)
@@ -23,7 +23,7 @@ use.
 # Example:
 metadata:
  annotations:
-    backstage.io/managed-by-location: github:http://github.com/spotify/backstage/catalog-info.yaml
+    backstage.io/managed-by-location: github:http://github.com/backstage/backstage/catalog-info.yaml
 ```

 The value of this annotation is a so called location reference string, that
@@ -47,7 +47,7 @@ colon is always present.
 # Example:
 metadata:
  annotations:
-    backstage.io/techdocs-ref: github:https://github.com/spotify/backstage.git
+    backstage.io/techdocs-ref: github:https://github.com/backstage/backstage.git
 ```

 The value of this annotation is a location reference string (see above). If this
@@ -18,7 +18,7 @@ These two are added to the `PreparersBuilder` and then passed into the
 `createRouter` function of the `@spotify/plugin-scaffolder-backend`.

 A full example backend can be found in
-[`scaffolder.ts`](https://github.com/spotify/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
+[`scaffolder.ts`](https://github.com/backstage/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
 but it looks something like the following

 ```ts
@@ -85,8 +85,8 @@ and put the contents into a temporary directory and return that directory path.

 Some good examples exist here:

- https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/prepare/file.ts
- https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/prepare/github.ts
+- https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/prepare/file.ts
+- https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/prepare/github.ts

 ### Registering your own Preparer

@@ -22,7 +22,7 @@ This publisher is passed through to the `createRouter` function of the
 supported, but PR's are always welcome.

 An full example backend can be found
-[here](https://github.com/spotify/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
+[here](https://github.com/backstage/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
 but it looks something like the following

 ```ts
@@ -82,7 +82,7 @@ Now it's up to you to implement the `publish` function and return

 Some good examples exist here:

- https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/publish/github.ts
+- https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/publish/github.ts

 ### Registering your own Publisher

@@ -20,7 +20,7 @@ This templater is added to the `TemplaterBuilder` and then passed into the
 `createRouter` function of the `@spotify/plugin-scaffolder-backend`

 An full example backend can be found
-[here](https://github.com/spotify/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
+[here](https://github.com/backstage/backstage/blob/d91c10f654475a60829fa33a5c81018e517a319a/packages/backend/src/plugins/scaffolder.ts),
 but it looks something like the following

 ```ts
@@ -96,7 +96,7 @@ Now it's up to you to implement the `run` function, and then return a

 Some good examples exist here:

- https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/templater/cookiecutter.ts
+- https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/stages/templater/cookiecutter.ts

 ### Registering your own Templater

@@ -51,7 +51,7 @@ passed through to the scaffolder backend.
 ### How it works

 Most of the heavy lifting is done in the
-[router.ts](https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/src/service/router.ts#L93)
+[router.ts](https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/service/router.ts#L93)
 file in the `scaffolder-backend` plugin.

 There are two routes defined in the router: `POST /v1/jobs` and
@@ -156,11 +156,11 @@ catalog:
  locations:
    # Backstage Example Templates
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/sample-templates/react-ssr-template/template.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/sample-templates/react-ssr-template/template.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/sample-templates/springboot-grpc-template/template.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/sample-templates/springboot-grpc-template/template.yaml
    - type: url
-      target: https://github.com/spotify/backstage/blob/master/plugins/scaffolder-backend/sample-templates/create-react-app/template.yaml
+      target: https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/sample-templates/create-react-app/template.yaml
    - type: url
      target: https://github.com/spotify/cookiecutter-golang/blob/master/template.yaml
 ```
@@ -17,14 +17,14 @@ This page answers frequently asked questions about [TechDocs](README.md).

 TechDocs is using [MkDocs](https://www.mkdocs.org/) to build project
 documentation under the hood. Documentation built with the
-[techdocs-container](https://github.com/spotify/backstage/blob/master/packages/techdocs-container/README.md)
+[techdocs-container](https://github.com/backstage/backstage/blob/master/packages/techdocs-container/README.md)
 is using the MkDocs
 [Material Theme](https://github.com/squidfunk/mkdocs-material).

 #### What is the mkdocs-techdocs-core plugin?

 The
-[mkdocs-techdocs-core](https://github.com/spotify/backstage/blob/master/packages/techdocs-container/techdocs-core/README.md)
+[mkdocs-techdocs-core](https://github.com/backstage/backstage/blob/master/packages/techdocs-container/techdocs-core/README.md)
 package is a MkDocs Plugin that works like a wrapper around multiple MkDocs
 plugins (e.g.
 [MkDocs Monorepo Plugin](https://github.com/spotify/mkdocs-monorepo-plugin)) as
@@ -40,10 +40,10 @@ about TechDocs and the philosophy in its
 | [TechDocs V.2 🔮⌛][v2] | Easy adoption of TechDocs (whatever environment you have) [See V.2 Use Cases.](#techdocs-v2)                                                                |
 | [TechDocs V.3 🔮⌛][v3] | Build a widget (plugin) framework so that contributors can easily contribute features to TechDocs - that others can use. [See V.3 Use Cases.](#techdocs-v3) |

-[v0]: https://github.com/spotify/backstage/milestone/15
-[v1]: https://github.com/spotify/backstage/milestone/16
-[v2]: https://github.com/spotify/backstage/milestone/22
-[v3]: https://github.com/spotify/backstage/milestone/17
+[v0]: https://github.com/backstage/backstage/milestone/15
+[v1]: https://github.com/backstage/backstage/milestone/16
+[v2]: https://github.com/backstage/backstage/milestone/22
+[v3]: https://github.com/backstage/backstage/milestone/17

 <!-- TODO: Add link to milestone for v3 -->

@@ -117,10 +117,10 @@ migrate Spotify's existing TechDocs features to open source.
 [creating and publishing documentation]: creating-and-publishing.md
 [faq]: FAQ.md 'Frequently asked questions'
 [techdocs/frontend]:
-  https://github.com/spotify/backstage/blob/master/plugins/techdocs
+  https://github.com/backstage/backstage/blob/master/plugins/techdocs
 [techdocs/backend]:
-  https://github.com/spotify/backstage/blob/master/plugins/techdocs-backend
+  https://github.com/backstage/backstage/blob/master/plugins/techdocs-backend
 [techdocs/container]:
-  https://github.com/spotify/backstage/blob/master/packages/techdocs-container
+  https://github.com/backstage/backstage/blob/master/packages/techdocs-container
 [techdocs/cli]:
-  https://github.com/spotify/backstage/blob/master/packages/techdocs-cli
+  https://github.com/backstage/backstage/blob/master/packages/techdocs-cli
@@ -14,7 +14,7 @@ The TechDocs Core Plugin is an [MkDocs](https://www.mkdocs.org/) plugin created
 as a wrapper around multiple MkDocs plugins and Python Markdown extensions to
 standardize the configuration of MkDocs used for TechDocs.

-[TechDocs Core](https://github.com/spotify/backstage/blob/master/packages/techdocs-container/techdocs-core/README.md)
+[TechDocs Core](https://github.com/backstage/backstage/blob/master/packages/techdocs-container/techdocs-core/README.md)

 ### TechDocs container

@@ -23,14 +23,14 @@ The TechDocs container is a Docker container available at
 pages, including stylesheets and scripts from Python flavored Markdown, through
 MkDocs.

-[TechDocs Container](https://github.com/spotify/backstage/blob/master/packages/techdocs-container/README.md)
+[TechDocs Container](https://github.com/backstage/backstage/blob/master/packages/techdocs-container/README.md)

 ### TechDocs publisher

 The `techdocs-backend` plugin currently comes with one publisher -
 `LocalPublish`.

-[TechDocs Backend](https://github.com/spotify/backstage/tree/master/plugins/techdocs-backend)
+[TechDocs Backend](https://github.com/backstage/backstage/tree/master/plugins/techdocs-backend)

 More standalone publishers will come in the near future...

@@ -41,7 +41,7 @@ documentation for publishing. Currently it mostly acts as a wrapper around the
 TechDocs container and provides an easy-to-use interface for our docker
 container.

-[TechDocs CLI](https://github.com/spotify/backstage/blob/master/packages/techdocs-cli/README.md)
+[TechDocs CLI](https://github.com/backstage/backstage/blob/master/packages/techdocs-cli/README.md)

 ### TechDocs Reader

@@ -53,7 +53,7 @@ The TechDocs Reader purpose is also to open up the opportunity to integrate
 TechDocs widgets for a customized full-featured TechDocs experience.
 ([coming soon V.3](./README.md#project-roadmap))

-[TechDocs Reader](https://github.com/spotify/backstage/blob/master/plugins/techdocs/src/reader/README.md)
+[TechDocs Reader](https://github.com/backstage/backstage/blob/master/plugins/techdocs/src/reader/README.md)

 ### Transformers

@@ -62,4 +62,4 @@ Reader. The reason why transformers were introduced was to provide a way to
 transform the HTML content on pre and post render (e.g. rewrite docs links or
 modify css).

-[Transformers API docs](https://github.com/spotify/backstage/blob/master/plugins/techdocs/src/reader/README.md)
+[Transformers API docs](https://github.com/backstage/backstage/blob/master/plugins/techdocs/src/reader/README.md)
@@ -37,7 +37,7 @@ in combination with
 [createMuiTheme](https://material-ui.com/customization/theming/#createmuitheme-options-args-theme)
 from [@material-ui/core](https://www.npmjs.com/package/@material-ui/core). See
 the
-[@backstage/theme source](https://github.com/spotify/backstage/tree/master/packages/theme/src)
+[@backstage/theme source](https://github.com/backstage/backstage/tree/master/packages/theme/src)
 and the implementation of the `createTheme` function for how this is done.

 You can also create a theme from scratch that matches the `BackstageTheme` type
@@ -8,7 +8,7 @@ sidebar_label: Kubernetes and Helm
 # Helm charts

 An example Backstage app can be deployed in Kubernetes using the
-[Backstage Helm charts](https://github.com/spotify/backstage/tree/master/contrib/chart/backstage).
+[Backstage Helm charts](https://github.com/backstage/backstage/tree/master/contrib/chart/backstage).

 First, choose a DNS name where Backstage will be hosted, and create a YAML file
 for your custom configuration.
@@ -32,7 +32,7 @@ appConfig:
 Then use it to run:

 ```bash
-git clone https://github.com/spotify/backstage.git
+git clone https://github.com/backstage/backstage.git
 cd contrib/chart/backstage
 helm dependency update
 helm install -f backstage-mydomain.yaml backstage .
@@ -61,4 +61,4 @@ backstage-ingress   *       123.1.2.3       80      17m
 > **NOTE**: this is not a production ready deployment.

 For more information on how to customize the deployment check the
-[README](https://github.com/spotify/backstage/tree/master/contrib/chart/backstage/README.md).
+[README](https://github.com/backstage/backstage/tree/master/contrib/chart/backstage/README.md).
@@ -9,5 +9,5 @@ Beyond that point we do not have an opinionated way to deploy Backstage within
 Kubernetes, as each cluster has its own unique set of tooling and patterns.

 We do provide examples to help you get started though. Check out
-[this example](https://github.com/spotify/backstage/tree/master/contrib/kubernetes/plain_single_backend_deplyoment/)
+[this example](https://github.com/backstage/backstage/tree/master/contrib/kubernetes/plain_single_backend_deplyoment/)
 for a basic single-deployment setup.
@@ -56,7 +56,7 @@ system resources and slow things down.
 ## Package Scripts

 There are many commands to be found in the root
-[package.json](https://github.com/spotify/backstage/blob/master/package.json),
+[package.json](https://github.com/backstage/backstage/blob/master/package.json),
 here are some useful ones:

 ```python
@@ -86,7 +86,7 @@ yarn create-plugin # Create a new plugin
 ```

 > See
-> [package.json](https://github.com/spotify/backstage/blob/master/package.json)
+> [package.json](https://github.com/backstage/backstage/blob/master/package.json)
 > for other yarn commands/options.

 ## Local configuration
@@ -44,7 +44,7 @@ look something like this. You can read more about this process in
 ### Contributing to Backstage

 You can read more in our
-[CONTRIBUTING](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md)
+[CONTRIBUTING](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md)
 guide, which can help you get setup with a Backstage development environment.

 ### Next steps
@@ -84,19 +84,19 @@ exploring.

 But you can also set up any of the available authentication methods. The easiest
 option will be GitHub. To setup GitHub authentication in Backstage, see
-[these instructions](https://github.com/spotify/backstage/tree/master/plugins/auth-backend#github).
+[these instructions](https://github.com/backstage/backstage/tree/master/plugins/auth-backend#github).

 ---

 Congratulations! That should be it. Let us know how it went
 [on discord](https://discord.gg/EBHEGzX), file issues for any
-[feature](https://github.com/spotify/backstage/issues/new?labels=help+wanted&template=feature_template.md)
+[feature](https://github.com/backstage/backstage/issues/new?labels=help+wanted&template=feature_template.md)
 or
-[plugin suggestions](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME),
+[plugin suggestions](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME),
 or
-[bugs](https://github.com/spotify/backstage/issues/new?labels=bug&template=bug_template.md)
+[bugs](https://github.com/backstage/backstage/issues/new?labels=bug&template=bug_template.md)
 you have, and feel free to
-[contribute](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md)!
+[contribute](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md)!

 ## Creating a Plugin

@@ -12,14 +12,14 @@ info:
    The API is supplied with a list of providers - such as `Google` or `Github` - and will add the endpoints
    described below to each of those providers.

-    Read more about [User Authentication and Authorization in Backstage](https://github.com/spotify/backstage/blob/master/docs/auth/overview.md).
+    Read more about [User Authentication and Authorization in Backstage](https://github.com/backstage/backstage/blob/master/docs/auth/overview.md).
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  version: 0.1.1-alpha.8
 externalDocs:
  description: Backstage official documentation
-  url: https://github.com/spotify/backstage/blob/master/docs/README.md
+  url: https://github.com/backstage/backstage/blob/master/docs/README.md
 servers:
  - url: http://localhost:7000/api/auth/
 tags:
@@ -63,17 +63,17 @@ Each plugin is a client side application which mounts itself on the UI. Plugins
 are written in TypeScript or JavaScript. They each live in their own directory
 in `backstage/plugins`. For example, the source code for the lighthouse plugin
 is available at
-[backstage/plugins/lighthouse](https://github.com/spotify/backstage/tree/master/plugins/lighthouse).
+[backstage/plugins/lighthouse](https://github.com/backstage/backstage/tree/master/plugins/lighthouse).

 ### Installing plugins

 Plugins are typically loaded by the UI in your Backstage applications
 `plugins.ts` file. For example,
-[here](https://github.com/spotify/backstage/blob/master/packages/app/src/plugins.ts)
+[here](https://github.com/backstage/backstage/blob/master/packages/app/src/plugins.ts)
 is that file in the Backstage sample app.

 Plugins can be enabled, and passed configuration in `apis.ts`. For example,
-[here](https://github.com/spotify/backstage/blob/master/packages/app/src/apis.ts)
+[here](https://github.com/backstage/backstage/blob/master/packages/app/src/apis.ts)
 is that file in the Backstage sample app.

 This is how the Lighthouse plugin would be enabled in a typical Backstage
@@ -169,8 +169,8 @@ in the future.
 To learn more about the future of databases and Backstage, see the following
 GitHub issues.

- [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/spotify/backstage/issues/1598)
- [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/spotify/backstage/pull/1527#discussion_r450374145)
+- [Knex + Plugins (Multiple vs Single Database) · Issue #1598 · spotify/backstage](https://github.com/backstage/backstage/issues/1598)
+- [Update migrations to support postgres by dariddler · Pull Request #1527 · spotify/backstage](https://github.com/backstage/backstage/pull/1527#discussion_r450374145)

 ## Containerization

@@ -8,7 +8,7 @@ description: Guidelines for how to use the Backstage logos and icons
 Guidelines for how to use the Backstage logo and icon can be found
 [here](/logo_assets/Backstage_Identity_Assets_Overview.pdf). The assets below
 are all in `.svg` format. Other formats are available in the
-[repository](https://github.com/spotify/backstage/tree/master/microsite/static/logo_assets).
+[repository](https://github.com/backstage/backstage/tree/master/microsite/static/logo_assets).

 ## Backstage logo

@@ -9,8 +9,8 @@ description: Roadmap of Backstage Project
 > Backstage is currently under rapid development. This means that you can expect
 > APIs and features to evolve. It is also recommended that teams who adopt
 > Backstage today upgrade their installation as new
-> [releases](https://github.com/spotify/backstage/releases) become available, as
-> Backwards compatibility is not yet guaranteed.
+> [releases](https://github.com/backstage/backstage/releases) become available,
+> as Backwards compatibility is not yet guaranteed.

 ## Phases

@@ -37,34 +37,34 @@ We have divided the project into three high-level _phases_:

 If you have questions about the roadmap or want to provide feedback, we would
 love to hear from you! Please create an
-[Issue](https://github.com/spotify/backstage/issues/new/choose), ping us on
+[Issue](https://github.com/backstage/backstage/issues/new/choose), ping us on
 [Discord](https://discord.gg/EBHEGzX) or reach out directly at
 [alund@spotify.com](mailto:alund@spotify.com).

 Want to help out? Awesome ❤️ Head over to
-[CONTRIBUTING](https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md)
+[CONTRIBUTING](https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md)
 guidelines to get started.

 ### Ongoing work 🚧

- **[Plugins for managing micro services end-2-end](https://github.com/spotify/backstage/milestone/14)**
+- **[Plugins for managing micro services end-2-end](https://github.com/backstage/backstage/milestone/14)**
  Out of the box Backstage will ship with a set of plugins (Overview, CI, API
  and Docs) that will demonstrate how a user can manage a micro service and
  follow a change all the way out in production. Completing this work will make
  it much easier to see how a plugin can be built that integrates with the
  Backstage Service Catalog.

- **[Users and teams](https://github.com/spotify/backstage/issues/1807)**
+- **[Users and teams](https://github.com/backstage/backstage/issues/1807)**
  Ownership is a central concept in Backstage. It should be easy to import your
  existing organizational data, such as users and groups/teams, into Backstage.
  A user the logs into Backstage should see software components owned by the
  team(s) they are in.

- **[Backstage platform is stable](https://github.com/spotify/backstage/milestone/19)** -
+- **[Backstage platform is stable](https://github.com/backstage/backstage/milestone/19)** -
  The platform APIs and features are stable and can be depended on for
  production use. After this plugins will require little to no maintenance.

-* **[Improved Kubernetes plugin](https://github.com/spotify/backstage/issues/2857)** -
+* **[Improved Kubernetes plugin](https://github.com/backstage/backstage/issues/2857)** -
  Native support for Kubernetes, making it easier for developers to see and
  manage their services running in k8s.

@@ -77,21 +77,21 @@ guidelines to get started.
  deployment available publicly so that people can click around and get a feel
  for the product without having to install anything.

- **[Global search](https://github.com/spotify/backstage/issues/1499)** - Extend
-  the basic search available in the Backstage Service Catalog with a global
-  search experience. Long term this search solution should be extensible, making
-  it possible for you add custom search results.
+- **[Global search](https://github.com/backstage/backstage/issues/1499)** -
+  Extend the basic search available in the Backstage Service Catalog with a
+  global search experience. Long term this search solution should be extensible,
+  making it possible for you add custom search results.

- **[[TechDocs V.2] Stabilization release](https://github.com/spotify/backstage/milestone/17)** -
+- **[[TechDocs V.2] Stabilization release](https://github.com/backstage/backstage/milestone/17)** -
  Platform stability and compatibility improvements.

 - **Additional auth providers** - Backstage should work for most (all!) auth
  solutions. Since Backstage can be used by companies regardless of what cloud
  (or on prem) you are using we are especially keen to get auth support for
-  [AWS](https://github.com/spotify/backstage/issues/290),
-  [Azure](https://github.com/spotify/backstage/issues/348) and others.
+  [AWS](https://github.com/backstage/backstage/issues/290),
+  [Azure](https://github.com/backstage/backstage/issues/348) and others.

- **[Initial GraphQL API](https://github.com/spotify/backstage/milestone/13)** -
+- **[Initial GraphQL API](https://github.com/backstage/backstage/milestone/13)** -
  A GraphQL API will open up the rich metadata provided by Backstage in a single
  query. Plugins can easily query this API as well as extend the model where
  needed.
@@ -102,18 +102,18 @@ Building and maintaining [plugins](https://backstage.io/plugins) is the work of
 the entire Backstage community.

 A list of plugins that are in development is
-[available here](https://github.com/spotify/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aplugin+sort%3Areactions-%2B1-desc).
+[available here](https://github.com/backstage/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aplugin+sort%3Areactions-%2B1-desc).
 We strongly recommend to upvote 👍 plugins you are interested in. This helps us
 and the community prioritize what plugins to build.

 Are you missing a plugin for your favorite tool? Please
-[suggest a new one](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
+[suggest a new one](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
 Chances are that someone will jump in and help build it.

 ### Completed milestones ✅

- [Kubernetes plugin - v1](https://github.com/spotify/backstage/tree/master/plugins/kubernetes)
- [Helm charts](https://github.com/spotify/backstage/tree/master/contrib/chart/backstage)
+- [Kubernetes plugin - v1](https://github.com/backstage/backstage/tree/master/plugins/kubernetes)
+- [Helm charts](https://github.com/backstage/backstage/tree/master/contrib/chart/backstage)
 - [Backstage Design System 💅](https://backstage.io/blog/2020/09/30/backstage-design-system)
 - [Cost Insights plugin 💸](https://engineering.atspotify.com/2020/09/29/managing-clouds-from-the-ground-up-cost-engineering-at-spotify/)
 - [Donate Backstage to the CNCF 🎉](https://backstage.io/blog/2020/09/23/backstage-cncf-sandbox)
@@ -123,11 +123,11 @@ Chances are that someone will jump in and help build it.
 - [Backstage Service Catalog (alpha)](https://backstage.io/blog/2020/06/22/backstage-service-catalog-alpha)
 - [Backstage Software Templates (alpha)](https://backstage.io/blog/2020/08/05/announcing-backstage-software-templates)
 - [Make it possible to add custom auth providers](https://backstage.io/blog/2020/07/01/how-to-enable-authentication-in-backstage-using-passport)
- [TechDocs v0](https://github.com/spotify/backstage/milestone/15)
+- [TechDocs v0](https://github.com/backstage/backstage/milestone/15)
 - CI plugins: CircleCI, Jenkins, GitHub Actions and TravisCI
- [Service API documentation](https://github.com/spotify/backstage/pull/1737)
+- [Service API documentation](https://github.com/backstage/backstage/pull/1737)
 - Backstage Service Catalog can read from: GitHub, GitLab,
-  [Bitbucket](https://github.com/spotify/backstage/pull/1938)
+  [Bitbucket](https://github.com/backstage/backstage/pull/1938)
 - Support auth providers: Google, Okta, GitHub, GitLab,
-  [auth0](https://github.com/spotify/backstage/pull/1611),
-  [AWS](https://github.com/spotify/backstage/pull/1990)
+  [auth0](https://github.com/backstage/backstage/pull/1611),
+  [AWS](https://github.com/backstage/backstage/pull/1990)
@@ -30,7 +30,7 @@ Out of the box, Backstage includes:
  code" approach

 - Plus, a growing ecosystem of
-  [open source plugins](https://github.com/spotify/backstage/tree/master/plugins)
+  [open source plugins](https://github.com/backstage/backstage/tree/master/plugins)
  that further expand Backstage’s customizability and functionality

 ## Backstage and the CNCF
@@ -8,7 +8,7 @@ description: Documentation on Adding Plugin to Marketplace

 To add a new plugin to the [plugin marketplace](https://backstage.io/plugins)
 create a file in
-[`microsite/data/plugins`](https://github.com/spotify/backstage/tree/master/microsite/data/plugins)
+[`microsite/data/plugins`](https://github.com/backstage/backstage/tree/master/microsite/data/plugins)
 with your plugin's information. Example:

 ```yaml
@@ -137,7 +137,7 @@ router.use('/summary', async (req, res) => {
 ```

 For a more detailed example, see
-[the lighthouse plugin](https://github.com/spotify/backstage/tree/master/plugins/lighthouse)
+[the lighthouse plugin](https://github.com/backstage/backstage/tree/master/plugins/lighthouse)
 that stores some state in a database and adds new capabilities to the underlying
 API.

@@ -22,7 +22,7 @@ To create a plugin, follow the steps outlined [here](create-a-plugin.md).

 If you start developing a plugin that you aim to release as open source, we
 suggest that you create a
-[new Issue](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
+[new Issue](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME).
 This helps the community know what plugins are in development.

 You can also use this process if you have an idea for a good plugin but you hope
@@ -7,7 +7,7 @@ description: Documentation on Publishing NPM packages
 ## NPM

 NPM packages are published through CI/CD in the
-[.github/workflows/master.yml](https://github.com/spotify/backstage/blob/master/.github/workflows/master.yml)
+[.github/workflows/master.yml](https://github.com/backstage/backstage/blob/master/.github/workflows/master.yml)
 workflow. Every commit that is merged to master will be checked for new versions
 of all public packages, and any new versions will automatically be published to
 NPM.
@@ -106,6 +106,6 @@ environment you will probably face challenges like CORS policies and/or
 backend-side authorization. To smooth this process out you can use proxy -
 either the one you already have (like Nginx, HAProxy, etc.) or the proxy-backend
 plugin that we provide for the Backstage backend.
-[Read more](https://github.com/spotify/backstage/blob/master/plugins/proxy-backend/README.md)
+[Read more](https://github.com/backstage/backstage/blob/master/plugins/proxy-backend/README.md)

 [Back to Getting Started](../README.md)
@@ -1,7 +1,7 @@
 # AlertApi

 The AlertApi type is defined at
-[packages/core-api/src/apis/definitions/AlertApi.ts:29](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L29).
+[packages/core-api/src/apis/definitions/AlertApi.ts:29](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L29).

 The following Utility API implements this type: [alertApiRef](./README.md#alert)

@@ -38,7 +38,7 @@ export type AlertMessage = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/AlertApi.ts:19](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L19).
+[packages/core-api/src/apis/definitions/AlertApi.ts:19](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L19).

 Referenced by: [post](#post), [alert\$](#alert).

@@ -67,7 +67,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [alert\$](#alert).

@@ -86,7 +86,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -109,6 +109,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # AppThemeApi

 The AppThemeApi type is defined at
-[packages/core-api/src/apis/definitions/AppThemeApi.ts:56](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L56).
+[packages/core-api/src/apis/definitions/AppThemeApi.ts:56](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L56).

 The following Utility API implements this type:
 [appThemeApiRef](./README.md#apptheme)
@@ -81,7 +81,7 @@ export type AppTheme = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/AppThemeApi.ts:25](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L25).
+[packages/core-api/src/apis/definitions/AppThemeApi.ts:25](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L25).

 Referenced by: [getInstalledThemes](#getinstalledthemes).

@@ -92,7 +92,7 @@ export type BackstagePalette = Palette &amp; <a href="#paletteadditions">Palette
 </pre>

 Defined at
-[packages/theme/src/types.ts:74](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L74).
+[packages/theme/src/types.ts:74](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L74).

 Referenced by: [BackstageTheme](#backstagetheme).

@@ -107,7 +107,7 @@ export interface BackstageTheme extends Theme {
 </pre>

 Defined at
-[packages/theme/src/types.ts:81](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L81).
+[packages/theme/src/types.ts:81](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L81).

 Referenced by: [AppTheme](#apptheme).

@@ -136,7 +136,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [activeThemeId\$](#activethemeid).

@@ -155,7 +155,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -170,7 +170,7 @@ export type PageTheme = {
 </pre>

 Defined at
-[packages/theme/src/types.ts:103](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L103).
+[packages/theme/src/types.ts:103](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L103).

 Referenced by: [BackstageTheme](#backstagetheme).

@@ -183,7 +183,7 @@ export type PageThemeSelector = {
 </pre>

 Defined at
-[packages/theme/src/types.ts:77](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L77).
+[packages/theme/src/types.ts:77](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L77).

 Referenced by: [BackstageTheme](#backstagetheme).

@@ -243,7 +243,7 @@ type PaletteAdditions = {
 </pre>

 Defined at
-[packages/theme/src/types.ts:23](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L23).
+[packages/theme/src/types.ts:23](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/theme/src/types.ts#L23).

 Referenced by: [BackstagePalette](#backstagepalette).

@@ -266,6 +266,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # BackstageIdentityApi

 The BackstageIdentityApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:134](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L134).
+[packages/core-api/src/apis/definitions/auth.ts:134](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L134).

 The following Utility APIs implement this type:

@@ -70,7 +70,7 @@ export type AuthRequestOptions = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).
+[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).

 Referenced by: [getBackstageIdentity](#getbackstageidentity).

@@ -91,6 +91,6 @@ export type BackstageIdentity = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:147](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L147).
+[packages/core-api/src/apis/definitions/auth.ts:147](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L147).

 Referenced by: [getBackstageIdentity](#getbackstageidentity).
@@ -1,7 +1,7 @@
 # Config

 The Config type is defined at
-[packages/config/src/types.ts:32](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L32).
+[packages/config/src/types.ts:32](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L32).

 The following Utility API implements this type:
 [configApiRef](./README.md#config)
@@ -140,7 +140,7 @@ export type Config = {
 </pre>

 Defined at
-[packages/config/src/types.ts:32](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L32).
+[packages/config/src/types.ts:32](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L32).

 Referenced by: [getConfig](#getconfig), [getOptionalConfig](#getoptionalconfig),
 [getConfigArray](#getconfigarray),
@@ -153,7 +153,7 @@ export type JsonArray = <a href="#jsonvalue">JsonValue</a>[]
 </pre>

 Defined at
-[packages/config/src/types.ts:18](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L18).
+[packages/config/src/types.ts:18](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L18).

 Referenced by: [JsonValue](#jsonvalue).

@@ -164,7 +164,7 @@ export type JsonObject = { [key in string]?: <a href="#jsonvalue">JsonValue</a>
 </pre>

 Defined at
-[packages/config/src/types.ts:17](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L17).
+[packages/config/src/types.ts:17](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L17).

 Referenced by: [JsonValue](#jsonvalue).

@@ -181,7 +181,7 @@ export type JsonValue =
 </pre>

 Defined at
-[packages/config/src/types.ts:19](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L19).
+[packages/config/src/types.ts:19](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/config/src/types.ts#L19).

 Referenced by: [get](#get), [getOptional](#getoptional),
 [JsonObject](#jsonobject), [JsonArray](#jsonarray), [Config](#config).
@@ -1,7 +1,7 @@
 # DiscoveryApi

 The DiscoveryApi type is defined at
-[packages/core-api/src/apis/definitions/DiscoveryApi.ts:30](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/DiscoveryApi.ts#L30).
+[packages/core-api/src/apis/definitions/DiscoveryApi.ts:30](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/DiscoveryApi.ts#L30).

 The following Utility API implements this type:
 [discoveryApiRef](./README.md#discovery)
@@ -1,7 +1,7 @@
 # ErrorApi

 The ErrorApi type is defined at
-[packages/core-api/src/apis/definitions/ErrorApi.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L53).
+[packages/core-api/src/apis/definitions/ErrorApi.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L53).

 The following Utility API implements this type: [errorApiRef](./README.md#error)

@@ -41,7 +41,7 @@ type Error = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/ErrorApi.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L24).
+[packages/core-api/src/apis/definitions/ErrorApi.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L24).

 Referenced by: [post](#post), [error\$](#error).

@@ -58,7 +58,7 @@ export type ErrorContext = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/ErrorApi.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L33).
+[packages/core-api/src/apis/definitions/ErrorApi.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L33).

 Referenced by: [post](#post), [error\$](#error).

@@ -87,7 +87,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [error\$](#error).

@@ -106,7 +106,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -129,6 +129,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # FeatureFlagsApi

 The FeatureFlagsApi type is defined at
-[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:60](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L60).
+[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:60](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L60).

 The following Utility API implements this type:
 [featureFlagsApiRef](./README.md#featureflags)
@@ -68,7 +68,7 @@ export type FeatureFlag = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:31](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L31).
+[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:31](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L31).

 Referenced by: [registerFlag](#registerflag),
 [getRegisteredFlags](#getregisteredflags).
@@ -83,7 +83,7 @@ export enum FeatureFlagState {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:36](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L36).
+[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:36](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L36).

 Referenced by: [FeatureFlagsSaveOptions](#featureflagssaveoptions).

@@ -108,6 +108,6 @@ export type FeatureFlagsSaveOptions = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:44](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L44).
+[packages/core-api/src/apis/definitions/FeatureFlagsApi.ts:44](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L44).

 Referenced by: [save](#save).
@@ -1,7 +1,7 @@
 # IdentityApi

 The IdentityApi type is defined at
-[packages/core-api/src/apis/definitions/IdentityApi.ts:22](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/IdentityApi.ts#L22).
+[packages/core-api/src/apis/definitions/IdentityApi.ts:22](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/IdentityApi.ts#L22).

 The following Utility API implements this type:
 [identityApiRef](./README.md#identity)
@@ -76,6 +76,6 @@ export type ProfileInfo = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:162](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L162).
+[packages/core-api/src/apis/definitions/auth.ts:162](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L162).

 Referenced by: [getProfile](#getprofile).
@@ -1,7 +1,7 @@
 # OAuthApi

 The OAuthApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:67](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L67).
+[packages/core-api/src/apis/definitions/auth.ts:67](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L67).

 The following Utility APIs implement this type:

@@ -82,7 +82,7 @@ export type AuthRequestOptions = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).
+[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).

 Referenced by: [getAccessToken](#getaccesstoken).

@@ -108,6 +108,6 @@ export type OAuthScope = string | string[]
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:38](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L38).
+[packages/core-api/src/apis/definitions/auth.ts:38](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L38).

 Referenced by: [getAccessToken](#getaccesstoken).
@@ -1,7 +1,7 @@
 # OAuthRequestApi

 The OAuthRequestApi type is defined at
-[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:99](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L99).
+[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:99](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L99).

 The following Utility API implements this type:
 [oauthRequestApiRef](./README.md#oauthrequest)
@@ -73,7 +73,7 @@ export type AuthProvider = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:27](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L27).
+[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:27](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L27).

 Referenced by: [AuthRequesterOptions](#authrequesteroptions),
 [PendingAuthRequest](#pendingauthrequest).
@@ -97,7 +97,7 @@ export type AuthRequester&lt;AuthResponse&gt; = (
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:66](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L66).
+[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:66](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L66).

 Referenced by: [createAuthRequester](#createauthrequester).

@@ -122,7 +122,7 @@ export type AuthRequesterOptions&lt;AuthResponse&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:43](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L43).
+[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:43](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L43).

 Referenced by: [createAuthRequester](#createauthrequester).

@@ -151,7 +151,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [authRequest\$](#authrequest).

@@ -170,7 +170,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -205,7 +205,7 @@ export type PendingAuthRequest = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:77](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L77).
+[packages/core-api/src/apis/definitions/OAuthRequestApi.ts:77](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L77).

 Referenced by: [authRequest\$](#authrequest).

@@ -228,6 +228,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # OpenIdConnectApi

 The OpenIdConnectApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:99](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L99).
+[packages/core-api/src/apis/definitions/auth.ts:99](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L99).

 The following Utility APIs implement this type:

@@ -66,6 +66,6 @@ export type AuthRequestOptions = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).
+[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).

 Referenced by: [getIdToken](#getidtoken).
@@ -1,7 +1,7 @@
 # ProfileInfoApi

 The ProfileInfoApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:117](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L117).
+[packages/core-api/src/apis/definitions/auth.ts:117](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L117).

 The following Utility APIs implement this type:

@@ -67,7 +67,7 @@ export type AuthRequestOptions = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).
+[packages/core-api/src/apis/definitions/auth.ts:40](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L40).

 Referenced by: [getProfile](#getprofile).

@@ -95,6 +95,6 @@ export type ProfileInfo = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:162](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L162).
+[packages/core-api/src/apis/definitions/auth.ts:162](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L162).

 Referenced by: [getProfile](#getprofile).
@@ -3,7 +3,7 @@
 The following is a list of all Utility APIs defined by `@backstage/core`. They
 are available to use by plugins and components, and can be accessed using the
 `useApi` hook, also provided by `@backstage/core`. For more information, see
-https://github.com/spotify/backstage/blob/master/docs/api/utility-apis.md.
+https://github.com/backstage/backstage/blob/master/docs/api/utility-apis.md.

 ### alert

@@ -12,7 +12,7 @@ Used to report alerts and forward them to the app
 Implemented type: [AlertApi](./AlertApi.md)

 ApiRef:
-[alertApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L41)
+[alertApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AlertApi.ts#L41)

 ### appTheme

@@ -21,7 +21,7 @@ API Used to configure the app theme, and enumerate options
 Implemented type: [AppThemeApi](./AppThemeApi.md)

 ApiRef:
-[appThemeApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L80)
+[appThemeApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/AppThemeApi.ts#L80)

 ### auth0Auth

@@ -32,7 +32,7 @@ Implemented types: [OpenIdConnectApi](./OpenIdConnectApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[auth0AuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L275)
+[auth0AuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L275)

 ### config

@@ -41,7 +41,7 @@ Used to access runtime configuration
 Implemented type: [Config](./Config.md)

 ApiRef:
-[configApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ConfigApi.ts#L22)
+[configApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ConfigApi.ts#L22)

 ### discovery

@@ -50,7 +50,7 @@ Provides service discovery of backend plugins
 Implemented type: [DiscoveryApi](./DiscoveryApi.md)

 ApiRef:
-[discoveryApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/DiscoveryApi.ts#L44)
+[discoveryApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/DiscoveryApi.ts#L44)

 ### error

@@ -59,7 +59,7 @@ Used to report errors and forward them to the app
 Implemented type: [ErrorApi](./ErrorApi.md)

 ApiRef:
-[errorApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L65)
+[errorApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/ErrorApi.ts#L65)

 ### featureFlags

@@ -68,7 +68,7 @@ Used to toggle functionality in features across Backstage
 Implemented type: [FeatureFlagsApi](./FeatureFlagsApi.md)

 ApiRef:
-[featureFlagsApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L83)
+[featureFlagsApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/FeatureFlagsApi.ts#L83)

 ### githubAuth

@@ -79,7 +79,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[githubAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L232)
+[githubAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L232)

 ### gitlabAuth

@@ -90,7 +90,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[gitlabAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L262)
+[gitlabAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L262)

 ### googleAuth

@@ -102,7 +102,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[googleAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L215)
+[googleAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L215)

 ### identity

@@ -111,7 +111,7 @@ Provides access to the identity of the signed in user
 Implemented type: [IdentityApi](./IdentityApi.md)

 ApiRef:
-[identityApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/IdentityApi.ts#L54)
+[identityApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/IdentityApi.ts#L54)

 ### microsoftAuth

@@ -123,7 +123,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[microsoftAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L289)
+[microsoftAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L289)

 ### oauth2

@@ -135,7 +135,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[oauth2ApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L303)
+[oauth2ApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L303)

 ### oauthRequest

@@ -144,7 +144,7 @@ An API for implementing unified OAuth flows in Backstage
 Implemented type: [OAuthRequestApi](./OAuthRequestApi.md)

 ApiRef:
-[oauthRequestApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L130)
+[oauthRequestApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/OAuthRequestApi.ts#L130)

 ### oktaAuth

@@ -156,7 +156,7 @@ Implemented types: [OAuthApi](./OAuthApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[oktaAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L245)
+[oktaAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L245)

 ### samlAuth

@@ -166,7 +166,7 @@ Implemented types: [ProfileInfoApi](./ProfileInfoApi.md),
 [BackstageIdentityApi](./BackstageIdentityApi.md), [SessionApi](./SessionApi.md)

 ApiRef:
-[samlAuthApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L317)
+[samlAuthApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L317)

 ### storage

@@ -175,4 +175,4 @@ Provides the ability to store data which is unique to the user
 Implemented type: [StorageApi](./StorageApi.md)

 ApiRef:
-[storageApiRef](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L68)
+[storageApiRef](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L68)
@@ -1,7 +1,7 @@
 # SessionApi

 The SessionApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:190](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L190).
+[packages/core-api/src/apis/definitions/auth.ts:190](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L190).

 The following Utility APIs implement this type:

@@ -77,7 +77,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [sessionState\$](#sessionstate).

@@ -96,7 +96,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -112,7 +112,7 @@ export enum SessionState {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:182](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L182).
+[packages/core-api/src/apis/definitions/auth.ts:182](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/auth.ts#L182).

 Referenced by: [sessionState\$](#sessionstate).

@@ -135,6 +135,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # SessionStateApi

 The SessionStateApi type is defined at
-[packages/core-api/src/apis/definitions/auth.ts:201](https://github.com/spotify/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/apis/definitions/auth.ts#L201).
+[packages/core-api/src/apis/definitions/auth.ts:201](https://github.com/backstage/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/apis/definitions/auth.ts#L201).

 The following Utility APIs implement this type:

@@ -56,7 +56,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L53).

 Referenced by: [sessionState\$](#sessionstate).

@@ -75,7 +75,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -91,7 +91,7 @@ export enum SessionState {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/auth.ts:192](https://github.com/spotify/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/apis/definitions/auth.ts#L192).
+[packages/core-api/src/apis/definitions/auth.ts:192](https://github.com/backstage/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/apis/definitions/auth.ts#L192).

 Referenced by: [sessionState\$](#sessionstate).

@@ -114,6 +114,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/82d329555c16af46db9b4e5cd2f44a3cc006a52e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -1,7 +1,7 @@
 # StorageApi

 The StorageApi type is defined at
-[packages/core-api/src/apis/definitions/StorageApi.ts:31](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L31).
+[packages/core-api/src/apis/definitions/StorageApi.ts:31](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L31).

 The following Utility API implements this type:
 [storageApiRef](./README.md#storage)
@@ -79,7 +79,7 @@ export type Observable&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:53](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).
+[packages/core-api/src/types.ts:53](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L53).

 Referenced by: [observe\$](#observe), [StorageApi](#storageapi).

@@ -98,7 +98,7 @@ export type Observer&lt;T&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:24](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).
+[packages/core-api/src/types.ts:24](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L24).

 Referenced by: [Observable](#observable).

@@ -144,7 +144,7 @@ export interface StorageApi {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/StorageApi.ts:31](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L31).
+[packages/core-api/src/apis/definitions/StorageApi.ts:31](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L31).

 Referenced by: [forBucket](#forbucket).

@@ -158,7 +158,7 @@ export type StorageValueChange&lt;T = any&gt; = {
 </pre>

 Defined at
-[packages/core-api/src/apis/definitions/StorageApi.ts:21](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L21).
+[packages/core-api/src/apis/definitions/StorageApi.ts:21](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/apis/definitions/StorageApi.ts#L21).

 Referenced by: [observe\$](#observe), [StorageApi](#storageapi).

@@ -181,6 +181,6 @@ export type Subscription = {
 </pre>

 Defined at
-[packages/core-api/src/types.ts:33](https://github.com/spotify/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).
+[packages/core-api/src/types.ts:33](https://github.com/backstage/backstage/blob/ca535f2f66c3a4980c80f4b1a049dfd07569010e/packages/core-api/src/types.ts#L33).

 Referenced by: [Observable](#observable).
@@ -15,48 +15,48 @@ In the project root, there are a set of files and folders which are not part of
 the project as such, and may or may not be familiar to someone looking through
 the code.

- [`.changeset/`](https://github.com/spotify/backstage/tree/master/.changeset) -
+- [`.changeset/`](https://github.com/backstage/backstage/tree/master/.changeset) -
  This folder contains files outlining which changes occurred in the project
  since the last release. These files are added manually, but managed by
  [changesets](https://github.com/atlassian/changesets) and will be removed at
  every new release. They are essentially building-blocks of a CHANGELOG.

- [`.github/`](https://github.com/spotify/backstage/tree/master/.github) -
+- [`.github/`](https://github.com/backstage/backstage/tree/master/.github) -
  Standard GitHub folder. It contains - amongst other things - our workflow
  definitions and templates. Worth noting is the
-  [styles](https://github.com/spotify/backstage/tree/master/.github/styles)
+  [styles](https://github.com/backstage/backstage/tree/master/.github/styles)
  folder which is used for a markdown spellchecker.

- [`.yarn/`](https://github.com/spotify/backstage/tree/master/.yarn) - Backstage
-  ships with it's own `yarn` implementation. This allows us to have better
-  control over our `yarn.lock` file and hopefully avoid problems due to yarn
-  versioning differences.
+- [`.yarn/`](https://github.com/backstage/backstage/tree/master/.yarn) -
+  Backstage ships with it's own `yarn` implementation. This allows us to have
+  better control over our `yarn.lock` file and hopefully avoid problems due to
+  yarn versioning differences.

- [`docker/`](https://github.com/spotify/backstage/tree/master/docker) - Files
+- [`docker/`](https://github.com/backstage/backstage/tree/master/docker) - Files
  related to our root Dockerfile. We are planning to refactor this, so expect
  this folder to be moved in the future.

- [`contrib/`](https://github.com/spotify/backstage/tree/master/contrib) -
+- [`contrib/`](https://github.com/backstage/backstage/tree/master/contrib) -
  Collection of examples or resources provided by the community. We really
  appreciate contributions in here and encourage them being kept up to date.

- [`docs/`](https://github.com/spotify/backstage/tree/master/docs) - This is
+- [`docs/`](https://github.com/backstage/backstage/tree/master/docs) - This is
  where we keep all of our documentation Markdown files. These ends up on
  http://backstage.io/docs. Just keep in mind that changes to the
-  [`sidebars.json`](https://github.com/spotify/backstage/blob/master/microsite/sidebars.json)
+  [`sidebars.json`](https://github.com/backstage/backstage/blob/master/microsite/sidebars.json)
  file may be needed as sections are added/removed.

- [`.editorconfig`](https://github.com/spotify/backstage/tree/master/.editorconfig) -
+- [`.editorconfig`](https://github.com/backstage/backstage/tree/master/.editorconfig) -
  A configuration file used by most common code editors.

- [`.imgbotconfig`](https://github.com/spotify/backstage/tree/master/.imgbotconfig) -
+- [`.imgbotconfig`](https://github.com/backstage/backstage/tree/master/.imgbotconfig) -
  Configuration for a [bot](https://imgbot.net/)

 ## Monorepo packages

 Every folder in both `packages/` and `plugins/` is within our monorepo setup, as
 defined in
-[`package.json`](https://github.com/spotify/backstage/blob/master/package.json):
+[`package.json`](https://github.com/backstage/backstage/blob/master/package.json):

 ```json
 "workspaces": {
@@ -74,30 +74,30 @@ Let's look at them individually.
 These are all the packages that we use within the project. [Plugins](#plugins)
 are separated out into their own folder, see further down.

- [`app/`](https://github.com/spotify/backstage/tree/master/packages/app) - This
-  is our take on how an App could look like, bringing together a set of packages
-  and plugins into a working Backstage App. This is not a published package, and
-  the main goals are to provide a demo of what an App could look like and to
-  enable local development.
+- [`app/`](https://github.com/backstage/backstage/tree/master/packages/app) -
+  This is our take on how an App could look like, bringing together a set of
+  packages and plugins into a working Backstage App. This is not a published
+  package, and the main goals are to provide a demo of what an App could look
+  like and to enable local development.

- [`backend/`](https://github.com/spotify/backstage/tree/master/packages/backend) -
+- [`backend/`](https://github.com/backstage/backstage/tree/master/packages/backend) -
  Every standalone Backstage project will have both an `app` _and_ a `backend`
  package. The `backend` uses plugins to construct a working backend that the
  frontend (`app`) can use.

- [`backend-common/`](https://github.com/spotify/backstage/tree/master/packages/backend-common) -
+- [`backend-common/`](https://github.com/backstage/backstage/tree/master/packages/backend-common) -
  There are no "core" packages in the backend. Instead we have `backend-common`
  which contains helper middleware and other utils.

- [`catalog-model/`](https://github.com/spotify/backstage/tree/master/packages/catalog-model) -
+- [`catalog-model/`](https://github.com/backstage/backstage/tree/master/packages/catalog-model) -
  You can consider this to be a library for working with the catalog of sorts.
  It contains the definition of an
  [Entity](https://backstage.io/docs/features/software-catalog/references#docsNav),
  as well as validation and other logic related to it. This package can be used
  in both the frontend and the backend.

- [`cli/`](https://github.com/spotify/backstage/tree/master/packages/cli) - One
-  of the biggest packages in our project, the `cli` is used to build, serve,
+- [`cli/`](https://github.com/backstage/backstage/tree/master/packages/cli) -
+  One of the biggest packages in our project, the `cli` is used to build, serve,
  diff, create-plugins and more. In the early days of this project, we started
  out with calling tools directly - such as `eslint` - through `package.json`.
  But as it was tricky to have a good development experience around that when we
@@ -105,86 +105,87 @@ are separated out into their own folder, see further down.
  everything looks the same in `package.json`. Much like
  [react-scripts](https://github.com/facebook/create-react-app/tree/master/packages/react-scripts).

- [`cli-common/`](https://github.com/spotify/backstage/tree/master/packages/cli-common) -
+- [`cli-common/`](https://github.com/backstage/backstage/tree/master/packages/cli-common) -
  This package mainly handles path resolving. It is a separate package to reduce
-  bugs in [cli](https://github.com/spotify/backstage/tree/master/packages/cli).
-  We also want as few dependencies as possible to reduce download time when
-  running the cli which is another reason this is a separate package.
+  bugs in
+  [cli](https://github.com/backstage/backstage/tree/master/packages/cli). We
+  also want as few dependencies as possible to reduce download time when running
+  the cli which is another reason this is a separate package.

- [`config/`](https://github.com/spotify/backstage/tree/master/packages/config) -
+- [`config/`](https://github.com/backstage/backstage/tree/master/packages/config) -
  The way we read configuration data. This package can take a bunch of config
  objects and merge them together.
-  [app-config.yaml](https://github.com/spotify/backstage/blob/master/app-config.yaml)
+  [app-config.yaml](https://github.com/backstage/backstage/blob/master/app-config.yaml)
  is an example of an config object.

- [`config-loader/`](https://github.com/spotify/backstage/tree/master/packages/config-loader) -
+- [`config-loader/`](https://github.com/backstage/backstage/tree/master/packages/config-loader) -
  This package is used to read config objects. It does not know how to merge,
  but only reads files and passes them on to the config. As this part is only
  used by the backend, we chose to separate `config` and `config-loader` into
  two different packages.

- [`core/`](https://github.com/spotify/backstage/tree/master/packages/core) -
+- [`core/`](https://github.com/backstage/backstage/tree/master/packages/core) -
  This package contains our visual React components, some of which you can find
  in
  [plugin examples](https://backstage.io/storybook/?path=/story/plugins-examples--plugin-with-data).
  Apart from that it re-exports everything from [`core-api`] so that users only
  need to rely on one package.

- [`core-api/`](https://github.com/spotify/backstage/tree/master/packages/core-api) -
+- [`core-api/`](https://github.com/backstage/backstage/tree/master/packages/core-api) -
  This package contains APIs and definitions of such. It is it's own package
  because we needed to split our `test-utils` package. It's an implementation
  detail that we try to hide from our users, and no one should have to depend on
  it directly.

- [`test-utils/`](https://github.com/spotify/backstage/tree/master/packages/test-utils) -
+- [`test-utils/`](https://github.com/backstage/backstage/tree/master/packages/test-utils) -
  This package contains specific testing facilities used when testing
  `core-api`.

- [`test-utils-core/`](https://github.com/spotify/backstage/tree/master/packages/test-utils-core) -
+- [`test-utils-core/`](https://github.com/backstage/backstage/tree/master/packages/test-utils-core) -
  This package contains more general purpose testing facilities for testing a
  Backstage App.

- [`create-app/`](https://github.com/spotify/backstage/tree/master/packages/create-app) -
+- [`create-app/`](https://github.com/backstage/backstage/tree/master/packages/create-app) -
  An CLI to specifically scaffold a new Backstage App. It does so by using a
-  [template](https://github.com/spotify/backstage/tree/master/packages/create-app/templates/default-app).
+  [template](https://github.com/backstage/backstage/tree/master/packages/create-app/templates/default-app).

- [`dev-utils/`](https://github.com/spotify/backstage/tree/master/packages/dev-utils) -
+- [`dev-utils/`](https://github.com/backstage/backstage/tree/master/packages/dev-utils) -
  Helps you setup a plugin for isolated development so that it can be served
  separately.

- [`docgen/`](https://github.com/spotify/backstage/tree/master/packages/docgen) -
+- [`docgen/`](https://github.com/backstage/backstage/tree/master/packages/docgen) -
  Uses the
  [Typescript Compiler API](https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API)
  to read out definitions and generate documentation for it.

- [`e2e-test/`](https://github.com/spotify/backstage/tree/master/packages/e2e-test) -
+- [`e2e-test/`](https://github.com/backstage/backstage/tree/master/packages/e2e-test) -
  Another CLI that can be run to try out what would happen if you built all the
  packages, publish them, created a new app, and the run it. CI uses this for
  e2e-tests.

- [`storybook/`](https://github.com/spotify/backstage/tree/master/packages/storybook) -
+- [`storybook/`](https://github.com/backstage/backstage/tree/master/packages/storybook) -
  This folder contains only the storybook config. Stories are within the core
  package. The Backstage Storybook is found
  [here](https://backstage.io/storybook)

- [`techdocs-cli/`](https://github.com/spotify/backstage/tree/master/packages/techdocs-cli) -
+- [`techdocs-cli/`](https://github.com/backstage/backstage/tree/master/packages/techdocs-cli) -
  Used for verifying TechDocs locally.

- [`techdocs-container/`](https://github.com/spotify/backstage/tree/master/packages/techdocs-container) -
+- [`techdocs-container/`](https://github.com/backstage/backstage/tree/master/packages/techdocs-container) -
  Used by the `techdocs-cli`

- [`test-utils-core/`](https://github.com/spotify/backstage/tree/master/packages/test-utils-core)
+- [`test-utils-core/`](https://github.com/backstage/backstage/tree/master/packages/test-utils-core)

- [`test-utils/`](https://github.com/spotify/backstage/tree/master/packages/test-utils)
+- [`test-utils/`](https://github.com/backstage/backstage/tree/master/packages/test-utils)

- [`theme/`](https://github.com/spotify/backstage/tree/master/packages/theme) -
+- [`theme/`](https://github.com/backstage/backstage/tree/master/packages/theme) -
  Holds the Backstage Theme.

 ### `plugins/`

 Most of the functionality of a Backstage App comes from plugins. Even core
 features can be plugins, take the
-[catalog](https://github.com/spotify/backstage/tree/master/plugins/catalog) as
+[catalog](https://github.com/backstage/backstage/tree/master/plugins/catalog) as
 an example.

 We can categorize plugins into three different types; **Frontend**, **Backend**
@@ -196,18 +197,18 @@ reason is for clear separation of concerns.

 Take a look at our [Plugin Gallery](https://backstage.io/plugins) or browse
 through the
-[`plugins/`](https://github.com/spotify/backstage/tree/master/plugins) folder.
+[`plugins/`](https://github.com/backstage/backstage/tree/master/plugins) folder.

 ## Packages outside of the monorepo

 For convenience we include packages in our project that are not part of our
 monorepo setup.

- [`microsite/`](https://github.com/spotify/backstage/blob/master/microsite) -
+- [`microsite/`](https://github.com/backstage/backstage/blob/master/microsite) -
  This folder contains the source code for backstage.io. It is built with
  [Docusaurus](https://docusaurus.io/). This folder is not part of the monorepo
  due to dependency reasons. Look at the
-  [README](https://github.com/spotify/backstage/blob/master/microsite/README.md)
+  [README](https://github.com/backstage/backstage/blob/master/microsite/README.md)
  for instructions on how to run it locally.

 ## Root files specifically used by the `app`
@@ -216,22 +217,22 @@ These files are kept in the root of the project mostly by historical reasons.
 Some of these files may be subject to be moved out of the root sometime in the
 future.

- [`.npmrc`](https://github.com/spotify/backstage/tree/master/.npmrc) - It's
+- [`.npmrc`](https://github.com/backstage/backstage/tree/master/.npmrc) - It's
  common for companies to have their own npm registry, this files makes sure
  that this folder use the public registry.

- [`.vale.ini`](https://github.com/spotify/backstage/tree/master/.vale.ini) -
+- [`.vale.ini`](https://github.com/backstage/backstage/tree/master/.vale.ini) -
  [Spell checker](https://github.com/errata-ai/vale) for Markdown files.

- [`.yarnrc`](https://github.com/spotify/backstage/tree/master/.yarnrc) -
+- [`.yarnrc`](https://github.com/backstage/backstage/tree/master/.yarnrc) -
  Enforces "our" version of Yarn.

- [`app-config.yaml`](https://github.com/spotify/backstage/tree/master/app-config.yaml) -
+- [`app-config.yaml`](https://github.com/backstage/backstage/tree/master/app-config.yaml) -
  Configuration for the app, both frontend and backend.

- [`catalog-info.yaml`](https://github.com/spotify/backstage/tree/master/catalog-info.yaml) -
+- [`catalog-info.yaml`](https://github.com/backstage/backstage/tree/master/catalog-info.yaml) -
  Description of Backstage in the Backstage Entity format.

- [`lerna.json`](https://github.com/spotify/backstage/tree/master/lerna.json) -
+- [`lerna.json`](https://github.com/backstage/backstage/tree/master/lerna.json) -
  [Lerna](https://github.com/lerna/lerna) monorepo config. We are using
  `yarn workspaces`, so this will only be used for executing scripts.
@@ -6,9 +6,9 @@ description: Support and Community Details and Links

 - [Discord chatroom](https://discord.gg/MUpMjP2) - Get support or discuss the
  project
- [Good First Issues](https://github.com/spotify/backstage/contribute) - Start
+- [Good First Issues](https://github.com/backstage/backstage/contribute) - Start
  here if you want to contribute
- [RFCs](https://github.com/spotify/backstage/labels/rfc) - Help shape the
+- [RFCs](https://github.com/backstage/backstage/labels/rfc) - Help shape the
  technical direction
 - [FAQ](../FAQ.md) - Frequently Asked Questions
 - [Code of Conduct](../../CODE_OF_CONDUCT.md) - This is how we roll
@@ -120,10 +120,10 @@ If everything is saved, you should see your name, id, and email on the
 github-playground page. Our data accessed is synchronous. So we just grab and
 go.

-https://github.com/spotify/backstage/tree/master/contrib
+https://github.com/backstage/backstage/tree/master/contrib

 6. Here is the entire file for reference
-   [ExampleComponent.tsx](https://github.com/spotify/backstage/tree/master/contrib/docs/tutorials/quickstart-app-plugin/ExampleComponent.md)
+   [ExampleComponent.tsx](https://github.com/backstage/backstage/tree/master/contrib/docs/tutorials/quickstart-app-plugin/ExampleComponent.md)

 # The Wipe

@@ -302,7 +302,7 @@ return (
 8. After saving that, and given we don't have any errors, you should see a table
   with basic information on your repositories.
 9. Here is the entire file for reference
-   [ExampleFetchComponent.tsx](https://github.com/spotify/backstage/tree/master/contrib/docs/tutorials/quickstart-app-plugin/ExampleFetchComponent.md)
+   [ExampleFetchComponent.tsx](https://github.com/backstage/backstage/tree/master/contrib/docs/tutorials/quickstart-app-plugin/ExampleFetchComponent.md)
 10. We finished! You should see your own GitHub repository's information
    displayed in a basic table. If you run into issues, you can compare the repo
    that backs this document,
@@ -81,8 +81,8 @@ Similar to how Backstage ties together all of Spotify’s infrastructure, our am

 ## What’s next?

-We are envisioning [three phases](https://github.com/spotify/backstage/milestones) of the project (so far), and we have already begun work on various aspects of these phases. The best way to track the work and see where you can jump in and help out is:
+We are envisioning [three phases](https://github.com/backstage/backstage/milestones) of the project (so far), and we have already begun work on various aspects of these phases. The best way to track the work and see where you can jump in and help out is:

-https://github.com/spotify/backstage/milestones
+https://github.com/backstage/backstage/milestones

 Want to discuss the project or need support? Join us on [Discord](https://discord.gg/MUpMjP2) or reach out on [alund@spotify.com](mailto:alund@spotify.com).
@@ -33,7 +33,7 @@ Trigger an audit directly from Backstage, or trigger audits programmatically wit

 ## Using Lighthouse in Backstage

-To learn how you can enable Lighthouse auditing within Backstage, head over to the [README](https://github.com/spotify/backstage/tree/master/plugins/lighthouse) for the plugin to get started.
+To learn how you can enable Lighthouse auditing within Backstage, head over to the [README](https://github.com/backstage/backstage/tree/master/plugins/lighthouse) for the plugin to get started.

 ## A personal note

@@ -132,4 +132,4 @@ If you are developing a plugin that might be useful for others, consider releasi

 ## Ready to get started?

-Head over to GitHub and check out the [project](https://github.com/spotify/backstage) or download our [CLI](https://www.npmjs.com/package/@backstage/cli). If you have more questions, join us on [Discord](https://discord.gg/MUpMjP2) or [create an issue](https://github.com/spotify/backstage/issues/new/choose).
+Head over to GitHub and check out the [project](https://github.com/backstage/backstage) or download our [CLI](https://www.npmjs.com/package/@backstage/cli). If you have more questions, join us on [Discord](https://discord.gg/MUpMjP2) or [create an issue](https://github.com/backstage/backstage/issues/new/choose).
@@ -34,11 +34,11 @@ To learn about how you can bring the Tech Radar to your Backstage installation,

 I want to thank both the Backstage team and Spotify. Firstly, I’ve been working with our internal version of Backstage for over a year, and the developer experience since open sourcing has been even more of a joy to work with. Secondly, the 10% hack time that Spotify generously provides to all engineers enabled me to open source the Tech Radar plugin.

-Since open sourcing it, the community has shown great interest in yet another powerful use case of Backstage. There was also an enthusiastic open source contributor who volunteered to migrate the plugin to TypeScript and React Hooks [in just 29 minutes](https://github.com/spotify/backstage/issues/661) of opening the issue!
+Since open sourcing it, the community has shown great interest in yet another powerful use case of Backstage. There was also an enthusiastic open source contributor who volunteered to migrate the plugin to TypeScript and React Hooks [in just 29 minutes](https://github.com/backstage/backstage/issues/661) of opening the issue!

 I can’t wait to see how others benefit from the Tech Radar in their organizations!

 [lighthouse website audits]: https://backstage.io/blog/2020/04/06/lighthouse-plugin
-[tech radar plugin]: https://github.com/spotify/backstage/tree/master/plugins/tech-radar
+[tech radar plugin]: https://github.com/backstage/backstage/tree/master/plugins/tech-radar
 [thoughtworks]: https://www.thoughtworks.com/radar
 [zalando]: https://opensource.zalando.com/tech-radar/
@@ -7,7 +7,7 @@ authorImageURL: https://pbs.twimg.com/profile_images/121166861/6919c047c0d0edaac

 **TL;DR** Thanks to the help from the Backstage community, we’ve made excellent progress and are now moving into Phase 2 of Backstage — building out a Service Catalog and the surrounding systems that will help unify the tools you use to manage your software.

-We released the open source version of Backstage a little less than two months ago, and have been thrilled to see so many people jumping in and contributing to the project in its early stages. We’re excited to see what the community can build together as we progress through [each phase of Backstage](https://github.com/spotify/backstage#project-roadmap).
+We released the open source version of Backstage a little less than two months ago, and have been thrilled to see so many people jumping in and contributing to the project in its early stages. We’re excited to see what the community can build together as we progress through [each phase of Backstage](https://github.com/backstage/backstage#project-roadmap).

 ![img](assets/20-05-20/Service_Catalog_MVP.png)

@@ -15,7 +15,7 @@ We released the open source version of Backstage a little less than two months a

 ## Progress so far

-Phase 1 was all about building an extensible frontend platform, enabling teams to start creating a single, consistent UI layer for your internal infrastructure and tools in the form of [plugins](https://github.com/spotify/backstage/labels/plugin). In fact, thanks to our amazing (30+) [contributors](https://github.com/spotify/backstage/graphs/contributors), we were able to complete most of Phase 1 earlier than expected. 🎉
+Phase 1 was all about building an extensible frontend platform, enabling teams to start creating a single, consistent UI layer for your internal infrastructure and tools in the form of [plugins](https://github.com/backstage/backstage/labels/plugin). In fact, thanks to our amazing (30+) [contributors](https://github.com/backstage/backstage/graphs/contributors), we were able to complete most of Phase 1 earlier than expected. 🎉

 Today, we are happy to announce that we are shifting our focus to Phase 2!

@@ -27,7 +27,7 @@ Quote from [Platform Nuts & Bolts: Extendable Data Models](https://www.kislayver

 Entities, or what we refer to as “components” in Backstage, represent all software, including services, websites, libraries, data pipelines, and so forth. The focus of Phase 2 will be on adding an entity model in Backstage that makes it easy for engineers to create and manage the software components they own.

-With the ability to create a plethora of components in Backstage, how does one keep track of all the software in the ecosystem? Therein lies the highlight feature of Phase 2: the [Service Catalog](https://github.com/spotify/backstage/milestone/4). The service catalog — or software catalog — is a centralized system that keeps track of ownership and metadata about all software in your ecosystem. The catalog is built around the concept of [metadata yaml files](/docs/architecture-decisions/adrs-adr002) stored together with the code, which are then harvested and visualized in Backstage.
+With the ability to create a plethora of components in Backstage, how does one keep track of all the software in the ecosystem? Therein lies the highlight feature of Phase 2: the [Service Catalog](https://github.com/backstage/backstage/milestone/4). The service catalog — or software catalog — is a centralized system that keeps track of ownership and metadata about all software in your ecosystem. The catalog is built around the concept of [metadata yaml files](/docs/architecture-decisions/adrs-adr002) stored together with the code, which are then harvested and visualized in Backstage.

 ![img](assets/20-05-20/Service_Catalog_MVP.png)

@@ -39,13 +39,13 @@ On top of that, we have found that the service catalog is a great way to organis

 ![img](assets/20-05-20/tabs.png)

-More concretely, having this structure in place will allow plugins such as [CircleCI](https://github.com/spotify/backstage/tree/master/plugins/circleci) to show only the builds for the specific service you are viewing, or a [Spinnaker](https://github.com/spotify/backstage/issues/631) plugin to show running deployments, or an Open API plugin to [show documentation](https://github.com/spotify/backstage/issues/627) for endpoints exposed by the service, or the [Lighthouse](https://github.com/spotify/backstage/tree/master/plugins/lighthouse) plugin to show audit reports for your website. You get the point.
+More concretely, having this structure in place will allow plugins such as [CircleCI](https://github.com/backstage/backstage/tree/master/plugins/circleci) to show only the builds for the specific service you are viewing, or a [Spinnaker](https://github.com/backstage/backstage/issues/631) plugin to show running deployments, or an Open API plugin to [show documentation](https://github.com/backstage/backstage/issues/627) for endpoints exposed by the service, or the [Lighthouse](https://github.com/backstage/backstage/tree/master/plugins/lighthouse) plugin to show audit reports for your website. You get the point.

 ## Timeline

 Our estimated timeline has us delivering these pieces in increments leading up to June 22. But with the support of the community we wouldn’t be surprised if things land earlier than that. 🙏

-If you are interested in joining us, check out our [Milestones](https://github.com/spotify/backstage/milestones) and connected Issues.
+If you are interested in joining us, check out our [Milestones](https://github.com/backstage/backstage/milestones) and connected Issues.

 ## Long-term vision

@@ -40,7 +40,7 @@ You’ll be able to see many of these virtues in action with this alpha release

 Alpha is our shorthand for "we don’t yet think Backstage is ready for production, but we’d love for you to test it and provide us with feedback". However, you should be able to try out the functionality of the service catalog:

-1. Register software components ([examples](https://github.com/spotify/backstage/tree/master/packages/catalog-model/examples))
+1. Register software components ([examples](https://github.com/backstage/backstage/tree/master/packages/catalog-model/examples))
 2. See all components represented in the catalog
 3. Search across all components
 4. Get an overview of the metadata of the components
@@ -49,6 +49,6 @@ Alpha is our shorthand for "we don’t yet think Backstage is ready for producti

 As with most alpha releases, you should expect things to change quite a lot until we reach the beta stage (we’re targeting the end of summer). There are obviously many things missing as well, but we wanted to start collecting feedback early and make it easier to see the end-to-end flow.

-If you have feedback or questions, please open a [GitHub issue](https://github.com/spotify/backstage/issues), ping us on [Discord chat](https://discord.gg/EBHEGzX) or send me an email at [alund@spotify.com](mailto:alund@spotify.com) 🙏
+If you have feedback or questions, please open a [GitHub issue](https://github.com/backstage/backstage/issues), ping us on [Discord chat](https://discord.gg/EBHEGzX) or send me an email at [alund@spotify.com](mailto:alund@spotify.com) 🙏

 To get regular product updates and news about the Backstage community, sign up for the [Backstage newsletter](https://mailchi.mp/spotify/backstage-community).
@@ -21,7 +21,7 @@ Passport has allowed us to leverage an existing open-source authentication frame

 ![auth-landing-page](assets/20-07-01/auth-sidebar.png)

-First, check out the provided Google and GitHub implementations! [Spin up a local copy of Backstage](https://backstage.io/blog/2020/04/30/how-to-quickly-set-up-backstage) along with our example-backend. You can find more documentation on setting up the example backend [here](https://github.com/spotify/backstage/tree/master/packages/backend), but be sure to include the relevant client IDs and secrets when running `yarn start`:
+First, check out the provided Google and GitHub implementations! [Spin up a local copy of Backstage](https://backstage.io/blog/2020/04/30/how-to-quickly-set-up-backstage) along with our example-backend. You can find more documentation on setting up the example backend [here](https://github.com/backstage/backstage/tree/master/packages/backend), but be sure to include the relevant client IDs and secrets when running `yarn start`:

 ```
 AUTH_GOOGLE_CLIENT_ID=x AUTH_GOOGLE_CLIENT_SECRET=x AUTH_GITHUB_CLIENT_ID=x AUTH_GITHUB_CLIENT_SECRET=x SENTRY_TOKEN=x LOG_LEVEL=debug yarn start
@@ -43,4 +43,4 @@ For full details, take a look at our [“Adding authentication providers” docu

 ## Interested in contributing to the next steps for authentication?

-We’ve already seen both GitLab and Okta contributions from the community — and we’re thinking about a few more providers we’d like to add to Backstage, too. You can find those, and other authentication-related issues, in our repository by filtering with the [auth label](https://github.com/spotify/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aauth).
+We’ve already seen both GitLab and Okta contributions from the community — and we’re thinking about a few more providers we’d like to add to Backstage, too. You can find those, and other authentication-related issues, in our repository by filtering with the [auth label](https://github.com/backstage/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aauth).
@@ -73,6 +73,6 @@ Backstage ships with four example templates, but since these are likely not the

 We have learned that one of the keys to getting these standards adopted is to keep an open process. Templates are code. By making it clear to your engineers that you are open to pull requests, and that teams with different needs can add their own templates, you are on the path of striking a good balance between autonomy and standardization.

-If you have feedback or questions, please open a [GitHub issue](https://github.com/spotify/backstage/issues), ping us on [Discord chat](https://discord.gg/EBHEGzX) or send me an email at [alund@spotify.com](mailto:alund@spotify.com) 🙏
+If you have feedback or questions, please open a [GitHub issue](https://github.com/backstage/backstage/issues), ping us on [Discord chat](https://discord.gg/EBHEGzX) or send me an email at [alund@spotify.com](mailto:alund@spotify.com) 🙏

 To get regular product updates and news about the Backstage community, sign up for the [Backstage newsletter](https://mailchi.mp/spotify/backstage-community).
@@ -21,11 +21,11 @@ But this is just one way to do it. Today we’re most excited for what the open

 ## Okay, let’s start collaborating

-If you go to [GitHub](https://github.com/spotify/backstage/tree/master/plugins) now, you’ll find everything you need to start collaborating with us to build out the docs-like-code Backstage plugin — we’ll call it TechDocs in the open as well.
+If you go to [GitHub](https://github.com/backstage/backstage/tree/master/plugins) now, you’ll find everything you need to start collaborating with us to build out the docs-like-code Backstage plugin — we’ll call it TechDocs in the open as well.

-You’ll find the code in [techdocs](https://github.com/spotify/backstage/tree/master/plugins/techdocs) (frontend) and [techdocs-backend](https://github.com/spotify/backstage/tree/master/plugins/techdocs-backend). (There are also two separate packages [techdocs-cli](https://github.com/spotify/backstage/tree/master/packages/techdocs-cli) and [techdocs-container](https://github.com/spotify/backstage/tree/master/packages/techdocs-container).)
+You’ll find the code in [techdocs](https://github.com/backstage/backstage/tree/master/plugins/techdocs) (frontend) and [techdocs-backend](https://github.com/backstage/backstage/tree/master/plugins/techdocs-backend). (There are also two separate packages [techdocs-cli](https://github.com/backstage/backstage/tree/master/packages/techdocs-cli) and [techdocs-container](https://github.com/backstage/backstage/tree/master/packages/techdocs-container).)

-You’ll find issues to work on in the [issues queue](https://github.com/spotify/backstage/issues?q=is%3Aissue+is%3Aopen+label%3A%22docs-like-code%22+label%3A%22help+wanted%22), typically starting with TechDocs: and labeled with docs-like-code, some labeled good first issue. Feel free to add your own issues, of course.
+You’ll find issues to work on in the [issues queue](https://github.com/backstage/backstage/issues?q=is%3Aissue+is%3Aopen+label%3A%22docs-like-code%22+label%3A%22help+wanted%22), typically starting with TechDocs: and labeled with docs-like-code, some labeled good first issue. Feel free to add your own issues, of course.

 ![available-templates](assets/announcing-techdocs/github-issues.png)

@@ -14,7 +14,7 @@ Backstage garnered quite a bit of interest from developers and organizations whe

 Backstage’s ability to simplify tooling and standardize engineering practices has attracted interest from other major tech companies, as well as airlines, auto manufacturers, investment firms, and global retailers. We know that Backstage solves a problem — infrastructure complexity — that’s common to a lot of large and growing companies today. But different companies work differently, use particular toolsets, and have unique use cases. By making Backstage open source, we can build it with people working inside a variety of engineering organizations all over the world. It makes for a better product that serves a wider group of users (beyond that of Spotify’s) and their needs.

-The Backstage community is healthy and growing quickly. Over [130 people](https://github.com/spotify/backstage/graphs/contributors) have contributed to the project, and roughly 40% of pull requests are now coming from external, non-Spotify, contributors. With companies now deciding to [adopt Backstage](https://github.com/spotify/backstage/blob/master/ADOPTERS.md) we are also seeing a shift in the kinds of contributions we are getting from the community. It is truly amazing to see contributions to core parts of the platform as well as significant functionality additions through working [plugins](https://backstage.io/plugins).
+The Backstage community is healthy and growing quickly. Over [130 people](https://github.com/backstage/backstage/graphs/contributors) have contributed to the project, and roughly 40% of pull requests are now coming from external, non-Spotify, contributors. With companies now deciding to [adopt Backstage](https://github.com/backstage/backstage/blob/master/ADOPTERS.md) we are also seeing a shift in the kinds of contributions we are getting from the community. It is truly amazing to see contributions to core parts of the platform as well as significant functionality additions through working [plugins](https://backstage.io/plugins).

 We’re excited to embark on this journey with the CNCF community. There’s so much great tech being built here, and it’s about time we share it to build even greater products, together. Entering into the CNCF Sandbox is just the first step. We are committed to working with the community to bring Backstage through the Incubation step, and finally all the way to becoming a Graduated, top-level project.

@@ -68,9 +68,9 @@ To keep up with our latest design guidelines, go to [Designing for Backstage](ht

 ![img](assets/backstage-github-ds.png)

-### [GitHub](https://github.com/spotify/backstage)
+### [GitHub](https://github.com/backstage/backstage)

-Join in on the action [at spotify/backstage on GitHub](https://github.com/spotify/backstage) by submitting issues and opening pull requests for all things related to components and patterns in Backstage.
+Join in on the action [at spotify/backstage on GitHub](https://github.com/backstage/backstage) by submitting issues and opening pull requests for all things related to components and patterns in Backstage.

 ![img](assets/backstage-discord-DS.png)

@@ -34,10 +34,10 @@ This grand vision is actually not that far off. Already today there is a growing

 Not all plugins you need will be open source. Every company has their own homegrown tooling. Building internal plugins lets you tailor your version of Backstage to be a perfect fit for your infrastructure and software development needs. If you end up [building plugins](https://backstage.io/docs/plugins/create-a-plugin) that could be useful for other companies, please consider releasing them as open source and [add them to the Marketplace](https://backstage.io/docs/plugins/add-to-marketplace).

-If you start developing a plugin that you aim to release as open source, we suggest that you create a [new plugin Issue](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME). This helps the community know what plugins are in development and opens up opportunities for collaboration. You can also use this process if you have an idea for a good plugin, but you need help building it.
+If you start developing a plugin that you aim to release as open source, we suggest that you create a [new plugin Issue](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME). This helps the community know what plugins are in development and opens up opportunities for collaboration. You can also use this process if you have an idea for a good plugin, but you need help building it.

 We are really excited to see all the amazing plugins that have already been built, and look forward to seeing even more ideas and collaboration as the Backstage community continues to grow.

-What plugins would you like to see in the Plugin Marketplace? [Tell us](https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME)!
+What plugins would you like to see in the Plugin Marketplace? [Tell us](https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME)!

 _Special shout-out to community member [Iain Billett](https://github.com/iain-b) from [Roadie](https://roadie.io) for helping build and contribute the [Plugin Marketplace page](https://backstage.io/plugins) (as his first PR no less!)._
@@ -4,7 +4,7 @@ author: Janisa Anandamohan
 authorURL: https://twitter.com/janisa_a
 ---

-How did Spotify save millions on cloud costs within a matter of months?? We made cost optimization just another part of the daily development process. Our newly open sourced [Cost Insights plugin](https://github.com/spotify/backstage/tree/master/plugins/cost-insights) makes a team’s cloud costs visible — and actionable — right inside Backstage. So engineers can see the impact of their cloud usage (down to a product and resource level) and make optimizations wherever and whenever it makes sense. By managing cloud costs from the ground up, you can make smarter decisions that let you continue to build and scale quickly, without wasting resources.
+How did Spotify save millions on cloud costs within a matter of months?? We made cost optimization just another part of the daily development process. Our newly open sourced [Cost Insights plugin](https://github.com/backstage/backstage/tree/master/plugins/cost-insights) makes a team’s cloud costs visible — and actionable — right inside Backstage. So engineers can see the impact of their cloud usage (down to a product and resource level) and make optimizations wherever and whenever it makes sense. By managing cloud costs from the ground up, you can make smarter decisions that let you continue to build and scale quickly, without wasting resources.

 <iframe width="780" height="440" src="https://www.youtube.com/embed/YLAd5hdXR_Q" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>

@@ -59,7 +59,7 @@ Engineers can then determine for themselves if the time invested in an optimizat

 ## Getting started

-You can begin working with the Cost Insights plugin today on [GitHub](https://github.com/spotify/backstage/tree/master/plugins/cost-insights). We include an example client with static data in the expected format. The `CostInsightsApi` should talk with a cloud billing backend that aggregates billing data from your cloud provider.
+You can begin working with the Cost Insights plugin today on [GitHub](https://github.com/backstage/backstage/tree/master/plugins/cost-insights). We include an example client with static data in the expected format. The `CostInsightsApi` should talk with a cloud billing backend that aggregates billing data from your cloud provider.

 The current release of Cost Insights includes:

@@ -72,8 +72,8 @@ The current release of Cost Insights includes:

 Our hope is to help other companies translate their cloud cost in a relatable way for their engineers to better understand their impact and accurately identify their opportunities for optimizations.

-And if you’re interested in contributing to our outstanding issues, you can find them in the issues queue, filtered under the [‘cost-insights’ label](https://github.com/spotify/backstage/labels/cost-insights).
+And if you’re interested in contributing to our outstanding issues, you can find them in the issues queue, filtered under the [‘cost-insights’ label](https://github.com/backstage/backstage/labels/cost-insights).

 ## Ready for DevSecCostOpsPlus (and whatever’s next)

-There’s DevOps, there’s DevSecOps, and then there’s Backstage: one frontend for all your infrastructure. From building, testing, and deploying to monitoring and security — Backstage helps you manage your entire tech organization and provides a seamless developer experience for engineers, from end to end to end. And now that also extends to cost management for your cloud infrastructure and tooling. Happy building and [happy optimizing](https://github.com/spotify/backstage/tree/master/plugins/cost-insights).
+There’s DevOps, there’s DevSecOps, and then there’s Backstage: one frontend for all your infrastructure. From building, testing, and deploying to monitoring and security — Backstage helps you manage your entire tech organization and provides a seamless developer experience for engineers, from end to end to end. And now that also extends to cost management for your cloud infrastructure and tooling. Happy building and [happy optimizing](https://github.com/backstage/backstage/tree/master/plugins/cost-insights).
@@ -41,7 +41,7 @@ class Footer extends React.Component {
          <div>
            <h5>Community</h5>
            <a href="https://discord.gg/MUpMjP2">Support chatroom</a>
-            <a href="https://github.com/spotify/backstage/blob/master/CONTRIBUTING.md">
+            <a href="https://github.com/backstage/backstage/blob/master/CONTRIBUTING.md">
              Contributing
            </a>
            <a href="https://mailchi.mp/spotify/backstage-community">
@@ -4,6 +4,6 @@ author: SDA SE
 authorUrl: https://sda.se/
 category: Discovery
 description: Components to discover and display API entities as an extension to the catalog plugin.
-documentation: https://github.com/spotify/backstage/blob/master/plugins/api-docs/README.md
+documentation: https://github.com/backstage/backstage/blob/master/plugins/api-docs/README.md
 iconUrl: https://thecoders.io/wp-content/uploads/2019/11/tech-swagger.svg
 npmPackageName: '@backstage/plugin-api-docs'
@@ -4,7 +4,7 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: CI
 description: Automate your development process with CI hosted in the cloud or on a private server.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/circleci
+documentation: https://github.com/backstage/backstage/tree/master/plugins/circleci
 iconUrl: https://www.saaves.com/storage/brochure/logo-circleci-icon1583764538.png
 npmPackageName: '@backstage/plugin-circleci'
 tags:
@@ -4,7 +4,7 @@ author: Trivago
 authorUrl: https://www.trivago.com
 category: CI
 description: Build, test, and deploy on Google's serverless CI/CD platform.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/cloudbuild
+documentation: https://github.com/backstage/backstage/tree/master/plugins/cloudbuild
 iconUrl: https://avatars2.githubusercontent.com/u/38220399?s=400&v=4
 npmPackageName: '@backstage/plugin-cloudbuild'
 tags:
@@ -4,7 +4,7 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: Discovery
 description: Visualize, understand and optimize your team's cloud costs.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/cost-insights
+documentation: https://github.com/backstage/backstage/tree/master/plugins/cost-insights
 iconUrl: https://www.materialui.co/materialIcons/editor/monetization_on_white_192x192.png
 npmPackageName: '@backstage/plugin-cost-insights'
 tags:
@@ -4,7 +4,7 @@ author: Trivago
 authorUrl: https://www.trivago.com
 category: Cloud
 description: Create, list and manage your Google Cloud Projects.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/gcp-projects
+documentation: https://github.com/backstage/backstage/tree/master/plugins/gcp-projects
 iconUrl: https://avatars1.githubusercontent.com/u/2810941?s=280&v=4
 npmPackageName: '@backstage/plugin-gcp-projects'
 tags:
@@ -4,7 +4,7 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: CI
 description: GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/github-actions
+documentation: https://github.com/backstage/backstage/tree/master/plugins/github-actions
 iconUrl: https://avatars2.githubusercontent.com/u/44036562?s=400&v=4
 npmPackageName: '@backstage/plugin-github-actions'
 tags:
@@ -4,7 +4,7 @@ author: Weaveworks
 authorUrl: https://www.weave.works/
 category: Kubernetes
 description: Create GitOps-managed Kubernetes clusters. Currently, it supports provisioning EKS clusters on GitHub via GitHub Actions.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/gitops-profiles
+documentation: https://github.com/backstage/backstage/tree/master/plugins/gitops-profiles
 iconUrl: https://res-5.cloudinary.com/crunchbase-production/image/upload/c_lpad,h_256,w_256,f_auto,q_auto:eco/v1462316670/i9d3delzvx1erzjhmcws.png
 npmPackageName: '@backstage/plugin-gitops-profiles'
 tags:
@@ -4,7 +4,7 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: Debugging
 description: Integrates GraphiQL as a tool to browse GraphQL API endpoints inside Backstage.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/graphiql
+documentation: https://github.com/backstage/backstage/tree/master/plugins/graphiql
 iconUrl: https://upload.wikimedia.org/wikipedia/commons/thumb/1/17/GraphQL_Logo.svg/1024px-GraphQL_Logo.svg.png
 npmPackageName: '@backstage/plugin-graphiql'
 tags:
@@ -4,7 +4,7 @@ author: '@timja'
 authorUrl: https://github.com/timja
 category: CI
 description: Jenkins offers a simple way to set up a continuous integration and continuous delivery environment.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/jenkins
+documentation: https://github.com/backstage/backstage/tree/master/plugins/jenkins
 iconUrl: https://img.icons8.com/color/1600/jenkins.png
 npmPackageName: '@backstage/plugin-jenkins'
 tags:
@@ -4,7 +4,7 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: Accessibility
 description: Google's Lighthouse tool is a great resource for benchmarking and improving the accessibility, performance, SEO, and best practices of your website.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/lighthouse
+documentation: https://github.com/backstage/backstage/tree/master/plugins/lighthouse
 iconUrl: https://seeklogo.com/images/G/google-lighthouse-logo-1C7FA08580-seeklogo.com.png
 npmPackageName: '@backstage/plugin-lighthouse'
 tags:
@@ -4,7 +4,7 @@ author: '@timwheelercom'
 authorUrl: https://github.com/timwheelercom
 category: Monitoring
 description: Observability platform built to help engineers create and monitor their software.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/newrelic
+documentation: https://github.com/backstage/backstage/tree/master/plugins/newrelic
 iconUrl: https://www.mulesoft.com/sites/default/files/2018-10/New_relic.png
 npmPackageName: '@backstage/plugin-newrelic'
 tags:
@@ -4,6 +4,6 @@ author: '@andrewthauer'
 authorUrl: https://github.com/andrewthauer
 category: Monitoring
 description: View Rollbar errors for your services in Backstage.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/rollbar
+documentation: https://github.com/backstage/backstage/tree/master/plugins/rollbar
 iconUrl: https://rollbar.com/assets/media/rollbar-mark-color.png
 npmPackageName: '@backstage/plugin-rollbar'
@@ -4,6 +4,6 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: Monitoring
 description: View Sentry issues in Backstage.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/sentry
+documentation: https://github.com/backstage/backstage/tree/master/plugins/sentry
 iconUrl: https://sentry-brand.storage.googleapis.com/sentry-glyph-white.png
 npmPackageName: '@backstage/plugin-sentry'
@@ -4,6 +4,6 @@ author: SDA SE
 authorUrl: https://sda.se/
 category: Quality
 description: Components to display code quality metrics from SonarCloud and SonarQube.
-documentation: https://github.com/spotify/backstage/blob/master/plugins/sonarqube/README.md
+documentation: https://github.com/backstage/backstage/blob/master/plugins/sonarqube/README.md
 iconUrl: img/sonarqube-icon.svg
 npmPackageName: '@backstage/plugin-sonarqube'
@@ -4,6 +4,6 @@ author: Spotify
 authorUrl: https://github.com/spotify
 category: Discovery
 description: Visualize the your company's official guidelines of different areas of software development.
-documentation: https://github.com/spotify/backstage/tree/master/plugins/tech-radar
+documentation: https://github.com/backstage/backstage/tree/master/plugins/tech-radar
 iconUrl: https://www.materialui.co/materialIcons/action/track_changes_white_192x192.png
 npmPackageName: '@backstage/plugin-tech-radar'
@@ -31,7 +31,7 @@ class Index extends React.Component {
                high-quality code quickly — without compromising autonomy.
              </Block.Paragraph>
              <Block.LinkButton
-                href={'https://github.com/spotify/backstage#getting-started'}
+                href={'https://github.com/backstage/backstage#getting-started'}
              >
                GitHub
              </Block.LinkButton>
@@ -282,7 +282,7 @@ class Index extends React.Component {
            Build your own software templates
          </ActionBlock.Title>
          <ActionBlock.Link
-            href={`https://github.com/spotify/backstage/blob/master/docs/features/software-templates/extending/index.md`}
+            href={`https://github.com/backstage/backstage/blob/master/docs/features/software-templates/extending/index.md`}
          >
            Contribute
          </ActionBlock.Link>
@@ -98,11 +98,11 @@ const Plugins = () => (
          <Container className="PluginCardFooter">
            <p>
              See what plugins are already{' '}
-              <a href="https://github.com/spotify/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aplugin+sort%3Areactions-%2B1-desc">
+              <a href="https://github.com/backstage/backstage/issues?q=is%3Aissue+is%3Aopen+label%3Aplugin+sort%3Areactions-%2B1-desc">
                in progress
              </a>{' '}
              and 👍. Missing a plugin for your favorite tool? Please{' '}
-              <a href="https://github.com/spotify/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME">
+              <a href="https://github.com/backstage/backstage/issues/new?labels=plugin&template=plugin_template.md&title=%5BPlugin%5D+THE+PLUGIN+NAME">
                suggest
              </a>{' '}
              a new one.
--- a/Show More
+++ b/Show More