blam
cc80ff7d46
* 'master' of github.com:spotify/backstage: v0.1.1-alpha.17 create-app: remove copyright headers from backend template create-app: update tech-docs backend wiring create-app: add empty list of auth providers cli: fix e2e package references Add api-catalog.yaml file (#1822) cli: update e2e-test to include dist versions of backend packages chore(deps): bump helmet from 3.23.2 to 4.0.0 feat: add simple healthcheck to app container packages/cli: fix packaging of packages without deps config-loader,backend-common: refactor config loading to pass in path and use common util for backend techdocs-cli: import version from techdocs-cli directly create-app: use cli-common to discover paths and import version directly cli: use cli-common to discover paths packages: add cli-common
Plugins
Backstage is a single-page application composed of a set of plugins.
Our goal for the plugin ecosystem is that the definition of a plugin is flexible enough to allow you to expose pretty much any kind of infrastructure or software development tool as a plugin in Backstage. By following strong design guidelines we ensure the the overall user experience stays consistent between plugins.
Creating a plugin
To create a plugin, follow the steps outlined here.
Suggesting a plugin
If you start developing a plugin that you aim to release as open source, we suggest that you create a new new Issue. 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.