one more try

Signed-off-by: aramissennyeydd <aramis.sennyey@doordash.com>
This commit is contained in:
aramissennyeydd
2024-10-19 14:17:18 -04:00
parent 9679c47aac
commit f56b2646a5
3 changed files with 7 additions and 7 deletions
+3 -4
View File
@@ -1,15 +1,14 @@
---
id: guides
title: Guides for Plugins
status: in-progress
---
## Guides for Plugin Development
:::note Note
This section is still a work in progress, many of the guides described below do not exist yet.
This docs is still a work in progress, many of the guides described below do not exist yet.
:::
## Guides for Plugin Development
### For Beginners: Introduction to Plugin Development
This section is designed for those new to plugin development. It covers the basics and provides a foundation for more advanced topics.
-2
View File
@@ -23,5 +23,3 @@ This approach is equally beneficial if you conceive an idea for a potentially im
## Integration with the Software Catalog
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).
---
@@ -1,9 +1,12 @@
---
id: why-build-plugins
title: Why build plugins?
status: in-progress
---
:::note Note
This docs is still a work in progress, many of the guides described below do not exist yet.
:::
# Why Build Plugins? Introduction to the Value and Impact of Plugins within Backstage
Backstage plugins are essential components that enable the integration of various tools and services into a unified developer portal. Heres a detailed look at how and why building plugins for Backstage can be highly beneficial: