Files
backstage/plugins
Taras Mankovski c926765a2c Allow templates to be located on non-default branch (#2839)
* Checkout branch if not on default

* Use checkout Ref

* Get first directory instead of relying on component_id

* Checkout branch when clonning

* Update test

* Default to empty string

* Added changeset

* Added test for Cookie Cutter installed & nothing generated

* Added comment
2020-10-14 08:24:41 +02:00
..
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +02:00
2020-10-12 22:42:54 +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 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.