build: restructure manuals section

content/build-cloud/optimization.md

@@ -34,7 +34,7 @@ For more information on how to optimize your builds, see
 
 ### Dockerignore files
 
-Using a [`.dockerignore` file](/build/building/context/#dockerignore-files),
+Using a [`.dockerignore` file](/build/concepts/context.md#dockerignore-files),
 you can be explicit about which local files you don’t want to include in the
 build context. Files caught by the glob patterns you specify in your
 ignore-file aren't transferred to the remote builder.

content/build/_index.md

@@ -7,37 +7,37 @@ grid:
   description: 'Build and package your application to run it anywhere: locally or
     in the cloud.'
   icon: inventory_2
-  link: /build/building/packaging
+  link: /build/concepts/overview/
 - title: Multi-stage builds
   description: Keep your images small and secure with minimal dependencies.
   icon: stairs
-  link: /build/building/multi-stage
+  link: /build/building/multi-stage/
 - title: Multi-platform images
   description: Build, push, pull, and run images seamlessly on different computer
     architectures.
   icon: content_copy
   link: /build/building/multi-platform/
-- title: Architecture
+- title: BuildKit
   description: Explore BuildKit, the open source build engine.
   icon: construction
   link: /build/buildkit/
 - title: Build drivers
   description: Configure where and how you run your builds.
   icon: engineering
-  link: /build/drivers/
+  link: /build/builders/drivers/
 - title: Exporters
   description: Export any artifact you like, not just Docker images.
   icon: output
-  link: /build/exporters
+  link: /build/exporters/
 - title: Build caching
   description: Avoid unnecessary repetitions of costly operations, such as package
     installs.
   icon: cycle
-  link: /build/cache
+  link: /build/cache/
 - title: Bake
   description: Orchestrate your builds with Bake.
   icon: cake
-  link: /build/bake
+  link: /build/bake/
 aliases:
 - /buildx/working-with-buildx/
 - /develop/develop-images/build_enhancements/

content/build/builders/_index.md

@@ -23,9 +23,9 @@ Docker context, your `default` builder refers to the new Docker context.
 
 ## Build drivers
 
-Buildx implements a concept of [build drivers](../drivers/index.md) to refer to
+Buildx implements a concept of [build drivers](drivers/_index.md) to refer to
 different builder configurations. The default builder created by the daemon
-uses the [`docker` driver](../drivers/docker.md).
+uses the [`docker` driver](drivers/docker.md).
 
 Buildx supports the following build drivers:
 
@@ -69,4 +69,4 @@ selected when you invoke builds.
 - For information about how to interact with and manage builders,
   see [Manage builders](./manage.md)
 - To learn about different types of builders,
-  see [Build drivers](../drivers/index.md)
+  see [Build drivers](drivers/index.md)

content/build/drivers/_index.md → content/build/builders/drivers/_index.md

@@ -6,6 +6,7 @@ aliases:
   - /build/buildx/drivers/
   - /build/building/drivers/
   - /build/buildx/multiple-builders/
+  - /build/drivers/
 ---
 
 Build drivers are configurations for how and where the BuildKit backend runs.
@@ -33,7 +34,7 @@ The following table outlines some differences between drivers.
 | **BuildKit configuration**   |             |         ✅         |      ✅      | Managed externally |
 
 \* _The `docker` driver doesn't support all cache export options.
-See [Cache storage backends](../cache/backends/_index.md) for more information._
+See [Cache storage backends](/build/cache/backends/_index.md) for more information._
 
 ## Loading to local image store
 
@@ -42,26 +43,26 @@ aren't automatically loaded into the local image store. If you don't specify an
 output, the build result is exported to the build cache only.
 
 To build an image using a non-default driver and load it to the image store,
-use the `--load` flag with the build command:
-
-```console
-$ docker buildx build --load -t <image> --builder=container .
-...
- => exporting to oci image format                                                                                                      7.7s
- => => exporting layers                                                                                                                4.9s
- => => exporting manifest sha256:4e4ca161fa338be2c303445411900ebbc5fc086153a0b846ac12996960b479d3                                      0.0s
- => => exporting config sha256:adf3eec768a14b6e183a1010cb96d91155a82fd722a1091440c88f3747f1f53f                                        0.0s
- => => sending tarball                                                                                                                 2.8s
- => importing to docker
-```
-
-With this option, the image is available in the image store after the build finishes:
-
-```console
-$ docker image ls
-REPOSITORY                       TAG               IMAGE ID       CREATED             SIZE
-<image>                          latest            adf3eec768a1   2 minutes ago       197MB
-```
+   use the `--load` flag with the build command:
+
+   ```console
+   $ docker buildx build --load -t <image> --builder=container .
+   ...
+   => exporting to oci image format                                                                                                      7.7s
+   => => exporting layers                                                                                                                4.9s
+   => => exporting manifest sha256:4e4ca161fa338be2c303445411900ebbc5fc086153a0b846ac12996960b479d3                                      0.0s
+   => => exporting config sha256:adf3eec768a14b6e183a1010cb96d91155a82fd722a1091440c88f3747f1f53f                                        0.0s
+   => => sending tarball                                                                                                                 2.8s
+   => importing to docker
+   ```
+
+   With this option, the image is available in the image store after the build finishes:
+
+   ```console
+   $ docker image ls
+   REPOSITORY                       TAG               IMAGE ID       CREATED             SIZE
+   <image>                          latest            adf3eec768a1   2 minutes ago       197MB
+   ```
 
 ### Load by default
 
@@ -84,7 +85,7 @@ flag.
 
 Read about each driver:
 
-- [Docker driver](./docker.md)
-- [Docker container driver](./docker-container.md)
-- [Kubernetes driver](./kubernetes.md)
+  - [Docker driver](./docker.md)
+  - [Docker container driver](./docker-container.md)
+  - [Kubernetes driver](./kubernetes.md)
 - [Remote driver](./remote.md)

content/build/drivers/docker-container.md → content/build/builders/drivers/docker-container.md

@@ -5,6 +5,7 @@ keywords: build, buildx, driver, builder, docker-container
 aliases:
   - /build/buildx/drivers/docker-container/
   - /build/building/drivers/docker-container/
+  - /build/drivers/docker-container/
 ---
 
 The Docker container driver allows creation of a managed and customizable
@@ -15,7 +16,7 @@ Docker driver. For example:
 
 - Specify custom BuildKit versions to use.
 - Build multi-arch images, see [QEMU](#qemu)
-- Advanced options for [cache import and export](../cache/backends/index.md)
+- Advanced options for [cache import and export](/build/cache/backends/_index.md)
 
 ## Synopsis
 
@@ -132,14 +133,14 @@ $ docker buildx build \
 You can customize the network that the builder container uses. This is useful
 if you need to use a specific network for your builds.
 
-For example, let's [create a network](../../reference/cli/docker/network/create.md)
+For example, let's [create a network](/reference/cli/docker/network/create.md)
 named `foonet`:
 
 ```console
 $ docker network create foonet
 ```
 
-Now create a [`docker-container` builder](../../reference/cli/docker/buildx/create.md)
+Now create a [`docker-container` builder](/reference/cli/docker/buildx/create.md)
 that will use this network:
 
 ```console
@@ -149,13 +150,13 @@ $ docker buildx create --use \
   --driver-opt "network=foonet"
 ```
 
-Boot and [inspect `mybuilder`](../../reference/cli/docker/buildx/inspect.md):
+Boot and [inspect `mybuilder`](/reference/cli/docker/buildx/inspect.md):
 
 ```console
 $ docker buildx inspect --bootstrap
 ```
 
-[Inspect the builder container](../../reference/cli/docker/inspect.md)
+[Inspect the builder container](/reference/cli/docker/inspect.md)
 and see what network is being used:
 
 ```console
@@ -166,4 +167,4 @@ map[foonet:0xc00018c0c0]
 ## Further reading
 
 For more information on the Docker container driver, see the
-[buildx reference](../../reference/cli/docker/buildx/create.md#driver).
+[buildx reference](/reference/cli/docker/buildx/create.md#driver).

content/build/drivers/docker.md → content/build/builders/drivers/docker.md

@@ -7,10 +7,11 @@ keywords: build, buildx, driver, builder, docker
 aliases:
   - /build/buildx/drivers/docker/
   - /build/building/drivers/docker/
+  - /build/drivers/docker/
 ---
 
 The Buildx Docker driver is the default driver. It uses the BuildKit server
-components built directly into the Docker engine. The Docker driver requires no
+components built directly into the Docker Engine. The Docker driver requires no
 configuration.
 
 Unlike the other drivers, builders using the Docker driver can't be manually
@@ -28,12 +29,12 @@ docker buildx build .
 
 It's not possible to configure which BuildKit version to use, or to pass any
 additional BuildKit parameters to a builder using the Docker driver. The
-BuildKit version and parameters are preset by the Docker engine internally.
+BuildKit version and parameters are preset by the Docker Engine internally.
 
 If you need additional configuration and flexibility, consider using the
 [Docker container driver](./docker-container.md).
 
 ## Further reading
 
 For more information on the Docker driver, see the
-[buildx reference](../../reference/cli/docker/buildx/create.md#driver).
+[buildx reference](/reference/cli/docker/buildx/create.md#driver).

content/build/drivers/kubernetes.md → content/build/builders/drivers/kubernetes.md

@@ -7,6 +7,7 @@ keywords: build, buildx, driver, builder, kubernetes
 aliases:
   - /build/buildx/drivers/kubernetes/
   - /build/building/drivers/kubernetes/
+  - /build/drivers/kubernetes/
 ---
 
 The Kubernetes driver lets you connect your local development or CI
@@ -108,7 +109,7 @@ replicas. `sticky` (the default) attempts to connect the same build performed
 multiple times to the same node each time, ensuring better use of local cache.
 
 For more information on scalability, see the options for
-[`docker buildx create`](../../reference/cli/docker/buildx/create.md#driver-opt).
+[`docker buildx create`](/reference/cli/docker/buildx/create.md#driver-opt).
 
 ## Node assignment
 
@@ -143,7 +144,7 @@ $ docker buildx create \
 ## Multi-platform builds
 
 The Kubernetes driver has support for creating
-[multi-platform images](../building/multi-platform.md),
+[multi-platform images](/build/building/multi-platform.md),
 either using QEMU or by leveraging the native architecture of nodes.
 
 ### QEMU
@@ -343,9 +344,9 @@ Prerequisites:
      --push .
    ```
 
-That's it! You've now built an image from a Kubernetes pod, using Buildx!
+That's it: you've now built an image from a Kubernetes pod, using Buildx.
 
 ## Further reading
 
 For more information on the Kubernetes driver, see the
-[buildx reference](../../reference/cli/docker/buildx/create.md#driver).
+[buildx reference](/reference/cli/docker/buildx/create.md#driver).

content/build/drivers/remote.md → content/build/builders/drivers/remote.md

@@ -7,6 +7,7 @@ keywords: build, buildx, driver, builder, remote
 aliases:
   - /build/buildx/drivers/remote/
   - /build/building/drivers/remote/
+  - /build/drivers/remote/
 ---
 
 The Buildx remote driver allows for more complex custom build workloads,