paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 37 Packages Projects Releases Wiki Activity

Update docs/integrations/plugins-101-building-your-first-plugin/why-build-plugins.md

Browse Source 
Co-authored-by: Aramis Sennyey <159921952+aramissennyeydd@users.noreply.github.com>
Signed-off-by: Mark Jackson <16655670+markjacksonfishing@users.noreply.github.com>
Signed-off-by: aramissennyeydd <aramis.sennyey@doordash.com>
This commit is contained in:
Mark Jackson
2024-08-19 07:25:18 -07:00
committed by aramissennyeydd
parent 22de0c6f49
commit 8ec73c607e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/plugins-101-building-your-first-plugin/why-build-plugins.md
+1 -1
View File
@@ -8,7 +8,7 @@ Plugins in Backstage centralize and simplify access to tools, reducing the time
## Customizable and Extensible Platform
Backstage's plugin architecture is designed to be highly flexible, enabling the integration of nearly any infrastructure or software development tool. This extensibility allows organizations to tailor Backstage to meet their specific needs, integrating internal tools, third-party services, and other custom functionalities seamlessly【93†source】【94†source】. For detailed guidelines on plugin development, refer to the [Backstage Plugin Development documentation](https://backstage.io/docs/plugins/plugin-development/).
Backstage's plugin architecture is designed to be highly flexible, enabling the integration of nearly any infrastructure or software development tool. This extensibility allows organizations to tailor Backstage to meet their specific needs, integrating internal tools, third-party services, and other custom functionalities seamlessly. For detailed guidelines on plugin development, refer to the [Backstage Plugin Development documentation](https://backstage.io/docs/plugins/plugin-development/).
## Improved Collaboration and Knowledge Sharing