From 88b7066740137f3f70e99c82f3a9cc2d7d727504 Mon Sep 17 00:00:00 2001 From: Simon Olander Date: Wed, 27 Nov 2024 16:20:01 +0100 Subject: [PATCH] chore(docs): fix broken links --------- Signed off by: Simon Olander (simon.olander@sap.com) --- docs/contribute/plugins.md | 2 +- docs/getting-started/core-concepts/_index.md | 8 ++++---- docs/user-guides/organization/creation.md | 2 +- docs/user-guides/plugin/local-plugin-development.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/contribute/plugins.md b/docs/contribute/plugins.md index c0fd2ec62..81438803a 100644 --- a/docs/contribute/plugins.md +++ b/docs/contribute/plugins.md @@ -56,7 +56,7 @@ Here's a high-level overview of how to develop a plugin for Greenhouse: - Test your plugin thoroughly to ensure it works as intended. Verify that both the frontend and backend components function correctly. - Implement validation for your plugin's configuration options. This helps prevent users from providing incorrect or incompatible values. - - Implement Helm Chart Tests for your plugin if it includes a Helm Chart. For more information on how to write Helm Chart Tests, please refer to [this guide](/docs/user-guides/plugin/plugin-tests). + - Implement Helm Chart Tests for your plugin if it includes a Helm Chart. For more information on how to write Helm Chart Tests, please refer to [this guide](/greenhouse/docs/user-guides/plugin/plugin-tests). 5. **Documentation**: diff --git a/docs/getting-started/core-concepts/_index.md b/docs/getting-started/core-concepts/_index.md index ea4dafd49..7b468db6a 100644 --- a/docs/getting-started/core-concepts/_index.md +++ b/docs/getting-started/core-concepts/_index.md @@ -9,7 +9,7 @@ description: > | Feature | Description | API | UI | Comments | | --- | --- | --- | --- | --- | -| [Organizations](/docs/getting-started/core-concepts/organizations) | Organizations are the top-level entities in Greenhouse. | 🟢 | 🟢 | | -| [Teams](/docs/getting-started/core-concepts/teams.md) | Teams are used to manage access and ownership of resources in Greenhouse. | 🟢 | 🟡 | Read-only access to Teams via the UI | -| [Clusters](/docs/getting-started/core-concepts/clusters.md) | Clusters represent a Kubernetes cluster that is managed by Greenhouse. | 🟡 | 🟡 | Limited modification of Clusters via UI, CLI for KubeConfig registry planned. | -| [Plugin Definitions & Plugins](/docs/getting-started/core-concepts/plugins.md) | Plugins are software components that extend and integrate with Greenhouse . | 🟡 | 🟡 | Read-only access via UI, a native Plugin Catalog is planned. | +| [Organizations](/greenhouse/docs/getting-started/core-concepts/organizations) | Organizations are the top-level entities in Greenhouse. | 🟢 | 🟢 | | +| [Teams](/greenhouse/docs/getting-started/core-concepts/teams.md) | Teams are used to manage access and ownership of resources in Greenhouse. | 🟢 | 🟡 | Read-only access to Teams via the UI | +| [Clusters](/greenhouse/docs/getting-started/core-concepts/clusters.md) | Clusters represent a Kubernetes cluster that is managed by Greenhouse. | 🟡 | 🟡 | Limited modification of Clusters via UI, CLI for KubeConfig registry planned. | +| [Plugin Definitions & Plugins](/greenhouse/docs/getting-started/core-concepts/plugins.md) | Plugins are software components that extend and integrate with Greenhouse . | 🟡 | 🟡 | Read-only access via UI, a native Plugin Catalog is planned. | diff --git a/docs/user-guides/organization/creation.md b/docs/user-guides/organization/creation.md index 94a62b8b7..8cfc170bb 100644 --- a/docs/user-guides/organization/creation.md +++ b/docs/user-guides/organization/creation.md @@ -36,7 +36,7 @@ This ensures all pre-requisites are met, the organization is configured correctl For SAP, we recommend using a SAP ID service (IDS) tenant. Please include the parameters for your tenant in the message to the Greenhouse team when signing up. - If you don't have a SAP ID Service tenant yet, please refer to the [SAP ID Service](/docs/user-guides/organization/sap-id) section for more information. + If you don't have a SAP ID Service tenant yet, please refer to the [SAP ID Service](/greenhouse/user-guides/organization/sap-id) section for more information. 3. **Greenhouse organization** diff --git a/docs/user-guides/plugin/local-plugin-development.md b/docs/user-guides/plugin/local-plugin-development.md index cc3aee489..ba0564ab7 100644 --- a/docs/user-guides/plugin/local-plugin-development.md +++ b/docs/user-guides/plugin/local-plugin-development.md @@ -27,7 +27,7 @@ At the end of the guide you will have spun up the local development environment, ### Starting the local develoment environment -Follow the [Local Development](/docs/contribute/local-dev) documentation to spin up the local Greenhouse development environment. +Follow the [Local Development](/greenhouse/docs/contribute/local-dev) documentation to spin up the local Greenhouse development environment. This will provide you with a local Greenhouse instance running, filled with some example Greenhouse resources and the Greenhouse UI running on `http://localhost:3000`.