Files
backstage/plugins
Patrik Oldsberg 10e5d6f8aa Remove NavItemBlueprint in favor of page-based nav discovery
Drop the deprecated NavItemBlueprint from the public API and migrate core
plugins to set title and icon on PageBlueprint instead. AppNav keeps
backward compatibility for legacy nav-item extensions via an internal
core.nav-item.target data ref.

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-19 11:00:46 +02:00
..
2026-05-12 18:28:01 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-12 18:28:01 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-12 18:28:01 +00:00
2026-05-12 18:28:01 +00:00
2026-05-12 18:28:01 +00:00
2026-05-05 14:57:07 +00:00
2026-04-28 15:53:09 +00:00
2026-04-28 15:53:09 +00:00
2026-05-05 14:57:07 +00:00
2026-05-12 18:28:01 +00:00

Plugins

Backstage is a single-page application composed of a set of plugins. This folder holds numerous plugins that are managed by this repository. However, most plugins are in the community plugins repo - hop over there if you want to contribute!

For more information about the plugin ecosystem, see the documentation here:

https://backstage.io/docs/plugins/

You can also see the Plugin Marketplace for other open source plugins you can add to your Backstage instance.

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 on the community plugins repo. 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.