fix: upgrade gatsby from 5.14.1 to 5.14.3

Snyk has created this PR to upgrade gatsby from 5.14.1 to 5.14.3.

See this package in npm:
gatsby

See this project in Snyk:
https://app.snyk.io/org/mastermindzh/project/6eb54845-2bb5-45e0-80e2-6b3a1c53eee6?utm_source=github&utm_medium=referral&page=upgrade-pr

.github/workflows/release.yml

@@ -19,7 +19,7 @@ jobs:
       - name: Setup Node.js
         uses: actions/setup-node@v3
         with:
-          node-version: 16.14.0
+          node-version: 22.12.0
 
       - name: Install dependencies
         run: npm ci

.vscode/settings.json

@@ -1,15 +1,26 @@
 {
     "cSpell.words": [
+        "codepen",
         "disqus",
         "fontawesome",
         "fortawesome",
         "frontmatter",
-        "slsw"
+        "Lieshoutt",
+        "Rickvan",
+        "rickvanlieshoutcom",
+        "slsw",
+        "soundcloud",
+        "todos",
+        "weibo"
     ],
     "grammarly.selectors": [
         {
             "language": "markdown",
             "scheme": "file"
         }
-    ]
+    ],
+    "sonarlint.connectedMode.project": {
+      "connectionId": "public-sonarcloud",
+      "projectKey": "Mastermindzh_rickvanlieshout.com"
+    }
 }

CHANGELOG.md

