paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 46 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:21:08 -07:00
committed by aramissennyeydd
parent 43ecc00742
commit 7f681d4553
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
@@ -4,7 +4,7 @@ Backstage plugins are essential components that enable the integration of variou
## Enhancing Developer Productivity
Plugins in Backstage centralize and simplify access to tools, reducing the time developers spend switching between different systems. By providing a consistent interface and user experience, plugins minimize cognitive load and streamline workflows, allowing developers to focus more on coding and less on tool management. Plugins can leverage platform APIs and reusable UI components to integrate external data and services seamlessly【93†source】【94†source】.
Plugins in Backstage centralize and simplify access to tools, reducing the time developers spend switching between different systems. By providing a consistent interface and user experience, plugins minimize cognitive load and streamline workflows, allowing developers to focus more on coding and less on tool management. Plugins can leverage platform APIs and reusable UI components to integrate external data and services seamlessly.
## Customizable and Extensible Platform