paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 18 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:24:28 -07:00
committed by aramissennyeydd
parent 7f681d4553
commit b5b42fe70b
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
@@ -12,7 +12,7 @@ Backstage's plugin architecture is designed to be highly flexible, enabling the
## Improved Collaboration and Knowledge Sharing
Plugins facilitate better collaboration among teams by consolidating documentation, code repositories, CI/CD pipelines, and monitoring tools in one place. This centralization makes it easier for team members to find information, share insights, and collaborate on projects, enhancing overall team productivity and coherence【94†source】【95†source】.
Plugins facilitate better collaboration among teams by consolidating documentation, code repositories, CI/CD pipelines, and monitoring tools in one place. This centralization makes it easier for team members to find information, share insights, and collaborate on projects, enhancing overall team productivity and coherence.
## Consistency and Best Practices