Gate Arizona LoRa + MQTT settings behind a Join-The-Discord overlay - #27
Closed
rancur wants to merge 2 commits into
Closed
Gate Arizona LoRa + MQTT settings behind a Join-The-Discord overlay#27rancur wants to merge 2 commits into
rancur wants to merge 2 commits into
Conversation
… overlay Adds a reusable `.azmsh-locked` component that blurs the community-shared settings values on two pages and overlays a native "Join The Discord" CTA, so newcomers must join Discord to obtain the live values. - how-to-connect.md (Step 4): blurred LoRa box (Preset + Frequency Slot for metro vs non-metro). Labels stay sharp; "Okay to MQTT: On" left visible since it is not a secret. - recommended-settings.md (MQTT Module step): blurred broker box (Server / Username / Password / Topic) plus a Join-The-Discord CTA. - assets/css/extra.css: new `.azmsh-locked` component built on Material theme variables (light/dark mode, deep-orange palette, responsive). - mkdocs.yml: register the CSS via extra_css. No real values ship in source: only realistic dummy placeholders sit under the blur, so view-source reveals nothing sensitive. Strict mkdocs build passes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
… appears in source The blurred MQTT box used the real broker hostname (mqtt.azmsh.net:1883) as its dummy placeholder, leaving the real host in page source despite the blur. Swap Server -> broker.example.net:1883 and Topic -> msh/XX/REGION so no real value is recoverable from the rendered HTML. Username/Password dummies and the LoRa preset/slot fakes were already non-real and are unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
rancur
pushed a commit
to rancur/azmsh-site
that referenced
this pull request
Jun 15, 2026
…The-Discord blur (not deleted) Restore the Arizona LoRa settings as GATED content using PR ArizonaMeshtasticCommunity#27's .azmsh-locked blur + "Join The Discord" overlay mechanism, instead of deleting them. Owner feedback: preview must look like ArizonaMeshtasticCommunity#27, with the labels sharp and the values hidden behind the Discord gate, on EVERY page that previously showed them in the clear. Gated / scrubbed across pages: - start-here.md Step 3: region/preset/frequency-slot now a blur box (dummy placeholder values, real values stay out of the served HTML). - start-here.md Step 4: primary channel name + key now a blur box. - start-here.md Step 5: MQTT broker blur box retained (already ArizonaMeshtasticCommunity#27). - suggested_channels.md: public PSK table (AQ==, Ww==, TQ==, MQ==) and the MediumFast preset name replaced with a single gated blur box; CLI example PSK genericized to <KEY_FROM_DISCORD>. - what-now.md: "Primary MediumFast" references neutralized to "primary". - privacy.md: literal default key (AQ==) and LongFast/MediumFast preset names removed from the educational text (kept the meaning). - host-a-node.md: exact 906.875 MHz frequency genericized to the 900 MHz ISM band. No preset / frequency / slot / channel-key value remains in the built site/ (grep-clean). mkdocs build --strict passes with zero warnings. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rancur
pushed a commit
to rancur/azmsh-site
that referenced
this pull request
Jun 15, 2026
Tighten the navigation into a clear newcomer journey plus a single
reference/troubleshooting area, eliminating duplicate and leftover stub
pages without proliferating new ones.
Nav (old -> new):
- Flatten Start Here (drop the nested "Receive Works, Can't Send" child)
- Fold "Receive Works, Can't Send" (cant-transmit) into FAQ as the first
section (#cant-send), with cross-links from Start Here + What Now.
- Fold "Flashing & Recovery" (flashing-gotchas) into FAQ (#flashing-gotchas),
removing it as a separate top-level page; FAQ is now the one troubleshooting
hub (can't-send, 403 map, claim-node, flashing, DM no-channel) with a jump-to
table of contents.
- cant-transmit.md + flashing-gotchas.md become meta-refresh redirect stubs to
the new FAQ anchors so old/external links never 404 (kept out of nav).
- Delete legacy reference stubs connect.md and
recommended_configuration_settings.md (superseded by Start Here; nothing
external links to them).
- Repoint stale links in recommended-hardware + wismesh build guide from the
old how-to-connect / recommended-settings stubs to the canonical Start Here +
Settings Reference anchors.
New nav: Home / Start Here (with Settings Reference) / What Now? /
FAQ & Troubleshooting (with can't-send) / Recommended Hardware /
Suggested Channels / Host a Node / Reach Out.
Gating from PR ArizonaMeshtasticCommunity#27 (#az radio settings, primary channel, suggested channels,
MQTT broker) is untouched: all values stay dummy placeholders behind the
.azmsh-locked blur + Join-The-Discord overlay. No preset/frequency/key/broker
value is exposed anywhere.
mkdocs build --strict passes with 0 warnings.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Member
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Gates the community-shared LoRa and MQTT settings behind a "Join The Discord" overlay. The two pages already tell newcomers to join Discord to get the live values; this enforces that visually. Each settings box now shows sharp labels with the actual values blurred, dimmed under a lock overlay, with a native orange Join The Discord call-to-action. Newcomers can see exactly which fields they need (Preset, Frequency Slot, broker Server/User/Pass/Topic) but must join Discord to read the real values.
Motivation
What changed (per file)
docs/docs/how-to-connect.md— Step 41. Preset:,2. Frequency Slot:) stay sharp so the reader knows what to look for.Okay to MQTT: Onis intentionally left fully visible since it is not a secret, just a toggle everyone uses.docs/docs/recommended-settings.md— MQTT Module stepdocs/assets/css/extra.css(new file).azmsh-lockedcomponent: blurs values (filter: blur(5px)), dims the box with a translucent overlay, and renders the CTA using the theme's own primary button class..azmsh-value--clearmodifier opts a single value out of the blur (used for "Okay to MQTT: On").mkdocs.ymlextra_css.Security / no-leak note
No real values ship in the page source. Only deliberately fake placeholders sit under the blur: the broker box uses a generic
broker.example.net:1883server and amsh/XX/REGIONtopic, with dummy username/password, and the LoRa box uses intentionally-wrong preset/slot fakes. The blur is purely visual; "view source" / DevTools reveals only this dummy text, never the live community values (verified absent from source: real broker host, real MQTT user/pass, real frequency slots). The real settings continue to live in Discord.Design
--md-default-fg-color,--md-code-bg-color, the deep-orange/amber palette), so it inherits the site's fonts and light/dark mode automatically..md-button .md-button--primaryclass, so it matches the existing orange buttons elsewhere on the site.mkdocs build --strict(the same check this repo's CI runs).Preview
Live, persistent preview of this exact branch (built and deployed to GitHub Pages on the author's fork). Click through to both changed pages and see the blurred boxes rendered in a real browser:
Both pages were verified loading over HTTPS with the CSS applied (computed
filter: blur(5px)confirmed on the value fields, overlay button present). Note: the preview is hosted under a/azmsh-site/subpath on github.io, so a few inter-page nav links that use the site's absolute/docs/...convention point at the production domain; that is a preview-host artifact only and does not affect production (root domain) or the two changed pages themselves.Screenshots
(Captured against the live preview above; rendering matches the deployed pages.)
Opened by Barry (Will's AI) on behalf of the Arizona Meshtastic Community maintainers.