From fb31ce1230d1fadd3745627fce8786d1f688de60 Mon Sep 17 00:00:00 2001 From: Vincenzo Scamporlino Date: Mon, 22 Apr 2024 12:25:42 +0200 Subject: [PATCH] docs: fix community-plugins links Signed-off-by: Vincenzo Scamporlino --- microsite/blog/2020-04-06-lighthouse-plugin.mdx | 2 +- microsite/blog/2020-05-22-phase-2-service-catalog.mdx | 2 +- microsite/blog/2020-10-22-cost-insights-plugin.mdx | 6 +++--- microsite/data/plugins/adr.yaml | 2 +- microsite/data/plugins/allure.yaml | 2 +- microsite/data/plugins/azure-sites.yaml | 2 +- microsite/data/plugins/cicd-statistics.yaml | 4 ++-- microsite/data/plugins/cloud-build.yaml | 4 ++-- microsite/data/plugins/codescene.yaml | 4 ++-- microsite/data/plugins/cost-insights.yaml | 4 ++-- microsite/data/plugins/entity-feedback.yaml | 4 ++-- microsite/data/plugins/entity-validation.yaml | 4 ++-- microsite/data/plugins/gcp-projects.yaml | 4 ++-- microsite/data/plugins/git-release-manager.yaml | 4 ++-- microsite/data/plugins/github-actions.yaml | 4 ++-- microsite/data/plugins/github-pull-requests-board.yaml | 4 ++-- microsite/data/plugins/gitops-cluster.yaml | 4 ++-- 17 files changed, 30 insertions(+), 30 deletions(-) diff --git a/microsite/blog/2020-04-06-lighthouse-plugin.mdx b/microsite/blog/2020-04-06-lighthouse-plugin.mdx index d94ec8bd8d..0027d0521c 100644 --- a/microsite/blog/2020-04-06-lighthouse-plugin.mdx +++ b/microsite/blog/2020-04-06-lighthouse-plugin.mdx @@ -33,7 +33,7 @@ Trigger an audit directly from Backstage, or trigger audits programmatically wit ## Using Lighthouse in Backstage -To learn how you can enable Lighthouse auditing within Backstage, head over to the [README](https://github.com/backstage/backstage/tree/master/plugins/lighthouse) for the plugin to get started. +To learn how you can enable Lighthouse auditing within Backstage, head over to the [README](https://github.com/backstage/community-plugins/tree/main/workspaces/lighthouse/plugins/lighthouse) for the plugin to get started. ## A personal note diff --git a/microsite/blog/2020-05-22-phase-2-service-catalog.mdx b/microsite/blog/2020-05-22-phase-2-service-catalog.mdx index 3b556bbd3d..81c99c7c07 100644 --- a/microsite/blog/2020-05-22-phase-2-service-catalog.mdx +++ b/microsite/blog/2020-05-22-phase-2-service-catalog.mdx @@ -40,7 +40,7 @@ On top of that, we have found that the service catalog is a great way to organis ![img](assets/20-05-20/tabs.png) -More concretely, having this structure in place will allow plugins such as [CircleCI](https://github.com/backstage/backstage/tree/master/plugins/circleci) to show only the builds for the specific service you are viewing, or a [Spinnaker](https://github.com/backstage/backstage/issues/631) plugin to show running deployments, or an Open API plugin to [show documentation](https://github.com/backstage/backstage/issues/627) for endpoints exposed by the service, or the [Lighthouse](https://github.com/backstage/backstage/tree/master/plugins/lighthouse) plugin to show audit reports for your website. You get the point. +More concretely, having this structure in place will allow plugins such as [CircleCI](https://github.com/backstage/backstage/tree/master/plugins/circleci) to show only the builds for the specific service you are viewing, or a [Spinnaker](https://github.com/backstage/backstage/issues/631) plugin to show running deployments, or an Open API plugin to [show documentation](https://github.com/backstage/backstage/issues/627) for endpoints exposed by the service, or the [Lighthouse](https://github.com/backstage/community-plugins/tree/main/workspaces/lighthouse/plugins/lighthouse) plugin to show audit reports for your website. You get the point. ## Timeline diff --git a/microsite/blog/2020-10-22-cost-insights-plugin.mdx b/microsite/blog/2020-10-22-cost-insights-plugin.mdx index 98bca88477..1ffddd3303 100644 --- a/microsite/blog/2020-10-22-cost-insights-plugin.mdx +++ b/microsite/blog/2020-10-22-cost-insights-plugin.mdx @@ -5,7 +5,7 @@ author: Janisa Anandamohan, Spotify authorURL: https://twitter.com/janisa_a --- -How did Spotify save millions on cloud costs within a matter of months?? We made cost optimization just another part of the daily development process. Our newly open sourced [Cost Insights plugin](https://github.com/backstage/backstage/tree/master/plugins/cost-insights) makes a team’s cloud costs visible — and actionable — right inside Backstage. So engineers can see the impact of their cloud usage (down to a product and resource level) and make optimizations wherever and whenever it makes sense. By managing cloud costs from the ground up, you can make smarter decisions that let you continue to build and scale quickly, without wasting resources. +How did Spotify save millions on cloud costs within a matter of months?? We made cost optimization just another part of the daily development process. Our newly open sourced [Cost Insights plugin](https://github.com/backstage/community-plugins/tree/main/workspaces/cost-insights/plugins/cost-insights) makes a team’s cloud costs visible — and actionable — right inside Backstage. So engineers can see the impact of their cloud usage (down to a product and resource level) and make optimizations wherever and whenever it makes sense. By managing cloud costs from the ground up, you can make smarter decisions that let you continue to build and scale quickly, without wasting resources.