Fix 13 app-linked anchor URLs across 10 pages (#4975)

shannonbradshaw · claude · web-flow · commit 12b6514329bb · 2026-04-18T14:16:18.000-04:00
Co-authored-by: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/docs/build-modules/write-a-logic-module.md b/docs/build-modules/write-a-logic-module.md
@@ -39,7 +39,7 @@ lifecycle, config validation, dependency, and deployment patterns are the same.
 For background on the generic service API, module lifecycle, dependencies, and
 background tasks, see the [overview](/build-modules/overview/).
 
-## Steps
+## Steps {#program-control-logic-in-module}
 
 When writing a logic module, follow the steps outlined below. To illustrate
 each step we'll use a temperature alert monitor as a worked example. It watches
diff --git a/docs/data/_index.md b/docs/data/_index.md
@@ -32,7 +32,6 @@ aliases:
   - /use-cases/image-data/
   - /get-started/collect-data/
   - /fleet/data-management/
-  - /data-ai/capture-data/capture-sync/
   - /data/data-capture-reference/
   - /data/how-sync-works/
   - /data-ai/capture-data/advanced/how-sync-works/
diff --git a/docs/data/capture-sync/capture-and-sync-data.md b/docs/data/capture-sync/capture-and-sync-data.md
@@ -10,6 +10,7 @@ aliases:
   - /data/capture-and-sync-data/
   - /build/foundation/capture-and-sync-data/
   - /foundation/capture-and-sync-data/
+  - /data-ai/capture-data/capture-sync/
 ---
 
 Configure your machine to automatically record sensor readings, camera images, and other component data, then sync it to the cloud. For an overview of how data capture and sync work, see the [Manage data overview](/data/overview/).
@@ -19,7 +20,7 @@ Configure your machine to automatically record sensor readings, camera images, a
 Go to [app.viam.com](https://app.viam.com) and navigate to your machine.
 Confirm it shows as **Live** in the upper left.
 
-## 2. Enable data capture on a component
+## 2. Enable data capture on a component {#configure-data-capture}
 
 1. Find your component (for example, `my-camera`) in the machine configuration.
 2. Click the **Data Capture** button.
@@ -87,6 +88,27 @@ Wait 30 seconds to a minute for data to accumulate and sync, then:
 
 If you see data flowing in, capture and sync are working correctly.
 
+## Supported resources {#supported-resources}
+
+Any built-in or modular component that implements a capturable method can be configured for data capture. The following table lists the most commonly captured component types and their methods:
+
+| Component type  | Capturable methods                                                                                                                      |
+| --------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| Camera          | `ReadImage`, `GetImages`, `NextPointCloud`                                                                                              |
+| Sensor          | `GetReadings`                                                                                                                           |
+| Movement sensor | `GetPosition`, `GetLinearVelocity`, `GetAngularVelocity`, `GetCompassHeading`, `GetLinearAcceleration`, `GetOrientation`, `GetReadings` |
+| Encoder         | `GetTicksCount`                                                                                                                         |
+| Motor           | `GetPosition`, `IsPowered`                                                                                                              |
+| Power sensor    | `GetVoltage`, `GetCurrent`, `GetPower`, `GetReadings`                                                                                   |
+| Servo           | `GetPosition`                                                                                                                           |
+| Arm             | `GetEndPosition`, `GetJointPositions`                                                                                                   |
+| Gantry          | `GetPosition`, `GetLengths`                                                                                                             |
+| Board           | `Analogs`, `Gpios`                                                                                                                      |
+| Vision service  | `CaptureAllFromCamera`                                                                                                                  |
+| SLAM service    | `GetPosition`, `GetPointCloudMap`                                                                                                       |
+
+Every component and service also supports capturing `DoCommand` responses. Modular components that return readings through any of these methods are automatically capturable.
+
 ## Troubleshooting
 
 {{< expand "No data appears in the Data tab" >}}
diff --git a/docs/data/visualize-data.md b/docs/data/visualize-data.md
@@ -43,7 +43,9 @@ Custom visualization with Viam SDKs gives you complete control. You write code t
 queries data through the Viam SDK and renders it however you want -- matplotlib
 charts, Plotly dashboards, HTML reports, or any other format.
 
-## Build a Viam Teleop dashboard
+<a id="dashboard"></a>
+
+## Build a Viam Teleop dashboard {#teleop}
 
 The Viam Teleop dashboard is the fastest way to visualize data from a single machine.
 
diff --git a/docs/fleet/provision-devices.md b/docs/fleet/provision-devices.md
@@ -35,7 +35,7 @@ If you are setting up a small number of machines manually, you can skip provisio
 - A [fragment](/fleet/reuse-configuration/) with the configuration your machines should use. Note the fragment ID.
 - A device with a supported Linux OS. See the [platform requirements](/set-up-a-machine/) for supported platforms.
 
-## 1. Create the defaults file
+## 1. Create the defaults file {#configure-agent-provisioning}
 
 Create a file called `viam-defaults.json` that defines the provisioning behavior. At minimum, specify a `fragment_id`.
 
diff --git a/docs/fleet/system-settings.md b/docs/fleet/system-settings.md
@@ -54,7 +54,7 @@ In the machine settings card, open **Settings** and expand **Known Networks**. C
 | `ipv4_gateway`      | string  | —        | IPv4 gateway address.                                                                      |
 | `ipv4_route_metric` | integer | `0`      | Route metric. Lower values are preferred. `0` defaults to 100 for wired, 600 for wireless. |
 
-## Configure tunneling
+## Configure tunneling {#configure-networking-settings-for-tunneling}
 
 Allow secure port forwarding from a local machine to a remote machine through Viam's cloud connection. You must list allowed ports in the machine configuration.
 
diff --git a/docs/hardware/configure-hardware.md b/docs/hardware/configure-hardware.md
@@ -56,6 +56,10 @@ You don't need to think about where a model comes from. The Viam app shows all a
 
 If no model exists for your hardware, you can [write your own module](/build-modules/write-a-driver-module/) that provides a model implementing the component API.
 
+<a id="browse-supported-hardware-by-component-api"></a>
+
+Browse all available components and services in the [Viam registry](https://app.viam.com/registry).
+
 ## Switching hardware without changing code
 
 Because every model of a given type exposes the same API, your application code does not change when you swap hardware.
@@ -70,7 +74,7 @@ This works whether `drive-motor` is configured as a `gpio` motor on a Raspberry
 To switch hardware, you change the model and attributes in your machine's configuration.
 Your code stays the same.
 
-## Add a component
+## Add a component {#configure-hardware-on-your-machine}
 
 The process for adding any component is the same whether you're adding a motor,
 a sensor, a board, or anything else. For step-by-step guides for specific
diff --git a/docs/hardware/multi-machine/overview.md b/docs/hardware/multi-machine/overview.md
@@ -33,7 +33,7 @@ Unless you configure a prefix, even the name stays the same.
 
 Viam gives you two ways to create this connection: sub-parts and remote parts.
 
-## Pick a pattern
+## Pick a pattern {#machine-parts}
 
 <!-- prettier-ignore -->
 | | Sub-part | Remote part |
diff --git a/docs/reference/device-setup/_index.md b/docs/reference/device-setup/_index.md
@@ -1,8 +1,34 @@
 ---
-title: "Device Setup"
-linkTitle: "Device Setup"
+title: "Device setup guides"
+linkTitle: "Device setup"
 weight: 55
+layout: "docs"
 type: "docs"
-no_list: true
-description: "Setup guides for single-board computers and other devices supported by Viam."
+description: "Board-specific setup instructions for single-board computers and microcontrollers supported by Viam."
 ---
+
+Before installing Viam on a single-board computer, follow the setup guide for your board to ensure the OS and firmware are ready.
+
+## Single-board computers
+
+| Board                          | Guide                                                                   |
+| ------------------------------ | ----------------------------------------------------------------------- |
+| Raspberry Pi (all models)      | [Raspberry Pi setup](/reference/device-setup/rpi-setup/)                |
+| NVIDIA Jetson Nano / Orin Nano | [Jetson Nano setup](/reference/device-setup/jetson-nano-setup/)         |
+| NVIDIA Jetson AGX Orin         | [Jetson AGX Orin setup](/reference/device-setup/jetson-agx-orin-setup/) |
+| BeagleBone AI-64               | [BeagleBone setup](/reference/device-setup/beaglebone-setup/)           |
+| Orange Pi Zero 2               | [Orange Pi Zero2 setup](/reference/device-setup/orange-pi-zero2/)       |
+| Orange Pi 3 LTS                | [Orange Pi 3 LTS setup](/reference/device-setup/orange-pi-3-lts/)       |
+| ODROID-C4                      | [ODROID-C4 setup](/reference/device-setup/odroid-c4-setup/)             |
+| Pumpkin                        | [Pumpkin setup](/reference/device-setup/pumpkin/)                       |
+| SK-TDA4VM                      | [SK-TDA4VM setup](/reference/device-setup/sk-tda4vm/)                   |
+
+## Microcontrollers
+
+| Board | Guide                                                   |
+| ----- | ------------------------------------------------------- |
+| ESP32 | [Set up an ESP32](/reference/device-setup/setup-micro/) |
+
+## After setup
+
+Once your board is ready, return to [Set up a machine](/set-up-a-machine/) to install Viam and connect to the cloud.
diff --git a/docs/set-up-a-machine/overview.md b/docs/set-up-a-machine/overview.md
@@ -50,18 +50,13 @@ A banner prompts you to set up the machine part.
 1. Click **View setup instructions** in the banner.
 2. In the wizard dialog that opens, click **Go to Advanced setup**.
 
-## 3. Select your platform
+## 3. Select your platform {#sbc-setup-instructions}
 
 Use the **Platform you want to run on** dropdown to select the operating system and architecture of the compute machine for your robot, the computer to which you've attached cameras, sensors, arms, or other components.
 
 Options include Linux / Aarch64, Linux / x86, Mac, Windows native, Windows (WSL), Linux / Armv7l, and ESP32.
 
-{{< alert title="Tip" color="tip" >}}
-
-If you're using a single-board computer like a Raspberry Pi or NVIDIA Jetson, make sure it's running a compatible Linux OS before continuing.
-The setup page links to an [installation guide](/reference/device-setup/) for supported single-board computers.
-
-{{< /alert >}}
+If you're using a single-board computer, make sure it's running a compatible Linux OS before continuing. See [Device setup guides](/reference/device-setup/) for board-specific instructions.
 
 ## 4. Select your installation method
 
diff --git a/docs/train/train-a-model.md b/docs/train/train-a-model.md
@@ -264,6 +264,31 @@ for _, job := range jobs {
 
 {{< /expand >}}
 
+## Upload your training script {#upload-your-training-script}
+
+To use your own training script instead of a built-in training type:
+
+1. Package your script with a `setup.py` or `pyproject.toml`. Viam invokes it as `python3 -m model.training`.
+2. Upload with the CLI:
+
+   ```sh {class="command-line" data-prompt="$"}
+   viam training-script upload --path=<path-to-script> --org-id=<org-id> --script-name=<name>
+   ```
+
+3. Submit a training job that references your script (from the web UI or CLI).
+
+For the full walkthrough including local testing with Docker, see [Custom training scripts](/train/custom-training-scripts/).
+
+## Parse command line inputs {#click-for-more-information-on-parsing-command-line-inputs}
+
+When you submit a training job with custom arguments, Viam passes them to your training script as command-line flags. Your script receives:
+
+- `--dataset_file`: path to the dataset manifest (default: `dataset.jsonl`)
+- `--model_output_directory`: where to write the trained model (fixed: `/model_output`)
+- Any custom arguments you defined, as `--key=value` pairs
+
+Argument keys must be alphanumeric with underscores or hyphens. For full details on writing and testing training scripts, see [Custom training scripts](/train/custom-training-scripts/).
+
 ## What's next
 
 - [Deploy a model to a machine](/train/deploy-a-model/) -- configure the module,
