Files
backstage/plugins
blam 247e58689b Merge branch 'blam/scaffolder' of github.com:spotify/backstage into blam/scaffolder
* 'blam/scaffolder' of github.com:spotify/backstage: (34 commits)
  yarn.lock: bump eslint-plugin-notice
  packages/dev-utils: use doc comments + text fix in README
  darkMode: fix HorizontalScrollGrid (#666) (#668)
  darkMode: fix bottom link (#664)
  Add padding for all Stories (#663)
  Use useInterval() hook to refetch audit status in lighthouse plugin WIP (#623)
  run yarn install against master yarn.lock
  changed object to Partial type
  adjust getBBox polyfill logic
  re-ran yarn.lock
  added initial docs
  added tests for RadarPage
  re-ran yarn install
  add polyfill for SVGElement.prototype.getBBox (not supported in JSDOM)
  migrated RadarBubble to material-ui styles
  migrated RadarEntry to material-ui styles
  migrated RadarFooter to material-ui styles
  migrated RadarLegend to material-ui styles
  migrated RadarGrid to material-ui styles
  removed css modules from css
  ...
2020-04-28 22:55:04 +02:00
..
2020-04-27 10:01:57 +02:00
2020-04-27 10:01:57 +02:00
2020-04-27 15:02:40 +02:00

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.

plugin

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.