admin/index glossary section

EdwardAngert · EdwardAngert · commit e96b1bc70036 · 2024-11-13T14:06:26.000Z
diff --git a/docs/admin/index.md b/docs/admin/index.md
@@ -18,17 +18,25 @@ For any information not strictly contained in these sections, check out our
 ## What is an image, template, devcontainer, or workspace
 
 - **Template**
-  - [Templates](./templates/index.md) are...
+  - [Templates](./templates/index.md) are
+	<!-- Managed by Coder Template Administrators The template should include infrastructure-level dependencies for the workspace (for example, Kubernetes PersistentVolumeClaims, docker containers, or EC2 VMs). These should be applicable to all workspaces built from the template. -->
+
 - **Workspace**
   - A [workspace](../user-guides/workspace-management.md) is the environment
     that a developer works in. Developers on a team each work from their own
     workspace and can use [multiple IDEs](./workspace-access/index.md).
 - **Image**
-  - An [image](./templates/managing-templates/image-management.md) contains the
+  - A [base image](./templates/managing-templates/image-management.md) contains the
     utilities that the Coder workspace is built on. It can be an
     [example image](https://github.com/coder/images), custom image, or one from
     [Docker Hub](https://hub.docker.com/search). It is defined in each template.
+		Managed externally to Coder.
+		<!-- The devcontainer base image should include dependencies such as the base OS (for example, Debian or Fedora), and OS-level packages (curl, git, java). Include as much as possible here to leverage image and layer caching. Avoid including project-specific tools here. Language-specific runtimes may be added here or in a Dev Container feature. -->
+
 - **Development containers**
   - more about devcontainers...
 
+- **Startup scripts**
+  -
+
 <children></children>
