search

TheThingsNetwork / docs

Documentation for The Things Network
https://www.thethingsnetwork.org/docs/
Apache License 2.0
63 stars 292 forks source link

Distinguish better between device registration and activation #504

Closed furtiman closed 2 years ago

furtiman commented 2 years ago

Summary

The sequence of pages that describe process of registering, and then activating the device use confusing wording.

  1. https://www.thethingsindustries.com/docs/getting-started/cloud-hosted/tti-join-server/register-devices/
  2. https://www.thethingsindustries.com/docs/getting-started/cloud-hosted/tti-join-server/activate-devices-cloud-hosted/

Why do we need this ?

...

What is already there? What do you see now?

The sequence can be accessed from Make a Device Claimable page, that belongs to the docs intended for device makers.

The word “register” is used in both of them, however one page is “register” (where ttn-lw-cli end-devices create test-app test-device is used, and the page ends with “You can now activate the devices on The Things Industries Cloud Hosted”)

that leads to another that is about activation (where ttn-lw-cli end-devices set test-app test-device is used, and the page also ends with “You can now activate the devices on The Things Industries Cloud”)

What is missing? What do you want to see?

If no other actions are required in this sequence, then the latter page should sound more like “activate with … -> Now it’s activated”

It should also link back to the Make a Device Claimable page, which tells about further steps in the process

How do you propose to document this?

Described above, plus the wording "register" and "activate" should be thoroughly checked in the content of both page to appear less confusing

Can you do this yourself and submit a Pull Request?

-

nejraselimovic commented 2 years ago

looping in @johanstokking

johanstokking commented 2 years ago

We're going to change this entirely with The Things Join Server. All this stuff will be gone. I'm closing the issue because we track this work elsewhere, but also because this issue is not in the right repo.