Fix broken links

Signed-off-by: Natalie Arellano <[email protected]>

Author: Natalie Arellano

config.toml

@@ -111,3 +111,9 @@ featureKatacoda = false
 [[module.mounts]]
     source = 'content/docs/.concepts/extension.md'
     target = 'content/docs/for-platform-operators/concepts/extension.md'
+[[module.mounts]]
+    source = 'content/docs/.concepts/composite-buildpack.md'
+    target = 'content/docs/for-buildpack-authors/concepts/composite-buildpack.md'
+[[module.mounts]]
+    source = 'content/docs/.concepts/composite-buildpack.md'
+    target = 'content/docs/for-platform-operators/concepts/composite-buildpack.md'

content/docs/.concepts/composite-buildpack.md

@@ -0,0 +1,10 @@
++++
+title="What is a composite buildpack?"
+weight=99
++++
+
+A composite buildpack, also sometimes called a "meta-buildpack",
+is a buildpack that does not contain any `./bin/detect` or `./bin/build` binaries,
+but instead references other buildpacks in its `buildpack.toml` via the `[[order]]` array.
+
+This is useful for composing more complex detection strategies.

content/docs/for-buildpack-authors/concepts/buildpack-group.md

@@ -57,4 +57,4 @@ The [Operator's Guide][operator-guide] has more information on creating builders
 [order-resolution]: https://github.com/buildpacks/spec/blob/main/buildpack.md#order-resolution
 [operator-guide]: /docs/for-platform-operators/
 [builder]: /docs/for-platform-operators/concepts/builder/
-[meta-buildpack]: /docs/for-platform-operators/concepts/buildpack/#meta-buildpack
+[meta-buildpack]: /docs/for-platform-operators/concepts/composite-buildpack

content/docs/for-buildpack-authors/how-to/migrate/buildpack-api-0.8-0.9.md

@@ -33,6 +33,6 @@ For older platforms (Platform API version 0.9 and below), arguments in `command`
 
 ### Image extensions are supported (experimental)
 
-Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/dockerfiles) for more information).
+Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/extension) for more information).
 
 For more information, see our tutorial on [authoring an image extension](/docs/for-buildpack-authors/tutorials/basic-extension).

content/docs/for-platform-operators/how-to/migrate/platform-api-0.9-0.10.md

@@ -85,7 +85,7 @@ For processes from older buildpacks, upgrading the platform will not change the
 
 ### Image extensions are supported (experimental)
 
-Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/dockerfiles) for more information). Image extensions output Dockerfiles which are applied by the lifecycle using [kaniko][https://github.com/GoogleContainerTools/kaniko], a tool for building container images in Kubernetes, as a library.
+Platform 0.10 introduces image extensions as experimental components for customizing build and run-time base images (see [here](/docs/for-platform-operators/concepts/extension) for more information). Image extensions output Dockerfiles which are applied by the lifecycle using [kaniko][https://github.com/GoogleContainerTools/kaniko], a tool for building container images in Kubernetes, as a library.
 
 Note: image extensions are not supported for Windows container images.
 

content/docs/reference/spec/buildpack-api.md

@@ -396,4 +396,4 @@ You can read the complete [Buildpack API specification on Github](https://github
 
 [buildpack]: /docs/for-platform-operators/concepts/buildpack/
 [lifecycle]: /docs/for-platform-operators/concepts/lifecycle/
-[meta-buildpack]: /docs/for-platform-operators/concepts/buildpack/#meta-buildpack
+[meta-buildpack]: /docs/for-platform-operators/concepts/composite-buildpack