Ben Lambert
a14dae9b10
* docs(scaffolder): Added some reference for the Template kind in the service catalog * docs(scaffolder): adding a basic readme for the scaffolder * docs(scaffolder): more small fixes * chore(scaffolder): removing unused routes in the scaffolder * docs(scaffolder): fixing linking to the template entity * docs(scaffolder): fixing indentation * docs(scaffolder): rewrite a little * chore(scaffolder): Added some more documentation sections * docs(scaffolder): added some documentation about loading your own templates * docs(scaffolder): created some great documentation. make docs great again * docs(scaffolder): added some more info about creating your own templater * chore(scaffolder): finshing of create your own templater docs * docs(scaffolder): updating the last of the preparr * docs(scaffolder): think docs are great for scaffolder again * chore(scaffolder): fixing issue with publisher base mistyping * docs(scaffolder): creating some how to use documentation * docs(scaffolder): more user docs for the scaffolder * docs(scaffolder): fix header * docs(scaffolder): fixing * docs(scaffolder): shuffle around the documenation
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.
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.