Add Go upload instructions

Author: JessamyT

docs/cli.md

@@ -628,7 +628,7 @@ This includes:
 - Building your module for different architectures using cloud runners
 - Building a module locally and running it on a target device. Rebuilding & restarting if already running.
 
-See [Upload a custom module](/how-tos/upload-module/) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for more information.
+See [Upload a module](/how-tos/upload-module/) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for more information.
 
 If you update and release your module as part of a continuous integration (CI) workflow, you can also
 [automatically upload new versions of your module on release](/how-tos/manage-modules/#update-an-existing-module-using-a-github-action) using a GitHub Action.
@@ -718,7 +718,7 @@ viam module upload --version=1.0.0 --platform=darwin/arm64 packaged-module.tar.g
 | `--org-id` | The organization ID to associate the module to. See [Using the `--org-id` argument](#using-the---org-id-and---public-namespace-arguments) | `create`, `upload` | **Required** |
 | `--public-namespace` | The [namespace](/cloud/organizations/#create-a-namespace-for-your-organization) to associate the module to. See [Using the `--public-namespace` argument](#using-the---org-id-and---public-namespace-arguments) | `create`, `upload` | **Required** |
 | `--platform` | The architecture of your module binary. See [Using the `--platform` argument](#using-the---platform-argument) | `upload`, `build logs` | **Required** |
-| `--tags` | Comma-separated list of platform tags that determine to which this binary can be deployed. Examples: `distro:debian,distro:ubuntu, os_version:22.04,os_codename:jammy`. For a machine to use an uploaded binary, all tags must be satisfied as well as the `--platform` field. <ul><li>`distro`: Distribution. You can find this in `/etc/os-release`. `"debian"` or `"ubuntu"`.</li><li>`os_version`:  Operating System version. On Linux, you can find this in `/etc/os-release`. Example for linux: `22.04`. On Mac, run `sw_vers --productVersion` and use the major version only. Example for mac: `14`.</li><li>`codename`: The operating system codename. Find this in `/etc/os-release`. For example: `"bullseye"`, `"bookworm"`, or `"jammy"`.</li><li>`cuda`: Whether using CUDA compiler. Run `nvcc --version`. For example: `"true"`.</li><li>`cuda_version`: The CUDA compiler version. Run `nvcc --version`. For example: `"11"` or `"12"`.</li><li>`jetpack`: Version of the NVIDIA JetPack SDK. Run `apt-cache show nvidia-jetpack`. For example: `"5"`.</li><li>`pi`: Version of the raspberry pi: `"4"` or `"5"`.</li><li>`pifull`: Compute module or model number, for example `cm5p` or `5B`.</li></ul> | `upload` | Optional |
+| `--tags` | Comma-separated list of platform tags that determine to which platforms this binary can be deployed. Examples: `distro:debian,distro:ubuntu, os_version:22.04,os_codename:jammy`. For a machine to use an uploaded binary, all tags must be satisfied as well as the `--platform` field. <ul><li>`distro`: Distribution. You can find this in `/etc/os-release`. `"debian"` or `"ubuntu"`.</li><li>`os_version`:  Operating System version. On Linux, you can find this in `/etc/os-release`. Example for linux: `22.04`. On Mac, run `sw_vers --productVersion` and use the major version only. Example for mac: `14`.</li><li>`codename`: The operating system codename. Find this in `/etc/os-release`. For example: `"bullseye"`, `"bookworm"`, or `"jammy"`.</li><li>`cuda`: Whether using CUDA compiler. Run `nvcc --version`. For example: `"true"`.</li><li>`cuda_version`: The CUDA compiler version. Run `nvcc --version`. For example: `"11"` or `"12"`.</li><li>`jetpack`: Version of the NVIDIA JetPack SDK. Run `apt-cache show nvidia-jetpack`. For example: `"5"`.</li><li>`pi`: Version of the raspberry pi: `"4"` or `"5"`.</li><li>`pifull`: Compute module or model number, for example `cm5p` or `5B`.</li></ul> | `upload` | Optional |
 | `--version` | The version of your module to set for this upload. See [Using the `--version` argument](#using-the---version-argument) | `upload` | **Required** |
 | `--wait` | Wait for the build to finish before outputting any logs | `build logs` | Optional |
 
@@ -863,7 +863,7 @@ In the example above, the model namespace is set to `acme` to match the owning o
 If the two namespaces do not match, the command will return an error.
 {{% /alert %}}
 
-See [Upload a custom module](/how-tos/upload-module/) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
+See [Upload a module](/how-tos/upload-module/) and [Update an existing module](/how-tos/manage-modules/#update-an-existing-module) for a detailed walkthrough of the `viam module` commands.
 
 See [Modular resources](/registry/) for a conceptual overview of modules and the modular resource system at Viam.
 

docs/how-tos/hello-world-module.md

@@ -205,7 +205,7 @@ First let's generate the camera component files, and we'll add the sensor code l
       We will add the sensor later.
     - Model name: `hello-camera`
     - Enable cloud build: `No`
-    - Register module: `No`
+    - Register module: `Yes`
 
 1.  Hit your Enter key and the generator will generate a folder called <file>hello-world</file> containing stub files for your modular camera component.
 
@@ -764,7 +764,10 @@ The hello world module you created is for learning purposes, not to provide any
 
 {{< /expand >}}
 
-To package and upload your module and make it available to configure on machines in your organization:
+To package (for Python) and upload your module and make it available to configure on machines in your organization:
+
+{{< tabs >}}
+{{% tab name="Python" %}}
 
 1. Package the module as an archive, run the following command from inside the <file>hello-world</file> directory:
 
@@ -780,10 +783,22 @@ To package and upload your module and make it available to configure on machines
    viam module upload --version 1.0.0 --platform any module.tar.gz
    ```
 
-1. Now, if you look at the [Viam Registry page](https://app.viam.com/registry) while logged into your account, you'll be able to find your private module listed.
-   You can configure the hello-sensor and hello-camera on your machines just as you would configure other components and services; there's no more need for local module configuration.
+{{% /tab %}}
+{{% tab name="Go" %}}
+
+From within your <file>hello-world</file> directory, run the `viam module upload` CLI command to upload the module to the registry:
+
+```sh {id="terminal-prompt" class="command-line" data-prompt="$"}
+viam module upload --version 1.0.0 --platform any .
+```
+
+{{% /tab %}}
+{{< /tabs >}}
+
+Now, if you look at the [Viam Registry page](https://app.viam.com/registry) while logged into your account, you'll be able to find your private module listed.
+You can configure the hello-sensor and hello-camera on your machines just as you would configure other components and services; there's no more need for local module configuration.
 
-   ![The create a component menu open, searching for hello. The hello-camera and hello-sensor components are shown in the search results.](/how-tos/hello-config.png)
+![The create a component menu open, searching for hello. The hello-camera and hello-sensor components are shown in the search results.](/how-tos/hello-config.png)
 
 For more information about uploading modules, see [Upload a module](/how-tos/upload-module/).
 

docs/how-tos/upload-module.md

@@ -111,7 +111,7 @@ Edit the newly-created `meta.json` file, and provide the required configuration
     <td><code>module_id</code></td>
     <td>string</td>
     <td><strong>Required</strong></td>
-    <td>The module ID, which includes either the module <a href="/cloud/organizations/#create-a-namespace-for-your-organization">namespace</a> or <a href="/cloud/organizations/">organization-id</a>, followed by its name (pre-populated using the <code>--name</code> you provided in the <code>viam module create</code> command).
+    <td>The module ID, which includes either the module <a href="/cloud/organizations/#create-a-namespace-for-your-organization">namespace</a> or <a href="/cloud/organizations/">organization ID</a>, followed by its name (pre-populated using the <code>--name</code> you provided in the <code>viam module create</code> command).
     <div class="alert alert-caution" role="alert">
   <h4 class="alert-heading">Caution</h4>
 
@@ -264,7 +264,7 @@ where:
   You can only provide one `platform` argument at a time to the `viam module upload` command.
   See [Using the `--platform` argument](/cli/#using-the---platform-argument) for the full list of supported architectures.
 - `module-path`: provide the path to the file, directory, or compressed archive (with `.tar.gz` or `.tgz` extension) that contains your custom module code.
-- `tags`: provide a comma-separated list of platform tags that determine to which this binary can be deployed. See [`viam module upload`](/cli/#module).
+- `tags`: provide a comma-separated list of platform tags that determine to which platforms this binary can be deployed. See [`viam module upload`](/cli/#module).
 
 {{% alert title="Important" color="note" %}}
 The `viam module upload` command only supports one `platform` argument at a time.
@@ -275,19 +275,19 @@ The Viam Registry page for your module displays the platforms your module suppor
 
 For example:
 
-- To upload a custom module that is defined in a single file named `my-module-file` in a local `bin` directory:
+- To upload a module that is defined in a single file named `my-module-file` in a local `bin` directory:
 
   ```sh {id="terminal-prompt" class="command-line" data-prompt="$"}
   viam module upload --version 1.0.0 --platform linux/amd64 ./bin/my-module-file
   ```
 
-- To upload a custom module that includes multiple files, as well as a separate entry point file, all contained with a local `bin` directory:
+- To upload a module that includes multiple files, as well as a separate entry point file, all contained with a local `bin` directory:
 
   ```sh {id="terminal-prompt" class="command-line" data-prompt="$"}
   viam module upload --version 1.0.0 --platform linux/amd64 ./bin
   ```
 
-- To upload a custom module that has been compressed as an archive named `packaged-module.tar.gz`:
+- To upload a module that has been compressed as an archive named `packaged-module.tar.gz`:
 
   ```sh {id="terminal-prompt" class="command-line" data-prompt="$"}
   viam module upload --version 1.0.0 --platform linux/amd64 packaged-module.tar.gz