Bump Theme 5.18.0

Author: russfeld

.github/workflows/gh-pages.yml

@@ -26,7 +26,7 @@ jobs:
           # extended: true
 
       - name: Build
-        run: hugo --config github.toml
+        run: hugo -b "https://ksu-cs-textbooks.github.io/cc410/"
 
       - name: Deploy
         uses: peaceiris/actions-gh-pages@v3

.gitlab-ci.yml

@@ -1,50 +1,50 @@
-image: docker:20.10.11
+# image: docker:20.10.11
 
-variables:
-  # When using dind service, you must instruct docker to talk with the
-  # daemon started inside of the service. The daemon is available with
-  # a network connection instead of the default /var/run/docker.sock socket.
-  #
-  # The 'docker' hostname is the alias of the service container as described at
-  # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services
-  #
-  # If you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier,
-  # the variable must be set to tcp://localhost:2375 because of how the
-  # Kubernetes executor connects services to the job container
-  # DOCKER_HOST: tcp://localhost:2375
-  #
-  DOCKER_HOST: tcp://docker:2375
-  #
-  # This instructs Docker not to start over TLS.
-  DOCKER_TLS_CERTDIR: ""
-  # 
-  # Checkout submodules recursively
-  GIT_SUBMODULE_STRATEGY: recursive
+# variables:
+#   # When using dind service, you must instruct docker to talk with the
+#   # daemon started inside of the service. The daemon is available with
+#   # a network connection instead of the default /var/run/docker.sock socket.
+#   #
+#   # The 'docker' hostname is the alias of the service container as described at
+#   # https://docs.gitlab.com/ee/ci/docker/using_docker_images.html#accessing-the-services
+#   #
+#   # If you're using GitLab Runner 12.7 or earlier with the Kubernetes executor and Kubernetes 1.6 or earlier,
+#   # the variable must be set to tcp://localhost:2375 because of how the
+#   # Kubernetes executor connects services to the job container
+#   # DOCKER_HOST: tcp://localhost:2375
+#   #
+#   DOCKER_HOST: tcp://docker:2375
+#   #
+#   # This instructs Docker not to start over TLS.
+#   DOCKER_TLS_CERTDIR: ""
+#   # 
+#   # Checkout submodules recursively
+#   GIT_SUBMODULE_STRATEGY: recursive
 
-services:
-  - docker:20.10.11-dind
+# services:
+#   - docker:20.10.11-dind
 
-before_script:
-  - docker info
-  - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
+# before_script:
+#   - docker info
+#   - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY
 
-build-latest:
-  stage: build
-  only:
-    - tags
-  script:
-    - docker pull $CI_REGISTRY_IMAGE:latest || true
-    - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
-    - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
-    - docker push $CI_REGISTRY_IMAGE:latest
-
-# build-branches:
+# build-latest:
 #   stage: build
-#   except:
-#     - master
-#     - main
+#   only:
+#     - tags
 #   script:
-#     - docker pull $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH || true
-#     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH .
+#     - docker pull $CI_REGISTRY_IMAGE:latest || true
+#     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:latest .
 #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
-#     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH
+#     - docker push $CI_REGISTRY_IMAGE:latest
+
+# # build-branches:
+# #   stage: build
+# #   except:
+# #     - master
+# #     - main
+# #   script:
+# #     - docker pull $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH || true
+# #     - docker build --cache-from $CI_REGISTRY_IMAGE:latest --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA --tag $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH .
+# #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
+# #     - docker push $CI_REGISTRY_IMAGE:$CI_COMMIT_BRANCH

config.toml

@@ -20,7 +20,7 @@ theme = "hugo-theme-relearn"
 # TELE - Teleprompter
 # EMBED - Embeddable Version
 [outputs]
-  home = ["HTML", "RSS", "PRINT", "JSON"]
+  home = ["HTML", "RSS", "PRINT", "SEARCH", "SEARCHPAGE"]
   section = ["HTML", "RSS", "PRINT", "TELE", "EMBED"]
   page = ["HTML", "RSS", "PRINT", "TELE", "EMBED"]
 
@@ -87,7 +87,9 @@ theme = "hugo-theme-relearn"
   # this can be overridden in the pages frontmatter
   ordersectionsby = "weight"
   # Change default color scheme with a variant one. Eg. can be "red", "blue", "green" or an array like [ "blue", "green" ].
