blam
c1a21d53af
* 'master' of github.com:spotify/backstage: (45 commits) chore(catalog): simplify the filter types a little fix(catalog-backend): update the mock-data script to point to new example entities renamed example_components to example-components and deleted old exampled feat(catalog): add back ability for OR/IN type searches Add sample plugins to sidebar (#1243) chore(catalog): rename all pages and components to use Entity nomenclature fix(catalog): moar clean up Updated examples fix(catalog): add types and clean up code Added owner and lifecycle to catalog table, slightly updated examples chore(catalog): the component type is gone yarn.lock again... fix(catalog): merge errors review fixes. i thought about another force update for a moment :D move components to separate files fix(catalog): moar clean up fix(catalog): make code intention clear by renaming Merge pull request #1214 from spotify/feat/star-components Merge pull request #1194 from spotify/freben/backend-common-service Merge pull request #1215 from spotify/mob/sidebar-auth ...
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.