From 67cd270143245be4de5d9330d7762c5fbe3b5c7f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20=C3=85lund?= Date: Mon, 31 Aug 2020 09:29:56 +0200 Subject: [PATCH] [Docs] Change edit URL and tweak adopting.md (#2151) * [Docs] Change edit URL * Update adopting.md --- docs/overview/adopting.md | 20 ++++++++++++++++++-- microsite/siteConfig.js | 2 +- 2 files changed, 19 insertions(+), 3 deletions(-) diff --git a/docs/overview/adopting.md b/docs/overview/adopting.md index 52c0118a6a..893eac6398 100644 --- a/docs/overview/adopting.md +++ b/docs/overview/adopting.md @@ -87,14 +87,17 @@ Example of tactics we have used to evangelize Backstage internally: - Pro-actively identify new plugins. Reach out to teams that own internal UIs or platforms that you think would make sense to consolidate into Backstage. -## Metrics +## KPIs and metrics These are some of the metrics that you can use to verify if Backstage has a successful impact on your software development process: - **Onboarding time** Time until new engineers are productive. At Spotify we measure this as the time until the employee has merged their 10th PR (this - metric was down 55% two years after deploying Backstage). + metric was down 55% two years after deploying Backstage). Even though you may + not be onboarding engineers at a rapid pace, this metric is a great proxy for + the overall complexity of your ecosystem. Reducing it will therefore benefit + your whole engineering organization, not just new joiners. - **Number of merges per developer/day** Less time spent jumping between different tools and looking for information means more time to focus on @@ -142,3 +145,16 @@ Backstage as _the_ platform: - % of contributions coming from outside the central Backstage team (currently 85% inside Spotify) + +- Traditional metrics such as visits (MAU, DAU, etc) and page views. Currently + ~50% of all Spotifiers use Backstage on a monthly basis, even though the + percentage of engineers is below 50%. Most engineers actually use Backstage on + a daily basis. + +Again, any feedback is appreciated. Please use the Edit button at the top of the +page to make a suggestion. + +_**Note!** It might be tempting to try to optimize Backstage usage and +"engagement". Even though you want to consolidate all your tooling and technical +documentation in Backstage, it is important to remember that time spent in +Backstage is time not spent writing code_ 🙃 diff --git a/microsite/siteConfig.js b/microsite/siteConfig.js index d6a2da9f91..73852d6ddd 100644 --- a/microsite/siteConfig.js +++ b/microsite/siteConfig.js @@ -17,7 +17,7 @@ const siteConfig = { url: 'https://backstage.io', // Your website URL cname: 'backstage.io', baseUrl: '/', // Base URL for your project */ - editUrl: 'https://github.com/spotify/backstage/tree/master/docs/', + editUrl: 'https://github.com/spotify/backstage/edit/master/docs/', // Used for publishing and more projectName: 'backstage',