Files
backstage/plugins
Himanshu Mishra 511f59f021 1. Use $file for googleGcs.credentials
2. Clarify that techdocs-common is only used in backend plugin since it is compiled to commonJS
2020-12-09 20:11:33 +01:00
..
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-07 16:46:15 +01:00
2020-12-03 15:28:22 +00:00
2020-12-04 10:42:47 -05:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-07 16:46:15 +01:00
2020-12-04 16:44:01 +01:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00:00
2020-12-03 15:28:22 +00: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 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 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.