Refactor IoT docs: "Onboard a Hotspot"#2075
Draft
jthiller wants to merge 4 commits into
Draft
Conversation
Replace the Data-Only Hotspot and Gateway Fleet sections with one "Onboard a Hotspot" section covering on-device (gateway-rs) and on-a-server (multi-gateway) methods. Add redirects from the old slugs.
Collapse the IoT onboarding fee to a single $0.50 add + $0.50 assert, and generalize Proof-of-Coverage mentions in the oracle and Solana data docs.
Deploying heliumdocs with
|
| Latest commit: |
64da600
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e6c01c39.heliumdocs.pages.dev |
| Branch Preview URL: | https://iot-onboard-a-hotspot.heliumdocs.pages.dev |
jthiller
changed the title
Distinguish the two methods by where the gateway software and signing key run (gateway-rs on the device vs multi-gateway on a server). Present the CLI wallet add + assert as the universal on-chain onboarding on both pages.
# Conflicts: # static/_redirects
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
1 participant
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.
What changed
This drops the"Data-Only Hotspot" distinction on Hotspots, reframing onboarding around the two
methods that exist today.
New section: "Onboard a Hotspot"
Replaces the old Data-Only Hotspots and Gateway Fleet Onboarding sections with one section:
/iot/onboard-a-hotspot/iot/onboard-a-hotspot/on-device(single Hotspot or a few)/iot/onboard-a-hotspot/server+ Server Setup (fleets)/iot/packet-forwarders/{dragino,rak-concentrators,balena,kerlink}Other changes
/iot/data-only-hotspots,/iot/data-only-hotspots-onboarding,/iot/gateway-fleet-onboarding,/iot/gateway-fleet-onboarding/setup,/iot/data-only/*) and theinbound redirects that targeted them are repointed.
intentionally left intact (PoC still applies to the Mobile network).
Verification
yarn buildpasses withonBrokenLinks: 'throw', so all internal links, sidebar entries, and thenew routes resolve.
Follow-up (not in this PR)
(
data-only-header.png,data-only-onboarding-header.png). New artwork to be supplied separately;the page references were left pointing at the existing files.