From a7dabace24e3d64ccd54976f2a2c7b0c73cddf69 Mon Sep 17 00:00:00 2001
From: Noah <h@n0ah.net>
Date: Tue, 10 Feb 2026 13:52:24 -0500
Subject: [PATCH] change footer text, add footer to resources pages

---
 index.html                |  2 +-
 meshcore-resources.html   | 18 ++++++++++++++++++
 meshtastic-resources.html | 18 ++++++++++++++++++
 3 files changed, 37 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index a77c71b..5cfd4e1 100644
--- a/index.html
+++ b/index.html
@@ -375,7 +375,7 @@
       </div>
     </div>
     <footer class="site-footer">
-      <p><a href="https://ctmesh.org/">CT Mesh</a> is a volunteer-run user group for <a href="https://meshtastic.org" target="_blank">Meshtastic</a> enthusiasts in Connecticut.</p>
+      <p><a href="https://ctmesh.org/">CT Mesh</a> is a volunteer-run user group for mesh technology enthusiasts in Connecticut.</p>
       <p><a href="https://creativecommons.org/licenses/by-sa/4.0/" target="_blank" rel="noopener">Content licensed CC BY-SA 4.0</a></p>
     </footer>
   </div>
diff --git a/meshcore-resources.html b/meshcore-resources.html
index d76de5a..0b316df 100644
--- a/meshcore-resources.html
+++ b/meshcore-resources.html
@@ -127,6 +127,20 @@
       margin-top: 1.5em;
       color: #ffffff;
     }
+    .site-footer {
+      margin-top: 2em;
+      padding-top: 2em;
+      text-align: center;
+      font-size: 0.875rem;
+      color: #2C2D3C;
+      border-top: 1px solid #ccc;
+    }
+    .site-footer a {
+      text-decoration: none;
+    }
+    .site-footer a:hover {
+      text-decoration: underline;
+    }
     @media (max-width: 800px) {
       body {
         padding-top: calc(env(safe-area-inset-top, 1em));
@@ -184,6 +198,10 @@ MCTOMQTT_MQTT3_PASSWORD=large4cats</pre>
     </div>
 
     <a class="btn back-link" href="index.html">&larr; Back to CT Mesh</a>
+    <footer class="site-footer">
+      <p><a href="https://ctmesh.org/">CT Mesh</a> is a volunteer-run user group for mesh technology enthusiasts in Connecticut.</p>
+      <p><a href="https://creativecommons.org/licenses/by-sa/4.0/" target="_blank" rel="noopener">Content licensed CC BY-SA 4.0</a></p>
+    </footer>
   </div>
   <script>
     const copyButtons = document.querySelectorAll("[data-copy-target]");
diff --git a/meshtastic-resources.html b/meshtastic-resources.html
index 5f2e6df..6199fa9 100644
--- a/meshtastic-resources.html
+++ b/meshtastic-resources.html
@@ -125,6 +125,20 @@
     .back-link {
       margin-top: 1.5em;
     }
+    .site-footer {
+      margin-top: 2em;
+      padding-top: 2em;
+      text-align: center;
+      font-size: 0.875rem;
+      color: #2C2D3C;
+      border-top: 1px solid #ccc;
+    }
+    .site-footer a {
+      text-decoration: none;
+    }
+    .site-footer a:hover {
+      text-decoration: underline;
+    }
     @media (max-width: 800px) {
       body {
         padding-top: calc(env(safe-area-inset-top, 1em));
@@ -202,6 +216,10 @@
     <p><strong>Important:</strong> Infrastructure roles like <code>ROUTER</code>, <code>REPEATER</code>, <code>ROUTER_CLIENT</code>, or <code>ROUTER_LATE</code> are rarely appropriate. Unless your node is sitting on top of one of the tallest buildings in Hartford with clear line-of-sight across the region, using these roles will hurt more than help. For almost everyone, the correct choice is <code>CLIENT</code>. If you think you've got a node that truly warrants an infrastructure role, reach out first - we'd rather make sure it benefits the mesh than inadvertently weakens it.</p>
 
     <a class="btn back-link" href="index.html">&larr; Back to CT Mesh</a>
+    <footer class="site-footer">
+      <p><a href="https://ctmesh.org/">CT Mesh</a> is a volunteer-run user group for mesh technology enthusiasts in Connecticut.</p>
+      <p><a href="https://creativecommons.org/licenses/by-sa/4.0/" target="_blank" rel="noopener">Content licensed CC BY-SA 4.0</a></p>
+    </footer>
   </div>
   <script>
     const copyButtons = document.querySelectorAll("[data-copy-target]");