From 44a1a447cc37100cd6e175308e8b77b92f8f7a71 Mon Sep 17 00:00:00 2001 From: Nikolas Skoufis Date: Tue, 1 Mar 2022 19:28:53 +1100 Subject: [PATCH] Fix up links to other pages Signed-off-by: Nikolas Skoufis --- docs/features/techdocs/concepts.md | 2 +- docs/features/techdocs/how-to-guides.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/features/techdocs/concepts.md b/docs/features/techdocs/concepts.md index f8e813d89e..e34f58bc70 100644 --- a/docs/features/techdocs/concepts.md +++ b/docs/features/techdocs/concepts.md @@ -62,7 +62,7 @@ However any logic that satisfies the Build Strategy interface can be implemented config as well as the entity being processed to make a decision. For an example of how the Build Strategy can be used to implement a 'hybrid' build model, refer to -the [How to implement a hybrid build strategy](./how-to-guides#how-to-implement-a-hybrid-build-strategy) guide. +the [How to implement a hybrid build strategy](./how-to-guides.md#how-to-implement-a-hybrid-build-strategy) guide. ## TechDocs Container diff --git a/docs/features/techdocs/how-to-guides.md b/docs/features/techdocs/how-to-guides.md index 5a5fe36526..56ca2252d0 100644 --- a/docs/features/techdocs/how-to-guides.md +++ b/docs/features/techdocs/how-to-guides.md @@ -541,7 +541,7 @@ Done! Now you have a support of the following diagrams along with mermaid: ## How to implement a hybrid build strategy -One limitation of the [Recommended deployment](./architecture#recommended-deployment) is that +One limitation of the [Recommended deployment](./architecture.md#recommended-deployment) is that the experience for users requires modifying their CI/CD process to publish their TechDocs. For some users, this may be unnecessary, and provides a barrier to entry for onboarding users to Backstage. However, a purely local TechDocs @@ -549,7 +549,7 @@ build restricts TechDocs creators to using the tooling provided in Backstage, as well as the plugins and features provided in the Backstage-included `mkdocs` installation. -To accommodate both of these use-cases, users can implement a custom [Build Strategy](./concepts#techdocs-build-strategy) +To accommodate both of these use-cases, users can implement a custom [Build Strategy](./concepts.md#techdocs-build-strategy) with logic to encode which TechDocs should be built locally, and which will be built externally.