Update links in templates documentation

stirby · stirby · commit 339486a5cc66 · 2024-10-04T23:44:41.000Z
Resolve incorrect relative paths across various templates documentation
files to ensure all links work seamlessly after recent refactoring.

- Corrected links to setup and workspace lifecycle docs
- Updated GitHub repository links for JFrog templates
- Fixed CLI reference paths for coder commands
- Adjusted path for template schedule image

These changes improve document navigation and maintain consistency.
diff --git a/docs/admin/templates/extending-templates/icons.md b/docs/admin/templates/extending-templates/icons.md
@@ -44,7 +44,7 @@ come bundled with your Coder deployment.
     CODER_EXTERNAL_AUTH_1_ICON=/icon/google.svg
     ```
 
-- [**Support Links**](../admin/setup/appearance.md#support-links):
+- [**Support Links**](../../setup/appearance.md#support-links):
 
   - Use icons for support links to make them recognizable. You can set the
     `icon` field for each link in `CODER_SUPPORT_LINKS` array.
diff --git a/docs/admin/templates/extending-templates/index.md b/docs/admin/templates/extending-templates/index.md
@@ -50,7 +50,7 @@ ephemeral resources are destroyed and recreated on restart. All resources are
 destroyed when a workspace is deleted.
 
 > You can read more about how resource behavior and workspace state in the
-> [workspace lifecycle documentation](../../workspaces/lifecycle.md).
+> [workspace lifecycle documentation](../../../user-guides/workspace-lifecycle.md).
 
 Template resources follow the
 [behavior of Terraform resources](https://developer.hashicorp.com/terraform/language/resources/behavior#how-terraform-applies-a-configuration)
diff --git a/docs/admin/templates/extending-templates/modules.md b/docs/admin/templates/extending-templates/modules.md
@@ -111,9 +111,11 @@ Based on the instructions
 
 #### Example template
 
-We have an example template [here](../../examples/jfrog/remote/main.tf) that
-uses our [JFrog Docker](../../examples/jfrog/docker/main.tf) template as the
-underlying module.
+We have an example template
+[here](https://github.com/coder/coder/blob/main/examples/jfrog/remote/main.tf)
+that uses our
+[JFrog Docker](https://github.com/coder/coder/blob/main/examples/jfrog/docker/main.tf)
+template as the underlying module.
 
 ### Private git repository
 
diff --git a/docs/admin/templates/managing-templates/dependencies.md b/docs/admin/templates/managing-templates/dependencies.md
@@ -91,8 +91,8 @@ inside a folder containing the Terraform source code for a given template.
 
 This will create a new file named `.terraform.lock.hcl` in the current
 directory. When you next run
-[`coder templates push`](../reference/cli/templates_push.md), the lock file will
-be stored alongside with the other template source code.
+[`coder templates push`](../../../reference/cli/templates_push.md), the lock
+file will be stored alongside with the other template source code.
 
 > Note: Terraform best practices also recommend checking in your
 > `.terraform.lock.hcl` into Git or other VCS.
diff --git a/docs/admin/templates/managing-templates/devcontainers.md b/docs/admin/templates/managing-templates/devcontainers.md
@@ -20,10 +20,10 @@ Coder:
 ## How it works
 
 A Coder admin adds a devcontainer-compatible template to Coder (envbuilder).
-Then developers enter their repository URL as a [parameter](./parameters.md)
-when they create their workspace.
-[Envbuilder](https://github.com/coder/envbuilder) clones the repo and builds a
-container from the `devcontainer.json` specified in the repo.
+Then developers enter their repository URL as a
+[parameter](../extending-templates/parameters.md) when they create their
+workspace. [Envbuilder](https://github.com/coder/envbuilder) clones the repo and
+builds a container from the `devcontainer.json` specified in the repo.
 
 When using the [Envbuilder Terraform provider](#provider), a previously built
 and cached image can be re-used directly, allowing instantaneous dev container
diff --git a/docs/admin/templates/managing-templates/schedule.md b/docs/admin/templates/managing-templates/schedule.md
@@ -3,7 +3,7 @@
 You can configure a template to control how workspaces are started and stopped.
 You can also manage the lifecycle of failed or inactive workspaces.
 
-![Schedule screen](../../../images/templates/schedule/template-schedule-settings.png)
+![Schedule screen](../../../images/admin/templates/schedule/template-schedule-settings.png)
 
 ## Schedule
 