-  themeVariant = ["light-theme", "dark-theme"]
+  themeVariant = ["auto", "light-theme", "dark-theme"]
+  # The first element is the variant for light mode, the second for dark mode
+  themeVariantAuto = ["light-theme", "dark-theme"]
   # Change the title separator. Default to "::".
   # titleSeparator = "-"
   # If set to true, the menu in the sidebar will be displayed in a collapsible tree view.

content/00-introduction/_index.md

@@ -2,12 +2,9 @@
 title = "Introduction"
 date = 2020-12-08T00:53:05-05:00
 weight = 3
-chapter = true
+archetype = "chapter"
+ordinal = "0"
 pre = "<b>0. </b>"
 +++
 
-### Chapter 0
-
-# Introduction
-
 Welcome to CC 410!

content/_index.md

@@ -1,10 +1,8 @@
 +++
-title = "CC 410 Textbook"
-date = 2021-08-17
+title = "CC 410 - Advanced Programming"
+archetype = "home"
 +++
 
-# CC 410 - Advanced Programming
-
 This is the textbook for **CC 410 - Advanced Programming**.
 
 **Course Description:** Advanced programming techniques and projects. Concepts from simulation and modeling, media applications, secure design, information management, parallelism, and networking. Software development methodologies, processes, and design patterns. Practical experience with professional communication and collaboration.

content/i-oop/01-hello-real-world/_index.md

@@ -2,12 +2,9 @@
 title = "Hello Real World"
 date = 2020-12-28T00:53:05-05:00
 weight = 5
-chapter = true
+archetype = "chapter"
+ordinal = "1"
 pre = "<b>1. </b>"
 +++
 
-### Chapter 1
-
-# Hello Real World
-
 Hello World, but like the pros do it!

content/i-oop/02-object-oriented-programming/05-structs.md

@@ -7,15 +7,15 @@ Many object-oriented languages, such as C++ and C#, include the concept of a **s
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 double[] vector = {3.0, 4.0, 5.0};
 ```
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 vector: List[float] = [3.0, 4.0, 5.0]
@@ -29,7 +29,7 @@ However, other than the variable name, there is no indication to other programme
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 public double dotProduct(double[] a, double[] b){
@@ -41,7 +41,7 @@ public double dotProduct(double[] a, double[] b){
 ```
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 def dot_product(a: List[float], b: List[float]) -> float:
@@ -58,7 +58,7 @@ A struct provides a much cleaner option, by allowing us to define a type that is
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 public class Vector3{
@@ -76,7 +76,7 @@ public class Vector3{
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 class Vector3:
@@ -95,7 +95,7 @@ Then, our dot product method can take two arguments of the `Vector3` type:
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 public double dotProduct(Vector3 a, Vector3 b){
@@ -105,7 +105,7 @@ public double dotProduct(Vector3 a, Vector3 b){
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 def dot_product(a: Vector3, b: Vector3) -> float:

content/i-oop/02-object-oriented-programming/06-modules.md

@@ -7,15 +7,15 @@ It might seem like the kind of modules that Parnas was describing don't exist in
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 Math.sqrt(9.5);
 ```
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 math.sqrt(9.5)
@@ -30,7 +30,7 @@ We can define our own module-like classes by making them `static`, i.e. we could
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 import java.lang.Math;
@@ -57,7 +57,7 @@ System.out.println(VectorMath.magnitude(vect1));
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 import math

content/i-oop/02-object-oriented-programming/07-state-behavior/_index.md

@@ -52,7 +52,7 @@ On the other hand, with encapsulation we can reason about state and behavior on
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 public static Vector3 scale(Vector3 vec, double scale){
@@ -65,7 +65,7 @@ public static Vector3 scale(Vector3 vec, double scale){
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 @staticmethod

content/i-oop/02-object-oriented-programming/08-classes-objects.md

@@ -17,7 +17,7 @@ Let's re-write our `Vector3` struct using this concept.
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 public class Vector3{
@@ -45,7 +45,7 @@ public class Vector3{
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 class Vector3:
@@ -78,7 +78,7 @@ We can create as many objects from this class definition as we might want. Each
 
 {{< tabs >}}
 
-{{% tab name="Java" %}}
+{{% tab title="Java" %}}
 
 ```java
 Vector3 one = new Vector3(1.0, 1.0, 1.0);
@@ -88,7 +88,7 @@ Vector3 a = new Vector3(5.4, -21.4, 3.11);
 
 {{% /tab %}}
 
-{{% tab name="Python" %}}
+{{% tab title="Python" %}}
 
 ```python
 one: Vector3 = Vector3(1.0, 1.0, 1.0)