Signed-off-by: markyjackson-taulia <marky.r.jackson@gmail.com>
This commit is contained in:
markyjackson-taulia
2024-06-19 06:58:17 -07:00
committed by aramissennyeydd
parent 3f5b5445fe
commit c537111903
+5 -3
View File
@@ -12,17 +12,19 @@ Our vision for the plugin ecosystem champions flexibility, empowering you to inc
## Creating a Plugin
Embark on your plugin development journey by following the detailed steps provided [here](create-a-plugin.md).
Embark on your plugin development journey by following the detailed steps provided in the [Create a Plugin guide](create-a-plugin.md).
## Suggesting a Plugin
If you're developing an open-source plugin, we encourage you to initiate a [new Issue in the community plugins repo](https://github.com/backstage/community-plugins/issues/new/choose). This gesture not only informs the community about upcoming plugins but also invites collaboration and feedback.
If you're developing an open-source plugin, we encourage you to create a
[new issue in the community plugins repository](https://github.com/backstage/community-plugins/issues/new/choose).
This informs the community about upcoming plugins and invites collaboration and feedback.
This approach is equally beneficial if you conceive an idea for a potentially impactful plugin but prefer if another contributor undertakes its development.
## Integration with the Software Catalog
Should your plugin complement the Software Catalog rather than exist as a standalone entity (for instance, as an additional tab or a card within an "Overview" tab), you'll find comprehensive guidance on achieving this integration [here](integrating-plugin-into-software-catalog.md).
Should your plugin complement the Software Catalog rather than exist as a standalone feature (for instance, as an additional tab or a card within an "Overview" tab), you'll find comprehensive guidance on achieving this integration in the [Integrating Plugin into Software Catalog guide](integrating-plugin-into-software-catalog.md).
## Guides for Plugin Development