Update links and aliases (#3808)

JessamyT · npentrel · commit 953fe67fd92f · 2025-01-07T22:02:41.000+01:00
diff --git a/docs/operate/get-started/other-hardware/_index.md b/docs/operate/get-started/other-hardware/_index.md
@@ -10,6 +10,7 @@ aliases:
   - /use-cases/create-module/
   - /how-tos/create-module/
   - /how-tos/sensor-module/
+  - /registry/advanced/iterative-development/
 prev: "/operate/get-started/supported-hardware/"
 next: "/operate/get-started/other-hardware/hello-world-module/"
 ---
@@ -831,7 +832,7 @@ viam module upload --version 1.0.0 --platform any module.tar.gz
 
 For details on platform support, see [Using the `--platform` argument](/dev/tools/cli/#using-the---platform-argument).
 
-For details about versioning, see [Module versioning](/operate/get-started/supported-hardware/#module-versioning).
+For details about versioning, see [Module versioning](/operate/reference/module-configuration/#module-versioning).
 
 {{% alert title="Important" color="note" %}}
 The `viam module upload` command only supports one `platform` argument at a time.
@@ -879,7 +880,7 @@ You can use the following package and upload method if you opted not to enable c
 
     For details on platform support, see [Using the `--platform` argument](/dev/tools/cli/#using-the---platform-argument).
 
-    For details about versioning, see [Module versioning](/operate/get-started/supported-hardware/#module-versioning).
+    For details about versioning, see [Module versioning](/operate/reference/module-configuration/#module-versioning).
 
 {{% alert title="Important" color="note" %}}
 The `viam module upload` command only supports one `platform` argument at a time.
@@ -897,7 +898,7 @@ From within your module's directory, run the `viam module upload` CLI command to
 viam module upload --version 1.0.0 --platform <platform> .
 ```
 
-For details about versioning, see [Module versioning](/operate/get-started/supported-hardware/#module-versioning).
+For details about versioning, see [Module versioning](/operate/reference/module-configuration/#module-versioning).
 
 {{% alert title="Important" color="note" %}}
 The `viam module upload` command only supports one `platform` argument at a time.
diff --git a/docs/operate/get-started/other-hardware/cpp-module.md b/docs/operate/get-started/other-hardware/cpp-module.md
@@ -17,7 +17,7 @@ draft: true # Take out Go and Python, and check updatedness before un-drafting.
 ---
 
 Viam provides built-in support for a variety of different {{< glossary_tooltip term_id="component" text="components" >}} and {{< glossary_tooltip term_id="service" text="services" >}}, as well as a registry full of {{< glossary_tooltip term_id="module" text="modules" >}} created by other users.
-If no [existing modules](/registry/modular-resources/) support your specific use case, you can write your own custom modular {{< glossary_tooltip term_id="resource" text="resources" >}} by creating a module, and either upload it to the [Viam Registry](https://app.viam.com/registry) to share it publicly, or deploy it to your machine as a local module without uploading it to the registry.
+If no [existing modules](/operate/get-started/supported-hardware/) support your specific use case, you can write your own custom modular {{< glossary_tooltip term_id="resource" text="resources" >}} by creating a module, and either upload it to the [Viam Registry](https://app.viam.com/registry) to share it publicly, or deploy it to your machine as a local module without uploading it to the registry.
 
 Follow the instructions below to learn how to write a new module using your preferred language and its corresponding [Viam SDK](/dev/reference/sdks/), and then deploy it to your machines.
 
@@ -175,7 +175,7 @@ For more Python module examples:
 
 - See the [Python SDK `examples` directory](https://github.com/viamrobotics/viam-python-sdk/tree/main/examples) for sample module code of varying complexity.
 - For an example featuring a sensor, see [MCP300x](https://github.com/viam-labs/mcp300x-adc-sensor).
-- For additional examples use the [modular resources search](/registry/modular-resources/) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
+- For additional examples use the [modular resources search](/operate/get-started/supported-hardware/#for-use-with-64-bit-architecture) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
 
 {{% /tab %}}
 {{% tab name="Go" %}}
@@ -190,7 +190,7 @@ For more Python module examples:
 For more Go module examples:
 
 - See the [Go SDK `examples` directory](https://github.com/viamrobotics/rdk/blob/main/examples/) for sample module code of varying complexity.
-- For additional examples use the [modular resources search](/registry/modular-resources/) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
+- For additional examples use the [modular resources search](/operate/get-started/supported-hardware/#for-use-with-64-bit-architecture) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
 
 {{% /tab %}}
 {{% tab name="C++" %}}
@@ -661,7 +661,7 @@ func (b *myBase) Close(ctx context.Context) error {
 {{< alert title="Note" color="note" >}}
 For an example featuring a sensor, see [MCP3004-8](https://github.com/mestcihazal/mcp3004-8-go).
 
-For additional examples use the [modular resources search](/registry/modular-resources/) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
+For additional examples use the [modular resources search](/operate/get-started/supported-hardware/#for-use-with-64-bit-architecture) to search for examples of the model you are implementing, and click on the model's link to be able to browse its code.
 {{< /alert >}}
 
 When implementing built-in methods from the Viam Go SDK in your model, be sure your implementation of those methods returns any values designated in the built-in method's return signature, typed correctly.
@@ -1477,7 +1477,7 @@ Strings of the form `<INSERT X>` indicate placeholders that you need to replace
 ````md
 # [`<INSERT MODULE NAME>` module](<INSERT LINK TO MODULE REPO>)
 
-This [module](https://docs.viam.com/registry/modular-resources/) implements the [`<INSERT API TRIPLET>` API]<INSERT LINK TO DOCS (if applicable)> in an <INSERT MODEL> model.
+This [module](https://docs.viam.com/operate/get-started/supported-hardware/) implements the [`<INSERT API TRIPLET>` API]<INSERT LINK TO DOCS (if applicable)> in an <INSERT MODEL> model.
 With this model, you can...
 
 ## Requirements
@@ -1608,7 +1608,7 @@ To test: `make test`
 
 {{% alert title="Tip" color="tip" %}}
 
-If you would like to test your module locally against a target platform other than your development machine before uploading it, you can follow the steps for [Iterative module development](/registry/advanced/iterative-development/) to verify that any code changes you have made work as expected on your target platform.
+If you would like to test your module locally against a target platform other than your development machine before uploading it, you can for example sync your code to an SBC with architecture that matches your target platform, and test your module there to verify that any code changes you have made work as expected on your target platform.
 
 {{% /alert %}}
 
@@ -1661,7 +1661,7 @@ See [Update and manage modules you created](/operate/get-started/other-hardware/
 You have now created a module, and are ready to deploy it to a fleet of machines.
 There are two ways to deploy a module:
 
-- Through the Viam Registry: Once you have uploaded your new module to the Viam Registry, [add the module to one or more machines in the Viam app](/registry/modular-resources/).
+- Through the Viam Registry: Once you have uploaded your new module to the Viam Registry, [add the module to one or more machines in the Viam app](/operate/get-started/supported-hardware/#configure-hardware-on-your-machine).
   You can also choose to configure [automated uploads for new module versions](/operate/get-started/other-hardware/manage-modules/#update-an-existing-module-using-a-github-action) through a continuous integration (CI) workflow, using a GitHub Action if desired, greatly simplifying how you push changes to your module to the registry as you make them.
 - As a local module (without uploading it to the Viam app), as you did in the [Test your module locally step above](#test-your-module-locally).
   This is a great way to test, but if you'd like to use the module on more machines it's easiest to add it to the registry either publicly or privately.
diff --git a/docs/operate/get-started/supported-hardware/_index.md b/docs/operate/get-started/supported-hardware/_index.md
@@ -6,6 +6,12 @@ layout: "docs"
 type: "docs"
 description: "Use supported hardware with your machine."
 modulescript: true
+aliases:
+  - program/extend/modular-resources/configure/
+  - /extend/modular-resources/configure/
+  - /modular-resources/configure/
+  - /registry/configure/
+  - /registry/modular-resources/
 prev: "/operate/get-started/setup/"
 next: "/operate/get-started/other-hardware/"
 ---
diff --git a/docs/operate/reference/architecture/_index.md b/docs/operate/reference/architecture/_index.md
@@ -84,7 +84,7 @@ If you want to add some other high-level software functionality beyond the built
 
 <img src="https://assets-global.website-files.com/62fba5686b6d47fe2a1ed2a6/63334e5e19a68d329b1c5b0e_viam-overview-illustrations-manage.svg" alt="A diagram illustrating secure machine control." class="alignleft" style="width:270px;"></img>
 
-Viam uses peer-to-peer communication, where all machines running `viam-server` or [`viam-micro-server`](/installation/viam-micro-server-dev/) (the version of `viam-server` for microcontrollers) communicate directly with each other as well as with the cloud.
+Viam uses peer-to-peer communication, where all machines running `viam-server` or [`viam-micro-server`](/operate/reference/viam-micro-server/) (the version of `viam-server` for microcontrollers) communicate directly with each other as well as with the cloud.
 This peer-to-peer connectivity is enabled by sending [gRPC commands over WebRTC connections](/operate/reference/architecture/machine-to-machine-comms/#low-level-inter-robotsdk-communication).
 
 On startup, `viam-server` establishes a {{< glossary_tooltip term_id="webrtc" text="WebRTC" >}} connection with the [Viam app](https://app.viam.com).
diff --git a/docs/operate/reference/components/camera/esp32-camera.md b/docs/operate/reference/components/camera/esp32-camera.md
@@ -33,9 +33,9 @@ For example, the `OV2640` with a ribbon cable connected to an ESP32:
 {{< imgproc src="/components/camera/esp32-camera-2640.png" alt="Fake Camera on the ESP32" resize="300x" >}}
 
 {{< alert title="Software requirements" color="note" >}}
-To use this model, you must follow the [`viam-micro-server` Development Setup](/installation/viam-micro-server-dev/), which enables you to install and activate the ESP-IDF.
-At the step [Generate a new project from a template](/installation/viam-micro-server-dev/#creating-a-project-or-module) where you create a new project with `cargo generate`, select the option to include camera module traits when prompted.
-Finish the [`viam-micro-server` Development Setup](/installation/viam-micro-server-dev/) and return to this guide.
+To use this model, you must follow the [`viam-micro-server` Development Setup](/operate/get-started/other-hardware/micro-module/), which enables you to install and activate the ESP-IDF.
+At the step [Generate a new project from a template](/operate/get-started/other-hardware/micro-module/#creating-a-project-or-module) where you create a new project with `cargo generate`, select the option to include camera module traits when prompted.
+Finish the [`viam-micro-server` Development Setup](/operate/get-started/other-hardware/micro-module/) and return to this guide.
 {{< /alert >}}
 
 {{< alert title="Data management not supported" color="caution" >}}
diff --git a/docs/operate/reference/components/camera/fake-micro-server.md b/docs/operate/reference/components/camera/fake-micro-server.md
@@ -18,9 +18,9 @@ A `fake` camera is a camera model for testing.
 The camera always returns the same image, which is an image of a circle inside a diamond.
 
 {{< alert title="Software requirements" color="note" >}}
-To use this model, you must follow the [`viam-micro-server` Development Setup](/installation/viam-micro-server-dev/), which enables you to install and activate the ESP-IDF.
-At the step [Generate a new project from a template](/installation/viam-micro-server-dev/#creating-a-project-or-module) where you create a new project with `cargo generate`, select the option to include camera module traits when prompted.
-Finish the [`viam-micro-server` Development Setup](/installation/viam-micro-server-dev/) and return to this guide.
+To use this model, you must follow the [`viam-micro-server` Development Setup](/operate/get-started/other-hardware/micro-module/), which enables you to install and activate the ESP-IDF.
+At the step [Generate a new project from a template](/operate/get-started/other-hardware/micro-module/#creating-a-project-or-module) where you create a new project with `cargo generate`, select the option to include camera module traits when prompted.
+Finish the [`viam-micro-server` Development Setup](/operate/get-started/other-hardware/micro-module/) and return to this guide.
 {{< /alert >}}
 
 {{< tabs name="Configure a Fake Camera" >}}
diff --git a/static/include/micro-rdk-hardware.md b/static/include/micro-rdk-hardware.md
@@ -15,5 +15,5 @@ Your microcontroller should have at least the following resources available to w
 The main difference between the WROOM and WROVER is that the WROVER has additional RAM with the SPIRAM chip.
 If you would like to allow more than one concurrent connection to your device we recommend using the WROVER.
 The WROVER allows a max of 3 incoming gRPC connections (whether over HTTP2 or WebRTC).
-You can change this max by [building your own version of `viam-micro-server`](/installation/viam-micro-server-dev/).
+You can change this max by [building your own version of `viam-micro-server`](/operate/get-started/other-hardware/micro-module/).
 {{< /alert >}}
