Fix prettier and revert service links not yet on main

shannonbradshaw · claude · shannonbradshaw · commit f502e0175590 · 2026-04-20T13:36:44.000-04:00
Keep base-rc, discovery, generic, navigation, and slam service links
pointing to /operate/reference/services/ since those pages haven't
been migrated to /reference/services/ on main yet. Also fix prettier
formatting on monitor/overview.md.

Co-Authored-By: Claude Opus 4.6 (1M context) &lt;noreply@anthropic.com&gt;
diff --git a/docs/build-modules/write-a-cpp-module.md b/docs/build-modules/write-a-cpp-module.md
@@ -61,7 +61,7 @@ For example, the [sensor API](/reference/apis/components/sensor/) has a `GetRead
 If instead of just getting readings, you actually have an encoder and need to be able to reset the zero position, use the [encoder API](/reference/apis/components/encoder/) so you can define functionality behind the `GetPosition` and `ResetPosition` methods.
 
 In addition to the list of methods, another reason to choose one API over another is how certain APIs fit into the Viam ecosystem.
-For example, though you could technically implement a GPS as a sensor with just the `GetReadings` method, if you implement it as a movement sensor then you have access to methods like `GetCompassHeading` which allow you to use your GPS module with the [navigation service](/reference/services/navigation/).
+For example, though you could technically implement a GPS as a sensor with just the `GetReadings` method, if you implement it as a movement sensor then you have access to methods like `GetCompassHeading` which allow you to use your GPS module with the [navigation service](/operate/reference/services/navigation/).
 For this reason, it's generally best to choose the API that most closely matches your hardware or software.
 {{< /expand >}}
 
diff --git a/docs/monitor/overview.md b/docs/monitor/overview.md
@@ -65,11 +65,11 @@ See [Troubleshoot problems](/monitor/troubleshoot/).
 
 This section covers tools for monitoring, operating, and debugging machines that are already configured and running.
 
-| If you need to...                              | See                                     |
-| ---------------------------------------------- | --------------------------------------- |
-| Set up a machine for the first time            | [Get started](/set-up-a-machine/)       |
-| Configure components and services              | [Configure hardware](/hardware/)        |
-| Capture and sync data from sensors             | [Manage data](/data/)                   |
-| Train and deploy ML models                     | [Train ML models](/train/)              |
+| If you need to...                              | See                                 |
+| ---------------------------------------------- | ----------------------------------- |
+| Set up a machine for the first time            | [Get started](/set-up-a-machine/)   |
+| Configure components and services              | [Configure hardware](/hardware/)    |
+| Capture and sync data from sensors             | [Manage data](/data/)               |
+| Train and deploy ML models                     | [Train ML models](/train/)          |
 | Build a custom web or mobile app with the SDKs | [Build apps](/build-apps/overview/) |
-| Manage fleet deployment and provisioning       | [Fleet deployment](/fleet/)             |
+| Manage fleet deployment and provisioning       | [Fleet deployment](/fleet/)         |
diff --git a/docs/reference/apis/services/base-rc.md b/docs/reference/apis/services/base-rc.md
@@ -16,7 +16,7 @@ aliases:
 
 The base remote control service API allows you to get a list of inputs from the controller that are being monitored for that control mode.
 
-The [Base remote control service](/reference/services/base-rc/) supports the following methods:
+The [Base remote control service](/operate/reference/services/base-rc/) supports the following methods:
 
 {{< readfile "/static/include/services/apis/generated/base_remote_control-table.md" >}}
 
diff --git a/docs/reference/apis/services/discovery.md b/docs/reference/apis/services/discovery.md
@@ -12,7 +12,7 @@ aliases:
 ---
 
 The discovery service API allows you to get a list of resources available to configure on a machine based on the hardware that is connected to or part of the machine.
-Discoverable resources can include components that are physically connected to the machine, as well as components that are available on the machine's local network (depending on the implementation of the [discovery service](/reference/services/discovery/)).
+Discoverable resources can include components that are physically connected to the machine, as well as components that are available on the machine's local network (depending on the implementation of the [discovery service](/operate/reference/services/discovery/)).
 
 The discovery service supports the following methods:
 
diff --git a/docs/reference/apis/services/generic.md b/docs/reference/apis/services/generic.md
@@ -14,7 +14,7 @@ aliases:
 # updated: ""  # When the content was last entirely checked
 ---
 
-The generic service API allows you to give commands to your [generic services](/reference/services/generic/) for running model-specific commands using [`DoCommand`](/reference/apis/services/generic/#docommand).
+The generic service API allows you to give commands to your [generic services](/operate/reference/services/generic/) for running model-specific commands using [`DoCommand`](/reference/apis/services/generic/#docommand).
 
 The generic service supports the following methods:
 
diff --git a/docs/reference/apis/services/navigation.md b/docs/reference/apis/services/navigation.md
@@ -16,7 +16,7 @@ aliases:
 
 The navigation service API allows you to define waypoints and move your machine along those waypoints while avoiding obstacles.
 
-The [navigation service](/reference/services/navigation/) supports the following methods:
+The [navigation service](/operate/reference/services/navigation/) supports the following methods:
 
 {{< readfile "/static/include/services/apis/generated/navigation-table.md" >}}
 
diff --git a/docs/reference/glossary/slam.md b/docs/reference/glossary/slam.md
@@ -9,4 +9,4 @@ aliases:
 
 SLAM (Simultaneous Localization and Mapping) algorithms use data from a machine's sensors, like LiDARs, cameras, and movement sensors, to generate a map of the environment and determine the machine's position within it.
 
-For more information, see [SLAM](/reference/services/slam/).
+For more information, see [SLAM](/operate/reference/services/slam/).
diff --git a/docs/tutorials/control/gamepad.md b/docs/tutorials/control/gamepad.md
@@ -123,7 +123,7 @@ To link the controller input to the base functionality, you need to add the base
 ## Add the base remote control service
 
 Services are software packages that provide robots with higher level functionality.
-To link the controller's input to the base functionality, you need to configure the [base remote control service](/reference/services/base-rc/):
+To link the controller's input to the base functionality, you need to configure the [base remote control service](/operate/reference/services/base-rc/):
 
 {{< tabs >}}
 {{% tab name="Config Builder" %}}
diff --git a/docs/tutorials/services/navigate-with-rover-base.md b/docs/tutorials/services/navigate-with-rover-base.md
@@ -37,7 +37,7 @@ weight: 5
 # SMEs: Ray Bjorkman, Fahmina
 ---
 
-The [navigation service](/reference/services/navigation/) allows you to queue up user-defined waypoints for your machine to move to in the order that you specify.
+The [navigation service](/operate/reference/services/navigation/) allows you to queue up user-defined waypoints for your machine to move to in the order that you specify.
 You can also add obstacles or set linear and angular velocity targets in your navigation service config.
 Viam's motion planner will plan routes that avoid those obstacles and attempt to keep the robot at your specified velocity.
 
@@ -72,7 +72,7 @@ Follow this tutorial to get started using Viam's Navigation service to help your
    3. A [`merged`](/reference/components/movement-sensor/merged/) model aggregating the readings together for the navigation service to consume.
 
    You can use any combo of movement sensors you want as long as you are getting all the types of measurements required.
-   See [the navigation service](/reference/services/navigation/#requirements) for more info on movement sensor requirements.
+   See [the navigation service](/operate/reference/services/navigation/#requirements) for more info on movement sensor requirements.
 
 {{% alert title="Tip" color="tip" %}}
 
@@ -456,15 +456,15 @@ To add the navigation service to your robot, do the following:
    ```
 
    Edit the attributes as applicable.
