blam
f76a8aedf4
* 'master' of github.com:backstage/backstage: (758 commits) add zalando to adpoters list Avoid passing undefined to values that are marked as optional Support profile of groups in LdapOrgReaderProcessor Import picture and display name by the GitHubOrgReaderProcessor Use the new group profile section in the group profile card Add support for the group profile element to Microsoft Graph processor Add profile section to group entity Implement readTree on BitBucketUrlReader - Add getBitbucketDefaultBranch Implement readTree on BitBucketUrlReader - Modify changeset Implement readTree on BitBucketUrlReader - Implement getBitbucketDownloadUrl and remove hash for Bitbucket Server Implement readTree on BitBucketUrlReader WIP: implement readTree for bitbucket updated scaffolder config.d to avoid config failure build(deps): bump swagger-ui-react from 3.37.2 to 3.38.0 included changeset Introduced config schema for plugins/scaffolder-backend Write relations directly as part of batch add / update of entities. Add codeowners for techdocs-common package techdocs-common: Add type dependencies Update nice-trains-punch.md ...
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 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 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.