ENGDOCS-2179 (#20591)

* ENGDOCS-2179

* link fix

* more link fix

* final link fix

Author: aevesdocker

.github/CODEOWNERS

@@ -11,21 +11,21 @@
 
 /content/desktop/ @aevesdocker
 
-/content/desktop/extensions/ @aevesdocker
+/content/extensions/ @aevesdocker
 
-/content/desktop/extensions-sdk/ @aevesdocker
+/content/extensions-sdk/ @aevesdocker
 
 /content/scout/ @dvdksn
 
-/content/docker-hub/ @aevesdocker @craig-osterhout @stephaurelio
+/content/docker-hub/ @aevesdocker @craig-osterhout
 
 /content/engine/ @dvdksn
 
-/content/subscription/ @aevesdocker @stephaurelio
+/content/subscription/ @aevesdocker
 
-/content/docker-hub/publish/ @aevesdocker
+/content/docker-hub/publish/ @craig-osterhout
 
-/content/docker-hub/official_images/ @aevesdocker
+/content/docker-hub/official_images/ @craig-osterhout
 
 /content/registry/ @dvdksn
 

.github/labeler.yml

@@ -111,8 +111,8 @@ area/configuration:
 area/extensions:
   - changed-files:
       - any-glob-to-any-file:
-          - content/desktop/extensions/**
-          - content/desktop/extensions-sdk/**
+          - content/extensions/**
+          - content/extensions/extensions-sdk/**
 
 area/samples:
   - changed-files:

content/desktop/_index.md

@@ -54,7 +54,7 @@ Docker Desktop reduces the time spent on complex setups so you can focus on writ
 - Docker CLI client
 - [Docker Scout](../scout/_index.md) (additional subscription may apply)
 - [Docker Build](../build/_index.md)
-- [Docker Extensions](./extensions/_index.md)
+- [Docker Extensions](../extensions/_index.md)
 - [Docker Compose](../compose/_index.md)
 - [Docker Content Trust](../engine/security/trust/_index.md)
 - [Kubernetes](https://github.com/kubernetes/kubernetes/)

content/desktop/settings/linux.md

@@ -257,7 +257,7 @@ Use the **Extensions** tab to:
 - **Allow only extensions distributed through the Docker Marketplace**
 - **Show Docker Extensions system containers**
 
-For more information about Docker extensions, see [Extensions](../extensions/index.md).
+For more information about Docker extensions, see [Extensions](/extensions/index.md).
 
 ## Features in development
 

content/desktop/settings/mac.md

@@ -299,7 +299,7 @@ Use the **Extensions** tab to:
 - **Allow only extensions distributed through the Docker Marketplace**
 - **Show Docker Extensions system containers**
 
-For more information about Docker extensions, see [Extensions](../extensions/index.md).
+For more information about Docker extensions, see [Extensions](/extensions/index.md).
 
 ## Features in development
 

content/desktop/settings/windows.md

@@ -346,7 +346,7 @@ Use the **Extensions** tab to:
 - **Allow only extensions distributed through the Docker Marketplace**
 - **Show Docker Extensions system containers**
 
-For more information about Docker extensions, see [Extensions](../extensions/index.md).
+For more information about Docker extensions, see [Extensions](/extensions/index.md).
 
 ## Features in development
 

content/desktop/extensions/_index.md renamed to content/extensions/_index.md

@@ -2,13 +2,13 @@
 description: Extensions
 keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows
 title: Overview of Docker Extensions
-toc_min: 1
-toc_max: 2
+aliases:
+ - /desktop/extensions/
 ---
 
 Docker Extensions let you use third-party tools within Docker Desktop to extend its functionality.
 
-You can seamlessly connect your favorite development tools to your application development and deployment workflows. Augment Docker Desktop with debugging, testing, security, and networking functionalities, and create custom add-ons using the Extensions [SDK](../extensions-sdk/index.md).
+You can seamlessly connect your favorite development tools to your application development and deployment workflows. Augment Docker Desktop with debugging, testing, security, and networking functionalities, and create custom add-ons using the Extensions [SDK](extensions-sdk/index.md).
 
 Anyone can use Docker Extensions and there is no limit to the number of extensions you can install.
 

content/desktop/extensions-sdk/_index.md renamed to content/extensions/extensions-sdk/_index.md

@@ -3,32 +3,33 @@ title: Overview of the Extensions SDK
 description: Overall index for Docker Extensions SDK documentation
 keywords: Docker, Extensions, sdk
 aliases:
-- /desktop/extensions-sdk/dev/overview/
+ - /desktop/extensions-sdk/dev/overview/
+ - /desktop/extensions-sdk/
 grid:
   - title: "The build and publish process"
     description: Understand the process for building and publishing an extension.
     icon: "checklist"
-    link: "/desktop/extensions-sdk/process/"
+    link: "/extensions/extensions-sdk/process/"
   - title: "Quickstart guide"
     description: Follow the quickstart guide to create a basic Docker extension quickly.
     icon: "explore"
-    link: "/desktop/extensions-sdk/quickstart/"
+    link: "/extensions/extensions-sdk/quickstart/"
   - title: "View the design guidelines"
     description: Ensure your extension aligns to Docker's design guidelines and principles.
     icon: "design_services"
-    link: "/desktop/extensions-sdk/design/design-guidelines/"
+    link: "/extensions/extensions-sdk/design/design-guidelines/"
   - title: "Publish your extension"
     description: Understand how to publish your extension to the Marketplace.
     icon: "publish"
-    link: "/desktop/extensions-sdk/extensions/"
+    link: "/extensions/extensions-sdk/extensions/"
   - title: "Interacting with Kubernetes"
     description: Find information on how to interact indirectly with a Kubernetes cluster from your Docker extension.
     icon: "multiple_stop"
-    link: "/desktop/extensions-sdk/dev/kubernetes/"
+    link: "/extensions/extensions-sdk/guides/kubernetes/"
   - title: "Multi-arch extensions"
     description: Build your extension for multiple architectures.
     icon: "content_copy"
-    link: "/desktop/extensions-sdk/extensions/multi-arch/"
+    link: "/extensions/extensions-sdk/extensions/multi-arch/"
 ---
 
 The resources in this section help you create your own Docker extension.

content/desktop/extensions-sdk/architecture/_index.md renamed to content/extensions/extensions-sdk/architecture/_index.md

@@ -2,6 +2,8 @@
 title: Extension architecture
 description: Docker extension architecture
 keywords: Docker, extensions, sdk, metadata
+aliases: 
+ - /desktop/extensions-sdk/architecture/
 ---
 
 Extensions are applications that run inside the Docker Desktop. They're packaged as Docker images, distributed
@@ -13,19 +15,19 @@ Extensions can be composed of three (optional) components:
 - A backend: One or many containerised services running in the Docker Desktop VM
 - Executables: Shell scripts or binaries that Docker Desktop copies on the host when installing the extension
 
-![Overview of the three components of an extension](./images/extensions-architecture.png?w=600h=400)
+![Overview of the three components of an extension](images/extensions-architecture.png?w=600h=400)
 
 An extension doesn't necessarily need to have all these components, but at least one of them depending on the extension features. 
 To configure and run those components, Docker Desktop uses a `metadata.json` file. See the
-[metadata](./metadata) section for more details.
+[metadata](metadata) section for more details.
 
 ## The frontend
 
 The frontend is basically a web application made from HTML, Javascript, and CSS. It can be built with a simple HTML
 file, some vanilla Javascript or any frontend framework, such as React or Vue.js.
 
 When Docker Desktop installs the extension, it extracts the UI folder from the extension image, as defined by the 
-`ui` section in the `metadata.json`. See the [ui metadata section](./metadata.md#ui-section) for more details.
+`ui` section in the `metadata.json`. See the [ui metadata section](metadata.md#ui-section) for more details.
 
 Every time users click on the **Extensions** tab, Docker Desktop initializes the extension's UI as if it was the first time. When they navigate away from the tab, both the UI itself and all the sub-processes started by it (if any) are terminated.
 
@@ -60,7 +62,7 @@ file
 
 Usually, the backend is made of one container that runs within the Docker Desktop VM. Internally, Docker Desktop creates
 a Docker Compose project, creates the container from the `image` option of the `vm` section of the `metadata.json`, and
-attaches it to the Compose project. See the [ui metadata section](./metadata.md#vm-section) for more details.
+attaches it to the Compose project. See the [ui metadata section](metadata.md#vm-section) for more details.
 
 In some cases, a `compose.yml` file can be used instead of an `image`. This is useful when the backend container
 needs more specific options, such as mounting volumes or requesting [capabilities](https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities)
@@ -79,7 +81,7 @@ or named pipe, depending on the operating system. If the backend was listening t
 prevent collision with other applications running on the host or in a container already. Also, some users are
 running Docker Desktop in constrained environments where they can't open ports on their machines.
 
-![Backend and frontend communication](./images/extensions-arch-2.png?w=500h=300)
+![Backend and frontend communication](images/extensions-arch-2.png?w=500h=300)
 
 Finally, the backend can be built with any technology, as long as it can run in a container and listen on a socket.
 
@@ -95,15 +97,15 @@ Shipping those executables with the extension ensure that the CLI tool is always
 the users' machine.
 
 When Docker Desktop installs the extension, it copies the executables on the host as defined by the `host` section in
-the `metadata.json`. See the [ui metadata section](./metadata.md#host-section) for more details.
+the `metadata.json`. See the [ui metadata section](metadata.md#host-section) for more details.
 
-![Executable and frontend communication](./images/extensions-arch-3.png?w=250h=300)
+![Executable and frontend communication](images/extensions-arch-3.png?w=250h=300)
 
 However, since they're executed on the users' machine, they have to be available to the platform they're running on.
 For example, if you want to ship the `kubectl` executable, you need to provide a different version for Windows, Mac,
 and Linux. Multi arch images will also need to include binaries built for the right arch (AMD / ARM)
 
 
-See the [host metadata section](./metadata.md#host-section) for more details.
+See the [host metadata section](metadata.md#host-section) for more details.
 
 Learn how to [invoke host binaries](../guides/invoke-host-binaries.md).