@@ -2,6 +2,50 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+### [1.3.1](https://github.com/mastermindzh/rickvanlieshout.com/compare/v1.3.0...v1.3.1) (2023-10-29)
+
+
+### Bug Fixes
+
+* fixed tags and categories in several blog posts ([7019f34](https://github.com/mastermindzh/rickvanlieshout.com/commits/7019f340050c04eed6065c4ddd4582d6b2d22b9b))
+* now setting og:url correctly as well as the canonical url ([e065f16](https://github.com/mastermindzh/rickvanlieshout.com/commits/e065f16fb505eb8f9e5acef6f92c5a016e276ebc))
+* set current url tags in both ssr and browser space ([1c4c9d0](https://github.com/mastermindzh/rickvanlieshout.com/commits/1c4c9d058a7382ebe52dd1b188b22ca8d7a185c3))
+* several fixes to improve ahrefs site score ([8245e1f](https://github.com/mastermindzh/rickvanlieshout.com/commits/8245e1f0d8854cd6a727a8b837ee3259ee040d48))
+* upgrade gatsby from 5.12.1 to 5.12.3 ([043d08e](https://github.com/mastermindzh/rickvanlieshout.com/commits/043d08e58f9962688bd615b8e8d535e4111e7aa2))
+* upgrade gatsby from 5.12.3 to 5.12.4 ([f13f40d](https://github.com/mastermindzh/rickvanlieshout.com/commits/f13f40df35cc0230ddcf7766a7b2e73477696439))
+
+## [1.3.0](https://github.com/mastermindzh/rickvanlieshout.com/compare/v1.2.3...v1.3.0) (2023-09-23)
+
+
+### Features
+
+* added my public keys to a keys.json file in the root of the website ([8a2f19e](https://github.com/mastermindzh/rickvanlieshout.com/commits/8a2f19e8a9abec4a3529c08cd06cf7e042e67725))
+
+
+### Bug Fixes
+
+* 404 on lego.com page of removed product ([0dc9773](https://github.com/mastermindzh/rickvanlieshout.com/commits/0dc97732e81458b39cccc6c100516e05f245697f))
+* added links to orphaned categories and tags pages ([0e9946c](https://github.com/mastermindzh/rickvanlieshout.com/commits/0e9946c92eb5022961a9f457ce82636a60e0e9ee))
+* added opengraph tags ([e6ebd5b](https://github.com/mastermindzh/rickvanlieshout.com/commits/e6ebd5b79f17ac41e4e1954857da8cd8ab50224a))
+* **opengraph:** added mandatory opengraph tags to all pages. Also fixed some other minor bugs ([98a3eb7](https://github.com/mastermindzh/rickvanlieshout.com/commits/98a3eb71f55c17da7964d6c5014e599a459329e1))
+* package.json & package-lock.json to reduce vulnerabilities ([9dc1f62](https://github.com/mastermindzh/rickvanlieshout.com/commits/9dc1f6275fdd1f6fe5fd9485f554345a1df268ec))
+* remove noindex and noindex follow tags ([d72e301](https://github.com/mastermindzh/rickvanlieshout.com/commits/d72e30196df5ca6944ae6dde7b4417c9efeb38d3))
+* removed nofollow links to my own website ([bebfe16](https://github.com/mastermindzh/rickvanlieshout.com/commits/bebfe1638e9ef1dc35b0b0fd6e8907edd344951f))
+* several pages linked to redirected urls. This replaces those links with the destination instead ([b5126bf](https://github.com/mastermindzh/rickvanlieshout.com/commits/b5126bf051dcdfe7159d24eb2cddeb3f8e1ceee8))
+* solve 404 on front-thumb image ([5344b98](https://github.com/mastermindzh/rickvanlieshout.com/commits/5344b98f8e37fb661a1ec70aaba1c5ef92cfa370))
+* updated npm packages and pinned unist-util-find to 1.0.2 to fix build errors ([5ea6e0a](https://github.com/mastermindzh/rickvanlieshout.com/commits/5ea6e0a20f9c8aff33a9ae18143e6f8fd3634127))
+* upgrade gatsby-plugin-image from 3.11.0 to 3.12.0 ([05662d2](https://github.com/mastermindzh/rickvanlieshout.com/commits/05662d2c492ae70575947b9327d64fa642a63698))
+* upgrade multiple dependencies with Snyk ([cbaca6f](https://github.com/mastermindzh/rickvanlieshout.com/commits/cbaca6f4cd9ba9ff290fcb2ede5a81d8c0e3f285))
+* upgrade multiple dependencies with Snyk ([10cbe94](https://github.com/mastermindzh/rickvanlieshout.com/commits/10cbe94397c43f80ff28cb5c81126fc3af632547))
+* upgrade multiple dependencies with Snyk ([3ef5ca5](https://github.com/mastermindzh/rickvanlieshout.com/commits/3ef5ca570b05e0cbc6c670eb9df179b1be1dba9c))
+* upgrade multiple dependencies with Snyk ([46c12f8](https://github.com/mastermindzh/rickvanlieshout.com/commits/46c12f8c98ab8beb7b6be040fa73761eb73b2dd9))
+
+
+### New content
+
+* A new blog about the LegoLeague event held at INFORIT ([4e6b042](https://github.com/mastermindzh/rickvanlieshout.com/commits/4e6b042a44d9a9f5d68dba653c1472be80d21ce9))
+* **legoleague:** fixed some writing ([92245be](https://github.com/mastermindzh/rickvanlieshout.com/commits/92245be1883f7e136dae7888a64a472cf6597180))
+
 ### [1.2.3](https://github.com/mastermindzh/rickvanlieshout.com/compare/v1.2.2...v1.2.3) (2023-04-19)
 
 ### Bug Fixes

README.md

@@ -1,6 +1,6 @@
 # Rickvanlieshout.com
 
-This is the repository for my personal blog/website [rickvanlieshout.com](https://rickvanlieshout.com).
+This is the repository for my personal blog/website [rickvanlieshout.com](https://www.rickvanlieshout.com).
 
 [![Build Status](https://ci.mastermindzh.tech/api/badges/Mastermindzh/rickvanlieshout.com/status.svg)](https://ci.mastermindzh.tech/Mastermindzh/rickvanlieshout.com)
 

categories.list.md

@@ -7,8 +7,8 @@ A list of categories used in the blog
 | ----------- | -------------------------------------------------------- |
 | blog        | random blog stuff                                        |
 | IOT         | anything to do with IOT                                  |
-| Homelab     | anything to do with my homelab (including smart home...) |
-| Development | anything to do with regular development                  |
+| homelab     | anything to do with my homelab (including smart home...) |
+| development | anything to do with regular development                  |
 | exploits    | blogs about exploits and bugs in open-source software    |
-| Lego        | blogs about Lego                                         |
+| lego        | blogs about Lego                                         |
 | house       | Content about the place I live                           |

content/config.json

@@ -46,7 +46,7 @@
   "author": {
     "name": "Rick van Lieshout",
     "photo": "/content/me.png",
-    "bio": "I'm a passionate software architect that bifurcates his love between great software development and leading others to learn and adopt new things.",
+    "bio": "I'm a passionate CTO who bifurcates his love between great software development and leading others in their continuous improvement journeys",
     "contacts": {
       "email": "info@rickvanlieshout.com",
       "github": "mastermindzh",

content/pages/resume/index.md

@@ -20,14 +20,14 @@ template: "page"
 _Always_<br />
 A fair share of my private work is done through open-source media. I don't have a portfolio but I have a [Github](https://github.com/mastermindzh) where I share most things.
 
-**Tech lead / CTO at INFORIT**<br />
+**CTO at Frontliners (previously INFORIT)**<br />
 _2018 - Now_<br />
-At INFORIT I am responsible for the entire technical architecture of the new TFX stack that I launched shortly after 2018. This involves setting up and maintaining a modern event-based microservice architecture on a Kubernetes-based SaaS cloud solution and migrating to modern programming languages such as dotnetcore and React.
+At Frontliners I am responsible for the entire technical architecture of the new TFX stack that I launched shortly after 2018. This involves setting up and maintaining a modern event-based microservice architecture on a Kubernetes-based SaaS cloud solution and migrating to modern programming languages such as dotnetcore and React.
 
 The other main responsibility I have is creating and maintaining a coherent team of lead developers by sharing knowledge, making decisions, and empowering leads to explore technologies outside of their comfort zone.
 
-At INFORIT I also help with the recruitment of new employees, setting up and maintaining agile strategies including proper test management, and general software development.
-During my time at INFORIT, we've grown from 5-7 in-house developers to 10, full-sized, SCRUM teams.
+At Frontliners I also help with the recruitment of new employees, setting up and maintaining agile strategies including proper test management, and general software development.
+During my time at Frontliners, we've grown from 5-7 in-house developers to 10, full-sized, SCRUM teams.
 
 Most relevant technologies used: dotnetcore, React, Angular, Kafka, RabbitMQ, Mongo, PostgreSQL, Growthbook, Docker & Kubernetes
 
@@ -64,6 +64,7 @@ Building an interactive and fully customizable dashboard on top of VAA's existin
 I'll list some of the training courses I've had whilst working.
 Some of these have (official) certificates, some don't, but all have brought value and knowledge.
 
+- Young Executive Program (YEP) - [De Baak](https://debaak.nl/trainingen/young-executives-program)
 - Hiring & interview training ([icm.nl](https://www.icm.nl/opleidingen-en-trainingen/hrm/selectiegesprekken-voeren/))
 - Conversation techniques & de-escalation ([TIJDwinst.com](https://gesprekstechnieken.com/cursus-gesprekstechnieken/)](<https://gesprekstechnieken.com/cursus-gesprekstechnieken/>)).
 - Kubernetes (NobleProg Certification Kubernetes on Azure (AKS), 26 August 2019 - 27 August 2019)

content/posts/2014/pi-cluster-1-shopping/index.md

@@ -2,7 +2,7 @@
 title: "Raspberry pi cluster Step 1: Shopping"
 date: "2014-09-05 23:00"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "raspberry"
   - "cluster"

content/posts/2014/pi-cluster-2-the-build/index.md

@@ -2,7 +2,7 @@
 title: "Raspberry pi cluster Step 2: Assembling the hardware"
 date: "2014-09-10"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "raspberry"
   - "cluster"
@@ -14,7 +14,7 @@ socialImage: "./media/improvising.jpg"
 
 So today I finally received the required parts to finish up my Raspberry pi cluster and I was **extremely** excited! To share this excitement with you lot here's a picture of all the parts I'll be using:
 
-![picture of all the parts spread on the mat](./media/pi_overview_full.JPG "all the bits!")
+![picture of all the parts spread on the mat](./media/pi_overview_full.jpg "all the bits!")
 
 I began by building the Raspberry pi "tower", sadly I forgot to take a picture with the DSLR so I only have this one cell image to show you guys:
 

content/posts/2014/pi-cluster-3-installing-the-os/index.md

@@ -2,7 +2,7 @@
 title: "Raspberry pi cluster Step 3: Installing the OS"
 date: "2014-09-14"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "raspberry"
   - "cluster"

content/posts/2014/pi-cluster-4-setting-up-the-master-node/index.md

@@ -2,7 +2,7 @@
 title: "Raspberry pi cluster Step 4: Setting up the master node"
 date: "2014-09-17"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "raspberry"
   - "cluster"

content/posts/2014/pi-cluster-5-expanding-the-cluster/index.md

@@ -2,14 +2,14 @@
 title: "Raspberry pi cluster step 5: Expanding the cluster"
 date: "2014-09-19"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "raspberry"
   - "cluster"
   - "pi"
 description: "Today's blog post will be about expanding the cluster with more nodes."
 disqusId: "6"
-socialImage: "./media/pidark_full.JPG"
+socialImage: "./media/pidark.jpg"
 ---
 
 In today's post we'll have a look at expanding the cluster with more nodes! We will have a look at how to clone them and how we can set up a universal login using ssh keys.
@@ -40,7 +40,7 @@ sudo nano /etc/network/interfaces
 
 After setting up all 4 pi's and plugging it all in you should see all 4 led's light up on the pi's. If this is not the case you might've forgotten to change either the ip address or the hostname. (which will lead to a conflict resulting in one of them not having internet access). Mine now looks like this (note the dramatic night picture taken at 10 past 12 am):
 
-![picture of 4 Raspberry pi's stacked on a network switch serving as a cluster](./media/pidark_full.JPG "It's not quite RGB but it's beautiful!")
+![picture of 4 Raspberry pi's stacked on a network switch serving as a cluster](./media/pidark.jpg "It's not quite RGB but it's beautiful!")
 
 ## Logging in to the nodes with ssh keys
 

content/posts/2014/using-the-cluster-for-home-automation/index.md

@@ -2,12 +2,12 @@
 title: "The pi cluster, home automation & kickstarter monitoring"
 date: "2014-09-27"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "python"
   - "raspberry"
   - "pi"
-  - "home automation"
+  - "home-automation"
 description: "Today's blog is about home automation."
 disqusId: "7"
 ---

content/posts/2015/making-things/index.md

@@ -50,7 +50,7 @@ We also started working on the controllers. The final design will be compromised
 ![back](./media/back.jpg "Back of the controller")
 ![bottom](./media/bottom.jpg "bottom of the controller")
 ![controller_pot](./media/controller_pot.jpg "potentiometer used inside the controller")
-![front](./media/Front_thumb.png "The front of the controller with the logo")
+![front](./media/front-thumb.png "The front of the controller with the logo")
 ![inside](./media/inside.jpg "the inside of an assembled controller")
 ![left_side](./media/left_side.jpg "The left side of the controller")
 ![right_side](./media/right_side.jpg "The right side of the controller")

content/posts/2015/tektree-part-3-wiring/index.md

@@ -11,23 +11,23 @@ disqusId: "17"
 socialImage: "./media/wiring1.jpg"
 ---
 
-In the 3rd part of my TekTree project I'll show you guys how to wire everything. This time I even used separate colours for the power,ground and signal wires. So no more complaining ! ^\_^ All in all I think the result looks absolutely wicked. Even without the arduino case which has yet to come in the mail. (and probably won't fit)
+In the 3rd part of my TekTree project I'll show you guys how to wire everything. This time I even used separate colours for the power, ground and signal wires. So no more complaining! ^\_^ All in all I think the result looks absolutely wicked. Even without the Arduino case which has yet to come in the mail. (and probably won't fit)
 
 ## Wiring part 1 - schematics
 
-Before I started to jam wires in every nook and cranny I could find I had to come up with a plan. Most of that plan has been put into a "Fritzing" sketch which can be found below and on [Github](https://github.com/Mastermindzh/TekTree). The only thing I couldn't figure out how to model on fritzing is the actual christmas tree and the power cord for the arduino.
+Before I started to jam wires in every nook and cranny I could find I had to come up with a plan. Most of that plan has been put into a "Fritzing" sketch which can be found below and on [Github](https://github.com/Mastermindzh/TekTree). The only thing I couldn't figure out how to model on fritzing is the actual Christmas tree and the power cord for the Arduino.
 
-The arduino will get power from a regular adaptor. The only modification I did to the adapter is putting a button on one of the wires. And the only reason I did that is because I'm too lazy to unplug the TekTree when I want to turn it off :)
+The Arduino will get power from a regular adaptor. The only modification I made to the adapter was putting a button on one of the wires. The only reason I did that is because I'm too lazy to unplug the TekTree when I want to turn it off :)
 
 ![Wiring of the back of the Tektree. You can see a lot of jumper wires sticking out and connecting to LEDs](./media/wiring1.jpg)
 
 ## Why so many wires?
 
-I want the project to be "manageable" for everyone. To do this I kept the wiring as simple as possible. Every LED has 2 prongs, 1 goes to ground 1 goes to the arduino. Simple. Same goes for the potentiometers, 3 legs, 1 power 1 ground 1 signal. The only led's I did bundle together (in terms of wiring) is the star. I did this to create a single star instead of multiple led's.
+I want the project to be "manageable" for everyone. To do this I kept the wiring as simple as possible. Every LED has 2 prongs, 1 goes to ground 1 goes to the Arduino. Simple. Same goes for the potentiometers, 3 legs, 1 power 1 ground 1 signal. The only leds I did bundle together (in terms of wiring) is the star. I did this to create a single star instead of multiple led's.
 
 ## Well you could've made it way prettier... and
 
-Well yes, as all of us know I'm perfectly capable of designing a [refined build](/images/blogs/han4pi/Front_thumb.png). I didn't want to go with a pcb this time however because that would make the barrier to entry way higher on this project. And that is something I definitely **don't** want.
+Well yes, as all of us know I'm perfectly capable of designing a [refined build](/images/blogs/han4pi/front.png). I didn't want to go with a pcb this time however because that would make the barrier to entry way higher on this project. And that is something I definitely **don't** want.
 
 I also didn't "group" all my ground wires together. (led -> led -> led -> board) This would've made the project a lot neater but it wouldn't be anywhere near as service friendly. (which was kinda the idea...)
 

content/posts/2017/scala-day-0-what-is-scala/index.md

@@ -3,9 +3,9 @@ title: Scala Day 0 - What is Scala?
 date: "2017-03-30"
 template: "post"
 draft: false
-category: "Development"
+category: "development"
 tags:
-  - "Development"
+  - "development"
   - "slsw"
 description: "My final assignment for a school course is to learn a new language from a book (uh-oh). I picked Scala and here's why"
 disqusId: "20"

content/posts/2017/scala-day-1-the-basics/index.md

@@ -3,9 +3,9 @@ title: Scala Day 1 - The Basics
 date: "2017-04-02"
 template: "post"
 draft: false
-category: "Development"
+category: "development"
 tags:
-  - "Development"
+  - "development"
   - "slsw"
 description: "Let's take a deep dive into a programming book and Scala!"
 disqusId: "21"

content/posts/2017/scala-day-2-lets-get-functional/index.md

@@ -3,9 +3,9 @@ title: Scala Day 2 - Let's get functional
 date: "2017-04-03"
 template: "post"
 draft: false
-category: "Development"
+category: "development"
 tags:
-  - "Development"
+  - "development"
   - "slsw"
 description: "Today we'll focus on the functional aspects of Scala"
 disqusId: "22"

content/posts/2017/scala-day-3-concurrency-is-key/index.md

@@ -3,9 +3,9 @@ title: Scala Day 3 - Concurrency is key!
 date: "2017-04-04"
 template: "post"
 draft: false
-category: "Development"
+category: "development"
 tags:
-  - "Development"
+  - "development"
   - "slsw"
 description: "A day full of functional joy and concurrency "
 disqusId: "23"

content/posts/2017/scala-day-4-a-challenge/index.md

@@ -3,9 +3,9 @@ title: Scala Day 4 - A challenge!
 date: "2017-04-05"
 template: "post"
 draft: false
-category: "Development"
+category: "development"
 tags:
-  - "Development"
+  - "development"
   - "slsw"
 description: "The last day of my journey with Scala is said to be a challenge"
 disqusId: "24"

content/posts/2022/adopting-convential-commits/index.md

@@ -2,13 +2,13 @@
 title: Adopting conventional commits and standard versions in a git and npm codebase
 date: "2022-11-07"
 template: "post"
-category: "Development"
+category: "development"
 tags:
   - "git"
-  - "conventional commits"
-  - "semantic commits"
-  - "INFORIT"
-  - "Standard releases"
+  - "conventional-commits"
+  - "semantic-commits"
+  - "inforit"
+  - "standard-releases"
 
 description: "A dive into conventional commits and their benefit whilst releasing with standard versions."
 socialImage: "./media/husky-error.png"
@@ -340,7 +340,7 @@ Now, let's add a Husky git hook to combat future commits that are unconventional
 npx husky-init && npm install
 ```
 
-This will automatically create the `.husky/pre-commit` file. Let's edit it and add commitlint:
+This will automatically create the `.husky/` directory. Let's create a file in it called `commit-msg` and add commitlint:
 
 ```sh
 #!/usr/bin/env sh

content/posts/2023/flashing-lsi-9211-with-efi/index.md

@@ -2,14 +2,14 @@
 title: Flashing the LSI-9211 to IT mode using an EFI shell
 date: "2023-04-12"
 template: "post"
-category: "Homelab"
+category: "homelab"
 tags:
   - "lsi"
   - "lsi9211"
   - "raid card"
   - "storage"
   - "SAS2000"
-  - "it mode"
+  - "it-mode"
 description: "Flashing the LSI-9211 used to be way more difficult, luckily the EFI shell makes this task a lot simpler!"
 socialImage: ./media/flash-result.jpg
 ---

content/posts/2023/lego-league/index.md

@@ -0,0 +1,98 @@
+---
+title: LegoLeague - Battling it out with little robots made from Lego
+date: "2023-09-18"
+template: "post"
+category: "Lego"
+tags:
+  - "lego"
+  - "spike"
+  - "programming"
+  - "team"
+  - "work"
+  - "inforit"
+description: "At INFORIT we love to play! Be it DND, board games or in this case... Legos. Read on to find out what we've been up to this past summer vacation"
+socialImage: ./media/lego-spike-set.png
+---
+
+![The 2023 LegoLeague play-mat laid out on an improvised table](./media/board.jpg "The 2023 LegoLeague battle board")
+
+A little before the start of the summer period my colleague Jan-Kees came up to me and proposed the idea of an internal LegoLeague. After a little bit of back-and-forth about what LegoLeague exactly was I agreed it would be a great idea to bring some colleagues together and have a little fun during work hours.
+Pretty much right away excitement got the better of us and we started drafting a plan... when? where? how? prizes? teams!?? A lot.
+But First...
+
+## What is LegoLeague?
+
+LegoLeague is an event where teams come together to build, program and test a [Lego Spike robot](https://www.lego.com/en-nl/product/lego-education-spike-prime-set-45678) to perform autonomous tasks. The tasks range from collecting "power cores", pushing or pulling levers, to dropping Lego blocks in a hopper to get some bonus points.
+
+All of this is accompanied by a theme, in our case energy production, which adds a layer of fun to solving these challenges.
+The video below shows a teaser of 2022-2023's "SuperPowered" event, the very thing we based our LegoLeague on:
+
+<iframe
+  width="560"
+  height="315"
+  src="https://www.youtube.com/embed/okR1AMFNV3Q?si=cq4KqyVVK6sAsCpY"
+  title="YouTube video player"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+  allowfullscreen>
+</iframe>
+
+For each task a team completes successfully they will score points.
+Teams get 2 minutes and 30 seconds (2:30) to score as many points as they can.
+The video below outlines some of the challenges the teams have available to them with a little explanation of how they function and even some info on the scores. This video is especially useful for teams that don't want to peruse the entire rule book but still wanted to figure out an optimal strategy.
+
+<iframe
+  width="560"
+  height="315"
+  src="https://www.youtube.com/embed/ILTjo0LHZQA?si=YqJvSYX3JNclPPeJ"
+  title="YouTube video player"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share"
+  allowfullscreen>
+</iframe>
+
+To build the robot each team gets a [Lego Spike Prime set](https://www.lego.com/nl-nl/product/lego-education-spike-prime-set-45678) and nothing more!
+In the original event, teams had access to a little more Lego in various kits but for our little event at [INFORIT](https://inforit.nl), we were only able to source the basic kits in time.
+Having said that, we wouldn't have been able to get our hands on any of the kits at all if it wasn't for the ["PReT" organization in Weesp](https://www.pretweesp.nl/). Thanks guys!
+
+![A Lego spike set](./media/lego-spike-set.png "A Lego spike set laid out on display")
+
+As for the programming... Teams are free to use either "[scratch](https://scratch.mit.edu/)" or "Python" to program their robots.
+Scratch being much easier for those who don't spend all day behind their computer working on software development whilst Python allows for more flexibility in what can be achieved.
+Spoiler alert: all teams chose scratch, it's much more accessible for non-developers!
+
+## The competition at INFORIT
+
+So yeah, we now know what a LegoLeague is and we have the approval to host the competition at [INFORIT](https://inforit.nl), now what?
+Well, Jan-Kees got to work building the arena and setting it up and I set out to gather team members. Given that it was the summer break I had to hustle to get teams together but eventually we managed to create some beautiful teams.
+
+Fortunately, [INFORIT](https://inforit.nl) values employee happiness, autonomy and continuous improvement. As such I was able to offer the 2 Friday afternoons free of day-to-day work, to work on the robot whilst providing catering, music, and the like to the teams whilst they are participating!
+
+In the end, we were successful in creating 4 teams of at least 3 people who were all mixed with developers and non-developers to keep the balance fair. Meanwhile, Jan-Kees also finished building the arena which you can see in the header of this blog or the pictures in the picture section.
+
+## Pictures
+
+Of course, we've taken loads of pictures during the event but those are mostly for internal use.
+Below I've included some pictures of the event that are all cleared for social media distribution with a little description of what's happening in each picture to, hopefully, convey some of the vibes of the event itself.
+
+![One of the competing robots on display. This one seems to have a little grabby arm to perform the tasks with.](./media/robot-warrior.jpg "one of the competing robots")
+![A contestant is looking at the board figuring out where the robot needs to go](./media/lex-counting.jpg "A contestant calculating exactly where to go. Such a pathfinder!")
+![two teams continuing to test their implementations](./media/testing-coding-repeat.jpg "code -> test -> repeat. Soooo important")
+![a picture of a laptop screen with lots of scratch code blocks on it](./media/complicated.png "This team might have overcomplicated things a tad. Looks impressive though.")
+
+## Winners, losers, etc
+
+In the end, this is still a competition. People competed hard to come out on top and 1 team did so successfully.
+Congratulations guys!
+
+![a group picture of all the contestants, some wearing their medals and carrying their candy prize](./media/winners.jpg "All of our winners! (excluding myself 😢)")
+
+## Nah, we are all winners in the end
+
+Having 4 teams gave us the unique opportunity to reward them all with something nice. The 3 teams that got podium places all got their medals and their rewards and the team in fourth place got their consolation prize.
+
+Luckily though, we're all winners, even the Jury members and the organizers.
+This event has brought us all closer together and improved the connection between our colleagues.
+I, personally, had a blast and would love to do similar things in the future.
+
+That's it again, thanks for reading and see you next time!

content/posts/2023/starting-a-new-hobby-that-might-just-take-over-my-house/index.md

@@ -4,7 +4,7 @@ date: "2023-02-14"
 template: "post"
 category: "blog"
 tags:
-  - "Lego"
+  - "lego"
   - "house"
 description: "What started as a simple decoration piece to fill some empty space in my home quickly grew into a new hobby of which the remnants can be found throughout my house"
 socialImage: ./media/building-the-owl.jpg

content/posts/2025/infrastructure-as-code-uptime-monitoring/index.md

@@ -0,0 +1,130 @@
+---
+title: Infrastructure as code - Service uptime monitoring
+date: "2025-01-18"
+template: "post"
+category: "homelab"
+tags:
+  - "uptime"
+  - "kuma"
+  - "iac"
+  - "infrastructure"
+  - "code"
+  - "servers"
+description: "In this post I demonstrate how I've moved from an old and simple UptimeKuma setup to a setup with AutoKuma so I can register my monitors with 'infrastructure as code'"
+socialImage: ./media/uptimekuma.png
+---
+
+If there’s one thing I’ve always embraced, it’s the philosophy of working smarter, not harder. Infrastructure as Code (IaC) has been one of the cornerstones of my career. a perfect blend of laziness and the pursuit of predictability. From my earliest days experimenting with Docker back in 2014 to leading a platform team at my current company, IaC has proven invaluable for simplifying complexity, ensuring reproducibility, and enabling automation.
+
+Below you'll find my journey and why I think every engineer should embrace it, eventually walking you through one of the latest automations I set up at home: Automatically creating uptime monitors in UptimeKuma based on Docker labels.
+
+## The Early Days: Discovering Docker
+
+Back in 2014, I stumbled upon Docker, and it was a game-changer. At the time, I was frustrated by the manual and error-prone process of setting up environments for my code (especially on other people's machines....). Docker offered a way to reliably recreate these environments with simple, declarative configuration files. Suddenly, I could spin up a development environment in minutes and be confident it would work exactly the same on another machine.
+
+In 2017, I taught several university classes on Docker, emphasizing the importance of reproducibility. My students learned how to containerize applications and ensure their work could be shared and run anywhere, regardless of underlying infrastructure. Reproducibility wasn’t just a technical advantage; it became a mindset I encouraged in every project.
+
+And yes.. for those that know me well, I did go overboard in some of the details and even ended up explaining the entire Copy-On-Write (COW) nature of the Docker filesystem in those classes... But ah well, people learned a lot :P.
+
+## Home Servers: The Personal Lab
+
+My passion for IaC extended to my home servers. By 2017, nearly everything I ran at home was Docker-based. I created dozens of bash scripts and system services to orchestrate my personal infrastructure. Whether it was media servers, backup systems, or development environments, everything was automated and version-controlled. Even my own computers mostly became IaC based as I figured out that part of the Linux community was saving their setups (and install instructions, usually) in so called "dotfiles". To this day you can still find my setup (and its changes when I switch machine) in my [Dotfiles on Github](https://github.com/Mastermindzh/dotfiles/).
+
+All in all, my home setup became a sandbox for testing new ideas and tools, many of which eventually found their way into my professional work as well.
+
+## Scaling IaC in the Workplace
+
+At my current company, I introduced Docker about eight years ago. It was a gradual process, but within a year, we had our first Kubernetes cluster running. This transition wasn’t just about adopting new tools; it was about embedding the principles of IaC into the organization’s culture.
+
+Over time, I spearheaded the creation of a dedicated platform team. With an architect/Product Owner and four DevOps engineers, this team took IaC to the next level. They implemented robust CI/CD pipelines, infrastructure monitoring, and scalable deployment patterns. Some of these practices mirrored what I had done at home, while others were tailored to the unique needs of the business. The result was a resilient and predictable infrastructure that supports rapid development and deployment.
+
+## Setting Up Uptime Monitoring with UptimeKuma
+
+One of the most satisfying aspects of IaC is the ability to automate even the smallest tasks. Take uptime monitoring, for example. At home and at work, ensuring that services are available is critical. Recently, I’ve been using my old UptimeKuma instance, a self-hosted monitoring tool that’s as powerful as it is user-friendly, a lot more after introducing it to some friends (who started homelabbing) and at work.
+
+Setting up UptimeKuma is straightforward, you can simply use our old friend Docker:
+
+```docker run -d --name uptime-kuma -v ./data/uptimekuma:/app/data -p 3001:3001 louislam/uptime-kuma```
+
+And access the Dashboard by navigating to <http://localhost:3001> to configure your monitors.
+But that isn't automatic enough for me, I like to put my things in compose files for home usage.
+
+## Automating uptime monitors with AutoKuma
+
+[AutoKuma](https://github.com/BigBoot/AutoKuma) allows us to set labels on our Docker containers that will then automatically generate monitors in UptimeKuma.
+
+One of my containers (UptimeKuma actually) has the following labels attached:
+
+```yml
+labels:
+  kuma.monitoring.group.name: "Monitoring"
+  kuma.uptime_kuma.http.parent_name: "monitoring"
+  kuma.uptime_kuma.http.name: "Kuma status monitoring"
+  kuma.uptime_kuma.http.url: "http://${HOST_IP}:3001"
+```
+
+This actually does 2 things:
+
+- creates a group with the *key/id* `monitoring` and the name `Monitoring`
+- Adds a monitor with the *key/id* `uptime_kuma` to UptimeKuma with the type `http`, name `Kuma status monitoring`, and url `http://${HOST_IP}:3001`
+
+Adding these labels, whilst AutoKuma is running and configured to pick up labels starting with `kuma` is enough for monitors to show up (after restarting the containers).
+All in all, my `docker-compose.yml` file for both UptimeKuma and AutoKuma now looks like this:
+
+```yml
+services:
+  autokuma:
+    image: ghcr.io/bigboot/autokuma:master
+    restart: unless-stopped
+    environment:
+      AUTOKUMA__KUMA__URL: http://${HOST_IP}:3001
+      AUTOKUMA__KUMA__USERNAME: ${KUMA_USERNAME}
+      AUTOKUMA__KUMA__PASSWORD: ${KUMA_PASSWORD}
+      AUTOKUMA__TAG_NAME: AutoKuma
+      AUTOKUMA__TAG_COLOR: "#42C0FB"
+      AUTOKUMA__DEFAULT_SETTINGS: |-
+        docker.docker_container: {{container_name}}
+        http.max_redirects: 10
+        *.max_retries: 3
+      AUTOKUMA__DOCKER__LABEL_PREFIX: kuma
+      AUTOKUMA__MIGRATE: true
+    volumes:
+      - ${APP_DATA}/autokuma:/data
+      - ${DOCKER_SOCKET}:/var/run/docker.sock
+    depends_on:
+      - kuma
+
+  kuma:
+    image: louislam/uptime-kuma:1
+    volumes:
+      - ${APP_DATA}/uptimekuma:/app/data
+      - ${DOCKER_SOCKET}:/var/run/docker.sock
+    ports:
+      - 3001:3001
+    restart: unless-stopped
+    labels:
+      kuma.monitoring.group.name: "Monitoring"
+      kuma.uptime_kuma.http.parent_name: "monitoring"
+      kuma.uptime_kuma.http.name: "Kuma status monitoring"
+      kuma.uptime_kuma.http.url: "http://${HOST_IP}:3001"
+```
+
+## Problems... the compose file doesn't work :O
+
+If you'd try to run the compose file in the previous chapter, even after replacing all the variables, things likely still won't work.
+This is because AutoKuma relies on the credentials for UptimeKuma which we setup during the initial launch of UptimeKuma.
+Unfortunately, that account is the only account we can currently set up in UptimeKuma since it doesn't have user management.
+And yes, that means we **have** to use these same credentials to get AutoKuma to work, which also prohibits us from enabling MFA.
+
+Anyway, after setting up the kuma account, simply adjust both the `KUMA_USERNAME` and `KUMA_PASSWORD` variables and restart the containers.
+After doing so we should see the monitor appear in UptimeKuma:
+
+![a screenshot of the UptimeKuma monitors that were automatically created with AutoKuma](./media/uptimekuma.png "neat!")
+
+## The Future of IaC
+
+Infrastructure as Code isn’t just a technical approach; it’s a philosophy that prioritizes automation, reproducibility, and simplicity. Whether you’re managing a home lab or a global platform, IaC provides the tools and practices to build resilient systems with minimal effort.
+
+For me, IaC has been a journey of continuous learning and experimentation. From Docker to Kubernetes, from bash scripts to dedicated platform teams, the principles remain the same: automate everything, document everything, and embrace the predictability that code brings to infrastructure.
+
+If you haven’t already, give UptimeKuma and AutoKuma a try. Their combination is an excellent example of how IaC can simplify even the most mundane tasks, leaving you more time to focus on what really matters... or just to be a little lazier.

gatsby-browser.ts

@@ -1,3 +0,0 @@
-import "./src/assets/scss/main.scss";
-import "./src/assets/scss/prism/github.scss";
-import "./src/assets/scss/prism/prism-tomorrow.scss";

gatsby-browser.tsx

@@ -0,0 +1,19 @@
+import "./src/assets/scss/main.scss";
+import "./src/assets/scss/prism/github.scss";
+import "./src/assets/scss/prism/prism-tomorrow.scss";
+
+export const onRouteUpdate = ({ location }: { location: { pathname: string } }) => {
+  const elements = document.querySelectorAll("[data-url]");
+  const currentUrl = `https://www.rickvanlieshout.com${location.pathname ?? ""}`;
+
+  const setAttributeIfAvailable = (element: Element, elementIdentifier: string) => {
+    if (element.hasAttribute(elementIdentifier)) {
+      element.setAttribute(elementIdentifier, currentUrl);
+    }
+  };
+
+  elements.forEach((element) => {
+    setAttributeIfAvailable(element, "href");
+    setAttributeIfAvailable(element, "content");
+  });
+};

gatsby-config.ts

@@ -164,14 +164,7 @@ export default {
         start_url: "/",
       },
     },
-    {
-      resolve: "gatsby-plugin-react-helmet-canonical-urls",
-      options: {
-        siteUrl: config.url,
-        stripQueryString: true,
-      },
-    },
-    // remove the old serviceworker if it is available.
+    // remove the old service worker if it is available.
     "gatsby-plugin-remove-serviceworker",
     "gatsby-plugin-image",
     "gatsby-plugin-catch-links",

gatsby-ssr.tsx

@@ -18,7 +18,19 @@ const setColorTheme = `
   }
 })();
 `;
-export const onRenderBody = ({ setPreBodyComponents }: RenderBodyArgs) => {
+export const onRenderBody = ({
+  setPreBodyComponents,
+  setHeadComponents,
+  pathname,
+}: RenderBodyArgs) => {
+  const currentUrl = `https://www.rickvanlieshout.com${pathname}`;
+
+  setHeadComponents([
+    <meta data-url="currentUrl" key="og:url" property="og:url" content={currentUrl} />,
+    <link data-url="currentUrl" key="canonical" rel="canonical" href={currentUrl} />,
+    <meta data-url="currentUrl" property="test:rick" key="test:rick" content={currentUrl} />,
+  ]);
+
   setPreBodyComponents([
     React.createElement("script", {
       key: "theme",

internal/testing/__mocks__/legalMenu.ts

@@ -1,5 +1,5 @@
 export default [
   { label: "Articles", path: "/" },
-  { label: "About Me", path: "/pages/about" },
-  { label: "Contact Me", path: "/pages/contacts" },
+  { label: "About Me", path: "/pages/about/" },
+  { label: "Contact Me", path: "/pages/contacts/" },
 ];

package.json

@@ -1,6 +1,6 @@
 {
   "name": "rickvanlieshout-com",
-  "version": "1.2.3",
+  "version": "1.3.1",
   "description": "My personal blog / website",
   "keywords": [
     "gatsby",
@@ -18,8 +18,8 @@
   "author": "Rick van Lieshout <info@rickvanlieshout.com>",
   "scripts": {
     "build": "npm run clean && gatsby build",
-    "commit": "git-cz",
     "clean": "rimraf .cache public",
+    "commit": "git-cz",
     "format": "npm run format:ts && npm run format:scss",
     "format:scss": "stylelint \"src/**/*.scss\" --fix",
     "format:ts": "eslint \"src\" --ext .tsx,.ts --fix && prettier --write .",
@@ -29,9 +29,9 @@
     "lint:ts": "eslint \"src\" --ext .tsx,.ts && prettier --check .",
     "prepare": "husky install",
     "release": "standard-version",
+    "release:major": "standard-version --release-as major",
     "release:minor": "standard-version --release-as minor",
     "release:patch": "standard-version --release-as patch",
-    "release:major": "standard-version --release-as major",
     "reset-snapshots": "find -type f -name '*.snap*' -delete && npm run test",
     "semantic-release": "semantic-release",
     "serve": "gatsby serve",
@@ -48,115 +48,114 @@
       "npm run format:scss"
     ]
   },
+  "config": {
+    "commitizen": {
+      "path": "@commitlint/cz-commitlint"
+    }
+  },
   "dependencies": {
-    "@fortawesome/fontawesome-svg-core": "^6.4.2",
-    "@fortawesome/free-solid-svg-icons": "^6.4.2",
-    "@fortawesome/react-fontawesome": "^0.2.0",
-    "classnames": "^2.3.2",
-    "disqus-react": "^1.1.5",
-    "gatsby": "^5.11.0",
-    "gatsby-link": "^5.11.0",
-    "gatsby-plugin-catch-links": "^5.11.0",
-    "gatsby-plugin-feed": "^5.11.0",
-    "gatsby-plugin-google-gtag": "^5.11.0",
-    "gatsby-plugin-image": "^3.11.0",
-    "gatsby-plugin-manifest": "^5.11.0",
+    "@fortawesome/fontawesome-svg-core": "^6.7.2",
+    "@fortawesome/free-solid-svg-icons": "^6.7.2",
+    "@fortawesome/react-fontawesome": "^0.2.2",
+    "classnames": "^2.5.1",
+    "disqus-react": "^1.1.6",
+    "gatsby": "^5.14.3",
+    "gatsby-link": "^5.14.1",
+    "gatsby-plugin-catch-links": "^5.14.0",
+    "gatsby-plugin-feed": "^5.14.0",
+    "gatsby-plugin-google-gtag": "^5.14.0",
+    "gatsby-plugin-image": "^3.14.0",
+    "gatsby-plugin-manifest": "^5.14.0",
     "gatsby-plugin-optimize-svgs": "^1.0.5",
-    "gatsby-plugin-react-helmet": "^6.11.0",
-    "gatsby-plugin-react-helmet-canonical-urls": "^1.4.0",
+    "gatsby-plugin-react-helmet": "^6.14.0",
     "gatsby-plugin-remove-serviceworker": "^1.0.0",
     "gatsby-plugin-robots-txt": "^1.8.0",
-    "gatsby-plugin-sass": "^6.11.0",
-    "gatsby-plugin-sharp": "^5.11.0",
-    "gatsby-plugin-sitemap": "^6.11.0",
-    "gatsby-remark-autolink-headers": "^6.11.0",
-    "gatsby-remark-copy-linked-files": "^6.11.0",
+    "gatsby-plugin-sass": "^6.14.0",
+    "gatsby-plugin-sharp": "^5.14.0",
+    "gatsby-plugin-sitemap": "^6.14.0",
+    "gatsby-remark-autolink-headers": "^6.14.0",
+    "gatsby-remark-copy-linked-files": "^6.14.0",
     "gatsby-remark-external-links": "0.0.4",
-    "gatsby-remark-images": "^7.11.0",
+    "gatsby-remark-images": "^7.14.0",
     "gatsby-remark-images-medium-zoom": "^1.7.0",
-    "gatsby-remark-prismjs": "^7.11.0",
-    "gatsby-remark-responsive-iframe": "^6.11.0",
-    "gatsby-remark-smartypants": "^6.11.0",
-    "gatsby-source-filesystem": "^5.11.0",
-    "gatsby-transformer-remark": "^6.11.0",
-    "gatsby-transformer-sharp": "^5.11.0",
+    "gatsby-remark-prismjs": "^7.14.0",
+    "gatsby-remark-responsive-iframe": "^6.14.0",
+    "gatsby-remark-smartypants": "^6.14.0",
+    "gatsby-source-filesystem": "^5.14.0",
+    "gatsby-transformer-remark": "^6.14.0",
+    "gatsby-transformer-sharp": "^5.14.0",
     "prismjs": "^1.29.0",
-    "react": "^18.2.0",
-    "react-cookie-consent": "^8.0.1",
-    "react-dom": "^18.2.0",
+    "react": "^18.3.1",
+    "react-cookie-consent": "^9.0.0",
+    "react-dom": "^18.3.1",
     "react-helmet": "^6.1.0",
     "react-toggle": "^4.1.3",
     "reading-time": "^1.5.0"
   },
   "devDependencies": {
-    "@commitlint/config-conventional": "^17.6.6",
-    "@commitlint/cz-commitlint": "^17.5.0",
-    "@jest/globals": "^29.5.0",
+    "@commitlint/config-conventional": "^17.8.1",
+    "@commitlint/cz-commitlint": "^19.6.1",
+    "@jest/globals": "^29.7.0",
     "@mastermindzh/eslint-config": "^1.0.2",
     "@mastermindzh/prettier-config": "^1.0.0",
     "@semantic-release/exec": "6.0.3",
     "@semantic-release/git": "10.0.1",
-    "@swc/core": "^1.3.67",
-    "@swc/jest": "^0.2.26",
-    "@types/gatsby-transformer-remark": "^2.9.1",
-    "@types/jest": "^29.5.2",
-    "@types/node": "^18.15.11",
-    "@types/react": "^18.2.14",
-    "@types/react-dom": "^18.2.6",
+    "@swc/core": "^1.10.4",
+    "@swc/jest": "^0.2.37",
+    "@types/gatsby-transformer-remark": "^2.9.4",
+    "@types/jest": "^29.5.14",
+    "@types/node": "^22.10.3",
+    "@types/react": "^18.3.18",
+    "@types/react-dom": "^18.3.5",
     "@types/react-helmet": "^6.1.6",
-    "@types/react-test-renderer": "^18.0.0",
-    "@types/react-toggle": "^4.0.3",
-    "@typescript-eslint/eslint-plugin": "^5.60.1",
-    "@typescript-eslint/parser": "^5.60.1",
-    "autoprefixer": "^10.4.14",
-    "browserslist": "^4.21.9",
+    "@types/react-test-renderer": "^18.3.1",
+    "@types/react-toggle": "^4.0.5",
+    "@typescript-eslint/eslint-plugin": "^5.62.0",
+    "@typescript-eslint/parser": "^5.62.0",
+    "autoprefixer": "^10.4.20",
+    "browserslist": "^4.24.3",
     "codecov": "^3.8.3",
-    "commitizen": "^4.3.0",
-    "commitlint": "^17.6.6",
-    "concurrently": "^8.2.0",
-    "eslint": "^8.43.0",
+    "commitizen": "^4.3.1",
+    "commitlint": "^19.6.1",
+    "concurrently": "^9.1.2",
+    "eslint": "^8.57.1",
     "eslint-config-airbnb": "^19.0.4",
-    "eslint-config-airbnb-typescript": "^17.0.0",
-    "eslint-config-prettier": "^8.8.0",
+    "eslint-config-airbnb-typescript": "^17.1.0",
+    "eslint-config-prettier": "^8.10.0",
     "eslint-config-react-app": "^7.0.1",
-    "eslint-import-resolver-typescript": "^3.5.5",
+    "eslint-import-resolver-typescript": "^3.7.0",
     "eslint-plugin-flowtype": "^8.0.3",
-    "eslint-plugin-import": "^2.27.5",
-    "eslint-plugin-jest": "^27.2.2",
-    "eslint-plugin-jsx-a11y": "^6.7.1",
+    "eslint-plugin-import": "^2.31.0",
+    "eslint-plugin-jest": "^27.9.0",
+    "eslint-plugin-jsx-a11y": "^6.10.2",
     "eslint-plugin-prettier": "^4.2.1",
-    "eslint-plugin-react": "^7.32.2",
-    "eslint-plugin-react-hooks": "^4.6.0",
+    "eslint-plugin-react": "^7.37.3",
+    "eslint-plugin-react-hooks": "^4.6.2",
     "eslint-plugin-simple-import-sort": "^10.0.0",
     "husky": "^8.0.3",
     "identity-obj-proxy": "3.0.0",
-    "jest": "^29.5.0",
-    "jest-cli": "^29.5.0",
-    "jest-environment-jsdom": "^29.5.0",
+    "jest": "^29.7.0",
+    "jest-cli": "^29.7.0",
+    "jest-environment-jsdom": "^29.7.0",
     "jest-svg-transformer": "^1.0.0",
-    "lint-staged": "^13.2.3",
-    "lost": "9.0.1",
-    "markdownlint": "^0.29.0",
-    "postcss": "^8.4.24",
-    "postcss-scss": "^4.0.6",
+    "lint-staged": "^15.3.0",
+    "lost": "9.0.2",
+    "markdownlint": "^0.37.3",
+    "postcss": "^8.4.49",
+    "postcss-scss": "^4.0.9",
     "prettier": "^2.8.8",
-    "prettier-plugin-packagejson": "^2.4.3",
-    "react-test-renderer": "^18.2.0",
-    "rimraf": "^4.4.1",
-    "sass": "^1.63.6",
+    "prettier-plugin-packagejson": "^2.5.6",
+    "react-test-renderer": "^18.3.1",
+    "rimraf": "^6.0.1",
+    "sass": "^1.83.0",
     "source-map-support": "^0.5.21",
     "standard-version": "^9.5.0",
-    "stylelint": "^15.9.0",
-    "stylelint-config-recommended-scss": "^9.0.1",
-    "stylelint-order": "^6.0.3",
-    "stylelint-scss": "^4.6.0",
-    "ts-node": "^10.9.1",
-    "typescript": "^5.1.6",
-    "unist-util-find": "1.0.2"
-  },
-  "config": {
-    "commitizen": {
-      "path": "@commitlint/cz-commitlint"
-    }
+    "stylelint": "^16.12.0",
+    "stylelint-config-recommended-scss": "^14.1.0",
+    "stylelint-order": "^6.0.4",
+    "stylelint-scss": "^6.10.0",
+    "ts-node": "^10.9.2",
+    "typescript": "^5.7.2",
+    "unist-util-find": "3.0.0"
   }
-}
+}

src/components/Layout/Layout.tsx

@@ -1,9 +1,9 @@
 import React from "react";
 import Helmet from "react-helmet";
 
+import { useSiteMetadata } from "@/hooks";
 import { CookieBar } from "../Cookiebar/CookieBar";
 import * as styles from "./Layout.module.scss";
-import { useSiteMetadata } from "@/hooks";
 
 interface Props {
   title: string;
@@ -11,6 +11,7 @@ interface Props {
   socialImage?: string;
   children: React.ReactNode;
   noIndex?: boolean;
+  slug?: string;
 }
 
 const Layout: React.FC<Props> = ({
@@ -19,6 +20,7 @@ const Layout: React.FC<Props> = ({
   description,
   socialImage = "",
   noIndex = false,
+  slug,
 }: Props) => {
   const { author, url } = useSiteMetadata();
   const metaImage = socialImage || author.photo;
@@ -33,6 +35,7 @@ const Layout: React.FC<Props> = ({
         <meta property="og:description" content={description} />
         <meta property="og:site_name" content={title} />
         <meta property="og:image" content={metaImageUrl} />
+        <meta property="og:title" content={title} />
         <meta name="twitter:card" content="summary" />
         <meta name="twitter:title" content={title} />
         <meta name="twitter:description" content={description} />

src/components/Page/Page.tsx

@@ -1,8 +1,8 @@
 import React, { useEffect, useRef } from "react";
 
-import * as styles from "./Page.module.scss";
 import type { Nullable } from "@/types";
-
+import { Helmet } from "react-helmet";
+import * as styles from "./Page.module.scss";
 
 interface Props {
   title?: string;
@@ -19,12 +19,17 @@ const Page: React.FC<Props> = ({ title, children }: Props) => {
   }, []);
 
   return (
-    <div ref={pageRef} className={styles.page}>
-      <div className={styles.inner}>
-        {title && <h1 className={styles.title}>{title}</h1>}
-        <div className={styles.body}>{children}</div>
+    <>
+      <Helmet>
+        <meta property="og:type" content="website" />
+      </Helmet>
+      <div ref={pageRef} className={styles.page}>
+        <div className={styles.inner}>
+          {title && <h1 className={styles.title}>{title}</h1>}
+          <div className={styles.body}>{children}</div>
+        </div>
       </div>
-    </div>
+    </>
   );
 };
 

src/components/Post/Author/Author.tsx

@@ -9,7 +9,7 @@ const Author = () => {
     <div className={styles.author}>
       <p className={styles.bio}>
         Written by:{" "}
-        <a href="/pages/about">
+        <a href="/pages/about/">
           <strong>{author.name}</strong>
         </a>
         {typeof window !== "undefined" ? (

src/components/Post/Author/__snapshots__/Author.test.tsx.snap

@@ -6,7 +6,7 @@ exports[`Author renders correctly 1`] = `
     Written by:
      
     <a
-      href="/pages/about"
+      href="/pages/about/"
     >
       <strong>
         Rick van Lieshout

src/components/Post/__snapshots__/Post.test.tsx.snap

@@ -165,7 +165,7 @@ exports[`Post renders correctly 1`] = `
         Written by:
          
         <a
-          href="/pages/about"
+          href="/pages/about/"
         >
           <strong>
             Rick van Lieshout

src/templates/CategoriesTemplate/CategoriesTemplate.tsx

@@ -13,7 +13,7 @@ const CategoriesTemplate: React.FC = () => {
   const categories = useCategoriesList();
 
   return (
-    <Layout title={`Categories - ${title}`} description={subtitle}>
+    <Layout title={`Categories - ${title}`} description={subtitle} slug="/categories/">
       <Sidebar />
       <Page title="Categories">
         <ul>

src/templates/CategoryTemplate/CategoryTemplate.tsx

@@ -28,7 +28,7 @@ const CategoryTemplate: React.FC<Props> = ({ data, pageContext }: Props) => {
     currentPage > 0 ? `${group} - Page ${currentPage} - ${siteTitle}` : `${group} - ${siteTitle}`;
 
   return (
-    <Layout title={pageTitle} description={siteSubtitle}>
+    <Layout title={pageTitle} description={siteSubtitle} slug={`/category/${group}/`}>
       <Sidebar />
       <Page title={group}>
         <Feed edges={edges} />

src/templates/IndexTemplate/IndexTemplate.tsx

@@ -26,7 +26,7 @@ const IndexTemplate: React.FC<Props> = ({ data, pageContext }: Props) => {
   const pageTitle = currentPage > 0 ? `Posts - Page ${currentPage} - ${siteTitle}` : siteTitle;
 
   return (
-    <Layout title={pageTitle} description={siteSubtitle}>
+    <Layout title={pageTitle} description={siteSubtitle} slug="">
       <Sidebar isIndex />
       <Page>
         <Feed edges={edges} />

src/templates/NotFoundTemplate/NotFoundTemplate.tsx

@@ -10,7 +10,7 @@ const NotFoundTemplate: React.FC = () => {
   const { title, subtitle } = useSiteMetadata();
 
   return (
-    <Layout title={`Not Found - ${title}`} description={subtitle}>
+    <Layout title={`Not Found - ${title}`} description={subtitle} slug="/404.html">
       <Sidebar />
       <Page title="Oh no! page be lost">
         <p>

src/templates/PageTemplate/PageTemplate.tsx

@@ -26,6 +26,7 @@ const PageTemplate: React.FC<Props> = ({ data }: Props) => {
       title={`${title} - ${siteTitle}`}
       description={metaDescription}
       socialImage={socialImage?.publicURL}
+      slug={data.markdownRemark.fields.slug}
     >
       <Sidebar />
       <Page title={title}>
@@ -40,6 +41,9 @@ export const query = graphql`
     markdownRemark(fields: { slug: { eq: $slug } }) {
       id
       html
+      fields {
+        slug
+      }
       frontmatter {
         title
         date

src/templates/PostTemplate/PostTemplate.tsx

@@ -24,6 +24,7 @@ const PostTemplate: React.FC<Props> = ({ data }: Props) => {
       title={`${title} - ${siteTitle}`}
       description={metaDescription}
       socialImage={socialImage?.publicURL}
+      slug={data.markdownRemark.fields.slug}
     >
       <Post post={data.markdownRemark} />
     </Layout>

src/templates/PostTemplate/__snapshots__/PostTemplate.test.tsx.snap

@@ -166,7 +166,7 @@ exports[`PostTemplate renders correctly 1`] = `
           Written by:
            
           <a
-            href="/pages/about"
+            href="/pages/about/"
           >
             <strong>
               Rick van Lieshout

src/templates/TagTemplate/TagTemplate.tsx

@@ -28,7 +28,7 @@ const TagTemplate: React.FC<Props> = ({ data, pageContext }: Props) => {
     currentPage > 0 ? `${group} - Page ${currentPage} - ${siteTitle}` : `${group} - ${siteTitle}`;
 
   return (
-    <Layout title={pageTitle} description={siteSubtitle}>
+    <Layout title={pageTitle} description={siteSubtitle} slug={`/tag/${group}/`}>
       <Sidebar />
       <Page title={group}>
         <Feed edges={edges} />

src/templates/TagsTemplate/TagsTemplate.tsx

@@ -13,7 +13,7 @@ const TagsTemplate: React.FC = () => {
   const tags = useTagsList();
 
   return (
-    <Layout title={`Tags - ${title}`} description={subtitle}>
+    <Layout title={`Tags - ${title}`} description={subtitle} slug="/tags/">
       <Sidebar />
       <Page title="Tags">
         <ul>

static/.htaccess

@@ -55,10 +55,10 @@ RewriteCond %{SERVER_PORT} ^80$
 RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301]
 
 RewriteCond %{HTTP_HOST} ^rickvanlieshout.com [NC]
-RewriteRule ^(.*)$ http://www.rickvanlieshout.com/$1 [L,R=301]
+RewriteRule ^(.*)$ https://www.rickvanlieshout.com/$1 [L,R=301]
 
 RewriteCond %{HTTP_HOST} ^mastermindzh.com [NC]
-RewriteRule ^(.*)$ http://www.mastermindzh.com/$1 [L,R=301]
+RewriteRule ^(.*)$ https://www.mastermindzh.com/$1 [L,R=301]
 
 # Optional: explicitly enable per-directory rewrites in the .htaccess context.
 

static/keys.json

@@ -1,5 +1,5 @@
 {
   "documentSigningKey": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPH8NJi1EDmYv6mMtd8eC9VBPDf/faGn9GV2PhSo4KtK",
-  "workLaptop": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIJ4LSpR4wx4U/ruu5qZ7hCERSyINp2tCk6IS7cYPfKt+",
+  "workLaptop": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIG5VEDMI0GkOUVjLsSLQF1mRr9UbdXF3YPIsYtqyXxj",
   "devPc": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAII9hfhULcwnmtzXATxU6oqWPhTS06WXPVzx28knx9rPL"
-}
+}