90a54f30f7
* 'master' of github.com:spotify/backstage: docs: clarify role of identity and SignInPage tests(register-component): update tests to use test-id for submit button feature(component-registration): allow SCM specification Fix identity typo Bump version of techdocs-core plugin in techdocs-container (#2539) TechDocs: adjust mkdocs extensions (#2516) comment to explain option Added toggled option for allowing longpath in windows through nodegit create-app: fix missing .gitignore file when scaffolded
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.
