Hide Guides navigation (#180)

Katie Horne · web-flow · commit a078b86613fc · 2021-03-22T15:15:36.000-05:00
diff --git a/guides/admin/helm-charts.md b/guides/admin/helm-charts.md
diff --git a/guides/admin/index.md b/guides/admin/index.md
@@ -0,0 +1,6 @@
+---
+title: "Admin Guides"
+description: Learn about admin tasks for Coder.
+---
+
+<children></children>
diff --git a/guides/admin/resources.md b/guides/admin/resources.md
@@ -23,7 +23,7 @@ each machine would see 100% utilization of its resources. However, these
 processes are relatively quick, so the machine is underutilized the vast
 majority of the time.
 
-![resources-nonshared.svg](../assets/resources-old.svg)
+![resources-nonshared.svg](../../assets/resources-old.svg)
 
 However, sharing resources can allow you to provide your developers with access
 to the computing resources while minimizing underutilization.
@@ -35,7 +35,7 @@ resources they need during peak load (e.g., compilation, build); this offers
 them a performant experience when required. However, the shared resources
 minimize resource underutilization.
 
-![resources-shared.svg](../assets/resources-new.svg)
+![resources-shared.svg](../../assets/resources-new.svg)
 
 ## Resource Contention
 
@@ -60,4 +60,4 @@ compute costs:
 - The Coder organization's environment inactivity shutdown threshold
 - The magnitude and frequency of code compilation operations
 
-![cpu_provision_ratio.png](../assets/cpu_provision_ratio.png)
+![cpu_provision_ratio.png](../../assets/cpu_provision_ratio.png)
diff --git a/guides/admin/usage-monitoring.md b/guides/admin/usage-monitoring.md
@@ -16,9 +16,9 @@ contention can result in the throttling of developer environments, while
 excessive underutilization suggests that you may be spending more on your cloud
 environment than necessary.
 
-![Monitoring CPU Utilization](../assets/compute-1.png)
+![Monitoring CPU Utilization](../../assets/compute-1.png)
 
-![Monitoring Memory Utilization](../assets/compute-2.png)
+![Monitoring Memory Utilization](../../assets/compute-2.png)
 
 There are several tools available to you to balance the tradeoff between
 environment performance and cloud cost. Read more about this on [compute
@@ -31,9 +31,9 @@ cluster resources to Coder's product-level resource identifiers. For example,
 the following chart tracks the CPU/Memory Limit Utilization of each environment
 container and labels them with the username and environment name identifiers:
 
-![Monitoring CPU Utilization by Environment and User](../assets/compute-3.png)
+![Monitoring CPU Utilization by Environment and User](../../assets/compute-3.png)
 
-![Monitoring Memory Utilization by Environment and User](../assets/compute-4.png)
+![Monitoring Memory Utilization by Environment and User](../../assets/compute-4.png)
 
 These views can help you track which users may require larger CPU allocations,
 enabling greater "burst-ability" under peak loads. However, remember that using
@@ -46,8 +46,8 @@ Monitoring the Coder control plane can help you maintain high uptime. For
 example, the following charts provide high-level insight into the state of the
 Coder API server:
 
-![Monitoring Log Event Severity](../assets/compute-5.png)
+![Monitoring Log Event Severity](../../assets/compute-5.png)
 
-![Monitoring API Status Codes](../assets/compute-6.png)
+![Monitoring API Status Codes](../../assets/compute-6.png)
 
-![Monitoring HTTP Latency](../assets/compute-7.png)
+![Monitoring HTTP Latency](../../assets/compute-7.png)
diff --git a/guides/customization/custom-env.md b/guides/customization/custom-env.md
@@ -18,10 +18,10 @@ Make sure that you've:
 - Given your image building tool the rights needed to push to a [Docker
   Registry](https://docs.docker.com/registry/introduction/) (e.g., [Docker
   Hub](https://hub.docker.com/))
-- (Optional) Configured [Dev URLs](../admin/devurls.md) for your deployment
+- (Optional) Configured [Dev URLs](../../admin/devurls.md) for your deployment
 
 Your Coder user account must have permissions to [import an
-image](../images/importing.md).
+image](../../images/importing.md).
 
 ## Step 1: Create a Development Image
 
@@ -197,7 +197,7 @@ yarn start
 ### Preview Your Application
 
 Once you've started your server, you can preview your application using the web
-browser of your choice (you must have [Dev URLs](../admin/devurls.md) enabled
+browser of your choice (you must have [Dev URLs](../../admin/devurls.md) enabled
 for this to work). To do so:
 
 1. On the Environment Overview of your Coder deployment, go to Dev URLs and
diff --git a/guides/customization/gitconfig.md b/guides/customization/gitconfig.md
@@ -11,14 +11,14 @@ Coder will create a global git configuration file located at `~/.gitconfig` in a
 newly created environments and set the user name and email address using the
 information associated with the user's Coder account.
 
-This step occurs before [coder/configure](https://coder.com/docs/images/configure)
-and [personalization](https://coder.com/docs/environments/personalization),
+This step occurs before [coder/configure](images/../../../images/configure.md)
+and [personalization](../../environments/personalization.md),
 which can be used to override the default `.gitconfig` created by Coder.
 If there's already a `.gitconfig` file, Coder will not recreate a default
 version when you rebuild an environment.
 
 We recommend that each Coder user set and modify their personal .gitconfig file
-using the [~/personalize script](../environments/personalization.md).
+using the [~/personalize script](../../environments/personalization.md).
 
 **Preferences defined using individual `.gitconfig` files take precedence over
 system-level settings.**
diff --git a/guides/customization/index.md b/guides/customization/index.md
@@ -0,0 +1,6 @@
+---
+title: "Customization Guides"
+description: Learn about tasks related to customizing Coder.
+---
+
+<children></children>
diff --git a/guides/customization/macos-keybinding.md b/guides/customization/macos-keybinding.md
@@ -16,4 +16,4 @@ To switch the keybindings:
 5. Use the **Keymap** toggle at the top to switch to **macOS**
 6. Click **OK** to save your changes and proceed
 
-![Configuring macOS Keybindings](../assets/macos-keybinding.png)
+![Configuring macOS Keybindings](../../assets/macos-keybinding.png)
diff --git a/guides/deployments/index.md b/guides/deployments/index.md
@@ -0,0 +1,6 @@
+---
+title: "Deployment Guides"
+description: Learn about tasks related to deploying Coder.
+---
+
+<children></children>
diff --git a/guides/deployments/keycloak.md b/guides/deployments/keycloak.md
@@ -11,7 +11,7 @@ Administration Guide's [Identity
 Brokering](https://www.keycloak.org/docs/latest/server_admin/#_identity_broker)
 section.
 
-![Identity Broker Process](../assets/SAML-process.png)
+![Identity Broker Process](../../assets/SAML-process.png)
 
 ## Step 1: Create a New Realm in Keycloak
 
@@ -53,7 +53,7 @@ to OIDC Bridge`.
 1. At this point, you should be able to open the **Application Configuration**
    backup on JumpCloud and export the IdP metadata to use with Keycloak.
 
-    ![Export SAML Metadata](../assets/SAML-config-2.png)
+    ![Export SAML Metadata](../../assets/SAML-config-2.png)
 
 1. On the **User Groups** tab, add the JumpCloud User Group(s) that need access
    to Coder.
@@ -68,51 +68,51 @@ to OIDC Bridge`.
     document](https://www.keycloak.org/docs/latest/server_admin/#saml-v2-0-identity-providers)
     provides additional information about adding a SAML 2.0 Identity Provider).
 
-    ![Keycloak Identity Providers](../assets/keycloak-identity-providers.png)
+    ![Keycloak Identity Providers](../../assets/keycloak-identity-providers.png)
 
 1. On the IdP configuration page, specify an **Alias** to use for your IdP
    provider.
 
 1. Scroll to the bottom of the configuration page and upload the IdP metadata
     you exported from JumpCloud.
 
-    ![Keycloak Metadata Import](../assets/keycloak-metadata-import.png)
+    ![Keycloak Metadata Import](../../assets/keycloak-metadata-import.png)
 
 ### Optional: Specify JumpCloud as the Default IdP
 
 1. Navigate to **Authentication**.
 
 2. Select the **Browser** flow from the dropdown in the top-left.
 
-    ![Default Identity Provider](../assets/keycloak-default-IdP.png)
+    ![Default Identity Provider](../../assets/keycloak-default-IdP.png)
 
 1. Find the **Identity Provider Redirector** row and click **Actions** >
    **Config**.
 
-    ![Identity Provider Redirector](../assets/keycloak-IdP-redirector.png)
+    ![Identity Provider Redirector](../../assets/keycloak-IdP-redirector.png)
 
 1. Set **Alias** and **Default Identity Provider** to the alias of the identity
    provider you created earlier.
 
-    ![Authenticator Config](../assets/keycloak-authenticator-config.png)
+    ![Authenticator Config](../../assets/keycloak-authenticator-config.png)
 
 ## Step 4: Configure the OpenID Connect (OIDC) Connector in Keycloak
 
 1. Navigate to **Clients** and click **Create**.
 
-    ![Create Client Connector](../assets/keycloak-create-client.png)
+    ![Create Client Connector](../../assets/keycloak-create-client.png)
 
 1. Add a new OIDC Client to point to your Coder deployment and click **Save**.
 
-    ![Add OIDC client](../assets/keycloak-add-client.png)
+    ![Add OIDC client](../../assets/keycloak-add-client.png)
 
 1. Once on the **Clients** configuration page, set the **Access Type** to
    **Confidential** and click **Save**.
 
 1. Your client configuration should look something like the following (make sure
    that all of the values point to your Coder deployment):
 
-    ![Client Configuration](../assets/keycloak-client-config.png)
+    ![Client Configuration](../../assets/keycloak-client-config.png)
 
 At this point, you can configure your Coder deployment to use the Keycloak OIDC
    Connector.
@@ -128,12 +128,12 @@ At this point, you can configure your Coder deployment to use the Keycloak OIDC
 1. Add the **Secret** to the **Client Secret** field (you can get this value
    from the **Credentials** page in the Keycloak Clients Configuration).
 
-    ![Keycloak Secret](../assets/keycloak-secret.png)
+    ![Keycloak Secret](../../assets/keycloak-secret.png)
 
 1. Add your Keycloak instance and Realm as the `Issuer`. This will be a URL
     formatted as follows: `https://<my-keycloak-url>/auth/realms/<my-realm>`
 
-    ![Coder Keycloak Config](../assets/keycloak-coder-config.png)
+    ![Coder Keycloak Config](../../assets/keycloak-coder-config.png)
 
 1. Click **Save Preferences**.
 
diff --git a/guides/deployments/nightly-releases.md b/guides/deployments/nightly-releases.md
@@ -111,5 +111,5 @@ release.
 
 If your currently installed nightly version is sufficiently older than a
 standard release (i.e., more than a week older), consider
-[upgrading](../setup/updating.md) from the nightly release to the standard
+[upgrading](../../setup/updating.md) from the nightly release to the standard
 release.
diff --git a/guides/deployments/teardown.md b/guides/deployments/teardown.md
@@ -6,10 +6,10 @@ description: Learn how to tear down Coder and the infrastructure on which it's d
 This guide shows you how to tear down Coder and the cluster it is deployed on.
 
 > These instructions help you remove infrastructure created when following our
-[Kubernetes setup tutorials](../setup/kubernetes/index.md). They do not include
-teardown steps for any additional resources that you create.  If you need to keep
-your cluster, you can run `helm uninstall coder`, which deletes all Coder
-services but retains environments and their associated disk space.
+[Kubernetes setup tutorials](../../setup/kubernetes/index.md). They do not
+include teardown steps for any additional resources that you create.  If you
+need to keep your cluster, you can run `helm uninstall coder`, which deletes all
+Coder services but retains environments and their associated disk space.
 
 ## Amazon Elastic Kubernetes Service (EKS)
 
diff --git a/guides/index.md b/guides/index.md
@@ -1,7 +1,7 @@
 ---
 title: "Guides"
 icon: "<svg viewBox=\"0 0 16 16\" xmlns=\"http://www.w3.org/2000/svg\">\n<path d=\"M4 6H2v14c0 1.1.9 2 2 2h14v-2H4V6zm16-4H8c-1.1 0-2 .9-2 2v12c0 1.1.9 2 2 2h12c1.1 0 2-.9 2-2V4c0-1.1-.9-2-2-2zm0 10l-2.5-1.5L15 12V4h5v8z\" />\n</svg>"
-description: Learn about Coder customization and advanced use cases.
+description: Coder customization and advanced use cases.
 ---
 
 <children><children>
diff --git a/guides/mobile-development/index.md b/guides/mobile-development/index.md
@@ -16,7 +16,7 @@ developed remotely on Coder.
    local machine.
 
 1. Start Android Studio, and when prompted, install the SDK. ![Android SDK
-   Install](../assets/android-sdk-missing.png)
+   Install](../../assets/android-sdk-missing.png)
 
 1. [Create and start](https://developer.android.com/studio/run/managing-avds) a
    Virtual Device. ![Android Device](../assets/android-avd.png)
@@ -25,7 +25,7 @@ developed remotely on Coder.
    installation path of your Android SDK (for example, it's typically
    `~/Library/Android/sdk` on macOS and
    `C:\Users\<USER_NAME>\AppData\Local\Android\sdk` on Windows). ![Android SDK
-   Path](../assets/android-sdk-path.png)
+   Path](../../assets/android-sdk-path.png)
 
 1. Start the Android Debug Server on port 5555:
 
@@ -42,7 +42,7 @@ developed remotely on Coder.
   ```
 
    Alternatively, you can import or extend [Coder's
-   image](https://github.com/cdr/enterprise-images/blob/master/images/android/Dockerfile.ubuntu).
+   image](https://github.com/cdr/enterprise-images/blob/master/images/android/Dockerfile.ubuntu))
 
 1. Forward your Android Debug Server to the remote environment:
 
diff --git a/manifest.json b/manifest.json
@@ -109,24 +109,48 @@
     },
     {
       "path": "./guides/index.md",
+      "navigable": false,
       "children": [
+        { 
+          "path": "./guides/admin/index.md",
+          "navigable": false,
+          "children": [
+            { "path": "./guides/admin/resources.md" },
+            { "path": "./guides/admin/usage-monitoring.md" },
+            { "path": "./guides/admin/helm-charts.md" }
+          ]
+        },
+        {
+          "path": "./guides/customization/index.md",
+          "navigable": false,
+          "children": [
+            { "path": "./guides/customization/custom-env.md" },
+            { "path": "./guides/customization/gitconfig.md" },
+            { "path": "./guides/customization/macos-keybinding.md" }
+          ]
+        },
+        {
+          "path": "./guides/deployments/index.md",
+          "navigable": false,
+          "children": [
+            { "path": "./guides/deployments/nightly-releases.md" },
+            { "path": "./guides/deployments/keycloak.md" },
+            { "path": "./guides/deployments/teardown.md" }
+          ]
+        },
         { "path": "./guides/ssl-certificates/index.md",
+          "navigable": false,
           "children": [
             { "path": "./guides/ssl-certificates/cloudflare.md" },
             { "path": "./guides/ssl-certificates/route53.md" }
           ]
         },
-        { "path": "./guides/resources.md" },
-        { "path": "./guides/custom-env.md" },
-        { "path": "./guides/gitconfig.md" },
-        { "path": "./guides/helm-charts.md" },
-        { "path": "./guides/macos-keybinding.md" },
-        { "path": "./guides/mobile-development.md" },
-        { "path": "./guides/nightly-releases.md" },
-        { "path": "./guides/api.md" },
-        { "path": "./guides/keycloak.md" },
-        { "path": "./guides/teardown.md" },
-        { "path": "./guides/usage-monitoring.md" }
+        { "path": "./guides/mobile-development/index.md",
+          "navigable": false
+        },
+        { "path": "./guides/api.md",
+          "navigable": false
+        }
       ]
     },
     {
