change footer text, add footer to resources pages
All checks were successful
Deploy Pages / deploy (push) Successful in 25s
All checks were successful
Deploy Pages / deploy (push) Successful in 25s
This commit is contained in:
@ -375,7 +375,7 @@
|
|||||||
</div>
|
</div>
|
||||||
</div>
|
</div>
|
||||||
<footer class="site-footer">
|
<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>
|
<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>
|
</footer>
|
||||||
</div>
|
</div>
|
||||||
|
|||||||
@ -127,6 +127,20 @@
|
|||||||
margin-top: 1.5em;
|
margin-top: 1.5em;
|
||||||
color: #ffffff;
|
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) {
|
@media (max-width: 800px) {
|
||||||
body {
|
body {
|
||||||
padding-top: calc(env(safe-area-inset-top, 1em));
|
padding-top: calc(env(safe-area-inset-top, 1em));
|
||||||
@ -184,6 +198,10 @@ MCTOMQTT_MQTT3_PASSWORD=large4cats</pre>
|
|||||||
</div>
|
</div>
|
||||||
|
|
||||||
<a class="btn back-link" href="index.html">← Back to CT Mesh</a>
|
<a class="btn back-link" href="index.html">← 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>
|
</div>
|
||||||
<script>
|
<script>
|
||||||
const copyButtons = document.querySelectorAll("[data-copy-target]");
|
const copyButtons = document.querySelectorAll("[data-copy-target]");
|
||||||
|
|||||||
@ -125,6 +125,20 @@
|
|||||||
.back-link {
|
.back-link {
|
||||||
margin-top: 1.5em;
|
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) {
|
@media (max-width: 800px) {
|
||||||
body {
|
body {
|
||||||
padding-top: calc(env(safe-area-inset-top, 1em));
|
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>
|
<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">← Back to CT Mesh</a>
|
<a class="btn back-link" href="index.html">← 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>
|
</div>
|
||||||
<script>
|
<script>
|
||||||
const copyButtons = document.querySelectorAll("[data-copy-target]");
|
const copyButtons = document.querySelectorAll("[data-copy-target]");
|
||||||
|
|||||||
Reference in New Issue
Block a user