-   Attribute information is available in [the navigation service documentation](/reference/services/navigation/#configuration).
+   Attribute information is available in [the navigation service documentation](/operate/reference/services/navigation/#configuration).
 
 1. Click **Save** in the top right corner of the screen to save your changes.
 
 Your navigation service should now appear in your machine's **CONFIGURE** tab as a card with a map like the following:
 
 {{<imgproc src="/tutorials/navigate-with-rover-base/navigation-config-builder.png" resize="1200x" declaredimensions=true alt="Navigation Card" style="width:650px" class="shadow imgzoom" >}}
 
-For more detailed information see [the navigation service](/reference/services/navigation/#configuration).
+For more detailed information see [the navigation service](/operate/reference/services/navigation/#configuration).
 
 {{% /tab %}}
 {{% tab name="JSON" %}}

Original file line number	Diff line number	Diff line change
`@@ -9,4 +9,4 @@ aliases:`
`9`	`9`
`10`	`10`	`SLAM (Simultaneous Localization and Mapping) algorithms use data from a machine's sensors, like LiDARs, cameras, and movement sensors, to generate a map of the environment and determine the machine's position within it.`
`11`	`11`
`12`		`-For more information, see [SLAM](/reference/services/slam/).`
	`12`	`+For more information, see [SLAM](/operate/reference/services/slam/).`