Fix broken links

Natalie Arellano · Natalie Arellano · commit 0aa235037a43 · 2024-02-14T14:35:54.000-05:00
Signed-off-by: Natalie Arellano &lt;narellano@vmware.com&gt;
diff --git a/content/docs/_index.md b/content/docs/_index.md
@@ -13,7 +13,7 @@ summary="Get started with Cloud Native Buildpacks."
 ## Tutorials
 
 * [An App’s Brief Journey from Source to Image](/docs/app-journey/) - An easy-to-follow introduction to Cloud Native Buildpacks using `pack`, a command line tool for Cloud Native Buildpacks.
-* [Creating a Cloud Native Buildpack](/docs/buildpack-author-guide/create-buildpack) - Tutorial walking through the creation of a simple Ruby buildpack.
+* [Creating a Cloud Native Buildpack](/docs/for-buildpack-authors/tutorials/basic-buildpack) - Tutorial walking through the creation of a simple Ruby buildpack.
 
 ## Going deeper
 
diff --git a/content/docs/app-journey.md b/content/docs/app-journey.md
@@ -99,7 +99,7 @@ deploying your new image to your favorite cloud!
 
 Windows image builds are now supported!
 
-<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-windows" class="button bg-blue">Windows build guide</a>
+<a href="/docs/for-app-developers/how-to/special-cases/build-for-windows" class="button bg-blue">Windows build guide</a>
 
 [builder]: /docs/for-platform-operators/concepts/builder/
 [buildpack]: /docs/for-platform-operators/concepts/buildpack/
diff --git a/content/docs/for-app-developers/how-to/build-inputs/buildpacks.md b/content/docs/for-app-developers/how-to/build-inputs/buildpacks.md
@@ -110,5 +110,5 @@ A buildpack located in a CNB Registry
 <small><sup>†</sup> Directory buildpacks are not currently supported on Windows.</small><br />
 <small><sup>‡</sup> Version may be omitted if there is only one buildpack in the builder matching the `id`.</small>
 
-[project-toml]: /docs/for-app-developers/how-to/configure-build-inputs/project-toml/
+[project-toml]: /docs/for-app-developers/how-to/build-inputs/project-toml/
 [samples]: https://github.com/buildpacks/samples
diff --git a/content/docs/for-app-developers/how-to/build-inputs/inline-buildpacks.md b/content/docs/for-app-developers/how-to/build-inputs/inline-buildpacks.md
@@ -54,6 +54,6 @@ EOF
 ### Further Reading
 For more about project descriptors, look at the [schema][descriptor-schema], as well as the [specification][spec].
 
-[project-toml]: /docs/for-app-developers/how-to/configure-build-inputs/project-toml/
+[project-toml]: /docs/for-app-developers/how-to/build-inputs/project-toml/
 [descriptor-schema]: /docs/reference/project-descriptor/
 [spec]: https://github.com/buildpacks/spec/blob/main/extensions/project-descriptor.md
diff --git a/content/docs/for-app-developers/how-to/build-inputs/project-toml.md b/content/docs/for-app-developers/how-to/build-inputs/project-toml.md
@@ -106,8 +106,8 @@ docker run sample-app
 ### Further Reading
 For more about project descriptors, look at the [schema][descriptor-schema], as well as the [specification][spec].
 
-[specify-buildpacks]: /docs/for-app-developers/how-to/configure-build-inputs/buildpacks
-[descriptor-envs]: /docs/for-app-developers/how-to/configure-build-inputs/build-time-environment/#using-project-descriptor
+[specify-buildpacks]: /docs/for-app-developers/how-to/build-inputs/buildpacks
+[descriptor-envs]: /docs/for-app-developers/how-to/build-inputs/build-time-environment/#using-project-descriptor
 [descriptor-schema]: /docs/reference/project-descriptor/
 [samples]: https://github.com/buildpacks/samples
 [spec]: https://github.com/buildpacks/spec/blob/main/extensions/project-descriptor.md
