Merge pull request #716 from jakobmoellerdev/versioned_docs

chore: docusaurus bump to `3.9.1`, update image paths and dependencies in website

Author: k8s-ci-robot

.github/workflows/test-docs.yaml

@@ -15,12 +15,12 @@ jobs:
       run:
         working-directory: ./website
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
         with:
           fetch-depth: 0
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-node@v5
         with:
-          node-version: 18
+          node-version: 20
 
       - name: Install dependencies
         run: npm install --frozen-lockfile

examples/aws/webstack/Readme.md

@@ -3,7 +3,7 @@
 This example creates a ResourceGraphDefinition called `WebStack` comprised of
 three other RGs: `WebApp`, `S3Bucket`, and `PodIdentity`
 
-![Nested RGD Instance](../../../images/architecture-diagrams/kro-WebStack.png)
+![Nested RGD Instance](../../../website/static/img/architecture/kro-WebStack.png)
 _Figure 1: Nested RGD Example_
 
 ### Create ResourceGraphDefinitions

website/docs/docs/concepts/00-resource-group-definitions.md

@@ -43,7 +43,7 @@ The `spec` section of a ResourceGraphDefinition contains two main components:
   - Dependencies between resources
   - Conditions for inclusion
   - Readiness criteria
-  - [External References](#resourcegraphdefinition-more-about-resources)
+  - [External References](#using-externalref-to-reference-objects-outside-the-resourcegraphdefinition)
 
 This structure translates to YAML as follows:
 

website/docs/docs/faq.md

@@ -83,7 +83,7 @@ sidebar_position: 100
    created by KRO instances. 
 
 
-   ![ArgoCD RGD tracked Instance](../../static/img/KRO-ArgoCD-Tracking.png)
+   ![ArgoCD RGD tracked Instance](/img/KRO-ArgoCD-Tracking.png)
    
    Note that the example shown above depicts ArgoCD's default resource tracking 
    via annotations. You may choose to use `annotation+label` or just `label` and 

website/docs/docs/overview.md

@@ -34,7 +34,7 @@ standardized and streamlined manner.
 
 <div align="center">
 
-![End user interface - Custom API](../../../images/architecture-diagrams/KRO-Dev-Interface.png)
+![End user interface - Custom API](/img/architecture/KRO-Dev-Interface.png)
 _Figure 1: End user interface - Custom API_
 
 </div>
@@ -56,7 +56,7 @@ handles the deployment and configuration of the required resources.
 
 <div align="center">
 
-![Platform Team Interface](../../../images/architecture-diagrams/KRO-Platform-Team.png)
+![Platform Team Interface](/img/architecture/KRO-Platform-Team.png)
 _Figure 2: ResourceGraphDefinition (RG) - Platform Team Interface_
 
 </div>
@@ -74,7 +74,7 @@ requirements.
 
 <div align="center">
 
-![ResourceGraphDefinition Instance](../../../images/architecture-diagrams/KRO-Instance.png)
+![ResourceGraphDefinition Instance](/img/architecture/KRO-Instance.png)
 _Figure 3: ResourceGraphDefinition Instance (RGI)_
 
 </div>

website/docusaurus.config.ts

@@ -23,7 +23,11 @@ const config: Config = {
   projectName: "kro", // Usually your repo name.
 
   onBrokenLinks: "throw",
-  onBrokenMarkdownLinks: "warn",
+  markdown: {
+      hooks: {
+        onBrokenMarkdownLinks: "warn",
+      },
+  },
 
   // Even if you don't use internationalization, you can use this field to set
   // useful metadata like html lang. For example, if your site is Chinese, you