get-started: add landing page w/ walkthroughs (#18808)

* add get-started landing page

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>

content/_index.md

@@ -7,7 +7,7 @@ grid:
   image:
     dark: /assets/images/rocket-dark.svg
     light: /assets/images/rocket.svg
-  link: /get-started/
+  link: /guides/get-started/
   description: Learn Docker basics and the benefits of containerizing your applications.
 - title: Download and install
   image:

content/get-started/_index.md

@@ -67,12 +67,6 @@ This guide contains step-by-step instructions on how to get started with Docker.
 - Deploy Docker applications using multiple containers with a database.
 - Run applications using Docker Compose.
 
-> **Note**
->
-> Before diving in, try the 5-minute hands-on
-> [walkthroughs](../guides/walkthroughs/_index.md) to get more familiar with
-> Docker Desktop.
-
 ## What is a container?
 
 A container is a sandboxed process running on a host machine that is isolated from all other processes running on that host machine. That isolation leverages [kernel namespaces and cgroups](https://medium.com/@saschagrunert/demystifying-containers-part-i-kernel-space-2c53d6979504),

content/guides/get-started/_index.md

@@ -0,0 +1,55 @@
+---
+title: Overview of get started
+keywords: get started, quick start, intro, concepts
+description: Learn how to get started with Docker and Docker Desktop
+
+grid:
+  - title: "What is a container?"
+    link: "/guides/walkthroughs/what-is-a-container/"
+    image: "/guides/walkthroughs/images/what-is-a-container.webp"
+  - title: "Run a container"
+    image: "/guides/walkthroughs/images/how-do-i-run-a-container.webp"
+    link: "/guides/walkthroughs/run-a-container/"
+  - title: "Run Docker Hub images"
+    image: "/guides/walkthroughs/images/run-docker-hub-images.webp"
+    link: "/guides/walkthroughs/run-hub-images/"
+  - title: "Multi-container apps"
+    image: "/guides/walkthroughs/images/multi-container-apps.webp"
+    link: "/guides/walkthroughs/multi-container-apps/"
+  - title: "Persist container data"
+    link: "/guides/walkthroughs/persist-data/"
+    image: "/guides/walkthroughs/images/persist-data.webp"
+  - title: "Access a local folder"
+    link: "/guides/walkthroughs/access-local-folder/"
+    image: "/guides/walkthroughs/images/bind-mounts.webp"
+  - title: "Containerize your application"
+    link: "/guides/walkthroughs/containerize-your-app/"
+    image: "/guides/walkthroughs/images/containerize-app.webp"
+  - title: "Publish your image to Docker Hub"
+    link: "/guides/walkthroughs/publish-your-image/"
+    image: "/guides/walkthroughs/images/publish-your-images.webp"
+aliases:
+- /get-started/hands-on-overview/
+---
+
+## Quick hands-on guides
+
+Let these 5-minute hands-on guides show you around Docker Desktop and introduce you to containerization concepts.
+
+{{< grid cols=2 >}}
+
+> **Note**
+>
+> These hands-on guides are also available as interactive walkthroughs inside
+> Docker Desktop's learning center.
+
+## Getting started guide
+
+Dive deeper into Docker and containerization concepts in this end-to-end guide.
+
+{{< card
+  title="Getting started guide"
+  link=/get-started/
+  description="A 45-minute guide where you start by containerizing a simple application and then follow along to develop it into a multi-container application."
+  icon="/assets/images/rocket.svg"
+>}}

content/guides/walkthroughs/_index.md

@@ -1,36 +0,0 @@
----
-title: Walkthroughs overview
-keywords: get started, quick start, intro, concepts
-description: Learn how to build, share, and run applications faster with Docker's 5-minute hands-on walkthroughs
-grid:
-  - title: "What is a container?"
-    description: Explore a running container in Docker Desktop
-    link: "/guides/walkthroughs/what-is-a-container/"
-  - title: "How do I run a container?"
-    description: Learn how to build an image and run it as a container
-    link: "/guides/walkthroughs/run-a-container/"
-  - title: "Run Docker Hub images"
-    description: Access over 100,000 images in Docker Hub and learn how to run them as a container
-    link: "/guides/walkthroughs/run-hub-images/"
-  - title: "Run multi-container applications"
-    description: Use Docker Compose to run multi-container applications
-    link: "/guides/walkthroughs/multi-container-apps/"
-  - title: "Persist data between containers"
-    description: Persist and share data among containers using a named volume
-    link: "/guides/walkthroughs/persist-data/"
-  - title: "Access a local folder"
-    description: Share and access a local folder from a container with a bind mount
-    link: "/guides/walkthroughs/access-local-folder/"
-  - title: "Containerize your application"
-    description: Find out how to containerize your own apps with a single command
-    link: "/guides/walkthroughs/containerize-your-app/"
-  - title: "Publish your image"
-    description: Publish and share you images on Docker Hub
-    link: "/guides/walkthroughs/publish-your-image/"
-aliases:
-- /get-started/hands-on-overview/
----
-
-Get introduced to Docker Desktop in these 5-minute hands-on guides.
-
-{{< grid >}}

content/guides/walkthroughs/access-local-folder.md

@@ -12,7 +12,8 @@ Docker isolates all content, code, and data in a container from your local files
 
 Sometimes, you may want to access a directory from your local filesystem. To do this, you can use bind mounts.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
+
 
 ## Step 1: Get the sample application
 

content/guides/walkthroughs/containerize-your-app.md

@@ -8,7 +8,7 @@ When working with containers, you typically need to create a `Dockerfile` to def
 
 To help you create these files, Docker Desktop has the `docker init` command. Run this command in a terminal within your project folder. `docker init` creates all the required files to containerize your application. This walkthrough shows you how this works.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Run the command to create Docker assets
 

content/guides/walkthroughs/multi-container-apps.md

@@ -6,7 +6,7 @@ description: Learn how to use Docker to run multi-container applications
 
 If you've already completed the [How do I run a container?](./run-a-container.md) walkthrough, you learned that you must start each container individually. Imagine how great it would be if a tool could start multiple containers with a single command. That tool is Docker Compose.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Get the sample application
 
@@ -33,14 +33,12 @@ Download the source and extract it.
 
 The sample application is a simple todo application built using ExpressJS and Node.js. The application saves all todos in a MongoDB database. You don't need to know any of these technologies to continue with the walkthrough.
 
-![The sample app architecture](images/getting-started-multi-container.webp?w=400)
+![The sample app architecture](images/getting-started-multi-container.webp?w=450&border=true)
 
 ## Step 2: Dig into the Compose file
 
 View the files of the sample application. Notice that it has a `compose.yaml` file. This file tells Docker how to run your application. Open the `compose.yaml` file in a code or text editor to view what it contains.
 
-![Viewing the Compose file](images/getting-started-compose.webp?w=400)
-
 ## Step 3: Run the application
 
 To run the multi-container application, open a terminal and run the following commands. Replace `/path/to/multi-container-app/` with the path to your application's directory.
@@ -93,7 +91,7 @@ To delete the application stack:
 1. Open the **Containers** tab of Docker Desktop
 2. Select the Delete icon next to your application stack.
 
-![Deleting the application stack](images/getting-started-delete-stack.webp?w=300&border=true)
+![Deleting the application stack](images/getting-started-delete-stack.webp?border=true)
 
 After you delete the application stack, follow the steps from [Step 3: Run the
 application](#step-3-run-the-application) to run the application again. Note
@@ -115,4 +113,4 @@ Related information:
 
 Continue to the next walkthrough to learn how to persist data even after deleting the application stack.
 
-{{< button url="./persist-data.md" text="Persist data between containers" >}}
+{{< button url="./persist-data.md" text="Persist container data" >}}

content/guides/walkthroughs/persist-data.md

@@ -1,7 +1,7 @@
 ---
-title: Persist data between containers
+title: Persist container data
 keywords: get started, quick start, intro, concepts
-description: Learn how to persist data between containers
+description: Learn how to persist container data
 ---
 
 This walkthrough shows you how to persist data between containers. To better understand some concepts in this walkthrough, complete the [Run multi-container applications](./multi-container-apps.md) walkthrough first.
@@ -12,7 +12,7 @@ Docker isolates all content, code, and data in a container from your local files
 
 Sometimes, you may want to persist the data that a container generates. To do this, you can use volumes.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Get the sample application
 
@@ -92,7 +92,7 @@ To delete the application stack:
 1. Open the **Containers** tab of Docker Desktop
 2. Select the Delete icon next to your application stack.
 
-![Deleting the application stack](images/getting-started-delete-stack.webp?w=300&border=true)
+![Deleting the application stack](images/getting-started-delete-stack.webp?border=true)
 
 After you delete the application stack, follow the steps from [Step 3: Run the
 application](#step-3-run-the-application) to run the application again. Note

content/guides/walkthroughs/publish-your-image.md

@@ -8,7 +8,7 @@ aliases:
 
 Follow this walkthrough to learn how to publish and share your images on Docker Hub.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Get the example image
 
@@ -18,13 +18,13 @@ To get the example image:
 2. In the search bar, specify `docker/welcome-to-docker`.
 3. Select **Pull** to pull the image from Docker Hub to you computer.
 
-![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.webp?w=400)
+![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.webp?w=650&border=true)
 
 ## Step 2: Sign in to Docker
 
 Select **Sign in** on the top-right of Docker Desktop to either sign in or create a new Docker account.
 
-![Signing in to Docker Desktop](images/getting-started-signin.webp?w=300)
+![Signing in to Docker Desktop](images/getting-started-signin.webp?w=300&border=true)
 
 ## Step 3: Rename your image
 
@@ -44,7 +44,7 @@ To push your image to Docker Hub:
 2. In the **Actions** column for your image, select the **Show image actions** icon.
 3. Select **Push to Hub**.
 
-![Pushing an image to Docker Hub](images/getting-started-push.webp?w=200&border=true)
+![Pushing an image to Docker Hub](images/getting-started-push.webp?border=true)
 
 Go to [Docker Hub](https://hub.docker.com)⁠ and verify that the list of your repositories now contains `YOUR-USERNAME/welcome-to-docker`.
 

content/guides/walkthroughs/run-a-container.md

@@ -8,9 +8,9 @@ aliases:
 
 In this walkthrough, you'll learn the basic steps of building an image and running your own container. This walkthrough uses a sample Node.js application, but it's not necessary to know Node.js.
 
-![Running an image in Docker Desktop](images/getting-started-run-intro.webp?w=400)
+![Running an image in Docker Desktop](images/getting-started-run-intro.webp?w=450&border=true)
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Get the sample application
 
@@ -40,8 +40,6 @@ Download the source and extract it.
 To run your code in a container, the most fundamental thing you need is a
 Dockerfile. A Dockerfile describes what goes into a container. This sample already contains a `Dockerfile`. For your own projects, you'll need to create your own `Dockerfile`. You can open the `Dockerfile` in a code or text editor and explore its contents.
 
-![Viewing Dockefile contents](images/getting-started-dockerfile.webp?w=400)
-
 ## Step 3: Build your first image
 
 You always need an image to run a container. In a terminal, run the following commands to build the image. Replace `/path/to/welcome-to-docker/` with the path to your `welcome-to-docker` directory.
@@ -69,14 +67,14 @@ To run your image as a container:
 2. Next to your image, select **Run**.
 3. Expand the **Optional settings**.
 4. In **Host port**, specify `8089`.
-   ![Specifying host port 8089](images/getting-started-run-image.webp?w=250&border=true)
+   ![Specifying host port 8089](images/getting-started-run-image.webp?w=500&border=true)
 5. Select **Run**.
 
 ## Step 5: View the frontend
 
 You can use Docker Desktop to access your running container. Select the link next to your container in Docker Desktop or go to [http://localhost:8089](http://localhost:8089) to view the frontend.
 
-![Selecting the container link](images/getting-started-frontend-2.webp?w=300&border=true)
+![Selecting the container link](images/getting-started-frontend-2.webp?border=true)
 
 ## Summary
 

content/guides/walkthroughs/run-hub-images.md

@@ -11,7 +11,7 @@ You can share and store images in Docker Hub
 images created by developers that you can run locally. You can search for Docker
 Hub images and run them directly from Docker Desktop.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Search for the image
 
@@ -20,7 +20,7 @@ You can search for Docker Hub images on Docker Desktop. To search for the image
 1. Open Docker Desktop and select the search.
 2. Specify `docker/welcome-to-docker` in the search.
 
-![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.webp?w=400)
+![Search Docker Desktop for the welcome-to-docker image](images/getting-started-search.webp?w=650&border=true)
 
 ## Step 2: Run the image
 
@@ -29,7 +29,7 @@ To run the `docker/welcome-to-docker` image:
 1. After finding the image using search, select **Run**.
 2. Expand the **Optional settings**.
 3. In **Host port**, specify `8090`.
-   ![Specifying host port 8090](images/getting-started-run.webp?w=250&border=true)
+   ![Specifying host port 8090](images/getting-started-run.webp?w=500&border=true)
 4. Select **Run**.
 
 > **Note**
@@ -44,7 +44,7 @@ To run the `docker/welcome-to-docker` image:
 
 That's it! The container is ready to use. Go to the **Containers** tab in Docker Desktop to view the container.
 
-![Viewing the Containers tab in Docker Desktop](images/getting-started-view.webp?w=400)
+![Viewing the Containers tab in Docker Desktop](images/getting-started-view.webp?border=true)
 
 ## Summary
 

content/guides/walkthroughs/what-is-a-container.md

@@ -15,7 +15,7 @@ use Docker Desktop to manage and explore your containers.
 In this walkthrough, you'll view and explore an actual container in Docker
 Desktop.
 
-Before you start, [get Docker Desktop](../../get-docker.md).
+{{< include "guides-get-docker.md" >}}
 
 ## Step 1: Set up the walkthrough
 
@@ -26,7 +26,7 @@ The first thing you need is a running container. Use the following instructions
 3. Expand the **Optional settings**.
 4. In **Container name**, specify `welcome-to-docker`.
 5. In **Host port**, specify `8088`.
-   ![Specifying host port 8088](images/getting-started-setup.webp?w=250&border=true)
+   ![Specifying host port 8088](images/getting-started-setup.webp?w=500&border=true)
 6. Select **Run**.
 
 ## Step 2: View containers on Docker Desktop
@@ -37,15 +37,13 @@ When working with more complex projects, you'll run different parts in different
 containers. For example, a different container for the frontend, backend, and
 database. In this walkthrough, you only have a simple frontend container.
 
-![Docker Desktop with get-started container running](images/getting-started-container.webp?w=400)
-
 ## Step 3: View the frontend
 
 The frontend is accessible on port 8088 of your local host. Select the link in
 the **Port(s)** column of your container, or visit
 [http://localhost:8088](http://localhost:8088) in your browser to view it.
 
-![Accessing container frontend from Docker Desktop](images/getting-started-frontend.webp?w=300&border=true)
+![Accessing container frontend from Docker Desktop](images/getting-started-frontend.webp?border=true)
 
 ## Step 4: Explore your container
 
@@ -53,7 +51,7 @@ Docker Desktop lets you easily view and interact with different aspects of your
 container. Try it out yourself. Select your container and then select **Files**
 to explore your container's isolated file system.
 
-![Viewing container details in Docker Desktop](images/getting-started-explore-container.webp?w=300&border=true)
+![Viewing container details in Docker Desktop](images/getting-started-explore-container.webp?border=true)
 
 ## Step 5: Stop your container
 
@@ -61,7 +59,7 @@ The `welcome-to-docker` container continues to run until you stop it. To stop
 the container in Docker Desktop, go to the **Containers** tab and select the
 **Stop** icon in the **Actions** column of your container.
 
-![Stopping a container in Docker Desktop](images/getting-started-stop.webp?w=400)
+![Stopping a container in Docker Desktop](images/getting-started-stop.webp?border=true)
 
 ## Summary
 

content/includes/guides-get-docker.md

@@ -0,0 +1 @@
+Before you start, get the latest version of [Docker Desktop](../../get-docker.md). Docker adds new features regularly and some parts of this guide may work only with the latest version of Docker Desktop.

data/toc.yaml

@@ -4,48 +4,49 @@ Guides:
 - title: Get Docker
   path: /get-docker/
 - sectiontitle: Get started
-  section:
-    - title: "Part 1: Overview"
-      path: /get-started/
-    - title: "Part 2: Containerize an application"
-      path: /get-started/02_our_app/
-    - title: "Part 3: Update the application"
-      path: /get-started/03_updating_app/
-    - title: "Part 4: Share the application"
-      path: /get-started/04_sharing_app/
-    - title: "Part 5: Persist the DB"
-      path: /get-started/05_persisting_data/
-    - title: "Part 6: Use bind mounts"
-      path: /get-started/06_bind_mounts/
-    - title: "Part 7: Multi-container apps"
-      path: /get-started/07_multi_container/
-    - title: "Part 8: Use Docker Compose"
-      path: /get-started/08_using_compose/
-    - title: "Part 9: Image-building best practices"
-      path: /get-started/09_image_best/
-    - title: "Part 10: What next?"
-      path: /get-started/11_what_next/
-
-- sectiontitle: Walkthroughs
   section:
     - title: "Overview"
-      path: /guides/walkthroughs/
+      path: /guides/get-started/
-    - title: "What is a container?"
+    - sectiontitle: "Quick hands-on guides"
-      path: /guides/walkthroughs/what-is-a-container/
+      section:
-    - title: "How do I run a container?"
+      - title: "What is a container?"
-      path: /guides/walkthroughs/run-a-container/
+        path: /guides/walkthroughs/what-is-a-container/
-    - title: "Run Docker Hub images"
+      - title: "Run a container"
-      path: /guides/walkthroughs/run-hub-images/
+        path: /guides/walkthroughs/run-a-container/
-    - title: "Run multi-container applications"
+      - title: "Run Docker Hub images"
-      path: /guides/walkthroughs/multi-container-apps/
+        path: /guides/walkthroughs/run-hub-images/
-    - title: "Persist data between containers"
+      - title: "Run multi-container applications"
-      path: /guides/walkthroughs/persist-data/
+        path: /guides/walkthroughs/multi-container-apps/
-    - title: "Access a local folder"
+      - title: "Persist container data"
-      path: /guides/walkthroughs/access-local-folder/
+        path: /guides/walkthroughs/persist-data/
-    - title: "Containerize your application"
+      - title: "Access a local folder"
-      path: /guides/walkthroughs/containerize-your-app/
+        path: /guides/walkthroughs/access-local-folder/
-    - title: "Publish your image"
+      - title: "Containerize your application"
-      path: /guides/walkthroughs/publish-your-image/
+        path: /guides/walkthroughs/containerize-your-app/
+      - title: "Publish your image"
+        path: /guides/walkthroughs/publish-your-image/
+    - sectiontitle: "Getting started guide"
+      section:
+      - title: "Part 1: Overview"
+        path: /get-started/
+      - title: "Part 2: Containerize an application"
+        path: /get-started/02_our_app/
+      - title: "Part 3: Update the application"
+        path: /get-started/03_updating_app/
+      - title: "Part 4: Share the application"
+        path: /get-started/04_sharing_app/
+      - title: "Part 5: Persist the DB"
+        path: /get-started/05_persisting_data/
+      - title: "Part 6: Use bind mounts"
+        path: /get-started/06_bind_mounts/
+      - title: "Part 7: Multi-container apps"
+        path: /get-started/07_multi_container/
+      - title: "Part 8: Use Docker Compose"
+        path: /get-started/08_using_compose/
+      - title: "Part 9: Image-building best practices"
+        path: /get-started/09_image_best/
+      - title: "Part 10: What next?"
+        path: /get-started/11_what_next/
 
 - sectiontitle: Language-specific guides
   section:

layouts/partials/components/card.html

@@ -51,4 +51,4 @@
     {{ if .link }}
   </a>
   {{ end }}
-</div>
+</div>