ENGDOCS-2179 (#20591)

* ENGDOCS-2179

* link fix

* more link fix

* final link fix

.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/extensions/**
-          - content/desktop/extensions-sdk/**
+          - 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/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
+aliases:
-toc_max: 2
+ - /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/extensions/extensions-sdk/_index.md

@@ -4,31 +4,32 @@ description: Overall index for Docker Extensions SDK documentation
 keywords: Docker, Extensions, sdk
 aliases:
  - /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/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,11 +15,11 @@ 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
 
@@ -25,7 +27,7 @@ The frontend is basically a web application made from HTML, Javascript, and CSS.
 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).

content/extensions/extensions-sdk/architecture/metadata.md

@@ -4,6 +4,7 @@ description: Docker extension metadata
 keywords: Docker, extensions, sdk, metadata
 aliases:
  - /desktop/extensions-sdk/extensions/METADATA
+ - /desktop/extensions-sdk/architecture/metadata/
 ---
 
 ## The metadata.json file

content/extensions/extensions-sdk/architecture/security.md

@@ -4,6 +4,7 @@ description: Aspects of the security model of extensions
 keywords: Docker, extensions, sdk, security
 aliases:
  - /desktop/extensions-sdk/guides/security/
+ - /desktop/extensions-sdk/architecture/security/
 ---
 
 ## Extension capabilities

content/extensions/extensions-sdk/build/backend-extension-tutorial.md

@@ -6,6 +6,7 @@ aliases:
  - /desktop/extensions-sdk/tutorials/minimal-backend-extension/
  - /desktop/extensions-sdk/build/minimal-backend-extension/
  - /desktop/extensions-sdk/build/set-up/backend-extension-tutorial/
+ - /desktop/extensions-sdk/build/backend-extension-tutorial/
 ---
 
 Your extension can ship a backend part with which the frontend can interact with. This page provides information on why and how to add a backend.
@@ -20,7 +21,7 @@ Before you start, make sure you have installed the latest version of [Docker Des
 ## Why add a backend?
 
 Thanks to the Docker Extensions SDK, most of the time you should be able to do what you need from the Docker CLI
-directly from [the frontend](./frontend-extension-tutorial.md#use-the-extension-apis-client).
+directly from [the frontend](frontend-extension-tutorial.md#use-the-extension-apis-client).
 
 Nonetheless, there are some cases where you might need to add a backend to your extension. So far, extension
 builders have used the backend to:
@@ -278,7 +279,7 @@ For more information on the `vm` section of the `metadata.json`, see [Metadata](
 
 ## Invoke the extension backend from your frontend
 
-Using the [advanced frontend extension example](./frontend-extension-tutorial.md), we can invoke our extension backend.
+Using the [advanced frontend extension example](frontend-extension-tutorial.md), we can invoke our extension backend.
 
 Use the Docker Desktop Client object and then invoke the `/hello` route from the backend service with `ddClient.
 extension.vm.service.get` that returns the body of the response.

content/extensions/extensions-sdk/build/frontend-extension-tutorial.md

@@ -7,11 +7,12 @@ aliases:
  - /desktop/extensions-sdk/build/set-up/react-extension/
  - /desktop/extensions-sdk/build/set-up/minimal-frontend-using-docker-cli/
  - /desktop/extensions-sdk/build/set-up/frontend-extension-tutorial/
+ - /desktop/extensions-sdk/build/frontend-extension-tutorial/
 ---
 
 To start creating your extension, you first need a directory with files which range from the extension’s source code to the required extension-specific files. This page provides information on how to set up an extension with a more advanced frontend.
 
-Before you start, make sure you have installed the latest version of [Docker Desktop](../../release-notes.md).
+Before you start, make sure you have installed the latest version of [Docker Desktop](/desktop/release-notes.md).
 
 ## Extension folder structure
 
@@ -356,7 +357,7 @@ when you need to debug it.
 
 ## What's next?
 
-- Add a [backend](./backend-extension-tutorial.md) to your extension.
+- Add a [backend](backend-extension-tutorial.md) to your extension.
 - Learn how to [test and debug](../dev/test-debug.md) your extension.
 - Learn how to [setup CI for your extension](../dev/continuous-integration.md).
 - Learn more about extensions [architecture](../architecture/index.md).

content/extensions/extensions-sdk/build/minimal-frontend-extension.md

@@ -5,11 +5,12 @@ keywords: Docker, extensions, sdk, build
 aliases:
  - /desktop/extensions-sdk/tutorials/minimal-frontend-extension/
  - /desktop/extensions-sdk/build/set-up/minimal-frontend-extension/
+ - /desktop/extensions-sdk/build/minimal-frontend-extension/
 ---
 
 To start creating your extension, you first need a directory with files which range from the extension’s source code to the required extension-specific files. This page provides information on how to set up a minimal frontend extension based on plain HTML.
 
-Before you start, make sure you have installed the latest version of [Docker Desktop](../../release-notes.md).
+Before you start, make sure you have installed the latest version of [Docker Desktop](/desktop/release-notes.md).
 
 > Tip
 >
@@ -102,7 +103,7 @@ The left-hand menu displays a new tab with the name of your extension.
 
 ## What's next?
 
-- Build a more [advanced frontend](./frontend-extension-tutorial.md) extension.
+- Build a more [advanced frontend](frontend-extension-tutorial.md) extension.
 - Learn how to [test and debug](../dev/test-debug.md) your extension.
 - Learn how to [setup CI for your extension](../dev/continuous-integration.md).
 - Learn more about extensions [architecture](../architecture/index.md).

content/extensions/extensions-sdk/design/_index.md

@@ -5,6 +5,7 @@ keywords: Docker, extensions, design
 aliases:
  - /desktop/extensions-sdk/design/design-overview/
  - /desktop/extensions-sdk/design/overview/
+ - /desktop/extensions-sdk/design/
 ---
 
 Our Design System is a constantly evolving set of specifications that aim to ensure visual consistency across Docker products, and meet [level AA accessibility standards](https://www.w3.org/WAI/WCAG2AA-Conformance). We've opened parts of it to extension authors, documenting basic styles (color, typography) and components. See: [Docker Extensions Styleguide](https://www.figma.com/file/U7pLWfEf6IQKUHLhdateBI/Docker-Design-Guidelines?node-id=1%3A28771).

content/extensions/extensions-sdk/design/design-guidelines.md

@@ -2,6 +2,8 @@
 title: Design guidelines for Docker extensions
 description: Docker extension design
 keywords: Docker, extensions, design
+aliases: 
+ - /desktop/extensions-sdk/design/design-guidelines/
 ---
 
 At Docker, we aim to build tools that integrate into a user's existing workflows rather than requiring them to adopt new ones. We strongly recommend that you follow these guidelines when creating extensions. We review and approve your Marketplace publication based on these requirements.

content/extensions/extensions-sdk/design/design-principles.md

@@ -2,6 +2,8 @@
 title: Docker design principles
 description: Docker extension design
 keywords: Docker, extensions, design
+aliases: 
+ - /desktop/extensions-sdk/design/design-principles/
 ---
 
 ## Provide actionable guidance

content/extensions/extensions-sdk/design/mui-best-practices.md

@@ -2,6 +2,8 @@
 title: MUI best practices
 description: Guidelines for using MUI to maximise compatibility with Docker Desktop
 keywords: Docker, extensions, mui, theme, theming, material-ui, material
+aliases: 
+ - /desktop/extensions-sdk/design/mui-best-practices/
 ---
 
 This article assumes you're following our recommended practice by using our [Material UI theme](https://www.npmjs.com/package/@docker/docker-mui-theme).

content/extensions/extensions-sdk/dev/api/backend.md

@@ -2,6 +2,8 @@
 title: Extension Backend
 description: Docker extension API
 keywords: Docker, extensions, sdk, API
+aliases: 
+ - /desktop/extensions-sdk/dev/api/backend/
 ---
 
 The `ddClient.extension.vm` object can be used to communicate with the backend defined in the [vm section](../../architecture/metadata.md#vm-section) of the extension metadata.

content/extensions/extensions-sdk/dev/api/dashboard-routes-navigation.md

@@ -2,6 +2,8 @@
 title: Navigation
 description: Docker extension API
 keywords: Docker, extensions, sdk, API
+aliases:
+ - /desktop/extensions-sdk/dev/api/dashboard-routes-navigation/
 ---
 
 `ddClient.desktopUI.navigate` enables navigation to specific screens of Docker Desktop such as the containers tab, the images tab, or a specific container's logs.

content/extensions/extensions-sdk/dev/api/dashboard.md

@@ -2,6 +2,8 @@
 title: Dashboard
 description: Docker extension API
 keywords: Docker, extensions, sdk, API
+aliases:
+ - /desktop/extensions-sdk/dev/api/dashboard/
 ---
 
 ## User notifications

content/extensions/extensions-sdk/dev/api/docker.md

@@ -2,6 +2,8 @@
 title: Docker
 description: Docker extension API
 keywords: Docker, extensions, sdk, API
+aliases: 
+ - /desktop/extensions-sdk/dev/api/docker/
 ---
 
 ## Docker objects

content/extensions/extensions-sdk/dev/api/overview.md

@@ -2,6 +2,8 @@
 title: Extension UI API
 description: Docker extension development overview
 keywords: Docker, extensions, sdk, development
+aliases:
+ - /desktop/extensions-sdk/dev/api/overview/
 ---
 
 The extensions UI runs in a sandboxed environment and doesn't have access to any

content/extensions/extensions-sdk/dev/api/reference/README.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases: 
+ - /desktop/extensions-sdk/dev/api/reference/README/
 ---
 
 # Extensions API Reference

content/extensions/extensions-sdk/dev/api/reference/interfaces/BackendV0.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0/
 ---
 
 # Interface: BackendV0

content/extensions/extensions-sdk/dev/api/reference/interfaces/DesktopUI.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI/
 ---
 
 # Interface: DesktopUI

content/extensions/extensions-sdk/dev/api/reference/interfaces/Dialog.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Dialog/
 ---
 
 # Interface: Dialog

content/extensions/extensions-sdk/dev/api/reference/interfaces/Docker.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Docker/
 ---
 
 # Interface: Docker

content/extensions/extensions-sdk/dev/api/reference/interfaces/DockerCommand.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand/
 ---
 
 # Interface: DockerCommand

content/extensions/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient/
 ---
 
 # Interface: DockerDesktopClient

content/extensions/extensions-sdk/dev/api/reference/interfaces/Exec.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases: 
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Exec/
 ---
 
 # Interface: Exec

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExecOptions.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExecOptions/
 ---
 
 # Interface: ExecOptions

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExecProcess.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess/
 ---
 
 # Interface: ExecProcess

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExecResult.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult/
 ---
 
 # Interface: ExecResult

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExecResultV0.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0/
 ---
 
 # Interface: ExecResultV0

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases: 
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions/
 ---
 
 # Interface: ExecStreamOptions

content/extensions/extensions-sdk/dev/api/reference/interfaces/Extension.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Extension/
 ---
 
 # Interface: Extension

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionCli.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases: 
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli/
 ---
 
 # Interface: ExtensionCli

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionHost.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost/
 ---
 
 # Interface: ExtensionHost

content/extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionVM.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM/
 ---
 
 # Interface: ExtensionVM

content/extensions/extensions-sdk/dev/api/reference/interfaces/Host.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases: 
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Host/
 ---
 
 # Interface: Host

content/extensions/extensions-sdk/dev/api/reference/interfaces/HttpService.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/HttpService/
 ---
 
 # Interface: HttpService

content/extensions/extensions-sdk/dev/api/reference/interfaces/NavigationIntents.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents/
 ---
 
 # Interface: NavigationIntents

content/extensions/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult/
 ---
 
 # Interface: OpenDialogResult

content/extensions/extensions-sdk/dev/api/reference/interfaces/RawExecResult.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult/
 ---
 
 # Interface: RawExecResult

content/extensions/extensions-sdk/dev/api/reference/interfaces/RequestConfig.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig/
 ---
 
 # Interface: RequestConfig

content/extensions/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0/
 ---
 
 # Interface: RequestConfigV0

content/extensions/extensions-sdk/dev/api/reference/interfaces/ServiceError.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/ServiceError/
 ---
 
 # Interface: ServiceError

content/extensions/extensions-sdk/dev/api/reference/interfaces/SpawnOptions.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/SpawnOptions/
 ---
 
 # Interface: SpawnOptions

content/extensions/extensions-sdk/dev/api/reference/interfaces/Toast.md

@@ -1,6 +1,8 @@
 ---
 description: Docker extension API reference
 keywords: Docker, extensions, sdk, API, reference
+aliases:
+ - /desktop/extensions-sdk/dev/api/reference/interfaces/Toast/
 ---
 
 # Interface: Toast

content/extensions/extensions-sdk/dev/continuous-integration.md

@@ -2,6 +2,8 @@
 title: Continuous Integration (CI)
 description: Automatically test and validate your extension.
 keywords: Docker, Extensions, sdk, CI, test, regression
+aliases: 
+ - /desktop/extensions-sdk/dev/continuous-integration/
 ---
 
 In order to help validate your extension and ensure it's functional, the Extension SDK provides tools to help you setup continuous integration for your extension.

content/extensions/extensions-sdk/dev/test-debug.md

@@ -4,6 +4,7 @@ description: Test and debug your extension.
 keywords: Docker, Extensions, sdk, preview, update, Chrome DevTools
 aliases:
  - /desktop/extensions-sdk/build/test-debug/
+ - /desktop/extensions-sdk/dev/test-debug/
 ---
 
 In order to improve the developer experience, Docker Desktop provides a set of tools to help you test and debug your extension.
@@ -74,4 +75,4 @@ $ docker extension rm <name-of-your-extension>
 - Learn more about extensions [architecture](../architecture/index.md).
 - Explore our [design principles](../design/design-principles.md).
 - Take a look at our [UI styling guidelines](../design/index.md).
-- Learn how to [setup CI for your extension](./continuous-integration.md).
+- Learn how to [setup CI for your extension](continuous-integration.md).

content/extensions/extensions-sdk/dev/usage.md

@@ -4,6 +4,7 @@ description: Docker extension CLI
 keywords: Docker, extensions, sdk, CLI
 aliases:
  - /desktop/extensions-sdk/dev/cli/usage/
+ - /desktop/extensions-sdk/dev/usage/
 ---
 
 The Extensions CLI is an extension development tool that is used to manage Docker extensions. Actions include install, list, remove, and validate extensions.

content/extensions/extensions-sdk/extensions/DISTRIBUTION.md

@@ -2,6 +2,8 @@
 title: Package and release your extension
 description: Docker extension disctribution
 keywords: Docker, extensions, sdk, distribution
+aliases: 
+ - /desktop/extensions-sdk/extensions/DISTRIBUTION/
 ---
 
 This page contains additional information on how to package and distribute extensions.

content/extensions/extensions-sdk/extensions/_index.md

@@ -2,6 +2,8 @@
 title: Extension release process
 description: General steps in how to publish an extension
 keywords: Docker, Extensions, sdk, publish
+aliases: 
+ - /desktop/extensions-sdk/extensions/
 ---
 
 This section describes how to make your extension available and more visible, so users can discover it and install it with a single click.
@@ -13,7 +15,7 @@ After you have developed your extension and tested it locally, you are ready to
 Releasing your extension consists of:
 
 - Providing information about your extension: description, screenshots, etc. so users can decide to install your extension
-- [Validating](./validate.md) that the extension is built in the right format and includes the required information
+- [Validating](validate.md) that the extension is built in the right format and includes the required information
 - Making the extension image available on [Docker Hub](https://hub.docker.com/)
 
 See [Package and release your extension](DISTRIBUTION.md) for more details about the release process.

content/extensions/extensions-sdk/extensions/labels.md

@@ -2,6 +2,8 @@
 title: Extension image labels
 description: Docker extension labels
 keywords: Docker, extensions, sdk, labels
+aliases: 
+ - /desktop/extensions-sdk/extensions/labels/
 ---
 
 Extensions use image labels to provide additional information such as a title, description, screenshots, and more.
@@ -10,7 +12,7 @@ This information is then displayed as an overview of the extension, so users can
 
 ![An extension overview, generated from labels](images/marketplace-details.png)
 
-You can define [image labels](../../../reference/dockerfile.md#label) in the extension's `Dockerfile`.
+You can define [image labels](/reference/dockerfile.md#label) in the extension's `Dockerfile`.
 
 > **Important**
 >

content/extensions/extensions-sdk/extensions/multi-arch.md

@@ -2,6 +2,8 @@
 title: Build the extensions for multiple architectures
 description: Step three in creating an extension.
 keywords: Docker, Extensions, sdk, build, multi-arch
+aliases: 
+ - /desktop/extensions-sdk/extensions/multi-arch/
 ---
 
 It is highly recommended that, at a minimum, your extension is supported for the following architectures:
@@ -34,7 +36,7 @@ $ docker buildx build --push --platform=linux/amd64,linux/arm64 --tag=username/m
 ```
 
 You can then check the image manifest to see if the image is available for both
-architectures using the [`docker buildx imagetools` command](../../../reference/cli/docker/buildx/imagetools/_index.md):
+architectures using the [`docker buildx imagetools` command](/reference/cli/docker/buildx/imagetools/_index.md):
 
 ```console
 $ docker buildx imagetools inspect username/my-extension:0.0.1
@@ -57,7 +59,7 @@ Manifests:
 > If you're having trouble pushing the image, make sure you're signed in to Docker Hub. Otherwise, run `docker login` to authenticate.
 { .tip }
 
-For more information, see [Multi-platform images](../../../build/building/multi-platform.md) page.
+For more information, see [Multi-platform images](/build/building/multi-platform.md) page.
 
 ## Adding multi-arch binaries
 

content/extensions/extensions-sdk/extensions/publish.md

@@ -2,6 +2,8 @@
 title: Publish your extension in the Marketplace
 description: Docker extension distribution
 keywords: Docker, extensions, publish
+aliases: 
+ - /desktop/extensions-sdk/extensions/publish/
 ---
 
 ## Submit your extension to the Marketplace
@@ -9,7 +11,7 @@ keywords: Docker, extensions, publish
 Docker Desktop displays published extensions in the Extensions Marketplace on [Docker Desktop](https://open.docker.com/extensions/marketplace) and [Docker Hub](https://hub.docker.com/search?q=&type=extension).
 The Extensions Marketplace is a space where developers can discover extensions to improve their developer experience and propose their own extension to be available for all Desktop users.
 
-Whenever you are [ready to publish](./DISTRIBUTION.md) your extension in the Marketplace, you can [self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+)
+Whenever you are [ready to publish](DISTRIBUTION.md) your extension in the Marketplace, you can [self-publish your extension](https://github.com/docker/extensions-submissions/issues/new?assignees=&labels=&template=1_automatic_review.yaml&title=%5BSubmission%5D%3A+)
 
 > **Note**
 >

content/extensions/extensions-sdk/extensions/share.md

@@ -2,6 +2,8 @@
 title: Share your extension
 description: Share your extension with a share link
 keywords: Docker, extensions, share
+aliases: 
+ - /desktop/extensions-sdk/extensions/share/
 ---
 
 Once your extension image is accessible on Docker Hub, anyone with access to the image can install the extension.

content/extensions/extensions-sdk/extensions/validate.md

@@ -6,6 +6,7 @@ aliases:
  - /desktop/extensions-sdk/extensions/validation/
  - /desktop/extensions-sdk/build/build-install/
  - /desktop/extensions-sdk/dev/cli/build-test-install-extension/
+ - /desktop/extensions-sdk/extensions/validate/
 ---
 
 Validate your extension before you share or publish it. Validating the extension ensures that the extension:

content/extensions/extensions-sdk/guides/invoke-host-binaries.md

@@ -3,6 +3,8 @@ title: Invoke host binaries
 description: Add invocations to host binaries from the frontend with the extension
   SDK.
 keywords: Docker, extensions, sdk, build
+aliases:
+ - /desktop/extensions-sdk/guides/invoke-host-binaries/
 ---
 
 In some cases, your extension may need to invoke some command from the host. For example, you

content/extensions/extensions-sdk/guides/kubernetes.md

@@ -4,6 +4,7 @@ description: How to connect to a Kubernetes cluster from an extension
 keywords: Docker, Extensions, sdk, Kubernetes
 aliases:
  - /desktop/extensions-sdk/dev/kubernetes/
+ - /desktop/extensions-sdk/guides/kubernetes/
 ---
 
 The Extensions SDK does not provide any API methods to directly interact with the Docker Desktop managed Kubernetes cluster or any other created using other tools such as KinD. However, this page provides a way for you to use other SDK APIs to interact indirectly with a Kubernetes cluster from your extension.
@@ -22,7 +23,7 @@ Docker Desktop conveniently provides the user with a local preconfigured `kubeco
 
 If your extension needs to interact with Kubernetes clusters, it is recommended that you include the `kubectl` command line tool as part of your extension. By doing this, users who install your extension get `kubectl` installed on their host.
 
-To find out how to ship the `kubectl` command line tool for multiple platforms as part of your Docker Extension image, see [Build multi-arch extensions](../../../desktop/extensions-sdk/extensions/multi-arch.md#adding-multi-arch-binaries).
+To find out how to ship the `kubectl` command line tool for multiple platforms as part of your Docker Extension image, see [Build multi-arch extensions](../extensions/multi-arch.md#adding-multi-arch-binaries).
 
 ## Examples
 

content/extensions/extensions-sdk/guides/oauth2-flow.md

@@ -4,6 +4,7 @@ description: Docker extension OAuth 2.0 flow
 keywords: Docker, extensions, sdk, OAuth 2.0
 aliases:
  - /desktop/extensions-sdk/dev/oauth2-flow/
+ - /desktop/extensions-sdk/guides/oauth2-flow/
 ---
 
 > **Note**

content/extensions/extensions-sdk/guides/use-docker-socket-from-backend.md

@@ -2,6 +2,8 @@
 title: Use the Docker socket from the extension backend
 description: Docker extension metadata
 keywords: Docker, extensions, sdk, metadata
+aliases: 
+ - /desktop/extensions-sdk/guides/use-docker-socket-from-backend/
 ---
 
 Extensions can invoke Docker commands directly from the frontend with the SDK. 

content/extensions/extensions-sdk/process.md

@@ -2,6 +2,8 @@
 description: Understand the process of creating an extension.
 title: The build and publish process
 keyword: Docker Extensions, sdk, build, create, publish
+aliases:
+ - /desktop/extensions-sdk/process/
 ---
 
 This documentation is structured so that it matches the steps you need to take when creating your extension. 
@@ -38,7 +40,7 @@ For further inspiration, see the other examples in the [samples folder](https://
 
 Docker Desktop displays published extensions in the Extensions Marketplace. The Extensions Marketplace is a curated space where developers can discover extensions to improve their developer experience and upload their own extension to share with the world.
 
-If you want your extension published in the Marketplace, read the [publish documentation](./extensions/publish.md).
+If you want your extension published in the Marketplace, read the [publish documentation](extensions/publish.md).
 
 {{< include "extensions-form.md" >}}
 

content/extensions/extensions-sdk/quickstart.md

@@ -4,17 +4,18 @@ description: Guide on how to build an extension quickly
 keywords: quickstart, extensions
 aliases:
  - desktop/extensions-sdk/tutorials/initialize/
+ - /desktop/extensions-sdk/quickstart/
 ---
 
 Follow this guide to get started with creating a basic Docker extension. The Quickstart guide automatically generates boilerplate files for you.
 
 ## Prerequisites
 
-- [Docker Desktop](../release-notes.md)
+- [Docker Desktop](/desktop/release-notes.md)
 - [NodeJS](https://nodejs.org/)
 - [Go](https://go.dev/dl/)
 
-> Note
+> **Note**
 >
 > NodeJS and Go are only required when you follow the quickstart guide to create an extension. It uses the `docker extension init` command to automatically generate boilerplate files. This command uses a template based on a ReactJS and Go application.
 

content/extensions/marketplace.md

@@ -2,6 +2,8 @@
 description: Extensions
 keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows, Marketplace
 title: Marketplace extensions
+aliases:
+ - /desktop/extensions/marketplace/
 ---
 
 There are two types of extensions available in the Extensions Marketplace:

content/extensions/non-marketplace.md

@@ -2,6 +2,8 @@
 description: Extensions
 keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows,
 title: Non-Marketplace extensions
+aliases:
+ - /desktop/extensions/non-marketplace/
 ---
 
 ## Install an extension not available in the Marketplace

content/extensions/private-marketplace.md

@@ -2,6 +2,8 @@
 description: How to configure and use Docker Extensions' private marketplace
 keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows, Marketplace, private, security
 title: Configure a private marketplace for extensions
+aliases: 
+ - /desktop/extensions/private-marketplace/
 ---
 
 > **Beta**
@@ -14,7 +16,7 @@ Learn how to configure and set up a private marketplace with a curated list of e
 
 It is designed specifically 
 
-Docker Extensions' private marketplace is designed specifically for organizations who don’t give developers root access to their machines. It makes use of [Settings Management](../hardened-desktop/settings-management/_index.md) so administrators have complete control over the private marketplace.
+Docker Extensions' private marketplace is designed specifically for organizations who don’t give developers root access to their machines. It makes use of [Settings Management](/desktop/hardened-desktop/settings-management/_index.md) so administrators have complete control over the private marketplace.
 
 ## Prerequisites
 
@@ -80,7 +82,7 @@ Each setting has a `value` that you can set, including a `locked` field that let
   }
   ```
 
-To find out more information about the `admin-settings.json` file, see [Settings Management](../hardened-desktop/settings-management/_index.md).
+To find out more information about the `admin-settings.json` file, see [Settings Management](/desktop/hardened-desktop/settings-management/_index.md).
 
 ## Step three: List allowed extensions 
 
@@ -137,7 +139,7 @@ $ /opt/docker-desktop/extension-admin generate
 
 This creates an `extension-marketplace` directory and downloads the marketplace metadata for all the allowed extensions.
 
-The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](../extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc. 
+The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc. 
 
 ## Step five: Test the private marketplace setup
 
@@ -194,7 +196,7 @@ These files must be placed on developer's machines. Depending on your operating
 - Windows: `C:\ProgramData\DockerDesktop`
 - Linux: `/usr/share/docker-desktop`
 
-Make sure your developers are signed in to Docker Desktop in order for the private marketplace configuration to take effect. As an administrator, you should [configure a registry.json to enforce Docker Desktop sign-in](../../security/for-admins/configure-sign-in.md).
+Make sure your developers are signed in to Docker Desktop in order for the private marketplace configuration to take effect. As an administrator, you should [configure a registry.json to enforce Docker Desktop sign-in](/security/for-admins/configure-sign-in.md).
 
 ## Feedback
 

content/extensions/settings-feedback.md

@@ -2,6 +2,8 @@
 description: Extensions
 keywords: Docker Extensions, Docker Desktop, Linux, Mac, Windows, feedback
 title: Settings and feedback for Docker Extensions
+aliases:
+ - /desktop/extensions/settings-feedback/
 ---
 
 ## Settings
@@ -17,12 +19,12 @@ Docker Extensions is switched on by default. To change your settings:
 
 >**Note**
 >
-> If you are an [organization owner](../../admin/organization/manage-a-team.md#organization-owner), you can turn off extensions for your users. Open the `settings.json` file, and set `"extensionsEnabled"` to `false`. 
+> If you are an [organization owner](/admin/organization/manage-a-team.md#organization-owner), you can turn off extensions for your users. Open the `settings.json` file, and set `"extensionsEnabled"` to `false`. 
 > The `settings.json` file is located at:
 >   - `~/Library/Group Containers/group.com.docker/settings.json` on Mac
 >   - `C:\Users\[USERNAME]\AppData\Roaming\Docker\settings.json` on Windows
 >
-> This can also be done with [Hardened Docker Desktop](../hardened-desktop/index.md)
+> This can also be done with [Hardened Docker Desktop](/desktop/hardened-desktop/index.md)
 
 ### Turn on or turn off extensions not available in the Marketplace
 

content/manuals.md

@@ -24,7 +24,7 @@ development:
 - title: Docker Extensions
   description: Customize your Docker Desktop workflow.
   icon: extension
-  link: /desktop/extensions/
+  link: /extensions/
 services:
 - title: Docker Hub
   description: Discover, share, and integrate container images

data/toc.yaml

@@ -983,51 +983,55 @@ Reference:
         path: /docker-hub/api/deprecated/
   - sectiontitle: Docker Extension SDK API
     section:
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/DesktopUI/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/DesktopUI/
         title: DesktopUI
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Dialog/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Dialog/
         title: Dialog
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Docker/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Docker/
         title: Docker
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/DockerCommand/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/DockerCommand/
         title: DockerCommand
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/DockerDesktopClient/
         title: DockerDesktopClient
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Exec/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Exec/
         title: Exec
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExecProcess/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExecProcess/
         title: ExecProcess
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExecResult/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExecResult/
         title: ExecResult
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExecStreamOptions/
         title: ExecStreamOptions
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Extension/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Extension/
         title: Extension
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionCli/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionCli/
         title: ExtensionCli
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionHost/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionHost/
         title: ExtensionHost
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExtensionVM/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExtensionVM/
         title: ExtensionVM
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Host/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Host/
         title: Host
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/HttpService/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/HttpService/
         title: HttpService
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/NavigationIntents/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/NavigationIntents/
         title: NavigationIntents
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/OpenDialogResult/
         title: OpenDialogResult
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/RawExecResult/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/RawExecResult/
         title: RawExecResult
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfig/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/RequestConfig/
         title: RequestConfig
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/RequestConfigV0/
         title: RequestConfigV0
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/Toast/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ServiceError/
+        title: ServiceError
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ServiceError/
+        title: SpawnOptions
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/Toast/
         title: Toast
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/ExecResultV0/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/ExecResultV0/
         title: ExecResultV0
-      - path: /desktop/extensions-sdk/dev/api/reference/interfaces/BackendV0/
+      - path: /extensions/extensions-sdk/dev/api/reference/interfaces/BackendV0/
         title: BackendV0
 - sectiontitle: Compose file reference
   section:
@@ -1346,100 +1350,100 @@ Manuals:
 
 - sectiontitle: Docker Extensions
   section:
-    - path: /desktop/extensions/
+    - path: /extensions/
       title: Overview
     - sectiontitle: Extensions on Docker Desktop
       section:
-        - path: /desktop/extensions/marketplace/
+        - path: /extensions/marketplace/
           title: Manage Marketplace extensions
-        - path: /desktop/extensions/non-marketplace/
+        - path: /extensions/non-marketplace/
           title: Manage non-Marketplace extensions
-        - path: /desktop/extensions/settings-feedback/
+        - path: /extensions/settings-feedback/
           title: Change settings and give feedback
-        - path: /desktop/extensions/private-marketplace/
+        - path: /extensions/private-marketplace/
           title: Configure a private Marketplace (Beta)
     - sectiontitle: Extensions SDK
       section:
-        - path: /desktop/extensions-sdk/
+        - path: /extensions/extensions-sdk/
           title: Overview
-        - path: /desktop/extensions-sdk/process/
+        - path: /extensions/extensions-sdk/process/
           title: The build and publish process
-        - path: /desktop/extensions-sdk/quickstart/
+        - path: /extensions/extensions-sdk/quickstart/
           title: Quickstart
         - sectiontitle: "Part one: Build"
           section:
             - title: Create a simple extension
-              path: /desktop/extensions-sdk/build/minimal-frontend-extension/
+              path: /extensions/extensions-sdk/build/minimal-frontend-extension/
             - title: Create an advanced frontend extension
-              path: /desktop/extensions-sdk/build/frontend-extension-tutorial/
+              path: /extensions/extensions-sdk/build/frontend-extension-tutorial/
             - title: Add a backend to your extension
-              path: /desktop/extensions-sdk/build/backend-extension-tutorial/
+              path: /extensions/extensions-sdk/build/backend-extension-tutorial/
         - sectiontitle: "Part two: Publish"
           section:
             - title: Overview
-              path: /desktop/extensions-sdk/extensions/
+              path: /extensions/extensions-sdk/extensions/
             - title: Labels
-              path: /desktop/extensions-sdk/extensions/labels/
+              path: /extensions/extensions-sdk/extensions/labels/
             - title: Validate
-              path: /desktop/extensions-sdk/extensions/validate/
+              path: /extensions/extensions-sdk/extensions/validate/
             - title: Package and release your extension
-              path: /desktop/extensions-sdk/extensions/DISTRIBUTION/
+              path: /extensions/extensions-sdk/extensions/DISTRIBUTION/
             - title: Generate a share link
-              path: /desktop/extensions-sdk/extensions/share/
+              path: /extensions/extensions-sdk/extensions/share/
             - title: Publish in the Marketplace
-              path: /desktop/extensions-sdk/extensions/publish/
+              path: /extensions/extensions-sdk/extensions/publish/
             - title: Build multi-arch extensions
-              path: /desktop/extensions-sdk/extensions/multi-arch/
+              path: /extensions/extensions-sdk/extensions/multi-arch/
         - sectiontitle: "Architecture"
           section:
             - title: Overview
-              path: /desktop/extensions-sdk/architecture/
+              path: /extensions/extensions-sdk/architecture/
             - title: Metadata
-              path: /desktop/extensions-sdk/architecture/metadata/
+              path: /extensions/extensions-sdk/architecture/metadata/
             - title: Security
-              path: /desktop/extensions-sdk/architecture/security/
+              path: /extensions/extensions-sdk/architecture/security/
         - sectiontitle: "Design and UI styling"
           section:
              - title: UI styling guidelines
-               path: /desktop/extensions-sdk/design/
+               path: /extensions/extensions-sdk/design/
              - title: Guidelines
-               path: /desktop/extensions-sdk/design/design-guidelines/
+               path: /extensions/extensions-sdk/design/design-guidelines/
              - title: Docker design principles
-               path: /desktop/extensions-sdk/design/design-principles/
+               path: /extensions/extensions-sdk/design/design-principles/
              - title: MUI best practices
-               path: /desktop/extensions-sdk/design/mui-best-practices/
+               path: /extensions/extensions-sdk/design/mui-best-practices/
         - sectiontitle: "Developer Guides"
           section:
             - title: Invoke host binaries
-              path: /desktop/extensions-sdk/guides/invoke-host-binaries/
+              path: /extensions/extensions-sdk/guides/invoke-host-binaries/
             - title: Use the Docker socket from the extension backend
-              path: /desktop/extensions-sdk/guides/use-docker-socket-from-backend/
+              path: /extensions/extensions-sdk/guides/use-docker-socket-from-backend/
             - title: Interacting with Kubernetes
-              path: /desktop/extensions-sdk/guides/kubernetes/
+              path: /extensions/extensions-sdk/guides/kubernetes/
             - title: Authentication
-              path: /desktop/extensions-sdk/guides/oauth2-flow/
+              path: /extensions/extensions-sdk/guides/oauth2-flow/
         - sectiontitle: Developer SDK tools
           section:
             - title: "Test and debug"
-              path: /desktop/extensions-sdk/dev/test-debug/
+              path: /extensions/extensions-sdk/dev/test-debug/
             - title: "Continuous integration"
-              path: /desktop/extensions-sdk/dev/continuous-integration/
+              path: /extensions/extensions-sdk/dev/continuous-integration/
             - title: CLI reference
-              path: /desktop/extensions-sdk/dev/usage/
+              path: /extensions/extensions-sdk/dev/usage/
             - sectiontitle: Extension APIs
               section:
                 - title: Overview
-                  path: /desktop/extensions-sdk/dev/api/overview/
+                  path: /extensions/extensions-sdk/dev/api/overview/
                 - title: Extension Backend
-                  path: /desktop/extensions-sdk/dev/api/backend/
+                  path: /extensions/extensions-sdk/dev/api/backend/
                 - title: Docker
-                  path: /desktop/extensions-sdk/dev/api/docker/
+                  path: /extensions/extensions-sdk/dev/api/docker/
                 - title: Dashboard
-                  path: /desktop/extensions-sdk/dev/api/dashboard/
+                  path: /extensions/extensions-sdk/dev/api/dashboard/
                 - title: Navigation
-                  path: /desktop/extensions-sdk/dev/api/dashboard-routes-navigation/
+                  path: /extensions/extensions-sdk/dev/api/dashboard-routes-navigation/
                 - title: API Reference
-                  path: /desktop/extensions-sdk/dev/api/reference/README/
+                  path: /extensions/extensions-sdk/dev/api/reference/README/
 
 - sectiontitle: Docker Scout
   section: