chore(applications): create application section

Author: slack

mkdocs.yml

@@ -28,14 +28,15 @@ pages:
   - Installing Workflow:
     - System Requirements: installing-workflow/system-requirements.md
     - Configuring Object Storage: installing-workflow/configuring-object-storage.md
+  - Applications:
+    - Buildpacks: applications/using-buildpacks.md
+    - Dockerfiles: applications/using-dockerfiles.md
+    - Docker Images: applications/using-docker-images.md
   - Using Workflow:
     - Installing the Client: using-workflow/installing-the-client.md
+    - Process Types and the Procfile: using-workflow/process-types-and-the-procfile.md
     - Registering a User: using-workflow/registering-a-user.md
     - Deploying an Application: using-workflow/deploying-an-application.md
-    - Process Types and the Procfile: using-workflow/process-types-and-the-procfile.md
-    - Using Buildpacks: using-workflow/using-buildpacks.md
-    - Using Dockerfiles: using-workflow/using-dockerfiles.md
-    - Using Docker Images: using-workflow/using-docker-images.md
     - Configuring an Application: using-workflow/configuring-an-application.md
     - Managing an Application: using-workflow/managing-an-application.md
     - Application SSL Certificates: using-workflow/application-ssl-certificates.md

src/using-workflow/using-buildpacks.md src/applications/using-buildpacks.mdsrc/using-workflow/using-buildpacks.md renamed to src/applications/using-buildpacks.md

@@ -150,5 +150,5 @@ documentation][logger-documentation].
 [release]: ../reference-guide/terms.md#release
 [router-documentation]: https://github.com/deis/router
 [router]: #router
-[using-buildpacks]: ../using-workflow/using-buildpacks.md
-[using-dockerfiles]: ../using-workflow/using-dockerfiles.md
+[using-buildpacks]: ../applications/using-buildpacks.md
+[using-dockerfiles]: ../applications/using-dockerfiles.md

src/using-workflow/using-docker-images.md src/applications/using-docker-images.mdsrc/using-workflow/using-docker-images.md renamed to src/applications/using-docker-images.md

@@ -130,12 +130,12 @@ to external or third-party vendor services.
 [backing services]: http://12factor.net/backing-services
 [build]: ../reference-guide/terms.md#build
 [builder]: components.md#builder
-[buildpacks]: ../using-workflow/using-buildpacks.md
+[buildpacks]: ../applications/using-buildpacks.md
 [cncf]: https://cncf.io/
 [components]: components.md
 [config]: ../reference-guide/terms.md#config
-[dockerfile]: ../using-workflow/using-dockerfiles.md
-[dockerimage]: ../using-workflow/using-docker-images.md
+[dockerfile]: ../applications/using-dockerfiles.md
+[dockerimage]: ../applications/using-docker-images.md
 [environment variables]: http://12factor.net/config
 [helm]: https://helm.sh
 [release]: ../reference-guide/terms.md#release

src/using-workflow/using-dockerfiles.md src/applications/using-dockerfiles.mdsrc/using-workflow/using-dockerfiles.md renamed to src/applications/using-dockerfiles.md

@@ -34,14 +34,14 @@ Deis supports three different ways of building applications:
 
 Heroku buildpacks are useful if you want to follow Heroku's best practices for building applications or if you are porting an application from Heroku.
 
-Learn how to deploy applications [using Buildpacks](using-buildpacks.md).
+Learn how to deploy applications [using Buildpacks](../applications/using-buildpacks.md).
 
 
 ### Dockerfiles
 
 Dockerfiles are a powerful way to define a portable execution environment built on a base OS of your choosing.
 
-Learn how to deploy applications [using Dockerfiles](using-dockerfiles.md).
+Learn how to deploy applications [using Dockerfiles](../applications/using-dockerfiles.md).
 
 
 ### Docker Image
@@ -50,7 +50,7 @@ Deploying a Docker image onto Deis allows you to take a Docker image from either
 or a private registry and copy it over bit-for-bit, ensuring that you are running the same
 image in development or in your CI pipeline as you are in production.
 
-Learn how to deploy applications [using Docker images](using-docker-images.md).
+Learn how to deploy applications [using Docker images](../applications/using-docker-images.md).
 
 [application]: ../reference-guide/terms.md#application
 [controller]: ../understanding-workflow/components.md#controller

src/understanding-workflow/components.md

@@ -87,7 +87,7 @@ Scaling a process type directly changes the number of [Containers][container] ru
 
 When deploying to Deis Workflow using a Heroku Buildpack, Workflow boots the `web` process type to
 boot the application server. When you deploy an application that has a Dockerfile or uses [Docker
-images](using-docker-images.md), Workflow boots the `cmd` process type. Both act similarly in that
+images][docker image], Workflow boots the `cmd` process type. Both act similarly in that
 they are exposed to the router as web applications. However, the `cmd` process type is special
 because, if left undefined, it is equivalent to running the [container][] without any additional
 arguments.  (i.e. The process specified by the Dockerfile or Docker image's `CMD` directive will
@@ -99,6 +99,6 @@ down the old process type and scale the new process type up.
 
 [container]: ../reference-guide/terms.md#container
 [process model]: https://devcenter.heroku.com/articles/process-model
-[buildpacks]: using-buildpacks.md
-[dockerfile]: using-dockerfiles.md
-[docker image]: using-docker-images.md
+[buildpacks]: ../applications/using-buildpacks.md
+[dockerfile]: ../applications/using-dockerfiles.md
+[docker image]: ../applications/using-docker-images.md