diff --git a/content/docs/for-app-developers/how-to/build-outputs/download-sbom.md b/content/docs/for-app-developers/how-to/build-outputs/download-sbom.md
@@ -35,11 +35,3 @@ layers
               │   └── sbom.syft.json
               └── sbom.syft.json
 ```
-
-## Adding Bill of Materials
-
-[`pack`](https://github.com/buildpacks/pack), [`kpack`](https://github.com/pivotal/kpack) and [tekton](https://tekton.dev/) users will find that images created using these tools contain an SBoM.
-
-Developers writing a new buildpack or updating an existing buildpack should use the [Adding bill of materials][adding-bill-of-materials] tutorial to incorporate a `Bill-of-Materials` in their buildpack.
-
-[adding-bill-of-materials]: /docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials/
diff --git a/content/docs/for-app-developers/how-to/special-cases/_index.md b/content/docs/for-app-developers/how-to/special-cases/_index.md
diff --git a/content/docs/for-app-developers/how-to/special-cases/build-for-arm.md b/content/docs/for-app-developers/how-to/special-cases/build-for-arm.md
diff --git a/content/docs/for-app-developers/how-to/special-cases/build-for-windows.md b/content/docs/for-app-developers/how-to/special-cases/build-for-windows.md
diff --git a/content/docs/for-app-developers/how-to/special-cases/build-on-podman.md b/content/docs/for-app-developers/how-to/special-cases/build-on-podman.md
diff --git a/content/docs/for-app-developers/how-to/special-cases/use-http-proxy.md b/content/docs/for-app-developers/how-to/special-cases/use-http-proxy.md
diff --git a/content/docs/for-app-developers/tutorials/basic-app/build.md b/content/docs/for-app-developers/tutorials/basic-app/build.md
@@ -67,21 +67,21 @@ The app should now be running and accessible via [localhost:8080](http://localho
 Linux ARM image builds are now supported!
 
 <!--+- if false+-->
-<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-arm" class="button bg-blue">Linux ARM build guide</a>
+<a href="/docs/for-app-developers/how-to/special-cases/build-for-arm" class="button bg-blue">Linux ARM build guide</a>
 <!--+end+-->
 
 <!--+ `
