blam
3df4cdd1b5
* 'master' of github.com:backstage/backstage: (430 commits) Fix techdocs for url locations (#3589) Slightly more padding in dense tables (#3571) build(deps-dev): bump docusaurus in /microsite (#3543) fix(lighthouse): Typo & example code tweaks (#3573) build(deps-dev): bump @types/testing-library__jest-dom (#3596) app,backend,create-app: add files declaration to package.jsons cli: update experimental backend:bundle command to output archives to dist catalog-backend: read all relations at once Deduplicate @changesets/config in yarn.lock update dep version Change sample repo URL Convert card to full Material-UI components fix import Increase pageSize for search result view (#3565) core-api: update ApiFactory type to correctly infer API type and disallow mismatched implementations update dependencies version Update CHANGELOG.md bump app template deps accordingly Delete PagerdutyCard.tsx remove plugin-catalog dep ...
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.
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.