Updated JupyterHub logo and link. Fixed info box layouts and added vu…

…lnerability scanner page
NCAR · Nov 8, 2024 · 0abccc7 · 0abccc7
1 parent 2f4c6be
commit 0abccc7
Show file tree

Hide file tree

Showing 4 changed files with 14 additions and 17 deletions.
diff --git a/docs/compute-systems/cirrus/slas.md b/docs/compute-systems/cirrus/slas.md
@@ -25,9 +25,8 @@ Regular: Basic functionality is present. There is a failure of extended function
 
 ### Agreements
 
-```{note}
-There is currently no After Hours support. All Response types that occur after hours will be addressed at the start of business.
-``` 
+!!! important
+    There is currently no After Hours support. All Response types that occur after hours will be addressed at the start of business. 
 
 | Response Level | Business Hours <br> 8:00 - 17:00 M-F | After Hours |
 |---|---|---|

diff --git a/docs/compute-systems/cirrus/users/hosting/additions.md b/docs/compute-systems/cirrus/users/hosting/additions.md
@@ -49,6 +49,6 @@ When automatically making changes to an application it's always best practice to
 
 [GitHub Actions](https://docs.github.com/en/actions) can be utilized to streamline the CI/CD pipeline for your application. For example, a [workflow](https://docs.github.com/en/actions/using-workflows/about-workflows) can be created that has [jobs](https://docs.github.com/en/actions/using-jobs/using-jobs-in-a-workflow) to build your container image, push it to a container registry, update your applications Helm chart with the new image details, and Argo CD will then automatically see the changes.
 
-```{warning}
-When tagging your container images avoid using the `:latest` tag. There's a number of different reasons for this but for CI/CD a primary one is that `:latest` never changes inside your applications Helm chart. If nothing changes there's nothing to synchronize and your application will not update. 
-```
+!!! important
+    When tagging your container images avoid using the `:latest` tag. There's a number of different reasons for this but for CI/CD a primary one is that `:latest` never changes inside your applications Helm chart. If nothing changes there's nothing to synchronize and your application will not update. 
+
diff --git a/docs/compute-systems/cirrus/users/jupyter/jupyterhub.md b/docs/compute-systems/cirrus/users/jupyter/jupyterhub.md
@@ -1,22 +1,20 @@
 # CIRRUS JupyterHub
 
+<div style="text-align:center">
+<a href="https://jupyter.k8s.ucar.edu/">
+<img src="https://ncar.github.io/cisl-cloud/_static/jhub-logo.png" 
+        alt="CIRRUS JupyterHub" 
+        style="display: block; margin: 0 auto" />
+CIRRUS JupyterHub</a>
+</div>
+
 ## Overview
 
 CIRRUS hosts a JupyterHub instance on Kubernetes (K8s). 
 
 !!! info
     The K8s JupyterHub is available inside the NCAR network only so you must either be ***onsite*** or connected to the ***VPN***.
 
-
-<span class="d-flex justify-content-center py-4">
-    <a href="https://jupyter.k8s.ucar.edu/">
-        <figure>
-            <img src="https://ncar.github.io/cisl-cloud/_static/jhub-logo.png">
-            <figcaption style="text-align:center">K8s JupyterHub</figcaption>
-        </figure>
-    </a>
-</span>
-
 ## Access
 The [JupyterHub Login](https://jupyter.k8s.ucar.edu/) page is the portal to enter and spin up a personal and persistent Jupyter environment. 
 

diff --git a/mkdocs.yml b/mkdocs.yml
@@ -148,7 +148,7 @@ nav:
       - Container Registry: 
             - compute-systems/cirrus/users/container-registry/index.md
             - Image Management: compute-systems/cirrus/users/container-registry/image-mgmt.md
-            - Vulnerability Scanner: compute-systems/cirrus/users/container-registry/vulnerability-scanner.md
+            - Vulnerability Scanner: compute-systems/cirrus/users/container-registry/vulnerability-scan.md
       - Jupyter: 
             - compute-systems/cirrus/users/jupyter/jupyterhub.md
             - Conda Environments: compute-systems/cirrus/users/jupyter/conda-envs.md