-Check out the [Linux ARM build guide](https://buildpacks.io//docs/for-app-developers/how-to/configure-build-environment/build-for-arm).
+Check out the [Linux ARM build guide](https://buildpacks.io//docs/for-app-developers/how-to/special-cases/build-for-arm).
 ` +-->
 ## What about Windows apps?
 
 Windows image builds are now supported!
 
 <!--+- if false+-->
-<a href="/docs/for-app-developers/how-to/configure-build-environment/build-for-windows" class="button bg-blue">Windows build guide</a>
+<a href="/docs/for-app-developers/how-to/special-cases/build-for-windows" class="button bg-blue">Windows build guide</a>
 <!--+end+-->
 <!--+ `
-Check out the [Windows build guide](https://buildpacks.io/docs/for-app-developers/how-to/configure-build-environment/build-for-windows/).
+Check out the [Windows build guide](https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-for-windows/).
 ` +-->
 
 [build]: /docs/for-app-developers/concepts/buildpacks-operations/build
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/01_setup-local-environment.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/01_setup-local-environment.md
@@ -96,5 +96,5 @@ Server: Docker Engine - Community
 <!--+ if false +-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/building-blocks-cnb" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb" class="button bg-pink">Next Step</a>
 <!--+ end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb.md
@@ -134,7 +134,7 @@ ERROR: failed to detect: buildpack(s) failed with err
 <!--+ if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/detection" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/03_detection" class="button bg-pink">Next Step</a>
 
 [builder]: /docs/for-platform-operators/concepts/builder
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/03_detection.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/03_detection.md
@@ -55,5 +55,5 @@ You will also notice that `RESTORING` now appears in the build output. This step
 <!--+if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/build-app" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app" class="button bg-pink">Next Step</a>
 <!--+end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app.md
@@ -103,7 +103,7 @@ A new image named `test-node-js-app` was created in your Docker daemon with a la
 <!--+if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/make-app-runnable" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/05_make-app-runnable" class="button bg-pink">Next Step</a>
 <!--+end+-->
 
 [layers-dir]: /docs/reference/spec/buildpack-api/#layers
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/05_make-app-runnable.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/05_make-app-runnable.md
@@ -81,5 +81,5 @@ We can add multiple process types to a single app. We'll do that in the next sec
 <!--+if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/specify-multiple-process-types" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching" class="button bg-pink">Next Step</a>
 <!--+end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching.md
@@ -150,5 +150,5 @@ Next, let's see how buildpack users may be able to provide configuration to the
 <!--+if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/make-buildpack-configurable" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable" class="button bg-pink">Next Step</a>
 <!--+end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable.md
@@ -111,14 +111,6 @@ You will notice that version of NodeJS specified in the app's `.node-js-version`
 -----> Downloading and extracting NodeJS 18.18.1
 ```
 
-Next, let's see how buildpacks can store information about the dependencies provided in the output app image for introspection.
-
-<!--+if false+-->
----
-
-<a href="/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials" class="button bg-pink">Next Step</a>
-<!--+end+-->
-
 ## Going further
 
 Now that you've finished your buildpack, how about extending it? Try:
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-buildpack/_index.md b/content/docs/for-buildpack-authors/tutorials/basic-buildpack/_index.md
@@ -18,18 +18,16 @@ Before we get started, make sure you've got the following installed:
 
 This is a step-by-step tutorial for creating a nodeJS Cloud Native Buildpack.
 
-- [Set up your local environment](/docs/buildpack-author-guide/create-buildpack/setup-local-environment)
-- [Building blocks of a Cloud Native Buildpack](/docs/buildpack-author-guide/create-buildpack/building-blocks-cnb)
-- [Detecting your application](/docs/buildpack-author-guide/create-buildpack/detection)
-- [Building your application](/docs/buildpack-author-guide/create-buildpack/build-app)
-- [Making your application runnable](/docs/buildpack-author-guide/create-buildpack/make-app-runnable)
-- [Specifying multiple process types](/docs/buildpack-author-guide/create-buildpack/specify-multiple-process-types)
-- [Improving performance with caching](/docs/buildpack-author-guide/create-buildpack/caching)
-- [Making your buildpack configurable](/docs/buildpack-author-guide/create-buildpack/make-buildpack-configurable)
-- [Adding a Bill-of-Materials](/docs/buildpack-author-guide/create-buildpack/adding-bill-of-materials)
+- [Set up your local environment](/docs/for-buildpack-authors/tutorials/basic-buildpack/01_setup-local-environment)
+- [Building blocks of a Cloud Native Buildpack](/docs/for-buildpack-authors/tutorials/basic-buildpack/02_building-blocks-cnb)
+- [Detecting your application](/docs/for-buildpack-authors/tutorials/basic-buildpack/03_detection)
+- [Building your application](/docs/for-buildpack-authors/tutorials/basic-buildpack/04_build-app)
+- [Making your application runnable](/docs/for-buildpack-authors/tutorials/basic-buildpack/05_make-app-runnable)
+- [Improving performance with caching](/docs/for-buildpack-authors/tutorials/basic-buildpack/06_caching)
+- [Making your buildpack configurable](/docs/for-buildpack-authors/tutorials/basic-buildpack/07_make-buildpack-configurable)
 
 <!--+if false+-->
 ---
 
-<a href="/docs/buildpack-author-guide/create-buildpack/setup-local-environment" class="button bg-pink">Start Tutorial</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-buildpack/01_setup-local-environment" class="button bg-pink">Start Tutorial</a>
 <!--+end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/01_setup-local-environment.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/01_setup-local-environment.md
@@ -85,5 +85,5 @@ git clone https://github.com/buildpacks/samples.git
 <!--+ if false +-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/why-dockerfiles" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles" class="button bg-pink">Next Step</a>
 <!--+ end+-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/02_why-dockerfiles.md
@@ -105,5 +105,5 @@ Let's take a look at how the `samples/vim` extension installs `vim` on the build
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/building-blocks-extension" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/03_building-blocks-extension" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/03_building-blocks-extension.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/03_building-blocks-extension.md
@@ -45,5 +45,5 @@ For guidance around writing extensions and more advanced use cases, see [here](/
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/build-dockerfile" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/04_build-dockerfile" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/04_build-dockerfile.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/04_build-dockerfile.md
@@ -91,4 +91,4 @@ Let's take a look at how the `samples/curl` extension fixes the error by switchi
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-switch" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/05_run-dockerfile-switch" class="button bg-pink">Next Step</a>
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/05_run-dockerfile-switch.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/05_run-dockerfile-switch.md
@@ -145,5 +145,5 @@ Luckily, we can also use image extensions to dynamically install runtime depende
 <!--+ if false+-->
 ---
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/run-dockerfile-extend" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/06_run-dockerfile-extend" class="button bg-pink">Next Step</a>
 <!--+ end +-->
diff --git a/content/docs/for-buildpack-authors/tutorials/basic-extension/_index.md b/content/docs/for-buildpack-authors/tutorials/basic-extension/_index.md
@@ -11,4 +11,4 @@ This is a step-by-step tutorial for creating and using image extensions, which a
 
 <!--more-->
 
-<a href="/docs/for-buildpack-authors/tutorials/basic-extension/setup-local-environment" class="button bg-pink">Start Tutorial</a>
+<a href="/docs/for-buildpack-authors/tutorials/basic-extension/01_setup-local-environment" class="button bg-pink">Start Tutorial</a>
diff --git a/content/docs/for-platform-operators/how-to/migrate/deprecated/platform-api-0.3-0.4.md b/content/docs/for-platform-operators/how-to/migrate/deprecated/platform-api-0.3-0.4.md
@@ -11,13 +11,13 @@ See the [spec release](https://github.com/buildpacks/spec/releases/tag/platform%
 
 ### Windows support
 
-Windows image builds are now supported! See the [Windows build guide](/docs/for-app-developers/how-to/configure-build-environment/build-for-windows)
+Windows image builds are now supported! See the [Windows build guide](/docs/for-app-developers/how-to/special-cases/build-for-windows)
 for more details.
 
 ### Multicall launcher
 
 When running the exported application image, it is now possible to provide arguments to pre-defined process types. 
-The new flow is described [here](/docs/for-app-developers/tutorials/basic-app/run/#run-a-multi-process-app).
+The new flow is described [here](/docs/for-app-developers/how-to/build-outputs/specify-launch-process/#run-a-multi-process-app).
 As part of these changes, the exporter will not set, and the launcher no longer accepts, the `CNB_PROCESS_TYPE` variable.
 See the associated [RFC](https://github.com/buildpacks/rfcs/blob/main/text/0045-launcher-arguments.md) and [spec PR](https://github.com/buildpacks/spec/pull/118)
 for more details.
