fix: include subdirectories in example templates (#1715)

docs/about.md

@@ -48,7 +48,7 @@ layer of infrastructure control. This additional layer allows admins to:
 - Enable persistent workspaces, which are like local machines, but faster and
   hosted by a cloud service
 
-Coder includes [production-ready templates](../examples) for use with AWS EC2,
+Coder includes [production-ready templates](../examples/templates) for use with AWS EC2,
 Azure, Google Cloud, Kubernetes, and more.
 
 ## What Coder is *not*

docs/install.md

@@ -52,10 +52,13 @@ Coder](https://github.com/coder/coder/releases) installed.
    coder templates init
    ```
 
+   Choose the "Develop in Docker" example to generate a sample template in the
+   `docker` subdirectory.
+
 1. Navigate into the new directory and create a new template:
 
     ```console
-    cd examples/docker
+    cd docker
     coder templates create
     ```
 

docs/templates.md

@@ -9,7 +9,7 @@ to everybody. Users can also manually update their workspaces.
 
 ## Manage templates
 
-Coder provides production-ready [sample templates](../examples/), but you can
+Coder provides production-ready [sample templates](../examples/templates/), but you can
 modify the templates with Terraform.
 
 ```sh

docs/workspaces.md

@@ -58,7 +58,7 @@ resources](./templates.md#persistent-and-ephemeral-resources).
 
 > ⚠️ To avoid data loss, refer to your template documentation for information on
 > where to store files, install software, etc., so that they persist. Default
-> templates are documented in [../examples](../examples/).
+> templates are documented in [../examples/templates](../examples/templates/).
 >
 > You can use `coder show <workspace-name>` to see which resources are
 > persistent and which are ephemeral.