Files
backstage/plugins
Patrik Oldsberg 891628b3b5 Merge pull request #3753 from backstage/mob/rr
core-api: Introduce new plugin extension API
2020-12-18 13:28:16 +01:00
..
2020-12-17 10:16:33 +00:00
2020-12-10 11:25:39 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 11:51:43 +01:00
2020-12-17 11:51:43 +01:00
2020-12-17 10:16:33 +00:00
2020-12-17 11:51:43 +01:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 11:51:43 +01:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-10 11:25:39 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 11:51:43 +01:00
2020-12-17 10:16:33 +00:00
2020-12-17 10:16:33 +00:00
2020-12-17 11:51:43 +01:00
2020-12-17 11:51:43 +01:00
2020-11-03 11:03:49 +01: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.