docs: remove frontmatter section

Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>

docs/guides/bake/build-contexts.md

@@ -1,7 +1,4 @@
----
+# Defining additional build contexts and linking targets
-title: "Defining additional build contexts and linking targets"
-keywords: build, buildx, bake, buildkit, hcl
----
 
 In addition to the main `context` key that defines the build context each target
 can also define additional named contexts with a map defined with key `contexts`.

docs/guides/bake/compose-file.md

@@ -1,7 +1,4 @@
----
+# Building from Compose file
-title: "Building from Compose file"
-keywords: build, buildx, bake, buildkit, compose
----
 
 ## Specification
 

docs/guides/bake/configuring-build.md

@@ -1,7 +1,4 @@
----
+# Configuring builds
-title: "Configuring builds"
-keywords: build, buildx, bake, buildkit, hcl, json
----
 
 Bake supports loading build definition from files, but sometimes you need even
 more flexibility to configure this definition.

docs/guides/bake/file-definition.md

@@ -1,7 +1,4 @@
----
+# Bake file definition
-title: "Bake file definition"
-keywords: build, buildx, bake, buildkit, hcl, json, compose
----
 
 `buildx bake` supports HCL, JSON and Compose file format for defining build
 [groups](#group), [targets](#target) as well as [variables](#variable) and

docs/guides/bake/hcl-funcs.md

@@ -1,7 +1,4 @@
----
+# User defined HCL functions
-title: "User defined HCL functions"
-keywords: build, buildx, bake, buildkit, hcl
----
 
 ## Using interpolation to tag an image with the git sha
 

docs/guides/bake/index.md

@@ -1,7 +1,4 @@
----
+# High-level build options with Bake
-title: "High-level build options with Bake"
-keywords: build, buildx, bake, buildkit, hcl, json, compose
----
 
 > This command is experimental.
 >

docs/guides/cni-networking.md

@@ -1,8 +1,4 @@
----
+# CNI networking
-title: "CNI networking"
-description: "Enhance your builder with CNI networking"
-keywords: build, buildx, buildkit, cni, network
----
 
 It can be useful to use a bridge network for your builder if for example you
 encounter a network port contention during multiple builds. If you're using

docs/guides/color-output.md

@@ -1,8 +1,4 @@
----
+# Color output controls
-title: "Color output controls"
-description: "Modifying colors of progress output"
-keywords: build, buildx, buildkit
----
 
 Buildx has support for modifying the colors that are used to output information
 to the terminal. You can set the environment variable `BUILDKIT_COLORS` to

docs/guides/custom-network.md

@@ -1,8 +1,4 @@
----
+# Using a custom network
-title: "Using a custom network"
-description: "Create and use a custom network for your build"
-keywords: build, buildx, buildkit, network
----
 
 [Create a network](https://docs.docker.com/engine/reference/commandline/network_create/)
 named `foonet`:

docs/guides/custom-registry-config.md

@@ -1,8 +1,4 @@
----
+# Using a custom registry configuration
-title: "Using a custom registry configuration"
-description: "Set registry configuration in your builder"
-keywords: build, buildx, buildkit, registry
----
 
 If you [create a `docker-container` or `kubernetes` builder](https://docs.docker.com/engine/reference/commandline/buildx_create/) and
 have specified certificates for registries in the [BuildKit daemon configuration](https://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md),

docs/guides/kubernetes-builder.md

@@ -1,8 +1,4 @@
----
+# Kubernetes builder
-title: "Kubernetes builder"
-description: "Connect buildx to a kubernetes cluster"
-keywords: build, buildx, buildkit
----
 
 The buildx kubernetes driver allows connecting your local development or ci
 environments to your kubernetes cluster to allow access to more powerful

docs/guides/opentelemetry.md

@@ -1,8 +1,4 @@
----
+# OpenTelemetry support
-title: "OpenTelemetry support"
-description: "OpenTelemetry support for your builder"
-keywords: build, buildx, buildkit, opentelemetry, tracing
----
 
 To capture the trace to [Jaeger](https://github.com/jaegertracing/jaeger), set
 `JAEGER_TRACE` environment variable to the collection address using a `driver-opt`.

docs/guides/registry-mirror.md

@@ -1,8 +1,4 @@
----
+# Registry mirror
-title: "Registry mirror"
-description: "Using a registry mirror in your build"
-keywords: build, buildx, buildkit, registry
----
 
 You can define a registry mirror to use for your builds by providing a [BuildKit daemon configuration](https://github.com/moby/buildkit/blob/master/docs/buildkitd.toml.md)
 while creating a builder with the [`--config` flags](https://docs.docker.com/engine/reference/commandline/buildx_create/#config).

docs/guides/remote-builder.md

@@ -1,8 +1,4 @@
----
+# Remote builder
-title: "Remote builder"
-description: "Connect buildx to an external buildkitd instance"
-keywords: build, buildx, buildkit
----
 
 The buildx remote driver allows for more complex custom build workloads that
 allow users to connect to external buildkit instances. This is useful for

docs/guides/resource-limiting.md

@@ -1,8 +1,4 @@
----
+# Resource limiting
-title: "Resource limiting"
-description: "Max parallelism and limit on TCP connection in your build"
-keywords: build, buildx, buildkit, compute, network
----
 
 ## Max parallelism