paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 27 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:49 -07:00
committed by aramissennyeydd
parent b5b42fe70b
commit d76cab574b
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
@@ -16,7 +16,7 @@ Plugins facilitate better collaboration among teams by consolidating documentati
## Consistency and Best Practices
By adhering to Backstage’s design guidelines, plugins ensure a consistent user experience across the platform. This consistency helps in maintaining usability and reducing the learning curve for new users, promoting the adoption of best practices within development teams【93†source】【95†source】. More details can be found in the [Introduction to Plugins](https://backstage.io/docs/plugins/) section.
By adhering to Backstage’s design guidelines, plugins ensure a consistent user experience across the platform. This consistency helps in maintaining usability and reducing the learning curve for new users, promoting the adoption of best practices within development teams. More details can be found in the [Introduction to Plugins](https://backstage.io/docs/plugins/) section.
## Scalability and Maintenance