Merge github.com:masterpointio/masterpoint.io into feature/homepage-rework-kris

Author: Gowiem

.github/workflows/lint.yaml

@@ -17,7 +17,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Check out Git repository
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
       - name: Trunk Check
         uses: trunk-io/trunk-action@75699af9e26881e564e9d832ef7dc3af25ec031b # v1.2.4
 

.github/workflows/trunk-upgrade.yaml

@@ -17,7 +17,7 @@ jobs:
       pull-requests: write
     steps:
       - name: Checkout
-        uses: actions/checkout@08c6903cd8c0fde910a37f88322edcfb5dd907a8 # v5.0.0
+        uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Create Token for MasterpointBot App
         uses: tibdex/github-app-token@3beb63f4bd073e61482598c45c71c1019b59b73a #v2.1.0

content/blog/2025-09-15-ultimate-terraform-versioning-guide.md

@@ -5,7 +5,7 @@ title: "The Ultimate Terraform Versioning Guide"
 author: Veronika Gnilitska
 slug: ultimate-terraform-versioning-guide
 date: 2025-09-15
-# date_modified: 2025-xx-xx Be sure to use this if you've updated the post as this helps with SEO and index freshness
+date_modified: 2025-11-25 # Be sure to use this if you've updated the post as this helps with SEO and index freshness
 description: A practical, no-fluff guide to versioning in Terraform/OpenTofu that helps you avoid the hidden traps of tool, provider, and module mismatches. If your team has ever faced surprises after “just updating Terraform” (or wants to prevent them), this guide is a must-read.
 image: /img/updates/tf-versioning-guide/main.jpeg
 ---
@@ -104,7 +104,10 @@ Since [Child Modules](https://masterpoint.io/blog/terraform-opentofu-terminology
 terraform {
   required_version = ">= 1.6.0"
   required_providers {
-    aws = ">= 5.0.0"
+    aws = {
+      source  = "hashicorp/aws"
+      version = ">= 5.0.0"
+    }
   }
 }
 ```
@@ -126,7 +129,10 @@ Example:
 terraform {
   required_version = "1.7.5"
   required_providers {
-    aws = "~> 5.81.0"
+    aws = {
+      source  = "hashicorp/aws"
+      version = "~> 5.81.0"
+    }
   }
 }
 ```

content/tying-the-masterpoint-knot.md

@@ -0,0 +1,26 @@
+---
+title: "Tying the Masterpoint Knot"
+description: "Learn how to tie the double fisherman's knot that inspired the Masterpoint logo with our step-by-step video tutorial and instructions."
+author: Matt Gowie
+date: 2025-12-12
+slug: tying-the-masterpoint-knot
+layout: "single"
+visible: true
+draft: false
+---
+
+Hey folks -- Matt from Masterpoint here. I had this funny idea to show people how to tie the double fisherman's knot that inspired the Masterpoint logo. This knot is a fundamental climbing knot that ties two ropes together (considered a "bend") and it's something I've used consistently throughout my years climbing. I hope you get a kick out of it!
+
+<div style="margin: 2rem 0;">
+  <iframe width="100%" height="400" src="https://www.youtube.com/embed/UVjAsHY8oU0" title="Tying the Masterpoint Knot" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe>
+</div>
+
+## Need a better visual?
+
+If the video above wasn't clear enough, the below image from Knotspedia shows step-by-step instructions for tying the double fisherman's knot, including some lovely comic-sans flavor.
+
+{{< lightboximg "/img/marketing/tying-masterpoint-knot-instructions.png" "Step-by-step instructions for tying the double fisherman's knot" >}}
+
+## Thanks
+
+Thanks for checking out this funny marketing experiment! Reach out to me at [[email protected]](mailto:[email protected]), send a photo of your knot, and let's catch up!

layouts/_default/_markup/render-heading.html

@@ -3,15 +3,29 @@
   Automatically adds clickable anchor links to all heading levels (H1-H6)
   for easy deep-linking and sharing of specific sections.
   The entire heading text is clickable, with a # symbol on the right.
+
+  Only applies to blog posts and case studies to avoid styling conflicts
+  on marketing pages (home, services, etc.).
 */ -}}
 
 {{- $level := .Level -}}
 {{- $text := .Text -}}
 {{- $anchor := .Anchor -}}
 
+{{- /* Determine if this page should have anchor links */ -}}
+{{- $enableAnchorLinks := false -}}
+{{- /* Enable for blog, case studies, and standalone root-level pages (like /referrals) */ -}}
+{{- if or (eq .Page.Section "blog") (eq .Page.Section "case-studies") (eq .Page.Section "") -}}
+  {{- $enableAnchorLinks = true -}}
+{{- end -}}
+
+{{- if $enableAnchorLinks -}}
 <h{{ $level }} id="{{ $anchor }}" class="heading-with-anchor">
   <a href="#{{ $anchor }}" class="heading-anchor-link" aria-label="Link to {{ $text }}">
     <span class="heading-text">{{ $text | safeHTML }}</span>
     <span class="heading-anchor-symbol">#</span>
   </a>
 </h{{ $level }}>
+{{- else -}}
+<h{{ $level }} id="{{ $anchor }}">{{ $text | safeHTML }}</h{{ $level }}>
+{{- end -}}