updated coder tour and screenshots

coder · matifali · May 22, 2024 · May 23, 2024 · May 23, 2024 · May 23, 2024
commit 3cf73edda3ae20a957a7b84d1c33886863428e22
diff --git a/docs/images/start/build-template.png b/docs/images/start/build-template.png
diff --git a/docs/images/start/first-template.png b/docs/images/start/first-template.png
diff --git a/docs/images/start/template-edit-source-code.png b/docs/images/start/template-edit-source-code.png
diff --git a/docs/images/start/template-publish.png b/docs/images/start/template-publish.png
diff --git a/docs/images/start/template-source-code.png b/docs/images/start/template-source-code.png
diff --git a/docs/start/coder-tour.md b/docs/start/coder-tour.md
@@ -1,28 +1,25 @@
-## Tour Coder and Set up your first deployment.
+# Tour Coder and with your first deployment
 
-For day-zero Coder users, we recommend following this guide to set up a local
-Coder deployment, create your first template, and connect to a workspace. This
-is completely free and leverages our
+This guide walks through the core product concepts by setting up a
+Coder deployment, creating your first template, and connecting to a workspace. This
+is made readily available by leveraging our
 [open source repository](https://github.com/coder/coder).
 
 We'll use [Docker](https://docs.docker.com/engine) to manage the compute for a
-slim deployment to experiment with
-[workpsaces](../tutorials/workspaces/README.md) and
-[templates](../tutorials/templates/README.md).
-
-Docker is not necessary for every Coder deployment and is only used here for
-simplicity.
+slim deployment.
 
 # Set up your Coder Deployment
 
-## 1. Install Docker
+### 1. Install Docker
 
-First, install [Docker](https://docs.docker.com/engine/install/) locally.
+First, install [Docker](https://docs.docker.com/engine/install) locally.
 
 > If you already have the Coder binary installed, restart it after installing
 > Docker.
 
-## 2. Install Coder daemon
+### 2. Install Coder daemon
+
+A single binary contains the CLI (`coder`) and is used for both the Coder server and the client.
 
 <div class="tabs">
 
@@ -36,11 +33,6 @@ curl -L https://coder.com/install.sh | sh
 
 ## Windows
 
-> **Important:** If you plan to use the built-in PostgreSQL database, you will
-> need to ensure that the
-> [Visual C++ Runtime](https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist#latest-microsoft-visual-c-redistributable-version)
-> is installed.
-
 You can use the
 [`winget`](https://learn.microsoft.com/en-us/windows/package-manager/winget/#use-winget)
 package manager to install Coder:
@@ -49,9 +41,17 @@ package manager to install Coder:
 winget install Coder.Coder
 ```
 
+> **Important:** If you plan to use the built-in PostgreSQL database, you will
+> need to ensure that the
+> [Visual C++ Runtime](https://learn.microsoft.com/en-US/cpp/windows/latest-supported-vc-redist#latest-microsoft-visual-c-redistributable-version)
+> is installed.
+
+
 </div>
 
-## 3. Start the server
+> See our [install docs](../install/README.md) for other methods of installing and deploying Coder.
+
+### 3. Start the server
 
 To start or restart the Coder deployment, use the following command:
 
@@ -67,9 +67,10 @@ create your first administrator account.
 Once you've signed in, you'll be brought to an empty workspaces page, which
 we'll soon populate with your first development environments.
 
-### More information on the Coder Server
 
-# Create your first template
+> To learn more about interacting with the control plane through the terminal, see our `coder server` [CLI docs](../cli/server.md).
+
+## Create your first template
 
 A common way to create a template is to begin with a starter template then
 modify it for your needs. Coder makes this easy with starter templates for
@@ -78,10 +79,12 @@ template is up and running, you can edit it in the Coder dashboard. Coder even
 handles versioning for you so you can publish official updates or revert to
 previous versions.
 
+> Read more about templates in our [tutorials section](../tutorials/templates.md).
+
 In this tutorial, you'll create your first template from the Docker starter
 template.
 
-## 1. Choose a starter template
+### 1. Choose a starter template
 
 Select **Templates** to see the **Starter Templates**. Use the **Docker
 Containers** template by pressing **Use Template**.
@@ -91,23 +94,28 @@ Containers** template by pressing **Use Template**.
 > You can also a find a comprehensive list of starter templates in **Templates**
 > -> **Create Template** -> **Starter Templates**.
 
-## 2. Create your template
+### 2. Create your template
 
 In **Create template**, fill in **Name** and **Display name**, then select
 **Create template**.
 
 ![Creating a template](../images/start/create-template.png)
 
-TODO:
-
-- add CLI guide for making a new template
-- refactor text below to be more beginner-friendly
+### Other template resources
+- [Templates overview](../tutorials/templates/README.md)
+- [Create templates through the CLI](../cli/templates_create.md)
+- See our [Community Templates](https://github.com/coder/coder/blob/main/examples/templates/community-templates.md) in Github
+- Create a template from a [Dev Container](../templates/dev-containers.md)
 
 # Create a workspace
 
-## 1. Create a workspace from your template
+Coder workspaces are the primary interface for end-users. Each workspace is defined by a template, but can be modified with parameters and settings. The easiest way to create a workspace is through the template GUI.
+
+> Read more about templates in our [tutorials section](../tutorials/workspaces.md).
+
+### 1. Create a workspace from your template
 
-When the template is ready, select **Create Workspace**.
+From the template page, select **Create Workspace**.
 
 ![Template Preview](../images/start/template-preview.png)
 
@@ -122,7 +130,7 @@ After a few seconds, your workspace is ready to use.
 
 ![Workspace is ready](../images/start/workspace-ready.png)
 
-## 4. Try out your new workspace
+### 2. Try out your new workspace
 
 This starter template lets you connect to your workspace in a few ways:
 
@@ -142,7 +150,11 @@ This starter template lets you connect to your workspace in a few ways:
 
 When you're done, you can stop the workspace.
 
-## 6. Modify your template
+
+## Expand your configuration
+
+
+### Modify your template
 
 Now you can modify your template to suit your team's needs.
 
@@ -152,29 +164,26 @@ web browser.
 
 In the Coder dashboard, select **Templates** then your first template.
 
-![Selecting the first template](../images/templates/select-template.png)
+![Selecting the first template](../images/start/first-template.png)
 
-In the drop-down menu, select **Edit files**.
+In the this view, select **Source Code** to view and edit the template files.
 
-![Edit template files](../images/templates/edit-files.png)
+![Edit template files](../images/start/template-source-code.png)
 
-Expand the **build** directory and select **Dockerfile**.
 
-![Selecting source code](../images/templates/source-code.png)
+Click the **Edit** button at the top-right of the `build/Dockerfile` to open the in-browser editor then replace `golang` with `python3`.
 
-Edit `build/Dockerfile` to replace `golang` with `python3`.
-
-![Editing source code](../images/templates/edit-source-code.png)
+![Editing source code](../images/start/template-edit-source-code.png)
 
 Select **Build template** and wait for Coder to prepare the template for
 workspaces.
 
-![Building a template](../images/templates/build-template.png)
+![Building a template](../images/start/build-template.png)
 
 Select **Publish version**. In the **Publish new version** dialog, make sure
 **Promote to default version** is checked then select **Publish**.
 
-![Publish a template](../images/templates/publish.png)
+![Publish a template](../images/start/template-publish.png)
 
 Now when developers create a new workspace from this template, they can use
 Python 3 instead of Go.
@@ -184,3 +193,7 @@ template, Coder will notify them that there's a new version of the template.
 
 You can also handle [change management](./change-management.md) through your own
 repo and continuous integration.
+
+
+### Next Steps
+- TODO