Move long-winded fly launch doc to reference section (superfly#552)

* move long-winded fly launch doc to reference

* relabel launch ref nav link

* rename file

* add redirect

* Update link text speedrun.html.md.erb

partials/_firecracker_nav.html.erb

@@ -20,9 +20,6 @@
       <li>
         <%= nav_link "Working with Fly Apps", "/docs/getting-started/working-with-fly-apps/" %>
       </li>
-      <li>
-        <%= nav_link "Launching a New App", "/docs/getting-started/launch-app/" %>
-      </li>
       <li>
         <%= nav_link "Troubleshooting Deployments", "/docs/getting-started/troubleshooting/" %>
       </li>
@@ -135,6 +132,9 @@
       <li>
         <%= nav_link "Builders", "/docs/reference/builders/" %>
       </li>
+      <li>
+        <%= nav_link "Fly Launch", "/docs/reference/fly-launch/" %>
+      </li>
       <li>
         <%= nav_link "Load Balancing", "/docs/reference/load-balancing/" %>
       </li>

getting-started/launch-app.html.md.erb → reference/fly-launch.html.md

@@ -1,26 +1,21 @@
 ---
-title: Launching a New App
+title: Fly Launch
 layout: docs
 sitemap: false
 nav: firecracker
 toc: false
+redirect-from:
+   - /docs/getting-started/launch-app/
 ---
 
-<div class="callout">
-### New to Fly.io?
-
-Start with the [Speedrun](/docs/speedrun), or for a little more detail, [Hands-on with Fly.io](/docs/hands-on/).
-</div>
-
-Usually, to create a new app on Fly.io, you'll write your source code and then run `fly launch`. [`fly launch`](/docs/flyctl/launch/) is an all-in-one tool that automates as much as possible between writing the code and deploying on Fly.io, setting you up with a running app with good defaults.
+Usually, to create a new App on Fly.io, you'll write your source code and then run `fly launch`. [`fly launch`](/docs/flyctl/launch/) is an all-in-one tool that automates as much as possible between writing the code and deploying on Fly.io, setting you up with a running app with good defaults.
 
 The language-specific launchers built into flyctl via `fly launch` perform different tasks as needed, but in broad strokes, here are the things that generally happen between writing your source code and it going live on Fly.io, whether this happens through `fly launch` or through a more manual process you might begin with `fly apps create`.
 
 ## New App Creation
 
 When `fly launch` or `fly apps create` creates a new app, it gets a name, an organization, a preferred deployment region, and a default configuration that's good for simple apps that should be publicly available on the web. At this early stage there's nothing to deploy; you can create an app before you even decide what language to write it in.
 
-
 ## Build Configuration
 
 An app deployed on Fly.io has to be packaged into a Docker image so we can turn it into a Firecracker VM.

speedrun.html.md.erb

@@ -24,7 +24,7 @@ For many languages and frameworks, you can deploy your app from zero, with the f
 
 You're not limited to these kinds of projects, though! `fly launch` also knows what to do [with a Dockerfile](/docs/getting-started/dockerfile/), so you can use the tech _you_ love.
 
-See [Launching a New App](/docs/getting-started/launch-app/) for more on what `fly launch` does.
+See [Fly Launch](/docs/reference/launch/) for more on what `fly launch` does.
 
 ## Next steps