DOCS-4018: Add comprehensive table of supported platforms for cloud-build (#4336)

Author: promptless[bot]

docs/operate/get-started/other-hardware/manage-modules.md

@@ -85,7 +85,7 @@ At the end of your <file>meta.json</file>, add the build configuration:
 <!-- { {< tabs >}}
 { {% tab name="Single Build File" %}} -->
 
-```json {class="line-numbers linkable-line-numbers" data-line="5-8"}
+```json {class="line-numbers linkable-line-numbers" data-line="5-9"}
 {
   "module_id": "example-module",
   ...
@@ -94,11 +94,24 @@ At the end of your <file>meta.json</file>, add the build configuration:
     "build": "./build.sh", // command that will build your module's tarball
     "path" : "dist/archive.tar.gz", // optional - path to your built module tarball
     "arch" : ["linux/amd64", "linux/arm64", "darwin/arm64"], // architecture(s) to build for
-    "darwin_deps" : ["go", "x264", "nlopt-static"] // optional - Homebrew dependencies for Darwin builds. Explicitly pass `[]` for empty. Default : ["go", "pkg-config", "nlopt-static", "x264", "jpeg-turbo", "ffmpeg"].
+    "darwin_deps" : ["go", "x264", "nlopt-static"] // optional - Homebrew dependencies for Darwin builds. Explicitly pass `[]` for empty.
   }
 }
 ```
 
+{{% expand "Cloud build configuration attributes" %}}
+
+<!-- prettier-ignore -->
+| Attribute | Inclusion | Description |
+| --------- | --------- | ----------- |
+| `"setup"` | Optional | Command to run for setting up the build environment. |
+| `"build"` | **Required** | Command to run to build the module tarball. |
+| `"path"` | Optional | Path to the build module tarball. |
+| `"arch"` | **Required** | Array of architectures to build for. Options: `"any"`, `"linux/any"`, `"darwin/any"`, `"any/amd64"`, `"any/arm64"`, `"any/arm32v6"`, `"any/arm32v7"`, `"linux/amd64"`, `"linux/arm64"`, `"linux/arm32v6"`, `"linux/arm32v7"`, `"darwin/amd64"`, `"darwin/arm64"`, `"windows/amd64"`. For more information see [Supported platforms for automatic updates](#supported-platforms-for-automatic-updates). |
+| `"darwin_deps"` | **Required** | Array of homebrew dependencies for Darwin builds. Explicitly pass `[]` for empty. Default: `["go", "pkg-config", "nlopt-static", "x264", "jpeg-turbo", "ffmpeg"]` |
+
+{{% /expand %}}
+
 {{< expand "Python module example" >}}
 
 The following code snippet demonstrates an example `setup.sh` for a Python module:
@@ -244,6 +257,26 @@ For more details, see the [`upload-module` GitHub Action documentation](https://
 
    Once the build is complete, the module will automatically update in the [Viam Registry](https://app.viam.com/registry), and the machines set to use the latest [version](/operate/reference/module-configuration/#module-versioning) of the module will automatically update to the new version.
 
+#### Supported platforms for automatic updates
+
+When using cloud build, you can specify which platforms you want to build your module for in the `arch` field of your `meta.json` file.
+The following table lists all available platforms:
+
+<!-- prettier-ignore -->
+| Platform | Recommended | Supported in cloud build | Container used by cloud build | Notes |
+|----------|-------------|--------------------------|------------------------------|-------|
+| `linux/amd64` | ✅ | ✅ | Ubuntu | Standard x86_64 Linux platform, |
+| `linux/arm64` | ✅ | ✅ | Ubuntu | For ARM64 Linux devices like Raspberry Pi 4, |
+| `darwin/arm64` | ✅ | ✅ | macOS | For Apple Silicon Macs (M1/M2/M3). |
+| `linux/arm32v6` | ✅ | ❌ | N/A | For older ARM devices; must be built manually. |
+| `linux/arm32v7` | ✅ | ❌ | N/A | For 32-bit ARM devices; must be built manually. |
+| `windows/amd64` | ✅ | ⚠️ | N/A | <ul><li>Cloud builds work for Go modules but have issues. linking to C libraries.</li><li>Windows support is still in development.</li></ul> |
+| `darwin/amd64` | ❌ | ❌ | N/A | Intel Macs; not recommended as Apple is phasing this platform out |
+
+{{% alert title="Note" color="note" %}}
+While the registry supports additional platforms like `windows/amd64`, `linux/arm32v6`, and `linux/arm32v7`, these are not currently supported by cloud build and must be [built and uploaded manually](#update-manually).
+{{% /alert %}}
+
 ### Update manually
 
 Use the [Viam CLI](/dev/tools/cli/) to manually update your module:
@@ -352,8 +385,8 @@ To transfer ownership of a module from one organization to another:
 1. Select the new organization from the dropdown menu, then click **Transfer module**.
 
 1. (Recommended) Transfer the GitHub repository containing the module code to the new owner.
-   Be sure to remove the existing secrets from the repository’s settings before transferring.
-   If the repository is using Viam’s cloud build, the secrets contain an organization API key that will be exposed to the new owner after the repository transfer.
+   Be sure to remove the existing secrets from the repository's settings before transferring.
+   If the repository is using Viam's cloud build, the secrets contain an organization API key that will be exposed to the new owner after the repository transfer.
 
 1. Update the `meta.json` file to reflect the new organization: