Move extension guide to buildpack-authors tutorial

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

Author: Natalie Arellano

content/docs/extension-guide/create-extension/_index.md

@@ -1,6 +1,14 @@
 +++
 title="Write a basic extension"
 weight=2
-expand=true
-include_summaries=true
+aliases = [
+  "/docs/extension-author-guide/create-extension"
+  ]
+include_summaries=false
 +++
+
+This is a step-by-step tutorial for creating and using image extensions, which allow for customization of the build-time and runtime base images using Dockerfiles.
+
+<!--more-->
+
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/setup-local-environment" class="button bg-pink">Start Tutorial</a>

content/docs/for-buildpack-authors/tutorials/write-basic-extension/_index.md

@@ -1,6 +1,6 @@
 +++
-title="Generating a build.Dockerfile"
-weight=404
+title="Extending the build-time base image with a build.Dockerfile"
+weight=4
 aliases = [
   "/docs/extension-author-guide/create-extension/build-dockerfile/",
   ]
@@ -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/extension-guide/create-extension/run-dockerfile-switch" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-switch" class="button bg-pink">Next Step</a>

content/docs/extension-guide/create-extension/build-dockerfile.md renamed to content/docs/for-buildpack-authors/tutorials/write-basic-extension/build-dockerfile.md

@@ -1,6 +1,6 @@
 +++
-title="Building blocks of a CNB Image Extension"
-weight=403
+title="The building blocks of a CNB image extension"
+weight=3
 aliases = [
   "/docs/extension-author-guide/building-blocks-extension/"
   ]
@@ -45,5 +45,5 @@ For guidance around writing extensions and more advanced use cases, see [here](/
 <!--+ if false+-->
 ---
 
-<a href="/docs/extension-guide/create-extension/build-dockerfile" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/build-dockerfile" class="button bg-pink">Next Step</a>
 <!--+ end +-->

content/docs/extension-guide/create-extension/building-blocks-extension.md renamed to content/docs/for-buildpack-authors/tutorials/write-basic-extension/building-blocks-extension.md

@@ -1,6 +1,6 @@
 +++
-title="Generating a run.Dockerfile that extends the runtime base image"
-weight=406
+title="Extending the runtime base image with a run.Dockerfile"
+weight=6
 +++
 
 <!-- test:suite=dockerfiles;weight=6 -->

content/docs/extension-guide/create-extension/run-dockerfile-extend.md renamed to content/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-extend.md

@@ -1,6 +1,6 @@
 +++
-title="Generating a run.Dockerfile that switches the runtime base image"
-weight=405
+title="Switching the runtime base image with a run.Dockerfile"
+weight=5
 aliases = [
   "/docs/extension-author-guide/run-dockerfile/"
   ]
@@ -145,5 +145,5 @@ Luckily, we can also use image extensions to dynamically install runtime depende
 <!--+ if false+-->
 ---
 
-<a href="/docs/extension-guide/create-extension/run-dockerfile-extend" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-extend" class="button bg-pink">Next Step</a>
 <!--+ end +-->

content/docs/extension-guide/create-extension/run-dockerfile-switch.md renamed to content/docs/for-buildpack-authors/tutorials/write-basic-extension/run-dockerfile-switch.md

@@ -1,16 +1,23 @@
 +++
 title="Set up your local environment"
-weight=401
+weight=1
 aliases = [
   "/docs/extension-author-guide/create-extension/setup-local-environment/",
   ]
 +++
 
-<!-- test:suite=dockerfiles;weight=1 -->
-
 Let's walk through a build that uses extensions, step by step. We will see an image extension that installs `curl` on
 the builder image, and switches the run image to an image that has `curl` installed.
 
+### Check system requirements
+
+Before we get started, make sure you've got the following installed:
+
+{{< download-button href="https://store.docker.com/search?type=edition&offering=community" color="blue" >}} Install Docker {{</>}}
+{{< download-button href="/docs/install-pack" color="pink" >}} Install pack {{</>}}
+
+<!-- test:suite=dockerfiles;weight=1 -->
+
 ### Ensure Docker is running
 
 <!-- test:exec -->
@@ -78,5 +85,5 @@ git clone https://github.com/buildpacks/samples.git
 <!--+ if false +-->
 ---
 
-<a href="/docs/extension-guide/create-extension/why-dockerfiles" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/why-dockerfiles" class="button bg-pink">Next Step</a>
 <!--+ end+-->

content/docs/extension-guide/create-extension/setup-local-environment.md renamed to content/docs/for-buildpack-authors/tutorials/write-basic-extension/setup-local-environment.md

@@ -1,6 +1,6 @@
 +++
-title="Why Dockerfiles"
-weight=402
+title="Why this feature?"
+weight=2
 aliases = [
   "/docs/extension-author-guide/create-extension/why-dockerfiles/",
   ]
@@ -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/extension-guide/create-extension/building-blocks-extension" class="button bg-pink">Next Step</a>
+<a href="/docs/for-buildpack-authors/tutorials/write-basic-extension/building-blocks-extension" class="button bg-pink">Next Step</a>
 <!--+ end +-->