diff --git a/build/index.md b/build/index.md
index bea1fe764e..a00a854eb2 100644
--- a/build/index.md
+++ b/build/index.md
@@ -27,3 +27,60 @@ BuildKit is the backend evolution from the Legacy Builder, it comes with new
 and much improved functionality that can be powerful tools for improving your
 builds' performance or reusability of your Dockerfiles, and it also introduces
 support for complex scenarios.
+
+## Docker Build features
+
+Docker Build is way more than your `docker build` command and is not only about packaging your code, it’s a whole ecosystem of tools and features that support you not only with common workflow tasks but also provides you with support for more complex and advanced scenarios.
+Here’s an overview of all the use cases with which Build can support you:
+
+### Building your images
+
+* **Packaging your software**  
+Bundle and package your code to run anywhere, from your local Docker Desktop, to Docker Engine and Kubernetes on the cloud.  
+To get started with Build, see the [Hello Build](hellobuild.md) page.
+
+* **Choosing a build driver**  
+Run Buildx with different configurations depending on the scenario you are working on, regardless of whether you are using your local machine or a remote compute cluster, all from the comfort of your local working environment.  
+Here’s a quick overview of the drivers and the use cases they support:  
+    * `docker`– use the default built-in builder to get started quickly.
+    * `docker-container` – spin up a dedicated builder in a docker container to unlock more advanced features like advanced caching, and multi-arch images.
+    * `kubernetes`– connect to your Kubernetes cluster to unlock more features and to run your builds at scale.
+    * `remote`–  manually manage your own BuildKit builder and connect directly to it.
+
+* **Optimizing builds with cache management**  
+Improve build performance by using a persistent shared build cache to avoid repeating costly operations such as package installations, downloading files from the internet, or code build steps.
+
+* **Creating build-once, run-anywhere with multi-architecture builds**
+Collaborate across platforms with one build artifact.  
+See [Build multi platform images](buildx/index.md/#build-multi-platform-images).
+
+### Automating your builds
+
+* **Integrating with GitHub**  
+Automate your image builds to run in GitHub actions using the official docker build actions. See:  
+    * [GitHub Action to build and push Docker images with Buildx](https://github.com/docker/build-push-action).
+    * [GitHub Action to extract metadata from Git reference and GitHub events](https://github.com/docker/metadata-action/).
+
+* **Orchestrating builds across complex projects together**  
+Connect your builds together and easily parameterize your images using buildx bake.  
+<!--replace when Bake content is onboarded -->
+See [High-level build options](buildx/index.md/#high-level-build-options)
+
+### Customizing your Builds
+
+* **Select your build output format**  
+Choose from a variety of available output formats, to export any artifact you like from BuildKit, not just docker images.  
+See [Set the export action for the build result](../engine/reference/commandline/buildx_build.md/#output).
+
+* **Managing build secrets**  
+Securely access protected repositories and resources at build time without leaking data into the final build or the cache.
+
+### Extending BuildKit
+
+* **Custom syntax on Dockerfile**  
+Use experimental versions of the Dockerfile frontend, or even just bring your own to BuildKit using the power of custom frontends.  
+See also the [Syntax directive](../engine/reference/builder/#syntax).
+
+* **Configure BuildKit**  
+Take a deep dive into the internal BuildKit configuration to get the most out of your builds.  
+See also [`buildkitd.toml`](https://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md), the configuration file for `buildkitd`.