diff --git a/docs/components/_tutorials_link.mdx b/components/_tutorials_link.mdx
similarity index 51%
rename from docs/components/_tutorials_link.mdx
rename to components/_tutorials_link.mdx
index b38a374ad..eea1fe4be 100644
--- a/docs/components/_tutorials_link.mdx
+++ b/components/_tutorials_link.mdx
@@ -9,22 +9,22 @@ These tutorials assume that you are comfortable working with [ROS](https://docs.
You can view all topics that are active using `ros2 topic list`.
-For a general list of topics and descriptions see the [Clearpath API](../ros/api/platform_api.mdx)
+For a general list of topics and descriptions see the [Clearpath API](/docs/ros/api/platform_api)
## Software Setup
-- [Robot Software](../ros/installation/robot.mdx)
-- [Offboard Computer](../ros/installation/offboard_pc.mdx)
-- [PS4 Joystick Controller (if applicable)](../ros/installation/controller.mdx)
+- [Robot Software](/docs/ros/installation/robot)
+- [Offboard Computer](/docs/ros/installation/offboard_pc)
+- [PS4 Joystick Controller (if applicable)](/docs/ros/installation/controller)
## Using your Robot
The following tutorials are recommended to get to know your robot:
-- [Driving your Robot](../ros/tutorials/driving.mdx)
-- [Simulating your Robot](../ros/tutorials/simulator/overview.mdx)
-- [Navigating](../ros/tutorials/navigation_demos/overview.mdx)
+- [Driving your Robot](/docs/ros/tutorials/driving)
+- [Simulating your Robot](/docs/ros/tutorials/simulator/overview)
+- [Navigating](/docs/ros/tutorials/navigation_demos/overview)
## Advanced Topics
-- [Configuring Network Bridge](../ros/networking/computer_setup.mdx)
+- [Configuring Network Bridge](/docs/ros/networking/computer_setup)
diff --git a/docs/components/maintenance/_wd_ssd_critical_update.mdx b/components/maintenance/_wd_ssd_critical_update.mdx
similarity index 100%
rename from docs/components/maintenance/_wd_ssd_critical_update.mdx
rename to components/maintenance/_wd_ssd_critical_update.mdx
diff --git a/components/maintenance/wd_ssd_critical_update.mdx b/components/maintenance/wd_ssd_critical_update.mdx
index 7b4f75bae..138740e76 100644
--- a/components/maintenance/wd_ssd_critical_update.mdx
+++ b/components/maintenance/wd_ssd_critical_update.mdx
@@ -26,7 +26,7 @@ Failure to perform the firmware update could result in permanent failure of the
#### How to update the firmware on affected SSDs
-1. Create an OS image backup of the SSD ([ROS 1 backup details here](/docs/ros1noetic/robots/outdoor_robots/husky/tutorials_husky#performing-a-backup),
+1. Create an OS image backup of the SSD ([ROS 1 backup details here](/docs_robots/legacy/ros1_robots/outdoor_robots/husky/tutorials_husky#performing-a-backup),
[ROS 2 backup details here](/docs/ros/installation/upgrading#saving-a-hard-drive-image)).
1. Remove the SSD from the robot. Ensure that you use an ESD grounded wrist strap when handling SSD or PCB components.
1. Use a USB SSD dock and a Windows computer to perform the update by [following the vendor's instructions](https://support-en.sandisk.com/app/answers/detailweb/a_id/50208#subject2).
diff --git a/components/supported_sensors.mdx b/components/supported_sensors.mdx
index a76f6f7e3..bac7cf03a 100644
--- a/components/supported_sensors.mdx
+++ b/components/supported_sensors.mdx
@@ -9,26 +9,26 @@ sensors that have been validated by Clearpath.
| Sensor | Type | Installation | Driver |
| :----------------------------------------------------------------------------------- | :----------- | :----------- | :------------------------------------------------------------------------------------------ |
-| [SICK LMS-111/LMS-151](../robots/accessories/sensors/lidar_2d/sick_lms111) | 2D Lidar | Debian | [LMS1xx](https://github.com/clearpathrobotics/LMS1xx) |
-| [Hokuyo UST10-LX](../robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
-| [Hokuyo UST20-LX](../robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
-| [Hokuyo UST30-LX](../robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
-| [MicroStrain 3DM-GX5](../robots/accessories/sensors/imu/microstrain_3dm_gx5) | IMU | Debian | [microstrain_intertial](https://github.com/LORD-MicroStrain/microstrain_inertial/tree/ros2) |
-| [MicroStrain 3DM-GQ7](../robots/accessories/sensors/gps/microstrain_gq7) | GPS/IMU | Debian | [microstrain_intertial](https://github.com/LORD-MicroStrain/microstrain_inertial/tree/ros2) |
-| [Redshift Labs UM7](../robots/accessories/sensors/imu/redshift_labs_um7) | IMU | Debian | [um7](https://github.com/ros-drivers/um7/tree/ros2) |
+| [SICK LMS-111/LMS-151](/docs_robots/accessories/sensors/lidar_2d/sick_lms111) | 2D Lidar | Debian | [LMS1xx](https://github.com/clearpathrobotics/LMS1xx) |
+| [Hokuyo UST10-LX](/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
+| [Hokuyo UST20-LX](/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
+| [Hokuyo UST30-LX](/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx) | 2D Lidar | Debian | [urg_node](https://github.com/ros-drivers/urg_node) |
+| [MicroStrain 3DM-GX5](/docs_robots/accessories/sensors/imu/microstrain_3dm_gx5) | IMU | Debian | [microstrain_intertial](https://github.com/LORD-MicroStrain/microstrain_inertial/tree/ros2) |
+| [MicroStrain 3DM-GQ7](/docs_robots/accessories/sensors/gps/microstrain_gq7) | GPS/IMU | Debian | [microstrain_intertial](https://github.com/LORD-MicroStrain/microstrain_inertial/tree/ros2) |
+| [Redshift Labs UM7](/docs_robots/accessories/sensors/imu/redshift_labs_um7) | IMU | Debian | [um7](https://github.com/ros-drivers/um7/tree/ros2) |
| CH Robotics UM6 | IMU | Debian | [um7](https://github.com/ros-drivers/um7/tree/ros2) |
-| [Velodyne Puck](../robots/accessories/sensors/lidar_3d/velodyne_puck) | 3D Lidar | Debian | [velodyne](https://github.com/ros-drivers/velodyne/tree/ros2) |
-| [Garmin GPS 18x](../robots/accessories/sensors/gps/garmin_gps_18x) | GPS | Debian | [nmea_navsat_driver](https://github.com/ros-drivers/nmea_navsat_driver/tree/ros2) |
+| [Velodyne Puck](/docs_robots/accessories/sensors/lidar_3d/velodyne_puck) | 3D Lidar | Debian | [velodyne](https://github.com/ros-drivers/velodyne/tree/ros2) |
+| [Garmin GPS 18x](/docs_robots/accessories/sensors/gps/garmin_gps_18x) | GPS | Debian | [nmea_navsat_driver](https://github.com/ros-drivers/nmea_navsat_driver/tree/ros2) |
| NovAtel SMART6 and SMART7 | GPS | Debian | [nmea_navsat_driver](https://github.com/ros-drivers/nmea_navsat_driver/tree/ros2) |
-| [Swift Navigation Duro](../robots/accessories/sensors/gps/swift_navigation_duro) | GPS | Source | [duro_gps_driver](https://github.com/szenergy/duro_gps_driver/tree/ros2-humble) |
-| [Axis F1035-E](../robots/accessories/sensors/cameras/axis_f1035_e) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
-| [Axis M5525-E](../robots/accessories/sensors/cameras/axis_m5525_e) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
-| [Axis Q6225-LE-E](../robots/accessories/sensors/cameras/axis_q6225_le) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
-| [Flir Blackfly S](../robots/accessories/sensors/cameras/flir_blackfly_s) | Camera | Debian | [flir_camera_driver](https://github.com/ros-drivers/flir_camera_driver/tree/humble-devel) |
-| [Flir Ladybug 5P](../robots/accessories/sensors/cameras/flir_ladybug5p) | Camera | Debian | [flir_camera_driver](https://github.com/ros-drivers/flir_camera_driver/tree/humble-devel) |
-| [Intel Realsense D435](../robots/accessories/sensors/cameras/realsense_d435) | Depth Camera | Debian | [realsense-ros](https://github.com/IntelRealSense/realsense-ros/tree/ros2-development) |
-| [Luxonis OAK-D](../robots/accessories/sensors/cameras/luxonis_oakd) | Depth Camera | Debian | [depthai-ros](https://github.com/luxonis/depthai-ros.git) |
-| [Stereolabs Zed 2](../robots/accessories/sensors/cameras/stereolabs_zed_2) | Depth Camera | Source | [zed-ros2-wrapper](https://github.com/stereolabs/zed-ros2-wrapper.git) |
+| [Swift Navigation Duro](/docs_robots/accessories/sensors/gps/swift_navigation_duro) | GPS | Source | [duro_gps_driver](https://github.com/szenergy/duro_gps_driver/tree/ros2-humble) |
+| [Axis F1035-E](/docs_robots/accessories/sensors/cameras/axis_f1035_e) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
+| [Axis M5525-E](/docs_robots/accessories/sensors/cameras/axis_m5525_e) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
+| [Axis Q6225-LE-E](/docs_robots/accessories/sensors/cameras/axis_q6225_le) | Camera | Debian | [axis_camera](https://github.com/ros-drivers/axis_camera.git) |
+| [Flir Blackfly S](/docs_robots/accessories/sensors/cameras/flir_blackfly_s) | Camera | Debian | [flir_camera_driver](https://github.com/ros-drivers/flir_camera_driver/tree/humble-devel) |
+| [Flir Ladybug 5P](/docs_robots/accessories/sensors/cameras/flir_ladybug5p) | Camera | Debian | [flir_camera_driver](https://github.com/ros-drivers/flir_camera_driver/tree/humble-devel) |
+| [Intel Realsense D435](/docs_robots/accessories/sensors/cameras/realsense_d435) | Depth Camera | Debian | [realsense-ros](https://github.com/IntelRealSense/realsense-ros/tree/ros2-development) |
+| [Luxonis OAK-D](/docs_robots/accessories/sensors/cameras/luxonis_oakd) | Depth Camera | Debian | [depthai-ros](https://github.com/luxonis/depthai-ros.git) |
+| [Stereolabs Zed 2](/docs_robots/accessories/sensors/cameras/stereolabs_zed_2) | Depth Camera | Source | [zed-ros2-wrapper](https://github.com/stereolabs/zed-ros2-wrapper.git) |
:::note
diff --git a/components/using_ros.mdx b/components/using_ros.mdx
index 807f58f67..186bf8732 100644
--- a/components/using_ros.mdx
+++ b/components/using_ros.mdx
@@ -1,4 +1,4 @@
Robot Operating System (ROS) is an extensible framework for controlling and working with robotic systems.
Clearpath Robotics recommends using ROS with your robot. If this is your first time using ROS, it is strongly
-recommended to run through our series of [ROS tutorials](../../../ros) to learn
+recommended to run through our series of [ROS tutorials](/docs/ros) to learn
the basics of ROS.
diff --git a/docs/robots/accessories/add-ons/controllers.mdx b/docs/robots/accessories/add-ons/controllers.mdx
deleted file mode 100644
index 266c61c35..000000000
--- a/docs/robots/accessories/add-ons/controllers.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: Controllers
-sidebar_position: 3
----
-
-| Description | CPR Item |
-| :------------------------------------------------------------------ | :------- |
-| [Logitech F710](#controllers_logitech_f710) | 002071 |
-| [Sony Dualshock](#controllers_sony_dualshock) | 011756 |
-| [Futaba 4GRS](#controllers_futaba_4grs) | 011389 |
-| [FORT Robotics Safe Remote Control](#controllers_fort_robotics_src) | 025725 |
-
-Controllers appear in Ubuntu in the _/dev/input/_ directory.
-Navigate to that directory,and then run `ls` to list the controllers.
-You can view the data stream of the controller by running `jstest /dev/input/js0`, changing the final value to the relevent controller.
-
-:::note
-
-You may need to install _jstest_ with `sudo apt-get install jstest-gtk`
-
-:::
-
-Clearpath uses the _/bluetooth_teleop_ ROS node to publish velocity commands from the joystick to _/twist_mux_.
-_/twist_mux_ Takes in multiple sources of velocity commands, and prioritizes what actually gets sent to _/cmd_vel_ to drive the robot.
-
-Depending on the robot platform and related controller, you will need to configure your robot's [robot.yaml configuration file](../../../ros/config/yaml/platform/controller.mdx).
-
----
-
-## Logitech F710 {#controllers_logitech_f710}
-
-
-
-
-
-
-
-Drivers are included in the current Linux Kernels that Clearpath Robotics uses.
-
-The included USB dongle requires a line-of-sight connection with the handheld controller.
-
----
-
-## Sony Dualshock {#controllers_sony_dualshock}
-
-
-
-
-
-
-
-This conroller requires a Bluetooth connection to the robot's computer.
-
-Linux Driver: https://github.com/clearpathrobotics/ds4drv
-
----
-
-## Futaba 4GRS {#controllers_futaba_4grs}
-
-
-
-
-
-
-
-This controller includes a PCBA that sends data to the ROS computer with a serial connection.
-
-The controller communicates with the PCBA receiver over a 2.4 GHz radio.
-
-Clearpath Robotics has built this controller into the Warthog and Moose platforms.
-
-It can be integrated on other robots, but requires custom integration as there is not an Open Source ROS driver at this time.
-
----
-
-## FORT Robotics controller {#controllers_fort_robotics_src}
-
-
-
-
-
-
-
-Similar to the Logitech controller listed above, the FORT Robotics controller data appears in _/dev/input/_ and uses a Linux Driver included in the current Ubuntu LTS release.
-
-The controller and receiver communicate over a 900 MHz radio, with the specific band configured based on your country.
-
-:::note
-
-The status of the motion-stop button does appear in the data, as well as the other buttons and joysticks.
-
-:::
diff --git a/docs/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx b/docs/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
deleted file mode 100644
index 419a38903..000000000
--- a/docs/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: MicroStrain 3DM-GX5
-sidebar_position: 1
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/microstrain_imu.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :---------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Microstrain 3DM-GX5-10 sensor | [017839](/assets/pdf/clearpath_robotics_017839-TDS1.pdf) | 028963 | 028962 |
-| Microstrain 3DM-GX5-15 sensor | [017772](/assets/pdf/clearpath_robotics_017772-TDS1.pdf) | 027114 | 027215 |
-| Microstrain 3DM-GX5-25 sensor | [014603](/assets/pdf/clearpath_robotics_014603-TDS1.pdf) | 027117 | 027217 |
-| Microstrain 3DM-GX5-35 sensor | [028528](/assets/pdf/clearpath_robotics_028528-TDS1.pdf) | 028964 | 028957 |
-| Microstrain 3DM-GX5-45 sensor | [017391](/assets/pdf/clearpath_robotics_017391-TDS2.pdf) | 028966 | 028965 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :---------------- |
-| Mass | 16.5 - 20 g |
-| Voltage, Minimum | 4 V, or USB |
-| Voltage, Maximum | 36 V, or USB |
-| Power, Maximum | 0.3 - 0.8 W |
-| Data | USB 2.0 or RS-232 |
-| Ingress Protection, Solids | 3 |
-| Ingress Protection, Liquids | 0 |
-| Operating Temperature, Min | -40 °C |
-| Operating Temperature, Max | 85 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store, 3DM-GX5-10](https://store.clearpathrobotics.com/collections/orientation/products/3dm-gx5-10)
-2. [Clearpath Robotics Store, 3DM-GX5-15](https://store.clearpathrobotics.com/collections/vru/products/3dm-gx5-15)
-3. [Clearpath Robotics Store, 3DM-GX5-25](https://store.clearpathrobotics.com/collections/ahrs/products/3dm-gx5-25)
-4. [Clearpath Robotics Store, 3DM-GX5-35](https://store.clearpathrobotics.com/collections/ahrs/products/3dm-gx5-35)
-5. [Clearpath Robotics Store, 3DM-GX5-45](https://store.clearpathrobotics.com/collections/gnss-ins/products/3dm-gx5-45)
-6. [Datasheet, 3DM-GX5-10](/assets/pdf/clearpath_robotics_017839-TDS1.pdf)
-7. [Datasheet, 3DM-GX5-15](/assets/pdf/clearpath_robotics_017772-TDS1.pdf)
-8. [Datasheet, 3DM-GX5-25](/assets/pdf/clearpath_robotics_014603-TDS1.pdf)
-9. [Datasheet, 3DM-GX5-35](/assets/pdf/clearpath_robotics_028528-TDS1.pdf)
-10. [Datasheet, 3DM-GX5-45](/assets/pdf/clearpath_robotics_017391-TDS1.pdf)
-11. [User Manual, 3DM-GX5-10](/assets/pdf/clearpath_robotics_017839-TDS2.pdf)
-12. [User Manual, 3DM-GX5-15](/assets/pdf/clearpath_robotics_017772-TDS2.pdf)
-13. [User Manual, 3DM-GX5-25](/assets/pdf/clearpath_robotics_014603-TDS2.pdf)
-14. [User Manual, 3DM-GX5-35](/assets/pdf/clearpath_robotics_028528-TDS2.pdf)
-15. [User Manual, 3DM-GX5-45](/assets/pdf/clearpath_robotics_017391-TDS2.pdf)
-16. [LORD MicroStrain Website](https://www.microstrain.com/inertial-sensors/g-series)
-17. [ROS webpage](http://wiki.ros.org/microstrain_inertial_driver)
-18. [GitHub](https://github.com/LORD-MicroStrain/microstrain_inertial)
diff --git a/docs/robots/accessories/sensors/imu/redshift_labs_um7.mdx b/docs/robots/accessories/sensors/imu/redshift_labs_um7.mdx
deleted file mode 100644
index 8a2c09d32..000000000
--- a/docs/robots/accessories/sensors/imu/redshift_labs_um7.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Redshift Labs UM7
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/redshift_um7.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :----------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Redshift Labs UM7 sensor | [011914](/assets/pdf/clearpath_robotics_011914-TDS1.pdf) | 028881 | 028880 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :-------------------------------------------------- |
-| Mass | 11 g |
-| Voltage, Minimum | 4 V |
-| Voltage, Maximum | 5.5 V |
-| Voltage, Sensor | 5 V |
-| Power, Average | 0.25 W |
-| Data | UART ( RS-232 ) Default setting is 115200 baud |
-| Ingress Protection, Solids | Unknown ( assume 4 ) |
-| Ingress Protection, Liquids | Unknown ( assume 0 ) |
-| Operating Temperature, Min | -40 °C |
-| Operating Temperature, Max | 85 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/orientation)
-2. [User Manual](/assets/pdf/clearpath_robotics_011914-TDS1.pdf)
-3. [Redshift Labs UM7 Website](https://redshiftlabs.com.au/product/um7-orientation-sensor/)
-4. [ROS webpage](https://github.com/ros-drivers/um7)
diff --git a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx b/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
deleted file mode 100644
index 4e68eea61..000000000
--- a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Hokuyo UST10-LX
-sidebar_position: 1
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/hokuyo_ust.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Hokuyo UST10-LX | [011759](/assets/pdf/clearpath_robotics_011759-TDS1.pdf) | 027207 | 026611 |
-| Hokuyo UST10-LX, 90° vertical mounting | [011759](/assets/pdf/clearpath_robotics_011759-TDS1.pdf) | 026966 | 027224 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 0.13 kg |
-| Voltage, Minimum | 10 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 12 V or 24 V |
-| Power, Average | 3.6 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.06 m |
-| Range, Maximum | 10 m |
-| Range, Accuracy | ± 40 mm |
-| View, Horizontal | 270 ° |
-| Resolution, Horizontal | 0.25 ° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 5 |
-| Operating Temperature, Min | -10 °C |
-| Operating Temperature, Max | 50 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/2dlidar/products/hokuyo-ust-10lx)
-2. [Datasheet](/assets/pdf/clearpath_robotics_011759-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_011759-TDS2.pdf)
-4. [Hokuyo Website](https://www.hokuyo-aut.jp/search/single.php?serial=167#download)
-5. [ROS webpage](http://wiki.ros.org/urg_node)
diff --git a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx b/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
deleted file mode 100644
index 0101ec519..000000000
--- a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Hokuyo UST20-LX
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/hokuyo_ust.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Hokuyo UST20-LX sensor | [016359](/assets/pdf/clearpath_robotics_016359-TDS1.pdf) | 029013 | 029012 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 0.13 kg |
-| Voltage, Minimum | 10 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 12 V or 24 V |
-| Power, Average | 3.6 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.06 m |
-| Range, Maximum | 20 m |
-| Range, Accuracy | ± 40 mm |
-| View, Horizontal | 270 ° |
-| Resolution, Horizontal | 0.25 ° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 5 |
-| Operating Temperature, Min | -10 °C |
-| Operating Temperature, Max | 50 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/2dlidar/products/hokuyo-ust-20lx)
-2. [Datasheet](/assets/pdf/clearpath_robotics_016359-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_016359-TDS2.pdf)
-4. [Hokuyo Website](https://www.hokuyo-aut.jp/search/single.php?serial=167#download)
-5. [ROS webpage](http://wiki.ros.org/urg_node)
diff --git a/docs/robots/accessories/sensors/lidar_2d/sick_lms111.mdx b/docs/robots/accessories/sensors/lidar_2d/sick_lms111.mdx
deleted file mode 100644
index 99488181b..000000000
--- a/docs/robots/accessories/sensors/lidar_2d/sick_lms111.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: SICK LMS-111
-sidebar_position: 4
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/sick_lms1xx.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :----------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| SICK LMS111-10100 sensor | [006387](/assets/pdf/clearpath_robotics_006387-TDS1.pdf) | 027657 | 027656 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :------------------------- | :------------------- |
-| Mass | 1.1 kg |
-| Voltage, Minimum | 10.8 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 24 V |
-| Power, Average | 8 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.5 m |
-| Range, Maximum | 20 m |
-| Range, Accuracy | ±3 cm |
-| View, Horizontal | 270 ° |
-| Resolution, Horizontal | 0.25 ° |
-| Operating Temperature, Min | -30 °C |
-| Operating Temperature, Max | 50 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/2dlidar/products/lms111)
-2. [Datasheet](/assets/pdf/clearpath_robotics_006387-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_006387-TDS2.pdf)
-4. [SICK website](https://www.sick.com/ca/en/detection-and-ranging-solutions/2d-lidar-sensors/lms1xx/lms111-10100/p/p109842)
-5. [ROS webpage](http://wiki.ros.org/LMS1xx)
diff --git a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx b/docs/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
deleted file mode 100644
index 2f271b191..000000000
--- a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Velodyne Puck
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/velodyne_lidar.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------------------------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Velodyne Puck sensor | [011703](/assets/pdf/clearpath_robotics_011703-TDS2.pdf) | — | — |
-| Velodyne Puck sensor, with M12 connector | [020972](/assets/pdf/clearpath_robotics_020972-TDS2.pdf) | 026859 | 027206 |
-| Velodyne Puck sensor, with M12 connector, 90° vertical mounting | [020972](/assets/pdf/clearpath_robotics_020972-TDS2.pdf) | 026965 | 027222 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 830 g |
-| Voltage, Minimum | 9 V |
-| Voltage, Maximum | 18 V |
-| Voltage, Sensor | 12 V |
-| Power, Average | 8 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.9 m |
-| Range, Maximum | 100 m |
-| Range, Accuracy | ±3 cm |
-| View, Horizontal | 360° |
-| View, Vertical | ±15° |
-| Resolution, Horizontal | 0.4° |
-| Resolution, Vertical | 2° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -10 °C |
-| Operating Temperature, Max | 60 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/3d-lidar/products/puck)
-2. [Datasheet](/assets/pdf/clearpath_robotics_011703-TDS2.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_011703-TDS1.pdf)
-4. [Velodyne website](https://store.clearpathrobotics.com/collections/3d-lidar/products/puck)
-5. [ROS webpage](http://wiki.ros.org/velodyne)
-6. [ROS tutorial](http://wiki.ros.org/velodyne/Tutorials/Getting%20Started%20with%20the%20Velodyne%20VLP16)
diff --git a/docs/robots/indoor_robots/boxer/tutorials_boxer.mdx b/docs/robots/indoor_robots/boxer/tutorials_boxer.mdx
deleted file mode 100644
index 8f5c1b2b5..000000000
--- a/docs/robots/indoor_robots/boxer/tutorials_boxer.mdx
+++ /dev/null
@@ -1,288 +0,0 @@
----
-title: Boxer Tutorials
-sidebar_label: Tutorials
-sidebar_position: 3
----
-
-import ComponentIntroductionBoxer from "/components/introduction_boxer.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Boxer Overview
-
-:::caution
-
-This guide is for the Boxer V2.4 (released in November 2021) and V2.5 (released in May 2023). Boxer V2.4 and V2.5 are not compatible with the older Boxer (V2.2).
-Owners of previous-generation (V2.2) Boxers should refer to the documentation [here](http://www.clearpathrobotics.com/assets/guides/kinetic/boxer/).
-
-:::
-
-:::note
-
-OTTO Motors and Clearpath Robotics operate under the same parent company.
-Boxer V2.4 and V2.5 are a collaboration between the teams at OTTO Motors and Clearpath Robotics.
-
-:::
-
-### Introduction
-
-Boxer is a large indoor mobile robot for prototyping and development of industrial applications.
-It is a lightly modified [OTTO 100](https://ottomotors.com/amrs) robot, equipped with a Backpack Computer mounted
-to the top of the Base Unit. This Backpack Computer communicates with the OTTO 100 via its attachment port, located
-on the top of the Base Unit.
-
-The Boxer is currently only supported in [ROS 1](/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/tutorials_boxer.mdx).
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/boxer).
-
-
-
----
-
-## Support {#support}
-
-
diff --git a/docs/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx b/docs/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
deleted file mode 100644
index 379451bff..000000000
--- a/docs/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
+++ /dev/null
@@ -1,328 +0,0 @@
----
-title: Ridgeback User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import ComponentSupport from "/components/support.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-import ComponentSafetyWarning from "/components/safety_warning.mdx";
-
-
-
-## Introduction
-
-Clearpath Robotics Ridgeback is a rugged, indoor omnidirectional platform designed to move manipulators and other heavy
-payloads with ease and precision. This manual contains information about the setup, safe operation, and maintenance of
-your Ridgeback unmanned omnidirectional platform.
-
-
-
-### Shipment Contents
-
-Your Ridgeback shipment contains the following:
-
-- Ridgeback Omnidirectional Robotic Platform, including computer, forward-facing LIDAR, batteries, and integrated
- battery charger
-- One Sony PS4 Bluetooth controller
-- One Ridgeback quick start guide
-
-If you elected to purchase standard payload modules or custom integration services with Ridgeback, then additional
-equipment will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Ridgeback is built around a computer running Ubuntu (Intel-based computer or Jetson developer kit), paired with a 32-bit microcontroller MCU.
-The MCU handles I/O, power supply monitoring, and motor control, as well as supplying data from the integrated IMU.
-The communication channel between the MCU and computer is a Gigabit Ethernet connection.
-
-#### Exterior Features {#ridgeback-exterior-features}
-
-The exterior of Ridgeback is shown below and includes:
-
-- Stop, Reset, and Power buttons
-- Body Lights
-- User Bay
-- Payload Integration Plate
-
-
-
-
- Ridgeback exterior
-
-
-
-#### Buttons
-
-There are four push buttons located on the back of the Ridgeback: the two red mushroom Stop buttons, the
-Stop Reset button below the left rear Stop button, and the Power ON/OFF button below the rear right
-Stop button. On the front of the robot, there are another two red mushroom Stop buttons. These buttons
-are described further in the table below.
-
-| Button | Description |
-| :----------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Power ON/OFF | Turns Ridgeback on or off. Note that the power button is a soft, momentary switch: to shut Ridgeback down, press and release it, and when the Onboard Computer has completed a safe power-down, the robot itself will also power-down. |
-| 4X Stop | Stops Ridgeback by placing the four integrated motor drivers into an electrical reset condition. This is intended as a backup option for immobilizing Ridgeback when autonomy software malfunctions or commands unintended motion. The Stop buttons have a mechanical latch, which can be released by twisting the latched button. If you have a wireless Stop pendant, or other stop-asserting hardware you would like to integrate with Ridgeback, a breakout header is supplied on the main microcontroller PCB. |
-| Stop Reset | Clears the electrically-enforced stop latch, allowing Ridgeback to run again after it has been stopped via one of the Stop buttons. Note that the mushroom button's mechanical latch must be cleared before the electrical reset can have any effect. |
-
-#### Body Lights
-
-Ridgeback includes eight RGB body lights, stacked in a pair on each corner of the chassis. These lights
-express system status according to the table below, but in the absence of one of the low-level conditions, they can
-be commanded from ROS to display indications from autonomy or other higher-level software.
-See http://wiki.ros.org/ridgeback_base for information on commanding the body lights.
-
-| Front Lights | Rear Lights | System State |
-| :------------------ | :--------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| Solid red | Solid red | The MCU is not in contact with the computer. That is, the `rosserial` connection is not active. This condition will be seen briefly on startup while Ridgeback's computer is booting up. If it persists, or is seen after initialization, either the base node on the computer has crashed, the network switch has failed, or a serious MCU error has occurred. If you suspect one of these conditions, please contact support. |
-| Flashing red | Flashing red | Stop mode is engaged. To disengage, twist the mushroom buttons to ensure that they are unlatched, and check any external stop hardware, if present. |
-| Flashing orange | Flashing orange | A system fault has been detected, typically the motor drivers. Refer to logs or diagnostics for details. |
-| Pulsing orange | Pulsing orange | Battery is low. Connect Ridgeback to the charger. |
-| Alternating red/off | Alternating red/orange | All stops are mechanically cleared but still electrically latched. Press the Stop Reset button to enable full operation. |
-| Pulsing green | Pulsing green | Charger is connected, Ridgeback's battery is charging. Note that the battery can also be charged with the platform off. This indication will only be seen if the charger is connected while Ridgeback is powered up. |
-| Solid green | Solid green | Charger is connected and Ridgeback is charged fully. |
-| Solid white | Solid red | Normal operation; ready to drive. The intensity of the lights will increase slightly when actually in motion. This is the status which may be overridden by publishing your own light patterns to the `/cmd_lights` ROS topic. |
-
-#### User Bay
-
-The User Bay provides access to the User Power Panel, as well as USB and Ethernet ports, and additional
-space for stowing user equipment. The electrical panel can be used to power your payloads, with further details available
-in [Electrical Integration](integration_ridgeback.mdx#ridgeback-payload-electrical-integration).
-The USB3 ports are connected directly to the Onboard Computer, and the Ethernet ports connect to the onboard network switch. To
-connect a device to the onboard network, it is suggested to give it a static IP in the 192.168.131.x/24 subnet and
-this cannot be changed since the MCU is statically set to 192.168.131.2 and expects the computer to be at
-192.168.131.1. Avoid IPs in use by the following pre-existing devices:
-
-| IP Address | Device Assignment |
-| :------------- | :--------------------------------------------------- |
-| 192.168.131.1 | Onboard Computer (both ports, br0 network interface) |
-| 192.168.131.2 | Ethernet-connected MCU |
-| 192.168.131.20 | Front-facing LIDAR |
-| 192.168.131.21 | Rear-facing LIDAR (if present) |
-
-See [Standard IP Addresses](../../../ros/networking/standard_ip_addresses.mdx) for a full list of common IP addresses.
-
-#### Payload Integration Plate
-
-The Payload Integration Plate provides a robust foundation for mounting payload structures such as
-UR5/UR10 manipulation arms or any other combination of sensors and manipulators. For more information
-and guidance on mounting payload structures on top of Ridgeback, please refer to
-[Mechanical Integration](integration_ridgeback.mdx#ridgeback-payload-mechanical-integration).
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855.
-
-When commanded with a positive translational velocity (forward), wheels travel in the positive x-direction.
-The direction of the axes differs from those used for roll, pitch, and yaw in aircraft, and care should be taken to ensure that data is interpreted correctly.
-
-
-
-### System Specifications
-
-| Specification | Measurement |
-| :-------------------- | :--------------------------------------------------------------------------- |
-| Dimension, Length | 960 mm |
-| Dimension, Width | 793 mm |
-| Dimension, Height | 311 mm † |
-| Ground Clearance | 18 mm |
-| Maximum Payload | 100 kg |
-| Speed, Maximum | 1.1 m/s |
-| Operating Environment | Indoor |
-| Operating Time | 15 hours with max payload (24 V 100 Ah) |
-| Battery Chemistry | Marine Grade AGM Sealed Lead Acid |
-| Charge Time | 8 hours |
-| User Power | 20 A @ VBAT (24 V), 5 A @ 12 V, 5 A @ 5 V |
-| Power | 800 W Typical Use, Shore Power Available |
-| Control Modes | Kinematic control (forward, sideways, rotation), individual wheel velocities |
-| Communication | Ethernet, USB 3.0, RS232 |
-| Internal Sensing | Battery Status, Wheel Odometry, Motor Currents, Onboard IMU |
-
-† The height of the Ridgeback was increased by 15 mm starting with the robot with serial number R100-0111. Older Ridgebacks measure 296 mm high.
-
-
-
-
-
----
-
-## Getting Started
-
-You are ready to go! This section details how to get Ridgeback into action.
-If you are just opening up the shipping crate, you can unfold the ramp, and remove the ratchet straps which
-secure Ridgeback during shipping.
-
-To begin, place Ridgeback "up on blocks" as described in the [Safety](#safety) section, making sure that the wheels
-are clear of the ground.
-
-### Onboard Computer Setup
-
-A standard Ridgeback ships with an integrated Onboard Computer that is directly connected to the Ridgeback MCU. Most users
-will also make use of an Offboard Computer, which is used to control Ridgeback and gather data.
-These two computers must be set up to communicate with each other. Details on the Offboard Computer setup
-can be found in [Ridgeback Tutorials](tutorials_ridgeback.mdx).
-
-### Powering Up
-
-Press the power button on the back of Ridgeback. Once the body lights are flashing red, clear the all Stop
-buttons (if necessary), and press the blinking red Stop Reset button. In a moment, the platform should go to
-solid red lights in back, and solid white in front.
-
-### Network Configuration
-
-To get Ridgeback connected to your local Wi-Fi network, you must first access the Onboard Computer using a wired connection to the robot.
-Open the User Bay, then connect to one of the network ports with a standard Ethernet cable.
-Then, see [Ridgeback Tutorials](tutorials_ridgeback.mdx) for details
-on completing the networking setup.
-
-### Connecting and Using the Controller {#controller}
-
-To use your controller, it must be paired with your Ridgeback and powered on.
-For a standard Ridgeback with the Onboard Computer from Clearpath Robotics, the controller is already paired with your Ridgeback.
-If your controller has become unpaired or if you wish to pair a new controller, following the instructions in the
-[Ridgeback Tutorials](tutorials_ridgeback.mdx).
-
-To teleoperate Ridgeback, first clear the motion-stop.
-Then, power on the controller by pressing the `PS` button on the controller.
-Once the blue LED on the top of the controller goes solid, you are paired and ready to drive.
-
-Hold the L1 trigger button (deadman switch) and push the left thumbstick forward to drive the Ridgeback.
-See the figure below for the Sony PS4 controls layout.
-If you are not seeing any action, refer to [Support](#ridgeback-support) to get in touch with support.
-
-
-
-
- PS4 Controls Layout
-
-
-
-### Using ROS
-
-
-
-### Battery Charging
-
-Ridgeback uses two 8A31DTM Group-31 lead-acid (PbSO4) deep-cycle AGM batteries mounted low in the
-chassis. They provide an output of 24 VDC (nominal) and 100 Ah of capacity.
-
-When finished with the Ridgeback, press and release the power button to power it off.
-
-Ridgeback has an internal charger. All that is required to charge Ridgeback is to open the User Bay access
-panel, locate the charger power cord and plug it into any 85-270 VAC 50/60Hz mains outlet. The robot can be
-turned "on", though we recommend against driving the robot when the battery is charging.
-
-The battery pack is rugged and designed for the environments into which Ridgeback may be deployed.
-However, please take note of the following:
-
-- The batteries and robot must not be stored or operated above 50 ◦C or below -20 ◦C.
-- If the robot is to be stored for any length of time it should be in a cool, dry location. The batteries should
- be fully charged and periodically maintained at full charge to ensure a long service life. Ridgeback
- should not be stored with a low state of charge nor for extended periods of time without top-up charging.
- The batteries may suffer from "sulfation" which reduces their capacity and lifetime.
-- Do not allow the batteries to reach a depth of discharge of 80%.
-- The batteries must not be punctured or disassembled.
-- The batteries should be disposed of pursuant to your local regulations regarding electrical and/or hazardous waste.
-
-The integrated Ridgeback charger will fully charge the internal lead-acid battery in a few hours. The charger will time out after 12 hours, so be sure to power cycle (by unplugging and re-plugging) the charger on a daily basis. Allow the battery to warm up to at least 10°C before charging.
-
-When the battery is running low on charge, the corner lights will start to flash yellow. This is your indication that the Ridgeback should be plugged in to charge soon.
-
-Please contact Clearpath Robotics for additional information about Ridgeback's batteries or for information about
-purchasing additional batteries.
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-Ridgeback contains several features to protect the safety of users and the integrity of the robot.
-
-:::caution
-
-Ridgeback is a powerful, heavy, fast moving robotic platform. Please read the following notices carefully.
-
-:::
-
-### General Warnings
-
-Ridgeback is a rugged and high-performance vehicle.
-For the safety of yourself and others, always conduct initial experiments and software development with the vehicle raised off the ground.
-Place a wooden crate, a set of sawhorses, a sturdy storage tub, or any other solid flat structure having a height greater than 150 mm (6 inches)
-under Ridgeback to keep the wheels clear of the ground ("up on blocks").
-
-When starting out, favour slower wheel speeds.
-Ridgeback's control loops can accurately maintain velocities as low as 0.1 m/s.
-Operating at such speeds will give you more time to react if things don't go quite as you expect.
-
-### Stop Buttons {#ridgeback-stop-buttons}
-
-Ridgeback has four red Stop buttons, two on the front and two on the back. To engage Stop Mode, press
-any of the four Stop buttons once; you should see that all four corner LEDs are flashing red.
-To disengage Stop Mode, pull any engaged Stop buttons to release them, then press the Stop Reset button
-located below the rear-left Stop button; all corner LEDs should return to their original values.
-
-When in Stop mode the Ridgeback will not drive. The commands received during stop are not buffered;
-Ridgeback will always act on the latest commands received. This means that if motion commands are discontinued
-before the Stop button is released, the Ridgeback will not move. If the commands are continued,
-Ridgeback will move at the speed commanded once the Stop is released.
-
-Always ensure the Stop buttons are accessible at all times. Avoid mounting payloads that extend over the
-front or rear of Ridgeback and would occlude the Stop buttons.
-
-Note that the Ridgeback MCU board includes a breakout to allow an external motion-stop button/switch to be
-integrated by the end user, which could be used to engage/disengage Stop Mode.
-See [Optional External Motion Stop](integration_ridgeback.mdx#ridgeback-external-motion-stop)
-for details on adding an external motion-stop button/switch.
-
-### Electrical System
-
-Ridgeback is powered by two lead-acid (PbSO4) deep-cycle AGM batteries that are capable of delivering over 2000 W
-for short durations. This gives Ridgeback's motors their great performance; however, it is also enough power to
-cause severe bodily harm. Always use caution when operating Ridgeback to avoid personal injury or property damage.
-To ensure safety, please observe the following precautions:
-
-- Do not tamper with the battery terminals or wiring.
-- Do not tamper with the fuse panel, except to check and change the fuses, and to connect and disconnect the battery plug.
-- Always replace fuses with the same type and rating to ensure continued protection against risk of fires.
-- Consult Clearpath Robotics Support if you need to service the batteries.
-- Do not lay tools or other objects on top of the batteries.
-- Do not move the robot while charging the batteries.
-- Charge the battery only with the integrated charger installed by Clearpath Robotics.
-- Please dispose of the batteries properly or return them to Clearpath Robotics to do so.
-
-### Lifting and Transport
-
-- Ensure that Ridgeback's Stop Mode is engaged when transporting short distances and powered off when transporting longer distances.
-- Do not push the robot at more than 0.5 m/s (1.6 ft/s) or damage to the motor controls may occur.
-
-### Performance Considerations
-
-Included in Ridgeback are native software checks and limits to protect the robot.
-However, it is recommended to monitor the system's status during usage with the `/status` and `/diagnostics` topics.
-These topics provide useful information regarding voltages, currents, temperatures and general health of the system.
-
-### Recommended Safe Work Procedures
-
-
-
----
-
-## Support {#ridgeback-support}
-
-
diff --git a/docs/robots/legacy/pr2.mdx b/docs/robots/legacy/pr2.mdx
deleted file mode 100644
index bb9636ba1..000000000
--- a/docs/robots/legacy/pr2.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: PR2
-sidebar_label: PR2
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-This page provides links to the design files for the PR2 robot, designed by Willow Garage.
-
-- [PR2 Cable Drawings (27 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_cable_drawings.zip)
-- [PR2 Electrical Manufacturing Files (113 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_electrical_mfg_files.zip)
-- [PR2 Schematics (34 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_schematics.zip)
-- [PR2 CAD Files (11220 MB -- large!)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_cad_files.zip)
diff --git a/docs/robots/outdoor_robots/jackal/tutorials_jackal.mdx b/docs/robots/outdoor_robots/jackal/tutorials_jackal.mdx
deleted file mode 100644
index f09679c62..000000000
--- a/docs/robots/outdoor_robots/jackal/tutorials_jackal.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Jackal Tutorials
-sidebar_label: Tutorials
-sidebar_position: 3
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Jackal Overview
-
-### Introduction
-
-Jackal is a rugged, lightweight, fast and easy-to-use unmanned ground robot for rapid prototyping
-and research applications. These tutorials will assist you with setting up and operating your Jackal.
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/jackal).
-
-
-
-## Jetson Installation
-
-Refer to the [Jetson](../../accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx) page for details on installing a Jetson in Jackal.
-However, at present, ROS 2 software is not supported on Jetson in Jackal.
-
----
-
-## Support {#support}
-
-
diff --git a/docs/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx b/docs/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
deleted file mode 100644
index 7a04f0c89..000000000
--- a/docs/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Warthog Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 6
----
-
-import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-## If the Issue Persists
-
-
diff --git a/docs_outdoornav_user_manual/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/docs_outdoornav_user_manual/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index de411daf7..ec9073447 100644
--- a/docs_outdoornav_user_manual/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/docs_outdoornav_user_manual/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/docs/robots/accessories/_category_.json b/docs_robots/accessories/_category_.json
similarity index 100%
rename from docs/robots/accessories/_category_.json
rename to docs_robots/accessories/_category_.json
diff --git a/docs/robots/accessories/accessories.mdx b/docs_robots/accessories/accessories.mdx
similarity index 100%
rename from docs/robots/accessories/accessories.mdx
rename to docs_robots/accessories/accessories.mdx
diff --git a/docs/robots/accessories/add-ons/_category_.json b/docs_robots/accessories/add-ons/_category_.json
similarity index 100%
rename from docs/robots/accessories/add-ons/_category_.json
rename to docs_robots/accessories/add-ons/_category_.json
diff --git a/docs/robots/accessories/add-ons/add-ons.mdx b/docs_robots/accessories/add-ons/add-ons.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/add-ons.mdx
rename to docs_robots/accessories/add-ons/add-ons.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/base_station.mdx b/docs_robots/accessories/add-ons/base_station.mdx
similarity index 90%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/base_station.mdx
rename to docs_robots/accessories/add-ons/base_station.mdx
index 704525ce0..175d621d0 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/base_station.mdx
+++ b/docs_robots/accessories/add-ons/base_station.mdx
@@ -37,6 +37,6 @@ Clearpath uses this RTK correction in its OutdoorNav autonomy software, but we d
:::note
-Refer to the [Network IP Addresses page](../../../ros/networking/network_ip_addresses.mdx) for the commonly used device IP addresses.
+Refer to the [Standard IP Addresses page](/docs/ros/networking/standard_ip_addresses) for the commonly used device IP addresses.
:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/controllers.mdx b/docs_robots/accessories/add-ons/controllers.mdx
similarity index 98%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/controllers.mdx
rename to docs_robots/accessories/add-ons/controllers.mdx
index 266c61c35..b7866e5e2 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/controllers.mdx
+++ b/docs_robots/accessories/add-ons/controllers.mdx
@@ -23,7 +23,7 @@ You may need to install _jstest_ with `sudo apt-get install jstest-gtk`
Clearpath uses the _/bluetooth_teleop_ ROS node to publish velocity commands from the joystick to _/twist_mux_.
_/twist_mux_ Takes in multiple sources of velocity commands, and prioritizes what actually gets sent to _/cmd_vel_ to drive the robot.
-Depending on the robot platform and related controller, you will need to configure your robot's [robot.yaml configuration file](../../../ros/config/yaml/platform/controller.mdx).
+Depending on the robot platform and related controller, you will need to configure your robot's [robot.yaml configuration file](/docs/ros/config/yaml/platform/controller).
---
diff --git a/docs/robots/accessories/add-ons/din_rail.mdx b/docs_robots/accessories/add-ons/din_rail.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/din_rail.mdx
rename to docs_robots/accessories/add-ons/din_rail.mdx
diff --git a/docs/robots/accessories/add-ons/network_access_point.mdx b/docs_robots/accessories/add-ons/network_access_point.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/network_access_point.mdx
rename to docs_robots/accessories/add-ons/network_access_point.mdx
diff --git a/docs/robots/accessories/add-ons/network_switch.mdx b/docs_robots/accessories/add-ons/network_switch.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/network_switch.mdx
rename to docs_robots/accessories/add-ons/network_switch.mdx
diff --git a/docs/robots/accessories/add-ons/outdoornav_starter_kit.mdx b/docs_robots/accessories/add-ons/outdoornav_starter_kit.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/outdoornav_starter_kit.mdx
rename to docs_robots/accessories/add-ons/outdoornav_starter_kit.mdx
diff --git a/docs/robots/accessories/add-ons/power_supplies.mdx b/docs_robots/accessories/add-ons/power_supplies.mdx
similarity index 97%
rename from docs/robots/accessories/add-ons/power_supplies.mdx
rename to docs_robots/accessories/add-ons/power_supplies.mdx
index fc81ec6c8..138479bd6 100644
--- a/docs/robots/accessories/add-ons/power_supplies.mdx
+++ b/docs_robots/accessories/add-ons/power_supplies.mdx
@@ -46,7 +46,7 @@ This is our process for choosing a new enclosed power supply.
:::
-9. Review the electrical termination method to see if it is ideal for your application. It is common to see screw terminals for [Ring Terminals](../../common/components/connectors/ring_terminal.mdx), though there are other options.
+9. Review the electrical termination method to see if it is ideal for your application. It is common to see screw terminals for [Ring Terminals](../../common/parts/connectors/ring_terminal.mdx), though there are other options.
diff --git a/docs/robots/accessories/add-ons/relay_board.mdx b/docs_robots/accessories/add-ons/relay_board.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/relay_board.mdx
rename to docs_robots/accessories/add-ons/relay_board.mdx
diff --git a/docs/robots/accessories/add-ons/stack_light.mdx b/docs_robots/accessories/add-ons/stack_light.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/stack_light.mdx
rename to docs_robots/accessories/add-ons/stack_light.mdx
diff --git a/docs/robots/accessories/add-ons/tower.mdx b/docs_robots/accessories/add-ons/tower.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/tower.mdx
rename to docs_robots/accessories/add-ons/tower.mdx
diff --git a/docs/robots/accessories/add-ons/usb_hub.mdx b/docs_robots/accessories/add-ons/usb_hub.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/usb_hub.mdx
rename to docs_robots/accessories/add-ons/usb_hub.mdx
diff --git a/docs/robots/accessories/add-ons/wireless_stop_system.mdx b/docs_robots/accessories/add-ons/wireless_stop_system.mdx
similarity index 100%
rename from docs/robots/accessories/add-ons/wireless_stop_system.mdx
rename to docs_robots/accessories/add-ons/wireless_stop_system.mdx
diff --git a/docs/robots/accessories/computers/_category_.json b/docs_robots/accessories/computers/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/_category_.json
rename to docs_robots/accessories/computers/_category_.json
diff --git a/docs/robots/accessories/computers/computers.mdx b/docs_robots/accessories/computers/computers.mdx
similarity index 100%
rename from docs/robots/accessories/computers/computers.mdx
rename to docs_robots/accessories/computers/computers.mdx
diff --git a/docs/robots/accessories/computers/jetson/_category_.json b/docs_robots/accessories/computers/jetson/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/jetson/_category_.json
rename to docs_robots/accessories/computers/jetson/_category_.json
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/_category_.json b/docs_robots/accessories/computers/jetson/jetson_hardware/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/_category_.json
rename to docs_robots/accessories/computers/jetson/jetson_hardware/_category_.json
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx b/docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
similarity index 100%
rename from docs/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
rename to docs_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
diff --git a/docs/robots/accessories/computers/jetson/jetson_software.mdx b/docs_robots/accessories/computers/jetson/jetson_software.mdx
similarity index 98%
rename from docs/robots/accessories/computers/jetson/jetson_software.mdx
rename to docs_robots/accessories/computers/jetson/jetson_software.mdx
index 5b6a8648d..7c7bafc91 100644
--- a/docs/robots/accessories/computers/jetson/jetson_software.mdx
+++ b/docs_robots/accessories/computers/jetson/jetson_software.mdx
@@ -388,7 +388,7 @@ This step is optional.
:::
-See instructions [here](../../../../ros/installation/controller.mdx#ps4-controller) for how to pair the PS4 controller.
+See instructions [here](/docs/ros/installation/controller#ps4-controller) for how to pair the PS4 controller.
### Step 7: Use Offboard Computer with Jetson (Optional)
diff --git a/docs/robots/accessories/computers/mini_itx.mdx b/docs_robots/accessories/computers/mini_itx.mdx
similarity index 98%
rename from docs/robots/accessories/computers/mini_itx.mdx
rename to docs_robots/accessories/computers/mini_itx.mdx
index 74a782dde..2987f3376 100644
--- a/docs/robots/accessories/computers/mini_itx.mdx
+++ b/docs_robots/accessories/computers/mini_itx.mdx
@@ -11,7 +11,7 @@ Mini ITX computers are the default computer option for many Clearpath robots.
:::note
To install and configure software on your Mini ITX computer, see
-[Robot Installation](../../../ros/installation/robot.mdx).
+[Robot Installation](/docs/ros/installation/robot).
:::
diff --git a/docs/robots/accessories/manipulators/_category_.json b/docs_robots/accessories/manipulators/_category_.json
similarity index 100%
rename from docs/robots/accessories/manipulators/_category_.json
rename to docs_robots/accessories/manipulators/_category_.json
diff --git a/docs/robots/accessories/manipulators/flir_ptu_e46.mdx b/docs_robots/accessories/manipulators/flir_ptu_e46.mdx
similarity index 100%
rename from docs/robots/accessories/manipulators/flir_ptu_e46.mdx
rename to docs_robots/accessories/manipulators/flir_ptu_e46.mdx
diff --git a/docs/robots/accessories/manipulators/kinova_gen3_lite.mdx b/docs_robots/accessories/manipulators/kinova_gen3_lite.mdx
similarity index 99%
rename from docs/robots/accessories/manipulators/kinova_gen3_lite.mdx
rename to docs_robots/accessories/manipulators/kinova_gen3_lite.mdx
index 467033bbd..896d0e612 100644
--- a/docs/robots/accessories/manipulators/kinova_gen3_lite.mdx
+++ b/docs_robots/accessories/manipulators/kinova_gen3_lite.mdx
@@ -89,7 +89,7 @@ The PACS™ kit for this sensor includes:
### ROS 2 Configuration
This manipulator is included in the Clearpath Robotics descriptino and robot package that is installed on all of our robots.
-This allows you to add or remove manipulator from your robot's software configuration by modying the [robot configuration yaml](../../../ros/config/yaml/manipulators.mdx).
+This allows you to add or remove manipulator from your robot's software configuration by modying the [robot configuration yaml](/docs/ros/config/yaml/manipulators).
diff --git a/docs/robots/accessories/manipulators/manipulators.mdx b/docs_robots/accessories/manipulators/manipulators.mdx
similarity index 100%
rename from docs/robots/accessories/manipulators/manipulators.mdx
rename to docs_robots/accessories/manipulators/manipulators.mdx
diff --git a/docs/robots/accessories/pacs.mdx b/docs_robots/accessories/pacs.mdx
similarity index 98%
rename from docs/robots/accessories/pacs.mdx
rename to docs_robots/accessories/pacs.mdx
index c443421b1..68c518269 100644
--- a/docs/robots/accessories/pacs.mdx
+++ b/docs_robots/accessories/pacs.mdx
@@ -70,7 +70,7 @@ Refer to the integration pages for our robots for more details:
| Plate—80 X 80, Attachment Interface, Large | [027110](/assets/pdf/clearpath_robotics_027110.pdf) |
| Plate—80 X 80, Attachment Interface, Manipulator (UR3 and UR5) | [027269](/assets/pdf/clearpath_robotics_027269.pdf) |
| Plate—80 X 80, Attachment Interface | [028866](/assets/pdf/clearpath_robotics_028866.pdf) |
-| Screw, Round Head, M5×0.8 | [Many](../common/components/fasteners/screw_round_head.mdx) |
+| Screw, Round Head, M5×0.8 | [Many](../common/parts/fasteners/screw_round_head.mdx) |
## Sensor and Attachment Kits
@@ -121,7 +121,7 @@ Refer to the integration pages for our robots for more details:
| | [Network Switch, 8 Port](add-ons/network_switch.mdx) | 025333 | 027641 | 027640 |
| | [Network Switch, 16 Port](add-ons/network_switch.mdx) | 029098 | - | - |
| | [USB Hub, 7 Port](add-ons/usb_hub.mdx) | 025440 | 027643 | 027642 |
-| **OutdoorNav HW** | [OutdoorNav Starter Kit](../../robots/accessories/add-ons/outdoornav_starter_kit.mdx) | - | 028356 | - |
+| **OutdoorNav HW** | [OutdoorNav Starter Kit](add-ons/outdoornav_starter_kit.mdx) | - | 028356 | - |
| **Power Supply** | [Power Supply, SB-15](add-ons/power_supplies.mdx) | - | 028902 | 028901 |
| | [Power Supply, SB-25](add-ons/power_supplies.mdx) | - | 028904 | 028903 |
| | [Power Supply, TEP 150](add-ons/power_supplies.mdx) | - | 028942 | 028941 |
diff --git a/docs/robots/accessories/sensors/_category_.json b/docs_robots/accessories/sensors/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/_category_.json
rename to docs_robots/accessories/sensors/_category_.json
diff --git a/docs/robots/accessories/sensors/cameras/_category_.json b/docs_robots/accessories/sensors/cameras/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/_category_.json
rename to docs_robots/accessories/sensors/cameras/_category_.json
diff --git a/docs/robots/accessories/sensors/cameras/axis_f1035_e.mdx b/docs_robots/accessories/sensors/cameras/axis_f1035_e.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/axis_f1035_e.mdx
rename to docs_robots/accessories/sensors/cameras/axis_f1035_e.mdx
diff --git a/docs/robots/accessories/sensors/cameras/axis_m5525_e.mdx b/docs_robots/accessories/sensors/cameras/axis_m5525_e.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/axis_m5525_e.mdx
rename to docs_robots/accessories/sensors/cameras/axis_m5525_e.mdx
diff --git a/docs/robots/accessories/sensors/cameras/axis_q6225_le.mdx b/docs_robots/accessories/sensors/cameras/axis_q6225_le.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/axis_q6225_le.mdx
rename to docs_robots/accessories/sensors/cameras/axis_q6225_le.mdx
diff --git a/docs/robots/accessories/sensors/cameras/flir_blackfly_s.mdx b/docs_robots/accessories/sensors/cameras/flir_blackfly_s.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/cameras/flir_blackfly_s.mdx
rename to docs_robots/accessories/sensors/cameras/flir_blackfly_s.mdx
index 5dce22601..70eb77883 100644
--- a/docs/robots/accessories/sensors/cameras/flir_blackfly_s.mdx
+++ b/docs_robots/accessories/sensors/cameras/flir_blackfly_s.mdx
@@ -41,7 +41,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
This allows you to add or remove the sensor from your robot's software description by modifying the
-[robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+[robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/cameras/flir_ladybug5p.mdx b/docs_robots/accessories/sensors/cameras/flir_ladybug5p.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/flir_ladybug5p.mdx
rename to docs_robots/accessories/sensors/cameras/flir_ladybug5p.mdx
diff --git a/docs/robots/accessories/sensors/cameras/luxonis_oakd.mdx b/docs_robots/accessories/sensors/cameras/luxonis_oakd.mdx
similarity index 92%
rename from docs/robots/accessories/sensors/cameras/luxonis_oakd.mdx
rename to docs_robots/accessories/sensors/cameras/luxonis_oakd.mdx
index 69b75aba1..f09ebf706 100644
--- a/docs/robots/accessories/sensors/cameras/luxonis_oakd.mdx
+++ b/docs_robots/accessories/sensors/cameras/luxonis_oakd.mdx
@@ -25,7 +25,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/cameras/occam_omni_60.mdx b/docs_robots/accessories/sensors/cameras/occam_omni_60.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/cameras/occam_omni_60.mdx
rename to docs_robots/accessories/sensors/cameras/occam_omni_60.mdx
diff --git a/docs/robots/accessories/sensors/cameras/realsense_d435.mdx b/docs_robots/accessories/sensors/cameras/realsense_d435.mdx
similarity index 95%
rename from docs/robots/accessories/sensors/cameras/realsense_d435.mdx
rename to docs_robots/accessories/sensors/cameras/realsense_d435.mdx
index d5774744e..572b26ed1 100644
--- a/docs/robots/accessories/sensors/cameras/realsense_d435.mdx
+++ b/docs_robots/accessories/sensors/cameras/realsense_d435.mdx
@@ -44,7 +44,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx b/docs_robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
rename to docs_robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
index 71ddcb862..4de8931cd 100644
--- a/docs/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
+++ b/docs_robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
@@ -46,7 +46,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/gps/_category_.json b/docs_robots/accessories/sensors/gps/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/gps/_category_.json
rename to docs_robots/accessories/sensors/gps/_category_.json
diff --git a/docs/robots/accessories/sensors/gps/garmin_gps_18x.mdx b/docs_robots/accessories/sensors/gps/garmin_gps_18x.mdx
similarity index 97%
rename from docs/robots/accessories/sensors/gps/garmin_gps_18x.mdx
rename to docs_robots/accessories/sensors/gps/garmin_gps_18x.mdx
index 8df082fc1..ac0d9553f 100644
--- a/docs/robots/accessories/sensors/gps/garmin_gps_18x.mdx
+++ b/docs_robots/accessories/sensors/gps/garmin_gps_18x.mdx
@@ -43,7 +43,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/gps/microstrain_gq7.mdx b/docs_robots/accessories/sensors/gps/microstrain_gq7.mdx
similarity index 98%
rename from docs/robots/accessories/sensors/gps/microstrain_gq7.mdx
rename to docs_robots/accessories/sensors/gps/microstrain_gq7.mdx
index 85207dd6b..1dba89997 100644
--- a/docs/robots/accessories/sensors/gps/microstrain_gq7.mdx
+++ b/docs_robots/accessories/sensors/gps/microstrain_gq7.mdx
@@ -43,7 +43,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/gps/swift_navigation_duro.mdx b/docs_robots/accessories/sensors/gps/swift_navigation_duro.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/gps/swift_navigation_duro.mdx
rename to docs_robots/accessories/sensors/gps/swift_navigation_duro.mdx
index 8577634af..efc0269a8 100644
--- a/docs/robots/accessories/sensors/gps/swift_navigation_duro.mdx
+++ b/docs_robots/accessories/sensors/gps/swift_navigation_duro.mdx
@@ -44,7 +44,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/imu/_category_.json b/docs_robots/accessories/sensors/imu/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/imu/_category_.json
rename to docs_robots/accessories/sensors/imu/_category_.json
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx b/docs_robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
similarity index 97%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
rename to docs_robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
index 419a38903..38394f306 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
+++ b/docs_robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
@@ -43,7 +43,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/redshift_labs_um7.mdx b/docs_robots/accessories/sensors/imu/redshift_labs_um7.mdx
similarity index 95%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/redshift_labs_um7.mdx
rename to docs_robots/accessories/sensors/imu/redshift_labs_um7.mdx
index 8a2c09d32..90fbe0862 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/redshift_labs_um7.mdx
+++ b/docs_robots/accessories/sensors/imu/redshift_labs_um7.mdx
@@ -40,7 +40,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/lidar_2d/_category_.json b/docs_robots/accessories/sensors/lidar_2d/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/lidar_2d/_category_.json
rename to docs_robots/accessories/sensors/lidar_2d/_category_.json
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
similarity index 95%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
rename to docs_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
index 4e68eea61..69c3039a6 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
+++ b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
@@ -46,7 +46,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
similarity index 95%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
rename to docs_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
index 0101ec519..2f72e6468 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
+++ b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
@@ -45,7 +45,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
similarity index 95%
rename from docs/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
rename to docs_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
index 19326cc91..f89f23086 100644
--- a/docs/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
+++ b/docs_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
@@ -43,7 +43,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/sick_lms111.mdx b/docs_robots/accessories/sensors/lidar_2d/sick_lms111.mdx
similarity index 95%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/sick_lms111.mdx
rename to docs_robots/accessories/sensors/lidar_2d/sick_lms111.mdx
index 99488181b..8fbe92b5f 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/sick_lms111.mdx
+++ b/docs_robots/accessories/sensors/lidar_2d/sick_lms111.mdx
@@ -43,7 +43,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/lidar_3d/_category_.json b/docs_robots/accessories/sensors/lidar_3d/_category_.json
similarity index 100%
rename from docs/robots/accessories/sensors/lidar_3d/_category_.json
rename to docs_robots/accessories/sensors/lidar_3d/_category_.json
diff --git a/docs/robots/accessories/sensors/lidar_3d/ouster.mdx b/docs_robots/accessories/sensors/lidar_3d/ouster.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/lidar_3d/ouster.mdx
rename to docs_robots/accessories/sensors/lidar_3d/ouster.mdx
diff --git a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
rename to docs_robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
index f0f02177e..6493a1011 100644
--- a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
+++ b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
@@ -48,7 +48,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
similarity index 96%
rename from docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
rename to docs_robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
index 2f271b191..a2f9958e7 100644
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
+++ b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
@@ -49,7 +49,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
rename to docs_robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
index fe70bfab3..cb9586171 100644
--- a/docs/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
+++ b/docs_robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
@@ -46,7 +46,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx b/docs_robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
similarity index 96%
rename from docs/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
rename to docs_robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
index 99f2a5978..15f7d06d6 100644
--- a/docs/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
+++ b/docs_robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
@@ -48,7 +48,7 @@ import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensor
## Software Bringup
This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
+This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](/docs/ros/config/yaml/sensors/overview).
diff --git a/docs/robots/accessories/sensors/sensors.mdx b/docs_robots/accessories/sensors/sensors.mdx
similarity index 100%
rename from docs/robots/accessories/sensors/sensors.mdx
rename to docs_robots/accessories/sensors/sensors.mdx
diff --git a/docs/robots/common/_category_.json b/docs_robots/common/_category_.json
similarity index 100%
rename from docs/robots/common/_category_.json
rename to docs_robots/common/_category_.json
diff --git a/docs/robots/common/colours.mdx b/docs_robots/common/colours.mdx
similarity index 100%
rename from docs/robots/common/colours.mdx
rename to docs_robots/common/colours.mdx
diff --git a/docs/robots/common/components/_category_.json b/docs_robots/common/parts/_category_.json
similarity index 100%
rename from docs/robots/common/components/_category_.json
rename to docs_robots/common/parts/_category_.json
diff --git a/docs/robots/common/components/connectors/_category_.json b/docs_robots/common/parts/connectors/_category_.json
similarity index 100%
rename from docs/robots/common/components/connectors/_category_.json
rename to docs_robots/common/parts/connectors/_category_.json
diff --git a/docs/robots/common/components/connectors/anderson_powerpole_15.mdx b/docs_robots/common/parts/connectors/anderson_powerpole_15.mdx
similarity index 100%
rename from docs/robots/common/components/connectors/anderson_powerpole_15.mdx
rename to docs_robots/common/parts/connectors/anderson_powerpole_15.mdx
diff --git a/docs/robots/common/components/connectors/anderson_sb_50.mdx b/docs_robots/common/parts/connectors/anderson_sb_50.mdx
similarity index 100%
rename from docs/robots/common/components/connectors/anderson_sb_50.mdx
rename to docs_robots/common/parts/connectors/anderson_sb_50.mdx
diff --git a/docs/robots/common/components/connectors/molex_mini_fit_jr.mdx b/docs_robots/common/parts/connectors/molex_mini_fit_jr.mdx
similarity index 100%
rename from docs/robots/common/components/connectors/molex_mini_fit_jr.mdx
rename to docs_robots/common/parts/connectors/molex_mini_fit_jr.mdx
diff --git a/docs/robots/common/components/connectors/ring_terminal.mdx b/docs_robots/common/parts/connectors/ring_terminal.mdx
similarity index 100%
rename from docs/robots/common/components/connectors/ring_terminal.mdx
rename to docs_robots/common/parts/connectors/ring_terminal.mdx
diff --git a/docs/robots/common/components/fasteners/_category_.json b/docs_robots/common/parts/fasteners/_category_.json
similarity index 100%
rename from docs/robots/common/components/fasteners/_category_.json
rename to docs_robots/common/parts/fasteners/_category_.json
diff --git a/docs/robots/common/components/fasteners/nut.mdx b/docs_robots/common/parts/fasteners/nut.mdx
similarity index 100%
rename from docs/robots/common/components/fasteners/nut.mdx
rename to docs_robots/common/parts/fasteners/nut.mdx
diff --git a/docs/robots/common/components/fasteners/screw_flat_head.mdx b/docs_robots/common/parts/fasteners/screw_flat_head.mdx
similarity index 100%
rename from docs/robots/common/components/fasteners/screw_flat_head.mdx
rename to docs_robots/common/parts/fasteners/screw_flat_head.mdx
diff --git a/docs/robots/common/components/fasteners/screw_round_head.mdx b/docs_robots/common/parts/fasteners/screw_round_head.mdx
similarity index 100%
rename from docs/robots/common/components/fasteners/screw_round_head.mdx
rename to docs_robots/common/parts/fasteners/screw_round_head.mdx
diff --git a/docs/robots/common/components/fasteners/screw_socket_head.mdx b/docs_robots/common/parts/fasteners/screw_socket_head.mdx
similarity index 100%
rename from docs/robots/common/components/fasteners/screw_socket_head.mdx
rename to docs_robots/common/parts/fasteners/screw_socket_head.mdx
diff --git a/docs/robots/common/components/components.mdx b/docs_robots/common/parts/parts.mdx
similarity index 100%
rename from docs/robots/common/components/components.mdx
rename to docs_robots/common/parts/parts.mdx
diff --git a/docs/robots/common/components/terminal_blocks.mdx b/docs_robots/common/parts/terminal_blocks.mdx
similarity index 100%
rename from docs/robots/common/components/terminal_blocks.mdx
rename to docs_robots/common/parts/terminal_blocks.mdx
diff --git a/docs/robots/common/physical_tools.mdx b/docs_robots/common/physical_tools.mdx
similarity index 100%
rename from docs/robots/common/physical_tools.mdx
rename to docs_robots/common/physical_tools.mdx
diff --git a/docs/robots/indoor_robots/_category_.json b/docs_robots/indoor_robots/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/_category_.json
rename to docs_robots/indoor_robots/_category_.json
diff --git a/docs/robots/indoor_robots/boxer/_category_.json b/docs_robots/indoor_robots/boxer/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/boxer/_category_.json
rename to docs_robots/indoor_robots/boxer/_category_.json
diff --git a/docs/robots/indoor_robots/boxer/integration_boxer.mdx b/docs_robots/indoor_robots/boxer/integration_boxer.mdx
similarity index 100%
rename from docs/robots/indoor_robots/boxer/integration_boxer.mdx
rename to docs_robots/indoor_robots/boxer/integration_boxer.mdx
diff --git a/docs/robots/indoor_robots/boxer/maintenance_boxer.mdx b/docs_robots/indoor_robots/boxer/maintenance_boxer.mdx
similarity index 100%
rename from docs/robots/indoor_robots/boxer/maintenance_boxer.mdx
rename to docs_robots/indoor_robots/boxer/maintenance_boxer.mdx
diff --git a/docs/robots/indoor_robots/boxer/troubleshooting_boxer.mdx b/docs_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
similarity index 89%
rename from docs/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
rename to docs_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
index 2a399ef7f..31b50effa 100644
--- a/docs/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
+++ b/docs_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/tutorials_boxer.mdx b/docs_robots/indoor_robots/boxer/tutorials_boxer.mdx
similarity index 98%
rename from docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/tutorials_boxer.mdx
rename to docs_robots/indoor_robots/boxer/tutorials_boxer.mdx
index 8f5c1b2b5..33d69c786 100644
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/tutorials_boxer.mdx
+++ b/docs_robots/indoor_robots/boxer/tutorials_boxer.mdx
@@ -32,7 +32,7 @@ It is a lightly modified [OTTO 100](https://ottomotors.com/amrs) robot, equipped
to the top of the Base Unit. This Backpack Computer communicates with the OTTO 100 via its attachment port, located
on the top of the Base Unit.
-The Boxer is currently only supported in [ROS 1](/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/tutorials_boxer.mdx).
+The Boxer is currently only supported in [ROS 1](/docs_robots/legacy/ros1_robots/indoor_robots/boxer/tutorials_boxer).
For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/boxer).
diff --git a/docs/robots/indoor_robots/boxer/user_manual_boxer.mdx b/docs_robots/indoor_robots/boxer/user_manual_boxer.mdx
similarity index 100%
rename from docs/robots/indoor_robots/boxer/user_manual_boxer.mdx
rename to docs_robots/indoor_robots/boxer/user_manual_boxer.mdx
diff --git a/docs/robots/indoor_robots/dingo/_category_.json b/docs_robots/indoor_robots/dingo/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/dingo/_category_.json
rename to docs_robots/indoor_robots/dingo/_category_.json
diff --git a/docs/robots/indoor_robots/dingo/integration_dingo/_category_.json b/docs_robots/indoor_robots/dingo/integration_dingo/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/dingo/integration_dingo/_category_.json
rename to docs_robots/indoor_robots/dingo/integration_dingo/_category_.json
diff --git a/docs/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx b/docs_robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
similarity index 100%
rename from docs/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
rename to docs_robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
diff --git a/docs/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json b/docs_robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
rename to docs_robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
diff --git a/docs/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx b/docs_robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
similarity index 100%
rename from docs/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
rename to docs_robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
diff --git a/docs/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx b/docs_robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
similarity index 100%
rename from docs/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
rename to docs_robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
diff --git a/docs/robots/indoor_robots/dingo/maintenance_dingo.mdx b/docs_robots/indoor_robots/dingo/maintenance_dingo.mdx
similarity index 93%
rename from docs/robots/indoor_robots/dingo/maintenance_dingo.mdx
rename to docs_robots/indoor_robots/dingo/maintenance_dingo.mdx
index b456b04df..9899d94f1 100644
--- a/docs/robots/indoor_robots/dingo/maintenance_dingo.mdx
+++ b/docs_robots/indoor_robots/dingo/maintenance_dingo.mdx
@@ -3,13 +3,12 @@ title: Dingo Maintenance
sidebar_label: Maintenance
sidebar_position: 5
---
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_battery_care.mdx";
import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
import ComponentLifepo4BatteryCareTips from "/components/maintenance/lifepo4_battery_care_tips.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
@@ -82,7 +81,7 @@ The initial stage will take 2 - 4 hours, and a complete charge may take up to 8
### MCU Firmware Update
-Refer to [firmware update instructions](../../../ros/installation/robot#firmware-update).
+Refer to [firmware update instructions](/docs/ros/installation/robot#firmware-update).
Be sure to select the ROS 2 distribution that matches the ROS 2 distribution installed on your robot.
### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
diff --git a/docs/robots/indoor_robots/dingo/troubleshooting_dingo.mdx b/docs_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
similarity index 89%
rename from docs/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
rename to docs_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
index 9df6913c5..08c4fdc2a 100644
--- a/docs/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
+++ b/docs_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs/robots/indoor_robots/dingo/tutorials_dingo.mdx b/docs_robots/indoor_robots/dingo/tutorials_dingo.mdx
similarity index 91%
rename from docs/robots/indoor_robots/dingo/tutorials_dingo.mdx
rename to docs_robots/indoor_robots/dingo/tutorials_dingo.mdx
index 59b2481b7..17ea569c8 100644
--- a/docs/robots/indoor_robots/dingo/tutorials_dingo.mdx
+++ b/docs_robots/indoor_robots/dingo/tutorials_dingo.mdx
@@ -5,7 +5,7 @@ sidebar_position: 4
---
import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/indoor_robots/dingo/user_manual_dingo.mdx b/docs_robots/indoor_robots/dingo/user_manual_dingo.mdx
similarity index 100%
rename from docs/robots/indoor_robots/dingo/user_manual_dingo.mdx
rename to docs_robots/indoor_robots/dingo/user_manual_dingo.mdx
diff --git a/docs/robots/indoor_robots/ridgeback/_category_.json b/docs_robots/indoor_robots/ridgeback/_category_.json
similarity index 100%
rename from docs/robots/indoor_robots/ridgeback/_category_.json
rename to docs_robots/indoor_robots/ridgeback/_category_.json
diff --git a/docs/robots/indoor_robots/ridgeback/integration_ridgeback.mdx b/docs_robots/indoor_robots/ridgeback/integration_ridgeback.mdx
similarity index 100%
rename from docs/robots/indoor_robots/ridgeback/integration_ridgeback.mdx
rename to docs_robots/indoor_robots/ridgeback/integration_ridgeback.mdx
diff --git a/docs/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx b/docs_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
similarity index 88%
rename from docs/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
rename to docs_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
index 9c71f3257..5365a3b92 100644
--- a/docs/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
+++ b/docs_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
@@ -3,11 +3,10 @@ title: Ridgeback Maintenance
sidebar_label: Maintenance
sidebar_position: 4
---
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
import Support from "/components/support.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
@@ -44,7 +43,7 @@ Please contact Clearpath Robotics for additional information about Ridgeback's b
### MCU Firmware Update
-Refer to [firmware update instructions](../../../ros/installation/robot#firmware-update).
+Refer to [firmware update instructions](/docs/ros/installation/robot#firmware-update).
Be sure to select the ROS 2 distribution that matches the ROS 2 distribution installed on your robot.
### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx b/docs_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
rename to docs_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
index 97de97591..e7d1b761e 100644
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
+++ b/docs_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx b/docs_robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
similarity index 89%
rename from docs/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
rename to docs_robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
index 7e192f988..d73a1a2a1 100644
--- a/docs/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
+++ b/docs_robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
@@ -5,7 +5,7 @@ sidebar_position: 3
---
import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx b/docs_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
similarity index 99%
rename from docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
rename to docs_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
index 379451bff..c20973e49 100644
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
+++ b/docs_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
@@ -109,7 +109,7 @@ this cannot be changed since the MCU is statically set to 192.168.131.2 and expe
| 192.168.131.20 | Front-facing LIDAR |
| 192.168.131.21 | Rear-facing LIDAR (if present) |
-See [Standard IP Addresses](../../../ros/networking/standard_ip_addresses.mdx) for a full list of common IP addresses.
+See [Standard IP Addresses](/docs/ros/networking/standard_ip_addresses) for a full list of common IP addresses.
#### Payload Integration Plate
diff --git a/docs/robots/learning_platforms/_category_.json b/docs_robots/learning_platforms/_category_.json
similarity index 100%
rename from docs/robots/learning_platforms/_category_.json
rename to docs_robots/learning_platforms/_category_.json
diff --git a/docs/robots/learning_platforms/turtlebot4.mdx b/docs_robots/learning_platforms/turtlebot4.mdx
similarity index 100%
rename from docs/robots/learning_platforms/turtlebot4.mdx
rename to docs_robots/learning_platforms/turtlebot4.mdx
diff --git a/docs/robots/legacy/_category_.json b/docs_robots/legacy/_category_.json
similarity index 100%
rename from docs/robots/legacy/_category_.json
rename to docs_robots/legacy/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/legacy/pr2.mdx b/docs_robots/legacy/pr2.mdx
similarity index 96%
rename from docs_versioned_docs/version-ros1noetic/robots/legacy/pr2.mdx
rename to docs_robots/legacy/pr2.mdx
index bb9636ba1..f8c7189c2 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/legacy/pr2.mdx
+++ b/docs_robots/legacy/pr2.mdx
@@ -1,7 +1,7 @@
---
title: PR2
sidebar_label: PR2
-sidebar_position: 1
+sidebar_position: 2
toc_min_heading_level: 2
toc_max_heading_level: 4
---
diff --git a/docs_robots/legacy/ros1_robots/_category_.json b/docs_robots/legacy/ros1_robots/_category_.json
new file mode 100644
index 000000000..23b4a6e86
--- /dev/null
+++ b/docs_robots/legacy/ros1_robots/_category_.json
@@ -0,0 +1,4 @@
+{
+ "label": "ROS 1 Robots",
+ "position": 1
+}
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/_category_.json b/docs_robots/legacy/ros1_robots/accessories/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/accessories.mdx b/docs_robots/legacy/ros1_robots/accessories/accessories.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/accessories.mdx
rename to docs_robots/legacy/ros1_robots/accessories/accessories.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/_category_.json b/docs_robots/legacy/ros1_robots/accessories/add-ons/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/add-ons.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/add-ons.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/add-ons.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/add-ons.mdx
diff --git a/docs/robots/accessories/add-ons/base_station.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/base_station.mdx
similarity index 90%
rename from docs/robots/accessories/add-ons/base_station.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/base_station.mdx
index 0ec2e6f96..695fd2520 100644
--- a/docs/robots/accessories/add-ons/base_station.mdx
+++ b/docs_robots/legacy/ros1_robots/accessories/add-ons/base_station.mdx
@@ -37,6 +37,6 @@ Clearpath uses this RTK correction in its OutdoorNav autonomy software, but we d
:::note
-Refer to the [Standard IP Addresses page](../../../ros/networking/standard_ip_addresses.mdx) for the commonly used device IP addresses.
+Refer to the [Network IP Addresses page](/docs/ros1noetic/ros/networking/network_ip_addresses) for the commonly used device IP addresses.
:::
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/controllers.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/controllers.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/controllers.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/controllers.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/din_rail.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/din_rail.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/din_rail.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/din_rail.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/network_access_point.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/network_access_point.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/network_access_point.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/network_access_point.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/network_switch.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/network_switch.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/network_switch.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/network_switch.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/outdoornav_starter_kit.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/outdoornav_starter_kit.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/outdoornav_starter_kit.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/outdoornav_starter_kit.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/power_supplies.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/power_supplies.mdx
similarity index 97%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/power_supplies.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/power_supplies.mdx
index c190acba1..7954ab6e9 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/power_supplies.mdx
+++ b/docs_robots/legacy/ros1_robots/accessories/add-ons/power_supplies.mdx
@@ -45,7 +45,7 @@ This is our process for choosing a new enclosed power supply.
:::
-9. Review the electrical termination method to see if it is ideal for your application. It is common to see screw terminals for [Ring Terminals](../../common/components/connectors/ring_terminal.mdx), though there are other options.
+9. Review the electrical termination method to see if it is ideal for your application. It is common to see screw terminals for [Ring Terminals](/docs_robots/common/parts/connectors/ring_terminal.mdx), though there are other options.
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/relay_board.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/relay_board.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/relay_board.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/relay_board.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/stack_light.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/stack_light.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/stack_light.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/stack_light.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/tower.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/tower.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/tower.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/tower.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/usb_hub.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/usb_hub.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/usb_hub.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/usb_hub.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/wireless_stop_system.mdx b/docs_robots/legacy/ros1_robots/accessories/add-ons/wireless_stop_system.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/add-ons/wireless_stop_system.mdx
rename to docs_robots/legacy/ros1_robots/accessories/add-ons/wireless_stop_system.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/computers.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/computers.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/computers.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/computers.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_software.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_software.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_software.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_software.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/mini_itx.mdx b/docs_robots/legacy/ros1_robots/accessories/computers/mini_itx.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/computers/mini_itx.mdx
rename to docs_robots/legacy/ros1_robots/accessories/computers/mini_itx.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/_category_.json b/docs_robots/legacy/ros1_robots/accessories/manipulators/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/manipulators/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/flir_ptu_e46.mdx b/docs_robots/legacy/ros1_robots/accessories/manipulators/flir_ptu_e46.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/flir_ptu_e46.mdx
rename to docs_robots/legacy/ros1_robots/accessories/manipulators/flir_ptu_e46.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/kinova_gen3_lite.mdx b/docs_robots/legacy/ros1_robots/accessories/manipulators/kinova_gen3_lite.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/kinova_gen3_lite.mdx
rename to docs_robots/legacy/ros1_robots/accessories/manipulators/kinova_gen3_lite.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/manipulators.mdx b/docs_robots/legacy/ros1_robots/accessories/manipulators/manipulators.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/manipulators/manipulators.mdx
rename to docs_robots/legacy/ros1_robots/accessories/manipulators/manipulators.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/pacs.mdx b/docs_robots/legacy/ros1_robots/accessories/pacs.mdx
similarity index 99%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/pacs.mdx
rename to docs_robots/legacy/ros1_robots/accessories/pacs.mdx
index 131e8484e..32d53e8f8 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/accessories/pacs.mdx
+++ b/docs_robots/legacy/ros1_robots/accessories/pacs.mdx
@@ -69,7 +69,7 @@ Refer to the integration pages for our robots for more details:
| Plate—80 X 80, Attachment Interface, Large | [027110](/assets/pdf/clearpath_robotics_027110.pdf) |
| Plate—80 X 80, Attachment Interface, Manipulator (UR3 and UR5) | [027269](/assets/pdf/clearpath_robotics_027269.pdf) |
| Plate—80 X 80, Attachment Interface | [028866](/assets/pdf/clearpath_robotics_028866.pdf) |
-| Screw, Round Head, M5×0.8 | [Many](../common/components/fasteners/screw_round_head.mdx) |
+| Screw, Round Head, M5×0.8 | [Many](/docs_robots/common/parts/fasteners/screw_round_head) |
## Sensor and Attachment Kits
@@ -120,7 +120,7 @@ Refer to the integration pages for our robots for more details:
| | [Network Switch, 8 Port](add-ons/network_switch.mdx) | 025333 | 027641 | 027640 | - |
| | [Network Switch, 16 Port](add-ons/network_switch.mdx) | 029098 | - | - | - |
| | [USB Hub, 7 Port](add-ons/usb_hub.mdx) | 025440 | 027643 | 027642 | - |
-| **OutdoorNav HW** | [OutdoorNav Starter Kit](../../robots/accessories/add-ons/outdoornav_starter_kit.mdx) | - | 028356 | - | - |
+| **OutdoorNav HW** | [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) | - | 028356 | - | - |
| **Power Supply** | [Power Supply, SB-15](add-ons/power_supplies.mdx) | - | 028902 | 028901 | - |
| | [Power Supply, SB-25](add-ons/power_supplies.mdx) | - | 028904 | 028903 | - |
| | [Power Supply, TEP 150](add-ons/power_supplies.mdx) | - | 028942 | 028941 | - |
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/axis_f1035_e.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/axis_f1035_e.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/axis_f1035_e.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/axis_f1035_e.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/axis_m5525_e.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/axis_m5525_e.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/axis_m5525_e.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/axis_m5525_e.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/flir_blackfly_s.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/flir_blackfly_s.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/flir_blackfly_s.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/flir_blackfly_s.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/flir_ladybug5p.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/flir_ladybug5p.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/flir_ladybug5p.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/flir_ladybug5p.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/occam_omni_60.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/occam_omni_60.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/occam_omni_60.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/occam_omni_60.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/realsense_d435.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/realsense_d435.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/realsense_d435.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/realsense_d435.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/gps/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/gps/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/garmin_gps_18x.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/gps/garmin_gps_18x.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/garmin_gps_18x.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/gps/garmin_gps_18x.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/swift_navigation_duro.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/gps/swift_navigation_duro.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/gps/swift_navigation_duro.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/gps/swift_navigation_duro.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/imu/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/imu/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/imu/microstrain_3dm_gx5.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/redshift_labs_um7.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/imu/redshift_labs_um7.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/imu/redshift_labs_um7.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/imu/redshift_labs_um7.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust10_lx.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust20_lx.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/sick_lms111.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/sick_lms111.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_2d/sick_lms111.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_2d/sick_lms111.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/_category_.json b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/_category_.json
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/ouster.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/ouster.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/ouster.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/ouster.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/sensors.mdx b/docs_robots/legacy/ros1_robots/accessories/sensors/sensors.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/accessories/sensors/sensors.mdx
rename to docs_robots/legacy/ros1_robots/accessories/sensors/sensors.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/integration_boxer.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/integration_boxer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/integration_boxer.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/integration_boxer.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/maintenance_boxer.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/maintenance_boxer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/maintenance_boxer.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/maintenance_boxer.mdx
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/troubleshooting_boxer.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
index 2a399ef7f..1903d98e3 100644
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/troubleshooting_boxer.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/tutorials_boxer.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/tutorials_boxer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/tutorials_boxer.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/tutorials_boxer.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/user_manual_boxer.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/boxer/user_manual_boxer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/user_manual_boxer.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/boxer/user_manual_boxer.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/maintenance_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/maintenance_dingo.mdx
similarity index 97%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/maintenance_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/maintenance_dingo.mdx
index b4c92ace1..28f0f1a75 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/maintenance_dingo.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/maintenance_dingo.mdx
@@ -9,7 +9,7 @@ import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_batt
import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
import ComponentLifepo4BatteryCareTips from "/components/maintenance/lifepo4_battery_care_tips.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/troubleshooting_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
index 9df6913c5..f9d48acbf 100644
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/troubleshooting_dingo.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/tutorials_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/tutorials_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/tutorials_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/tutorials_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/user_manual_dingo.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/dingo/user_manual_dingo.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/user_manual_dingo.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/dingo/user_manual_dingo.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/_category_.json b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/_category_.json
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/integration_ridgeback.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/integration_ridgeback.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/integration_ridgeback.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/integration_ridgeback.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
similarity index 97%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
index b2a31caa3..dffb9e437 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
@@ -6,7 +6,7 @@ sidebar_position: 4
import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
similarity index 89%
rename from docs/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
index 97de97591..3586cc698 100644
--- a/docs/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
similarity index 99%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
rename to docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
index ae12ff48d..bffed76d1 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
+++ b/docs_robots/legacy/ros1_robots/indoor_robots/ridgeback/user_manual_ridgeback.mdx
@@ -112,7 +112,7 @@ this cannot be changed since the MCU is statically set to 192.168.131.2 and expe
| 192.168.131.20 | Front-facing LIDAR |
| 192.168.131.21 | Rear-facing LIDAR (if present) |
-See [Network IP Addresses](../../../ros/networking/network_ip_addresses.mdx) for a full list of common IP addresses.
+See [Network IP Addresses](/docs/ros1noetic/ros/networking/network_ip_addresses) for a full list of common IP addresses.
#### Payload Integration Plate
diff --git a/docs/robots/outdoor_robots/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a300/integration_husky/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a300/integration_husky/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/integration_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/integration_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/integration_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/integration_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/electronics_rack_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/electronics_rack_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/top_plate_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/top_plate_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/user_bay_cover_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/user_bay_cover_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/maintenance_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/maintenance_husky.mdx
similarity index 99%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/maintenance_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/maintenance_husky.mdx
index 0998b636e..2bb568b13 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/maintenance_husky.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/maintenance_husky.mdx
@@ -10,7 +10,7 @@ import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_batt
import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
import ComponentBillOfMaterialsNote from "/components/maintenance/bill_of_materials_note.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/troubleshooting_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/troubleshooting_husky.mdx
similarity index 98%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/troubleshooting_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/troubleshooting_husky.mdx
index e13214932..82fa5c25d 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/troubleshooting_husky.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/troubleshooting_husky.mdx
@@ -184,11 +184,11 @@ Your Husky will roll if:
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/tutorials_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/tutorials_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/tutorials_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/tutorials_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/user_manual_husky.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/husky/user_manual_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/user_manual_husky.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/husky/user_manual_husky.mdx
diff --git a/docs/robots/outdoor_robots/jackal/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/jackal/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/integration_jackal.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/integration_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/integration_jackal.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/integration_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/maintenance_jackal.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/maintenance_jackal.mdx
similarity index 96%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/maintenance_jackal.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/maintenance_jackal.mdx
index a3c3bbe72..614351e0e 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/maintenance_jackal.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/maintenance_jackal.mdx
@@ -6,7 +6,7 @@ sidebar_position: 4
import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
index b40fdd219..c47bead8a 100644
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/tutorials_jackal.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/tutorials_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/tutorials_jackal.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/tutorials_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/user_manual_jackal.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/jackal/user_manual_jackal.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/user_manual_jackal.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/jackal/user_manual_jackal.mdx
diff --git a/docs/robots/outdoor_robots/warthog/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/_category_.json
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/_category_.json
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
diff --git a/docs/robots/outdoor_robots/husky/a300/integration_husky/kits/_category_.json b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a300/integration_husky/kits/_category_.json
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
similarity index 97%
rename from docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
index 8aacdf691..d6692baa3 100644
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
@@ -48,7 +48,7 @@ Please email \ if you want Clearpath's te
## Tools Required
- Drill, with Ø6 mm drill bit
-- Rivet installation tool (Refer to our [Physical Tools](../../../../common/physical_tools.mdx) page for a suggested rivet installation tool)
+- Rivet installation tool (Refer to our [Physical Tools](/docs_robots/common/physical_tools) page for a suggested rivet installation tool)
- Large flat-head screwdriver, or a thread insert installation tool
- Hex Key, 5 mm
- Torque wrench _(optional, for safety applications)_
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/maintenance_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/maintenance_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/maintenance_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/maintenance_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
index 3dbc3a08c..10aa155d5 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
+++ b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
+Refer to the [Networking page](/docs/ros1noetic/ros/networking).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
+Reter to the [Networking page](/docs/ros1noetic/ros/networking).
---
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/tutorials_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/tutorials_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/tutorials_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/tutorials_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/user_manual_warthog.mdx b/docs_robots/legacy/ros1_robots/outdoor_robots/warthog/user_manual_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/user_manual_warthog.mdx
rename to docs_robots/legacy/ros1_robots/outdoor_robots/warthog/user_manual_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/robots.mdx b/docs_robots/legacy/ros1_robots/robots.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/robots.mdx
rename to docs_robots/legacy/ros1_robots/robots.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/_category_.json b/docs_robots/legacy/ros1_robots/solutions/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/_category_.json
rename to docs_robots/legacy/ros1_robots/solutions/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/_category_.json b/docs_robots/legacy/ros1_robots/solutions/husky_observer/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/_category_.json
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/integration_husky_observer.mdx b/docs_robots/legacy/ros1_robots/solutions/husky_observer/integration_husky_observer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/integration_husky_observer.mdx
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/integration_husky_observer.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/maintenance_husky_observer.mdx b/docs_robots/legacy/ros1_robots/solutions/husky_observer/maintenance_husky_observer.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/maintenance_husky_observer.mdx
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/maintenance_husky_observer.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/troubleshooting_husky_observer.mdx b/docs_robots/legacy/ros1_robots/solutions/husky_observer/troubleshooting_husky_observer.mdx
similarity index 91%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/troubleshooting_husky_observer.mdx
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/troubleshooting_husky_observer.mdx
index 62b59ad56..ed5e84fc8 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/troubleshooting_husky_observer.mdx
+++ b/docs_robots/legacy/ros1_robots/solutions/husky_observer/troubleshooting_husky_observer.mdx
@@ -6,7 +6,7 @@ sidebar_position: 5
import Support from "/components/support.mdx";
-Refer to [Husky Troubleshooting](../../../robots/outdoor_robots/husky/troubleshooting_husky.mdx) and
+Refer to [Husky Troubleshooting](../../../ros1_robots/outdoor_robots/husky/troubleshooting_husky.mdx) and
[OutdoorNav Frequently Asked Questions](/docs_outdoornav_user_manual/faq) for
troubleshooting tips related to the base Husky and to the OutdoorNav software.
Additional topics related to Husky Observer are outlined below.
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/tutorials_husky_observer.mdx b/docs_robots/legacy/ros1_robots/solutions/husky_observer/tutorials_husky_observer.mdx
similarity index 81%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/tutorials_husky_observer.mdx
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/tutorials_husky_observer.mdx
index 3dd3e9fb0..95422fc5f 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/tutorials_husky_observer.mdx
+++ b/docs_robots/legacy/ros1_robots/solutions/husky_observer/tutorials_husky_observer.mdx
@@ -14,7 +14,7 @@ import Support from "/components/support.mdx";
### Introduction
Husky Observer is a fully integrated system that enables robotics developers to accelerate inspection solutions.
-It is built on top of the versatile [Husky](../../../robots/outdoor_robots/husky/user_manual_husky.mdx) base platform
+It is built on top of the versatile [Husky](../../../ros1_robots/outdoor_robots/husky/user_manual_husky.mdx) base platform
The tutorial topics are listed in the right column and presented in the suggested reading order.
For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/husky).
@@ -28,7 +28,7 @@ These tutorials assume that you are comfortable working with ROS. We recommend s
:::note
-The Husky Observer is built on the the Husky platform. See also the [Husky Tutorials](../../../robots/outdoor_robots/husky/tutorials_husky.mdx#husky-ros-packages).
+The Husky Observer is built on the the Husky platform. See also the [Husky Tutorials](../../../ros1_robots/outdoor_robots/husky/tutorials_husky.mdx#husky-ros-packages).
:::
diff --git a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/user_manual_husky_observer.mdx b/docs_robots/legacy/ros1_robots/solutions/husky_observer/user_manual_husky_observer.mdx
similarity index 99%
rename from docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/user_manual_husky_observer.mdx
rename to docs_robots/legacy/ros1_robots/solutions/husky_observer/user_manual_husky_observer.mdx
index 667ca830e..962daf115 100644
--- a/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/user_manual_husky_observer.mdx
+++ b/docs_robots/legacy/ros1_robots/solutions/husky_observer/user_manual_husky_observer.mdx
@@ -22,7 +22,7 @@ import ComponentInstallingRemoteComputerSoftware from "/docs_versioned_docs/vers
## Introduction
Husky Observer is a fully integrated system that enables robotics developers to accelerate inspection solutions.
-Built on top of the versatile [Husky](../../../robots/outdoor_robots/husky/user_manual_husky.mdx) base platform,
+Built on top of the versatile [Husky A200](../../../ros1_robots/outdoor_robots/husky/user_manual_husky.mdx) base platform,
Husky Observer enables robotics developers to fast-track their system development. With it, you can get your test
application running faster without worrying about autonomous navigation and sensor integration.
@@ -845,7 +845,7 @@ and [Appendix A](#networking-configuration) for networking details.
To use your controller, it must be paired with your Husky Observer and powered on.
Note that your controller is already paired with your Husky Observer when it ships.
If your controller has become unpaired or if you wish to pair a new controller, following the instructions in the
-[Husky Tutorials](../../../robots/outdoor_robots/husky/tutorials_husky.mdx#pairing-the-controller).
+[Husky Tutorials](../../outdoor_robots/husky/tutorials_husky.mdx#pairing-the-controller).
To teleoperate Husky Observer, first release the motion stop. Then, referring to the following image, press the
enable button (either slow or turbo mode) and use the left thumbstick to drive Husky Observer.
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/_category_.json b/docs_robots/outdoor_robots/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/_category_.json
rename to docs_robots/outdoor_robots/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/_category_.json b/docs_robots/outdoor_robots/husky/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/_category_.json
rename to docs_robots/outdoor_robots/husky/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a200/_category_.json b/docs_robots/outdoor_robots/husky/a200/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/_category_.json
rename to docs_robots/outdoor_robots/husky/a200/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/_category_.json b/docs_robots/outdoor_robots/husky/a200/integration_husky/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/integration_dingo/_category_.json
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/integration_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/integration_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/integration_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/integration_husky.mdx
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/electronics_rack_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/electronics_rack_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_full_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_full_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_full_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_full_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_partial_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_partial_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_partial_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_partial_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_stiffener_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_stiffener_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a200/integration_husky/kits/riser_stiffener_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/riser_stiffener_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/top_plate_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/top_plate_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx b/docs_robots/outdoor_robots/husky/a200/integration_husky/kits/user_bay_cover_husky.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/integration_husky/kits/user_bay_cover_husky.mdx
diff --git a/docs/robots/outdoor_robots/husky/a200/maintenance_husky.mdx b/docs_robots/outdoor_robots/husky/a200/maintenance_husky.mdx
similarity index 99%
rename from docs/robots/outdoor_robots/husky/a200/maintenance_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/maintenance_husky.mdx
index eeceec264..d6e217875 100644
--- a/docs/robots/outdoor_robots/husky/a200/maintenance_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a200/maintenance_husky.mdx
@@ -10,7 +10,7 @@ import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_batt
import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
import ComponentBillOfMaterialsNote from "/components/maintenance/bill_of_materials_note.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx b/docs_robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx
similarity index 98%
rename from docs/robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx
index 61bc338ff..8e0824ff5 100644
--- a/docs/robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a200/troubleshooting_husky.mdx
@@ -185,11 +185,11 @@ Your Husky will roll if:
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs/robots/outdoor_robots/husky/a200/tutorials_husky.mdx b/docs_robots/outdoor_robots/husky/a200/tutorials_husky.mdx
similarity index 92%
rename from docs/robots/outdoor_robots/husky/a200/tutorials_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/tutorials_husky.mdx
index a16e18464..a8d176175 100644
--- a/docs/robots/outdoor_robots/husky/a200/tutorials_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a200/tutorials_husky.mdx
@@ -7,7 +7,7 @@ toc_max_heading_level: 4
---
import ComponentIntroductionHusky from "/components/introduction_husky.mdx";
-import ComponentTutorialLinks from "../../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/outdoor_robots/husky/a200/user_manual_husky.mdx b/docs_robots/outdoor_robots/husky/a200/user_manual_husky.mdx
similarity index 99%
rename from docs/robots/outdoor_robots/husky/a200/user_manual_husky.mdx
rename to docs_robots/outdoor_robots/husky/a200/user_manual_husky.mdx
index 3e07db3df..12ee0d572 100644
--- a/docs/robots/outdoor_robots/husky/a200/user_manual_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a200/user_manual_husky.mdx
@@ -268,7 +268,7 @@ To teleoperate Husky, first release the motion stop. Then, referring to the foll
Robot Operating System (ROS) is an extensible framework for controlling and working with robotic systems.
Clearpath Robotics recommends using ROS with your robot. If this is your first time using ROS, it is strongly
-recommended to run through our series of [ROS tutorials](../../../../ros) to learn
+recommended to run through our series of [ROS tutorials](/docs/ros) to learn
the basics of ROS.
### Battery Charging
diff --git a/docs/robots/outdoor_robots/husky/a300/_category_.json b/docs_robots/outdoor_robots/husky/a300/_category_.json
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a300/_category_.json
rename to docs_robots/outdoor_robots/husky/a300/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/_category_.json b/docs_robots/outdoor_robots/husky/a300/integration_husky/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/_category_.json
rename to docs_robots/outdoor_robots/husky/a300/integration_husky/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a300/integration_husky/integration_husky.mdx b/docs_robots/outdoor_robots/husky/a300/integration_husky/integration_husky.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/husky/a300/integration_husky/integration_husky.mdx
rename to docs_robots/outdoor_robots/husky/a300/integration_husky/integration_husky.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/_category_.json b/docs_robots/outdoor_robots/husky/a300/integration_husky/kits/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/husky/integration_husky/kits/_category_.json
rename to docs_robots/outdoor_robots/husky/a300/integration_husky/kits/_category_.json
diff --git a/docs/robots/outdoor_robots/husky/a300/maintenance_husky.mdx b/docs_robots/outdoor_robots/husky/a300/maintenance_husky.mdx
similarity index 99%
rename from docs/robots/outdoor_robots/husky/a300/maintenance_husky.mdx
rename to docs_robots/outdoor_robots/husky/a300/maintenance_husky.mdx
index 34ffdf64a..e7f6ad225 100644
--- a/docs/robots/outdoor_robots/husky/a300/maintenance_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a300/maintenance_husky.mdx
@@ -705,7 +705,7 @@ Ensure proper personal protective equipment is used when performing battery main
### MCU Firmware Update {#mcu_firmware_update}
-Refer to [firmware update instructions](../../../../ros/installation/robot#firmware-update).
+Refer to [firmware update instructions](/docs/ros/installation/robot#firmware-update).
Be sure to select the ROS 2 distribution that matches the ROS 2 distribution installed on your robot.
### Motor Controller Firmware Update {#maintenance_husky_motor_controller_firmware}
diff --git a/docs/robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx b/docs_robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx
similarity index 99%
rename from docs/robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx
rename to docs_robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx
index 111e0cd69..984f6894c 100644
--- a/docs/robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a300/troubleshooting_husky.mdx
@@ -219,7 +219,7 @@ See [above](#wifi-fault).
1. Using the keyboard/monitor, run `ip a` and confirm that an interface with IP address of
`192.168.131.1` exists.
1. Power cycle the robot to see if the issue persists.
-1. For additional assistance, refer to the [Networking page](../../../../ros/networking/overview.mdx) or
+1. For additional assistance, refer to the [Networking page](/docs/ros/networking/overview) or
contact [Support](#support).
---
diff --git a/docs/robots/outdoor_robots/husky/a300/tutorials_husky.mdx b/docs_robots/outdoor_robots/husky/a300/tutorials_husky.mdx
similarity index 89%
rename from docs/robots/outdoor_robots/husky/a300/tutorials_husky.mdx
rename to docs_robots/outdoor_robots/husky/a300/tutorials_husky.mdx
index 58319b867..e0f13c1f6 100644
--- a/docs/robots/outdoor_robots/husky/a300/tutorials_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a300/tutorials_husky.mdx
@@ -7,7 +7,7 @@ toc_max_heading_level: 4
---
import ComponentIntroductionHusky from "/components/introduction_husky_a300.mdx";
-import ComponentTutorialLinks from "../../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/outdoor_robots/husky/a300/user_manual_husky.mdx b/docs_robots/outdoor_robots/husky/a300/user_manual_husky.mdx
similarity index 99%
rename from docs/robots/outdoor_robots/husky/a300/user_manual_husky.mdx
rename to docs_robots/outdoor_robots/husky/a300/user_manual_husky.mdx
index 36764a863..e200591bb 100644
--- a/docs/robots/outdoor_robots/husky/a300/user_manual_husky.mdx
+++ b/docs_robots/outdoor_robots/husky/a300/user_manual_husky.mdx
@@ -1651,13 +1651,13 @@ Husky can be configured to connect to an existing Wi-Fi network.
To get Husky connected to your local Wi-Fi network, follow the setup below.
1. Follow the steps for [Connecting to Husky over an Ethernet Connection](#ethernet-connection).
-1. Run `sudo clearpath-computer-setup` and follow the [Custom Networking](../../../../ros/networking/computer_setup#custom-networking)
+1. Run `sudo clearpath-computer-setup` and follow the [Custom Networking](/docs/ros/networking/computer_setup#custom-networking)
instructions for setting up the Wi-Fi connection.
### Connecting and Using the Controller {#controller}
To use your controller, it must be paired with your Husky and powered on.
-Follow the instructions in the [Joystick Controller Pairing](../../../../ros/installation/controller)
+Follow the instructions in the [Joystick Controller Pairing](/docs/ros/installation/controller)
to pair the controller to Husky.
To teleoperate Husky, first [clear any stop conditions](#husky-emergency-stop-button). Then, referring
@@ -1680,7 +1680,7 @@ In slow mode, the maximum robot speed is 0.3 m/s; in fast mode, the maximum robo
Robot Operating System (ROS) is an extensible framework for controlling and working with robotic systems.
Clearpath Robotics recommends using ROS with your robot. If this is your first time using ROS, it is strongly
-recommended to run through our series of [ROS tutorials](../../../../ros) to learn
+recommended to run through our series of [ROS tutorials](/docs/ros) to learn
the basics of ROS.
Husky A300 is compatible with ROS 2 Jazzy.
diff --git a/docs/robots/outdoor_robots/husky/husky.mdx b/docs_robots/outdoor_robots/husky/husky.mdx
similarity index 75%
rename from docs/robots/outdoor_robots/husky/husky.mdx
rename to docs_robots/outdoor_robots/husky/husky.mdx
index 5b2933446..e88798764 100644
--- a/docs/robots/outdoor_robots/husky/husky.mdx
+++ b/docs_robots/outdoor_robots/husky/husky.mdx
@@ -15,25 +15,25 @@ documentation.
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/_category_.json b/docs_robots/outdoor_robots/jackal/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/_category_.json
rename to docs_robots/outdoor_robots/jackal/_category_.json
diff --git a/docs/robots/outdoor_robots/jackal/integration_jackal.mdx b/docs_robots/outdoor_robots/jackal/integration_jackal.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/jackal/integration_jackal.mdx
rename to docs_robots/outdoor_robots/jackal/integration_jackal.mdx
diff --git a/docs/robots/outdoor_robots/jackal/maintenance_jackal.mdx b/docs_robots/outdoor_robots/jackal/maintenance_jackal.mdx
similarity index 78%
rename from docs/robots/outdoor_robots/jackal/maintenance_jackal.mdx
rename to docs_robots/outdoor_robots/jackal/maintenance_jackal.mdx
index 8583f2baf..fe162289c 100644
--- a/docs/robots/outdoor_robots/jackal/maintenance_jackal.mdx
+++ b/docs_robots/outdoor_robots/jackal/maintenance_jackal.mdx
@@ -5,7 +5,7 @@ sidebar_position: 4
---
import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
+import ComponentsWdSsdCriticalUpdate from "/components/maintenance/_wd_ssd_critical_update.mdx";
import Support from "/components/support.mdx";
@@ -18,7 +18,7 @@ import Support from "/components/support.mdx";
### MCU Firmware Update
-Refer to [firmware update instructions](../../../ros/installation/robot#firmware-update).
+Refer to [firmware update instructions](/docs/ros/installation/robot#firmware-update).
Be sure to select the ROS 2 distribution that matches the ROS 2 distribution installed on your robot.
### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
diff --git a/docs/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx b/docs_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
similarity index 89%
rename from docs/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
rename to docs_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
index b40fdd219..54731c5ee 100644
--- a/docs/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
+++ b/docs_robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/tutorials_jackal.mdx b/docs_robots/outdoor_robots/jackal/tutorials_jackal.mdx
similarity index 92%
rename from docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/tutorials_jackal.mdx
rename to docs_robots/outdoor_robots/jackal/tutorials_jackal.mdx
index f09679c62..ad7bea82b 100644
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/tutorials_jackal.mdx
+++ b/docs_robots/outdoor_robots/jackal/tutorials_jackal.mdx
@@ -7,7 +7,7 @@ toc_max_heading_level: 4
---
import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/outdoor_robots/jackal/user_manual_jackal.mdx b/docs_robots/outdoor_robots/jackal/user_manual_jackal.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/jackal/user_manual_jackal.mdx
rename to docs_robots/outdoor_robots/jackal/user_manual_jackal.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/_category_.json b/docs_robots/outdoor_robots/warthog/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/_category_.json
rename to docs_robots/outdoor_robots/warthog/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/_category_.json b/docs_robots/outdoor_robots/warthog/integration_warthog/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/_category_.json
rename to docs_robots/outdoor_robots/warthog/integration_warthog/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx b/docs_robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json b/docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
rename to docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/_category_.json
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx b/docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_crossbar_warthog.mdx
diff --git a/docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx b/docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx b/docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
similarity index 100%
rename from docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
diff --git a/docs/robots/outdoor_robots/warthog/maintenance_warthog.mdx b/docs_robots/outdoor_robots/warthog/maintenance_warthog.mdx
similarity index 98%
rename from docs/robots/outdoor_robots/warthog/maintenance_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/maintenance_warthog.mdx
index b4c523f2b..9eb0b7888 100644
--- a/docs/robots/outdoor_robots/warthog/maintenance_warthog.mdx
+++ b/docs_robots/outdoor_robots/warthog/maintenance_warthog.mdx
@@ -3,7 +3,6 @@ title: Warthog Maintenance
sidebar_label: Maintenance
sidebar_position: 5
---
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
import Support from "/components/support.mdx";
@@ -185,7 +184,7 @@ You need to use an external computer to update Warthog's MCU firmware. You canno
firmware requires power-cycling the MCU. Warthog's MCU controls the power supply to the Onboard Computer. These instructions
assume the external computer is running some flavour of Linux with access to Clearpath's ROS packages.
-Refer to [firmware update instructions](../../../ros/installation/robot#firmware-update).
+Refer to [firmware update instructions](/docs/ros/installation/robot#firmware-update).
Be sure to select the ROS 2 distribution that matches the ROS 2 distribution installed on your robot.
---
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx b/docs_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
similarity index 89%
rename from docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
index 7a04f0c89..be09577f5 100644
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
+++ b/docs_robots/outdoor_robots/warthog/troubleshooting_warthog.mdx
@@ -18,11 +18,11 @@ import Support from "/components/support.mdx";
### Not getting Wi-Fi internet connection
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
+Refer to the [Networking page](/docs/ros/networking/overview).
### Cannot connect to the robot's computer over a network cable
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
+Reter to the [Networking page](/docs/ros/networking/overview).
---
diff --git a/docs/robots/outdoor_robots/warthog/tutorials_warthog.mdx b/docs_robots/outdoor_robots/warthog/tutorials_warthog.mdx
similarity index 87%
rename from docs/robots/outdoor_robots/warthog/tutorials_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/tutorials_warthog.mdx
index adf4e9410..77a76684f 100644
--- a/docs/robots/outdoor_robots/warthog/tutorials_warthog.mdx
+++ b/docs_robots/outdoor_robots/warthog/tutorials_warthog.mdx
@@ -5,7 +5,7 @@ sidebar_position: 4
---
import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
+import ComponentTutorialLinks from "/components/_tutorials_link.mdx";
import Support from "/components/support.mdx";
diff --git a/docs/robots/outdoor_robots/warthog/user_manual_warthog.mdx b/docs_robots/outdoor_robots/warthog/user_manual_warthog.mdx
similarity index 100%
rename from docs/robots/outdoor_robots/warthog/user_manual_warthog.mdx
rename to docs_robots/outdoor_robots/warthog/user_manual_warthog.mdx
diff --git a/docs/robots/robots.mdx b/docs_robots/robots.mdx
similarity index 100%
rename from docs/robots/robots.mdx
rename to docs_robots/robots.mdx
diff --git a/docs/robots/solutions/_category_.json b/docs_robots/solutions/_category_.json
similarity index 100%
rename from docs/robots/solutions/_category_.json
rename to docs_robots/solutions/_category_.json
diff --git a/docs/robots/solutions/husky_observer/husky_observer.mdx b/docs_robots/solutions/husky_observer/husky_observer.mdx
similarity index 58%
rename from docs/robots/solutions/husky_observer/husky_observer.mdx
rename to docs_robots/solutions/husky_observer/husky_observer.mdx
index a9f26f66e..af2795cb2 100644
--- a/docs/robots/solutions/husky_observer/husky_observer.mdx
+++ b/docs_robots/solutions/husky_observer/husky_observer.mdx
@@ -9,6 +9,6 @@ sidebar_position: 1
Husky Observer is currently available in ROS 1 Noetic only. Use the link below
to access the User Manual.
-[Link to Husky Observer User Manual](/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/user_manual_husky_observer.mdx)
+[Link to Husky Observer User Manual](/docs_robots/legacy/ros1_robots/solutions/husky_observer/user_manual_husky_observer)
:::
diff --git a/docs_versioned_docs/version-ros1noetic/components/_installing_robot_software.mdx b/docs_versioned_docs/version-ros1noetic/components/_installing_robot_software.mdx
index fec2a0e49..6d48b9fff 100644
--- a/docs_versioned_docs/version-ros1noetic/components/_installing_robot_software.mdx
+++ b/docs_versioned_docs/version-ros1noetic/components/_installing_robot_software.mdx
@@ -23,7 +23,7 @@ Installing with the Clearpath Robotics ISO image will completely wipe data on th
The Clearpath Robotics ISO image only targets Intel-family computers (`amd64` architecture).
If your robot runs on an Nvidia Jetson computer, see
-[Jetson Software](/docs_versioned_docs/version-ros1noetic/robots/accessories/computers/jetson/jetson_software.mdx) for software installation details.
+[Jetson Software](/docs_robots/legacy/ros1_robots/accessories/computers/jetson/jetson_software) for software installation details.
:::
diff --git a/docs_versioned_docs/version-ros1noetic/robots/common/_category_.json b/docs_versioned_docs/version-ros1noetic/robots/common/_category_.json
deleted file mode 100644
index 44fea45e2..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/common/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Common",
- "position": 7
-}
diff --git a/docs_versioned_docs/version-ros1noetic/robots/common/colours.mdx b/docs_versioned_docs/version-ros1noetic/robots/common/colours.mdx
deleted file mode 100644
index 5cd241377..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/common/colours.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Colours
-sidebar_position: 3
----
-
-
-
-
-
-
-
-These are the materials and colours visible on the outside of our robots:
-
-| Material | Colour | Material Note |
-| :------------------------- | :----- | :-------------------------------------------------------------------------- |
-| Electroless Nickel Plating | Silver | |
-| Stainless Steel | Silver | |
-| Anodized Aluminum | Black | Anodic Coating, Type II Class 2 in Accordance With MIL-A-8625, Colour Black |
-| Powder Coating | Yellow | Tiger Drylac 49/22550 or 38/20006, Gloss, Smooth, Colour RAL 1006 |
-| Powder Coating | Black | Tiger Drylac 39/80200, Matte, Fine Texture, Colour "Black" |
-| Lettering | White | Polyurethane, RAL 7074 "Telegrey 4" |
-| Lettering | Black | Polyurethane, RAL 9005 "Jet Black" |
-| Rubber | Black | |
-| Plastic | Black | |
-
-
-
-:::info Customization
-
-Let our Sales team know if you need custom colours or graphics on your robot.
-We can work with our paint, silkscreen, and vinyl suppliers to make the customizations that you require.
-
-:::
diff --git a/docs_versioned_docs/version-ros1noetic/robots/common/components/_category_.json b/docs_versioned_docs/version-ros1noetic/robots/common/components/_category_.json
deleted file mode 100644
index 32d855aed..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/common/components/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Components",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros1noetic/robots/common/components/components.mdx b/docs_versioned_docs/version-ros1noetic/robots/common/components/components.mdx
deleted file mode 100644
index a5eade6d7..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/common/components/components.mdx
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: Components Overview
-sidebar_label: Components
-sidebar_position: 1
----
-
-
-
-
-
-The items listed on this page are common connectors, fasteners, and jellybeans that we frequently use in our robots.
-Refer to our [Sensors](../../accessories/sensors/sensors.mdx) and [Add-ons](../../accessories/add-ons/add-ons.mdx) sections for larger subassemblies.
-
----
-
-## Connectors
-
-
-
-
-
-| Description | CPR item | Manufacturer item |
-| :----------------------------- | :------: | :---------------- |
-| M4 stud, 76 A maximum current | 023570 | 3049107 |
-| M5 stud, 125 A maximum current | 023068 | 3049204 |
diff --git a/docs_versioned_docs/version-ros1noetic/robots/common/physical_tools.mdx b/docs_versioned_docs/version-ros1noetic/robots/common/physical_tools.mdx
deleted file mode 100644
index 84f14e462..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/common/physical_tools.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Physical Tools
-sidebar_position: 2
----
-
-These are the most common tools we use at Clearpath Robotics to build and maintain robots.
-There is a much longer list of tools we use to design, test, and build more complicated aspects of our robots—such as Printed Circuit Board Assemblies.
-The intention of this page is to show you what tools we use for maintenance, and for adding sensors to our robots.
-
-:::info Contact Us
-
-Contact our Sales team at \ if you want us to add sensors or custom attachments to your robot.
-We can suggest hardware and software that will meet your application goals.
-
-You can see some of our past Integration Services projects [here](https://clearpathrobotics.com/integration-services/).
-
-:::
-
-:::note
-
-Some tools are specific to the electrical connectors we use at Clearpath Robotics.
-For example, we show a Panduit crimper for ring terminals.
-This suggestion is because use Panduits ring terminals in our cable assemblies.
-There are other manufacturers that make comparable products, such as Molex, Phoenix Contact, and Tyco Electronics.
-
-:::
-
-| Category | Description | Preferred Manufacturer | Manufacturer Item Number |
-| :------------------------------- | :-------------------------------------------------------- | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------- |
-| **Consumables** | Lint Free Cloth | Kimtech | |
-| | Isopropyl Alcohol | | |
-| | Thread Locker, Light | Loctite | [222](https://www.mcmaster.com/1810A27/) |
-| | Thread Locker, Medium | Loctite | [243](https://www.mcmaster.com/91458A115/) |
-| | Thread, Anti-Seize | Loctite | [8065](https://www.mcmaster.com/1019A11/) |
-| | Silicone Sealant | Dow Corning | [3138356](https://www.mcmaster.com/7587A2/) |
-| | Electrical Compound | | |
-| | Cable Ties | | |
-| **Mechanical Fabrication** | Rivet Installation Tool | Milwaukee | [2550-20](https://www.milwaukeetool.com/Products/Power-Tools/Specialty-Tools/Rivet-Tools/2550-20) |
-| | Drill | Milwaukee | [2606-20](https://www.milwaukeetool.com/Products/Power-Tools/Drilling/Drill-Drivers/2606-20) |
-| | Rotary Tool | Dremel | |
-| | Hole Deburring Tool | | |
-| **Mechanical Assembly** | Hex Keys, Metric | Wiha | [66980](https://www.digikey.ca/en/products/detail/wiha/66980/11658234) |
-| | Hex Keys, Imperial | Wiha | [66981](https://www.digikey.ca/en/products/detail/wiha/66981/11658233?s=N4IgTCBcDaICwGYCMBaAbGgnADlQOQBEQBdAXyA) |
-| | Crescent Wrenches, Metric (5 mm - 13 mm) | | |
-| | Crescent Wrenches, Imperial | | |
-| | Adjustable Wrench, Small | | |
-| | Adjustable Wrench, Large | | |
-| | Sockets and Socket Wrenches, Metric (5 mm - 13 mm) | | |
-| | Sockets and Socket Wrenches, Imperial | | |
-| | Sidecutters | Knipex | [78 03 125](https://www.digikey.ca/en/products/detail/knipex-tools-lp/78-03-125/10451639) |
-| **Electrical Cable Fabrication** | Soldering Iron | Pace | [MBT360](https://paceworldwide.com/mbt360-multi-channel-soldering-and-rework-station-w-td-200-and-sx-100) |
-| | Multimeter | Fluke | [115](https://www.digikey.ca/en/products/detail/fluke-electronics/FLUKE-115/1506332) |
-| | Soldering Helping Hands | | |
-| | Wire Strippers | Greenlee Communications | [PA1123](https://www.digikey.ca/en/products/detail/tempo-communications/PA1123/1990599) |
-| | Utility Knife | Olfa | [L-2](https://olfa.com/collections/professional/products/18mm-l-2-rubber-inset-utility-knife#shop) |
-| | Heat Gun | Milwaukee | [2688-20](https://www.milwaukeetool.com/Products/Power-Tools/Specialty-Tools/Heating-Tools/2688-20) |
-| | Crimper, Anderson Powerpole PP15 | Anderson Power Products | [1309G8](https://www.digikey.ca/en/products/detail/anderson-power-products-inc/1309G8/10647425?s=N4IgTCBcDaIIwGYAMBOA4gDhAXQL5A) |
-| | Crimper, Anderson SB50 and PP75 | Anderson Power Products | [1309G4](https://www.digikey.ca/en/products/detail/anderson-power-products-inc/1309G4/10650073) |
-| | Crimper, Molex Mini-Fit-Jr | Molex | [0638190901](https://www.digikey.ca/en/products/detail/molex/0638190901/9655931?s=N4IgTCBcDaIAwDYDMAOAjATjltIC6AvkA) |
-| | Extractor, Molex Mini-Fit-Jr | Molex | [11030044](https://www.digikey.ca/en/products/detail/molex/0011030044/210947?s=N4IgTCBcDaIIxwAwGZGICzpAXQL5A) |
-| | Crimper, Molex Mega-Fit | Molex | [2002187200](https://www.digikey.ca/en/products/detail/molex/2002187200/14311428?s=N4IgTCBcDa4AxzARgBwHYwJAXQL5A) |
-| | Extractor, Molex Mega-Fit | Molex | [0638240810](https://www.digikey.ca/en/products/detail/molex/0638240810/11657656?s=N4IgTCBcDaIGwGYAcYAsAGJBGdIC6AvkA) |
-| | Crimper, Ferrule (Phoenix Contact) | Phoenit Contact | [1213144](https://www.digikey.ca/en/products/detail/phoenix-contact/1213144/5875365) |
-| | Crimper, Ring Terminal (Panduit) | Panduit | [0638190901](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1550/447992) |
-| | Crimper, Quick Disconnect (Panduit) | Panduit | [CT-1525](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1525/447991?s=N4IgTCBcDaIMIBUC0BGArGNIC6BfIA) |
-| | Crimper, Ring Lug Terminals (Panduit) | Panduit | [CT-1700](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1700/447996?s=N4IgTCBcDaIMYBcC0BGA7ABgyAugXyA) |
-| | Sidecutters | Knipex | [78 03 125](https://www.digikey.ca/en/products/detail/knipex-tools-lp/78-03-125/10451639) |
-| **Electrical Assembly** | Scouring Pads (ScotchBrite) | 3M | [61500290558](https://www.digikey.ca/en/products/detail/3m/61500290558/3589749) |
-| | Multimeter | Fluke | [115](https://www.digikey.ca/en/products/detail/fluke-electronics/FLUKE-115/1506332) |
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/troubleshooting_boxer.mdx b/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
deleted file mode 100644
index d8292c5ee..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/boxer/troubleshooting_boxer.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Boxer Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 5
----
-
-import ComponentIntroductionBoxer from "/components/introduction_boxer.mdx";
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-## If the Issue Persists
-
-
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/troubleshooting_dingo.mdx b/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
deleted file mode 100644
index 01bb845e2..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/dingo/troubleshooting_dingo.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Dingo Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 6
----
-
-import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-## If the Issue Persists
-
-
diff --git a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx b/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
deleted file mode 100644
index 8836af8b1..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/indoor_robots/ridgeback/troubleshooting_ridgeback.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Ridgeback Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 5
----
-
-import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-## If the Issue Persists
-
-
diff --git a/docs_versioned_docs/version-ros1noetic/robots/legacy/_category_.json b/docs_versioned_docs/version-ros1noetic/robots/legacy/_category_.json
deleted file mode 100644
index 2db18d85f..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/legacy/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Legacy",
- "position": 5
-}
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx b/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
deleted file mode 100644
index 42e9f269c..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/jackal/troubleshooting_jackal.mdx
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Jackal Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 5
----
-
-import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/networking.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/networking.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-## If the Issue Persists
-
-
diff --git a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx b/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
deleted file mode 100644
index 8aacdf691..000000000
--- a/docs_versioned_docs/version-ros1noetic/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/extrusion_rails_warthog.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Extrusion Rails
-sidebar_position: 1
----
-
-
-
-
-
-This kit adds [25 mm X 50 mm aluminum extrusions](/assets/pdf/clearpath_robotics_028459-TDS1.pdf) to both sides of the Warthog.
-The extrusions are attached to the Warthog using M6×1 stainless steel screws, and [stainless steel rivets](https://www.mcmaster.com/97525A247/) with a Ø5 mm shank.
-
-You can attach your own custom brakets to the extrusions using M5×0.8 T-slot nuts, or these other useful off-the-shelf items:
-
-| Description | CPR Item | Manufacturer | Manufacturer Item |
-| :-------------------------------------------- | :------------------------------------------------------: | :----------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Nut, T-Slot—M5×0.8 X 5.8 X 10, Steel | [028463](/assets/pdf/clearpath_robotics_028463-TDS1.pdf) | Misumi | [HNTTSS5-5](https://us.misumi-ec.com/vona2/detail/110302246150/?HissuCode=HNTTSS5-5&PNSearch=HNTTSS5-5&searchFlow=results2type&KWSearch=HNTTSS5-5) |
-| Bracket, T-Slot, 90°—5.8, 20, Aluminum, Black | [028464](/assets/pdf/clearpath_robotics_028464-TDS1.pdf) | Misumi | [HBLFSSWB5](https://us.misumi-ec.com/vona2/detail/110300437350/?HissuCode=HBLFSSWB5&PNSearch=HBLFSSWB5&searchFlow=results2type&KWSearch=HBLFSSWB5) |
-| Bracket, Flat, 90°—Stainless Steel | | Misumi | [SHPTUL5](https://us.misumi-ec.com/vona2/detail/110302245810/?HissuCode=SHPTUL5&PNSearch=SHPTUL5&searchFlow=results2type&KWSearch=SHPTUL5) |
-| Beam, T-slot—25 X 25, Aluminum, Black | Configurable Lengths | Misumi | [HFSB5-2525](https://us.misumi-ec.com/vona2/detail/110302685050/?HissuCode=HFSB5-2525&PNSearch=HFSB5-2525&searchFlow=results2type&KWSearch=HFSB5-2525) |
-| Beam, T-slot—25 X 50, Aluminum, Black | Configurable Lengths | Misumi | [HFSB5-2550](https://us.misumi-ec.com/vona2/detail/110302685140/?HissuCode=HFSB5-2550&PNSearch=HFSB5-2550&searchFlow=results2type&KWSearch=HFSB5-2550) |
-
-Misumi also offers a range of configurable products that can help with your integration.
-
-Please email \ if you want Clearpath's team to design a bracket structure for your application.
-
----
-
-## Sales Kits
-
-| Description | Sales Kit |
-| :------------------------------------ | :-------: |
-| Installation—Extrusion, 25 X 50, 1217 | 028454 |
-
-## Parts List
-
-| ID | Description | CPR item | Manufacturer Item | Quantity |
-| :-: | :-------------------------------------------------------------- | :-------------------------------------------------: | :----------------------------------------------- | :------: |
-| 1 | Block—76.2 X 25.4 X 25.4 X M10×1.5 | [028452](/assets/pdf/clearpath_robotics_028452.pdf) | | 8 |
-| 2 | Insert, Thread, Adhesive—M6×1 X M10×1.5 X 10.5, Stainless Steel | 028458 | [97120A230](https://www.mcmaster.com/97120A230/) | 8 |
-| 3 | Beam, T-slot—25 X 50, 1217, Aluminum, Black | [028459](/assets/pdf/clearpath_robotics_028459.pdf) | | 2 |
-| 4 | Rivet, Blind, Dome—Ø5 X 20 - 25, Stainless Steel | 028460 | [97525A247](https://www.mcmaster.com/97525A247/) | 16 |
-| 5 | Screw, Cap, Socket Head—M6×1 X 35, Stainless Steel | 023186 | [92290A334](https://www.mcmaster.com/92290A334/) | 8 |
-
-## Tools Required
-
-- Drill, with Ø6 mm drill bit
-- Rivet installation tool (Refer to our [Physical Tools](../../../../common/physical_tools.mdx) page for a suggested rivet installation tool)
-- Large flat-head screwdriver, or a thread insert installation tool
-- Hex Key, 5 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Use the drill to remove the 16 existing rivets on the top deck of the Warthog.
-You can use the Extrusion Beam _(ID3)_ as a reference of what rivets to remove.
-
-:::caution
-
-Just remove the rivet's head with the drill.
-We do not want to enlarge the holes in the Warthog's frame.
-
-:::
-
-:::note
-
-This kit only includes 4 Blocks _(ID1)_ per Beam.
-You can install up to 7 Blocks per beam if your application requires a stiffer base.
-
-:::
-
-:::note
-
-Part of the rivet will fall into the Warthog's steel tube frame.
-We intend for you to leave these scrap bits of rivet within the Warthog's frame.
-
-:::
-
-### Step 2
-
-Place the Blocks _(ID1)_ above the holes where you had removed the rivets.
-
-### Step 3
-
-Insert the new Rivets _(ID4)_ through the Blocks _(ID1)_ and into the Warthog's frame.
-
-### Step 4
-
-Fasten the rivets using your rivet installation tool.
-
-### Step 5
-
-Install a Thread Insert _(ID2)_ into each of the Blocks _(ID1)_ using your standard screwdriver or thread insert installation tool.
-Make sure the installed Thread Inserts are below the top surface of the Blocks.
-
-### Step 6
-
-Place the two Beams _(ID3)_ onto the Warthog's Blocks _(ID1)_.
-
-:::info notice
-
-Notice that the Beams have a small diameter hole on one side, and a larger diameter hole on the other side.
-The small holes face down, the large holes face up.
-
-:::
-
-### Step 7
-
-Install a Screw _(ID5)_ into each of the Blocks _(ID1)_.
-This will fasten the Beams _(ID3)_ onto the Warthog.
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros1noetic/ros/networking/networking.mdx b/docs_versioned_docs/version-ros1noetic/ros/networking/networking.mdx
index 469e5bb26..879eb573b 100644
--- a/docs_versioned_docs/version-ros1noetic/ros/networking/networking.mdx
+++ b/docs_versioned_docs/version-ros1noetic/ros/networking/networking.mdx
@@ -7,7 +7,7 @@ sidebar_position: 3
For details on setting up wired and wireless networking connections to your Clearpath
robot, refer to the robot-specific tutorials, such as the
-[Husky ROS 1 tutorial](../../robots/outdoor_robots/husky/tutorials_husky.mdx#husky-networking).
+[Husky ROS 1 tutorial](/docs_robots/legacy/ros1_robots/outdoor_robots/husky/tutorials_husky#husky-networking).
:::
diff --git a/docs_versioned_docs/version-ros1noetic/ros/ros.mdx b/docs_versioned_docs/version-ros1noetic/ros/ros.mdx
index 896079396..b05aae8b4 100644
--- a/docs_versioned_docs/version-ros1noetic/ros/ros.mdx
+++ b/docs_versioned_docs/version-ros1noetic/ros/ros.mdx
@@ -9,6 +9,6 @@ information for the use of software in robotics systems.
:::note
-For robot-specific software information, refer to the corresponding [Robots](robots/robots.mdx) page.
+For robot-specific software information, refer to the corresponding [Robots](/docs_robots/robots) page.
:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/_category_.json
deleted file mode 100644
index 78c643b7c..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Accessories",
- "position": 6
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/accessories.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/accessories.mdx
deleted file mode 100644
index d4f8c8c9f..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/accessories.mdx
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Accessories Overview
-sidebar_label: Accessories Overview
-sidebar_position: 6
----
-
-Many different types of accessories can be added onto Clearpath robot platforms to suit your specific needs.
-
-:::info links to accessory pages
-
-- [Computers](computers/computers.mdx)
-- [Sensors](sensors/sensors.mdx)
-- [Manipulators](manipulators/manipulators.mdx)
-- [PACS™](pacs.mdx)
-- [Add-ons](add-ons/add-ons.mdx)
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/_category_.json
deleted file mode 100644
index e4c5c20a4..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Add-ons",
- "position": 6
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/add-ons.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/add-ons.mdx
deleted file mode 100644
index 946cf0251..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/add-ons.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Add-ons Overview
-sidebar_label: Add-ons
-sidebar_position: 1
----
-
-
-
-
-
-The following pages list add-on subsystems to support our base robot platforms and sensors.
-Thses pages will list subsystems like:
-
-- Wi-Fi and networking
-- Lights
-- Controllers
-- Power Supplies
-- Cabling and Electrical considerations
-- Brackets and Mechanical considerations
-
-We suggest you:
-
-1. Review our documentation of these accessories.
-2. If you want Clearpath Robotics to integrate accessories on your robot, contact our Sales team at \, whether you want to use a new Clearpath Robotics platform, or reuse your existing vehicle.
-3. Contact our Support team at \ if you have any questions.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/base_station.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/base_station.mdx
deleted file mode 100644
index 0ec2e6f96..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/base_station.mdx
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Base Station
-sidebar_position: 2
----
-
-
-
-
- Base Station with GPS
-
-
-
-Our Base Station is a Network Access Point inside a weatherproof enclosure.
-
-It includes:
-
-- A weatherproof enclosure mounted to a tripod
-- A network access point and antenna to create a Wi-Fi network
-- An AC-DC power supply
-- A battery and charger, so you can use the Base Station remotely
-
-Our robots are configured to automatically connect to the Base Station's Wi-Fi network.
-You can then connect your development computer to the Base Station through Wi-Fi or a network cable, and then share data with the robot over Wi-Fi.
-Our standard Base Station can send data at 100 Mbit/s at up to 100 metres range.
-
-We also have a GPS variant of the Base Station where we add a [Swift Navigation Duro](../sensors/gps/swift_navigation_duro.mdx) to the system, connecting it to the Access Point with a network cable.
-This GPS sensor allows the robot to apply an RTK (Real-Time Kinematic) correction for more accurate localization.
-
-:::note
-
-Clearpath uses this RTK correction in its OutdoorNav autonomy software, but we do not use this data in the standard _/odometry_ rostopic.
-
-:::
-
-:::note
-
-Refer to the [Standard IP Addresses page](../../../ros/networking/standard_ip_addresses.mdx) for the commonly used device IP addresses.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/din_rail.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/din_rail.mdx
deleted file mode 100644
index 235b8e2fc..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/din_rail.mdx
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: DIN rail
-sidebar_position: 4
----
-
-
-
-
-
-
-
-
-
-## Kits
-
-| Description | CPR Item |
-| :-------------------------------- | :------: |
-| Kit, Attachment—80 X 80, DIN Rail | 027881 |
-
-## DIN Rail Lengths
-
-
- Click to expand
-
-
-The OutdoorNav Starter Kit is a low-cost hardware bundle that allows you to begin autonomous outdoor navigation using
-Clearpath's [OutdoorNav Autonomy Software](/docs_outdoornav_user_manual/). It integrates
-easily onto Husky and Jackal, but is compatible with third-party robots as outlined below.
-
-## Item Numbers {#item-numbers}
-
-| Description | Sales Kit |
-| :------------------------------------------ | :-------: |
-| OutdoorNav Starter Kit | 028356 |
-| OutdoorNav Starter Kit Husky Adapter Cable | 029915 |
-| OutdoorNav Starter Kit Jackal Adapter Cable | 029914 |
-| GNSS Antenna Relocation Kit | 028590 |
-| RealSense D435f Relocation Kit | 028817 |
-
-## Mechanical Mounting
-
-The OutdoorNav Starter Kit can be mounted directly using either its 80 X 80 mm or 120 X 120 mm hole pattern as shown in the following image.
-
-
-
-
- Starter Kit mounting hole pattern
-
-
-
-On Jackal, mount the kit using the standard 120 X 120 hole pattern at the front of Jackal.
-
-On Husky, mount the kit on the leading edge of the top plate. Where a PACS-compatible top plate exists, the kit can be mounted directly.
-When using an older Husky without a PACS-compatible top plate, it will be necessary to drill your own holes.
-
-Refer also to the [OutdoorNav Starter Kit Hardware Checklist](/docs_outdoornav_user_manual/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist).
-
----
-
-## Electrical Integration
-
-### Power Integration
-
-The OutdoorNav Starter Kit includes a 1 m IP67 power cable to provide power from the base platform to the Starter Kit.
-Adapter cables can be used for robot-specific integrations.
-
-- For power integration on Husky, purchase the OutdoorNav Starter Kit Husky Adapter Cable, as listed in [Item Numbers](#item-numbers).
-- For power integration on Jackal, purchase the OutdoorNav Starter Kit Jackal Adapter Cable, as listed in [Item Numbers](#item-numbers).
-- For power integration on a third-party robot, an adapter cable will need to be created.
-
- - The provided 1 m power cable is terminated with a Molex Mini-Fit Jr connector (Molex 0039012025).
- - The adapter cable should use the appropriate mating connector (Molex 0039013029).
- - The pinout is illustrated in the figure below:
-
- - Pin 1: VIN (18 to 75 VDC, 7 A max)
- - Pin 2: GND
-
-
-
-
- Starter Kit power cable connector
-
-
-
-### Data Integration
-
-The OutdoorNav Starter Kit includes a 1 m IP67 Ethernet cable for data connectivity between the base platform to the Starter Kit.
-Refer to [OutdoorNav Platform Computer Checklist](/docs_outdoornav_user_manual/integration_requirements/platform_computer_checklist)
-for addititional details on data connectivity.
-
----
-
-## Software Integration
-
-The required software for the OutdoorNav Starter Kit is pre-installed. However, the base platform computer must be configured as outlined
-in the [OutdoorNav Platform Computer Checklist](/docs_outdoornav_user_manual/integration_requirements/platform_computer_checklist).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/power_supplies.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/power_supplies.mdx
deleted file mode 100644
index dc9989900..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/power_supplies.mdx
+++ /dev/null
@@ -1,99 +0,0 @@
----
-title: Power Supplies
-sidebar_position: 7
----
-
-import ComponentPacsExplanation from "/components/pacs_explanation_and_link.mdx";
-
-Clearpath's robots include User Power connectors with regulated 5 V, 12 V, and 24 V depending on the robot platorm.
-Refer to your robot platform's user manual for more details about these User Power connections:
-
-- [Boxer](../../indoor_robots/boxer/user_manual_boxer.mdx)
-- [Dingo](../../indoor_robots/dingo/user_manual_dingo.mdx)
-- [Husky](../../outdoor_robots/husky/user_manual_husky.mdx)
-- [Jackal](../../outdoor_robots/jackal/user_manual_jackal.mdx)
-- [Ridgeback](../../indoor_robots/ridgeback/user_manual_ridgeback.mdx)
-- [TurtleBot4](../../learning_platforms/turtlebot4.mdx)
-- [Warthog](../../outdoor_robots/warthog/user_manual_warthog.mdx)
-
-If you need more power, or at a different output voltage, you can add an enclosed DC-DC power supply.
-This is our process for choosing a new enclosed power supply.
-
-## Process For Choosing A Power Supply {#choosing_a_power_supply}
-
-1. Go to [Digi-Key](https://www.digikey.ca/en/products/filter/dc-dc-converters/132) or [Mouser](https://www.mouser.ca/c/power/dc-dc-converters/?orgKeyword=dc-dc%20converter), and search for _DC-DC Converter_
-2. Filter the results for _Active_ items.
-3. Filter for your preferred Manufacturer, such as:
- - CUI Inc.
- - Delta Electronics
- - MEAN WELL
- - Murata
- - Traco Power
-4. Filter for your intended output voltage.
-5. Filter for your required minimum output current or power.
-6. Review the results, and find options that have an input voltage range matching your robot's battery.
- For example, a Power Supply with an input voltage range of 18 - 36 VDC is acceptable for a Husky with a lead-acid battery, since the Husky's battery volage will be between 24 - 29 VDC.
-7. Review the allowable operating temperature range, and confirm that it is acceptable for your applicaiton.
-8. Review the Power Supply's datasheet, looking for mechanical mounting as well as shock & vibration requirements.
-
- :::tip
-
- 1. Consider using one of the following [PACS™ Kits](#power_supplies_pacs_kits).
- - **15 Watt**: 028901 | Installation, Kit, Sensor—80 X 80, Power Supply, SB-15
- - **25 Watt**: 028903 | Installation, Kit, Sensor—80 X 80, Power Supply, SB-25
- - **150 Watt**: 028941 | Installation, Kit, Sensor—80 X 80, Power Supply, TEP 150
- 2. There are Power Supplies that include mounting brackets for [DIN Rails](../add-ons/din_rail.mdx), which could simplify your integration.
-
- :::
-
-9. Review the electrical termination method to see if it is ideal for your application. It is common to see screw terminals for [Ring Terminals](../../common/components/connectors/ring_terminal.mdx), though there are other options.
-
-
-
-
- Example filtering for a 12 VDC power supply on Digi-Key
-
-
-
-
-
-We use these Relay Boards from [Numato Lab®](https://numato.com/) for controlling lights, larger relay-contactors, and similar powered devices.
-The relay board is wired to a ROS computer with a USB cable, and appears in the computer's _/dev_ directory as a serial device.
-We have developed a ROS driver using Numato's API, so we can control the relays through _rosservices_, and monitor the GPIO inputs through _rostopics_.
-
-| Description | CPR Item | Sales Kit |
-| :------------------------------ | :------: | :-------: |
-| Relay, USB controlled—2 Channel | 019464 | 029099 |
-| Relay, USB controlled—4 Channel | 019465 | 029100 |
-| Relay, USB controlled—8 Channel | 019466 | 029101 |
-
-
-
-
-
-
- Used in a robot, for controlling a stack light, and GPIO for button inputs
-
-
-
----
-
-## DIN Rail Kits {#relay_board_kits}
-
-:::note
-
-Refer to the [DIN Rail](../add-ons/din_rail.mdx) page for related PACS™ Kits, and item numbers of common DIN Rail lengths.
-
-:::
-
-
-
-
-
-| Description | CPR Item |
-| :-------------------------------------------------------------- | :------: |
-| PACS™ kit, including mounting, controls base, and top cap | 027220 |
-| Kit, controls base and top cap | 020711 |
-| Mounting adapter | 020710 |
-| Light Module, Green | 020714 |
-| Light Module, Red | 020715 |
-| Light Module, Amber | 020716 |
-| Light Module, Blue | 020717 |
-| Light Module, White | 020718 |
-| Light Module, Yellow | 020719 |
-| Light Module, Magenta | 020720 |
-
-## Pinout {#stack_light_pinout}
-
-| Pin | Description | Voltage |
-| :-: | :------------------------------------ | :------ |
-| COM | Ground | GND |
-| 1 | Channel 1, lowest module in the stack | +24 VDC |
-| 2 | channel 2 | +24 VDC |
-| 3 | channel 3 | +24 VDC |
-| 4 | channel 4 | +24 VDC |
-| 5 | channel 5 | +24 VDC |
-| 6 | channel 6 | +24 VDC |
-| 7 | channel 7, highest possible module | +24 VDC |
-
----
-
-## Hardware Build
-
-### Parts List
-
-The PACS™ kit for a stack light includes:
-
-| ID | Description | CPR item | Quantity |
-| :-------: | :--------------------------------------------------------- | :-------------------------------------------------: | :------: |
-| 1 | Plate—80 X 80, Attachment Interface | [026914](/assets/pdf/clearpath_robotics_026914.pdf) | 1 |
-| 2 | Stack Light Module, Mounting Adapter—Surface Mount | 020710 | 1 |
-| 3A and 3B | Bundle, Stack Light Module, Controls Base and Top Cap | 020711 | 1 |
-| 4 | Screw, Cap, Socket Head—M4×0.7 X 16, Stainless Steel | 023128 | 2 |
-| 5 | Nut, Hex, Lock, Polymer Insert—M4×0.7 X 5, Stainless Steel | 019899 | 2 |
-| 6 | Spacer, Round—Ø5.3 X Ø8 X 7, Aluminum Alloy | 026612 | 4 |
-| 7 | Screw, Cap, Round Head—M5×0.8 X 16, Stainless Steel | 023257 | 4 |
-
-:::note
-
-Light Modules are not included in the PACS™ parts list since the configuration of modules depends on your specific integration.
-Refer to the listed Light Modules at the top of this page for common modules.
-Refer to [this catalog](/assets/pdf/clearpath_robotics_027220-TDS1.pdf) for all available modules and parts, including strobing lights, and buzzers.
-
-:::
-
-### Instructions
-
-1. Mount the Mounting Adapter (ID 2) to the attachment-plate (ID 1) using the M4 screws (ID 4) and nuts (ID 5).
- Refer to the [attachment-plate's drawing notes](/assets/pdf/clearpath_robotics_026914.pdf) for what holes to use for mounting the stack light.
-2. Place the Controls Base (ID 3A) onto the assembly and twist 10° clockwise to lock it in place.
-3. Make and connect a cable for controlling the stack light's modules.
- Refer to the [Pinout Section](#stack_light_pinout) above for details.
-4. Mount this assembly onto your robot, using the included spacers (ID 6) and screws (ID 7).
-5. Add light modules onto the assembly and twist 10° clockwise to lock them in place.
- This locking connection creates an IP65 weatherproof seal, and completes the electrical connection to the Controls Base.
-6. Place the Top Cap (ID 3B) onto the assembly and twist 10° to lock it in place.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/tower.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/tower.mdx
deleted file mode 100644
index f45fe04db..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/tower.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Tower
-sidebar_position: 10
----
-
-
-
-
-
-
-
-
-
-
-
-
-
-| Description | CPR Item | Manufacturer | Manufacturer Item |
-| :-------------------- | :------: | :---------------------- | :---------------- |
-| Spacer, Ø5.3 X Ø8 X 5 | 027005 | RAF Electronic Hardware | M0594-5-AL |
-| Standoff, 15 mm | 026991 | Wurth Elektronik | 971150581 |
-| Standoff, 35 mm | 026995 | Wurth Elektronik | 971350581 |
-| Standoff, 55 mm | 026999 | Wurth Elektronik | 971550581 |
-| Standoff, 75 mm | 027002 | Wurth Elektronik | 971750581 |
-
-We use the listed standoffs to lift sensors for better viewing angles.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/usb_hub.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/usb_hub.mdx
deleted file mode 100644
index a35b9e145..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/usb_hub.mdx
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: USB Hub
-sidebar_position: 11
----
-
-## Item Numbers
-
-| Description | CPR Item |
-| :----------------------------------------------- | :------------------------------------------------------: |
-| USB 3.0 Hub, 7 port, 9 - 24 VDC | [025440](/assets/pdf/clearpath_robotics_025440-TDS1.pdf) |
-| USB 3.0 Hub, 7 port, 9 - 24 VDC, PACS™ kit | 027642 |
-
----
-
-## Hardware Build
-
-
-
-
- 017642 | USB 3.0 Hub, 7 port, PACS™ kit
-
-
-
-### Parts List
-
-The PACS™ kit for this sensor includes:
-
-| ID | Description | CPR item | Quantity |
-| :-: | :-------------------------------------- | :------------------------------------------------------: | :------: |
-| 1 | Kit, Attachment—80 X 80, DIN Rail | [027881](../add-ons/din_rail.mdx) | 1 |
-| 2 | USB Hub—7 Port, USB 3.0 | [025440](/assets/pdf/clearpath_robotics_025440-TDS1.pdf) | 1 |
-| 3 | Spacer, DIN rail, Locking—35 X 7.5 X 10 | 023649 | 2 |
-
-### Instructions, 5 Port
-
-1. Build the DIN rail assembly. The instructions are listed on the [DIN Rail page](../add-ons/din_rail.mdx)
-2. Mount this assembly onto your robot, using the DIN Rail kit's included spacers and screws.
-3. Remove the USB Hub from its packaging.
- Connect its included DIN Rail bracket to the USB Hub.
-4. Connect the USB Hub assmbly onto the DIN Rail assembly.
-5. Use two DIN Spacers (ID 3) to hold the USB Hub on the DIN Rail.
-6. Make a power cable using the green terminal block connector that was included with the USB Hub.
- There is white lettering on the side of the USB Hub designating +V and -V terminals.
-7. Make sure the robot is off.
- Connect the sensor's cable to the USB Hub, and to the related User Power terminal on the robot:
- - +12 V regulated
- - +12 V unregulated VBAT
- - +24 V regulated
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/wireless_stop_system.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/wireless_stop_system.mdx
deleted file mode 100644
index b511cc27e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/add-ons/wireless_stop_system.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Wireless Stop System
-sidebar_position: 12
----
-
-
-
-### Parts List, Kar-Tech
-
-| ID | Description | CPR Item |
-| :-: | :--------------------------------------------------------- | :-------------------------------------------------: |
-| 1 | Plate—80 X 80, Attachment Interface, Large | [026964](/assets/pdf/clearpath_robotics_026964.pdf) |
-| 2 | Bundle, Wireless Safety Controller—Kartech | 014663 |
-| 3 | Screw, Cap, Round Head—M4×0.7 X 12, Stainless Steel | 023310 |
-| 4 | Nut, Hex, Lock, Polymer Insert—M4×0.7 X 5, Stainless Steel | 019899 |
-| 5 | Spacer, Round—Ø5.3 X Ø8 X 7, Aluminum Alloy | 026612 |
-| 6 | Screw, Cap, Round Head—M5×0.8 X 16, Stainless Steel | 023257 |
-
-### Instructions, Kar-Tech
-
-1. Fasten the Kar-Tech (ID 1) to the attachment-plate (ID 1) using M4 screws (ID 3) and nuts (ID 4).
-2. Mount this assembly onto your robot, using the included spacers (ID 5) and screws (ID 6).
-3. Add a connector to the Kar-Tech's cable.
- Refer to [014663-TDS1](/assets/pdf/clearpath_robotics_014663-TDS1.pdf) for full details of the Kar-Tech component, including pinout.
-
----
-
-## Hardware Build, FORT Robotics Mobility
-
-
-
-
-
-
-
-### Parts List, FORT Robotics Mobility
-
-| ID | Description | CPR Item | Quantity |
-| :-: | :------------------------------------------------- | :-------------------------------------------------: | :------: |
-| 1 | Plate—80 X 80, Attachment Interface, Large | [027110](/assets/pdf/clearpath_robotics_027110.pdf) | 1 |
-| 2 | Bundle, Wireless Safety Controller—FORT Robotics | 025727 | 1 |
-| 3 | Antenna 2.4 GHz | 007198 | 1 |
-| 4 | Screw, Cap, Flat Head—M4×0.7 X 10, Stainless Steel | 023455 | 4 |
-| 5 | Screw, Cap, Flat Head—M5×0.8 X 12, Stainless Steel | 023471 | 4 |
-
-### Instructions, FORT Robotics Mobility
-
-1. Fasten the attachment-plate (ID 1) to the robot using M5 screws (ID 5)
-2. Mount the FORT Robotics component (ID 2) to the attachment-plate (ID 1) using four M4×0.7 screws (ID 4).
-3. Attach the antenna (ID 3) to the FORT (ID 2).
-4. Add a connector to the cable included in the FOR bundle (ID 2).
- Clearpath drawing [025657](/assets/pdf/clearpath_robotics_025657.pdf) shows an example configuration.
- Refer to [015584-TDS2](/assets/pdf/clearpath_robotics_015584-TDS2.pdf) for full details of the FORT component, including pinout.
-5. Connect the cable you just made to the robot's User Power connector, and to your motion-stop loop control wiring.
-6. Connect a USB-mini 2.0 cable between your ROS computer and the FORT Robotics component.
- This cable is not included in the PACS™ kit.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/_category_.json
deleted file mode 100644
index 9d253c7b2..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Computers",
- "position": 2
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/computers.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/computers.mdx
deleted file mode 100644
index eebd526c8..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/computers.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Computers Overview
-sidebar_label: Computers
-sidebar_position: 1
----
-
-
-
-
- Jackal with a water cooled Intel i9 processor and Nvidia 1050
-
-
-
-
-
-Clearpath's robots use ROS or ROS 2, which require the robot to have a computer running an Operating System like Ubuntu.
-We mostly use Mini-ITX computers with Intel Core i3 and i7 processors, but we can run ROS on the major architectures including:
-
-- Intel Core i series
-- arm64 (Nvidia Jetson, and Raspberry Pi)
-
-Clearpath Robotics has preconfigured _Standard_ and _Performance_ computer kits for our robots, but we can make a custom computer to meet your project's requirements.
-
-## Computer Selection Considerations
-
-1. Operating conditions, air temperature
-2. Operating conditions, shock & vibration
-3. Amount of compute required, CPU
-4. Amount of compute required, GPU
-5. Amount of RAM required
-6. Amount of memory storage required
-7. Speed of memory required (for applications with many cameras)
-8. Number of connected sensors, and their data rates
-9. Any software specific considerations that impact hardware:
- - What operating system do you intend to use?
- - Are there kernel drivers for this component?
- - Does this software require a GPU?
- - Does this software require a specific processor architecture?
-10. Can the selected robot power all these devices, and what will the runtime be?
-
-## Computer Selection Process
-
-1. Choose between a consumer-computer and an industrial-computer.
- 1. Operating environment's temperature range.
- Consumer computers are intended for an environment between 0°C - 30°C.
- Most outdoor robots operate in summer environments with hotter ambient air, and have extra heat added to the computer through solar radiation.
- The type of computer and cooling strategy can allow you to use the full compute capability of the computer in these environments.
- 2. Mechanical shock & vibration in your application.
-2. Choose between an Intel or arm64 architecture.
- 1. Amount of compute required for sensor data.
- 2. Amount of compute required for software, such as Autonomy.
- 3. Are you planning to run any software specific to arm64, such as tools in [Nvidia JetPack SDK](https://developer.nvidia.com/embedded/jetpack)?
- 4. Amount of RAM required.
- 5. Number of sensors, and types of connections, and required speeds
- - USB 2
- - USB 3.0 - 3.2
- - Ethernet (100 Mbit/s, 1 Gbit/s, 10 Gbit/s)
- - CAN, and other industrial protocols
- - Serial (RS-232, RS-422, RS-485)
- Some devices may be connected to the computer through Network Switches, Hubs, or USB-converters.
- Some devices like cameras can have a large amount of data, and require a dedicated bus on the computer, so it is best to consider the whole application when choosing the computer.
-3. Amount of hard storage required, and how fast you need to write to this storage.
- Consider what data you are collecting from sensors, and want to store for later use.
- There can be a considerable amount of data from sensors like cameras, so write speeds may be a limiting factor depending on your computer configuration.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/_category_.json
deleted file mode 100644
index 6f92e35d9..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jetson",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/_category_.json
deleted file mode 100644
index ce77a05be..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jetson Hardware",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
deleted file mode 100644
index 9fce60f79..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title: Jetson Hardware
-sidebar_label: Jetson Hardware
-sidebar_position: 1
----
-
-## Installation
-
-Jetson Xavier AGX, Nano, and TX2 can be installed on a variety of platforms.
-Refer to the child pages for the details of the hardware installation.
-
-See also the instructions for
-[installing the Jetson software](../jetson_software.mdx).
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
deleted file mode 100644
index c865d2584..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jetson Nano Hardware",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
deleted file mode 100644
index 3de788cab..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Jetson Nano Hardware in Dingo
-sidebar_label: Dingo
-sidebar_position: 3
----
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Nano hardware in Dingo. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Open up Dingo
-
-Start by removing Dingo's side panels, yellow cover plates, and removing the center channel covers.
-
-
-
-
- Dingo's center channel
-
-
-
-### Step 2: Install the Nano
-
-Dingo includes pre-threaded mounting holes for the Jetson Nano. We recommend using 20mm standoffs to raise the board.
-
-
-
-
- Dingo's computer bay
-
-
-
-Connect the Jetson's power cable to the 5V output from Dingo's MCU.
-
-
-
-
- A Jetson Nano installed inside Dingo
-
-
-
-The Ethernet port on the Nano will eventually need to be connected to the Ethernet port of Dingo's MCU. If you have
-a network switch installed you can connect the MCU and the Nano to the switch. Otherwise leave the MCU disconnected
-for now so that the Nano's Ethernet port can be used for downloading the software from the internet.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
deleted file mode 100644
index 4122bfe98..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Jetson Nano Hardware in Husky A200
-sidebar_label: Husky A200
-sidebar_position: 1
----
-
-import ComponentHuskyComputerRemoval from "/components/husky_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Nano hardware in Husky A200. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the Nano
-
-:::note
-
-Custom mounting brackets are available on
-[GitHub](https://github.com/clearpathrobotics/jetson_setup/raw/melodic/models/JetsonNanoXavierHuskyMount.stl).
-
-:::
-
-1. Print off the mount from above using a 3D printer. A 0.2 mm layer thickness should be sufficient.
-
-2. Add 4X M3 stand-offs to the board mount points. A 6 mm height is recommended.
-
-
-
-
- Installing the standoffs
-
-
-
-3. Use M3 screws to fasten the Nano to the mount.
-
-
-
-
- Fastening the Nano to the mount
-
-
-
-4. Attach the Nano and mount to the two M3 holes opposite the platform serial connector.
-
-
-
-
- Attaching the mount to Husky
-
-
-
-5. Re-attach the power and serial cables from the platform to the Jetson.
-
-
-
- Attaching the cables
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
deleted file mode 100644
index 0c8358e41..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Jetson Nano Hardware in Jackal
-sidebar_label: Jackal
-sidebar_position: 2
----
-
-import ComponentJackalComputerRemoval from "/components/jackal_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Nano hardware in Jackal. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the Nano
-
-:::note
-
-Custom mounting brackets are available on
-[GitHub](https://github.com/clearpathrobotics/jetson_setup/raw/melodic/models/JetsonNanoXavierJackalMount.stl).
-
-:::
-
-1. Print off the mount from above using a 3D printer. A 0.2 mm layer thickness should be sufficient.
-
-2. Add 4X M3 stand-offs to the board mount points. A 6 mm height is recommended.
-
-
-
-
- Installing the standoffs
-
-
-
-3. Use M3 screws to fasten the Nano to the mount.
-
-
-
-
- Fastening the Nano to the mount
-
-
-
-4. Position the Nano with the mount over the rear two PEMs on the tray and
- fasten with M3 screws and washers.
-
-
-
-
- Attaching the mount to Jackal
-
-
-
-5. Make a power cable that connects to the 12 V user
- power (Molex connector) to a barrel connector with center positive. Refer
- to the [Jackal User Manual](../../../../../outdoor_robots/jackal/user_manual_jackal.mdx) for the
- pinout of the user power.
-
- :::warning
-
- Do NOT plug this into the ITX power plug on the power distribution board.
-
- :::
-
-
-
-
- Adding the power connector
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
deleted file mode 100644
index 185ec242f..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jetson TX2 Hardware",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
deleted file mode 100644
index 7316afcac..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx
+++ /dev/null
@@ -1,67 +0,0 @@
----
-title: Jetson TX2 Hardware in Husky A200
-sidebar_label: Husky A200
-sidebar_position: 1
----
-
-import ComponentHuskyComputerRemoval from "/components/husky_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the TX2 hardware in Husky A200. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the TX2
-
-:::note
-
-Custom mounting brackets are available
-[on Github](https://github.com/clearpathrobotics/jetson_setup/raw/noetic/models/JetsonTX2HuskyMount.stl).
-
-:::
-
-1. Download and 3D print the mounts. A 0.2 mm layer thickness should be sufficient.
-
-2. Using 4X M3 bolts, attach the plates inside the Husky platform. On the plates, add 4 M3 stand-offs
- to the board mount points. A 6 mm height is recommended.
-
-
-
-
- Installing the mounting plates
-
-
-
-3. Once the mounts are installed, attach the TX2 onto the mounts using M3 bolts.
-
-4. Take the power cable that powered the ITX computer and plug it into the TX2. Then, attach the serial
- communication cable to the USB port on the TX2. If you have multiple USB peripherals on the robot,
- you may need to use a USB hub.
-
-
-
-
- Installing the cables
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
deleted file mode 100644
index 47e7bc78f..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Jetson TX2 Hardware in Jackal
-sidebar_label: Jackal
-sidebar_position: 2
----
-
-import ComponentJackalComputerRemoval from "/components/jackal_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the TX2 hardware in Jackal. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the TX2
-
-1. Install the Jetson TX2 using M3 screws or the screws removed from the computer. The holes
- will only line up in one orientation.
-2. Plug a USB mini cable from the Jetson to the Jackal MCU board. This is beside where the USB
- header was removed if you had a computer. We recommend using a USB hub to increase the number
- of connected devices.
-
-3. Plug the power switch cable into the power switch header (J6).
-
-4. If you wish to use the antenna cables attached to the Jackal, remove the U.FL connectors from
- the Jetson module and connect the antenna cables.
-
- :::caution
-
- Take your time with this step as the UF.L connectors are fragile. If you wish not to disconnect the UF.L
- cables you can replace the antenna mounts on the Jackal with SMA extensions.
-
- :::
-
-
-
-
- UF.L connectors
-
-
-
-5. Make a power cable that connects to the 12 V user
- power (Molex connector) to a barrel connector with center positive. Refer
- to the [Jackal User Manual](../../../../../outdoor_robots/jackal/user_manual_jackal.mdx) for the
- pinout of the user power.
-
- :::warning
-
- Do NOT plug this into the ITX power plug on the power distribution board.
-
- :::
-
-
-
-
- 12 V user power
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
deleted file mode 100644
index 3a01a438d..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jetson Xavier AGX Hardware",
- "position": 4
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
deleted file mode 100644
index de6f7818b..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Jetson Xavier AGX Hardware in Dingo
-sidebar_label: Dingo
-sidebar_position: 3
----
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Xavier AGX hardware in Dingo. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Open up Dingo
-
-Start by removing Dingo's side panels, yellow cover plates, and removing the center channel covers.
-
-
-
-
- Dingo's center channel
-
-
-
-### Step 2: Install the Xavier
-
-Dingo includes pre-threaded mounting holes for the Jetson Xavier. We recommend using 20 mm standoffs to raise the board.
-
-
-
-
- Dingo's computer bay
-
-
-
-Connect the Jetson's power cable to the 12 V output from Dingo's MCU.
-
-
-
-
-
-
-
-The ethernet port on the Jetson will eventually need to be connected to the ethernet port of Dingo's MCU. If you have
-a network switch installed you can connect the MCU and the Jetson to the switch. Otherwise leave the MCU disconnected
-for now so that the Jetson's ethernet port can be used for downloading the software from the internet.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
deleted file mode 100644
index a7f788326..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Jetson Xavier AGX Hardware in Husky A200
-sidebar_label: Husky A200
-sidebar_position: 1
----
-
-import ComponentHuskyComputerRemoval from "/components/husky_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Xavier AGX hardware in Husky A200. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the Xavier AGX
-
-Custom mounting brackets are available on
-[Github](https://github.com/clearpathrobotics/jetson_setup/raw/melodic/models/JetsonNanoXavierHuskyMount.stl).
-
-1. Print this mount off using a 3D printer. A 0.2 mm layer thickness should be sufficient.
-
-
-
-
- Removing the support feet
-
-
-
-2. Use an allen wrench to remove the support feet from the bottom of the Xavier board by removing the
- M3 bolts. Place the feet on the 3D printed mount.
-
-
-
-
- Removing the support feet
-
-
-
-3. Attach the Xavier to the mount using four M3 x 40 screws through the bottom of the mount in the holes for Xavier.
-
-
-
-
-
- Attaching Xavier to the mount
-
-
-
-4. Attach the Xavier and mount to the two M3 holes opposite the platform serial connector.
-
-5. Re-attach the power and serial cables from the platform to the Xavier.
-
-
-
-
- Attaching the cables
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
deleted file mode 100644
index 9d96b0e1c..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Jetson Xavier AGX Hardware in Jackal
-sidebar_label: Jackal
-sidebar_position: 2
----
-
-import ComponentHuskyComputerRemoval from "/components/husky_remove_miniitx.mdx";
-
-## Installation
-
-:::note
-
-This page outlines the steps for installing the Xavier AGX hardware in Husky. See also
-the instructions for
-[installing the Jetson software](../../jetson_software.mdx).
-
-:::
-
-### Step 1: Remove Mini-ITX Computer
-
-:::note
-
-Skip this step if you don't have an existing computer.
-
-:::
-
-
-
-### Step 2: Install the Xavier AGX
-
-Custom mounting brackets are available on
-[Github](https://github.com/clearpathrobotics/jetson_setup/raw/melodic/models/JetsonNanoXavierJackalMount.stl).
-
-1. Print this mount off using a 3D printer. A 0.2 mm layer thickness should be sufficient.
-
-2. Use an allen wrench to remove the support feet from the bottom of the Xavier board by removing the M3 bolts.
- Place the feet on the 3D printed mount.
-
-3. Attach the Xavier to the mount using four M3x40 screws through the bottom of the mount in the holes for Xavier.
-
-
-
-
-
- Attaching Xavier AGX to the mount
-
-
-
-4. Position the mount with the Xavier over the rear two PEMs on the tray and fasten with M3x6 screws and washers.
-
-
-
-
- Fasten the mount in Jackal
-
-
-
-5. Make a power cable that connects to the 12V user
- power (Molex connector) to a barrel connector with center positive. Refer
- to the [Jackal User Manual](../../../../../outdoor_robots/jackal/user_manual_jackal.mdx) for the
- pinout of the user power.
-
- :::warning
-
- Do NOT plug this into the ITX power plug on the power distribution board.
-
- :::
-
-
-
-
- 12V user power
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_software.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_software.mdx
deleted file mode 100644
index 5b6a8648d..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/jetson/jetson_software.mdx
+++ /dev/null
@@ -1,403 +0,0 @@
----
-title: Jetson Software
-sidebar_label: Jetson Software
-sidebar_position: 3
----
-
-## Software Installation
-
-:::note
-
-This page outlines the steps for installing the Jetson software for a Husky A200, Jackal, or Dingo. See also
-the instructions for installing the Jetson hardware.
-
-- Xavier AGX
- - [Husky A200](jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_husky.mdx)
- - [Jackal](jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_jackal.mdx)
- - [Dingo](jetson_hardware/jetson_xavier_agx_hardware/jetson_xavier_agx_hardware_dingo.mdx)
-- Nano
- - [Husky A200](jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_husky.mdx)
- - [Jackal](jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_jackal.mdx)
- - [Dingo](jetson_hardware/jetson_nano_hardware/jetson_nano_hardware_dingo.mdx)
-- TX2
- - [Husky A200](jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_husky.mdx)
- - [Jackal](jetson_hardware/jetson_tx2_hardware/jetson_tx2_hardware_jackal.mdx)
-
-:::
-
-### Step 1: Put Jetson in Recovery Mode (TX2 and Xavier AGX only)
-
-:::caution
-
-This step is not required for Jetson Nano
-
-:::
-
-Put the Jetson into recovery mode by following these steps:
-
-1. Connect the Jetson to the computer onto which SDK Manager will be installed (see next step) using the provided microUSB cable.
-2. Make sure the Jetson is powered off.
-3. Connect a monitor, mouse, and keyboard to the Jetson. (The mouse is optional, but recommended.
- If you do not have an all-in-one mouse+keyboard you will need to use a small USB hub, as the
- Jetson only has a single USB port.)
-4. Press and hold the REC button.
-5. Press the power button.
-
-### Step 2A: Download and Install Nvidia's SDK Manager (TX2 and Xavier AGX only)
-
-:::caution
-
-This step is not required for Jetson Nano
-
-:::
-
-1. Download the appropriate version of [Nvidia's SDK Manager](https://developer.nvidia.com/nvidia-sdk-manager)
- onto the computer connected to the Jetson.
-
- :::note
-
- SDK Manager is used for installing software on the Jetson from the host computer.
- If using Jetson TX2, only JetPack 4.x is supported and the host computer will need to have Ubuntu 16.04 or
- Ubuntu 18.04 installed. If using Jetson Xavier Nano/AGX, JetPack 5.x is supported and the host computer will need
- to have Ubuntu 18.04 or Ubuntu 20.04 installed.
-
- :::
-
-2. Install the SDK Manager by running the following commands:
-
- ```
- cd
- sudo dpkg -i sdkmanager__amd64.deb
- ```
-
- :::note
- If your system is missing dependencies you may see error messages in the output of the `dpkg` command.
- To resolve these, run `sudo apt-get -f install`.
- :::
-
-3. Login the the SDK Manager using your Nvidia developer credentials.
-
-
-
-
- Nvidia developer login
-
-
-
-4. Specify the Hardware Configuration. You do not need to setup your Host Machine unless you are planning on
- doing Cuda work on your local computer. This can usually be disabled. Under the Target Hardware, make sure
- to choose TX2 or Xavier AGX to match your hardware. Once complete, click "Continue to Step 02".
-
-
-
-
- Selecting Target Hardware (TX2 shown)
-
-
-
-5. Accept the terms. Make sure the Download and Target directories are in locations that you have write-access
- to and that your hard drive has enough space for the files. Click "Continue to Step 03".
-
-
-
-
- Selecting Target Hardware
-
-
-
-6. Enter your sudo password and wait for the SDK manager will download the necessary files and install the image
- on the Jetson.
-
-
-
-
- Entering sudo password
-
-
-
-
-
-
- Download in progress
-
-
-
-### Step 2B: Install Image on SD Card (Nano only)
-
-:::caution
-
-This step is not required for Jetson Xavier AGX or TX2
-
-:::
-
-1. Download the latest version of the
- [Nano SD Image](https://developer.nvidia.com/jetson-nano-sd-card-image).
-
-2. Download the latest version of [Balena Etcher](https://www.balena.io/etcher/).
-
-
-
-
- Download in progress
-
-
-
-3. Use Etcher to flash the image onto your SD card.
-
-4. Install the SD card into the Nano and power up the Nano.
-
-### Step 3: Configure the Installation
-
-1. Make sure to plug a keyboard and monitor into the Jetson. On first boot,
- it will go through the usual Ubuntu setup steps. Accept the Licenses.
-
-
-
-
- Accepting licenses
-
-
-
-2. Choose your language.
-
-
-
-
- Choosing your language
-
-
-
-3. Choose your keyboard layout.
-
-
-
-
- Choosing your keyboard layout
-
-
-
-4. Set your location.
-
-
-
-
- Setting your location
-
-
-
-5. Specify a hostname, username, and password for the machine.
-
- :::note
-
- For compatibility with older versions of the Jetson software, set the username and
- password to `nvidia`. To standardize with other Clearpath Robotics products, set the
- username to `administrator` and the password to `clearpath`.
-
- :::
-
-
-
-
- Specifying your hostname, username, and password
-
-
-
-6. (**Nano only**): If prompted for a partition size, use the default size, which should fill the
- whole SD card. Make sure it matches the maximum possible size, unless you have other plans
- for that space.
-
-
-
-
- Specifying partition size (Nano only)
-
-
-
-7. Wait for the installation to install the remaining standard packages.
-
-
-
-
- Waiting for remaining packages
-
-
-
-8. Once the OS is setup, you will be brought to the desktop.
-
-
-
-
- Post-install desktop
-
-
-
-9. Open a terminal and run `ifconfig` or `ip a` to see the IP address it is using. You will
- need to connect it to network through wireless or ethernet.
-
-
-
-
- Finding the IP address
-
-
-
-### Step 4: Install Extra SDK Components (TX2 and Xavier AGX only)
-
-:::caution
-
-This step is not required for Jetson Nano
-
-:::
-
-1. Back in your host computer, it will be waiting to install the extra SDK components on your Jetson.
- Enter the username, password, and IP address you found above.
-
-
-
-
- Installing SDK components
-
-
-
-2. The install will connenct to the remote Jetson over the network. It will continue the install
- by transferring the files and install them.
-
-
-
-
- Waiting for SDK component installation
-
-
-
-3. You can check the terminal window to see the progress of individual commands. This process will
- take a while, so it can be nice to verify that the process isn't stalled.
-
-
-
-
- Installation terminal view
-
-
-
-4. Once the process is done, you can click FINISH to close the window.
-
-
-
-
- Installation complete
-
-
-
-### Step 5: Configure for Use with your Clearpath Robot
-
-1. Once the OS has been written to the Jetson, log into it and run the following commands to configure
- it for use with your Clearpath robot:
-
- ```
- wget -c https://raw.githubusercontent.com/clearpathrobotics/ros_computer_setup/main/install.sh && bash install.sh
- ```
-
- :::note
-
- If `curl` is not installed on your Jetson by default you can install it by running `sudo apt-get install curl`.
-
- :::
-
-
-
-
- ROS Computer Setup
-
-
-
- These commands will download and install ROS along with the necessary `apt` packages to get your robot up and running.
- Depending on your network speed it may take a long time for everything to install. Reboot the Jetson after these commands
- are done to complete the configuration.
-
-2. When the Jetson starts up again, it should be connected to the robot. To see that the robot is connected by opening a
- terminal and executing `rostopic echo /status`. You should see a 1 Hz message containing the robot's diagnostic
- information.
-
- Your Jetson should now be configured to operate as the robot's main computer.
-
-### Step 6: Pair a PS4 Controller with your Clearpath Robot (Optional)
-
-:::note
-
-This step is optional.
-
-:::
-
-See instructions [here](../../../../ros/installation/controller.mdx#ps4-controller) for how to pair the PS4 controller.
-
-### Step 7: Use Offboard Computer with Jetson (Optional)
-
-:::note
-
-This step is optional.
-
-:::
-
-To use your Offboard Computer (for example laptop) with the Jetson, note the IP address of the Jetson, and install the robot-specific
-desktop packages on the Offboard Computer.
-Refer to the "Installing Offboard Computer Software" section of your robot User Manual for details.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/mini_itx.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/computers/mini_itx.mdx
deleted file mode 100644
index 74a782dde..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/computers/mini_itx.mdx
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Mini ITX
-sidebar_label: Mini ITX
-sidebar_position: 2
----
-
-import ComponentWdSsdCriticalUpdate from "/components/maintenance/wd_ssd_critical_update.mdx";
-
-Mini ITX computers are the default computer option for many Clearpath robots.
-
-:::note
-
-To install and configure software on your Mini ITX computer, see
-[Robot Installation](../../../ros/installation/robot.mdx).
-
-:::
-
-:::note
-
-If you want Clearpath Robotics to integrate sensors on your robot, contact our Sales team
-at \, whether you want to use a new Clearpath Robotics platform,
-or reuse your existing vehicle.
-
-:::
-
-:::note
-
-Contact our Support team at \ if you have any questions.
-
-:::
-
-## Maintenance
-
-
-
-## Troubleshooting
-
-#### Computer will not turn on automatically
-
-We configure the BIOS on our robots computers to boot automatically when they receive power.
-This is typically used for servers and similar industrial computers were they need to automatically restart after a blackout.
-
-To update the BIOS:
-
-1. Connect a monitor and keyboard to the robot's computer.
-2. Turn the computer on, and immediately start pressing the _delete_ key on the robot's keyboard.
- You should be pressing it at least 4 times per second.
-
- :::note
-
- _delete_ is the most common key to enter BIOS, but your computer's motherboard may require a different key to be pressed.
- The startup screen has a note stating what key needs to be pressed, but it passes by quickly, and starts loading the Operating System.
- You can take a video of the monitor to review the information slowly.
-
- :::
-
-3. The monitor should show the BIOS landing page.
- There is a setting that will start the computer automatically.
- Unfortunately, this setting seems to change names with every motherboard.
- It is often in the Power or CPU areas of the BIOS settings.
-4. Save and Reboot after your change the setting to have the computer start with automatic power on.
-
-#### Computer keeps reverting to old BIOS settings
-
-This is often due to a low voltage CMOS battery.
-This is a battery on the computer's motherboard that powers firmware devices, like the computer's clock when the OS is not running.
-The location will change depending on the motherboard, but the battery will look like a silver coin.
-
-To replace it:
-
-1. Shut off the robot.
-2. Use a static grounding strap, so you do not damage the computer.
-3. Use hand tools to disassemble your robot, to get access to the computer.
-4. Open the computer, so you can see the motherboard.
-5. Remove the CMOS battery from the motherboard.
- It is usually held in a spring clip that also makes the electrical connection to the motherboard.
- Some motherboards use a CMOS battery with a pigtail lead, but this is uncommon.
-6. Purchase and install a replacement battery that matches the manufacturer information on the old battery.
- You may find the battery on sites like [Amazon](https://www.amazon.com/), [Digi-Key](https://www.digikey.com/), and [Octopart](https://octopart.com/).
- Contact our Support team if you cannot find a replacement.
-7. Turn on the computer, and reenter your BIOS settings.
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/_category_.json
deleted file mode 100644
index 28c62929d..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Manipulators",
- "position": 4
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/flir_ptu_e46.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/flir_ptu_e46.mdx
deleted file mode 100644
index aed57c19a..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/flir_ptu_e46.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: FLIR PTU E46
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :---------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| PTU E46 | [018807](/assets/pdf/clearpath_robotics_018807-TDS1.pdf) | 028873 | 028872 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :----------------- |
-| Mass, PTU | 1.4 kg |
-| Mass, Payload Maximum | 2.72 kg |
-| Voltage, Minimum | 12 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 24 V |
-| Power, Average | 6 W |
-| Data | Ethernet or RS-232 |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 5 |
-| Operating Temperature, Min | -20 °C |
-| Operating Temperature, Max | 60 °C |
-
----
-
-## Software Bringup
-
-This sensor is not included in the Clearpath Robotics robot package.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com)
-2. [Datasheet](/assets/pdf/clearpath_robotics_018807-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_018807-TDS2.pdf)
-4. [FLIR PTU E46 Website](https://www.flir.com/products/ptu-e46/?vertical=mcs&segment=oem)
-5. [ROS webpage](https://github.com/ros-drivers/flir_ptu)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/kinova_gen3_lite.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/kinova_gen3_lite.mdx
deleted file mode 100644
index 467033bbd..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/kinova_gen3_lite.mdx
+++ /dev/null
@@ -1,187 +0,0 @@
----
-title: Kinova Gen3 Lite
-sidebar_position: 3
----
-
-import KinovaGen3Lite from "/docs_versioned_docs/version-ros2humble/components/yaml/manipulators/kinova_gen3_lite.mdx";
-import Kinova2FLite from "/docs_versioned_docs/version-ros2humble/components/yaml/manipulators/kinova_2f_lite.mdx";
-import Support from "/components/support.mdx";
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item |
-| :-------------------------------- | :------------------------------------------------------: |
-| Kinova Gen3 lite Bundle | [022586](/assets/pdf/clearpath_robotics_022586-TDS2.pdf) |
-| Kinova Gen3 lite, PACS™ kit | 027219 |
-
----
-
-## Specifications
-
-### Overview
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 5.4 kg |
-| Voltage, Minimum | 21 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 24 V |
-| Power, Average | 20 W |
-| Power, Peak | 100 W |
-| Data | Ethernet, 100 Mbit/s |
-| Reach | 760 mm |
-| Payload | 0.5 kg |
-| Speed | 250 mm/s |
-| Range | ±155° |
-| Ingress Protection, Solids | 2 |
-| Ingress Protection, Liquids | 2 |
-| Operating Temperature, Min | 0°C |
-| Operating Temperature, Max | 40°C |
-
-### IP addresses
-
-| Description | IP address |
-| :----------------------------------- | :----------- |
-| Default from Manufacturer, USB - USB | 192.168.1.10 |
-
----
-
-## Hardware Build
-
-### Parts List
-
-The PACS™ kit for this sensor includes:
-
-| ID | Description | CPR Item | Quantity |
-| :-: | :-------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1 | Plate—80 X 80, Attachment Interface | [026914](/assets/pdf/clearpath_robotics_026914.pdf) | 1 |
-| 2 | Manipulator Bundle | [022586](/assets/pdf/clearpath_robotics_022586-TDS1.pdf) | 1 |
-| 3 | Screw, Cap, Round Head—M6×1 X 8, Stainless Steel | 023326 | 4 |
-| 4 | Spacer, Round—Ø5.3 X Ø8 X 7, Aluminum Alloy | 026612 | 4 |
-| 5 | Screw, Cap, Round Head—M5×0.8 X 16, Stainless Steel | 023257 | 4 |
-
-### Instructions
-
-1. Remove the Kinova arm from it's packaging.
-2. There is a _Quick Connect Mounting Knob_ on the bottom of the arm.
- You will need to remove this to mount the arm to the PACS™ bracket.
- Hold the _Mounting Knob's_ square body using an adjustable wrench.
- Then use a hex key to turn the _Mounting Knob's_ screw counerclockwise.
- Then remove the _Mounting Knob_ from the arm.
-3. Refer to the attachment-plate's (ID 1) drawing [026914](/assets/pdf/clearpath_robotics_026914.pdf).
- The notes indicate which holes are for the Kinova arm.
- You will need to enlarge the four holes to Ø6.3 mm with a drill.
-4. Mount the arm (ID 2) to the attachment-plate (ID 1) using four M6×1 screws (ID 3).
-5. Mount this assembly onto your robot, using the included spacers (ID 4) and screws (ID 5).
-
----
-
-## Software Bringup
-
-### ROS 2 Configuration
-This manipulator is included in the Clearpath Robotics descriptino and robot package that is installed on all of our robots.
-This allows you to add or remove manipulator from your robot's software configuration by modying the [robot configuration yaml](../../../ros/config/yaml/manipulators.mdx).
-
-
-
-
-
-### Networking, with netplan
-
-The _Kinova Gen3 lite_ does not let you change its static IP address.
-Its address is always _192.168.1.10._ when you connect using a USB - USB cable.
-
-You will need to extend the network bridge to the _192.168.1.x_ subnet to interface with the _Kinova Gen3 lite_ arm.
-
-Open the netplan configuration file with `/etc/netplan/50-clearpath-bridge.yaml`.
-You will be adding a bridge*usb section to the file, and an additional \_192.168.1.1/24* address to the network bridge.
-Your file should look like this:
-
-```
-
-network:
- version: 2
- renderer: networkd
- ethernets:
- bridge_en:
- dhcp4: no
- dhcp6: no
- match:
- name: en*
- bridge_eth:
- dhcp4: no
- dhcp6: no
- match:
- name: eth*
- bridge_usb:
- dhcp4: no
- dhcp6: no
- match:
- name: usb*
- bridges:
- br0:
- dhcp4: yes
- dhcp6: no
- interfaces: [bridge_en, bridge_eth, bridge_usb]
- addresses:
- - 192.168.131.1/24
- - 192.168.1.1/24
-```
-
-Close and save the file be pressing `ctrl + x`, then typing `y`, and pressing `Enter`.
-
-Now apply your new netplan changes by running `sudo netplan apply`.
-
-You can test the netplan settings by pinging the robot's computer, and pinging the Kinova arm:
-
-```
-ping 192.168.131.1
-ping 192.168.1.10
-```
-
-:::tip
-
-If you cannot ping the computer or arm, try rebooting and replugging the Kinoca Gen3 lite arm before reviewing your installation steps.
-
-:::
-
----
-
-## Troubleshooting
-
-#### Arm is not turning on
-
-1. Turn off the robot.
-2. Remove the Kinova's circular power connector.
-3. Turn the robot back on.
-4. Use a multimeter to check that the voltage is 24 V between:
- - Position 2 and Position 3
- - Position 5 and Position 8
-5. If you are not reading 24 V, then:
- - An upstream connector may not be fully seated.
- - A fuse may be blown.
- - A power supply may have failed.
-
-### If the Issue Persists
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/manipulators/products/gen3-lite)
-2. [Datasheet](/assets/pdf/clearpath_robotics_022586-TDS1.pdf)
-3. [Installation Guide](/assets/pdf/clearpath_robotics_022586-TDS3.pdf)
-4. [User Manual](/assets/pdf/clearpath_robotics_022586-TDS2.pdf)
-5. [Kinova Website](https://www.kinovarobotics.com/product/gen3-lite-robots)
-6. [ROS webpage](https://github.com/Kinovarobotics/ros_kortex)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/manipulators.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/manipulators.mdx
deleted file mode 100644
index 62e08fcf2..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/manipulators/manipulators.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Manipulators Overview
-sidebar_label: Manipulators
-sidebar_position: 1
----
-
-
-
----
-
-These pages outline the hardware and software steps required to get manipulators installed on your Clearpath robot.
-This documentation should be considered a quick reference, rather than a complete technical data package from the manipulator's Original Equipment Manufacturer.
-
-Also note that we have only listed the documentation of our most commonly used manipulators.
-
-We suggest you:
-
-1. Review our documentation of the manipulators related to your robot integration.
-2. Review the related Further Reading section.
-3. If you are planning to purchase a manipulator, consider visiting our [Component Store](https://store.clearpathrobotics.com/).
-4. If you want Clearpath Robotics to integrate sensors on your robot, contact our Sales team at \, whether you want to use a new Clearpath Robotics platform, or reuse your existing vehicle.
-5. Contact our Support team at \ if you have any questions.
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/pacs.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/pacs.mdx
deleted file mode 100644
index a56f68135..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/pacs.mdx
+++ /dev/null
@@ -1,159 +0,0 @@
----
-title: PACS™
-sidebar_label: PACS™
-sidebar_position: 5
----
-
-import Admonition from "@theme/Admonition";
-
-
-
-
-
- A Dingo-O with many M5×0.8 threaded holes on its full-riser. These holes are aligned with M5×0.8 mounting holes on the lower plate.
-
-
-
-
-## Overview
-
-The Platform Attachment Configuration System (PACS™) is a Clearpath Robotics standard for adding components to a robot.
-Our robots have mounting plates with a 80 mm X 80 mm grid of M5×0.8 threaded holes.
-This allows us to add sensors and attachments using adapter plates.
-The _Parts Lists_ in our [Sensors pages](sensors/sensors.mdx) include these 80 mm X 80 mm brackets.
-Some example brackets are also detailed in the [Common PACS™ Items section](#pacs_common_pacs_items_for_all_robots) below.
-
-
-
-
- A Husky configured with many sensors and accessories using PACS™ brackets.
-
-
-
-
-
-
-
- A Husky top plate, with PACS™ hardpoint A01 in the front-left of the robot, and G08 in the back-right
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :---------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Axis F1035-E sensor | [020068](/assets/pdf/clearpath_robotics_020068-TDS1.pdf) | 027105 | 027212 |
-| Axis F34 controller hub | [020442](/assets/pdf/clearpath_robotics_020442-TDS1.pdf) | 027634 | 027633 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :---------------------------------- | :------------------- |
-| Mass, Camera | 96 g |
-| Mass, Hub | 238 g |
-| Voltage, Minimum | PoE, 8 V |
-| Voltage, Maximum | PoE, 28 V |
-| Voltage, Sensor | PoE, 24 V |
-| Power, Average | 12.6 W |
-| Data | Ethernet, 100 Mbit/s |
-| View, Horizontal | 194° |
-| View, Vertical | 113° |
-| Ingress Protection, Solids, Camera | 6 |
-| Ingress Protection, Liquids, Camera | 7 |
-| Ingress Protection, Solids, Hub | 2 |
-| Ingress Protection, Liquids, Hub | 0 |
-| Operating Temperature, Min | 0°C |
-| Operating Temperature, Max | 40°C |
-
----
-
-## Software Bringup
-
-This sensor is not currently included in the Clearpath Robotics robot package but may be in the future.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Datasheet, Camera](/assets/pdf/clearpath_robotics_020068-TDS1.pdf)
-2. [Datesheet, Hub](/assets/pdf/clearpath_robotics_020442-TDS1.pdf)
-3. [Dimensions, Camera](/assets/pdf/clearpath_robotics_020068-TDS2.pdf)
-4. [Dimensions, Hub](/assets/pdf/clearpath_robotics_020442-TDS2.pdf)
-5. [User Manual](/assets/pdf/clearpath_robotics_020442-TDS3.pdf)
-6. [Axis website](https://www.axis.com/products/axis-f1035-e-sensor-unit)
-7. [ROS webpage](http://wiki.ros.org/axis_camera)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_m5525_e.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_m5525_e.mdx
deleted file mode 100644
index cfb30a20e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_m5525_e.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Axis M5525-E
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/axis_camera.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------------ | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Axis M5525-E sensor | [006758](/assets/pdf/clearpath_robotics_006758-TDS1.pdf) | 027106 | 027225 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass, Camera | 1.1 kg |
-| Voltage, Minimum | PoE, 20 V |
-| Voltage, Maximum | PoE, 28 V |
-| Voltage, Sensor | PoE, 24 V |
-| Power, Average | 6.6 W |
-| Data | Ethernet, 100 Mbit/s |
-| View, Horizontal | 360° |
-| View, Vertical | 0° - 90° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 6 |
-| Operating Temperature, Min | -10°C |
-| Operating Temperature, Max | 50°C |
-
----
-
-## Software Bringup
-
-This sensor is not currently included in the Clearpath Robotics robot package but may be in the future.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Datasheet](/assets/pdf/clearpath_robotics_006758-TDS1.pdf)
-2. [Dimensions](/assets/pdf/clearpath_robotics_006758-TDS3.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_006758-TDS2.pdf)
-4. [Axis website](https://www.axis.com/products/axis-m5525-e)
-5. [ROS webpage](http://wiki.ros.org/axis_camera)
-6. [ROS tutorial](http://wiki.ros.org/axis_camera/Tutorials/SettingUpAxisNetworkCamera)
-7. [GitHub](https://github.com/ros-drivers/axis_camera)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_q6225_le.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_q6225_le.mdx
deleted file mode 100644
index 98cc9ac80..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/axis_q6225_le.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: Axis Q6225-LE
-sidebar_position: 3
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/axis_camera.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------------ | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Axis Q62 sensor | 030647 | n/a | n/a |
-
----
-
-## Specifications
-
-### M5525-E
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass, Camera | 8.7kg |
-| Voltage, Minimum | PoE, 20 V |
-| Voltage, Maximum | PoE, 28 V |
-| Voltage, Sensor | PoE, 24 V |
-| Power, Average | 16W |
-| Data | Ethernet, 100Mbit/s |
-| View, Horizontal | 68.3° - 2.2° |
-| View, Vertical | 37° - 1.3° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 6 |
-| Operating Temperature, Min | -50°C |
-| Operating Temperature, Max | 50°C |
-
----
-
-## Software Bringup
-
-This sensor is not currently included in the Clearpath Robotics robot package but may be in the future.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Datasheet](/assets/pdf/clearpath_robotics_030647-TDS1.pdf)
-2. [Axis website](https://www.axis.com/products/axis-q6225-le)
-3. [ROS webpage](http://wiki.ros.org/axis_camera)
-4. [ROS tutorial](http://wiki.ros.org/axis_camera/Tutorials/SettingUpAxisNetworkCamera)
-5. [GitHub](https://github.com/ros-drivers/axis_camera)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_blackfly_s.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_blackfly_s.mdx
deleted file mode 100644
index 5dce22601..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_blackfly_s.mdx
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: FLIR Blackfly S
-sidebar_position: 4
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/flir_blackfly.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------------- | :----------: | :-------: | :------------------------------: |
-| FLIR Blackfly sensor | Many options | 027118 | 027218 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :------------------------- | :--------------------------------- |
-| Mass, Camera | 53 g |
-| Voltage, Minimum | 8 V or USB |
-| Voltage, Maximum | 24 V or USB |
-| Power, Average | 4.2 W |
-| Data | GigE or USB3 |
-| Resolution | 0.4 - 24.5 MP (depending on model) |
-| Frame Rate | 15 - 552 FPS |
-| Operating Temperature, Min | 0°C |
-| Operating Temperature, Max | 50°C |
-
----
-
-## Software Bringup
-
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the
-[robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/vision/products/blackfly-s)
-2. [FLIR website](https://www.flir.ca/products/blackfly-s-gige/)
-3. [ROS webpage](http://wiki.ros.org/spinnaker_sdk_camera_driver)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_ladybug5p.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_ladybug5p.mdx
deleted file mode 100644
index 0a172c2e6..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/flir_ladybug5p.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: FLIR Ladybug5+
-sidebar_position: 5
----
-
-import Support from "/components/support.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------- | :------: | :-------: | :------------------------------: |
-| FLIR Ladybug5+ sensor | 017245 | 028894 | 028893 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :--------------------------- |
-| Mass, Camera | 3000 g |
-| Voltage, Minimum | 12 V |
-| Voltage, Maximum | 24 V |
-| Power, Average | 13 W |
-| Data | USB 3.1 |
-| Resolution | 30 MP (5 MP X 6 sensors) |
-| Frame Rate | 30 FPS @ 8k 60 FPS @ 4k |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 5 |
-| Operating Temperature, Min | -20 °C |
-| Operating Temperature, Max | 50 °C |
-
----
-
-## Software Bringup
-
-This sensor is not included in the Clearpath Robotics robot package.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
-:::note
-
-This camera does not have an official ROS driver.
-Clearpath checks that camera's data is being received on the robot's computer by using FLIR's [Software Development Kit](https://www.flir.com/products/ladybug-sdk/)
-
-:::
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/vision/products/ladybug-5p)
-2. [Datasheet](/assets/pdf/clearpath_robotics_017245-TDS1.pdf)
-3. [Datasheet](/assets/pdf/clearpath_robotics_017245-TDS2.pdf)
-4. [Dimensions](/assets/pdf/clearpath_robotics_017245-TDS4.pdf)
-5. [User Manual](/assets/pdf/clearpath_robotics_017245-TDS3.pdf)
-6. [FLIR website](https://www.flir.com/products/ladybug5plus/)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/luxonis_oakd.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/luxonis_oakd.mdx
deleted file mode 100644
index 69b75aba1..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/luxonis_oakd.mdx
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Luxonis OAK-D
-sidebar_position: 6
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/luxonis_oakd.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Luxonis OAK-D Pro | 025961 | | |
-| Luxonis OAK-D Lite | 025963 | | |
-| Luxonis OAK-D Pro W PoE | 028065 | | 032195 |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](hhttps://store.clearpathrobotics.com/collections/vendors?q=Luxonis)
-2. [Luxonis Website](https://luxonis.com/)
-3. [ROS driver](https://github.com/luxonis/depthai-ros/)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/occam_omni_60.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/occam_omni_60.mdx
deleted file mode 100644
index 9b8b2eb87..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/occam_omni_60.mdx
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Occam Omni 60
-sidebar_position: 7
----
-
-import Support from "/components/support.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Occam Omni 60 sensor, colour | [019645](/assets/pdf/clearpath_robotics_019645-TDS1.pdf) | 027102 | 027211 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :----------- |
-| Mass | 377 g |
-| Voltage, Minimum | 4.75 VDC |
-| Voltage, Maximum | 5.25 V |
-| Voltage, Sensor | USB or 5 VDC |
-| Power, Average | 2 W |
-| Data | USB 3.0 |
-| View, Horizontal | 360° |
-| View, Vertical | 58° |
-| Ingress Protection, Solids | 3 |
-| Ingress Protection, Liquids | 0 |
-
-## Software Bringup
-
-This sensor is not included in the Clearpath Robotics robot package.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Dimensions](/assets/pdf/clearpath_robotics_019645-TDS2.pdf)
-2. [User Manual](/assets/pdf/clearpath_robotics_019645-TDS3.pdf)
-3. [Occam Website](http://occamvisiongroup.com/product/omni-60-omnidirectional-camera/)
-4. [ROS webpage](http://wiki.ros.org/occam_vision_group_stereo-camera#ROS_SDK)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/realsense_d435.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/realsense_d435.mdx
deleted file mode 100644
index d5774744e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/realsense_d435.mdx
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: RealSense D435
-sidebar_position: 8
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/intel_realsense.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Intel RealSense D435 sensor | [017103](/assets/pdf/clearpath_robotics_017103-TDS1.pdf) | 026869 | 027208 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------ |
-| Mass | 75 g |
-| Voltage, Minimum | 4.75 V |
-| Voltage, Maximum | 5.25 V |
-| Voltage, Sensor | USB ( 5 VDC ) |
-| Power, Maximum | 3.5 W |
-| Data | USB 3.0 |
-| Range, Minimum | 0.2 m |
-| Range, Maximum | 3 m |
-| View, Horizontal | 69° at 2 m |
-| View, Vertical | 42° at 2 m |
-| Ingress Protection, Solids | 3 |
-| Ingress Protection, Liquids | 0 |
-| Operating Temperature, Min | 0 °C |
-| Operating Temperature, Max | 35 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/vision/products/intel-realsense-d435)
-2. [Datasheet](/assets/pdf/clearpath_robotics_017103-TDS1.pdf)
-3. [Dimensions](/assets/pdf/clearpath_robotics_017103-TDS3.pdf)
-4. [User Manual](/assets/pdf/clearpath_robotics_017103-TDS2.pdf)
-5. [RealSense Website](https://www.intelrealsense.com/depth-camera-d435/)
-6. [ROS webpage](http://wiki.ros.org/RealSense)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
deleted file mode 100644
index 71ddcb862..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/cameras/stereolabs_zed_2.mdx
+++ /dev/null
@@ -1,70 +0,0 @@
----
-title: Stereolabs Zed 2
-sidebar_position: 9
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/stereolabs_zed.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------ | :------------------------------------------------------: | :-------: | :------------------------------: |
-| ZED 2 sensor | [023611](/assets/pdf/clearpath_robotics_023611-TDS1.pdf) | 028960 | 028959 |
-| ZED 2i sensor | [025844](/assets/pdf/clearpath_robotics_025844-TDS1.pdf) | 026872 | 027210 |
-
----
-
-## Specifications
-
-| Description | Value, ZED 2 | Value, ZED 2i |
-| :-------------------------- | :------------------- | :------------ |
-| Mass | 166 g | 166 g |
-| Voltage, Minimum | 4.75 V | 4.75 V |
-| Voltage, Maximum | 5.25 V | 5.25 V |
-| Voltage, Sensor | USB (5 VDC) | USB (5 VDC) |
-| Power, Average | 1.9 W | 1.9 W |
-| Data | USB 3.0 | USB 3.0 |
-| Range, Minimum | 0.3 m | 0.2 m |
-| Range, Maximum | 20 m | 20 m |
-| View, Horizontal | 110° | 110° |
-| View, Vertical | 70° | 70° |
-| Ingress Protection, Solids | Unknown ( assume 4 ) | 6 |
-| Ingress Protection, Liquids | Unknown ( assume 0 ) | 6 |
-| Operating Temperature, Min | -10 °C | -10 °C |
-| Operating Temperature, Max | 45 °C | 45 °C |
-
----
-
-## Software Bringup
-
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Datasheet, ZED 2](/assets/pdf/clearpath_robotics_023611-TDS1.pdf)
-2. [Dimensions, ZED 2](/assets/pdf/clearpath_robotics_023611-TDS2.pdf)
-3. [Datasheet, ZED 2i](/assets/pdf/clearpath_robotics_025844-TDS1.pdf)
-4. [Dimensions, ZED 2i](/assets/pdf/clearpath_robotics_025844-TDS2.pdf)
-5. [Stereolabs ZED Website](https://www.stereolabs.com)
-6. [ROS webpage](http://wiki.ros.org/zed-ros-wrapper)
-7. [ROS turorial](https://www.stereolabs.com/docs/ros/)
-8. [GitHub](https://github.com/stereolabs/zed-ros-wrapper)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/_category_.json
deleted file mode 100644
index 947de28a6..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "GPS",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/garmin_gps_18x.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/garmin_gps_18x.mdx
deleted file mode 100644
index 8df082fc1..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/garmin_gps_18x.mdx
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Garmin GPS 18x
-sidebar_position: 1
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/garmin_18x.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Garmin GPS 18x sensor, 5 Hz | [001893](/assets/pdf/clearpath_robotics_001893-TDS1.pdf) | 028876 | 028875 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :--------------------------------------------------------------------------------------------------------- | :------------------------------------------------------ |
-| Mass | 165 kg |
-| Voltage, Minimum | 4 V |
-| Voltage, Maximum | 5.5 V |
-| Voltage, Sensor | 5 V |
-| Power, Average | 0.5 W |
-| Data | TIA-232-F ( RS-232 ) Default setting is 19200 baud |
-| View, Vertical | Unknown |
-| Position Accuracy | 15 m |
-| Position Accuracy RTK (requires a [Base Station](../../add-ons/base_station.mdx) or a positioning-service) | Unknown |
-| Ingress Protection, Solids | Unknown ( assume 6 ) |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -30 °C |
-| Operating Temperature, Max | 80 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/gps)
-2. [User Manual](/assets/pdf/clearpath_robotics_001893-TDS1.pdf)
-3. [Swift Navigation Website](https://www.garmin.com/en-CA/p/13195)
-4. [ROS webpage](https://github.com/ros-drivers/nmea_navsat_driver)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/microstrain_gq7.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/microstrain_gq7.mdx
deleted file mode 100644
index 85207dd6b..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/microstrain_gq7.mdx
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: MicroStrain GQ7
-sidebar_position: 3
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/microstrain_gq7.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| MicroStrain GQ7 | N/A | N/A | N/A |
-
----
-
-## Specifications
-
-| Description | Value |
-| :--------------------------------------------------------------------------------------------------------- | :------------------------------------------------------ |
-| Mass | 78 g |
-| Voltage, Minimum | 4.2 V |
-| Voltage, Maximum | 16 V |
-| Voltage, Sensor | 5 V or 12 V |
-| Power, Average | 2.0 W |
-| Data | USB or RS-232 Default setting is 115200 baud |
-| View, Vertical | Unknown |
-| Position Accuracy | 1.25 m horizontal 2 m vertical |
-| Position Accuracy RTK (requires a [Base Station](../../add-ons/base_station.mdx) or a positioning-service) | 2 cm |
-| Ingress Protection, Solids | 4 |
-| Ingress Protection, Liquids | None |
-| Operating Temperature, Min | -40 °C |
-| Operating Temperature, Max | 85 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
-#### Antenna Offsets
-
-The GQ7 needs to have it's antenna offsets properly configured in order to get optimal position and orientation estimates. The `microstrain_inertial_driver` makes this easy to do,
-and allows multiple ways to accomplish this.
-
-##### From tf tree
-
-The `microstrain_inertial_driver` can look up the location of the antennas from the transform tree as long as it is configured to look for the correct frames.
-One can configure antenna offsets to be looked up from the transform tree by including the following parameters
-
-```yaml
-gps:
- - model: microstrain_gq7
- ...
- ros_parameters:
- microstrain_inertial_driver:
- gnss1_antenna_offset_source : 2
- gnss1_frame_id : "right_antenna_link"
- gnss2_antenna_offset_source : 2
- gnss2_frame_id : "left_antenna_link"
-```
-
-A more complete example of configuring the GQ7 to look up the locations of the antennas from the transform tree, and setting up the antennas in the robot.yaml can be found
-[here](https://github.com/clearpathrobotics/clearpath_config/tree/main/clearpath_config/sample/j100/j100_microstrain_gq7.yaml)
-
-##### Manually
-
-This method is not recommended for use with clearpath robots as the `robot.yaml` makes it easy to define GNSS antennas in your robot description, but it is the quickest way to get started.
-One can configure antenna offsets manually by including the following parameters:
-
-**IMPORTANT**: When manually configuring the antenna offsets, the measurements will be in the MicroStrain vehicle frame. See
-[this wiki page](https://wiki.ros.org/microstrain_inertial_driver/use_enu_frame#different_frames) for more information.
-
-```yaml
-gps:
- - model: microstrain_gq7
- ...
- ros_parameters:
- microstrain_inertial_driver:
- gnss1_antenna_offset_source : 1
- gnss1_antenna_offset : [0.0, 0.7, -1.0] # x, y, z in meters
- gnss2_antenna_offset_source : 1
- gnss2_antenna_offset : [0.0, -0.7, -1.0] # x, y, z in meters
-```
-
-#### Transforms
-
-In order to integrate more easily with existing ROS tools such as RViz and Nav2, the `microstrain_inertial_driver` will publish several transforms.
-
-The default behavior of the device when used in a clearpath robot is to publish the global position of the `odom` frame relative to the first valid fix received by the device,
-but it can be configured to publish the global position of a different frame, or no frames at all.
-For more information on the transforms published and how to configure them, see the [transforms](https://wiki.ros.org/microstrain_inertial_driver/transforms)
-page of the `microstrain_inertial_driver` wiki.
-
-
----
-
-## Troubleshooting
-
-
-
-For issues directly related to the `microstrain_inertial_driver` or the GQ7, please open an issue on [GitHub](https://github.com/LORD-MicroStrain/microstrain_inertial/issues/new/choose)
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/gnss-ins)
-2. [GQ7 User Manual](https://files.microstrain.com/GQ7+User+Manual/Home.htm)
-3. [GQ7 Webpage](https://www.microstrain.com/inertial-sensors/3dm-gq7)
-4. [microstrain_inertial_driver wiki](https://wiki.ros.org/microstrain_inertial_driver)
-5. [microstrain_inertial_description wiki](https://wiki.ros.org/microstrain_inertial_description)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/swift_navigation_duro.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/swift_navigation_duro.mdx
deleted file mode 100644
index 8577634af..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/gps/swift_navigation_duro.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Swift Navigation Duro
-sidebar_position: 2
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/swiftnav_duro.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :------------------------------------ | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Swift Navigation Duro sensor | [015822](/assets/pdf/clearpath_robotics_015822-TDS1.pdf) | 027107 | 027213 |
-| Swift Navigation Duro inertial sensor | 018151 | 027108 | 027214 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :--------------------------------------------------------------------------------------------------------- | :------------------- |
-| Mass | 0.8 kg |
-| Voltage, Minimum | 10 V |
-| Voltage, Maximum | 35 V |
-| Voltage, Sensor | 12 V or 24 V |
-| Power, Average | 5 W |
-| Data | Ethernet, 100 Mbit/s |
-| View, Vertical | ±60° from vertical |
-| Position Accuracy | 2.5 m |
-| Position Accuracy RTK (requires a [Base Station](../../add-ons/base_station.mdx) or a positioning-service) | 0.01 m |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -40 °C |
-| Operating Temperature, Max | 75 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/gps/products/duro)
-2. [Datasheet](/assets/pdf/clearpath_robotics_015822-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_015822-TDS2.pdf)
-4. [Swift Navigation Website](https://www.swiftnav.com/duro)
-5. [ROS webpage](http://wiki.ros.org/swiftnav_ros)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/_category_.json
deleted file mode 100644
index 087a345d3..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/imu/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "IMU",
- "position": 4
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/_category_.json
deleted file mode 100644
index 83f246104..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "2D Lidar",
- "position": 5
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
deleted file mode 100644
index 19326cc91..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_2d/hokuyo_ust30_lx.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Hokuyo UST30-LX
-sidebar_position: 3
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/hokuyo_ust.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Hokuyo UST30-LX sensor | [027584](/assets/pdf/clearpath_robotics_027584-TDS1.pdf) | 029015 | 029014 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 0.13 kg |
-| Voltage, Minimum | 10 V |
-| Voltage, Maximum | 30 V |
-| Voltage, Sensor | 12 V or 24 V |
-| Power, Average | 3.6 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.06 m |
-| Range, Maximum | 30 m |
-| Range, Accuracy | ± 40 mm |
-| View, Horizontal | 270 ° |
-| Resolution, Horizontal | 0.25 ° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -30 °C |
-| Operating Temperature, Max | 50 °C |
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/2dlidar)
-2. [Datasheet](/assets/pdf/clearpath_robotics_027584-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_027584-TDS2.pdf)
-4. [Hokuyo Website](https://www.hokuyo-aut.jp/search/single.php?serial=233#download)
-5. [ROS webpage](http://wiki.ros.org/urg_node)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/_category_.json b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/_category_.json
deleted file mode 100644
index ffc1a94b7..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "3D Lidar",
- "position": 6
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/ouster.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/ouster.mdx
deleted file mode 100644
index d2144fab5..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/ouster.mdx
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Ouster
-sidebar_position: 5
----
-
-import Support from "/components/support.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :---------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Sensor, Ouster OS0-32, gen 7 | | | |
-| Sensor, Ouster OS0-64, gen 7 | [028738](/assets/pdf/clearpath_robotics_028738-TDS1.pdf) | 028861 | 028851 |
-| Sensor, Ouster OS0-128, gen 7 | [028740](/assets/pdf/clearpath_robotics_028740-TDS1.pdf) | 028862 | 028852 |
-| Sensor, Ouster OS1-32, gen 7 | [028848](/assets/pdf/clearpath_robotics_028848-TDS1.pdf) | 028863 | 028853 |
-| Sensor, Ouster OS1-64, gen 7 | [028742](/assets/pdf/clearpath_robotics_028742-TDS1.pdf) | 028864 | 028854 |
-| Sensor, Ouster OS1-128, gen 7 | [028745](/assets/pdf/clearpath_robotics_028745-TDS1.pdf) | 028865 | 028855 |
-| Sensor, Ouster OS2-32, gen 7 | [028849](/assets/pdf/clearpath_robotics_028849-TDS1.pdf) | 028866 | 028856 |
-| Sensor, Ouster OS2-64, gen 7 | [028747](/assets/pdf/clearpath_robotics_028747-TDS1.pdf) | 028867 | 028857 |
-| Sensor, Ouster OS2-128, gen 7 | [028749](/assets/pdf/clearpath_robotics_028749-TDS1.pdf) | 028868 | 028858 |
-
----
-
-## Specifications
-
-| Description | Value, OS0 | Value, OS1 | Value, OS2 |
-| :--------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Mass | 447 g | 447 g | 1100 g |
-| Voltage, Minimum | 9 V | 9 V | 9 V |
-| Voltage, Maximum | 34 V | 34 V | 34 V |
-| Voltage, Sensor | 12 V or 24 V | 12 V or 24 V | 12 V or 24 V |
-| Power, Average | 17 W | 17 W | 21 W |
-| Data |
**OS0-32** Ethernet, 65.6 Mbit/s
**OS0-64** Ethernet, 128.5 Mbit/s
**OS0-128** Ethernet 254.3 Mbit/s
|
**OS0-32** Ethernet, 65.6 Mbit/s
**OS0-64** Ethernet, 128.5 Mbit/s
**OS0-128** Ethernet 254.3 Mbit/s
|
**OS0-32** Ethernet, 65.6 Mbit/s
**OS0-64** Ethernet, 128.5 Mbit/s
**OS0-128** Ethernet 254.3 Mbit/s
|
-| Range, Minimum | 0.3 m | 0.3 m | 1.0 m |
-| Range, Maximum ( 10% reflectivity) | 15 m | 45 m | 80 m |
-| Range, Maximum ( 80% reflectivity) | 45 m | 100 m | 210 m |
-| Range, Accuracy | ± 3 cm | ± 3 cm | ± 3 cm |
-| View, Horizontal | 360° | 360° | 360° |
-| View, Vertical | ± 45° | ± 22.5° | ± 11.25° |
-| Resolution, Horizontal | Configurable
0.7°
0.35°
0.18°
| Configurable
0.7°
0.35°
0.18°
| Configurable
0.7°
0.35°
0.18°
|
-| Resolution, Vertical |
**OS0-32** 2.8°
**OS0-64** 1.4°
**OS0-128** 0.7°
|
**OS0-32** 1.4°
**OS0-64** 0.7°
**OS0-128** 0.35°
|
**OS0-32** 0.7°
**OS0-64** 0.35°
**OS0-128** 0.18°
|
-| Ingress Protection, Solids | 6 | 6 | 6 |
-| Ingress Protection, Liquids | 8 | 8 | 8 |
-| Operating Temperature, Min | -40 °C | -40 °C | -20 °C |
-| Operating Temperature, Max | 60 °C | 60 °C | 60 °C |
-
----
-
-## Software Bringup
-
-This sensor is not included in the Clearpath Robotics robot package.
-If you purchased this sensor with your Clearpath robot, we will install the necessary ROS packages and configuration details on the robot's computer.
-
-Refer to this page's Further Reading section for more details.
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/3d-lidar)
-2. [OS0, Datasheet](/assets/pdf/clearpath_robotics_028738-TDS1.pdf)
-3. [OS0, Manual](/assets/pdf/clearpath_robotics_028738-TDS2.pdf)
-4. [OS0, Drawing](/assets/pdf/clearpath_robotics_028738-TDS3.pdf)
-5. [OS1, Datasheet](/assets/pdf/clearpath_robotics_028848-TDS1.pdf)
-6. [OS1, Manual](/assets/pdf/clearpath_robotics_028848-TDS2.pdf)
-7. [OS1, Drawing](/assets/pdf/clearpath_robotics_028848-TDS3.pdf)
-8. [OS2, Datasheet](/assets/pdf/clearpath_robotics_028849-TDS1.pdf)
-9. [OS2, Manual](/assets/pdf/clearpath_robotics_028849-TDS2.pdf)
-10. [OS2, Drawing](/assets/pdf/clearpath_robotics_028849-TDS3.pdf)
-11. [Ouster website](https://ouster.com/)
-12. [ROS GitHub](https://github.com/ouster-lidar/ouster-ros)
-13. [ROS tutorial](https://static.ouster.dev/sdk-docs/ros/index.html)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
deleted file mode 100644
index f0f02177e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck hi_res.mdx
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Velodyne Hi-Res
-sidebar_position: 3
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/velodyne_lidar.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Velodyne Puck sensor | [013688](/assets/pdf/clearpath_robotics_029029-TDS1.pdf) | — | — |
-| Velodyne Puck sensor, with M12 connector | [029029](/assets/pdf/clearpath_robotics_029029-TDS1.pdf) | 029032 | 029031 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 830 g |
-| Voltage, Minimum | 9 V |
-| Voltage, Maximum | 18 V |
-| Voltage, Sensor | 12 V |
-| Power, Average | 8 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.9 m |
-| Range, Maximum | 100 m |
-| Range, Accuracy | ±3 cm |
-| View, Horizontal | 360° |
-| View, Vertical | ±10° |
-| Resolution, Horizontal | 0.4° |
-| Resolution, Vertical | 1.33° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -10 °C |
-| Operating Temperature, Max | 60 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/3d-lidar/products/puck-hi-res)
-2. [Datasheet](/assets/pdf/clearpath_robotics_029029-TDS1.pdf)
-3. [User Manual, Sensor](/assets/pdf/clearpath_robotics_029029-TDS2.pdf)
-4. [User Manual, Control Box](/assets/pdf/clearpath_robotics_029029-TDS3.pdf)
-5. [Drawing, Sensor](/assets/pdf/clearpath_robotics_029029-TDS4.pdf)
-6. [Drawing, Control Box](/assets/pdf/clearpath_robotics_029029-TDS6.pdf)
-7. [Wiring, Contol Box](/assets/pdf/clearpath_robotics_029029-TDS5.pdf)
-8. [Velodyne website](https://velodynelidar.com/products/puck-hi-res/)
-9. [ROS webpage](http://wiki.ros.org/velodyne)
-10. [ROS tutorial](http://wiki.ros.org/velodyne/Tutorials/Getting%20Started%20with%20the%20Velodyne%20VLP16)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
deleted file mode 100644
index fe70bfab3..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_puck_lite.mdx
+++ /dev/null
@@ -1,72 +0,0 @@
----
-title: Velodyne Puck Lite
-sidebar_position: 1
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/velodyne_lidar.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Velodyne Puck Lite sensor | [016312](/assets/pdf/clearpath_robotics_023729-TDS1.pdf) | — | — |
-| Velodyne Puck Lite sensor, with M12 connector | [023729](/assets/pdf/clearpath_robotics_023729-TDS1.pdf) | 029027 | 029026 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :------------------------- | :------------------- |
-| Mass | 590 g |
-| Voltage, Minimum | 9 V |
-| Voltage, Maximum | 18 V |
-| Voltage, Sensor | 12 V |
-| Power, Average | 8 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.9 m |
-| Range, Maximum | 100 m |
-| Range, Accuracy | ±3 cm |
-| View, Horizontal | 360° |
-| View, Vertical | ±15° |
-| Resolution, Horizontal | 0.4° |
-| Resolution, Vertical | 2° |
-| Operating Temperature, Min | -10 °C |
-| Operating Temperature, Max | 60 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/3d-lidar/products/puck-lite)
-2. [Datasheet](/assets/pdf/clearpath_robotics_023729-TDS1.pdf)
-3. [User Manual, Sensor](/assets/pdf/clearpath_robotics_023729-TDS2.pdf)
-4. [User Manual, Control Box](/assets/pdf/clearpath_robotics_023729-TDS3.pdf)
-5. [Drawing, Sensor](/assets/pdf/clearpath_robotics_023729-TDS4.pdf)
-6. [Drawing, Control Box](/assets/pdf/clearpath_robotics_023729-TDS6.pdf)
-7. [Wiring, Contol Box](/assets/pdf/clearpath_robotics_023729-TDS5.pdf)
-8. [Velodyne website](https://velodynelidar.com/products/puck-lite/)
-9. [ROS webpage](http://wiki.ros.org/velodyne)
-10. [ROS tutorial](http://wiki.ros.org/velodyne/Tutorials/Getting%20Started%20with%20the%20Velodyne%20VLP16)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
deleted file mode 100644
index 99f2a5978..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/lidar_3d/velodyne_ultra_puck.mdx
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Velodyne Ultra Puck
-sidebar_position: 4
----
-
-import Support from "/components/support.mdx";
-import YAML from "/docs_versioned_docs/version-ros2humble/components/yaml/sensors/velodyne_lidar.mdx";
-
-
-
-
-
-## Item Numbers
-
-| Description | CPR Item | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------------------------------- | :------------------------------------------------------: | :-------: | :------------------------------: |
-| Velodyne Ultra Puck sensor | [016901](/assets/pdf/clearpath_robotics_029035-TDS1.pdf) | — | — |
-| Velodyne Ultra Puck sensor, with M12 connector | [029035](/assets/pdf/clearpath_robotics_029035-TDS1.pdf) | 029037 | 029036 |
-
----
-
-## Specifications
-
-| Description | Value |
-| :-------------------------- | :------------------- |
-| Mass | 925 g |
-| Voltage, Minimum | 10.5 V |
-| Voltage, Maximum | 18 V |
-| Voltage, Sensor | 12 V |
-| Power, Average | 10 W |
-| Data | Ethernet, 100 Mbit/s |
-| Range, Minimum | 0.9 m |
-| Range, Maximum | 200 m |
-| Range, Accuracy | ±3 cm |
-| View, Horizontal | 360° |
-| View, Vertical | -25° to +15° |
-| Resolution, Horizontal | 0.4° |
-| Resolution, Vertical | 0.33° |
-| Ingress Protection, Solids | 6 |
-| Ingress Protection, Liquids | 7 |
-| Operating Temperature, Min | -20 °C |
-| Operating Temperature, Max | 60 °C |
-
----
-
-## Software Bringup
-This sensor is included in the Clearpath Robotics robot package that is installed on all of our robots.
-This allows you to add or remove the sensor from your robot's software description by modifying the [robot configuration yaml](../../../../ros/config/yaml/sensors/overview.mdx).
-
-
-
----
-
-## Troubleshooting
-
-
-
----
-
-## Further Reading
-
-1. [Clearpath Robotics Store](https://store.clearpathrobotics.com/collections/3d-lidar/products/ultra-puck)
-2. [Datasheet](/assets/pdf/clearpath_robotics_029035-TDS1.pdf)
-3. [User Manual](/assets/pdf/clearpath_robotics_029035-TDS2.pdf)
-4. [Drawing, Sensor](/assets/pdf/clearpath_robotics_029035-TDS3.pdf)
-5. [Velodyne website](https://velodynelidar.com/products/ultra-puck/)
-6. [ROS webpage](http://wiki.ros.org/velodyne)
-7. [ROS tutorial](http://wiki.ros.org/velodyne/Tutorials/Getting%20Started%20with%20the%20Velodyne%20VLP16)
diff --git a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/sensors.mdx b/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/sensors.mdx
deleted file mode 100644
index ec123e019..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/accessories/sensors/sensors.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Sensors Overview
-sidebar_label: Sensors
-sidebar_position: 1
----
-
-
-
-
-
-This documentation should be considered a quick reference, rather than a complete technical data package from the sensor's Original Equipment Manufacturer.
-Every sensor page in our documentation has a _Further Reading_ section at the bottom, listing hyperlinks to the related ROS drivers, and OEM documentation.
-
-Also note that we have only listed the documentation of our most commonly used sensors.
-
-We suggest you:
-
-1. Review our documentation of the sensors related to your robot integration.
-2. Review the related _Further Reading_ section.
-3. If you are planning to purchase a sensor for standalone use, or for integration with a non-Clearpath system, consider visiting our Component Store, [store.clearpathrobotics.com](https://store.clearpathrobotics.com/).
-4. If you want Clearpath Robotics to integrate sensors on your robot, contact our Sales team at \, whether you want to use a new Clearpath Robotics platform, or reuse your existing vehicle.
-5. Contact our Support team at \ if you have any questions.
diff --git a/docs_versioned_docs/version-ros2humble/robots/common/_category_.json b/docs_versioned_docs/version-ros2humble/robots/common/_category_.json
deleted file mode 100644
index 44fea45e2..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/common/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Common",
- "position": 7
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/common/colours.mdx b/docs_versioned_docs/version-ros2humble/robots/common/colours.mdx
deleted file mode 100644
index 5cd241377..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/common/colours.mdx
+++ /dev/null
@@ -1,36 +0,0 @@
----
-title: Colours
-sidebar_position: 3
----
-
-
-
-
-
-
-
-These are the materials and colours visible on the outside of our robots:
-
-| Material | Colour | Material Note |
-| :------------------------- | :----- | :-------------------------------------------------------------------------- |
-| Electroless Nickel Plating | Silver | |
-| Stainless Steel | Silver | |
-| Anodized Aluminum | Black | Anodic Coating, Type II Class 2 in Accordance With MIL-A-8625, Colour Black |
-| Powder Coating | Yellow | Tiger Drylac 49/22550 or 38/20006, Gloss, Smooth, Colour RAL 1006 |
-| Powder Coating | Black | Tiger Drylac 39/80200, Matte, Fine Texture, Colour "Black" |
-| Lettering | White | Polyurethane, RAL 7074 "Telegrey 4" |
-| Lettering | Black | Polyurethane, RAL 9005 "Jet Black" |
-| Rubber | Black | |
-| Plastic | Black | |
-
-
-
-:::info Customization
-
-Let our Sales team know if you need custom colours or graphics on your robot.
-We can work with our paint, silkscreen, and vinyl suppliers to make the customizations that you require.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/common/components/_category_.json b/docs_versioned_docs/version-ros2humble/robots/common/components/_category_.json
deleted file mode 100644
index 32d855aed..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/common/components/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Components",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/common/components/components.mdx b/docs_versioned_docs/version-ros2humble/robots/common/components/components.mdx
deleted file mode 100644
index a5eade6d7..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/common/components/components.mdx
+++ /dev/null
@@ -1,157 +0,0 @@
----
-title: Components Overview
-sidebar_label: Components
-sidebar_position: 1
----
-
-
-
-
-
-The items listed on this page are common connectors, fasteners, and jellybeans that we frequently use in our robots.
-Refer to our [Sensors](../../accessories/sensors/sensors.mdx) and [Add-ons](../../accessories/add-ons/add-ons.mdx) sections for larger subassemblies.
-
----
-
-## Connectors
-
-
-
-
-
-| Description | CPR item | Manufacturer item |
-| :----------------------------- | :------: | :---------------- |
-| M4 stud, 76 A maximum current | 023570 | 3049107 |
-| M5 stud, 125 A maximum current | 023068 | 3049204 |
diff --git a/docs_versioned_docs/version-ros2humble/robots/common/physical_tools.mdx b/docs_versioned_docs/version-ros2humble/robots/common/physical_tools.mdx
deleted file mode 100644
index 84f14e462..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/common/physical_tools.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-title: Physical Tools
-sidebar_position: 2
----
-
-These are the most common tools we use at Clearpath Robotics to build and maintain robots.
-There is a much longer list of tools we use to design, test, and build more complicated aspects of our robots—such as Printed Circuit Board Assemblies.
-The intention of this page is to show you what tools we use for maintenance, and for adding sensors to our robots.
-
-:::info Contact Us
-
-Contact our Sales team at \ if you want us to add sensors or custom attachments to your robot.
-We can suggest hardware and software that will meet your application goals.
-
-You can see some of our past Integration Services projects [here](https://clearpathrobotics.com/integration-services/).
-
-:::
-
-:::note
-
-Some tools are specific to the electrical connectors we use at Clearpath Robotics.
-For example, we show a Panduit crimper for ring terminals.
-This suggestion is because use Panduits ring terminals in our cable assemblies.
-There are other manufacturers that make comparable products, such as Molex, Phoenix Contact, and Tyco Electronics.
-
-:::
-
-| Category | Description | Preferred Manufacturer | Manufacturer Item Number |
-| :------------------------------- | :-------------------------------------------------------- | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------- |
-| **Consumables** | Lint Free Cloth | Kimtech | |
-| | Isopropyl Alcohol | | |
-| | Thread Locker, Light | Loctite | [222](https://www.mcmaster.com/1810A27/) |
-| | Thread Locker, Medium | Loctite | [243](https://www.mcmaster.com/91458A115/) |
-| | Thread, Anti-Seize | Loctite | [8065](https://www.mcmaster.com/1019A11/) |
-| | Silicone Sealant | Dow Corning | [3138356](https://www.mcmaster.com/7587A2/) |
-| | Electrical Compound | | |
-| | Cable Ties | | |
-| **Mechanical Fabrication** | Rivet Installation Tool | Milwaukee | [2550-20](https://www.milwaukeetool.com/Products/Power-Tools/Specialty-Tools/Rivet-Tools/2550-20) |
-| | Drill | Milwaukee | [2606-20](https://www.milwaukeetool.com/Products/Power-Tools/Drilling/Drill-Drivers/2606-20) |
-| | Rotary Tool | Dremel | |
-| | Hole Deburring Tool | | |
-| **Mechanical Assembly** | Hex Keys, Metric | Wiha | [66980](https://www.digikey.ca/en/products/detail/wiha/66980/11658234) |
-| | Hex Keys, Imperial | Wiha | [66981](https://www.digikey.ca/en/products/detail/wiha/66981/11658233?s=N4IgTCBcDaICwGYCMBaAbGgnADlQOQBEQBdAXyA) |
-| | Crescent Wrenches, Metric (5 mm - 13 mm) | | |
-| | Crescent Wrenches, Imperial | | |
-| | Adjustable Wrench, Small | | |
-| | Adjustable Wrench, Large | | |
-| | Sockets and Socket Wrenches, Metric (5 mm - 13 mm) | | |
-| | Sockets and Socket Wrenches, Imperial | | |
-| | Sidecutters | Knipex | [78 03 125](https://www.digikey.ca/en/products/detail/knipex-tools-lp/78-03-125/10451639) |
-| **Electrical Cable Fabrication** | Soldering Iron | Pace | [MBT360](https://paceworldwide.com/mbt360-multi-channel-soldering-and-rework-station-w-td-200-and-sx-100) |
-| | Multimeter | Fluke | [115](https://www.digikey.ca/en/products/detail/fluke-electronics/FLUKE-115/1506332) |
-| | Soldering Helping Hands | | |
-| | Wire Strippers | Greenlee Communications | [PA1123](https://www.digikey.ca/en/products/detail/tempo-communications/PA1123/1990599) |
-| | Utility Knife | Olfa | [L-2](https://olfa.com/collections/professional/products/18mm-l-2-rubber-inset-utility-knife#shop) |
-| | Heat Gun | Milwaukee | [2688-20](https://www.milwaukeetool.com/Products/Power-Tools/Specialty-Tools/Heating-Tools/2688-20) |
-| | Crimper, Anderson Powerpole PP15 | Anderson Power Products | [1309G8](https://www.digikey.ca/en/products/detail/anderson-power-products-inc/1309G8/10647425?s=N4IgTCBcDaIIwGYAMBOA4gDhAXQL5A) |
-| | Crimper, Anderson SB50 and PP75 | Anderson Power Products | [1309G4](https://www.digikey.ca/en/products/detail/anderson-power-products-inc/1309G4/10650073) |
-| | Crimper, Molex Mini-Fit-Jr | Molex | [0638190901](https://www.digikey.ca/en/products/detail/molex/0638190901/9655931?s=N4IgTCBcDaIAwDYDMAOAjATjltIC6AvkA) |
-| | Extractor, Molex Mini-Fit-Jr | Molex | [11030044](https://www.digikey.ca/en/products/detail/molex/0011030044/210947?s=N4IgTCBcDaIIxwAwGZGICzpAXQL5A) |
-| | Crimper, Molex Mega-Fit | Molex | [2002187200](https://www.digikey.ca/en/products/detail/molex/2002187200/14311428?s=N4IgTCBcDa4AxzARgBwHYwJAXQL5A) |
-| | Extractor, Molex Mega-Fit | Molex | [0638240810](https://www.digikey.ca/en/products/detail/molex/0638240810/11657656?s=N4IgTCBcDaIGwGYAcYAsAGJBGdIC6AvkA) |
-| | Crimper, Ferrule (Phoenix Contact) | Phoenit Contact | [1213144](https://www.digikey.ca/en/products/detail/phoenix-contact/1213144/5875365) |
-| | Crimper, Ring Terminal (Panduit) | Panduit | [0638190901](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1550/447992) |
-| | Crimper, Quick Disconnect (Panduit) | Panduit | [CT-1525](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1525/447991?s=N4IgTCBcDaIMIBUC0BGArGNIC6BfIA) |
-| | Crimper, Ring Lug Terminals (Panduit) | Panduit | [CT-1700](https://www.digikey.ca/en/products/detail/panduit-corp/CT-1700/447996?s=N4IgTCBcDaIMYBcC0BGA7ABgyAugXyA) |
-| | Sidecutters | Knipex | [78 03 125](https://www.digikey.ca/en/products/detail/knipex-tools-lp/78-03-125/10451639) |
-| **Electrical Assembly** | Scouring Pads (ScotchBrite) | 3M | [61500290558](https://www.digikey.ca/en/products/detail/3m/61500290558/3589749) |
-| | Multimeter | Fluke | [115](https://www.digikey.ca/en/products/detail/fluke-electronics/FLUKE-115/1506332) |
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/_category_.json
deleted file mode 100644
index 3f1c6ad02..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Indoor",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/_category_.json
deleted file mode 100644
index f542b3edf..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Boxer",
- "position": 2
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/integration_boxer.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/integration_boxer.mdx
deleted file mode 100644
index f6630ea59..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/integration_boxer.mdx
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Boxer Integration
-sidebar_label: Integration
-sidebar_position: 2
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionBoxer from "/components/introduction_boxer.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import Support from "/components/support.mdx";
-
-
-
-To attach custom hardware to Boxer, you will have to take care of mechanical mounting, electrical
-supply, and software integration. This guide aims to equip you with respect to these challenges.
-
----
-
-### Mechanical Mounting
-
-When determining mechanical mounting, you can use the Standard mounting pattern on the top plate of the Boxer.
-At this time, the "PACS™" mounting system is not available for Boxer.
-
-#### Mechanical, Standard
-
-External payloads can be attached to the mounting plate of the Boxer by using the Ø8 mm countersunk through holes on the underside, or adding new holes.
-Whichever method you choose, the method for removing the top plate is the same and outlined below.
-
-1. Ensure the robot is shut off, and the circuit breaker is turned to the _off_ position.
-2. Disconnect and remove all existing payloads on the top plate.
-3. Using a 2 mm hex key, remove the twelve M3 round head screws holding the connection covers in place.
- Remove the panels.
- Take care to disconnect the network cable and attachment cable from the robot when removing the connection covers.
-4. Using a 4 mm hex key, remove the eleven M5 socket head screws holding the plate down.
-5. Remove the plate from the Boxer.
-
-The Boxer plate is made from 8 mm aluminum and can be easily machined according to your customization needs.
-
-The plate also has eight Ø8 mm holes in the corners which are countersunk from the underside of the plate, making them ideal for flathead screws installed to protrude from the plate.
-
-
-
-
-
-### Electrical Integration
-
-For connecting with any external payloads, such as a backpack computer, refer to the product's datasheet or manual.
-If your robot was equipped with these payloads by Clearpath Robotics this documentation is provided along with your Boxer.
-Contact [Support](#support) if you need more information.
-
-Ensure that the Boxer is shut off and the circuit breaker is turned to the _off_ position before performing any electrical work on the Boxer.
-
-The Boxer is equipped with an attachment interface that consists of a Power-over-Ethernet (PoE) RJ45 bulkhead connector, a USB Type-A bulkhead connector, and a 37-position panel receptacle and mated plug.
-To connect with the Boxer attachment interface see Section 10 of the [OTTO 100 V2.5 Operation and Maintenance Manual](https://docs.ottomotors.com/PDFs/100-v2.5-OMM.pdf).
-
-To add wires to the 37-position connector for you application, follow the TE Connectivity documentation for [connector 206305-1](https://www.te.com/usa-en/product-206305-1.html) to use appropriate crimp pins.
-Note that the 37-position connector will come pre-populated from Clearpath Robotics with 2 wires.
-These 2 wires complete the base Boxer's Motion Stop loop, allowing the robot to move.
-Other positions of the connector may be pre-populated, well as the PoE and USB, if your robot was equipped with payloads according to your Clearpath Robotics customizations.
-
-### Software Integration
-
-
-
-Refer to the following for more details:
-
-- [Computers](../../accessories/computers/computers.mdx)
-- [Sensors](../../accessories/sensors/sensors.mdx)
-- [Manipulators](../../accessories/manipulators/manipulators.mdx)
-- [Accessories](../../accessories/add-ons/add-ons.mdx)
-
----
-
-## Support
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/maintenance_boxer.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/maintenance_boxer.mdx
deleted file mode 100644
index 89350362c..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/maintenance_boxer.mdx
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Boxer Maintenance
-sidebar_label: Maintenance
-sidebar_position: 4
----
-
-import ComponentIntroductionBoxer from "/components/introduction_boxer.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Battery care
-
-To help extend the life of the batteries, follow the steps below.
-
-- Do not discharge the batteries lower than 10%.
- Batteries lower than 5% are permanently damaged and cannot be recharged.
-- Recharge batteries to 100% after every use.
-- Recharge batteries and turn the circuit breaker to ”OFF” before putting the system into long-term storage.
-- Batteries that are in long-term storage will need to be recharged every 6 months.
-- Charge batteries when the ambient temperature is between 20 °C to 30 °C.
- Consult Clearpath Robotics if you need to charge batteries outside these conditions.
-
----
-
-## Software Maintenance {#software_maintenance}
-
-Boxer is always being improved, both its own software and the many community ROS packages upon which it
-depends! You can use the apt package management system to receive new versions all software running on the
-platform.
-
-### Updating the Base Unit
-
-OTTO Motors periodically releases updates for the OTTO 100, which can be applied to Boxer's Base Unit.
-
-Please refer to [OTTO Motors' documentation](https://docs.ottomotors.com/en/30495-30532-installing-robot-software.html)
-for details on applying software updates.
-
-At the time of writing, the latest version of the OTTO 100 software supported by the Boxer's Noetic backpack is 2.22.3.
-
-### Updating the Backpack Computer
-
-The Backpack Computer can be updated by connecting it to the internet, either using a wired or wireless connection, and
-running the following commands:
-
-```
-sudo apt-get update
-sudo apt-get upgrade
-```
-
-If you see any errors, contact [Support](#support).
-
-### Starting From Scratch
-
-If Boxer's computer has become inoperable, or for any reason you want to restore it to the factory state,
-contact [Support](#support).
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/user_manual_boxer.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/user_manual_boxer.mdx
deleted file mode 100644
index 79f30387b..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/boxer/user_manual_boxer.mdx
+++ /dev/null
@@ -1,596 +0,0 @@
----
-title: Boxer User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionBoxer from "/components/introduction_boxer.mdx";
-import Support from "/components/support.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-import ComponentSafetyWarning from "/components/safety_warning.mdx";
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
-## Introduction
-
-Boxer is a large indoor mobile robot for prototyping and development of industrial applications.
-Adapted from the OTTO Motors _OTTO 100 autonomous mobile robot (AMR)_, Boxer is programmable
-and easily extensible with additional hardware.
-
-:::note
-
-Current Boxer shipments are based on OTTO 100 V2.5. Some shipments from 2021-2023 are based on
-OTTO 100 V2.4. All information in this manual applies equally to both versions except where
-otherwise noted.
-
-:::
-
-
-
-### Shipment Contents
-
-Your Boxer shipment contains the following:
-
-- Clearpath Robotics Boxer
-- OTTO 100 Manual Charger
-- Handheld Joystick Controller
-- Optional: OTTO 100 Fast Charger
-
-If you elected to purchase standard payload modules or custom integration services with Boxer, then additional equipment will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Boxer is built on the OTTO 100 AMR, which provides the core locomotion, safety, and sensing capabilities, along with a ROS 2 API
-for control of the system. Boxer is typically augmented with a Backpack Computer, which allows for user software to be installed
-and executed on the system, controlling the Base Unit through the ROS 2 API over a local Ethernet connection. The backpack
-computer also allows for control and monitoring of any additional payloads added to Boxer.
-
-#### Exterior Features
-
-Below is an overview of the Boxer robot hardware that outlines the key components that you should be aware of in order to get started
-with using your robot. Note that the front emergency stop button is only present on Boxer V2.5.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-#### Human-Machine Interface (HMI) Panel
-
-The back of Boxer has the Human-Machine-Interface panel _(HMI)_.
-The HMI has 5 elements:
-
-1. Ethernet port
-2. Power button
-3. Emergency stop reset button
-4. Chargeport
-5. Rear emergency stop button
-
-
-
-
-
-#### Front Emergency Stop Button
-
-In addition to the rear emergency stop button described in the HMI Panel above, Boxer 2.5 (but not Boxer 2.4)
-has a front emergency stop button, which is mounted to the right of the front safety LiDAR. Refer to
-[Emergency Stop Buttons](#boxer-stop-buttons) for additional details.
-
-
-
-
-
-
-
-#### Body Lights
-
-Boxer includes RGB LED strips around its body. These lights express system status according to the table below.
-
-| LED Pattern | System State |
-| :------------ | :-------------------------------------------------------------------------- |
-| Solid Red | Robot is starting up |
-| Flashing Red | Robot is emergency stopped or safety stopped |
-| Circling Blue | Base Unit is in Manual mode, allowing it to be controlled via the ROS 2 API |
-
-At present these lights are not controllable through any ROS topics.
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855
-When commanded with a positive translational velocity (forward), wheels travel in the positive X-direction.
-The direction of the axes differs from those used for roll, pitch, and yaw in aircraft, and care should be taken to ensure that data is interpreted correctly.
-
-
-
-
- Boxer Coordinate System
-
-
-
-### System Specifications
-
-| Specification | Measurement |
-| :--------------------------------- | :---------- |
-| Dimensions, Length | 740 mm |
-| Dimensions, Width | 550 mm |
-| Dimensions, Height | 320 mm |
-| Mass | 114 kg |
-| Velocity, Max | 2.0 m/s |
-| Obstacle, Max Step Height | 6 mm |
-| Obstacle, Floor Gap | 13 mm |
-| Operating Relative Humidity, Min | 0 % |
-| Operating Relative Humidity, Max | 85 % |
-| Operating Temperature, Min | 20 °C |
-| Operating Temperature, Max | 30 °C |
-| Storage Temperature, Min | -20 °C |
-| Storage Temperature, Max | 35 °C |
-| Operating Time, Standby | 8 hours |
-| Operating Time, Continuous Driving | 3 hours |
-
----
-
-## Getting Started
-
-### Unboxing
-
-Boxer ships fully assembled and no assembly is required.
-To unbox, remove the screws holding the top wood panel and the front wood panel.
-Remove the screws holding the cross bracing.
-An electric driver should be used to aid in the removal of the screws.
-Lay the top wood panel down with one end on the edge of the crate and the other end on the ground to create a ramp as shown below.
-Pull the robot out of the crate by hand, and then roll the robot down the wood ramp.
-
-
-
-
-
-### Powering Up
-
-1. Turn the 2 circuit breakers to the on position.
- You will need to lift the metal bar to do this.
-
-
-
-2. Press the Power Button.
-
-
-
-3. Wait for the system to boot.
- The Boxer's lights will go through a sequence of colors during this process:
-
- - All white for approximately 30 seconds
- - All red for approximately 30 seconds
- - Flashing white for less than 5 seconds
- - Then flashing red
-
- Note that the Boxer will be sounding an alarm which will be adjusted during the base unit configuration below.
-
-### Base Unit Configuration
-
-Connect the Boxer to the Wi-Fi network using the steps below.
-Refer to [Connecting to a robot using an Ethernet cable](https://docs.ottomotors.com/en/30495-30527-connecting-to-a-robot-using-ethernet.html) and
-[Connecting a robot to a network](https://docs.ottomotors.com/en/30495-30526-connecting-a-robot-to-a-network.html) for more details.
-
-1. Configure a network port on your laptop with the IP address \<10.255.255.200\>.
-2. Connect a network cable from the port on your laptop to the network port on the rear of the Base Unit.
-
-
-
-3. On your laptop, open a web-browser like Google Chrome, and go to the address http://10.255.255.1:8090
-4. Enter the required information to connect to your network.
- See your IT administrator for proper settings for your network.
-
-
-
-
-
-
-5. Take note of the hostname.
- It will be used in future steps for accessing the robot.
- You can also find this hostname engraved on the HMI panel, at the rear of the Boxer.
-6. Click _Save and Restart Network_.
-7. Power cycle the Boxer.
-8. Using the hostname or static IP set in the Wi-Fi setup above, load the _OTTO App_ user interface by opening a web-browser, and going to the address _http://hostname:5000_.
- (e.g. [http://A31-002124076:5000](http://A31-002124076:5000) )
- The _OTTO App_ should load, and look similar to the image below.
-
-
-
-9. Adjust the volume to an appropriate level for your facility by selecting the _Vehicle_ option from the top-left menu and adjusting the volume as appropriate.
-
-
-
-10. You have finished onfiguring the Boxer Base Unit, and it's ready for use.
-
-### Backpack Computer Configuration
-
-This section outlines how to configure the Backpack Computer attached to the Base Unit.
-You can omit this section if your Boxer is not equipped with a Backpack Computer.
-
-The Backpack Computer is an add-on computer that is networked with the Base Unit's computer, located inside then Boxer.
-This Backpack Computer can be used to integrate peripherals, like sensors and manipulators.
-A ROS bridge automatically runs upon booting the Backpack Computer, and transmits the Base Unit computer's ROS data to the Backpack Computer.
-This ROS bridge allows you to leverage the Base Unit for your own application.
-The Backpack Computer uses Netplan as its network configuration tool, and has a static IP address of \<192.168.131.1\>.
-
-#### Connecting to the Backpack Computer
-
-You can connect to the Backpack Computer on Boxer over a wired or Wi-Fi connection.
-
-To connect to the Backpack Computer over a wired connection:
-
-1. Configure a network port on your laptop with the IP address \<192.168.131.100\>.
-2. Connect a network cable from your laptop to an open network port on the Backpack Computer.
-3. Test the connection between the user computer and Backpack Computer by opening a terminal and entering: `ping 192.168.131.1 `
-4. From your laptop's terminal, you can access the Backpack Computer by entering: `ssh administrator@192.168.131.1`
-
-To connect to the Backpack Computer over a Wi-Fi connection:
-
-1. Connect your laptop to the same Wi-Fi network as the Backpack Computer.
-2. Note the IP address of the Backpack Computer's wireless interface by running this command the Backpack Computer's terminal: `ip a`
-3. To test the connection between your laptop and Backpack Computer, enter this command in a terminal from your laptop: `ping ` (eg. `ping 192.168.0.11`)
-4. From your laptop's terminal, you can access the Backpack Computer by entering: `ssh administrator@` (eg. `ssh administrator@192.168.0.11`)
-
-#### Connecting the Backpack Computer to a Wi-Fi Network
-
-To connect the Backpack Computer to a wireless network follow these steps:
-
-1. Access the Backpack Computer over an SSH connection.
- Since the Backpack Computer is presumably not connected to a Wi-Fi network yet, you will need to access the Backpack Computer over a wired connection.
- The previous section details how to connect to the Backpack Computer over a wired connection.
-2. Once you have accessed the Backpack Computer, create a netplan configuration by running the following command.
-
- sudo touch /etc/netplan/60-wifi.yaml
-
- This will create a file called _60-wifi.yaml_ inside of the _/etc/netplan/_ directory.
-
-3. Open _/etc/netplan/60-wifi.yaml_ with your favourite text editor and populate it.
- Use this example configuration file as reference:
-
- ```
- network:
- wifis:
- # change wlp2s0 to exactly match your wireless interface
- # common values are wlp2s0, wlp3s0, wlan0, etc...
- # if you aren't sure, use the `iwconfig` or `ip a` command
- wlp2s0:
- optional: true
- access-points:
- # replace "my-ssid" with the SSID of your wireless network
- my-ssid:
- # put your wireless password here
- password: wifi_password_goes_here
- # DHCP4 should be enabled for most wireless routers
- # alternatively you can use a static IP address.
- # e.g, uncomment the following
- #addresses: [192.168.1.100/24]
- #gateway: 192.168.1.1
- #dhcp4: false
- dhcp4: true
- dhcp4-overrides:
- send-hostname: true
- ```
-
-4. Connect the Backpack Computer to the wireless network by running the command below.
- Note that this may take a moment to complete:
-
- ```
- sudo netplan apply
- ```
-
-5. To verify that the Backpack Computer is connected to the wireless network, check that the Backpack Computer has an IP address assigned to its wireless interface by running:
-
- ```
- ip a
- ```
-
-### Battery Charging
-
-The system can be charged using an [OTTO 100 Manual Charger](https://ebikes.ca/product-info/grin-products/cycle-satiator.html) or an [OTTO 100 Fast Charger](https://docs.ottomotors.com/en/84902-86097-100-fast-charger.html).
-Details for use and installation are provided in the linked User Manuals.
-
-Only use the OTTO 100 Manual Charger or OTTO 100 Fast Charger provided with your Boxer.
-Use of other chargers may cause damage or injury.
-
----
-
-## Operation
-
-This section outlines how to use the basic functions of the Boxer platform in order to get started quickly.
-There are several methods of operating the robot.
-
-### Getting Started with the OTTO User Interface
-
-This section details how to get the Robot driving around using the OTTO user interface.
-
-1. Power on the system.
-2. Ensure that all emergency stop buttons are released by pulling out the red buttons at the front (V2.5 only) and rear of the unit, and then pressing the blue emergency stop Reset button.
-
-
-
-
-
-
-3. Using the base Boxer's hostname or static IP, open the OTTO App by entering the following in your laptop's web-browser:
-
- http://\:5000
-
-4. You are now ready to start driving your system.
-
-### Driving Manually
-
-To drive the robot manually, follow the steps below.
-
-1. Power up the robot and connect to the OTTO App at `http://:5000`
-2. The first time after power-up, it is necessary to take the system out of neutral by clicking on the joystick icon at the bottom right of the interface.
-
-
-
-3. Ensure that the system is in manual mode and use the _thumbstick_ at the bottom right of the interface to drive the robot in the desired direction.
- Note that the maximum speed can be adjusted using the slider _Tortoise-Hare_ at the bottom of the interface.
- We recommended you begin at slow speeds until you become comfortable with how to control the robot.
-
-
-
-
-### Mapping
-
-Prior to navigating autonomously, a map of the facility must be created.
-The details of creating a map are beyond the scope of this document.
-Detailed instructions for mapping can be found here:
-
-- [OTTO App training](https://otto.talentlms.com/)
-
-### Connecting and Using the Controller {#controller}
-
-To use your controller, it must be paired with your Boxer and powered on.
-If your purchased the Backpack Computer from Clearpath Robotics, your controller is already paired with your Boxer.
-If your controller has become unpaired or if you wish to pair a new controller, following the instructions in the
-[Boxer Tutorials](tutorials_boxer.mdx).
-
-To use the controller:
-
-1. Power up the robot and connect to the OTTO App at `http://:5000`
-2. The system will boot up into a neutral state.
- Take the robot out of _Neutral_ by clicking the _Joystick_ icon at the bottom right of the interface.
-3. Release all emergency stop buttons and press the emergency stop reset button.
-4. Press the PS button on the controller to sync with the robot.
- Once the blue LED on the top of the controller is solid, the Robot is paired and ready to move.
- Hold the L1 trigger button to engage the enable switch.
- Push the left thumbstick in the direction you wish to move the Boxer.
-5. For full speed mode, hold the R1 trigger.
- Note that it is recommended that you use full speed mode only when comfortable with the operation of the Boxer.
-
-
-
-
-### Using ROS
-
-
-
-
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-The Boxer robot contains several features to protect the safety of users and the integrity of the vehicle.
-
-### General Warnings
-
-Use of an autonomous robot is inherently dangerous.
-
-For the safety of yourself and others, always conduct initial experiments and software development with
-the robot raised off the ground. Place a wooden crate, a set of sawhorses, a sturdy storage tub, or any
-other solid flat structure under Boxer to keep the wheels clear of the
-ground ("up on blocks").
-
-When starting out, favour slower wheel speeds.
-Operating at such speeds will allow for more reaction time in the case of unexpected behaviour.
-
-When the robot is operating, keep clear of the wheels.
-
-Refer to the [OTTO 100 V2.5 Operation and Maintenance Manual](https://docs.ottomotors.com/PDFs/100-v2.5-OMM.pdf) for further safety precautions when using self-driving vehicles.
-
-### Emergency Stop Buttons {#boxer-stop-buttons}
-
-:::warning
-
-Ensure the emergency stop buttons are accessible at all times.
-Avoid mounting payloads that extend over the front or rear of Boxer and would occlude the emergency stop buttons.
-
-:::
-
-Please take time to locate the red emergency stop buttons on the front (V2.5 only) and rear and of the system.
-The emergency stop function allows a person in the physical vicinity of the robot to halt its motion and prevent re-initiation of motion.
-This emergency stop system is intended for use in emergency situations.
-The emergency stop system should not be used as the means of controlling robot motion during regular operation.
-
-When any emergency stop button is pressed, it provides a secure way to stop the robot movement, but does not control power attached by the attachment panel.
-The emergency stop function can be reset by pulling out all the red emergency stop buttons until they return to an extended position and then pressing the emergency stop reset button.
-The robot may begin moving again immediately after the emergency stop reset button has been pressed.
-
-When in emergency stop mode, the light strip will be flashing red and Boxer will not drive.
-The commands received during emergency stop mode are not buffered; Boxer will always act on the latest commands received.
-This means that if the commands are stopped before the stop is released, the Boxer will not move.
-If the commands are continued, Boxer will move at the speed commanded once the stop is released.
-
-### Safety Lidars
-
-Boxer is also equipped with safety lidars in the front and back that will cause the robot to lose power if a collision is predicted,
-or if the robot is operating too fast in an enclosed environment. The safety stop is automatic, and is not controlled through any ROS
-topics. Once the danger has passed the safety stop will automatically disengage.
-
-If Boxer seems to be stuck in a safety stop, check that there is no dirt or debris on either the front or rear lidars. Wipe the
-lidars down using an appropriate lidar wipe or soft cloth to remove any dirt.
-
-### Recommended Safe Work Procedures
-
-
-
----
-
-## Support
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/_category_.json
deleted file mode 100644
index 7af794442..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Dingo",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/_category_.json
deleted file mode 100644
index e5f1838f9..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Integration",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
deleted file mode 100644
index eb52834ee..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/integration_dingo.mdx
+++ /dev/null
@@ -1,258 +0,0 @@
----
-title: Dingo Integration
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentPacsMechanical from "/components/pacs_mechanical.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import Support from "/components/support.mdx";
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
-To attach custom hardware to Dingo, you will have to take care of mechanical mounting, electrical
-supply, and software integration. This guide aims to equip you with respect to these challenges.
-
----
-
-### Mechanical Mounting
-
-When determining mechanical mounting, you have two options, both of which are described below.
-
-- the "Standard" mounting pattern on Dingo's trough cover
-- the "PACS™" mounting system and associated kits
-
-#### Mechanical, Standard
-
-A standard Dingo is delivered with an 80 mm square mounting pattern of M5 threaded holes on Dingo's trough cover as shown
-in [Exterior Features](../user_manual_dingo.mdx#dingo-exterior-features), which can be used for attaching external payloads.
-The mounting holes come with M5 screws pre-installed.
-You may mount your hardware directly onto the trough cover or you may design and mount a new plate to the trough cover and secure it to the trough cover using M5 screws.
-
-#### Mechanical, PACS™
-
-
-
-Refer to the following pages for Dingo brackets that can simplify your integration.
-
-- [Top Plate](kits/top_plate_dingo.mdx)
-- [Riser Full](kits/riser_full_dingo.mdx)
-
-### Electrical Integration {#dingo-payload-electrical-integration}
-
-Except for bus-powered USB cameras, most payloads have separate leads for power and data.
-
-#### Data Connections
-
-Data connections may be brought through the openings in the trough cover and connected directly to the internal computer.
-
-Dingo's internal computer options support USB3 and Ethernet connectivity.
-In addition, the PCIe Gen3 x16 slot may be used to supply a GPU or other attachements, as necessary.
-Additionally, the internal mounting area may be used for an Ethernet switch, when attaching multiple Ethernet payloads, or for a PoE power injector as required.
-
-#### Connector Summary
-
-The Dingo MCU board provides a number of connections for power, relays, auxiliary inputs and auxiliary outputs.
-These are summarized in the following table and described in more detail in the following sections.
-
-| MCU board label | MCU board connector | Mating connector | Crimp terminals | Crimping tool |
-| :--------------- | :---------------------------------------------------------- | :---------------------------------------------------------- | :----------------------------------------------------------- | :--------------- |
-| PWR1, PWR2 | Dingo 1.0: Molex 0039301040 Dingo 1.5: Molex 0039302040 | Dingo 1.0: Molex 0039012040 Dingo 1.5: Molex 0039014041 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-| VBAT | Molex 768250002 | Molex 1700010102 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-| INPUTS | TE 3-794682-8 | TE 794617-8 | TE 1-794610-1 (AWG 20-24) or TE 1-794611-1 (AWG 26-30) | TE 91391-1 |
-| SW_IN | TE 2-1445094-2 | TE 1445022-2 | TE 1-794610-1 (AWG 20-24) or TE 1-794611-1 (AWG 26-30) | TE 91391-1 |
-| AUX1, AUX2, AUX3 | TE 3-794682-4 | TE 794617-4 | TE 1-794610-1 (AWG 20-24) or TE 1-794611-1 (AWG 26-30) | TE 91391-1 |
-| RELAY | TE 4-794682-0 | TE 1-794616-0 | TE 1-794610-1 (AWG 20-24) or TE 1-794611-1 (AWG 26-30) | TE 91391-1 |
-| FAN | Molex 0533750210 | Molex 0511630200 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-| ESTOP | Molex 053370610 | Molex 0511630600 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-
-#### User Power Connections
-
-The following are available as user power: unregulated battery power (see VBAT), regulated 12 V power (see PWR1 and PWR2), and regulated 5 V power (see PWR1 and PWR2).
-
-Similar to the data connections, the power leads may be brought through the trough cover and connected to the user power.
-Remove the front trough cover by removing four flathead screws and locate the appropriate power connector on the MCU board.
-Refer to the figure below for the location of the user power connectors.
-Route the power from the MCU board to the appropriate location, either to the internal payload modules or through the openings in the trough cover to the topside payload.
-
-
-
-
-
-
- Dingo 1.0 MCU and User Power
-
-
-
-
-
-
-
- Dingo 1.5 MCU and User Power
-
-
-
-
-
-#### AUX Inputs {#dingo-aux-inputs}
-
-The Dingo MCU includes an 8-pin `INPUTS` connector and a 2-pin `SW_IN` connector that allow the user to provide inputs to the system.
-The user can then subscribe to these inputs on the `/mcu/aux_inputs` ROS topic.
-The AUX inputs are mapped to the ROS message bits as follows:
-
-- IN1: bit 0
-- IN2: bit 1
-- IN3: bit 2
-
-Electrically, the `INPUTS` connector is used for IN1 and IN2, with pin mapping as outlined below.
-Note that each of the two inputs can be 12 V or 24 V inputs, with a shared return path.
-The inputs have opto-electrical isolation.
-
-- 1: 12 V power (for external input circuit, if needed)
-- 2: IN1 return
-- 3: GND (for external input circuit, if needed)
-- 4: IN2 return
-- 5: IN1 12 V input
-- 6: IN1 24 V input
-- 7: IN2 12 V input
-- 8: IN2 24 V input
-
-Electrically, the `SW_IN` connector is used for IN3, with pin mapping as outlined below.
-This is intended to be a 'switch' input and it generates a 100 ms pulse to the microcontroller when asserted.
-
-- 1: 3.3 V input (IN3)
-- 2: GND
-
-#### AUX Outputs and Relay {#dingo-aux-outputs}
-
-The Dingo MCU includes three user-controlled outputs (AUX1, AUX2, AUX3), that can be controlled by publishing to the `/mcu/aux_outputs` ROS topic.
-To enable the AUX outputs, simply publish a single message with the appropriate bits set to 1 to turn the output on and 0 to turn it off.
-The state does not persist meaning new commands will need to keep the bit enabled as well.
-The AUX outputs are mapped to the ROS message bits as follows:
-
-- AUX1: bit 0
-- AUX2: bit 1
-- AUX3: bit 2
-
-For example, to disable all AUX outputs:
-
-```
-rostopic pub /mcu/aux_output std_msgs/UInt8 "data: 0"
-```
-
-For example, to enable all AUX outputs:
-
-```
-rostopic pub /mcu/aux_output std_msgs/UInt8 "data: 7"
-```
-
-For example, to enable just the AUX3 output:
-
-```
-rostopic pub /mcu/aux_output std_msgs/UInt8 "data: 4"
-```
-
-Each of the AUX outputs is a 4-pin connector with pin mapping as outlined below.
-
-**AUX1 Pin Mapping**
-
-- 1: VSYS (shore power or battery power) with 5 A fuse
-- 2: VSYS (shore power or battery power) with 5 A fuse
-- 3: GND
-- 4: GND
-
-**AUX2 Pin Mapping**
-
-- 1: 12 V with 5 A fuse
-- 2: 12 V with 5 A fuse
-- 3: GND
-- 4: GND
-
-**AUX3 Pin Mapping**
-
-- 1: 5 V with 5 A fuse
-- 2: 5 V with 5 A fuse
-- 3: GND
-- 4: GND
-
-**Relays**
-
-In addition to the AUX output connectors, publishing to `/mcu/aux_outputs` also
-controls the AUX relays. These relays are available through the 10-pin
-connector on the MCU labelled `RELAY` with pin mapping:
-
-- 1 and 6: 12 V with 2 A fuse
-- 5 and 10: GND
-- 2 and 7: AUX1 relay closed with aux_outputs bit 0 is '1'
-- 3 and 8: AUX2 relay closed with aux_outputs bit 1 is '1'
-- 4 and 9: AUX3 relay closed with aux_outputs bit 2 is '1'
-
-#### Optional Fan {#dingo-fan}
-
-While a fan is not included by default with Dingo, a fan may be integrated into the system.
-Electrically, connect a 12 V 2-pin fan to the MCU connector labelled `FAN` using a mating connector.
-The pins should be connected as follows:
-
-- 1: 12 V @ 500mA max
-- 2: GND
-
-Then, the use can publish a ROS message to the `/mcu/fans` topic to control the fan.
-
-#### Optional External Motion Stop {#dingo-external-motion-stop}
-
-In addition to the built-in Motion Stop button, an external motion-stop button can be added that has similar functionality.
-Electrically, the external motion-stop button can be connected to the 6-pin MCU connector labelled `ESTOP` using a mating connector.
-
-The six pins should be connected as follows:
-
-- 1-2: to an external "normally closed" motion-stop breakout button:
- - press to engage the motion stop
- - twist and release the external motion stop button to clear the motion-stop
- - to re-enable the motors, the Motion Stop Button on the HMI panel must be pressed
-- 3-4: short these pins to indicate that external motion-stop is selected
-- 5-6: short these pins to indicate that external motion-stop is present
-
-#### MCU Debug LEDs
-
-The Dingo MCU PCBA comes equipped with four LEDs controlled by Dingo firmware for debugging.
-If the system is working properly, these LEDs functions as follows:
-
-- **DBG1**: toggles every 500 ms when main loop on MCU is running
-- **DBG2**: on if MCU connected to ROS on computer; else false (same as COMMS LED on HMI)
-- **DBG3**: toggles when MCU is relaying messages from CAN bus to computer
-- **DBG4**: toggles when MCU is relaying messages from computer to CAN bus
-
-### Software Integration
-
-
-
-Refer to the following for more details:
-
-- [Computers](../../../accessories/computers/computers.mdx)
-- [Sensors](../../../accessories/sensors/sensors.mdx)
-- [Manipulators](../../../accessories/manipulators/manipulators.mdx)
-- [Accessories](../../../accessories/add-ons/add-ons.mdx)
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
deleted file mode 100644
index 29029fd60..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Kits",
- "position": 2
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
deleted file mode 100644
index 43bf58d45..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/riser_full_dingo.mdx
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: Full Riser
-sidebar_position: 3
----
-
-
-
-:::note
-
-We suggest you to remove the 3rd and 5th rows of screws from the front of the Dingo-D or Dingo-O.
-You can choose different locations to suit your application, but this will require custom URDF software work.
-
-:::
-
-### Step 2
-
-Insert the male threaded side of the shafts _(ID2)_ into the holes where you removed the screws in _Step 1_.
-
-:::note
-
-Torque these shafts to 5 N·m if you are concerned about them loosening from high vibration applications.
-
-:::
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 3
-
-Repeat this for the 3 remaining shafts.
-
-### Step 4
-
-Place the riser's plate on top of the shafts.
-The plate is symmetrical, so there is not a front / back side.
-
-### Step 5
-
-Fasten the plate using 4 screws _(ID3)_
-
-:::note
-
-Torque these screws to 5 N·m if you are concerned about them loosening from high vibration applications.
-
-:::
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
deleted file mode 100644
index d4e6f8aff..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/integration_dingo/kits/top_plate_dingo.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Top Plate
-sidebar_position: 2
----
-
-
-
-
-
-The standard top plates for the Dingo include M5×0.8 threaded holes that match the Clearpath PACS™ standard.
-These top plates are included with all Dingo-D and Dingo-O robots.
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/maintenance_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/maintenance_dingo.mdx
deleted file mode 100644
index 80be337af..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/maintenance_dingo.mdx
+++ /dev/null
@@ -1,97 +0,0 @@
----
-title: Dingo Maintenance
-sidebar_label: Maintenance
-sidebar_position: 5
----
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
-import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_battery_care.mdx";
-import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
-import ComponentLifepo4BatteryCareTips from "/components/maintenance/lifepo4_battery_care_tips.mdx";
-import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Battery Care
-
-### Lead-Acid Battery Care
-
-Dingo's default power supply is a sealed 12 V lead-acid battery pack (VRLA), providing 20 Ah of charge.
-These tips are intended to help keep your Dingo Lead-Acid Battery in tip-top shape.
-With proper maintenance, the battery should maintain the majority of its capacity for hundreds of cycles.
-
-
-
-Your robot's battery charger works in 3 stages:
-
-1. Constant current charging or bulk charge (9 to 14.6 V @ 6 A): indicator LED is red
-2. Constant voltage charging or topping charge (14.6 V @ 6 A down to 2 A): indicator LED is red
-3. Trickle or Float charge (14.6 V @ 2 A down to 0 A): indicator LED is green
-
-The bulk of the capacity (70%) is regained during the first stage.
-
-It is important to let the charger complete all 3 stages whenever possible, to help maintain the life of the battery.
-The initial stage will take 3 - 5 hours, and a complete charge may take up to 10 hours, depending on the
-depth of discharge.
-
-
-
-Your robot's battery charger works in 3 stages:
-
-1. Constant current charging or bulk charge (9 to 14.6 V @ 6 A): indicator LED is red
-2. Constant voltage charging or topping charge (14.6 V @ 6 A down to 2 A): indicator LED is red
-3. Trickle or Float charge (14.6 V @ 2 A down to 0 A): indicator LED is green
-
-The initial stage will take 5 - 7 hours, and a complete charge may take up to 14 hours.
-
-### LiFEPO4 Battery Care
-
-:::note
-
-LiFEPO4 are not available for Dingo 1.0. They are only available for Dingo 1.5 and newer.
-
-:::
-
-Dingo's optional power supply is a Lithium Iron Phosphate battery pack (LiFEPO4),
-providing minimum 20 Ah of charge. These tips are intended to help keep your Dingo LiFEPO4 Battery
-in tip-top shape. With proper maintenance, the battery should maintain the majority of its capacity for
-thousands of cycles, typically a 10x increase over SLA batteries.
-
-The LiFEPO4 battery charger works in 3 stages:
-
-1. Constant current charging or bulk charge (9 to 14.6 V @ 7 A): indicator LED is red
-2. Constant voltage charging or topping charge (14.6 V @ 7 A down to 0.7 A): indicator LED is red
-3. Balancing or Float charge (14.6 V @ 0.7 A down to 0 A): indicator LED is green
-
-The bulk of the capacity (70%) is regained during the first stage.
-
-It is important to let the charger complete all 3 stages whenever possible, to help maintain the life of the battery.
-The initial stage will take 2 - 4 hours, and a complete charge may take up to 8 hours, depending on the depth of discharge.
-
-
-
----
-
-## Software Maintenance {#software_maintenance}
-
-### Getting New Packages
-
-
-
-### MCU Firmware Update
-
-
-
-### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
-
-
-
----
-
-## Support {#support}
-
-
-
----
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/tutorials_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/tutorials_dingo.mdx
deleted file mode 100644
index 59b2481b7..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/tutorials_dingo.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Dingo Tutorials
-sidebar_label: Tutorials
-sidebar_position: 4
----
-
-import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Dingo Overview
-
-### Introduction
-
-Dingo a lightweight and easy-to-use unmanned indoor ground vehicle for ROS, suitable for research and rapid prototyping applications.
-These tutorials will assist you with setting up and operating your Dingo.
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/dingo).
-
-
-
-### Jetson Installation
-
-Refer to the [Jetson](../../accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx) page for details on installing a Jetson in Dingo.
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/user_manual_dingo.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/user_manual_dingo.mdx
deleted file mode 100644
index 518384a33..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/dingo/user_manual_dingo.mdx
+++ /dev/null
@@ -1,635 +0,0 @@
----
-title: Dingo User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionDingo from "/components/introduction_dingo.mdx";
-import ComponentSupport from "/components/support.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-import ComponentSafetyWarning from "/components/safety_warning.mdx";
-
-import Tabs from "@theme/Tabs";
-import TabItem from "@theme/TabItem";
-
-
-
-## Introduction
-
-Dingo is a lightweight and easy-to-use unmanned indoor ground vehicle for ROS.
-
-There are two Dingo variants:
-
-- **Dingo-D** uses differential drive and has two module bays, one of which must be a battery module; the second module is typically a computer module.
-- **Dingo-O** uses omnidirectional drive and has four module bays, at least two of which are typically battery modules; the other modules may be computer modules or networking equipment.
-
-
USB cable (x1): USB Cable, Type A to Micro B (0.3 m)
-
Molex connectors (x2): Molex P/N - 0039012040
-
Molex crimp pins (x8): Molex P/N - 0039000073
-
Fuse 5A (x1): Littelfuse Inc. P/N - 0891005.NXS
-
Fuse 10A (x1): Littelfuse Inc. P/N - 0891010.NXS
-
Fuse 20A (x1): Littelfuse Inc. P/N - 0891020.NXS
-
Fuse 30A (x1): Littelfuse Inc. P/N - 0891030.NXS
-
-
-
-
-
-
Dingo UGV (Dingo-D or Dingo-O variant)
-
One or more batteries of the following type:
-
-
12 V sealed lead-acid (SLA) batteries
-
- 12.8 V LiFEPO4 batteries
-
-
-
One universal charger for your batteries
-
One Sony PS4 Bluetooth controller
-
One Dingo quick start guide
-
Accessories:
-
-
USB cable (x1): USB Cable, Type A to Micro B (0.3 m)
-
Molex connectors (x2): Molex P/N - 0039014041
-
Molex crimp pins (x8): Molex P/N - 0039000073
-
Fuse 5A (x1): Littelfuse Inc. P/N - 0891005.NXS
-
Fuse 10A (x1): Littelfuse Inc. P/N - 0891010.NXS
-
Fuse 20A (x1): Littelfuse Inc. P/N - 0891020.NXS
-
-
-
-
-
-If you elected to purchase standard payload modules or custom integration services with Dingo, then additional equipment will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Dingo is built around a computer running Ubuntu (Intel-based computer or Jetson developer kit), paired with a 32-bit microcontroller MCU.
-The MCU handles I/O, power supply monitoring, and motor control, as well as supplying data from the integrated IMU.
-The communication channel between the MCU and computer is a 100 Mbps Ethernet connection.
-
-#### Exterior Features {#dingo-exterior-features}
-
-The exteriors of Dingo-D and Dingo-O are shown below and include:
-
-- External payload mounts on the top trough cover;
-- 98.4 mm diameter wheels (Dingo-D) or 101.6 mm diameter mechanum wheels (Dingo-O);
-- Human machine interface panel (HMI);
-- Top (yellow) fairings;
-- Side access panels;
-- Front panel connectors (Dingo 1.5 only):
- - Wired battery charger port
- - DC shore power port
- - WiBotic wireless battery charge port (optional, not shown)
-
-
-
-
-
-
-
-#### Human-Machine Interface (HMI) Details
-
-The human-machine-interface (HMI) panel is shown below and includes from left:
-
-| Icon | Description |
-| :---------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| | **Motion Stop button**: LED is solid green when Dingo is able to drive and is flashing green when the Dingo's motors are disengaged; pressing button toggles the motors between engaged and disengaged mode (further details in [Motion Stop Buttons](#dingo-stop-buttons)); LED is not illuminated when connected to DC shore power or to the wired charger (as the robot is prevented from moving in this state) |
-| | **Comms indictor**: LED is solid green when communication between the MCU and computer has been established and LED is off otherwise |
-| | **Wi-Fi indicator**: LED is solid green when Wi-Fi is connected and LED is off otherwise |
-| | **Battery indicator**: LED is solid green when the battery level is ok, flashing green when connected to DC shore power, solid yellow when the battery level is getting low (should be charged soon), and solid red when the battery level is critical (should be charged immediately) |
-| | **System Power button**: LED is solid blue when the system is powered on and running and the LED is flashing blue during the shutdown process; when the system is powered off, pressing the power button begins the power on process; when the system is powered on, a quick press of the power button begins a graceful shutdown and a prolonged press of the power button triggers and immediate power off of the system |
-
-
-
-
- HMI Panel
-
-
-
-#### Payload Details
-
-The interiors of Dingo-D and Dingo-O are shown below along with example payload modules.
-
-To access Dingo's payload modules (computers or batteries), simply slide and remove the top (yellow) fairings.
-To access Dingo's MCU PCBA (for user power), remove the four M5 flathead screws from the top trough cover, and then remove the trough cover.
-
-
-
-
-
-
- Area inside Dingo-D 1.0, with example modules
-
-
-
-
-
- Area inside Dingo-O 1.0, with example modules
-
-
-
-
-
-
-
- Area inside Dingo-D 1.5, with example modules
-
-
-
-
-
- Area inside Dingo-O 1.5, with example modules
-
-
-
-
-
-#### Corner LEDs and System State
-
-Dingo is equipped with LEDs at the four corners of the robot, which indicate the state of the system:
-
-
-
-
-
-
-
System State (lowest to highest priority)
-
Corner LED Output
-
-
-
-
-
Idle
-
Front LEDs solid white (low intensity), rear LEDs solid red (low intensity)
-
-
-
Driving
-
Front LEDs solid white (medium intensity), rear LEDs solid red (medium intensity)
-
-
-
Low Battery
-
Pulsing orange LEDs
-
-
-
Reset Required
-
Adjacent corners alternating between red and off
-
-
-
Motion Stop Engaged
-
Flashing red LEDs
-
-
-
System Fault
-
Flashing orange LEDs
-
-
-
-
-
-
-
-
-
System State (lowest to highest priority)
-
Corner LED Output
-
-
-
-
-
Idle
-
Front LEDs solid white (low intensity), rear LEDs solid red (low intensity)
-
-
-
Driving
-
Front LEDs solid white (medium intensity), rear LEDs solid red (medium intensity)
-
-
-
Low Battery
-
Pulsing orange LEDs
-
-
-
Reset Required
-
Adjacent corners alternating between red and off
-
-
-
Motion Stop Engaged
-
Flashing red LEDs
-
-
-
- Charging: wired or wireless (Dingo 1.5 only)
-
-
Pulsing green LEDs
-
-
-
Shore Power Connected
-
Pulsing blue LEDs
-
-
-
- Shore Power Connected and Charging (Dingo 1.5 only)
-
-
Pulsing green to blue LEDs
-
-
-
Puma Fault
-
Flashing red LED on Puma at fault, solid red for other corners
-
-
-
- Shore Power Fault (Dingo 1.5 only)
-
-
Flashing blue and red LEDs
-
-
-
Battery Fault
-
Flashing yellow and red LEDs
-
-
-
LED Command Timeout
-
Solid red
-
-
-
-
-
-
-While in "Idle" and "Driving" states, the user can override the LEDs by publishing to the `/mcu/lights` topic.
-
-#### DC Shore Power
-
-Dingo provides a DC Shore Power connection ([internal connector for Dingo 1.0](integration_dingo/integration_dingo.mdx#dingo-payload-electrical-integration); [external connector for Dingo 1.5](#dingo-exterior-features))
-to allow the system to be powered without requiring batteries to be present. Note that when DC Shore Power is connected, the motors are disabled and it is not possible to drive the
-Dingo; however, all other electronics (computers, sensors, etc) will remain enabled.
-
-
-
- For Dingo 1.0, to connect the shore power, remove the top trough cover (to access the MCU) and then attach the shore power cable to the 2-port connector labelled "SHORE" on the MCU.
-
-
- For Dingo 1.5, users can also connect the manual charger while using DC Shore Power to allow the batteries to charge fully with no load present on them. The DC Shore Power supply is an off the shelf Mean Well power supply, part number GST280A15-C6P. This power supply is a 15V, 225W AC/DC converter with a 6 position
- Molex connector that plugs into the mating port on the front of the Dingo.
-
-
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855.
-
-When commanded with a positive translational velocity (forward), wheels travel in the positive X-direction.
-The direction of the axes differs from those used for roll, pitch, and yaw in aircraft, and care should be taken to ensure that data is interpreted correctly.
-
-
-
-### System Specifications
-
-| Specification | Dingo-D (Differential Drive) | Dingo-O (Omnidirectional Drive) |
-| :------------------------- | :----------------------------------------------------------------------- | :----------------------------------------------------------------------- |
-| Dimension, Length | 551 mm | 686 mm |
-| Dimension, Width | 517 mm | 517 mm |
-| Dimension, Height | 110 mm | 114 mm |
-| Ground Clearance | 14 mm | 16 mm |
-| Mass | 12 kg | 17.5 kg |
-| Maximum Modules | 2 | 4 |
-| Maximum Payload | 20 kg | 25 kg |
-| Speed, Maximum | 1.3 m/s | 1.3 m/s |
-| Operating Environment | Indoor | Same as Dingo-D |
-| Operating Time (Dingo 1.0) | 2 hours (1X SLA), 4 hours (1X Lithium) | 2 hours (2X SLA), 4 hours (2X Lithium) |
-| Operating Time (Dingo 1.5) | 2 hours (1X SLA), 4 hours (1X LiFEPO4) | 2 - 6 hours (1X - 3X SLA), 3.5 - 11 hours (1X - 3X LiFEPO4) |
-| Battery Chemistry | Sealed Lead-Acid or Lithium (Dingo 1.0) / LiFEPO4 (Dingo 1.5) | Same as Dingo-D |
-| Charge Time | 3.3 hours (1X SLA) or 3.0 hours (1X LiFEPO4) | 3.3 - 10 hours (1X - 3X SLA) or 3 - 9 hours (1X - 3X LiFEPO4) |
-| User Power (Dingo 1.0) | 20 A @ VBAT (11 - 16.8 V), 7A @ 12 V, 5 A @ 5 V | Same as Dingo-D |
-| User Power (Dingo 1.5) | 20 A @ VBAT (11 - 15 V), 10A @ 12 V, 5 A @ 5 V | Same as Dingo-D |
-| Communication | Ethernet, USB 3.0 | Same as Dingo-D |
-| Internal Sensing | Battery Status, Wheel Odometry, Motor Currents, Onboard IMU | Same as Dingo-D |
-
-
-
-
-
----
-
-## Getting Started
-
-You are ready to go! This section details how to get Dingo into action.
-To begin, place Dingo "up on blocks" as described in the [Safety](#safety) section, making sure that the wheels are clear of the ground.
-
-For most Dingo setups, there will be an Onboard Computer which is directly connected to the Dingo and an Offboard Computer which is used to control Dingo and gather data.
-These two computers must be set up to communicate with each other.
-
-### Onboard Computer Setup
-
-If you purchased an Onboard Computer from Clearpath Robotics with Dingo, it is already installed, connected, and powered.
-If not, or to set up your own Onboard Computer, see the [Dingo Tutorials](tutorials_dingo.mdx).
-
-Note that the Onboard Computer must be connected to Dingo's Ethernet port, which is accessible in the center channel.
-
-### Powering Up
-
-If you've just unpacked Dingo from its packaging, you may need to open it up and connect the battery.
-
-Press the power button on Dingo's HMI panel.
-The LEDs should show a test pattern, after which you will wait about 30 seconds for the internal computer to finish booting up.
-Once it has finished booting, the Comms indicator should turn green.
-This indicates that ROS is up on the computer and has established communications with the Dingo base.
-
-### Network Configuration
-
-To get Dingo connected to your local Wi-Fi network, you must first access the Onboard Computer using a wired connection to the robot.
-Remove the top trough cover and the appropriate yellow fairing to access the computer module, then connect to one of the network ports with a standard Ethernet cable.
-See the [Dingo Tutorials](tutorials_dingo.mdx) for details.
-
-### Connecting and Using the Controller {#controller}
-
-To use your controller, it must be paired with your Dingo and powered on.
-If your purchased the Onboard Computer from Clearpath Robotics, your controller is already paired with your Dingo.
-If your controller has become unpaired or if you wish to pair a new controller, following the instructions in the [Dingo Tutorials](tutorials_dingo.mdx).
-
-To teleoperate Dingo, first clear the motion-stop.
-Then, power on the controller by pressing the `PS` button on the controller.
-Once the blue LED on the top of the controller goes solid, you are paired and ready to drive.
-
-Hold the L1 trigger button (deadman switch) and push the left thumbstick forward to drive the Dingo.
-For full speed mode, hold the R1 trigger.
-See the figure below for the Sony PS4 controls layout.
-If you are not seeing any action, refer to [Support](#dingo-support) to get in touch with support.
-
-
-
-
- PS4 Controls Layout
-
-
-
-### Using ROS
-
-
-
-### Battery Charging
-
-
-
- For Dingo 1.0, when finished with the Dingo, press and release the power button to power it off.
- Then remove the batteries for charging.
-
- Dingo's batteries are charged outside the Dingo using the charger(s) provided.
-
- Alternatively, if you have multiple batteries, you can hot-swap them one at a time.
- The system will remain operational while hot-swapping as long as there is at least one battery in the system or the system is connected to shore power prior to removing the batteries.
- Note that plugging in shore power will engage a motion-stop and it is not possible to drive Dingo while connected to shore power.
-
- The Sealed Lead-Acid batteries have overcurrent protection in the form of an ATO fuse.
- The lithium batteries include integrated protections against fault due to overcurrent, overdischarge, and short circuit.
- The batteries are rugged and designed for the demanding environments into which Dingo may be deployed.
-
-
- For Dingo 1.5, to charge the batteries, simply connect the manual charger to the charge port on the front of the Dingo. Charging can take place while the unit is powered,
- or unpowered, or while the unit is connected to DC Shore Power. The charging current for the SLA system is 6A, and 7A for the LiFEPO4 system. Care must be
- taken when charging while the system is powered, as if the load/total current is higher than the supplied charge current the batteries will continue to drain.
- If the total system current is less than the charge current the batteries will charge, but at a reduced rate as the system will be using a portion of the
- charger current to maintain operation.
-
-
-
-For multi-battery systems the charge current is distributed across the number of batteries present in the system, so charging time will increase appropriately.
-Care should be taken when removing or installing batteries. The batteries must be at the same charge level or voltage before connecting them together in the system.
-The easiest way to ensure this is to have an external charger, and by charging each battery individually with that charger to a full charge so all batteries are at
-the same charge level (or voltage). Once at the same level it is ok to connect them together in the unit. Failure to follow this procedure can result in
-battery/system damage and/or personal injury.
-
-However, please take note of the following:
-
-- SLA batteries must be charged while in a 0 to +45 ◦C range and discharged while in a -30 to +60 ◦C range.
-- Lithium batteries must be charged while in a 0 to +50 ◦C range and discharged while in a -20 to +60 ◦C range.
-- LiFEPO4 batteries must be charged within a 0 to +45 ⁰C range and discharged while in a -20 to +60 ⁰C range.
-- Chargers must be placed on a hard surface, not on a carpet or other insulating device, as they can get hot during the bulk charging phase.
-
-Please contact Clearpath Robotics for additional information about Dingo's batteries or for information about purchasing additional batteries.
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-Dingo contains several features to protect the safety of users and the integrity of the robot.
-
-:::caution
-
-Dingo is a fast moving robotic platform. Please read the following notices carefully.
-
-:::
-
-### General Warnings
-
-Dingo is a rugged and high-performance vehicle.
-For the safety of yourself and others, always conduct initial experiments and software development with the vehicle raised off the ground.
-Place a wooden crate, a set of sawhorses, a sturdy storage tub, or any other solid flat structure having a height greater than 150 mm (6 inches) under Dingo to keep the wheels clear of the ground ("up on blocks").
-
-When starting out, favour slower wheel speeds.
-Dingo's control loops can accurately maintain velocities as low as 0.1 m/s.
-Operating at such speeds will give you more time to react if things don't go quite as you expect.
-
-### Motion Stop Buttons {#dingo-stop-buttons}
-
-The Motion Stop button is located on the HMI Panel at the back of Dingo.
-To engage Stop Mode, press the Motion Stop button once; you should see that the green LED by the Motion Stop button is flashing and that all four corner LEDs are flashing red.
-To disengage Stop Mode, press the Motion Stop button again; all LEDs should return to their original values.
-
-When in Stop Mode, the Dingo will not drive.
-The commands received while in Stop Mode are not buffered; Dingo will always act on the latest commands received.
-This means that if the commands are stopped before the Motion Stop button is pressed to disengage Stop Mode, the Dingo will not move.
-If the commands are continued, Dingo will move at the speed commanded once the Motion Stop button is pressed to disengage Stop Mode.
-
-Ensure that the Motion Stop button is accessible at all times.
-Avoid mounting payloads that extend over the rear of Dingo and would block access to the Motion Stop button.
-
-Note that the Dingo MCU board does provide a breakout to allow an external motion-stop button/switch to be integrated by the end user, which could be used to engage/disengage Stop Mode.
-See [Optional External Motion Stop](integration_dingo/integration_dingo.mdx#dingo-external-motion-stop) for details on adding an external motion-stop button/switch.
-
-### Electrical System
-
-Dingo is powered by batteries capable of delivering over 2000W for short durations.
-This gives Dingo's motors their great performance; however, it is also enough power to cause severe bodily harm.
-Always use caution when operating Dingo to avoid personal injury or property damage.
-To ensure safety, please observe the following precautions:
-
-- Do not tamper with the battery terminals or wiring.
-- Do not tamper with the fuses, except to check and change the fuses.
-- Always replace fuses with the same type and rating to ensure continued protection against risk of fires.
-- Consult Clearpath Robotics support if you need to service the batteries.
-- Do not lay tools or other objects on top of the batteries.
-- Charge the battery only with the charger provided by Clearpath Robotics.
-- Please dispose of the batteries properly or return them to Clearpath Robotics to do so.
-
-### Lifting and Transport
-
-- Ensure that Dingo's Stop Mode is engaged when transporting short distances and powered off when transporting longer distances.
-- Do not push the robot at more than 0.5 m/s (1.6 ft/s) or damage to the motor controls may occur.
-
-### Performance Considerations
-
-Included in Dingo are native software checks and limits to protect the robot.
-However, it is recommended to monitor the system's status during usage with the `/status` and `/diagnostics` topics.
-These topics provide useful information regarding voltages, currents, temperatures and general health of the system.
-
-### Recommended Safe Work Procedures
-
-
-
----
-
-## Support {#dingo-support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/_category_.json b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/_category_.json
deleted file mode 100644
index 8288a653f..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Ridgeback",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/integration_ridgeback.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/integration_ridgeback.mdx
deleted file mode 100644
index 45e4c9ef8..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/integration_ridgeback.mdx
+++ /dev/null
@@ -1,168 +0,0 @@
----
-title: Ridgeback Integration
-sidebar_label: Integration
-sidebar_position: 2
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import Support from "/components/support.mdx";
-
-
-
-To attach custom hardware to Ridgeback, you will have to take care of mechanical mounting, electrical
-supply, and software integration. This guide aims to equip you with respect to these challenges.
-
----
-
-### Mechanical Mounting
-
-When determining mechanical mounting, you can use the Standard mounting pattern on the Ridgeback.
-At this time, the "PACS™" mounting system is not available for Ridgeback.
-
-#### Mechanical, Standard {#ridgeback-payload-mechanical-integration}
-
-The payload integration plate can be used to mount external payloads on top of the Ridgeback. The plate
-is made of aluminum, which allows Ridgeback to support payloads up to 100 kg (220 lbs). Ridgeback's
-batteries are positioned low in the chassis and slightly rearward of center of the robot to balance the
-weight distribution when mounting front-facing manipulator payloads. To minimize the possibility of tipping
-over, payload structures should always be mounted as close to center as possible.
-
-##### Payload Mounting Holes
-
-Located at the front-end of the mounting plate are two 5/8"-11 screw holes for mounting Baxter, UR5/UR510 manipulator
-arms, or any other payload structure. These holes are indicated in the figure below. If you purchased the Baxter
-or UR5/UR10 package from Clearpath Robotics, Ridgeback will come with the required hardware adapters to securely mount
-the payload structures to the plate.
-
-If your payload structure requires additional mounting holes or a different hole configuration, the plate can be removed
-and additional holes can be drilled. To remove the mounting plate, simply remove the screws that form the diamond pattern
-on top of the plate.
-
-
-
-
- Payload integration plate
-
-
-
-:::warning
-
-Permanent damage resulting from custom modifications to the mounting plate is not covered under warranty and may not be
-supported by Clearpath Support. Please contact our support team if you require assistance or have any questions relating
-to custom modifications.
-
-:::
-
-### Electrical Integration {#ridgeback-payload-electrical-integration}
-
-Except for bus-powered USB cameras, most payloads have separate leads for power and data.
-
-#### Data Connections
-
-The two larger holes on the left and right side of the payload integration plate allow you to pass
-electrical wires and cables from the mounted payloads into the User Bay. Electrical wires should always
-pass through the provided plastic grommets to protect against cutting and abrasion.
-
-Ridgeback's internal computer options support USB3 and Ethernet connectivity.
-
-An Ethernet switch or PoE power injector can be added to the User Bay as required.
-
-#### Connector Summary {#ridgeback-connector-summary}
-
-Several user power connectors are accessible in the User Bay for powering user payloads.
-These are summarized in the following table and described in more detail in the following sections.
-The power rails on the User Bay Power board are protected against short circuit by fuses. See the
-illustration for the connector and fuse locations.
-
-- For the High Current VBAT User Power (labelled as 24 VDC, 20 A MAX), terminate your payload's power lead with the appropriate Anderson connectors.
-- For the User Power Ports, terminate your payload's power lead with the appropriate crimps and pins.
- for the four pin Molex connector. The maximum current draw permitted on each rail is 5A.
-- For the Inverter Power, terminate your payload's power lead with the appropriate Anderson connectors.
-
-| Port (see Figure) | MCU board connector | Mating connector | Crimp terminals | Crimping tool |
-| :--------------------------- | :----------------------------------------------------------------------- | :------------------------------------------------- | :----------------------------------------------------------- | :--------------- |
-| High Current VBAT User Power | Anderson PP15/45 1327-BK (red) + 1327G6-BK (black) + Anderson 261G2-LPBK | Anderson PP15/45 1327-BK (red) + 1327G6-BK (black) | Anderson 262G2-LPBK (AWG 16-20) or 261G3-LPBK (AWG 10-14) | Anderson 1309G8 |
-| User Power Ports | Molex 0039301040 | Molex 0039012040 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-| Inverter Power | Anderson 1327G8-BK (blue) + 1327G6-BK (black) | Anderson 1327G8-BK (blue) + 1327G6-BK (black) | Anderson 262G2-LPBK (AWG 16-20) or 261G3-LPBK (AWG 10-14) | Anderson 1309G8 |
-
-
-
-
- User power board
-
-
-
-#### User Power Connections
-
-Similar to the data connections, power leads may be brought through the two larger holes on the left and
-right side of the payload integration plate, and connected to the power ports in the User Bay.
-The following are available as user power:
-
-- Unregulated VBAT power (25.6 V nominal) available in two ways:
- - High Current VBAT User Power (20 A max)
- - User Power ports: 5 A, shared across the User Power ports
-- Regulated 12 V power: 5 A, shared across the User Power ports
-- Regulated 5 V power: 5 A, shared across the User Power ports.
-
-:::caution
-
-Each User Power Port (Molex 0039301040) has a shared ground (GND) pin with a maximum current rating of 8 A. Ensure
-that the combined current draw for the VBAT, 12 V, and 5 V pins for the corresponding GND
-pin does not exceed 8 A.
-
-:::
-
-:::caution Unregulated Power Rail
-
-The unregulated battery output may range from as low as 20 VDC up to 30 VDC depending on the state of charge of
-the battery and the electrical loading on the system. Ensure any accessories connected to that rail are able to
-deal with unregulated battery voltages.
-
-:::
-
-:::warning Risk of Fire
-
-For continued protection against risk of fire, always replace fuses only with those of the same type and rating.
-
-:::
-
-#### Optional External Motion Stop {#ridgeback-external-motion-stop}
-
-In addition to the built-in Motion Stop button, an external motion-stop latching button/switch can be added that has similar functionality.
-Electrically, the external motion-stop latching button/switch can be connected to the 4-pin MCU connector labelled `E-STOP BREAKOUT` using
-a mating connector. This 4-pin connector is the same as the one used for the User Power Ports. Refer to
-[Connector Summary](#ridgeback-connector-summary) for details.
-
-The four pins should be connected as follows:
-
-- 1-2: to external motion-stop breakout
- - To engage motion-stop: press and release the latching button/switch (3.3 V)
- - To clear motion-stop: ensure the button is released on the external motion stop, then press and release the Motion Stop button on the
- Ridgeback unit to clear the motion-stop
-- 3-4: short these pins to indicate that external motion-stop is present
-
-### Software Integration
-
-
-
-Refer to the following for more details:
-
-- [Computers](../../accessories/computers/computers.mdx)
-- [Sensors](../../accessories/sensors/sensors.mdx)
-- [Manipulators](../../accessories/manipulators/manipulators.mdx)
-- [Accessories](../../accessories/add-ons/add-ons.mdx)
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
deleted file mode 100644
index 0c6d5a5a5..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/maintenance_ridgeback.mdx
+++ /dev/null
@@ -1,59 +0,0 @@
----
-title: Ridgeback Maintenance
-sidebar_label: Maintenance
-sidebar_position: 4
----
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
-import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Battery Replacement
-
-If Ridgeback's batteries need replacement, they are accessible by removing the top-plate and the insulator
-cover. Before performing any service or maintenance to the robot, the battery pack must be fully disconnected.
-The batteries weigh approximately 33 kg (73 lbs) each, so use care and caution when lifting the
-batteries out of the chassis. Please contact Clearpath Robotics regarding replacement batteries.
-
-It may also be necessary to remove the antenna cables carefully prior to removing the batteries.
-
-## Long-term storage
-
-When storing Ridgeback for long periods of time, its important to properly maintain the batteries to fully
-maximize their life. Consider one of the following two procedures when placing Ridgeback in long-term storage:
-
-- Fully charge Ridgeback, turn it off and put it into storage. Once a week, connect power to the charger
- and allow the charger to top up the battery for an hour or so.
-- Fully charge Ridgeback, turn it off and put it into storage, but leave the charger connected and powered
- the entire time Ridgeback is in storage via a wall timer that turns off for one hour every 24-hour cycle.
- The charger will monitor the battery and will automatically charge it up as needed. Note that the wall
- timer is needed since the charger times out and turns off otherwise.
-
-Please contact Clearpath Robotics for additional information about Ridgeback's batteries.
-
----
-
-## Software Maintenance {#software_maintenance}
-
-### Getting New Packages
-
-
-
-### MCU Firmware Update
-
-
-
-### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
-
-
-
----
-
-## Support {#support}
-
-
-
----
diff --git a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx b/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
deleted file mode 100644
index 36d22db48..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/indoor_robots/ridgeback/tutorials_ridgeback.mdx
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Ridgeback Tutorials
-sidebar_label: Tutorials
-sidebar_position: 4
----
-
-import ComponentIntroductionRidgeback from "/components/introduction_ridgeback.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Ridgeback Overview
-
-### Introduction
-
-Ridgeback is a rugged, indoor omnidirectional platform designed to move manipulators and other heavy
-payloads with ease and precision. These tutorials will assist you with setting up and operating your Ridgeback.
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/ridgeback).
-
-
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/learning_platforms/_category_.json b/docs_versioned_docs/version-ros2humble/robots/learning_platforms/_category_.json
deleted file mode 100644
index 1a7590254..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/learning_platforms/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Learning Platforms",
- "position": 4
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/learning_platforms/turtlebot4.mdx b/docs_versioned_docs/version-ros2humble/robots/learning_platforms/turtlebot4.mdx
deleted file mode 100644
index 2a92e737d..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/learning_platforms/turtlebot4.mdx
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: TurtleBot 4 User Manual
-sidebar_label: TurtleBot 4
-sidebar_position: 1
----
-
-import ComponentIntroductionTurtleBot4 from "/components/introduction_turtlebot4.mdx";
-
-
-
-:::note
-
-TurtleBot 4 documentation is hosted on a separate site. Use the link below
-to access the User Manual.
-
-[Link to TurtleBot 4 User Manual](https://turtlebot.github.io/turtlebot4-user-manual/)
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/legacy/_category_.json b/docs_versioned_docs/version-ros2humble/robots/legacy/_category_.json
deleted file mode 100644
index 5de5d26c3..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/legacy/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Legacy",
- "position": 6
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/legacy/pr2.mdx b/docs_versioned_docs/version-ros2humble/robots/legacy/pr2.mdx
deleted file mode 100644
index bb9636ba1..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/legacy/pr2.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: PR2
-sidebar_label: PR2
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-This page provides links to the design files for the PR2 robot, designed by Willow Garage.
-
-- [PR2 Cable Drawings (27 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_cable_drawings.zip)
-- [PR2 Electrical Manufacturing Files (113 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_electrical_mfg_files.zip)
-- [PR2 Schematics (34 MB)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_schematics.zip)
-- [PR2 CAD Files (11220 MB -- large!)](https://pr2-docs.s3.us-east-2.amazonaws.com/pr2_cad_files.zip)
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/_category_.json
deleted file mode 100644
index 74c9bd8fe..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Outdoor",
- "position": 2
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/_category_.json
deleted file mode 100644
index 79472b97e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Husky A200",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/_category_.json
deleted file mode 100644
index e5f1838f9..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Integration",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/integration_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/integration_husky.mdx
deleted file mode 100644
index f15fc20a4..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/integration_husky.mdx
+++ /dev/null
@@ -1,245 +0,0 @@
----
-title: Husky A200 Integration
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionHusky from "/components/introduction_husky.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import ComponentTableHuskyOne from "/components/table_husky_1.mdx";
-import Support from "/components/support.mdx";
-
-
-
-To attach custom hardware to Husky, you will have to take care of mechanical mounting, electrical
-supply, and software integration. This guide aims to equip you with respect to these challenges.
-
-## Mechanical Mounting
-
-When determining mechanical mounting, you have two options, both of which are described below.
-
-- the "Standard" aluminum extrusion interface
-- the "PACS™" mounting system and associated kits
-
-### Mechanical, Standard
-
-A standard Husky is delivered with a 20 X 20 aluminum extrusion frame around the top of the user bay.
-This can be used for mouning sensors, lights, and other small attachments.
-We suggest using the following items to interface with this extrusion:
-
-| Description | CPR Item | Manufacturer | Manufacturer Item |
-| :------------------------------------------------ | :-------------: | :----------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 20 X 20 Aluminum Extrusion | | Misumi | [HFSB5-2020](https://us.misumi-ec.com/vona2/detail/110302683830/?HissuCode=HFSB5-2020&PNSearch=HFSB5-2020&searchFlow=results2type&KWSearch=HFSB5-2020) |
-| 20 X 20 Plasic End Cap | 000232 | Misumi | [HFC5-2020-B](https://us.misumi-ec.com/vona2/detail/110300440510/?HissuCode=HFC5-2020-B&PNSearch=HFC5-2020-B&searchFlow=results2type&KWSearch=HFC5-2020-B) |
-| Extrusion Corner Bracket, Blind | 000228 | Misumi | [SHBLBS5](https://us.misumi-ec.com/vona2/detail/110300439970/?HissuCode=SHBLBS5&PNSearch=SHBLBS5&searchFlow=results2type&KWSearch=SHBLBS5) |
-| Extrusion Stud, M5×0.8 | 001018 | Misumi | [HNTLSN5-5-12](https://us.misumi-ec.com/vona2/detail/110302369440/?HissuCode=HNTLSN5-5-12&PNSearch=HNTLSN5-5-12&searchFlow=results2type&KWSearch=HNTLSN5-5-12) |
-| Extrusion Nut, M5×0.8 | 026955 | Misumi | [SHNTAP5-5](https://us.misumi-ec.com/vona2/detail/110302247550/?HissuCode=SHNTAP5-5&PNSearch=SHNTAP5-5&searchFlow=results2type&KWSearch=SHNTAP5-5) |
-| Anchor, Cable Tie | 010439 | McMaster | [7582K65](https://www.mcmaster.com/7582K65/) |
-| Screw, M5×0.8, Stainless Steel (assorted lengths) | 023314 - 023324 | McMaster | [Many](https://www.mcmaster.com/screws/rounded-head-screws/hex-drive-rounded-head-screws/system-of-measurement~metric/metric-18-8-stainless-steel-button-head-hex-drive-screws/thread-size~m5/finish~passivated/) |
-| Nut, M5×0.8, Stainless Steel | 015175 | McMaster | [94205A240](https://www.mcmaster.com/94205A240/) |
-
-Misumi also offers a range of configurable products for this 20 X 20 extrusion that can help with your integration.
-
-### Mechanical, PACS™
-
-[PACS™](../../../accessories/pacs) is a Clearpath Robotics standard.
-We add a grid of M5×0.8 holes onto the top plate of the robot.
-This grid of holes has a 80 mm X 80 mm spacing.
-You can create your own brackets to interface with these holes, or can use an existing Clearpath Robotics designed bracket.
-
-:::note
-
-Our [Sensors](../../../accessories/sensors) and [Accessories](../../../accessories/add-ons) pages indicate the required bracket for the particular attachment.
-
-:::
-
-Refer to the following pages for Husky brackets that can simplify your integration.
-
-- [Top Plate](kits/top_plate_husky.mdx)
-- [Weatherproofing Cover](kits/user_bay_cover_husky.mdx)
-- [Riser, Full](kits/riser_full_husky.mdx)
-- [Riser, Partial](kits/riser_partial_husky.mdx)
-- [Riser, Stiffener](kits/riser_stiffener_husky.mdx)
-- [Electronics Rack](kits/electronics_rack_husky.mdx)
-- [OutdoorNav Starter Kit](../../../accessories/add-ons/outdoornav_starter_kit.mdx)
-
----
-
-## Electrical Integration
-
-Except for bus-powered USB cameras, most payloads have separate leads for power and data.
-
-### Data Connections
-
-Data connections (USB and Ethernet) are made to the Husky computer mounted in the user bay.
-In addition, the PCIe Gen3 x16 slot may be used to supply a GPU or other attachements, as necessary.
-Additionally, the user bay may be used for an Ethernet switch, when attaching multiple
-Ethernet payloads, or for a PoE power injector as required.
-
-### User Bay Power Connections
-
-The user bay power connections are capable of supplying:
-
-- VBAT (approximately 24-29 V, unregulated) fused at 5 A
-- 12 V fused at 7.5 A
-- 24 V fused at 3 A.
-
-In total, 282 W of power is available from these User Power breakouts.
-
-:::note
-
-You can order a upgrade for your Husky, that will add 480 W of power (VBAT fused at 20 A). Each terminal comes equipped with a
-removable connector into which your payload power leads may connect.
-
-:::
-
-:::note
-
-Husky UGVs with serial numbers lower than A200-0802 have different user power connections.
-These older robots have 5 V, 12 V, and 24 V supplies, all fused at 5A.
-Your Husky's serial number is shown on a sticker, attached to the right side of the robot.
-
-:::
-
-To connect to user power:
-
-1. Expose about 5 mm of bare wire from the payload power leads and twist the exposed wire on both leads.
-2. Take 2 Molex terminals from the spare parts kit provided and insert the exposed wire and crimp the
- terminals, ensuring the wires are well secured inside the terminal, as shown below.
-3. Take 1 connector housing from the spare parts kit provided and insert the positive payload power lead
- (red) into position 4, 5, or 6 of the connector until it locks into place. The positions numbers are
- visible on the back of the plastic housing.
-4. Insert the negative payload power lead (black) into position 1, 2, or 3 of the connector until it locks
- into place.
-
-
-
-
- Crimping a wire
-
-
-
-
-
- Inserting the crimped wires into the Molex connector
-
-
-
-When connecting payloads, be sure to observe correct polarity as marked on the inside of the user bay.
-Do not exceed the specified maximum current limit of each power rail; failure to do so may result in
-damage to Husky or your payload.
-
-For more technical information on the Molex power connectors, as well as their corresponding mating connectors,
-please visit the
-[Digi-Key WM23702-ND Product Page](https://www.digikey.ca/en/products/detail/molex/0039012065/930272?s=N4IgTCBcDaIOoFkwGYDsAGMBaAcgERAF0BfIA).
-
-### Serial Connection
-
-The pinout of the DE-9 connector is shown below.
-
-| | |
-| :-----------------------------------------------------------------------: | :------------------------: |
-| | |
-
-### External Motion Stop {#husky_external_stop}
-
-
-
-
- E-stop Safety Loop connector inside the Husky user bay
-
-
-
-There is a connector labeled _E-STOP SAFETY LOOP_ that is inside the Husky's user bay.
-The connector has 2 contacts that lead to the Husky MCU circuit board.
-The MCU supplies +12 V on one of these leads, and monitors the voltage on the other lead.
-The MCU will place the Husky in a Stop state if the monitored line is below +12 V.
-
-Your robot may have a connector that adds a jumper wire between these 2 leads to complete the circuit;
-or your robot may have more Stop switches in series with this circuit.
-These additional components in series may be:
-
-- Emergency Stop buttons
-- [Wireless Stop receivers](../../../accessories/add-ons/wireless_stop_system.mdx)
-- Relays or similar PLC components
-- Manipulator control cabinets
-
-:::info
-
-- The connector labeled _E-STOP SAFETY LOOP_ is a [Switchcraft EN3P2FX](https://www.switchcraft.com/en3-harsh-environment-panel-mount-2-contact-female/en3p2fx/)
-- The mating connector is a [Switchcraft EN3C2MX](https://www.switchcraft.com/en3-harsh-environment-cable-mount-2-contacts-male/en3c2mx/) ( _Clearpath Robotics item 008075_ )
-
-:::
-
-:::note
-
-This was an optional upgrade kit on Huskies built before March 2023.
-Clearpath Robotics still offers this upgrade kit to add an external motion stop to an older Husky.
-Contact [Support](#support) for details.
-
-:::
-
-:::caution
-
-This is a single channel Stop loop, being monitored by a microcontroller.
-When the microcontroller is in a Stop state; it will open relays which supply power to the Husky's motor controllers.
-These relays are not force guided or monitored.
-
-Please contact [Support](#support) if you need more information for your application's risk assessment.
-
-:::
-
-### MCU Debug LEDs
-
-The Husky MCU PCBA comes equipped with LEDs for debugging.
-They work as follows:
-
-- **D16: HEARTBEAT**: toggles every 500 ms when the main firmware loop on the MCU is running.
-- **D7: VBAT 20 A**: illuminated if the VBAT, 20 A fuse is good.
- This LED will be off if the fuse is blown.
-- **D8: VBAT 5 A**: illuminated if the VBAT, 5 A fuse is good.
- This LED will be off if the fuse is blown.
-- **D12: 12 V 7.5 A**: illuminated if the 12 V, 7.5 A fuse is good.
- This LED will be off if the fuse is blown.
-- **D10: 24 V 3 A**: illuminated if the 24 V, 3 A fuse is good.
- This LED will be off if the fuse is blown.
-
-:::note
-
-On older revisions of the Husky MCU PCBA, the labels are different, but the functionality is similar:
-
-- D5: HEARTBEAT
-- D2: VBAT, 5 A
-- D3: 12 V, 5 A
-- D4: 5 V, 5 A
-
-:::
-
----
-
-## Software Integration
-
-
-
-Refer to the following for more details:
-
-- [Computers](../../../accessories/computers/computers.mdx)
-- [Sensors](../../../accessories/sensors/sensors.mdx)
-- [Manipulators](../../../accessories/manipulators/manipulators.mdx)
-- [Accessories](../../../accessories/add-ons/add-ons.mdx)
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/_category_.json
deleted file mode 100644
index cc3b026a7..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Kits",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx
deleted file mode 100644
index 6509fb95e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/electronics_rack_husky.mdx
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Electronics Rack
-sidebar_position: 7
----
-
-## Sales Kits
-
-:::note
-
-These kits require a Husky with a Top Plate, and a Riser.
-Refer to the [Top Plate](top_plate_husky.mdx), [Full Riser](riser_full_husky.mdx) pages for further details.
-
-:::
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :------------------------------------------------- | :-------: | :------------------------------: |
-| Installation, Kit, Electronics Rack—Husky, 100, 2U | 026956 | 027233 |
-| Installation, Kit, Electronics Rack—Husky, 100, 4U | 026957 | 027234 |
-| Installation, Kit, Electronics Rack—Husky, 100, 6U | 026958 | 027235 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :----------------------------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1A | Beam—Rack, Upright Rails, 2U | [026959](/assets/pdf/clearpath_robotics_026959.pdf) | 4 |
-| 1B | Beam—Rack, Upright Rails, 4U | [026896](/assets/pdf/clearpath_robotics_026896.pdf) | 4 |
-| 1C | Beam—Rack, Upright Rails, 6U | [026960](/assets/pdf/clearpath_robotics_026960.pdf) | 4 |
-| 2 | Nut, Extrusion, Post-Assembly, Leaf Spring—M5×0.8 X 5.8, Stainless Steel | [026955](/assets/pdf/clearpath_robotics_026955-TDS1.pdf) | 16 |
-| 3 | Screw, Cap, Round Head—M5×0.8 X 8, Stainless Steel | 023316 | 16 |
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx
deleted file mode 100644
index faf0d47b7..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_full_husky.mdx
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Full Riser
-sidebar_position: 4
----
-
-
-
-
-
-## Sales Kits
-
-:::note
-
-These kits require a Husky with a Top Plate.
-Refer to the [Top Plate](top_plate_husky.mdx) page for further details.
-
-:::
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :--------------------------------------------------- | :-------: | :------------------------------: |
-| Installation, Kit, Riser Full, With Holes—Husky, 100 | 027676 | 027677 |
-| Installation, Kit, Riser Full, With Holes—Husky, 200 | 027678 | 027679 |
-| Installation, Kit, Riser Full, With Holes—Husky, 300 | 027680 | 027681 |
-| Installation, Kit, Riser Full—Husky, 100 | 026948 | 027229 |
-| Installation, Kit, Riser Full—Husky, 200 | 026949 | 027230 |
-| Installation, Kit, Riser Full—Husky, 300 | 026950 | 027231 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :------------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1A | Plate—Integration, 670 X 590, With Holes | [027675](/assets/pdf/clearpath_robotics_027675.pdf) | 1 |
-| 1B | Plate—Integration, 670 X 590, Without Holes | [026888](/assets/pdf/clearpath_robotics_026888.pdf) | 1 |
-| 2A | Beam—93.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026921](/assets/pdf/clearpath_robotics_026921-TDS1.pdf) | 4 |
-| 2B | Beam—193.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026922](/assets/pdf/clearpath_robotics_026922-TDS1.pdf) | 4 |
-| 2C | Beam—293.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026923](/assets/pdf/clearpath_robotics_026923-TDS1.pdf) | 4 |
-| 2D | Beam—393.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026924](/assets/pdf/clearpath_robotics_026924-TDS1.pdf) | 4 |
-| 2E | Beam—493.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026925](/assets/pdf/clearpath_robotics_026925-TDS1.pdf) | 4 |
-| 2F | Beam—593.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026926](/assets/pdf/clearpath_robotics_026926-TDS1.pdf) | 4 |
-| 2G | Beam—693.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026927](/assets/pdf/clearpath_robotics_026927-TDS1.pdf) | 4 |
-| 2H | Beam—793.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026928](/assets/pdf/clearpath_robotics_026928-TDS1.pdf) | 4 |
-| 2I | Beam—893.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026929](/assets/pdf/clearpath_robotics_026929-TDS1.pdf) | 4 |
-| 2J | Beam—993.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026930](/assets/pdf/clearpath_robotics_026930-TDS1.pdf) | 4 |
-| 3 | Screw, Cap, Round Head—M5×0.8 X 14, Stainless Steel | 023319 | 8 |
-| 4 | Screw, Cap, Flat Head—M5×0.8 X 14, Stainless Steel | 023472 | 8 |
-
-## Tools
-
-- Hex Key, 3 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Fasten a Beam _(ID2)_ to the Husky's top plate using 2 screws _(ID3)_.
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 2
-
-Repeat this for the 3 remaining Beams.
-
-### Step 3
-
-Place the Riser's Plate on top of the Beams.
-The top of this Plate has the countersink features.
-The plate is symmetrical, so there is not a front / back side.
-
-### Step 4
-
-Fasten the Plate using 8 screws _(ID4)_
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx
deleted file mode 100644
index fddaf5f52..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_partial_husky.mdx
+++ /dev/null
@@ -1,91 +0,0 @@
----
-title: Partial Riser
-sidebar_position: 5
----
-
-
-
-
-
-## Sales Kits
-
-:::note
-
-These kits require a Husky with a Top Plate.
-Refer to the [Top Plate](top_plate_husky.mdx) page for further details.
-
-:::
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :------------------------------------------- | :-------: | :------------------------------: |
-| Installation, Kit, Riser Partial—Husky, 100 | 026932 | 027236 |
-| Installation, Kit, Riser Partial—Husky, 200 | 026933 | 027237 |
-| Installation, Kit, Riser Partial—Husky, 300 | 026934 | 027238 |
-| Installation, Kit, Riser Partial—Husky, 400 | 026935 | 027239 |
-| Installation, Kit, Riser Partial—Husky, 500 | 026936 | 027240 |
-| Installation, Kit, Riser Partial—Husky, 600 | 026937 | 027241 |
-| Installation, Kit, Riser Partial—Husky, 700 | 026938 | 027242 |
-| Installation, Kit, Riser Partial—Husky, 800 | 026939 | 027243 |
-| Installation, Kit, Riser Partial—Husky, 900 | 026940 | 027244 |
-| Installation, Kit, Riser Partial—Husky, 1000 | 026941 | 027245 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :------------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1 | Plate—Integration, 110 X 590 | [026887](/assets/pdf/clearpath_robotics_026887.pdf) | 1 |
-| 2A | Beam—93.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026921](/assets/pdf/clearpath_robotics_026921-TDS1.pdf) | 4 |
-| 2B | Beam—193.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026922](/assets/pdf/clearpath_robotics_026922-TDS1.pdf) | 4 |
-| 2C | Beam—293.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026923](/assets/pdf/clearpath_robotics_026923-TDS1.pdf) | 4 |
-| 2D | Beam—393.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026924](/assets/pdf/clearpath_robotics_026924-TDS1.pdf) | 4 |
-| 2E | Beam—493.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026925](/assets/pdf/clearpath_robotics_026925-TDS1.pdf) | 4 |
-| 2F | Beam—593.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026926](/assets/pdf/clearpath_robotics_026926-TDS1.pdf) | 4 |
-| 2G | Beam—693.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026927](/assets/pdf/clearpath_robotics_026927-TDS1.pdf) | 4 |
-| 2H | Beam—793.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026928](/assets/pdf/clearpath_robotics_026928-TDS1.pdf) | 4 |
-| 2I | Beam—893.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026929](/assets/pdf/clearpath_robotics_026929-TDS1.pdf) | 4 |
-| 2J | Beam—993.5 X 20 X 40, T-slot, 4X M5×0.8, Aluminum, Black | [026930](/assets/pdf/clearpath_robotics_026930-TDS1.pdf) | 4 |
-| 3 | Screw, Cap, Round Head—M5×0.8 X 14, Stainless Steel | 023319 | 4 |
-| 4 | Screw, Cap, Flat Head—M5×0.8 X 14, Stainless Steel | 023472 | 4 |
-
-## Tools
-
-- Hex Key, 3 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Fasten a Beam _(ID2)_ to the Husky's top plate using 2 screws _(ID3)_.
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 2
-
-Repeat this for the remaining Beam, adding the Beam to the other side of the robot, but in the same attachment row.
-
-### Step 3
-
-Place the Riser's Plate on top of the Beams.
-The top of this Plate has the countersink features.
-The plate is symmetrical, so there is not a front / back side.
-
-### Step 4
-
-Fasten the Plate using 4 screws _(ID4)_
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx
deleted file mode 100644
index fe8205352..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/riser_stiffener_husky.mdx
+++ /dev/null
@@ -1,88 +0,0 @@
----
-title: Riser Stiffener
-sidebar_position: 6
----
-
-
-
-
-
-## Sales Kits
-
-:::note
-
-These kits require a Husky with a Top Plate, and a Riser.
-Refer to the [Top Plate](top_plate_husky.mdx), [Full Riser](riser_full_husky.mdx), and [Partial Riser](riser_partial_husky.mdx) pages for further details.
-
-:::
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :----------------------------------------------------------------- | :-------: | :------------------------------: |
-| Installation, Kit, Attachment Tower Stiffener—Husky, Vertical, 144 | 027487 | 027482 |
-| Installation, Kit, Attachment Tower Stiffener—Husky, Vertical, 224 | 027488 | 027483 |
-| Installation, Kit, Attachment Tower Stiffener—Husky, Vertical, 304 | 027489 | 027484 |
-| Installation, Kit, Attachment Tower Stiffener—Husky, Vertical, 384 | 027490 | 027485 |
-| Installation, Kit, Attachment Tower Stiffener—Husky, Vertical, 464 | 027491 | 027486 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :----------------------------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1A | Beam, 45°—144 X 20 X 20, T-slot, Aluminum | [027492](/assets/pdf/clearpath_robotics_027492-TDS1.pdf) | 2 |
-| 1B | Beam, 45°—224 X 20 X 20, T-slot, Aluminum | [027479](/assets/pdf/clearpath_robotics_027479-TDS1.pdf) | 2 |
-| 1C | Beam, 45°—304 X 20 X 20, T-slot, Aluminum | [027493](/assets/pdf/clearpath_robotics_027493-TDS1.pdf) | 2 |
-| 1D | Beam, 45°—384 X 20 X 20, T-slot, Aluminum | [027494](/assets/pdf/clearpath_robotics_027494-TDS1.pdf) | 2 |
-| 1E | Beam, 45°—464 X 20 X 20, T-slot, Aluminum | [027495](/assets/pdf/clearpath_robotics_027495-TDS1.pdf) | 2 |
-| 2 | Screw, Cap, Socket Head—M5×0.8 X 8, Stainless Steel | 023149 | 4 |
-| 3 | Nut, Extrusion, Post-Assembly, Leaf Spring—M5×0.8 X 5.8, Stainless Steel | [026955](/assets/pdf/clearpath_robotics_027492-TDS1.pdf) | 2 |
-| 4 | Nut, Hex, Lock, Polymer Insert—M5×0.8 X 5, Stainless Steel | 010170 | 2 |
-
-## Tools
-
-- Hex Key, 3 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Decide if you are installing the Stiffener on the front or back side of the Riser.
-
-### Step 2
-
-Clip one of the nuts _(ID3)_ into the Riser's Beam, on the side where you will be installing the Stiffener.
-
-### Step 3
-
-Loosely attach the 45° Beam to the nut using a screw _(ID3)_.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 4
-
-Align the 45° beam with its mating hole on the Husky's Top Plate
-
-### Step 5
-
-Add a screw _(ID2)_ thru the Stiffener and Top Plate, with the screw's head facing up.
-
-### Step 6
-
-Tighten the joint by adding a hex nut _(ID4)_ to the bottom of the Husky's Top Plate.
-Torque the nut to 5 N·m.
-
-### Step 7
-
-Tighten the screw from Step 3.
-
-### Step 8
-
-Repeat steps 1 - 7 for the second Stiffener.
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx
deleted file mode 100644
index 144d4dce6..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/top_plate_husky.mdx
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Top Plate
-sidebar_position: 2
----
-
-
-
-
-
-## Sales Kits
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :-------------------------------------------- | :-------: | :------------------------------: |
-| Installation, Kit, Attachment Top Plate—Husky | 026942 | 027227 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :--------------------------------------------------------- | :-------------------------------------------------: | :------: |
-| 1 | Plate—670 X 590 | [026359](/assets/pdf/clearpath_robotics_026359.pdf) | 1 |
-| 2 | Angle, Bracket—564 X 25 X 25 | [007845](/assets/pdf/clearpath_robotics_007845.pdf) | 2 |
-| 3 | Screw, Cap, Socket Head—M5×0.8 X 14, Stainless Steel | 023152 | 4 |
-| 4 | Screw, Cap, Flat Head—M5×0.8 X 16, Stainless Steel | 023473 | 12 |
-| 5 | Nut, Hex, Lock, Polymer Insert—M5×0.8 X 5, Stainless Steel | 010170 | 12 |
-
-## Tools required
-
-- Wrench, 8 mm
-- Hex Key, 3 mm
-- Hex Key, 4 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Remove the old top plate or 20 X 20 aluminum extruision from the top of your Husky.
-
-### Step 2
-
-Remove the 4 screws on the sides of the Husky (2 per side).
-
-### Step 3
-
-Install the two Angle Brackets _(ID2)_ onto the bottom of the Plate _(ID1)_.
-The top side of the plate has the countersink features to the 12 mounting holes.
-Use the 12 screws _(ID4)_ and nuts _(ID5)_ to attach the Angle brackets to the Plate.
-Torque to 5 N·m
-
-:::tip
-
-Fasteners should be turned slowly to prevent galling of the stainless steel fasteners.
-Do not exceed 0.5 revolution per second when the fastener is nearly tight.
-
-:::
-
-### Step 4
-
-Place the asesmbly onto the Husky.
-The Husky's width may be larger than the assembly.
-It is easiest to start at the back of the Husky, and slowly rotate the assembly onto the Husky.
-You may need to loosen the 12 fastener connections from step 3 to get the assembly to fit onto the Husky.
-
-### Step 5
-
-Fasten the assembly on the Husky using 4 screws _(ID3)_.
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 6
-
-Re-torque any fasteners from step 3 that you loosened to ease installation of the assembly onto the Husky.
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx
deleted file mode 100644
index eae4fc009..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/integration_husky/kits/user_bay_cover_husky.mdx
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: User Bay Cover
-sidebar_position: 3
----
-
-
-
-
-
-## Sales Kits
-
-:::note
-
-These kits require a Husky with a Top Plate.
-Refer to the [Top Plate](top_plate_husky.mdx) page for further details.
-
-:::
-
-| Description | Sales Kit | Installation Kit, With Fasteners |
-| :------------------------------------------------------------ | :-------: | :------------------------------: |
-| Installation, Kit, Cover, User Bay—Husky, Blank | 026947 | 027228 |
-| Installation, Kit, Cover, User Bay—Husky, Connectors | 027255 | 027254 |
-| Installation, Kit, Cover, User Bay—Husky, Fans and Connectors | 027194 | 027250 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :-------------------------------------------------- | :-------------------------------------------------: | :------: |
-| 1A | Plate—Connector Bulkhead, Blank | [026855](/assets/pdf/clearpath_robotics_026855.pdf) | 1 |
-| 1B | Plate—Connector Bulkhead, Connector Cutouts | [027256](/assets/pdf/clearpath_robotics_027256.pdf) | 1 |
-| 1C | Plate—Connector Bulkhead, Fan and Connector Cutouts | [027195](/assets/pdf/clearpath_robotics_027195.pdf) | 1 |
-| 2 | Gasket—Connector Bulkhead, Rubber | [029427](/assets/pdf/clearpath_robotics_029427.pdf) | 1 |
-| 3 | Screw, Cap, Round Head—M5×0.8 X 8, Stainless Steel | 023316 | 18 |
-| 4 | Washer—Ø5.3 X Ø10 X 2.36, Rubber | [029278](https://www.mcmaster.com/94733a413/) | 18 |
-| 5 | _(Optional)_ Fan Guard—60 mm | [011155](https://www.mcmaster.com/19155K3/) | 2 |
-
-## Tools
-
-- Hex Key, 3 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Place the Gasket _(ID2)_ on the Husky's Top Plate.
-
-### Step 2
-
-Place the Connector Plate _(ID1)_ on the Gasket.
-
-### Step 3
-
-Use 18 screws _(ID3)_ and washers _(ID4)_ to fasten the Connector Plate to the Husky.
-Torque these screws to 5 N·m.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/maintenance_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/maintenance_husky.mdx
deleted file mode 100644
index 9c59ceac0..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/maintenance_husky.mdx
+++ /dev/null
@@ -1,280 +0,0 @@
----
-title: Husky A200 Maintenance
-sidebar_label: Maintenance
-sidebar_position: 5
----
-
-import ComponentReplacingTireOrInnerTube from "/components/maintenance_husky/maintenance_husky_tire_and_inner_tube.mdx";
-import ComponentUpdatingPumaFirmware from "/components/maintenance/firmware_update_puma.mdx";
-import ComponentLeadAcidBatteryCare from "/components/maintenance/lead_acid_battery_care.mdx";
-import ComponentLeadAcidBatteryCareTips from "/components/maintenance/lead_acid_battery_care_tips.mdx";
-import ComponentBillOfMaterialsNote from "/components/maintenance/bill_of_materials_note.mdx";
-import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
-
-
-
----
-
-## Common Replacement Items {#husky_maintenance_common_replacement_items}
-
-
-
-| Description | CPR Item | Manufacturer | Manufacturer Item | Distributor | Distributor Item |
-| :------------------------- | :------- | :---------------------- | :-------------------- | :---------- | :--------------- |
-| Battery | 005670 | Clearpath Robotics | - | - | - |
-| Battery Charger | 000597 | Clearpath Robotics | - | - | - |
-| Connector, Mini-fit-jr | 022207 | Molex | 39-01-2065 | Digi-Key | WM23702-ND |
-| Contact Crimp, Mini-fit-jr | 022207 | Molex | 40-13-0852 | Digi-Key | WM24935-ND |
-| Fuse, 3 A | 020411 | Littelfuse | 0287003.PXCN | Digi-Key | F4193-ND |
-| Fuse, 5 A | 006745 | Littlefuse | 0287005.PXCN | Digi-Key | F4197-ND |
-| Fuse, 7.5 A | 025899 | Littelfuse | 028707.5PXCN | Digi-Key | F4198-ND |
-| Fuse, 20 A | 025898 | Littelfuse | 0287020.PXCN | Digi-Key | F4201-ND |
-| Fuse, 30 A | 025896 | Littelfuse | 0299030.ZXNV | Digi-Key | F1036-ND |
-| MCU circuit board | 027104 | Clearpath Robotics | - | - | - |
-| Motor, standard | 005063 | Midwest Motion Products | S22-346F-24V GP52-079 | - | - |
-| Motor, high torque | 007449 | Midwest Motion Products | S22-346F-24V GP52-150 | - | - |
-| Tire | 000269 | Carlisle | 5100201 | - | - |
-| Tire's inner tube | 000435 | Carlisle | 323790 | - | - |
-
----
-
-## Chassis
-
-Husky is an all-terrain robot, but it is not waterproof.
-Care should be taken that no part of the main chassis is ever submerged in water.
-When the chassis becomes wet or dirty, wipe it down with a damp cloth and dry with a towel.
-
-If water is suspected to have entered the Husky A200 chassis, remove the battery and allow Husky to fully dry
-for a minimum of 24 hours.
-
-:::note
-
-Clearpath Robotics offers a Waterproofing Kit for Husky.
-This includes a top cover for the user bay, sealed drivetrain bearings, and rubber foam tape on all the panel seams.
-
-:::
-
----
-
-## Checking Drivetrain Health
-
-Depending on the environment in which the robot is used in and duty cycle,
-the robot drivetrain may require maintenance during its life. Maintenance
-activities can include gearhead replacement, tire tread replacement, motor
-brush replacement, belt replacement, bearing replacement, etc.
-
-It is recommended that the user perform an auditory inspection of the
-robot drivetrain once per month. Take note of any clicking, grinding or
-irregular skipping sounds while the robot is moving. Note that some clicking
-in the gearheads is normal during stops and starts, due to backlash between
-the gears.
-
----
-
-## Wheels
-
-Tire pressure may change with temperature and should be checked monthly
-with a pressure gauge. Inspecting tires, releasing pressure, and inflating
-tires are completed through the tire's inflation stem.
-Tire pressure should not exceed 137 kPa (20 psi), and lower pressure may be desired based on terrain requirements.
-A monthly visual inspection of the tire treads is also recommended.
-Replacement wheel assemblies can be purchased from Clearpath Robotics and
-can be installed by the user.
-
-:::tip
-
-Husky's wheels can handle a range of different terrains, but work best when inflated to the proper pressure.
-Lower tire pressures, for example 68.5 kPa (10 psi), ensure better traction in rough and varied terrain, where rocks
-or other obstacles may be encountered. This has the adverse effect of lowering drivetrain efficiency and decreasing
-battery charge, so high pressures up to a maximum of 137 kPa (20 psi) should be used when driving on flat surfaces.
-
-Lower tire pressuses also reduce the effective diameter of the wheel, and will impact your odometry readings.
-Odometry is calculated using the average diameter of a tire inflated to 137 kPa (20 psi).
-
-:::
-
----
-
-## Replacing Tire or Inner Tube
-
-
-
----
-
-## Lead-Acid Battery Care
-
-Husky's default power supply is a sealed 24 V lead-acid battery (VRLA), providing 20 Ah of charge.
-These tips are intended to help keep your Husky Lead-Acid Battery in tip-top shape.
-With proper maintenance, the battery should maintain the majority of its capacity for hundreds of cycles.
-
-
-
-Your robot's battery charger works in 3 stages:
-
-1. Constant current charging
-2. Topping charge
-3. Float charge
-
-The bulk of the capacity (70%) is regained during the first stage.
-
-It is important to let the charger complete all 3 stages whenever possible, to help maintain the life of the battery.
-The initial stage will take 5 - 7 hours, and a complete charge may take up to 14 hours.
-
-
-
-
-
-
-
----
-
-## Lithium Battery Care
-
-If your Husky has an upgrade to lithium batteries, note the required maintenance below.
-
-### Balancing Lithium Batteries
-
-The Husky's batteries must be balanced on a regular basis to ensure accurate
-feedback, consistent performance, and long life. If the batteries are
-allowed to fall out of balance, they will become unevenly loaded. This can
-lead to back-feeding between batteries, reduced charge-holding capacity
-for the system as a whole, and increased stress on both batteries.
-If the imbalance becomes severe enough, one of the system batteries
-will enter a protective state and disconnect itself from the system.
-Once the battery enters this state there is a limited time window to
-recover it. If that window expires the battery will become irreversibly
-damaged with no possibility of recovery.
-
-Battery balancing is a slow process that will occur automatically when
-the fully-charged batteries are held at their float voltage. Because the
-automatic charger will shut off when it determines that the batteries are
-fully charged, the system cannot be balanced using the autocharge dock.
-The manual charger must be used.
-
-To perform a "quick" balance, leave the robot plugged into the manual
-charger overnight. A quick balance is recommended at least once per week.
-A full balance of 24+ hours is recommended at least once per month.
-
-Contact Clearpath Robotics for assistance with recovering a battery that
-has entered a protective state.
-
-### Checking Lithium Battery Health
-
-A regularly-balanced battery system can be recharged thousands of times
-before degrading. Even with good battery maintenance, the battery will
-lose capacity over time. This results in reduced runtime and driving
-range for your Husky. This translates to reduced run-time and
-range. The robot will need to be recharged more frequently and overall
-system availability will be reduced.
-
-It is recommended that the system operator review runtime performance
-once per year to determine whether battery replacement is required.
-Runtime measurements should be taken immediately after a full balancing
-operation. Battery replacement is performed by Clearpath Robotics and
-is subject to battery availability. Replacement batteries may be
-purchased in advance and warehoused at Clearpath for future use.
-
----
-
-## Replacing Fuses
-
-You Husky's MCU has fuses that can be changed through the rear battery access panel.
-The large battery input fuse is on the other side of the MCU, so you will need to remove Husky's metal panels to access this fuse.
-
-:::caution
-
-Refer to the white lettering on the circuit board for what rating of fuse to replace in the fuse holder.
-
-The [Common Replacement Items](#husky_maintenance_common_replacement_items) section of this page shows where you can purchase new fuses.
-
-:::
-
-
- Click to expand
-
-
-
-
- Husky's rear battery access
-
-
-
-
-
-
-
-
- User power fuses
-
-
-
-
-
-
-
-
- Main battery fuse
-
-
-
-
-
----
-
-## Software Maintenance {#software_maintenance}
-
-### Getting New Packages
-
-
-
-### MCU Firmware Update
-
-Customer updates of Husky firmware are not supported at this time. Contact [Support](#support) if
-Husky firmware updates are needed.
-
-### Motor Controller Firmware Update {#maintenance_husky_motor_controller_firmware}
-
-
-
-### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
-
-
-
----
-
-## Support {#support}
-
-
-
----
-
-## Future Work
-
-### Components that may require replacement
-
-- Battery
-- MCU
-- PUMA
-- Gearmotor
-- Drive Belt
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/troubleshooting_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/troubleshooting_husky.mdx
deleted file mode 100644
index 6178e9fe1..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/troubleshooting_husky.mdx
+++ /dev/null
@@ -1,225 +0,0 @@
----
-title: Husky A200 Troubleshooting
-sidebar_label: Troubleshooting
-sidebar_position: 6
----
-
-import ComponentSupportIntroduction from "/components/support_introduction.mdx";
-import Support from "/components/support.mdx";
-
-
-
-
- Rear of a Husky
-
-
-
-
-
----
-
-## Status lights
-
-### `COMM` light on the rear panel is red
-
-A red COMM light means the Husky's computer to microcontroller serial connection is not established.
-This serial connection requires:
-
-- The computer to be on
-- The USB-Serial cable to be functioning properly.
- A functioning cable will appear in Ubuntu as `/dev/ttyUSB` or `/dev/ttyACM`
-- The serial port has been given permissions in Linux.
-- The MCU's microcontroller is on.
-- The MCU has Husky's firmware installed on it.
-- Functioning connections from the USB-Serial cable to the MCU's microcontroller.
- (soldered connectors, PCBA traces, microcontroller's soldered pins)
-
-If your robot was functioning recently, the most common causes are:
-
-- The robot's computer is not powered, or is still booting.
- Wait 60 seconds after startup to see if the computer-to-MCU connection starts after the computer turns on.
- If not, connect to the computer with SSH, or using a computer monitor to see if the computer is running.
-- The USB-Serial cable is not connected.
- Check that the USB end is seated in the robot's computer.
- Check that the DE-9 end is seated on it's [jack in the Husky user bay](user_manual_husky.mdx#onboard-computer-setup).
-- Someone has changed the robot.yaml configuration file. You can review the robot.yaml by running:
- ```
- nano /etc/clearpath/robot.yaml
- ```
-
-### `COMM` light is yellow
-
-A yellow COMM light indicates that there is a functioning Serial connection between the robot's computer and MCU's microcontroller, but there is a ROS software error on the computer.
-The common causes for this error are:
-
-- The Husky's motion-stop button has been pressed. Twist the red button on the back of the Husky clockwise to release the motion-stop.
- You can confirm the motion-stop state in ROS by running:
- ```
- rostopic echo /status
- ```
-- The Husky's lockout keyswitch is in the _Locked_ position.
- Use the included key to turn the lockout to the _Unlocked_ position.
-
-### `COMM` light flickers
-
-This frequently happens when the MCU is not receiving motion commands fast enough.
-Increase your published motion command in ROS to at least 10 Hz.
-
-```
-rostopic pub -r 10 /cmd_vel ...
-```
-
-:::note
-
-The maximum command frequency that Husky accepts is 50 Hz.
-
-:::
-
-### `ERR` light is on
-
-This light indicates a General Error.
-It is red when the Husky is in a motion-stop state, has insufficient battery voltage, or an if there is unspecified software error.
-
-### `STOP` status light is on
-
-1. Twist the red stop button at the back of the Husky.
-2. Confirm that the robot is not locked out.
-3. Confirm that all external stop devices are functioning, and that their related switches and relays are closed.
- You may need to use a multimeter to test voltage between the external stop connector and each of these external stop switches.
- Refer to the [External Stop](integration_husky/integration_husky.mdx#husky_external_stop) section for details.
-
-:::note
-
-You can confirm the motion-stop state in ROS by running:
-
-```
-rostopic echo /status
-```
-
-:::
-
-### Power button's blue light is not on
-
-The power button on the back of Husky has a blue light that turns on when the button is pressed, indicating that the Husky is receiving power.
-This light will turn on if the switch is receiving power, there is no sofware controlling it.
-For the button to turn on:
-
-1. The Husky needs to have a charged battery installed.
-2. The main fuse on the Husky's MCU needs to be functioning.
-3. The ribbon cable between the MCU and switch PCBA needs to be fully seated on both ends.
-4. The connector on the switch's cable needs to be fully seated on the switch's PCBA.
-
-We have not seen these connections fail, even in applications with lots of vibration.
-The most common fix for this issue is to check that battery is charged, and that it's power cable is seated in the Husky's MCU.
-
-### Battery indicator is flashing
-
-1. Battery voltage is too low for Husky to drive the motors.
-2. Charge the battery and try again.
-
-### Battery indicator only shows 50% charge with a fresh battery
-
-The battery indicator is controlled by the Husky MCU's microcontroller, based on a voltage measurement of the battery.
-The controls program was designed for a lithium battery.
-_24 V lithium batteries_ reach a peak voltage of 29 V.
-Our Standard _24 V lead-acid battery_ does not reach as high of a voltage, so the MCU's microcontroller thinks the battery is not fully charged.
-
-There is no way to change this behaviour on your Husky.
-
----
-
-## Mobility
-
-### Husky experiences momentary drops in communication, or Husky's velocity has an inconsistent jumping motion
-
-It's possible the robot has reached the thermal limit, or current limit.
-The maximum current limits are set to 26 A, however, as the motors are only rated for 10.7 A continuous, anything above that will trigger the current limit eventually, the higher above this limit, the more quickly it will trigger.
-If you are unsure whether this is the case, feel free to contact \ with a rosbag of your system.
-
-:::note
-
-Clearpath Robotics also offers a high torque upgrade if more torque is required for your project.
-
-:::
-
-### Husky rolls on a slope
-
-Husky's wheels are always connected to the motors.
-When you send a motion command with `/cmd_vel`, the Husky's MCU subscribes to that message, and relays a command to the Husky's motor controllers.
-These motor controllers change the voltage across the DC brushed motors, causing a mechanical torque at the wheels.
-
-When you stop publishing to `/cmd_vel`, ROS starts publishing a default value to `/cmd_vel` of zero velocity.
-At this point, the motor controllers are not attempting to change the Husky's velocity using electrical power.
-When the Husky's velocity is near 0 m/s, the motor controllers will use the motor's copper windings as a resistor.
-This is why your Husky will roll on a slope, since the resistive torque of the copper windings is less than the gravitational force on the robot.
-
-:::note
-
-The `/twist_mux` topic controls to priority of `/cmd_vel` messages.
-
-:::
-
-:::tip
-
-If this amount of rolling is unacceptable, you can update the motor controller's firmware to a version that applies holding torque.
-The process to update the firmware is detailed on our [Husky Maintenance page](maintenance_husky.mdx#maintenance_husky_motor_controller_firmware).
-
-:::
-
-Your Husky will roll if:
-
-- The Husky's motion-stop button is pressed.
-- Husky's motor controllers are receiving a zero velocity command, rather than a small value like 0.01 m/s.
-- The MCU is not functioning.
- This will appear as other issues, such as the status lights not illuminating.
-- The computer is not communicating with the MCU.
- This will appear as a red COMM light on the rear panel.
-- A motor shaft is broken.
-
----
-
-## Networking
-
-### Not getting Wi-Fi internet connection
-
-Refer to the [Networking page](../../../ros/networking/overview.mdx).
-
-### Cannot connect to the robot's computer over a network cable
-
-Reter to the [Networking page](../../../ros/networking/overview.mdx).
-
----
-
-## Computer
-
-### The computer does not automatically start
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
-### The computer keeps reverting to old BIOS settings
-
-Refer to the [Mini ITX troubleshooting page](../../accessories/computers/mini_itx.mdx).
-
----
-
-## ROS
-
-### ROS package is not starting
-
-Verify the upstart logs, `/var/log/upstart/husky_core.log`, to see if there are any error during upstart.
-
-### Sensors are not turning on
-
-1. Check that the sensor's User Power connector has the correct voltage.
-2. If the voltage is correct, then review the [Troubleshooting section for the related sensor](../../accessories/sensors/sensors.mdx).
-
-### A ROS package isn't starting
-
-1. Verify the upstart logs, `/var/log/upstart/husky_core.log` to see if there are any error during upstart.
-
-## If the Issue Persists
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/tutorials_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/tutorials_husky.mdx
deleted file mode 100644
index 13816f29a..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/tutorials_husky.mdx
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Husky A200 Tutorials
-sidebar_label: Tutorials
-sidebar_position: 4
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionHusky from "/components/introduction_husky.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Husky Overview
-
-### Introduction
-
-Husky is a rugged, outdoor-ready unmanned ground vehicle (UGV), suitable for research and rapid prototyping applications.
-These tutorials will assist you with setting up and operating your Husky.
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/husky).
-
-
-
-## Jetson Installation
-
-Refer to the [Jetson](../../accessories/computers/jetson/jetson_hardware/jetson_hardware.mdx) page for details on installing a Jetson in Husky.
-However, at present, ROS 2 software is not supported on Jetson in Husky.
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/user_manual_husky.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/user_manual_husky.mdx
deleted file mode 100644
index c365cbab4..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/husky/user_manual_husky.mdx
+++ /dev/null
@@ -1,402 +0,0 @@
----
-title: Husky A200 User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionHusky from "/components/introduction_husky.mdx";
-import Support from "/components/support.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-import ComponentSafetyWarning from "/components/safety_warning.mdx";
-
-
-
-## Introduction
-
-Husky is a rugged and easy-to-use unmanned ground robot for rapid prototyping and research applications.
-
-
-
-### Shipment Contents
-
-Your Husky shipment contains the following:
-
-- Clearpath Robotics Husky
-- 24 V Sealed Lead-Acid Battery Pack
-- Battery Door Cover
-- Battery Charger
-- Lockout Keys (2X)
-- Power Connectors (3X)
-
-If you purchased standard payload modules or custom integration services with Husky, then additional equipment will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Husky is built around a computer running Ubuntu (Intel-based computer or Jetson developer kit), paired with a 32-bit microcontroller MCU.
-The MCU handles power supply monitoring and motor control.
-The communication channel between the MCU and computer is a serial connection.
-
-#### Exterior Features
-
-The Husky exterior is shown below and includes:
-
-- Extruded aluminum mounting rail
-- User payload area, including user power panel
-- Front and rear bumper bars
-- Battery bay
-- Status panel
-- Power button
-- Motion Stop button and lockout
-
-
-
-
- Husky exterior, front view
-
-
-
-
-
-
- Husky exterior, rear view
-
-
-
-#### Status Panel
-
-The status panel is a display of LED indicators located on the rear of the chassis which provide information about the current status of Husky.
-The indicators are described in the table below.
-
-| Icon | Description |
-| :----------------------------------------------------------------------: | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| | **Battery Status** The four LED segments provide an approximate indication of the relative lifetime remaining in the battery. |
-| | **Communication Status** When green, Husky is receiving a stream of correctly-formatted motion commands, and is ready to drive. When yellow, Husky is receiving commands, but will not drive due to emergency stop or another error. When red, serial communications are currently timed-out. |
-| | **General Error Status** Illuminates red when Husky will not drive due to an error state. Such states include emergency stop, insufficient battery power, or an unspecified software error. |
-| | **Emergency Stop Status** Illuminates red when Husky will not drive due to the emergency stop being activated, either onboard or wireless (if available). |
-| | **Charge Indicator** Illuminates red when Husky user power is being supplied externally. |
-
-#### Buttons and Lockouts
-
-The silver button at the top of the Status Panel is used to power the Husky on and off. From the "off" state, pressing the button
-will cause the Husky to power on and a blue ring at the edge of the button will be illuminated. From the "on" state, pressing
-the button will cause the Husky to power off and the blue ring will no longer be illuminated.
-
-See [Stop button and Lockout](#husky-stop-button-and-lockout) for details of the Stop button and Lockout.
-
-#### Payloads
-
-Additional payloads such IMUs, lidars, cameras, GPS, manipulators and many more can be integrated with Husky, either as part of your Husky purchase or installed after receiving your Husky.
-You can find a list of supported packages and related documentation for payloads in this documention portal, under the [Computers](../../accessories/computers/computers.mdx),
-[Sensors](../../accessories/sensors/sensors.mdx), [Manipulators](../../accessories/manipulators/manipulators.mdx), and [Accessories](../../accessories/add-ons/add-ons.mdx) sections.
-In addition, refer to [Husky Integration](integration_husky/integration_husky.mdx) for details on how to integrate your own payload or how to integrate a payload kit from Clearpath Robotics.
-Each payload kit that ships from Clearpath Robotics comes with a custom mounting bracket and cabling for easy attachment to Husky.
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855, and is shown in the figure below.
-Husky's front is shown.
-When commanded with a positive translational velocity (forward), wheels travel in the positive X-direction.
-The direction of the axes differs from those used for roll, pitch, and yaw in aircraft, and care should be taken to ensure that data is interpreted correctly.
-
-
-
-
-
-#### Robot Equations
-
-As a starting point, Clearpath Robotics recommends using the following relationship between wheel velocity and platform velocity:
-
-$$
-v=\cfrac{v_{r}+v_{l}}{2}
-$$
-
-$$
-\omega=\cfrac{v_{r}-v_{l}}{W}
-$$
-
-$v$ represents the instantaneous translational speed of the platform and $\omega$ the instantaneous rotational speed.
-$v_\{r\}$ and $v_\{l\}$ are the right and left wheel velocities, respectively.
-$W$ is the effective track of the robot, 0.555 m.
-
-### System Specifications
-
-| Specification | Measurement |
-| :----------------------------- | :----------------------------------------------------------------------- |
-| Dimension, Length | 990 mm |
-| Dimension, Width | 670 mm |
-| Dimension, Height | 390 mm |
-| Track Width | 550 mm |
-| Wheelbase Length | 512 mm |
-| Ground Clearance | 130 mm |
-| Mass | 50 kg |
-| Maximum Payload¹ | 75 kg |
-| All-terrain Payload² | 20 kg |
-| Speed, Maximum | 1 m/s |
-| Climb Grade | 45 ° |
-| Traversal Grade / Sideslope | 30 ° |
-| Operating Temperature, Minimum | -10 °C |
-| Operating Temperature, Maximum | 40 °C (not in direct sunlight) |
-| Operating Time, Average | 3 hours |
-| Operating Time, Standby | 8 hours |
-| Battery | 20 Ah @ 24 V, sealed lead-acid |
-| Battery Charger | Short-circuit, over-current, over-voltage and reverse voltage protection |
-| Charge Time | 10 hours |
-| User Power, 2021 and older | 5 V, 12 V, V-battery, each fused at 5 A |
-| User Power, 2022 and newer | 12 V @ 7.5 A, 24 V @ 3 A, VBAT @ 5 A |
-| Communication | RS-232, 115200 baud |
-| Wheel Encoders | 78,000 ticks/m |
-| Internal Sensing | Battery Status, Wheel Odometry, Motor Currents |
-| Environmental | IP44 (base Husky); IP30 (with computer); IP55 (with weatherproofing kit) |
-
-_¹Continuous operation on relatively flat terrain with wide turns._
-_²robot climbing 30° grade with high-mounted payload, or turning in place in high-friction conditions._
-
-
-
-
-
----
-
-## Getting Started
-
-You are ready to go! This section details how to get Husky into action.
-To begin, place Husky "up on blocks" as described in the [Safety](#safety) section, making sure that the wheels are clear of the ground.
-
-For most Husky setups, there will be an Onboard Computer which is directly connected to the Husky and an Offboard Computer which is used to control Husky and gather data.
-These two computers must be set up to communicate with each other.
-
-### Onboard Computer Setup
-
-If you purchased an Onboard Computer from Clearpath Robotics with Husky, it is already installed, connected, and powered.
-If not, or to set up your own Onboard Computer, see the [Husky Tutorials](tutorials_husky.mdx).
-
-Note that the Onboard Computer must be connected to Husky's serial port, which is located in the user power panel accessible from the User Bay.
-
-
-
-
- Husky's serial port
-
-
-
-The connector is a female DE-9, suitable for connection directly to a USB-serial adaptor or to a computer serial port via a straight-through modem cable (not a null modem cable).
-How you connect the Onboard Computer to Husky depends on whether the Onboard Computer has a dedicated serial port.
-Husky is delivered with a USB-serial adaptor.
-
-### Powering Up
-
-Husky comes with the battery fully charged and installed, but disconnected for safety during shipping.
-To reconnect the battery:
-
-- Ensure Husky's main power button is in the "off" position and that stop mode is activated.
-- Using curled index fingers to grip the battery door latches, press with thumbs on the latch buttons
- and lift the battery door free of the chassis.
-- Carefully connect the battery plug to the mating connector in the fuse panel.
- Ensure that it is firmly seated and clicks into place.
- It will be difficult to connect it in the incorrect polarity.
-- Replace the battery door cover, ensuring that it clicks into place and is flush with the rear panel.
-
-
-
-
-
-To power on Husky, firmly press the power button located above the status panel.
-It will illuminate blue, and the status panel lights will show a brief test pattern.
-The `COMM` status light will turn red, as the computer is not yet communicating with Husky.
-
-The `STOP` status light will be red if the Stop button is pressed.
-If the Stop button is not pressed, press it and verify that the `STOP` light illuminates.
-Leave the platform in stop mode until it is successfully receiving commands, indicated by the `COMM` status light turning green or yellow.
-If a computer was purchased with Husky, it will be setup to interface automatically upon startup; 60-90 seconds after booting up, `COMM` status light will change from red to green (or yellow, depending on the stop mode status).
-This indicates that ROS is up on the computer and has established communications with the Husky base.
-
-### Network Configuration
-
-To get Husky connected to your local Wi-Fi network, you must first access the Onboard Computer using a wired connection to the robot.
-See the [Husky Tutorials](tutorials_husky.mdx) for details.
-
-### Connecting and Using the Controller {#controller}
-
-To use your controller, it must be paired with your Husky and powered on.
-If your purchased the Onboard Computer from Clearpath Robotics, your controller is already paired with your Husky.
-If your controller has become unpaired or if you wish to pair a new controller, following the instructions in the
-[Husky Tutorials](tutorials_husky.mdx).
-
-To teleoperate Husky, first release the motion stop. Then, referring to the following images, press the enable button (either slow or fast mode) and use the left thumbstick to drive Husky.
-
-
-
-### Using ROS
-
-Robot Operating System (ROS) is an extensible framework for controlling and working with robotic systems.
-Clearpath Robotics recommends using ROS with your robot. If this is your first time using ROS, it is strongly
-recommended to run through our series of [ROS tutorials](../../../ros) to learn
-the basics of ROS.
-
-### Battery Charging
-
-The battery shipped with Husky A200 may be charged outside the robot or while still inside of Husky.
-If charging while installed, you will need to open the access door to the battery area, and disconnect the battery from the MCU board.
-From there:
-
-1. Connect the DC output cable from the charger to the battery terminal connector.
-2. Plug the charger power cord into the charger and then into a wall receptacle.
-3. The LED light on the charger will illuminate red.
-4. When battery is fully charged, the LED light will turn green.
-5. Unplug the charger from the wall and then disconnect it from the battery.
-
-The battery charger shipped with Clearpath Robotics's lead-acid battery-powered products uses a two-state charge cycle.
-
-1. A fast, high current initial charge, until the battery voltage reaches 27.2 V.
-2. A topping charge, during which the battery charges at 27.2 V constant voltage.
-
-:::note
-
-Some older Husky chargers use a three-state charge cycle. For those older chargers, the LED light turns off
-(rather than green) when charging is complete.
-
-:::
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-Husky contains several features to protect the safety of users and the integrity of the robot.
-
-### General Warnings
-
-Husky is a rugged and high-performance robot.
-For the safety of yourself and others, always conduct initial experiments and software development with
-the robot raised off the ground. Place a wooden crate, a set of sawhorses, a sturdy storage tub, or any
-other solid flat structure having a height greater than 150 mm under Husky to keep the wheels clear of the
-ground ("up on blocks").
-
-When starting out, favour slower wheel speeds. Husky's control loops can accurately maintain velocities as low as 0.1 m/s.
-Operating at such speeds will give you more time to react if things don't go quite as you expect.
-
-When Husky is operating, keep clear of the wheels, paying particular attention to the pinch hazard which exists between each wheel and the end of the corresponding bumper bar.
-
-### Stop Button and Lockout {#husky-stop-button-and-lockout}
-
-:::warning
-
-Ensure the Stop button is accessible at all times.
-Avoid mounting payloads that extend over the rear of Husky and would occlude the Stop button.
-
-:::
-
-The motion-stop function allows a person in the physical vicinity of the robot to halt its motion and prevent re-initiation of motion.
-Power supply to Husky's motor drivers is enabled by a normally-open relay, which is closed in series with the stop switch.
-This motion-stop system is intended for use in emergency situations.
-The motion stop system should not be used as the means of controlling robot motion during regular operation.
-
-When in stop mode, the status panel stop light will illuminate red and Husky will not drive.
-The commands received during stop mode are not buffered; Husky will always act on the latest commands received.
-This means that if the commands are stopped before the stop is released, the Husky will not move.
-If the commands are continued, Husky will move at the speed commanded once the stop is released.
-
-This "Stop" function can be asserted by pressing the red stop actuator present at the rear of the Husky, opposite the status panel, as shown in the following figure.
-The motion-stop function can be reset by twisting the depressed actuator until it returns to an extended position.
-There is no second "start" action required to reset the stop function.
-The robot may begin moving again immediately after the stop actuator has returned to its extended position.
-
-
-
-
- Stop button and Lockout
-
-
-
-The lockout provides a way to secure Husky from performing any type of motion.
-When in lockout mode, the robot will still power on, but the motors will not drive.
-
-### Electrical System
-
-Husky is powered by a single 24 V sealed lead-acid battery, similar to the type found in electric wheelchairs, golf carts, and other devices.
-Husky's battery is capable of delivering 1800 W, similar to wall mains.
-This gives Husky's motors their great performance, however, it is also enough power to cause severe bodily harm.
-Please observe the following precautions:
-
-- Do not tamper with the plug attached to the battery.
-- Do not tamper with the fuse panel, except to check and change the fuses, and to connect and disconnect the battery plug.
-- Do not operate Husky without the battery door in place.
- The battery is not restrained without the door, and will come loose, damaging the fuse panel.
-- Charge the battery only with the charger provided by Clearpath Robotics.
-- Please dispose of the batteries properly.
-
-### Lifting and Transport
-
-For the safety of users and to maximize the lifetime of Husky, please observe the following when manually transporting the robot:
-
-- Husky should be lifted by two persons, firmly gripping the front and rear bumper-bars.
- The battery can be removed to lighten the load of a manual transport.
-- Ensure that Husky is in Stop mode when transporting short distances and powered off when transporting longer distances.
-- It is not advised to push Husky, as this can cause damage to the motors.
-
-### Performance Considerations
-
-Included in Husky are native software checks and limits to protect the robot.
-However, it is recommended to monitor the system's status during usage with the `/status` and `/diagnostics` topics.
-These topics provide useful information regarding voltages, currents, temperatures and general health of the system.
-
-The total current draw does not include the motors drivers; it is the current consumed by the MCU and user power ports.
-Husky's motors are rated to draw 10.7 A continuous, but they will spike to several times higher than this, particularly when traversing rough terrain and when turning on the spot.
-To reduce current draw, consider commanding wider-radius turns from your control software.
-
-The temperature is measured in the motor drivers and on the motor casings; the coils inside the motor casings cannot be measured.
-Therefore, it is important to note that the temperature measured on the motor casings is a lagging indicator of the temperature of the coils inside the casing.
-Be aware of the delay in heat propagation on the motors during heavy use.
-The thermal limit of the system is 50 °C, and the system will shut down if this limit is reached.
-Monitoring these fields over longer periods of operation will allow you to ensure that you are not putting excessive wear on Husky's motors.
-
-### Recommended Safe Work Procedures
-
-
-
----
-
-## Support
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/_category_.json
deleted file mode 100644
index 85befb884..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Jackal",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/integration_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/integration_jackal.mdx
deleted file mode 100644
index 7211fffe2..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/integration_jackal.mdx
+++ /dev/null
@@ -1,123 +0,0 @@
----
-title: Jackal Integration
-sidebar_label: Integration
-sidebar_position: 2
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import Support from "/components/support.mdx";
-
-
-
-To attach custom hardware to Jackal, you will have to take care of mechanical mounting, electrical
-supply, and software integration. This guide aims to equip you with respect to these challenges.
-
----
-
-### Mechanical Mounting
-
-When determining mechanical mounting, you can use the Standard square mounting pattern on the lid of the Jackal.
-At this time, the "PACS™" mounting system is not available for Jackal.
-
-#### Mechanical, Standard
-
-A standard Jackal is delivered with an 80 mm square mounting pattern of M5 threaded holes on its lid, which can be
-used for attaching external payloads. The mounting holes come with M5 screws pre-installed.
-You may mount your hardware directly onto the lid or you may design and mount a new plate to the lid and secure
-it to the lid using M5 screws.
-
-### Mechanical, PACS
-
-While Jackal does not yet support PACS directly, the following kits may simplify your integration.
-
-- [OutdoorNav Starter Kit](../../accessories/add-ons/outdoornav_starter_kit.mdx)
-
-### Electrical Integration {#jackal-payload-electrical-integration}
-
-Except for bus-powered USB cameras, most payloads have separate leads for power and data.
-
-#### Data Connections
-
-Data connections may be brought through the hatch and connected directly to the internal computer. Both
-of Jackal's internal computer options support USB3 and Ethernet connectivity. With the performance
-computer, the PCIe slot may be used to supply Firewire, Thunderbolt, or additional USB3 ports, as necessary.
-
-Additionally, the internal mounting area may be used for an Ethernet switch, when attaching multiple
-Ethernet payloads, or for a PoE power injector as required.
-
-#### Connector Summary
-
-The Jackal User Power Board (UPB) board provides a number of connections for power.
-These are summarized in the following table and described in more detail in the following sections.
-
-- For the High Current VBAT User Power, terminate your payload's power lead with the appropriate terminals.
-- For the User Power Ports, terminate your payload's power lead with the appropriate crimps and pins.
- for the four pin Molex connector. This option may be best if you are removing your payload from Jackal frequently.
-- For the User Power Screw Terminals, pull out the black terminal block, and use a small screwdriver to securely attach power leads to it.
- Confirm voltage and polarity before reconnecting the terminal block.
-
-| Port (see Figure) | MCU board connector | Mating connector | Crimp terminals | Crimping tool |
-| :--------------------------- | :-------------------------------------------------------------------------------------------------- | :------------------------------------------------- | :----------------------------------------------------------- | :--------------- |
-| High Current VBAT User Power | Anderson PP15/45 1327-BK (red) + 1327G6-BK (black) + Anderson PCB45 1336G1 (lower) + 1337G1 (upper) | Anderson PP15/45 1327-BK (red) + 1327G6-BK (black) | Anderson 262G2-LPBK (AWG 16-20) or 261G3-LPBK (AWG 10-14) | Anderson 1309G8 |
-| User Power Ports | Molex 0039301040 | Molex 0039012040 | Molex 0507528200 (AWG 20-22) or Molex 0503518100 (AWG 22-28) | Molex 2002184900 |
-| User Power Screw Terminals | Molex 39522-1006 | Molex 39520-0706 | N/A | N/A |
-
-
-
-
- User power board
-
-
-
-#### User Power Connections
-
-Similar to the data connections, power leads may be brought through the hatch, and connected to the User Power Board.
-The following are available as user power:
-
-- Unregulated VBAT power (25.6 V nominal, 16 A max), shared across the High Current VBAT User Power (16 A max),
- User Power Ports (8 A max per port) and the User Power Screw Terminals (15 A max)
-- Regulated 12 V power (7 A max), shared across the User Power ports (7 A max per port) and the User Power
- Screw Terminals (7 A max)
-- Regulated 5 V power (5 A max), shared across the User Power ports (5 A max per port) and the User Power
- Screw Terminals (5 A max).
-
-:::caution
-
-Each User Power Port (Molex 0039301040) has a shared ground (GND) pin with a maximum current rating of 8 A. Ensure
-that the combined current draw for the VBAT, 12V, and 5V pins for the corresponding GND
-pin does not exceed 8 A.
-
-:::
-
-#### MCU Debug LEDs
-
-The Jackal MCU circuit board comes equipped with four LEDs controlled by Jackal firmware for debugging.
-If the system is working properly, these LEDs functions as follows:
-
-- **DBG1**: toggles every 500 ms when main loop on MCU is running
-- **DBG2**: not used in normal operation; LED should be off
-- **DBG3**: not used in normal operation; LED should be off
-- **DBG4**: not used in normal operation; LED should be off
-
-### Software Integration
-
-
-
-Refer to the following for more details:
-
-- [Computers](../../accessories/computers/computers.mdx)
-- [Sensors](../../accessories/sensors/sensors.mdx)
-- [Manipulators](../../accessories/manipulators/manipulators.mdx)
-- [Accessories](../../accessories/add-ons/add-ons.mdx)
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/maintenance_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/maintenance_jackal.mdx
deleted file mode 100644
index 892efe448..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/maintenance_jackal.mdx
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Jackal Maintenance
-sidebar_label: Maintenance
-sidebar_position: 4
----
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
-import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import Support from "/components/support.mdx";
-import ComponentsWdSsdCriticalUpdate from "../../../components/maintenance/_wd_ssd_critical_update.mdx";
-
-
-
-## Software Maintenance {#software_maintenance}
-
-### Getting New Packages
-
-
-
-### MCU Firmware Update
-
-
-
-### WD Blue SA510 SATA SSD Critical Firmware Update {#wd-firmware-update}
-
-
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/user_manual_jackal.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/user_manual_jackal.mdx
deleted file mode 100644
index a7b2aa30e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/jackal/user_manual_jackal.mdx
+++ /dev/null
@@ -1,361 +0,0 @@
----
-title: Jackal User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionJackal from "/components/introduction_jackal.mdx";
-import Support from "/components/support.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-import ComponentSafetyWarning from "/components/safety_warning.mdx";
-
-
-
-## Introduction
-
-Jackal is a rugged, lightweight, fast and easy-to-use unmanned ground robot for rapid prototyping
-and research applications. Jackal includes a computer, as well as basic IMU and GPS. Standard
-perception modules are available, including URDF, simulator integration, and demonstration
-applications.
-
-
-
-### Shipment Contents
-
-Your Jackal shipment contains the following:
-
-- Clearpath Robotics Jackal
-- 270 Wh lithium battery
-- 110 VAC - 220 VAC battery charger
-- Sony PS4 Bluetooth controller
-
-If you purchased standard payload modules or custom integration services with Jackal, then additional
-equipment will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Jackal is built around a computer running Ubuntu (Intel-based computer or Jetson developer kit), paired
-with a 32-bit microcontroller MCU. The MCU handles IO, power supply monitoring and motor control, as well as supplying
-data from the integrated IMU and GPS receiver. The communication channel between the MCU and computer is a Full
-Speed USB connection, with the MCU operating as a standard serial CDC device.
-
-The communication protocol used is rosserial. An instance of the `rosserial_server` serial node is embedded
-in the `jackal_base` node, where it is connected to Jackal's kinematic controller.
-
-An internal magnetometer is available, but not recommended for use due to its location in the vehicle chassis.
-
-#### Exterior Features
-
-The Jackal exterior is shown below and includes:
-
-- 80 mm mounting pattern on the lid
-- 194 mm diameter wheels
-- Human machine interface panel (HMI)
-- Lid latches
-
-
-
-#### Human-Machine Interface (HMI) Details
-
-
-
-The human-machine-interface (HMI) panel is shown below and includes from left:
-
-| Icon | Description |
-| :---------------------------------------------------------------------: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| | **Motion Stop button**: LED is solid green when Jackal is able to drive and flashing green when the Jackal's motors are disengaged; pressing button toggles the motors between engaged and disengaged mode (further details in [Motion Stop Buttons](#jackal-stop-buttons)) |
-| | **Comms indictor**: LED is solid green when communication between the MCU and computer has been established and LED is off otherwise |
-| | **Wi-Fi indicator**: LED is solid green when Wi-Fi is connected and LED is off otherwise |
-| | **Battery indicator**: LED is solid green when the battery level is ok, solid yellow when the battery level is getting low (should be charged soon), and solid red when the battery level is critical (should be charged immediately) |
-| | **System Power button**: LED is solid blue when the system is powered on and running and the LED is flashing blue during the shutdown process; when the system is powered off, pressing the power button begins the power on process; when the system is powered on, a quick press of the power button begins a graceful shutdown and a prolonged press of the power button triggers and immediate power off of the system |
-
-
-
-
- HMI Panel
-
-
-
-#### Payloads
-
-Additional payloads such IMUs, lidars, cameras, GPS, manipulators and many more can be integrated
-with Jackal, either as part of your Jackal purchase or installed after receiving your Jackal.
-You can find a list of supported packages and related documentation for payloads in this
-documention portal, under the [Computers](../../accessories/computers/computers.mdx),
-[Sensors](../../accessories/sensors/sensors.mdx), [Manipulators](../../accessories/manipulators/manipulators.mdx),
-and [Accessories](../../accessories/add-ons/add-ons.mdx) sections. In addition, refer to [Jackal Integration](integration_jackal.mdx) for
-details on how to integrate your own payload or how to integrate a payload kit from Clearpath Robotics.
-Each payload kit that ships from Clearpath Robotics comes with a custom mounting bracket and cabling for
-easy attachment to Jackal.
-
-#### Interior Features
-
-To access Jackal's interior, actuate the latches under the front end of the lid, on the opposite end from
-the HMI. When you lift the lid, you will see Jackal's onboard lithium battery, and its two connectors.
-The large Anderson Power Pole connector is to supply power to Jackal and must be connected for
-Jackal to operate. The smaller white Molex connector allows the battery to be charged inside Jackal
-while Jackal is powered off. It is recommended to connect both. The interior components of Jackal are
-labeled below.
-
-
-
-
- Battery area inside Jackal
-
-
-
-Further, you may undo the thumbscrews which hold Jackal's computer tray to the lid. The tray lowers,
-revealing Jackal's onboard computer, user power supplies, and internal user hardware mounting area.
-The figures below illustrate the components of the tray and user power supplies.
-Note that the fused user power is available as four-pin Molex connectors, or a plug-in screw terminal
-block. For more information on integrating payloads electrically, see
-[Jackal Integration](integration_jackal.mdx#jackal-payload-electrical-integration).
-
-
-
-
- Computer and user tray
-
-
-
-
-
-
- User power supply
-
-
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855.
-
-
-
-When commanded with a positive translational velocity (forward), wheels travel in the positive X-direction.
-The direction of the axes differs from those used for roll, pitch, and yaw in aircraft, and care should be
-taken to ensure that data is interpreted correctly.
-
-
-
-### System Specifications
-
-| Specification | Measurement |
-| :-------------------- | :----------------------------------------------------------------------- |
-| Dimension, Length | 508 mm |
-| Dimension, Width | 430 mm |
-| Dimension, Height | 250 mm |
-| Ground Clearance | 65 mm |
-| Maximum Payload | 20 kg |
-| Speed, Maximum | 2.0 m/s |
-| Battery Chemistry | Lithium, 270 Wh |
-| Operating Time | 8 hours (basic usage), 2 hours (heavy usage) |
-| Charge Time | 4 hours |
-| User Power | 16 A @ VBAT (25.6 V nominal), 7 A @ 12 V, 5 A @ 5 V |
-| Communication | Ethernet, USB 3.0 |
-| Internal Sensing | Battery Status, Wheel Odometry, Motor Currents, Onboard IMU, Onboard GPS |
-| Operating Temperature | -19 to 45 °C |
-| Operating Environment | Indoor or Outdoor (designed for IP62) |
-
-
-
-
-
----
-
-## Getting Started
-
-You are ready to go! This section details how to get Jackal into action.
-To begin, place Jackal "up on blocks" as described in the [Safety](#safety) section, making sure that the wheels are clear of the ground.
-
-For most Jackal setups, there will be an Onboard Computer which is directly connected to the Jackal and an Offboard Computer
-which is used to control Jackal and gather data. These two computers must be set up to communicate with each other.
-
-### Onboard Computer Setup
-
-If you purchased an Onboard Computer from Clearpath Robotics with Jackal, it is already installed, connected, and powered.
-If not, or to set up your own Onboard Computer, see the
-[Jackal Tutorials](tutorials_jackal.mdx).
-
-Note that the Onboard Computer must be connected to the USB port on the Jackal MCU, which is accessible inside the Jackal.
-
-### Powering Up
-
-If you've just unpacked Jackal from its packaging, you may need to open it up and connect the battery.
-
-Press the power button on Jackal's HMI panel.
-The LEDs should show a test pattern, after which you will wait about 30 seconds for the internal computer to finish booting up.
-Once it has finished booting, the Comms indicator should turn green.
-This indicates that ROS is up on the computer and has established communications with the Jackal base.
-
-### Network Configuration
-
-To get Jackal connected to your local Wi-Fi network, you must first access the Onboard Computer using a wired connection to the robot.
-Open the chassis, lower the computer tray, and connect to the network port labeled STATIC with a standard
-ethernet cable. See the [Jackal Tutorials](tutorials_jackal.mdx) for details
-on completing the Wi-Fi setup.
-
-### Connecting and Using the Controller {#controller}
-
-To use your controller, it must be paired with your Jackal and powered on.
-If your purchased the Onboard Computer from Clearpath Robotics, your controller is already paired with your Jackal.
-If your controller has become unpaired or if you wish to pair a new controller, following the instructions in
-the [Jackal Tutorials](tutorials_jackal.mdx).
-
-To teleoperate Jackal, first clear the motion-stop.
-Then, power on the controller by pressing the `PS` button on the controller.
-Once the blue LED on the top of the controller goes solid, you are paired and ready to drive.
-Hold the L1 trigger button (deadman switch) and push the left thumbstick forward to drive the Jackal.
-For full speed mode, hold the R1 trigger.
-See the figure below for the Sony PS4 controls layout.
-If you are not seeing any action, refer to [Support](#jackal-support) to get in touch with support.
-
-
-
-
- PS4 Controls Layout
-
-
-
-### Using ROS
-
-
-
-### Battery Charging
-
-When finished with the Jackal, press and release the power button to power it off.
-
-Jackal's lithium battery may be charged internal to the chassis: simply plug in
-the charger to the charge port located under the rear fender. Charging will occur
-when Jackal is powered down.
-
-Alternatively, if you have multiple batteries, you can easily lift the lid and
-remove the battery for external charging. When charging externally, remove the pigtail
-which adapts the charger to the platform's weather sealed charge port.
-
-The battery is manufactured for Clearpath Robotics by AllCell Technologies. The
-pack includes integrated protections against fault due to overcurrent, overdischarge,
-and short circuit. The pack is rugged and designed for the demanding environments into
-which Jackal may be deployed.
-
-However, please take note of the following:
-
-- The pack must not be stored or operated above +60 °C or below -19 °C.
-- The pack must not be punctured or disassembled.
-- The pack should be dropped off or delivered to your local hazardous waste authority for disposal.
-- When traveling with Jackal, consult your airline's restrictions regarding lithium
- batteries. If possible, bring the pack in your carry on luggage, where it will
- be subject to normal cabin temperatures and pressures.
-
-Please contact Clearpath Robotics for additional information about Jackal's battery or
-for information about purchasing additional packs.
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-Jackal contains several features to protect the safety of users and the integrity of the robot.
-
-:::caution
-
-Jackal is a fast moving robotic platform. Please read the following notices carefully.
-
-:::
-
-### General Warnings
-
-Jackal is a rugged and high-performance robot.
-For the safety of yourself and others, always conduct initial experiments and software development with
-the robot raised off the ground. Place a wooden crate, a set of sawhorses, a sturdy storage tub, or any
-other solid flat structure having a height greater than 100 mm under Jackal to keep the wheels clear of the
-ground ("up on blocks").
-
-When starting out, favour slower wheel speeds. Jackal's control loops can accurately maintain velocities as low as 0.1 m/s.
-Operating at such speeds will give you more time to react if things don't go quite as you expect.
-
-### Motion Stop Buttons {#jackal-stop-buttons}
-
-The Motion Stop button is located on the HMI Panel at the back of Jackal.
-To engage Stop Mode, press the Motion Stop button once; you should see that the green LED by the Motion Stop button is flashing and that all four corner LEDs are flashing red.
-To disengage Stop Mode, press the Motion Stop button again; all LEDs should return to their original values.
-
-When in Stop Mode, the Jackal will not drive.
-The commands received while in Stop Mode are not buffered; Jackal will always act on the latest commands received.
-This means that if the commands are stopped before the Motion Stop button is pressed to disengage Stop Mode, the Jackal will not move.
-If the commands are continued, Jackal will move at the speed commanded once the Motion Stop button is pressed to disengage Stop Mode.
-
-Ensure that the Motion Stop button is accessible at all times.
-Avoid mounting payloads that extend over the rear of Jackal and would block access to the Motion Stop button.
-
-### Electrical System
-
-Jackal is powered by batteries capable of delivering high outputs for short durations.
-This gives Jackal's motors their great performance; however, it is also enough power to cause severe bodily harm.
-Always use caution when operating Jackal to avoid personal injury or property damage.
-To ensure safety, please observe the following precautions:
-
-- Do not tamper with the plug attached to the battery.
-- Do not tamper with the fuses, except to check and change the fuses.
-- Always replace fuses with the same type and rating to ensure continued protection against risk of fires.
-- Consult Clearpath Robotics support if you need to service the batteries.
-- Charge the battery only with the charger provided by Clearpath Robotics.
-- Please dispose of the batteries properly or return them to Clearpath Robotics to do so.
-
-### Lifting and Transport
-
-For the safety of users and to maximize the lifetime of Jackal, please observe the following when manually transporting the robot:
-
-- Ensure that Jackal's Stop Mode is engaged when transporting short distances and powered off when transporting longer distances.
-- Do not push the robot at more than 0.5 m/s (1.6 ft/s) or damage to the motor controls may occur.
-
-### Performance Considerations
-
-Included in Jackal are native software checks and limits to protect the robot.
-However, it is recommended to monitor the system's status during usage with the `/status` and `/diagnostics` topics.
-These topics provide useful information regarding voltages, currents, temperatures and general health of the system.
-
-### Recommended Safe Work Procedures
-
-
-
----
-
-## Support {#jackal-support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/_category_.json
deleted file mode 100644
index 54966dd03..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Warthog",
- "position": 1
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/_category_.json b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/_category_.json
deleted file mode 100644
index e5f1838f9..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Integration",
- "position": 3
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
deleted file mode 100644
index fb4baf658..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/integration_warthog.mdx
+++ /dev/null
@@ -1,155 +0,0 @@
----
-title: Warthog Integration
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentPacsMechanical from "/components/pacs_mechanical.mdx";
-import ComponentCommonSoftwareIntegration from "/components/common_software_integration.mdx";
-import Support from "/components/support.mdx";
-
-To attach custom hardware to Warthog, you will have to take care of mechnical mounting, electrical supply, and software integration.
-This section aims to equip you with respect to these challenges.
-
----
-
-## Mechanical {#warthog-mechanical-mounting}
-
-When determining mechanical mounting, you have two options, both of which are described below.
-
-- the "Standard" aluminum extrusion interface
-- the "PACS™" mounting system and associated kits
-
-### Mechanical, Standard
-
-A standard Warthog includes thru holes on the sides of the battery compartment.
-You can besign mounting brackets to interface with these holes.
-
-### Mechanical, PACS™
-
-
-
-Refer to the following pages for Warthog brackets that can simplify your integration.
-
-- [Extrusion Rails](kits_warthog/extrusion_rails_warthog.mdx)
-- [Extrusion Cross-Bar](kits_warthog/extrusion_crossbar_warthog.mdx)
-- [Top Plate](kits_warthog/top_plate_warthog.mdx)
-
-### Common Mechanical Integration Guidelines
-
-- 705 mm (27.75") is the maximum allowed width of any installed payload (this assumes that the payload is also centered across the width of the UGV chassis.
-- No part of the payload may extend over the sheet metal housings of the drive units or into the small 50 mm (2") gaps between the chassis and drive units.
- Damage to both the UGV and the payload will result.
-- The chassis has a removable access cover measuring 1175 mm X 667 mm (46.25" X 26.25").
- This access cover is supported underneath by two adjustable cross members.
- Regardless of payload, it is imperative that both cross members remain installed (approximately evenly spaced) to provided required support to the access cover.
- Consider that any payload installed above the top deck will prevent access to the chassis through the access cover, without first removing the installed payload.
-- The rotation of the suspension differential link in the horizontal plane will allow the payload to extend beyond the chassis top deck in both fore and aft locations.
- The amount of this payload extension (overhang) is dependent on several factors, including the weight and method of attachment of the payload as well as the terrain in which the UGV will operate.
- Ensure that the amount of overhanging payload allows the UGV to operate safely and does not contact the terrain, especially when crossing steep and/or deep gullies.
-- The available internal chassis volume is:
- - Length of 445 mm (17.5")
- - Width of 660 mm (26")
- - Height of 241 mm (9.5").
- This space is located at the center of the chassis between two battery packs.
- Consider that anything placed inside the chassis must be secured as to not move or shift during UGV operation.
-
-:::caution
-
-Permanent damage resulting from custom modifications to the mounting plate is not covered under warranty and may not be supported by Clearpath Support.
-Please contact our Support team if you require assistance or have any questions relating to custom modifications.
-
-:::
-
----
-
-## Electrical Integration {#warthog-electrical-integration}
-
-:::danger
-
-For continued protection against risk of fire, only replace fuses with those of the same type and rating.
-
-:::
-
-Except for bus-powered USB cameras, most payloads have separate leads for power and data.
-
-### Top Plate Power and Data Connections Connections
-
-| Description | Notes | Mating Connector (CPR Item) | Mating Connector (Manufacturer Item) |
-| :------------------------------------------------------ | :-------------------------------------- | :-------------------------- | :---------------------------------------------------------------------------------------- |
-| [USER POWER](/assets/pdf/clearpath_robotics_014673.pdf) | 12 V, 24 V, 48 VBAT; each fused to 10 A | 015016 | [RR-153274-23050](https://www.usbfirewire.com/parts/rr-153274-23050.html#RR-153274-23050) |
-| USB 3.0 | | | Male USB type-A |
-| ETHERNET RJ45 | | | Male RJ45 |
-| [SERIAL](/assets/pdf/clearpath_robotics_014672.pdf) | | 015015 | [RR-153274-23040](https://www.usbfirewire.com/parts/rr-153274-23040.html#RR-153274-23040) |
-
-
-
-
- Warthog user panel
-
-
-
-
-
-
- Warthog connector pinouts
-
-
-
-The user power receptacles located in the User Panel are capable of supplying 12 VDC, 24 VDC, and unregulated battery voltage (48 - 60 VDC) for powering Warthog's payloads.
-See the figures below for connector locations and pinouts.
-Ensure you select a contact that's appropriate for the gauge of wire used.
-
-:::note power
-
-The user power breakouts are intended for small sensors, like lidar and cameras.
-Warthog's 48 V battery pack is fused at 275 A (13200 W).
-We often add DC-DC and DC-AC supplies inside the Warthog to power large devices like manipulators, lights, and other custom integration attachments.
-
-Refer to the process described on our [Power Supplies](../../../accessories/add-ons/power_supplies.mdx#choosing_a_power_supply) page to help you choose a power supply or inverter.
-
-:::
-
-:::danger
-
-Always use adequately sized fuses for your selected wire thickness to prevent electrical fires.
-
-:::
-
-### System Electrical Diagram
-
-
-
-This is a 25 mm X 50 mm aluminum extrusion that mounts between the Warthog's [Extrusion Rails](extrusion_rails_warthog.mdx).
-The Cross-Bar is installed with T-slot nuts and 90° brackets.
-The Cross-Bar can be attached anywhere along the length of the Warthog's Extrusion Rails.
-
-## Sales Kits
-
-:::note
-
-This kit requires a Warthog with Extrusion Rails.
-Refer to the [Extrusion Rails](extrusion_rails_warthog.mdx) page for further details.
-
-:::
-
-| Description | Sales Kit |
-| :--------------------------------------------- | :-------: |
-| Installation—Extrusion Cross-Bar, 25 X 50, 652 | 028455 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :--------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1 | Beam, T-slot—25 X 50, 655, Aluminum, Black | [028465](/assets/pdf/clearpath_robotics_028465-TDS1.pdf) | 1 |
-| 2 | Bracket, T-Slot, 90°—5.8, 20, Aluminum, Black | [028464](/assets/pdf/clearpath_robotics_028464-TDS1.pdf) | 8 |
-| 3 | Nut, T-Slot—M5×0.8 X 5.8 X 10, Steel | [028463](/assets/pdf/clearpath_robotics_028463-TDS1.pdf) | 32 |
-| 4 | Screw, Cap, Socket Head—M5×0.8 X 10, Stainless Steel | 023150 | 32 |
-
-## Tools required
-
-- Hex Key, 4 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Attach 8 Brackets _(ID2)_ to the ends of the Beam _(ID1)_.
-Use 2 T-slot Nuts _(ID3)_ and 2 Screws _(ID4)_ per Bracket.
-
-:::note
-
-Torque these screws to 5 N·m if you are concerned about them loosening from high vibration applications.
-
-:::
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 2
-
-Add a T-slot Nut _(ID3)_ and Screw _(ID4)_ to each of the remaining holes of the Brackets _(ID2)_.
-Leave these Screws loose, in anticipation of the next step.
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
-
-### Step 3
-
-Slide the Cross-Bar assembly between the Warthog's Extrusion Rails.
-Make sure all 16 of the loose T-slot nuts are guided into the Extrusion Rails.
-
-### Step 4
-
-Slide the Cross-Bar assembly to your intended final position on the Warthog per your application.
-
-### Step 5
-
-Tighten all 16 Screws.
-
-:::note
-
-Torque these screws to 5 N·m if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
deleted file mode 100644
index e1ad6c6fd..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/integration_warthog/kits_warthog/top_plate_warthog.mdx
+++ /dev/null
@@ -1,82 +0,0 @@
----
-title: Top Plate
-sidebar_position: 3
----
-
-
-
-
-
-The top plates for the Warthog include M5×0.8 threaded holes that match the Clearpath PACS™ standard.
-
----
-
-## Sales Kits
-
-:::note
-
-This kit requires a Warthog with Extrusion Rails.
-Refer to the [Extrusion Rails](extrusion_rails_warthog.mdx) page for further details.
-
-:::
-
-:::tip
-
-This Top Plate can be stiffened by adding a Crossbar underneath it.
-Refer to the [Crossbar](extrusion_crossbar_warthog.mdx) page for further details.
-
-:::
-
-| Description | Sales Kit |
-| :---------------------------------------------- | :-------: |
-| Installation, Kit, Attachment Top Plate—Warthog | 028462 |
-
-## Parts List
-
-| ID | Description | CPR item | Quantity |
-| :-: | :--------------------------------------------------- | :------------------------------------------------------: | :------: |
-| 1 | Plate—110 X 704.5 | [028451](/assets/pdf/clearpath_robotics_028451.pdf) | 1 |
-| 2 | Nut, T-Slot—M5×0.8 X 5.8 X 10, Steel | [028463](/assets/pdf/clearpath_robotics_028463-TDS1.pdf) | 9 |
-| 3 | Screw, Flat Head—M5×0.8 X 12, Stainless Steel | 023471 | 3 |
-| 4 | Screw, Cap, Socket Head—M5×0.8 X 12, Stainless Steel | 023151 | 6 |
-
-## Tools required
-
-- Hex Key, 3 mm
-- Torque wrench _(optional, for safety applications)_
-- Loctite 243 _(optional, for high vibration applications)_
-
-## Installation
-
-### Step 1
-
-Insert T-slot nuts _(ID2)_ into the Warthog's [Extrusion Rail](extrusion_rails_warthog.mdx) and [Cross-Bar](extrusion_crossbar_warthog.mdx).
-
-:::note
-
-You may need to loosen the Cross-Bar's brackets to get access to the end for inserting the T-slot nuts.
-
-:::
-
-### Step 2
-
-Place the Plate _(ID1)_ ontop of the Extrusion Rails and Crossbar. The Plate's countersink features should be facing up.
-
-### Step 3
-
-Install Screws _(ID3)_ and _(ID4)_ into the Plate's holes; threading the Screws into the T-slot nuts from _Step 1_.
-
-:::note
-
-Torque these screws to 5 N·m if you are concerned about them loosening from high vibration applications.
-
-:::
-
-:::note
-
-You may add a small amount of thread locker to these screws if you are concerned about them loosening from high vibration applications.
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/maintenance_warthog.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/maintenance_warthog.mdx
deleted file mode 100644
index 52c9f5cfd..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/maintenance_warthog.mdx
+++ /dev/null
@@ -1,194 +0,0 @@
----
-title: Warthog Maintenance
-sidebar_label: Maintenance
-sidebar_position: 5
----
-import ClearpathFirmware from "../../../components/_clearpath_firmware.mdx";
-import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
-import GettingNewPackages from "/components/maintenance/getting_new_packages.mdx";
-import Support from "/components/support.mdx";
-
-
-
----
-
-## Battery and Charging
-
-### Overview
-
-Warthog contains a 48 V lead-acid battery pack, consisting of four 12 V lead-acid batteries, or a LiFEPO4 battery pack, consisting of four 118 Ah 12.8 V batteries
-connected in a 4S1P configuration with a single Battery Management System (BMS) control unit. Battery configuration may vary with each unit. In order to
-maximize performance, it's important to ensure that the battery level across each set of lead-acid or LiFEPO4 batteries is within 0.1-0.2 V.
-If the batteries exceed this tolerance, it's advised to charge them to within tolerance before wiring these packs in parallel. The overall battery life
-will vary depending upon the usage of the unit. The typical lifetime of a lead-acid battery pack is approximately 250-300 charge/discharge cycles,
-depending on the depth of discharge.
-
-### Battery Management System
-
-:::note
-
-If your Warthog is equipped with a lead-acid battery pack, you can ignore this section on the Battery Management System.
-
-:::
-
-:::note
-
-Your charger must be disconnected completely from the Warthog when not charging the unit. Leaving the cable plugged
-into the Warthog enables the BMS system to be powered on fully even when the robot is off, which will cause the
-batteries to be drained to an over-discharged state.
-
-:::
-
-If your Warthog is equipped with a LiFEPO4 battery pack, it is also equipped with a single Battery Management System (BMS) control unit.
-The main function of the BMS is to:
-
-- Protect the individual modules from being overcharged or excessively discharged.
-- Protect the modules from operating outside of their acceptable temperature range.
-- Provide status information to higher level systems via a CAN interface.
-- Provide independent system management without a higher level control system.
-- Provide status, warning and error messages from each of the modules connected to the battery power system.
-- Control the charging operation.
-- Perform module to module balancing of the system, the battery module will control cell balancing within itself.
-
-There is a main power contactor which is controlled by the BMS unit and is placed in such a way that it controls all power to the system.
-Upon turning on the main disconnect switch:
-
-The BMS powers up first and begins communicating with all of the battery modules in the system.
-
-1. If they are all present and have no errors the BMS will close the main contactor and allow the Warthog to power up as normal,
- this process can take a few seconds before the main contactor closes.
- - If all the modules are not present, the system State of Charge (SOC) is too low, or there are errors being reported by any of the
- modules in the system, the contactor will not close, and the system will not power up.
-2. Similarly, if a user is in discharge mode (the Warthog is in use) and any errors are detected, or if the SOC falls to a cut off point,
- the contactor will open and remove power from the system to protect the modules.
- - It is not good practice to run the state-of-charge (SOC) to 0%. This will decrease the life of the battery module. In general, keeping the SOC to a
- minimum of 30-50% can increase the lifetime of the batteries.
- - As a note, the system SOC is identical to the module with the lowest SOC in the system, so if three modules are at 45% SOC, and
- one module is at 25%, then the SOC of the system is 25%, and the BMS will act accordingly cutting off power to protect the module with
- the lowest SOC. Cell balancing and proper charging techniques are important to maintaining good battery health.
-3. The Warthog can be charged when the unit is powered and running, and can also be charged when the unit is not powered (main disconnect switch is open).
- - The charger has been configured and wired in a way that the BMS is actually controlling the charger and can turn it off, and on, depending
- on the status of the charging cycle.
- - Even though the unit can be charged while running, this process does not allow for proper cell balancing to occur. It will allow for bulk charge
- to occur to regain most of the charge in the system, however, repeatedly charging in this manner will allow each module to become out of balance with
- the other modules. If this process if followed long enough the SOC values for each module can vary by a substantial amount. The larger the variation,
- the longer it will take to fully balance the system. Therefore it is recommended (depending on use) that at least once every two to three weeks that
- **the system be completely charged while the main disconnect switch is in the off position.** Doing so will allow the BMS to go through an
- equalization phase where the charger is being turned on and off by the BMS to balance the voltages across each cell layer, in each module across the system.
- **This is a very important step in maintain battery health, and getting the maximum lifetime out of the battery system.**
- - Refer to [BMS ROS Topics](#bms-ros-topics) to view the necessary topics through the ROS API.
-4. To allow for this level of control there are three contactors in the system:
- - The main contactor for discharge of the system.
- - The charge contactor to connect to the output of the charger.
- - The charge control relay to turn the charger outputs on and off and control the cell balancing or equalization phase of the charge cycle.
-
-#### BMS ROS Topics {#bms-ros-topics}
-
-:::note
-
-If your Warthog is equipped with a lead-acid battery pack, you can ignore this section on the BMS ROS Topics.
-
-:::
-
-The table below shows topics that will be very useful in monitoring battery health, as outlined in the section above.
-
-| Topic | Purpose |
-| :------------------------- | :--------------------------------------------- |
-| `/bms/system_status` | Primarily to view `state_of_charge` (%) |
-| `/bms/system_measurements` | Primarily to view `battery_system_current` (A) |
-
-Note that the `battery_system_current` topic will be positive when the batteries are charging, indicating that
-current is flowing into the batteries. The lights on the charger unit itself will also indicate when the device is
-charging.
-
-#### To Connect the Charger
-
-1. Plug in the charger DC output cable (heavier gauge cable).
-2. Plug in the charger auxiliary control cable. (Note: Only relevant to Warthogs with LiFEPO4 batteries.)
-3. Plug the charger into AC power (directly to the wall outlet, no extension cords).
-4. This can be done with or without power on Warthog being on (however the note above applies: at least once every 2-3 weeks, the charge
- process needs to be allowed to fully balance the system).
-
-#### To Disconnect the Charger
-
-1. Unplug the charger from AC power.
-2. Unplug the charger auxiliary cable.
-3. Unplug the charger DC output cable (heavier gauge cable).
-
-#### Battery Pack Specifications
-
-Key battery system specifications are listed in the table below.
-
-| Specification | Measurement |
-| :-------------------------------- | :---------------------------------- |
-| System Voltage ( nominal ) | 51.2V ( up to 59 V while charging ) |
-| System Capcity | 118 Ah |
-| System Energy | 6.041 kWh |
-| Continuous Discharge Current | 150 A |
-| Peak Discharge Current ( 30 sec ) | 300 A |
-| Discharge Temperature Range | -10 °C to 50 °C |
-| Charge Temperature Range | 0 °C to 45 °C |
-
-### General Battery Safety and Maintenance
-
-Always exercise caution and observe the following safety practices when connecting, disconnecting or handling batteries:
-
-- Batteries are high voltage, high current.
-- Batteries must be properly fastened down to ensure they do not move when the Warthog is in operation.
-- Ensure that the batteries are evenly distributed throughout the Warthog to maximize stability.
-- Battery levels on the unit should be checked on a regular basis.
- It's important to maintain the battery voltage at a suitable level for proper operation.
-
-### Long-term Storage
-
-When storing Warthog for long periods of time, it's important to properly maintain the batteries to fully maximize their life.
-Consider the following procedure when placing Warthog in long-term storage:
-
-- Fully charge Warthog, turn it off and put it into storage.
- Once a week, connect power to the charger and allow the charger to top up the battery for an hour or so.
- Disconnect all charger cables connected to the Warthog while the charger is not powered; not disconnecting all of the charger cables can keep the BMS active and deplete the batteries.
-
-Please contact Clearpath Robotics for additional information about Warthog's batteries.
-
----
-
-## Tracks Upgrade
-
-If your unit came equipped with the tracks upgrade, please keep the following considerations in mind:
-
-- The tracks drive units pull considerably more current to operate.
- It is advised to operate a Warthog with tracks at reduced speeds, either through ROS commands or by reducing the speed scale when operating with the Futaba controller.
-- Due to the increased drive current, expect lower battery life than a wheeled Warthog.
- It is recommend to drive at reduced speeds to increase battery life.
-- It is possible to trigger an over current error in the motor controller by increasing speed drastically shortly after resetting a stop condition.
- The system's body lights will seem as if the unit is ready to drive, however it will not respond to drive commands.
- To clear this state, simply cycle another stop condition, and ramp up speeds slower.
-
----
-
-## Software Maintenance {#software_maintenance}
-
-### Getting New Packages
-
-
-
-### MCU Firmware Update
-
-:::caution
-
-Accessing Warthog's MCU requires access to several hard-to-get-to parts of the robot. Unless absolutely
-necessary, we do not recommend re-flashing the robot's MCU firmware.
-
-:::
-
-You need to use an external computer to update Warthog's MCU firmware. You cannot use Warthog's Onboard Computer, as installing the
-firmware requires power-cycling the MCU. Warthog's MCU controls the power supply to the Onboard Computer. These instructions
-assume the external computer is running some flavour of Linux with access to Clearpath's ROS packages.
-
-
-
----
-
-## Support
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/tutorials_warthog.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/tutorials_warthog.mdx
deleted file mode 100644
index adf4e9410..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/tutorials_warthog.mdx
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Warthog Tutorials
-sidebar_label: Tutorials
-sidebar_position: 4
----
-
-import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
-import ComponentTutorialLinks from "../../../components/_tutorials_link.mdx";
-import Support from "/components/support.mdx";
-
-
-
-## Warthog Overview
-
-### Introduction
-
-Clearpath Robotics Warthog is a rugged, all-terrain unmanned ground vehicle.
-
-For more information or to receive a quote, please [visit us online](http://clearpathrobotics.com/warthog).
-
-
-
----
-
-## Support {#support}
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/user_manual_warthog.mdx b/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/user_manual_warthog.mdx
deleted file mode 100644
index 69583aada..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/outdoor_robots/warthog/user_manual_warthog.mdx
+++ /dev/null
@@ -1,473 +0,0 @@
----
-title: Warthog User Manual
-sidebar_label: User Manual
-sidebar_position: 1
-toc_min_heading_level: 2
-toc_max_heading_level: 4
----
-
-import ComponentIntroductionWarthog from "/components/introduction_warthog.mdx";
-import ComponentUsingRos from "/components/using_ros.mdx";
-import Support from "/components/support.mdx";
-import ComponentCommonSafeWorkProcedures from "/components/common_safe_work_procedures.mdx";
-
-
-
-## Introduction
-
-Clearpath Robotics Warthog is a rugged, all-terrain unmanned ground vehicle capable of brief periods of locomotion
-in water. Warthog fully supports the Robot Operating System (ROS) and can be equipped with a variety of payloads,
-including sensors and manipulators, to accommodate a wide range of robotics applications in mining, agriculture
-and environmental monitoring.
-
-### Shipment Contents
-
-Your Warthog shipment contains the following:
-
-- Warthog UGV
- - Onboard computer
- - User Breakout Panel with power, Ethernet, Serial (RS232) and USB connectivity
- - 48 V Lead-Acid Battery Pack or 48 V LiFEPO4 Battery Pack
-- One battery charger
-- One Futaba remote control
-- One Warthog quick start guide
-- One Wireless Stop remote
-
-If you purchased standard payload modules or custom integration services with Warthog, then additional equipment
-will be included per your specific configuration, plus further documentation as required.
-
-### Hardware Overview
-
-#### System Architecture
-
-Warthog is built around an onboard computer running Ubuntu (Intel-based computer or Jetson developer kit), paired with a
-32-bit microcontroller MCU. The MCU handles IO, system and battery monitoring, and provides an interface to the CAN-controlled
-motor drivers. The communication channel between the MCU and computer is an Ethernet connection.
-
-
-
-
- System Architecture
-
-
-
-#### System Features
-
-The Warthog is shown below and includes:
-
-- Battery charger access
-- Bilge pumps
-- User breakouts
-- Payload integration area
-- Four Stop buttons (one on each corner)
-- Four body lights (one on each corner)
-
-
-
-
-
-
- Warthog hardware overview
-
-
-
-#### Battery Charger Access
-
-Please review [this PDF](/assets/pdf/clearpath_robotics_016519-TDS1.pdf) for information about the provided charger.
-
-#### Bilge Pumps
-
-The Warthog has two bilge pumps, with one situated in each of the drive units underneath the motor.
-The bilge pumps are used to remove water from the main chassis and drive units during operation in water.
-At initial startup, an audible sound can be heard from the bilge pumps being initiated.
-These pumps are an automatic pumping system that check for water levels inside the drive units.
-The pumps automatically come on every two minutes and check for water levels.
-If the water level inside the drive unit exceeds a predetermined level, the pumps will remain on, otherwise they will shut off.
-During prolonged use in water, some water may appear in the drive unit.
-This is normal and acceptable.
-This outlet leads from the pump to the exterior of the Warthog.
-It is used to remove excess water from the chassis and drive units.
-No obstructions should be placed in front of or around this area.
-Obstruction of water flow may result in damage to the internal electrical components and loss of function in the Warthog.
-
-#### User Breakouts
-
-The User Breakout Panel provides access to the user power panel, as well as USB, serial, and ethernet ports.
-The power panel can be used to power your payloads.
-The USB 3.0 and Ethernet ports are connected directly to the onboard computer.
-To connect a device to the onboard network, it's suggested to give it a static IP in the _192.168.131.xxx_ subnet, avoiding IPs in use by the following pre-existing devices:
-
-| IP address | Description |
-| :-----------: | :-------------------------------------------------- |
-| 192.168.131.1 | Onboard Computer (all ports, br0 network interface) |
-| 192.168.131.2 | Ethernet-connected MCU |
-
-Typically addresses numbered 192.168.131.100 and above will not collide with any of Warthog's payloads.
-Please see [Electrical Integration](integration_warthog/integration_warthog.mdx#warthog-electrical-integration) for more information.
-
-#### Payload Integration Area
-
-All payloads should be mounted to the central chassis when traversing through water to prevent rolling.
-The primary payload of the unit should be placed on the central chassis.
-If necessary loading can be placed on the drive units however payloads should not exceed 23 kg (50 lbs) on each drive unit.
-
-For more information and guidance on mounting payload structures on top of Warthog, please refer to subsection
-[Mechanical Mounting](integration_warthog/integration_warthog.mdx#warthog-mechanical-mounting).
-
-#### Body Lights
-
-Warthog includes four RGB body lights, one on each corner of the chassis. These lights
-express system status according to the table below, but in the absence of one of the low-level conditions, they can
-be commanded from ROS to display indications from autonomy or other higher-level software.
-See http://wiki.ros.org/warthog_base for information on commanding the body lights.
-
-| Front Lights | Rear Lights | System State |
-| :-------------- | :-------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Solid red | Solid red | The MCU is not in contact with the computer. That is, the `rosserial` connection is not active. This condition will be seen briefly on startup while Warthog's computer is booting up. If it persists, or is seen after initialization, either the base node on the computer has crashed, the network switch has failed, or a serious MCU error has occurred. If you suspect one of these conditions, please contact support. |
-| Flashing red | Flashing red | Stop mode is engaged. To disengage, twist the mushroom buttons on the Warthog and on the Wireless Stop remote to ensure that they are unlatched. See also [Using the Wireless Stop Remote](#using-the-wireless-stop-remote). |
-| Flashing orange | Flashing orange | Motor drivers not yet ready to drive. The motors have a brief initialization sequence which must complete after a stop condition clears before they are ready to drive. If this condition persists, please contact our support team. |
-| Pulsing orange | Pulsing orange | Battery is low. Connect Warthog to the charger. |
-| Solid white | Solid red | Normal operation; Warthog is ready to drive. This status may be overridden by publishing your own light patterns to the `/cmd_lights` ROS topic. |
-
-#### Orientation References
-
-The reference frame used by all Clearpath Robotics ground robots is based on ISO 8855. When commanded with a positive translational
-velocity (forward), wheels travel in the positive X-direction. The direction of the axes differs from those used for roll, pitch,
-and yaw in aircraft, and care should be taken to ensure that data is interpreted correctly.
-
-### System Specifications
-
-| Specification | Value |
-| :------------------------------ | :----------------------------------------------------------------------------------------- |
-| External Dimensions (L x W x H) | 1.52 X 1.38 X 0.83 metres (4.9' X 4.5' X 2.72') |
-| Base Weight | 280 kg (551 lbs) |
-| Ground Clearance | 254 mm (10 in) |
-| Max Payload | 272 kg (600 lbs) |
-| Max Incline | 35 - 45° |
-| Max Speed | 18 km/h (11 mph) |
-| Suspension | Geometric Passive Articulation |
-| Drive Configuration | 4 X 4 Skid Steer |
-| Operating Environment | Outdoor |
-| Traction | Ø610 mm (24") Argo Turf tire (default) or 300 mm (12") wide Quad Track System (optional) |
-| Battery Chemistry | AGM sealed lead-acid (LiFEPO4 optional) |
-| Capacity | 105 Ah at 48 V, expandable to 118 Ah at 51.2V with LiFEPO4 option |
-| Nominal Run Time | Lead-acid: 2.5 hrs, LiFEPO4: 6 hrs |
-| Charge Time | 4 Hours approx |
-| User Power | 12 V, 24 V and 48 V Fused at 10 A |
-| Control Modes | Remote control, computer controlled velocity commands, indoor/outdoor autonomy packages |
-| Feedback Battery | Voltage, motor currents, wheel odometry, control system status, temperature, safety status |
-| Communication | Ethernet, USB, Remote Control, Wi-Fi |
-| Drivers | Packaged with ROS Noetic (includes RViz, Gazebo support), Matlab API available |
-
-
-
-
- Warthog dimensions
-
-
-
----
-
-## Getting Started
-
-You are ready to go! This section details how to get Warthog into action.
-To begin, place Warthog "up on blocks", making sure that the wheels are clear of the ground.
-
-For most Warthog setups, there will be an Onboard Computer which is directly connected to the Warthog and an Offboard Computer which is used to control Husky and gather data.
-These two computers must be set up to communicate with each other.
-
-### Onboard Computer Setup
-
-Warthog ships with an Onboard Computer from Clearpath Robotics, which is already installed, connected, and powered.
-If you need to reinstall the software on it, refer to the [Warthog Tutorials](tutorials_warthog.mdx).
-
-### Powering Up
-
-To power on your Warthog, twist the red power button on the back of Warthog. Once the body lights are flashing red,
-twist (to reset) all four Stop buttons (if necessary), and press go on the Wireless Stop remote (next section).
-In a moment, Warthog should go to solid red lights in back, and solid white in front.
-This indicates that ROS is up on the computer and has established communications with the MCU.
-
-### Using the Wireless Stop Remote {#using-the-wireless-stop-remote}
-
-Included with the Warthog is a Wireless Stop remote. If for any reason the robot must be halted immediately, press the red STOP button.
-This will immediately cut power to the robot's motors.
-
-
-
-
- Warthog's Wireless Stop Remote
-
-
-
-It's capable of engaging a stop remotely.
-The system is designed to enter a stopped state when the remote is not communicating or loses communication with the base.
-The Wireless Stop remote operates as follows:
-
-1. Pull the red STOP button outwards to disengage it from a stop condition.
-2. Press and hold the green START button on the right side of the unit until the battery LED indicator above the buttons turns green.
- If the battery light is red, this means the STOP button is still engaged.
-3. Press the button labelled RELEASE within three seconds followed by the START button again.
-4. The battery LED should be blinking green quickly, this indicates the remote is paired with the receiver.
- To disengage the stop, press START once again.
-
-The battery LED should now be blinking slower, this indicates the remote stop has been disengaged.
-The corner body lights of the Warthog will change from blinking red to solid red at the rear and white at the front assuming
-all other safety stop sources have been disengaged.
-The Warthog is now ready to drive.
-
-:::note
-
-If you're not seeing any change in behaviour, please contact our support team.
-
-:::
-
-### Using the Stop buttons
-
-Warthog has four Stop buttons located on the four corners of the robot. Pressing any of
-these buttons will cut power to the motors, just like the STOP button on the Wireless Stop remote.
-To disengage the stop, simply twist the button in the direction indicated by the arrows.
-
-Whenever you need to perform maintenance on Warthog, we recommend engaging the stop if the
-robot cannot be fully powered down.
-
-### Drivetrain
-
-The Warthog has the ability to be put into neutral which is controlled be the four levers (two per side) in the
-rockers.
-
-
-
-
- Drivetrain lever
-
-
-
-Use the bolts to restrict the lever from moving as down when the drivetrain is in neutral.
-The groove for the neutral position is marked with white and the bolt is also marked.
-This is shown below.
-
-
-
-
- Drivetrain in neutral
-
-
-
-Pull the handle on the lever to move it into gear which can be seen below.
-Ensure the lever is in the green groove.
-If the lever is difficult to move, rock the Warthog back and forth.
-Do not try to force the lever to move.
-
-
-
-
- Drivetrain in gear
-
-
-
-### Using the Futaba Controller {#controller}
-
-The long range remote control (RC) Futaba radio transmitter can be used to teleoperate the Warthog.
-To begin, slide the power switch to the ON position which is labelled in the figure below.
-
-:::caution
-
-The speed adjustment knob should be turned initially all the way to the left while familiarizing yourself with the
-transmitter and slowly increasing it to get it moving.
-
-:::
-
-The position of the speed adjustment scale is shown in the figure as _CH4_.
-The transmitter needs to be enabled which is done using the _Enable Switch_.
-The _Enable Switch_ is a two position spring loaded switch.
-To enable the RC teleoperation, the switch needs to be held down.
-If released, the switch returns to the up position to disable the robot.
-The left joystick is used for the forward and reverse motion of the robot and the right joystick is used for turning.
-
-
-
-
- Futaba radio transmitter
-
-
-
-
-
-
- Futaba radio transmitter's screen
-
-
-
-:::note
-
-If the Clearpath Robotics Outdoor Navigation software is installed on the Warthog, the Futaba remote controller (RC) must be turned OFF for autonomous missions to be properly executed by the navigation software.
-The Futaba RC will always publish messages to the `/rc_teleop/cmd_vel` topic when it is ON, and since it has higher priority than the navigation's `/cmd_vel`, the Warthog will not move if autonomous missions are sent and the RC is still ON.
-
-:::
-
-### Network Configuration
-
-To get Warthog connected to your local Wi-Fi network, you must first access the Onboard Computer using a wired connection to the robot.
-Locate the User Breakout Panel on the rear of the chassis and connect to an Ethernet port with a standard
-Ethernet cable. See the [Warthog Tutorials](tutorials_warthog.mdx) for details
-on completing the Wi-Fi setup.
-
-### Using ROS
-
-
-
----
-
-## Safety Considerations {#safety}
-
-Clearpath Robotics is committed to high standards of safety.
-Warthog contains several features to protect the safety of users and the integrity of the robot.
-
-:::danger
-
-Warthog is a powerful, heavy, fast moving robotic platform.
-Please read the following safety information carefully.
-
-:::
-
-### General Warnings
-
-For the safety of yourself and others, always conduct initial experiments and software development with the motors not engaged.
-Whenever the robot is not being operated and the motors are engaged, keep it in a stop state.
-Do not ride on the vehicle, it can accelerate and brake quickly.
-
-When starting out, favour slower wheel speeds.
-Warthog's control loops can accurately maintain velocities as low as 0.1 m/s.
-Operating at such speeds will give you more time to react if things don't go quite as you expect.
-
-When enabling the system using the GO button on the wireless remote, be sure to stand well back from the Warthog.
-User code running on the Warthog may still be trying to command the motors, and this can result in sudden and unexpected movement of the vehicle.
-Be prepared to stop the system again using the wireless remote.
-
-### Maneuverability in Water
-
-Before entering the water it is important to ensure that:
-
-- Bilge pumps are functioning properly
-- The side panels and top cover are properly fastened down
-- All access panels are fastened down
-
-### Pinch Points {#warthog-pinch-points}
-
-When operating the Warthog it is important to maintain a safe distance away from the unit.
-The suspension has the ability to pivot.
-Do not place fingers anywhere along the suspension link as it can result in injury.
-
-
-
-
- Warthog pinch point
-
-
-
-### Stop buttons
-
-The Stop system on the Warthog has two major components: The hardwired Stop switches and the Wireless
-Stop remote.
-
-#### Hardwired Stop
-
-Pressing down one of the 4 red mushroom Stop buttons around the Warthog will disable power to the motor controller SEVCON devices (Key switch input on PIN 1).
-This disables the large contactors and also enables the brakes (passive, spring activated when not powered).
-The status indicator lights around the Warthog will flash red.
-To reset a Stop button, the top of the button should be twisted until the button pops out again.
-The GO button on Wireless remote must then pressed.
-The Warthog is fully enabled once a relay click is heard, and the front lights change to white.
-
-#### Wireless Stop Remote
-
-To operate the Warthog, the Wireless Stop remote also has to be powered on (by holding the Power button for at least 1 second).
-The remote STOP button toggles the stop status.
-It must be pressed once to enable stop, and pressed again to return to a stop reset ready state.
-The GO button on the remote will then reset the stop condition.
-Always ensure the STOP button is accessible at all times.
-Avoid mounting payloads that extend over the rear of Warthog and would occlude the Stop buttons.
-
-### Electrical System
-
-The largest electrical safety consideration with the Warthog system is the VBAT connection.
-As it is pulled straight from the batteries, it may have a voltage of 48 V (depleted) to 62 V (Charging) and can be used to power large external devices.
-This voltage can cause electrical shock if directly contacted, and is fused internally with an inline fuse at 10 A.
-In general, take care to connect or disconnect devices preferably only when the entire system is powered off via the external switch on the rear (main power switch).
-Take note that triggering a stop condition only disables voltage to the motor controller SEVCON drivers and motors, not the rest of the system which includes the connectors.
-The labelled status LEDs on the user panels indicate status of the system voltages.
-If a LED is not lit, then it's most likely that a system fuse has blown.
-Contacting Clearpath support is the best option.
-To ensure safety, please also observe the following precautions:
-
-- Do not tamper with the battery terminals or wiring.
-- Consult Clearpath Robotics support if you need to service the battery pack.
-- Do not lay tools or other objects on top of the battery.
-- Do not move the robot while charging the battery.
-- Charge the battery only with the charger provided by Clearpath Robotics.
-- Please dispose of the batteries properly, or return the batteries to Clearpath Robotics to do so.
-
-### Lifting and Transport
-
-For the safety of users and to maximize the lifetime of Warthog, please observe the following when manually transporting the robot:
-
-- Ensure that Warthog's stop mode is engaged when transporting short distances and powered off when transporting longer distances.
-- Do not push the robot at more than 0.5 m/s (1.6 ft/s) or damage to the motor controls may occur.
-
-### Performance Considerations
-
-Included in Warthog are native software checks and limits to protect the robot.
-However, it is recommended to monitor the system's status during usage with the `/status` and `/diagnostics` topics.
-These topics provide useful information regarding voltages, currents, temperatures and general health of the system.
-
-### Recommended Safe Work Procedures
-
-#### Common Safe Work Procedures
-
-
-
-#### Warthog-Specific Safe Work Procedures
-
-- Keep hands and fingers away from the suspension linkage components at the rear of the robot.
-- Never approach the robot while it is operating in water.
-- When working on or around the robot always disconnect the motors using the drivetrain levers as described in the user manual.
-- Never disconnect the robot motors using drivetrain levers when on a slope.
-- Do not attempt to move or operate the robot while charging the batteries.
-
----
-
-## Support
-
-
diff --git a/docs_versioned_docs/version-ros2humble/robots/robots.mdx b/docs_versioned_docs/version-ros2humble/robots/robots.mdx
deleted file mode 100644
index 8eec92162..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/robots.mdx
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Robots Overview
-sidebar_label: Robots Overview
-sidebar_position: 1
----
-
-
-
-
-
-We make base robot platforms, build custom integrations, and design bespoke robots to meet our customers' applications.
-
-We are committed to the [Robot Operating System (ROS)](https://ros.org/) and the community of researchers and users that support it.
-Each robot that Clearpath deploys is designed to be used with this open source platform.
-The extensibility of ROS has also allowed Clearpath to use it to develop the proprietary autonomy software for indoor and outdoor use.
-
-:::tip we suggest you:
-
-1. Review the documentation for our robot platforms, sensors, add-ons, and autonomy software.
-2. Try some of our tutorials. Some of these tutorials use a simulated robot, so you can try developing with ROS before purchasing hardware.
-3. Review some of our [GitHub](https://github.com/clearpathrobotics) repositories.
-4. Discuss your application with our Sales team at \, whether you already have a robot or not.
-
-:::
-
-:::info links to our robot pages
-
-- [Boxer](indoor_robots/boxer/user_manual_boxer.mdx)
-- [Dingo](indoor_robots/dingo/user_manual_dingo.mdx)
-- [Husky](outdoor_robots/husky/user_manual_husky.mdx)
-- [Husky Observer](solutions/husky_observer/husky_observer.mdx)
-- [Jackal](outdoor_robots/jackal/user_manual_jackal.mdx)
-- [Ridgeback](indoor_robots/ridgeback/user_manual_ridgeback.mdx)
-- [TurtleBot 4](learning_platforms/turtlebot4.mdx)
-- [Warthog](outdoor_robots/warthog/user_manual_warthog.mdx)
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/robots/solutions/_category_.json b/docs_versioned_docs/version-ros2humble/robots/solutions/_category_.json
deleted file mode 100644
index 73361e5e3..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/solutions/_category_.json
+++ /dev/null
@@ -1,4 +0,0 @@
-{
- "label": "Solutions",
- "position": 5
-}
diff --git a/docs_versioned_docs/version-ros2humble/robots/solutions/husky_observer/husky_observer.mdx b/docs_versioned_docs/version-ros2humble/robots/solutions/husky_observer/husky_observer.mdx
deleted file mode 100644
index a9f26f66e..000000000
--- a/docs_versioned_docs/version-ros2humble/robots/solutions/husky_observer/husky_observer.mdx
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: Husky Observer
-sidebar_label: Husky Observer
-sidebar_position: 1
----
-
-:::note
-
-Husky Observer is currently available in ROS 1 Noetic only. Use the link below
-to access the User Manual.
-
-[Link to Husky Observer User Manual](/docs_versioned_docs/version-ros1noetic/robots/solutions/husky_observer/user_manual_husky_observer.mdx)
-
-:::
diff --git a/docs_versioned_docs/version-ros2humble/ros/config/yaml/serial.mdx b/docs_versioned_docs/version-ros2humble/ros/config/yaml/serial.mdx
index c378dee62..7111c3b69 100644
--- a/docs_versioned_docs/version-ros2humble/ros/config/yaml/serial.mdx
+++ b/docs_versioned_docs/version-ros2humble/ros/config/yaml/serial.mdx
@@ -11,9 +11,9 @@ The Clearpath serial number is composed of two sections, separated by a hyphen,
At this moment, the supported robot platforms are:
-1. [Husky A200](../../../robots/outdoor_robots/husky/user_manual_husky): `a200-0000`
-3. [Jackal J100](../../../robots/outdoor_robots/jackal/user_manual_jackal.mdx): `j100-0000`
-4. [Warthog W200](../../../robots/outdoor_robots/warthog/user_manual_warthog.mdx): `w200-0000`
+1. [Husky A200](/docs_robots/outdoor_robots/husky/a200/user_manual_husky): `a200-0000`
+3. [Jackal J100](/docs_robots/outdoor_robots/jackal/user_manual_jackal): `j100-0000`
+4. [Warthog W200](/docs_robots/outdoor_robots/warthog/user_manual_warthog): `w200-0000`
Every robot platform has specific attachments that are selected based on the serial number passed. Therefore, it is **required** that a serial number is specified in the `robot.yaml`.
diff --git a/docs_versioned_docs/version-ros2humble/ros/installation/robot.mdx b/docs_versioned_docs/version-ros2humble/ros/installation/robot.mdx
index ab58a905e..678e5252c 100644
--- a/docs_versioned_docs/version-ros2humble/ros/installation/robot.mdx
+++ b/docs_versioned_docs/version-ros2humble/ros/installation/robot.mdx
@@ -311,8 +311,8 @@ sudo systemctl daemon-reload && sudo systemctl start clearpath-robot.service
#### Additional settings
- Certain sensors may require additional setup, please review the [Accessories](../../robots/accessories/accessories.mdx) pages
+ Certain sensors may require additional setup, please review the [Accessories](/docs_robots/accessories) pages
for any additional instructions for the sensors that you are using. For example, the Blackfly camera has additional instructions
- listed under [software bringup](../../robots/accessories/sensors/cameras/flir_blackfly_s#software-bringup).
+ listed under [software bringup](/docs_robots/accessories/sensors/cameras/flir_blackfly_s#software-bringup).
diff --git a/docs_versioned_docs/version-ros2jazzy/.keep b/docs_versioned_docs/version-ros2jazzy/.keep
new file mode 100644
index 000000000..e69de29bb
diff --git a/docs/components/_clearpath_firmware.mdx b/docs_versioned_docs/version-ros2jazzy/components/_clearpath_firmware.mdx
similarity index 100%
rename from docs/components/_clearpath_firmware.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/_clearpath_firmware.mdx
diff --git a/docs/components/_jackal_firmware.mdx b/docs_versioned_docs/version-ros2jazzy/components/_jackal_firmware.mdx
similarity index 100%
rename from docs/components/_jackal_firmware.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/_jackal_firmware.mdx
diff --git a/docs/components/networking/_computer_networking_setup_install.mdx b/docs_versioned_docs/version-ros2jazzy/components/networking/_computer_networking_setup_install.mdx
similarity index 100%
rename from docs/components/networking/_computer_networking_setup_install.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/networking/_computer_networking_setup_install.mdx
diff --git a/docs/components/networking/_ros2_networking_overview.mdx b/docs_versioned_docs/version-ros2jazzy/components/networking/_ros2_networking_overview.mdx
similarity index 100%
rename from docs/components/networking/_ros2_networking_overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/networking/_ros2_networking_overview.mdx
diff --git a/docs/components/networking/_standard_clearpath_bridge_setup.mdx b/docs_versioned_docs/version-ros2jazzy/components/networking/_standard_clearpath_bridge_setup.mdx
similarity index 100%
rename from docs/components/networking/_standard_clearpath_bridge_setup.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/networking/_standard_clearpath_bridge_setup.mdx
diff --git a/docs/components/yaml/attachments/a200/bumper.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/bumper.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/bumper.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/bumper.mdx
diff --git a/docs/components/yaml/attachments/a200/img/bumper.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/bumper.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/bumper.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/bumper.png
diff --git a/docs/components/yaml/attachments/a200/img/observer_backpack.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/observer_backpack.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/observer_backpack.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/observer_backpack.png
diff --git a/docs/components/yaml/attachments/a200/img/sensor_arch_300.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/sensor_arch_300.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/sensor_arch_300.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/sensor_arch_300.png
diff --git a/docs/components/yaml/attachments/a200/img/sensor_arch_510.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/sensor_arch_510.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/sensor_arch_510.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/sensor_arch_510.png
diff --git a/docs/components/yaml/attachments/a200/img/top_plate_default.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_default.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/top_plate_default.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_default.png
diff --git a/docs/components/yaml/attachments/a200/img/top_plate_large.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_large.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/top_plate_large.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_large.png
diff --git a/docs/components/yaml/attachments/a200/img/top_plate_pacs.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_pacs.png
similarity index 100%
rename from docs/components/yaml/attachments/a200/img/top_plate_pacs.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/img/top_plate_pacs.png
diff --git a/docs/components/yaml/attachments/a200/observer_backpack.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/observer_backpack.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/observer_backpack.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/observer_backpack.mdx
diff --git a/docs/components/yaml/attachments/a200/sensor_arch_300.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/sensor_arch_300.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/sensor_arch_300.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/sensor_arch_300.mdx
diff --git a/docs/components/yaml/attachments/a200/sensor_arch_510.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/sensor_arch_510.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/sensor_arch_510.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/sensor_arch_510.mdx
diff --git a/docs/components/yaml/attachments/a200/top_plate_default.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_default.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/top_plate_default.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_default.mdx
diff --git a/docs/components/yaml/attachments/a200/top_plate_large.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_large.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/top_plate_large.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_large.mdx
diff --git a/docs/components/yaml/attachments/a200/top_plate_pacs.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_pacs.mdx
similarity index 100%
rename from docs/components/yaml/attachments/a200/top_plate_pacs.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/top_plate_pacs.mdx
diff --git a/docs/components/yaml/attachments/dx1X0/img/top_plate_dd100.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_dd100.png
similarity index 100%
rename from docs/components/yaml/attachments/dx1X0/img/top_plate_dd100.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_dd100.png
diff --git a/docs/components/yaml/attachments/dx1X0/img/top_plate_dd150.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_dd150.png
similarity index 100%
rename from docs/components/yaml/attachments/dx1X0/img/top_plate_dd150.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_dd150.png
diff --git a/docs/components/yaml/attachments/dx1X0/img/top_plate_do1X0.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_do1X0.png
similarity index 100%
rename from docs/components/yaml/attachments/dx1X0/img/top_plate_do1X0.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/img/top_plate_do1X0.png
diff --git a/docs/components/yaml/attachments/dx1X0/top_plate.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/top_plate.mdx
similarity index 100%
rename from docs/components/yaml/attachments/dx1X0/top_plate.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/dx1X0/top_plate.mdx
diff --git a/docs/components/yaml/attachments/j100/fender_default.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/fender_default.mdx
similarity index 100%
rename from docs/components/yaml/attachments/j100/fender_default.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/fender_default.mdx
diff --git a/docs/components/yaml/attachments/j100/fender_sensor.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/fender_sensor.mdx
similarity index 100%
rename from docs/components/yaml/attachments/j100/fender_sensor.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/fender_sensor.mdx
diff --git a/docs/components/yaml/attachments/j100/img/fender_default.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/fender_default.png
similarity index 100%
rename from docs/components/yaml/attachments/j100/img/fender_default.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/fender_default.png
diff --git a/docs/components/yaml/attachments/j100/img/fender_sensor.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/fender_sensor.png
similarity index 100%
rename from docs/components/yaml/attachments/j100/img/fender_sensor.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/fender_sensor.png
diff --git a/docs/components/yaml/attachments/j100/img/top_plate_ark_enclosure.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/top_plate_ark_enclosure.png
similarity index 100%
rename from docs/components/yaml/attachments/j100/img/top_plate_ark_enclosure.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/img/top_plate_ark_enclosure.png
diff --git a/docs/components/yaml/attachments/j100/top_plate_ark_enclosure.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/top_plate_ark_enclosure.mdx
similarity index 100%
rename from docs/components/yaml/attachments/j100/top_plate_ark_enclosure.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/j100/top_plate_ark_enclosure.mdx
diff --git a/docs/components/yaml/attachments/r100/fams.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/fams.mdx
similarity index 100%
rename from docs/components/yaml/attachments/r100/fams.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/fams.mdx
diff --git a/docs/components/yaml/attachments/r100/hams.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/hams.mdx
similarity index 100%
rename from docs/components/yaml/attachments/r100/hams.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/hams.mdx
diff --git a/docs/components/yaml/attachments/r100/img/fams.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/fams.png
similarity index 100%
rename from docs/components/yaml/attachments/r100/img/fams.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/fams.png
diff --git a/docs/components/yaml/attachments/r100/img/hams.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/hams.png
similarity index 100%
rename from docs/components/yaml/attachments/r100/img/hams.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/hams.png
diff --git a/docs/components/yaml/attachments/r100/img/tower.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/tower.png
similarity index 100%
rename from docs/components/yaml/attachments/r100/img/tower.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/img/tower.png
diff --git a/docs/components/yaml/attachments/r100/tower.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/tower.mdx
similarity index 100%
rename from docs/components/yaml/attachments/r100/tower.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/r100/tower.mdx
diff --git a/docs/components/yaml/attachments/w200/arm_mount.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/arm_mount.mdx
similarity index 100%
rename from docs/components/yaml/attachments/w200/arm_mount.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/arm_mount.mdx
diff --git a/docs/components/yaml/attachments/w200/bulkhead_arm_mount.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/bulkhead_arm_mount.mdx
similarity index 100%
rename from docs/components/yaml/attachments/w200/bulkhead_arm_mount.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/bulkhead_arm_mount.mdx
diff --git a/docs/components/yaml/attachments/w200/bulkhead_default.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/bulkhead_default.mdx
similarity index 100%
rename from docs/components/yaml/attachments/w200/bulkhead_default.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/bulkhead_default.mdx
diff --git a/docs/components/yaml/attachments/w200/generator.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/generator.mdx
similarity index 100%
rename from docs/components/yaml/attachments/w200/generator.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/generator.mdx
diff --git a/docs/components/yaml/attachments/w200/img/arm_mount.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/arm_mount.png
similarity index 100%
rename from docs/components/yaml/attachments/w200/img/arm_mount.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/arm_mount.png
diff --git a/docs/components/yaml/attachments/w200/img/bulkhead_arm_mount.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/bulkhead_arm_mount.png
similarity index 100%
rename from docs/components/yaml/attachments/w200/img/bulkhead_arm_mount.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/bulkhead_arm_mount.png
diff --git a/docs/components/yaml/attachments/w200/img/bulkhead_default.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/bulkhead_default.png
similarity index 100%
rename from docs/components/yaml/attachments/w200/img/bulkhead_default.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/bulkhead_default.png
diff --git a/docs/components/yaml/attachments/w200/img/generator.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/generator.png
similarity index 100%
rename from docs/components/yaml/attachments/w200/img/generator.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/w200/img/generator.png
diff --git a/docs/components/yaml/links/box.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/box.mdx
similarity index 100%
rename from docs/components/yaml/links/box.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/box.mdx
diff --git a/docs/components/yaml/links/cylinder.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/cylinder.mdx
similarity index 100%
rename from docs/components/yaml/links/cylinder.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/cylinder.mdx
diff --git a/docs/components/yaml/links/frame.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/frame.mdx
similarity index 100%
rename from docs/components/yaml/links/frame.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/frame.mdx
diff --git a/docs/components/yaml/links/img/box.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/box.png
similarity index 100%
rename from docs/components/yaml/links/img/box.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/box.png
diff --git a/docs/components/yaml/links/img/cylinder.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/cylinder.png
similarity index 100%
rename from docs/components/yaml/links/img/cylinder.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/cylinder.png
diff --git a/docs/components/yaml/links/img/frame.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/frame.png
similarity index 100%
rename from docs/components/yaml/links/img/frame.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/frame.png
diff --git a/docs/components/yaml/links/img/mesh.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/mesh.png
similarity index 100%
rename from docs/components/yaml/links/img/mesh.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/mesh.png
diff --git a/docs/components/yaml/links/img/sphere.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/sphere.png
similarity index 100%
rename from docs/components/yaml/links/img/sphere.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/img/sphere.png
diff --git a/docs/components/yaml/links/mesh.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/mesh.mdx
similarity index 100%
rename from docs/components/yaml/links/mesh.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/mesh.mdx
diff --git a/docs/components/yaml/links/sphere.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/links/sphere.mdx
similarity index 100%
rename from docs/components/yaml/links/sphere.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/links/sphere.mdx
diff --git a/docs/components/yaml/manipulators/img/kinova_2f_lite.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_2f_lite.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/kinova_2f_lite.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_2f_lite.png
diff --git a/docs/components/yaml/manipulators/img/kinova_gen3_6dof.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_6dof.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/kinova_gen3_6dof.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_6dof.png
diff --git a/docs/components/yaml/manipulators/img/kinova_gen3_7dof.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_7dof.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/kinova_gen3_7dof.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_7dof.png
diff --git a/docs/components/yaml/manipulators/img/kinova_gen3_lite.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_lite.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/kinova_gen3_lite.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/kinova_gen3_lite.png
diff --git a/docs/components/yaml/manipulators/img/robotiq_2f_140.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/robotiq_2f_140.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/robotiq_2f_140.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/robotiq_2f_140.png
diff --git a/docs/components/yaml/manipulators/img/robotiq_2f_85.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/robotiq_2f_85.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/robotiq_2f_85.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/robotiq_2f_85.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/failed.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/failed.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/failed.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/failed.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/headless_0.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_0.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/headless_0.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_0.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/headless_1.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_1.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/headless_1.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_1.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/headless_2.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_2.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/headless_2.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/headless_2.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/initialize_0.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_0.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/initialize_0.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_0.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/initialize_1.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_1.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/initialize_1.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_1.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/initialize_2.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_2.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/initialize_2.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_2.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/initialize_3.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_3.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/initialize_3.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_3.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/initialize_4.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_4.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/initialize_4.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/initialize_4.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/installation_default_program.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/installation_default_program.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/installation_default_program.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/installation_default_program.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/installation_urcaps.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/installation_urcaps.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/installation_urcaps.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/installation_urcaps.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/program_urcaps.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/program_urcaps.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/program_urcaps.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/program_urcaps.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/settings_network.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_network.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/settings_network.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_network.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/settings_remote_control.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_remote_control.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/settings_remote_control.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_remote_control.png
diff --git a/docs/components/yaml/manipulators/img/universal_robots/settings_urcaps.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_urcaps.png
similarity index 100%
rename from docs/components/yaml/manipulators/img/universal_robots/settings_urcaps.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/img/universal_robots/settings_urcaps.png
diff --git a/docs/components/yaml/manipulators/kinova_2f_lite.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_2f_lite.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/kinova_2f_lite.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_2f_lite.mdx
diff --git a/docs/components/yaml/manipulators/kinova_gen3_6dof.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_6dof.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/kinova_gen3_6dof.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_6dof.mdx
diff --git a/docs/components/yaml/manipulators/kinova_gen3_7dof.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_7dof.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/kinova_gen3_7dof.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_7dof.mdx
diff --git a/docs/components/yaml/manipulators/kinova_gen3_lite.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_lite.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/kinova_gen3_lite.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/kinova_gen3_lite.mdx
diff --git a/docs/components/yaml/manipulators/robotiq_2f_140.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/robotiq_2f_140.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/robotiq_2f_140.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/robotiq_2f_140.mdx
diff --git a/docs/components/yaml/manipulators/robotiq_2f_85.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/robotiq_2f_85.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/robotiq_2f_85.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/robotiq_2f_85.mdx
diff --git a/docs/components/yaml/manipulators/universal_robots.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/universal_robots.mdx
similarity index 100%
rename from docs/components/yaml/manipulators/universal_robots.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/manipulators/universal_robots.mdx
diff --git a/docs/components/yaml/mounts/bracket_horizontal.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_horizontal.mdx
similarity index 100%
rename from docs/components/yaml/mounts/bracket_horizontal.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_horizontal.mdx
diff --git a/docs/components/yaml/mounts/bracket_large.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_large.mdx
similarity index 100%
rename from docs/components/yaml/mounts/bracket_large.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_large.mdx
diff --git a/docs/components/yaml/mounts/bracket_vertical.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_vertical.mdx
similarity index 100%
rename from docs/components/yaml/mounts/bracket_vertical.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/bracket_vertical.mdx
diff --git a/docs/components/yaml/mounts/disk.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/disk.mdx
similarity index 100%
rename from docs/components/yaml/mounts/disk.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/disk.mdx
diff --git a/docs/components/yaml/mounts/disk_post.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/disk_post.mdx
similarity index 100%
rename from docs/components/yaml/mounts/disk_post.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/disk_post.mdx
diff --git a/docs/components/yaml/mounts/fath_pivot.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/fath_pivot.mdx
similarity index 100%
rename from docs/components/yaml/mounts/fath_pivot.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/fath_pivot.mdx
diff --git a/docs/components/yaml/mounts/img/bracket_horizontal.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_horizontal.png
similarity index 100%
rename from docs/components/yaml/mounts/img/bracket_horizontal.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_horizontal.png
diff --git a/docs/components/yaml/mounts/img/bracket_large.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_large.png
similarity index 100%
rename from docs/components/yaml/mounts/img/bracket_large.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_large.png
diff --git a/docs/components/yaml/mounts/img/bracket_vertical.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_vertical.png
similarity index 100%
rename from docs/components/yaml/mounts/img/bracket_vertical.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/bracket_vertical.png
diff --git a/docs/components/yaml/mounts/img/disk.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/disk.png
similarity index 100%
rename from docs/components/yaml/mounts/img/disk.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/disk.png
diff --git a/docs/components/yaml/mounts/img/disk_post.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/disk_post.png
similarity index 100%
rename from docs/components/yaml/mounts/img/disk_post.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/disk_post.png
diff --git a/docs/components/yaml/mounts/img/fath_pivot.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/fath_pivot.png
similarity index 100%
rename from docs/components/yaml/mounts/img/fath_pivot.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/fath_pivot.png
diff --git a/docs/components/yaml/mounts/img/post_dual.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_dual.png
similarity index 100%
rename from docs/components/yaml/mounts/img/post_dual.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_dual.png
diff --git a/docs/components/yaml/mounts/img/post_quad.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_quad.png
similarity index 100%
rename from docs/components/yaml/mounts/img/post_quad.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_quad.png
diff --git a/docs/components/yaml/mounts/img/post_single.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_single.png
similarity index 100%
rename from docs/components/yaml/mounts/img/post_single.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/post_single.png
diff --git a/docs/components/yaml/mounts/img/riser_1x7.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_1x7.png
similarity index 100%
rename from docs/components/yaml/mounts/img/riser_1x7.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_1x7.png
diff --git a/docs/components/yaml/mounts/img/riser_4x4.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_4x4.png
similarity index 100%
rename from docs/components/yaml/mounts/img/riser_4x4.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_4x4.png
diff --git a/docs/components/yaml/mounts/img/riser_8x7.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_8x7.png
similarity index 100%
rename from docs/components/yaml/mounts/img/riser_8x7.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/riser_8x7.png
diff --git a/docs/components/yaml/mounts/img/sick_inverted.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/sick_inverted.png
similarity index 100%
rename from docs/components/yaml/mounts/img/sick_inverted.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/sick_inverted.png
diff --git a/docs/components/yaml/mounts/img/sick_upright.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/sick_upright.png
similarity index 100%
rename from docs/components/yaml/mounts/img/sick_upright.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/img/sick_upright.png
diff --git a/docs/components/yaml/mounts/post_dual.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_dual.mdx
similarity index 100%
rename from docs/components/yaml/mounts/post_dual.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_dual.mdx
diff --git a/docs/components/yaml/mounts/post_quad.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_quad.mdx
similarity index 100%
rename from docs/components/yaml/mounts/post_quad.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_quad.mdx
diff --git a/docs/components/yaml/mounts/post_single.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_single.mdx
similarity index 100%
rename from docs/components/yaml/mounts/post_single.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/post_single.mdx
diff --git a/docs/components/yaml/mounts/riser_1x7.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_1x7.mdx
similarity index 100%
rename from docs/components/yaml/mounts/riser_1x7.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_1x7.mdx
diff --git a/docs/components/yaml/mounts/riser_4x4.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_4x4.mdx
similarity index 100%
rename from docs/components/yaml/mounts/riser_4x4.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_4x4.mdx
diff --git a/docs/components/yaml/mounts/riser_8x7.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_8x7.mdx
similarity index 100%
rename from docs/components/yaml/mounts/riser_8x7.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/riser_8x7.mdx
diff --git a/docs/components/yaml/mounts/sick_inverted.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/sick_inverted.mdx
similarity index 100%
rename from docs/components/yaml/mounts/sick_inverted.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/sick_inverted.mdx
diff --git a/docs/components/yaml/mounts/sick_upright.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/sick_upright.mdx
similarity index 100%
rename from docs/components/yaml/mounts/sick_upright.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/mounts/sick_upright.mdx
diff --git a/docs/components/yaml/sensors/axis_camera.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/axis_camera.mdx
similarity index 100%
rename from docs/components/yaml/sensors/axis_camera.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/axis_camera.mdx
diff --git a/docs/components/yaml/sensors/chrobotics_um6.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/chrobotics_um6.mdx
similarity index 100%
rename from docs/components/yaml/sensors/chrobotics_um6.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/chrobotics_um6.mdx
diff --git a/docs/components/yaml/sensors/flir_blackfly.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/flir_blackfly.mdx
similarity index 100%
rename from docs/components/yaml/sensors/flir_blackfly.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/flir_blackfly.mdx
diff --git a/docs/components/yaml/sensors/garmin_18x.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/garmin_18x.mdx
similarity index 100%
rename from docs/components/yaml/sensors/garmin_18x.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/garmin_18x.mdx
diff --git a/docs/components/yaml/sensors/hokuyo_ust.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/hokuyo_ust.mdx
similarity index 100%
rename from docs/components/yaml/sensors/hokuyo_ust.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/hokuyo_ust.mdx
diff --git a/docs/components/yaml/sensors/img/axis_camera.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/axis_camera.png
similarity index 100%
rename from docs/components/yaml/sensors/img/axis_camera.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/axis_camera.png
diff --git a/docs/components/yaml/sensors/img/chrobotics_um6.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/chrobotics_um6.png
similarity index 100%
rename from docs/components/yaml/sensors/img/chrobotics_um6.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/chrobotics_um6.png
diff --git a/docs/components/yaml/sensors/img/flir_blackfly.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/flir_blackfly.png
similarity index 100%
rename from docs/components/yaml/sensors/img/flir_blackfly.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/flir_blackfly.png
diff --git a/docs/components/yaml/sensors/img/garmin_18x.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/garmin_18x.png
similarity index 100%
rename from docs/components/yaml/sensors/img/garmin_18x.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/garmin_18x.png
diff --git a/docs/components/yaml/sensors/img/hokuyo_ust.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/hokuyo_ust.png
similarity index 100%
rename from docs/components/yaml/sensors/img/hokuyo_ust.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/hokuyo_ust.png
diff --git a/docs/components/yaml/sensors/img/intel_realsense.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/intel_realsense.png
similarity index 100%
rename from docs/components/yaml/sensors/img/intel_realsense.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/intel_realsense.png
diff --git a/docs/components/yaml/sensors/img/luxonis_oakd.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/luxonis_oakd.png
similarity index 100%
rename from docs/components/yaml/sensors/img/luxonis_oakd.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/luxonis_oakd.png
diff --git a/docs/components/yaml/sensors/img/microstrain_gq7.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/microstrain_gq7.png
similarity index 100%
rename from docs/components/yaml/sensors/img/microstrain_gq7.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/microstrain_gq7.png
diff --git a/docs/components/yaml/sensors/img/microstrain_imu.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/microstrain_imu.png
similarity index 100%
rename from docs/components/yaml/sensors/img/microstrain_imu.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/microstrain_imu.png
diff --git a/docs/components/yaml/sensors/img/novatel_smart6.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/novatel_smart6.png
similarity index 100%
rename from docs/components/yaml/sensors/img/novatel_smart6.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/novatel_smart6.png
diff --git a/docs/components/yaml/sensors/img/novatel_smart7.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/novatel_smart7.png
similarity index 100%
rename from docs/components/yaml/sensors/img/novatel_smart7.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/novatel_smart7.png
diff --git a/docs/components/yaml/sensors/img/redshift_um7.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/redshift_um7.png
similarity index 100%
rename from docs/components/yaml/sensors/img/redshift_um7.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/redshift_um7.png
diff --git a/docs/components/yaml/sensors/img/sick_lms1xx.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/sick_lms1xx.png
similarity index 100%
rename from docs/components/yaml/sensors/img/sick_lms1xx.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/sick_lms1xx.png
diff --git a/docs/components/yaml/sensors/img/stereolabs_zed.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/stereolabs_zed.png
similarity index 100%
rename from docs/components/yaml/sensors/img/stereolabs_zed.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/stereolabs_zed.png
diff --git a/docs/components/yaml/sensors/img/swiftnav_duro.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/swiftnav_duro.png
similarity index 100%
rename from docs/components/yaml/sensors/img/swiftnav_duro.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/swiftnav_duro.png
diff --git a/docs/components/yaml/sensors/img/velodyne_lidar.png b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/velodyne_lidar.png
similarity index 100%
rename from docs/components/yaml/sensors/img/velodyne_lidar.png
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/img/velodyne_lidar.png
diff --git a/docs/components/yaml/sensors/intel_realsense.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/intel_realsense.mdx
similarity index 100%
rename from docs/components/yaml/sensors/intel_realsense.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/intel_realsense.mdx
diff --git a/docs/components/yaml/sensors/luxonis_oakd.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/luxonis_oakd.mdx
similarity index 100%
rename from docs/components/yaml/sensors/luxonis_oakd.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/luxonis_oakd.mdx
diff --git a/docs/components/yaml/sensors/microstrain_gq7.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/microstrain_gq7.mdx
similarity index 100%
rename from docs/components/yaml/sensors/microstrain_gq7.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/microstrain_gq7.mdx
diff --git a/docs/components/yaml/sensors/microstrain_imu.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/microstrain_imu.mdx
similarity index 100%
rename from docs/components/yaml/sensors/microstrain_imu.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/microstrain_imu.mdx
diff --git a/docs/components/yaml/sensors/novatel_smart6.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/novatel_smart6.mdx
similarity index 100%
rename from docs/components/yaml/sensors/novatel_smart6.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/novatel_smart6.mdx
diff --git a/docs/components/yaml/sensors/novatel_smart7.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/novatel_smart7.mdx
similarity index 100%
rename from docs/components/yaml/sensors/novatel_smart7.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/novatel_smart7.mdx
diff --git a/docs/components/yaml/sensors/redshift_um7.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/redshift_um7.mdx
similarity index 100%
rename from docs/components/yaml/sensors/redshift_um7.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/redshift_um7.mdx
diff --git a/docs/components/yaml/sensors/sick_lms1xx.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/sick_lms1xx.mdx
similarity index 100%
rename from docs/components/yaml/sensors/sick_lms1xx.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/sick_lms1xx.mdx
diff --git a/docs/components/yaml/sensors/stereolabs_zed.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/stereolabs_zed.mdx
similarity index 100%
rename from docs/components/yaml/sensors/stereolabs_zed.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/stereolabs_zed.mdx
diff --git a/docs/components/yaml/sensors/swiftnav_duro.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/swiftnav_duro.mdx
similarity index 100%
rename from docs/components/yaml/sensors/swiftnav_duro.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/swiftnav_duro.mdx
diff --git a/docs/components/yaml/sensors/velodyne_lidar.mdx b/docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/velodyne_lidar.mdx
similarity index 100%
rename from docs/components/yaml/sensors/velodyne_lidar.mdx
rename to docs_versioned_docs/version-ros2jazzy/components/yaml/sensors/velodyne_lidar.mdx
diff --git a/docs/ros/api/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/api/_category_.json
similarity index 100%
rename from docs/ros/api/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/api/_category_.json
diff --git a/docs/ros/api/lighting.mdx b/docs_versioned_docs/version-ros2jazzy/ros/api/lighting.mdx
similarity index 100%
rename from docs/ros/api/lighting.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/api/lighting.mdx
diff --git a/docs/ros/api/mcu_api.mdx b/docs_versioned_docs/version-ros2jazzy/ros/api/mcu_api.mdx
similarity index 100%
rename from docs/ros/api/mcu_api.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/api/mcu_api.mdx
diff --git a/docs/ros/api/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/api/overview.mdx
similarity index 100%
rename from docs/ros/api/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/api/overview.mdx
diff --git a/docs/ros/api/platform_api.mdx b/docs_versioned_docs/version-ros2jazzy/ros/api/platform_api.mdx
similarity index 100%
rename from docs/ros/api/platform_api.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/api/platform_api.mdx
diff --git a/docs/ros/api/sensors_api.mdx b/docs_versioned_docs/version-ros2jazzy/ros/api/sensors_api.mdx
similarity index 100%
rename from docs/ros/api/sensors_api.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/api/sensors_api.mdx
diff --git a/docs/ros/config/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/config/_category_.json
similarity index 100%
rename from docs/ros/config/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/config/_category_.json
diff --git a/docs/ros/config/camera_compression.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/camera_compression.mdx
similarity index 100%
rename from docs/ros/config/camera_compression.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/camera_compression.mdx
diff --git a/docs/ros/config/customization.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/customization.mdx
similarity index 100%
rename from docs/ros/config/customization.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/customization.mdx
diff --git a/docs/ros/config/generators.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/generators.mdx
similarity index 100%
rename from docs/ros/config/generators.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/generators.mdx
diff --git a/docs/ros/config/img/husky_accessories_0.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_accessories_0.png
similarity index 100%
rename from docs/ros/config/img/husky_accessories_0.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_accessories_0.png
diff --git a/docs/ros/config/img/husky_mounts_0.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_mounts_0.png
similarity index 100%
rename from docs/ros/config/img/husky_mounts_0.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_mounts_0.png
diff --git a/docs/ros/config/img/husky_mounts_1.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_mounts_1.png
similarity index 100%
rename from docs/ros/config/img/husky_mounts_1.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_mounts_1.png
diff --git a/docs/ros/config/img/husky_platform_0.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_0.png
similarity index 100%
rename from docs/ros/config/img/husky_platform_0.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_0.png
diff --git a/docs/ros/config/img/husky_platform_1.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_1.png
similarity index 100%
rename from docs/ros/config/img/husky_platform_1.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_1.png
diff --git a/docs/ros/config/img/husky_platform_2.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_2.png
similarity index 100%
rename from docs/ros/config/img/husky_platform_2.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_platform_2.png
diff --git a/docs/ros/config/img/husky_sample.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sample.png
similarity index 100%
rename from docs/ros/config/img/husky_sample.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sample.png
diff --git a/docs/ros/config/img/husky_sensors_0.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_0.png
similarity index 100%
rename from docs/ros/config/img/husky_sensors_0.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_0.png
diff --git a/docs/ros/config/img/husky_sensors_1.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_1.png
similarity index 100%
rename from docs/ros/config/img/husky_sensors_1.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_1.png
diff --git a/docs/ros/config/img/husky_sensors_2.png b/docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_2.png
similarity index 100%
rename from docs/ros/config/img/husky_sensors_2.png
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/husky_sensors_2.png
diff --git a/docs/ros/config/img/live_yaml.gif b/docs_versioned_docs/version-ros2jazzy/ros/config/img/live_yaml.gif
similarity index 100%
rename from docs/ros/config/img/live_yaml.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/config/img/live_yaml.gif
diff --git a/docs/ros/config/live.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/live.mdx
similarity index 100%
rename from docs/ros/config/live.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/live.mdx
diff --git a/docs/ros/config/services.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/services.mdx
similarity index 100%
rename from docs/ros/config/services.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/services.mdx
diff --git a/docs/ros/config/workspaces.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/workspaces.mdx
similarity index 100%
rename from docs/ros/config/workspaces.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/workspaces.mdx
diff --git a/docs/ros/config/yaml/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/_category_.json
similarity index 100%
rename from docs/ros/config/yaml/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/_category_.json
diff --git a/docs/ros/config/yaml/links.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/links.mdx
similarity index 100%
rename from docs/ros/config/yaml/links.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/links.mdx
diff --git a/docs/ros/config/yaml/manipulators.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/manipulators.mdx
similarity index 100%
rename from docs/ros/config/yaml/manipulators.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/manipulators.mdx
diff --git a/docs/ros/config/yaml/mounts.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/mounts.mdx
similarity index 100%
rename from docs/ros/config/yaml/mounts.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/mounts.mdx
diff --git a/docs/ros/config/yaml/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/overview.mdx
similarity index 100%
rename from docs/ros/config/yaml/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/overview.mdx
diff --git a/docs/ros/config/yaml/platform/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/_category_.json
similarity index 100%
rename from docs/ros/config/yaml/platform/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/_category_.json
diff --git a/docs/ros/config/yaml/platform/attachments/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/_category_.json
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/_category_.json
diff --git a/docs/ros/config/yaml/platform/attachments/a200.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/a200.mdx
similarity index 92%
rename from docs/ros/config/yaml/platform/attachments/a200.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/a200.mdx
index 05e27c9c3..31e8b315f 100644
--- a/docs/ros/config/yaml/platform/attachments/a200.mdx
+++ b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/a200.mdx
@@ -11,7 +11,7 @@ import A200SensorArch510 from "/docs_versioned_docs/version-ros2humble/component
import A200TopPlateDefault from "/docs_versioned_docs/version-ros2humble/components/yaml/attachments/a200/top_plate_default.mdx";
import A200TopPlateLarge from "/docs_versioned_docs/version-ros2humble/components/yaml/attachments/a200/top_plate_large.mdx";
import A200TopPlatePACS from "/docs_versioned_docs/version-ros2humble/components/yaml/attachments/a200/top_plate_pacs.mdx";
-import A200ObserverBackpack from "/docs/components/yaml/attachments/a200/observer_backpack.mdx";
+import A200ObserverBackpack from "/docs_versioned_docs/version-ros2jazzy/components/yaml/attachments/a200/observer_backpack.mdx";
## Bumper
The A200 can have bumpers of a variable length. By setting the `extension` parameter, the bumper can be extended if required.
@@ -35,7 +35,7 @@ The **large** top plate does not have a user rail and is primarily used to mount
#### Observer Backpack
-The Observer backpack is a large enclosure with multiple mounting locations for additional sensors. It is used by the [Husky Observer](https://docs.clearpathrobotics.com/docs/robots/solutions/husky_observer/).
+The Observer backpack is a large enclosure with multiple mounting locations for additional sensors. It is used by the [Husky Observer](/docs_robots/solutions/husky_observer/).
diff --git a/docs/ros/config/yaml/platform/attachments/dx1X0.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/dx1X0.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/dx1X0.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/dx1X0.mdx
diff --git a/docs/ros/config/yaml/platform/attachments/j100.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/j100.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/j100.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/j100.mdx
diff --git a/docs/ros/config/yaml/platform/attachments/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/overview.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/overview.mdx
diff --git a/docs/ros/config/yaml/platform/attachments/r100.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/r100.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/r100.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/r100.mdx
diff --git a/docs/ros/config/yaml/platform/attachments/w200.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/w200.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/attachments/w200.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/attachments/w200.mdx
diff --git a/docs/ros/config/yaml/platform/battery.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/battery.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/battery.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/battery.mdx
diff --git a/docs/ros/config/yaml/platform/controller.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/controller.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/controller.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/controller.mdx
diff --git a/docs/ros/config/yaml/platform/ekf.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/ekf.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/ekf.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/ekf.mdx
diff --git a/docs/ros/config/yaml/platform/extras.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/extras.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/extras.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/extras.mdx
diff --git a/docs/ros/config/yaml/platform/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/overview.mdx
similarity index 100%
rename from docs/ros/config/yaml/platform/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/platform/overview.mdx
diff --git a/docs/ros/config/yaml/sensors/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/_category_.json
similarity index 100%
rename from docs/ros/config/yaml/sensors/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/_category_.json
diff --git a/docs/ros/config/yaml/sensors/cameras.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/cameras.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/cameras.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/cameras.mdx
diff --git a/docs/ros/config/yaml/sensors/gps.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/gps.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/gps.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/gps.mdx
diff --git a/docs/ros/config/yaml/sensors/imu.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/imu.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/imu.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/imu.mdx
diff --git a/docs/ros/config/yaml/sensors/lidar2d.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar2d.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/lidar2d.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar2d.mdx
diff --git a/docs/ros/config/yaml/sensors/lidar3d.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar3d.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/lidar3d.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/lidar3d.mdx
diff --git a/docs/ros/config/yaml/sensors/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/overview.mdx
similarity index 100%
rename from docs/ros/config/yaml/sensors/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/sensors/overview.mdx
diff --git a/docs/ros/config/yaml/serial.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/serial.mdx
similarity index 67%
rename from docs/ros/config/yaml/serial.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/serial.mdx
index 28b812c15..ddf076fd7 100644
--- a/docs/ros/config/yaml/serial.mdx
+++ b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/serial.mdx
@@ -11,10 +11,10 @@ The Clearpath serial number is composed of two sections, separated by a hyphen,
At this moment, the supported robot platforms are:
-1. [Husky A200](../../../robots/outdoor_robots/husky/a200/user_manual_husky): `a200-0000`
-2. [Husky A300](../../../robots/outdoor_robots/husky/a300/user_manual_husky): `a300-0000`
-3. [Jackal J100](../../../robots/outdoor_robots/jackal/user_manual_jackal.mdx): `j100-0000`
-4. [Warthog W200](../../../robots/outdoor_robots/warthog/user_manual_warthog.mdx): `w200-0000`
+1. [Husky A200](/docs_robots/outdoor_robots/husky/a200/user_manual_husky): `a200-0000`
+2. [Husky A300](/docs_robots/outdoor_robots/husky/a300/user_manual_husky): `a300-0000`
+3. [Jackal J100](/docs_robots/outdoor_robots/jackal/user_manual_jackal): `j100-0000`
+4. [Warthog W200](/docs_robots/outdoor_robots/warthog/user_manual_warthog): `w200-0000`
Every robot platform has specific attachments that are selected based on the serial number passed. Therefore, it is **required** that a serial number is specified in the `robot.yaml`.
diff --git a/docs/ros/config/yaml/system.mdx b/docs_versioned_docs/version-ros2jazzy/ros/config/yaml/system.mdx
similarity index 100%
rename from docs/ros/config/yaml/system.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/config/yaml/system.mdx
diff --git a/docs/ros/installation/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/installation/_category_.json
similarity index 100%
rename from docs/ros/installation/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/_category_.json
diff --git a/docs/ros/installation/controller.mdx b/docs_versioned_docs/version-ros2jazzy/ros/installation/controller.mdx
similarity index 100%
rename from docs/ros/installation/controller.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/controller.mdx
diff --git a/docs/ros/installation/img/wifi_interface.jpg b/docs_versioned_docs/version-ros2jazzy/ros/installation/img/wifi_interface.jpg
similarity index 100%
rename from docs/ros/installation/img/wifi_interface.jpg
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/img/wifi_interface.jpg
diff --git a/docs/ros/installation/offboard_pc.mdx b/docs_versioned_docs/version-ros2jazzy/ros/installation/offboard_pc.mdx
similarity index 100%
rename from docs/ros/installation/offboard_pc.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/offboard_pc.mdx
diff --git a/docs/ros/installation/robot.mdx b/docs_versioned_docs/version-ros2jazzy/ros/installation/robot.mdx
similarity index 98%
rename from docs/ros/installation/robot.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/robot.mdx
index 4d8b850bc..07811711f 100644
--- a/docs/ros/installation/robot.mdx
+++ b/docs_versioned_docs/version-ros2jazzy/ros/installation/robot.mdx
@@ -311,8 +311,8 @@ sudo systemctl daemon-reload && sudo systemctl start clearpath-robot.service
#### Additional settings
- Certain sensors may require additional setup, please review the [Accessories](../../robots/accessories/accessories.mdx) pages
+ Certain sensors may require additional setup, please review the [Accessories](/docs_robots/accessories) pages
for any additional instructions for the sensors that you are using. For example, the Blackfly camera has additional instructions
- listed under [software bringup](../../robots/accessories/sensors/cameras/flir_blackfly_s#software-bringup).
+ listed under [software bringup](/docs_robots/accessories/sensors/cameras/flir_blackfly_s#software-bringup).
diff --git a/docs/ros/installation/upgrading.mdx b/docs_versioned_docs/version-ros2jazzy/ros/installation/upgrading.mdx
similarity index 100%
rename from docs/ros/installation/upgrading.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/installation/upgrading.mdx
diff --git a/docs/ros/networking/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/networking/_category_.json
similarity index 100%
rename from docs/ros/networking/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/_category_.json
diff --git a/docs/ros/networking/computer_setup.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/computer_setup.mdx
similarity index 100%
rename from docs/ros/networking/computer_setup.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/computer_setup.mdx
diff --git a/docs/ros/networking/img/clearpath_setup-interface.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-interface.png
similarity index 100%
rename from docs/ros/networking/img/clearpath_setup-interface.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-interface.png
diff --git a/docs/ros/networking/img/clearpath_setup-netplan.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-netplan.png
similarity index 100%
rename from docs/ros/networking/img/clearpath_setup-netplan.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-netplan.png
diff --git a/docs/ros/networking/img/clearpath_setup-ssid.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-ssid.png
similarity index 100%
rename from docs/ros/networking/img/clearpath_setup-ssid.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-ssid.png
diff --git a/docs/ros/networking/img/clearpath_setup-wifi.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-wifi.png
similarity index 100%
rename from docs/ros/networking/img/clearpath_setup-wifi.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/clearpath_setup-wifi.png
diff --git a/docs/ros/networking/img/network-integrity-troubleshooting-flowchart.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/network-integrity-troubleshooting-flowchart.png
similarity index 100%
rename from docs/ros/networking/img/network-integrity-troubleshooting-flowchart.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/network-integrity-troubleshooting-flowchart.png
diff --git a/docs/ros/networking/img/radiation-pattern-1.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/radiation-pattern-1.png
similarity index 100%
rename from docs/ros/networking/img/radiation-pattern-1.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/radiation-pattern-1.png
diff --git a/docs/ros/networking/img/radiation-pattern-2.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/radiation-pattern-2.png
similarity index 100%
rename from docs/ros/networking/img/radiation-pattern-2.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/radiation-pattern-2.png
diff --git a/docs/ros/networking/img/ros2-comms-troubleshooting-flowchart.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-comms-troubleshooting-flowchart.png
similarity index 100%
rename from docs/ros/networking/img/ros2-comms-troubleshooting-flowchart.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-comms-troubleshooting-flowchart.png
diff --git a/docs/ros/networking/img/ros2-fastdds-command-center-diagram.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-command-center-diagram.png
similarity index 100%
rename from docs/ros/networking/img/ros2-fastdds-command-center-diagram.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-command-center-diagram.png
diff --git a/docs/ros/networking/img/ros2-fastdds-discovery-server-diagram.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-discovery-server-diagram.png
similarity index 100%
rename from docs/ros/networking/img/ros2-fastdds-discovery-server-diagram.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-discovery-server-diagram.png
diff --git a/docs/ros/networking/img/ros2-fastdds-fully-connected-diagram.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-fully-connected-diagram.png
similarity index 100%
rename from docs/ros/networking/img/ros2-fastdds-fully-connected-diagram.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-fully-connected-diagram.png
diff --git a/docs/ros/networking/img/ros2-fastdds-simple-discovery-diagram.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-simple-discovery-diagram.png
similarity index 100%
rename from docs/ros/networking/img/ros2-fastdds-simple-discovery-diagram.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/ros2-fastdds-simple-discovery-diagram.png
diff --git a/docs/ros/networking/img/wireshark-io-graph.png b/docs_versioned_docs/version-ros2jazzy/ros/networking/img/wireshark-io-graph.png
similarity index 100%
rename from docs/ros/networking/img/wireshark-io-graph.png
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/img/wireshark-io-graph.png
diff --git a/docs/ros/networking/network_ip_addresses.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_ip_addresses.mdx
similarity index 100%
rename from docs/ros/networking/network_ip_addresses.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_ip_addresses.mdx
diff --git a/docs/ros/networking/network_troubleshooting/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/_category_.json
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/_category_.json
diff --git a/docs/ros/networking/network_troubleshooting/intermittent_connectivity.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/intermittent_connectivity.mdx
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/intermittent_connectivity.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/intermittent_connectivity.mdx
diff --git a/docs/ros/networking/network_troubleshooting/network_integrity.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/network_integrity.mdx
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/network_integrity.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/network_integrity.mdx
diff --git a/docs/ros/networking/network_troubleshooting/network_troubleshooting_tools.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/network_troubleshooting_tools.mdx
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/network_troubleshooting_tools.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/network_troubleshooting_tools.mdx
diff --git a/docs/ros/networking/network_troubleshooting/ros2_connectivity.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/ros2_connectivity.mdx
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/ros2_connectivity.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/ros2_connectivity.mdx
diff --git a/docs/ros/networking/network_troubleshooting/troubleshooting_overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/troubleshooting_overview.mdx
similarity index 100%
rename from docs/ros/networking/network_troubleshooting/troubleshooting_overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/network_troubleshooting/troubleshooting_overview.mdx
diff --git a/docs/ros/networking/ntp.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/ntp.mdx
similarity index 100%
rename from docs/ros/networking/ntp.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/ntp.mdx
diff --git a/docs/ros/networking/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/overview.mdx
similarity index 100%
rename from docs/ros/networking/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/overview.mdx
diff --git a/docs/ros/networking/ros2-networking.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/ros2-networking.mdx
similarity index 100%
rename from docs/ros/networking/ros2-networking.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/ros2-networking.mdx
diff --git a/docs/ros/networking/ros2_communication.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/ros2_communication.mdx
similarity index 100%
rename from docs/ros/networking/ros2_communication.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/ros2_communication.mdx
diff --git a/docs/ros/networking/ros2_discovery_config.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/ros2_discovery_config.mdx
similarity index 100%
rename from docs/ros/networking/ros2_discovery_config.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/ros2_discovery_config.mdx
diff --git a/docs/ros/networking/standard_ip_addresses.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/standard_ip_addresses.mdx
similarity index 100%
rename from docs/ros/networking/standard_ip_addresses.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/standard_ip_addresses.mdx
diff --git a/docs/ros/networking/wifi_fundamentals.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/wifi_fundamentals.mdx
similarity index 100%
rename from docs/ros/networking/wifi_fundamentals.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/wifi_fundamentals.mdx
diff --git a/docs/ros/networking/wifi_hardware.mdx b/docs_versioned_docs/version-ros2jazzy/ros/networking/wifi_hardware.mdx
similarity index 100%
rename from docs/ros/networking/wifi_hardware.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/networking/wifi_hardware.mdx
diff --git a/docs/ros/ros.mdx b/docs_versioned_docs/version-ros2jazzy/ros/ros.mdx
similarity index 100%
rename from docs/ros/ros.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/ros.mdx
diff --git a/docs/ros/tutorials/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/_category_.json
similarity index 100%
rename from docs/ros/tutorials/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/_category_.json
diff --git a/docs/ros/tutorials/cheat_sheet.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/cheat_sheet.mdx
similarity index 100%
rename from docs/ros/tutorials/cheat_sheet.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/cheat_sheet.mdx
diff --git a/docs/ros/tutorials/driving.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/driving.mdx
similarity index 100%
rename from docs/ros/tutorials/driving.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/driving.mdx
diff --git a/docs/ros/tutorials/img/rviz_add_button.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_add_button.png
similarity index 100%
rename from docs/ros/tutorials/img/rviz_add_button.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_add_button.png
diff --git a/docs/ros/tutorials/img/rviz_add_visualization.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_add_visualization.png
similarity index 100%
rename from docs/ros/tutorials/img/rviz_add_visualization.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_add_visualization.png
diff --git a/docs/ros/tutorials/img/rviz_blank.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_blank.png
similarity index 100%
rename from docs/ros/tutorials/img/rviz_blank.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_blank.png
diff --git a/docs/ros/tutorials/img/rviz_laserscan.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_laserscan.png
similarity index 100%
rename from docs/ros/tutorials/img/rviz_laserscan.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_laserscan.png
diff --git a/docs/ros/tutorials/img/rviz_no_model.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_no_model.png
similarity index 100%
rename from docs/ros/tutorials/img/rviz_no_model.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/rviz_no_model.png
diff --git a/docs/ros/tutorials/img/view_robot.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/view_robot.png
similarity index 100%
rename from docs/ros/tutorials/img/view_robot.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/img/view_robot.png
diff --git a/docs/ros/tutorials/manipulation/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/_category_.json
similarity index 100%
rename from docs/ros/tutorials/manipulation/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/_category_.json
diff --git a/docs/ros/tutorials/manipulation/gazebo.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/gazebo.mdx
similarity index 100%
rename from docs/ros/tutorials/manipulation/gazebo.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/gazebo.mdx
diff --git a/docs/ros/tutorials/manipulation/img/moveit_gazebo.gif b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/img/moveit_gazebo.gif
similarity index 100%
rename from docs/ros/tutorials/manipulation/img/moveit_gazebo.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/manipulation/img/moveit_gazebo.gif
diff --git a/docs/ros/tutorials/navigation_demos/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/_category_.json
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/_category_.json
diff --git a/docs/ros/tutorials/navigation_demos/img/localization.gif b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/localization.gif
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/img/localization.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/localization.gif
diff --git a/docs/ros/tutorials/navigation_demos/img/nav2.gif b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/nav2.gif
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/img/nav2.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/nav2.gif
diff --git a/docs/ros/tutorials/navigation_demos/img/slam.gif b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/slam.gif
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/img/slam.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/img/slam.gif
diff --git a/docs/ros/tutorials/navigation_demos/localization.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/localization.mdx
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/localization.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/localization.mdx
diff --git a/docs/ros/tutorials/navigation_demos/nav2.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/nav2.mdx
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/nav2.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/nav2.mdx
diff --git a/docs/ros/tutorials/navigation_demos/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/overview.mdx
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/overview.mdx
diff --git a/docs/ros/tutorials/navigation_demos/slam.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/slam.mdx
similarity index 100%
rename from docs/ros/tutorials/navigation_demos/slam.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/navigation_demos/slam.mdx
diff --git a/docs/ros/tutorials/rviz.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/rviz.mdx
similarity index 100%
rename from docs/ros/tutorials/rviz.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/rviz.mdx
diff --git a/docs/ros/tutorials/simulator/_category_.json b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/_category_.json
similarity index 100%
rename from docs/ros/tutorials/simulator/_category_.json
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/_category_.json
diff --git a/docs/ros/tutorials/simulator/img/driving.gif b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/img/driving.gif
similarity index 100%
rename from docs/ros/tutorials/simulator/img/driving.gif
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/img/driving.gif
diff --git a/docs/ros/tutorials/simulator/img/simulation.png b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/img/simulation.png
similarity index 100%
rename from docs/ros/tutorials/simulator/img/simulation.png
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/img/simulation.png
diff --git a/docs/ros/tutorials/simulator/install.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/install.mdx
similarity index 100%
rename from docs/ros/tutorials/simulator/install.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/install.mdx
diff --git a/docs/ros/tutorials/simulator/overview.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/overview.mdx
similarity index 100%
rename from docs/ros/tutorials/simulator/overview.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/overview.mdx
diff --git a/docs/ros/tutorials/simulator/simulate.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/simulate.mdx
similarity index 100%
rename from docs/ros/tutorials/simulator/simulate.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/simulator/simulate.mdx
diff --git a/docs/ros/tutorials/video_over_wifi.mdx b/docs_versioned_docs/version-ros2jazzy/ros/tutorials/video_over_wifi.mdx
similarity index 100%
rename from docs/ros/tutorials/video_over_wifi.mdx
rename to docs_versioned_docs/version-ros2jazzy/ros/tutorials/video_over_wifi.mdx
diff --git a/docs_versioned_sidebars/version-ros1noetic-sidebars.json b/docs_versioned_sidebars/version-ros1noetic-sidebars.json
index 32d86dd40..f328fc26e 100644
--- a/docs_versioned_sidebars/version-ros1noetic-sidebars.json
+++ b/docs_versioned_sidebars/version-ros1noetic-sidebars.json
@@ -1,10 +1,4 @@
{
- "robots": [
- {
- "type": "autogenerated",
- "dirName": "robots"
- }
- ],
"ros": [
{
"type": "autogenerated",
diff --git a/docs_versioned_sidebars/version-ros2humble-sidebars.json b/docs_versioned_sidebars/version-ros2humble-sidebars.json
index 32d86dd40..f328fc26e 100644
--- a/docs_versioned_sidebars/version-ros2humble-sidebars.json
+++ b/docs_versioned_sidebars/version-ros2humble-sidebars.json
@@ -1,10 +1,4 @@
{
- "robots": [
- {
- "type": "autogenerated",
- "dirName": "robots"
- }
- ],
"ros": [
{
"type": "autogenerated",
diff --git a/docs_versioned_sidebars/version-ros2jazzy-sidebars.json b/docs_versioned_sidebars/version-ros2jazzy-sidebars.json
new file mode 100644
index 000000000..f328fc26e
--- /dev/null
+++ b/docs_versioned_sidebars/version-ros2jazzy-sidebars.json
@@ -0,0 +1,8 @@
+{
+ "ros": [
+ {
+ "type": "autogenerated",
+ "dirName": "ros"
+ }
+ ]
+}
diff --git a/docs_versions.json b/docs_versions.json
index 718f9e3e1..fd67d3e3f 100644
--- a/docs_versions.json
+++ b/docs_versions.json
@@ -1,4 +1,5 @@
[
+ "ros2jazzy",
"ros2humble",
"ros1noetic"
]
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 1333bc048..53487e17a 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -49,6 +49,9 @@ const config = {
rehypePlugins: [rehypeKatex],
showLastUpdateTime: true,
versions: {
+ ros2jazzy: {
+ label: 'ROS 2 Jazzy',
+ },
ros2humble: {
label: 'ROS 2 Humble',
},
@@ -56,7 +59,23 @@ const config = {
label: 'ROS 1 Noetic',
}
},
- includeCurrentVersion: true,
+ includeCurrentVersion: false,
+ admonitions: {
+ keywords: ['safety-danger', 'safety-warning', 'safety-caution'],
+ extendDefaults: true,
+ },
+ },
+ ],
+ [
+ "@docusaurus/plugin-content-docs",
+ {
+ id: "docs_robots",
+ path: "docs_robots",
+ routeBasePath: "docs_robots",
+ sidebarPath: require.resolve("./sidebars.js"),
+ remarkPlugins: [remarkMath],
+ rehypePlugins: [rehypeKatex],
+ showLastUpdateTime: true,
admonitions: {
keywords: ['safety-danger', 'safety-warning', 'safety-caution'],
extendDefaults: true,
@@ -106,11 +125,11 @@ const config = {
},
items: [
{
- type: "docsVersion",
- to: "/docs/robots/",
+ type: "doc",
+ docId: "robots",
label: "Robots",
position: "left",
- docsPluginId: "docs",
+ docsPluginId: "docs_robots",
},
{
type: "docsVersion",
diff --git a/outdoornav_user_manual_versioned_docs/version-0.10.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.10.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index f8b6842ef..fe17d103a 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.10.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.10.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/outdoornav_user_manual_versioned_docs/version-0.11.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.11.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index f8b6842ef..fe17d103a 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.11.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.11.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/outdoornav_user_manual_versioned_docs/version-0.12.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.12.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index f8b6842ef..fe17d103a 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.12.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.12.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/outdoornav_user_manual_versioned_docs/version-0.13.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.13.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index de411daf7..ec9073447 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.13.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.13.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/outdoornav_user_manual_versioned_docs/version-0.14.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.14.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index de411daf7..ec9073447 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.14.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.14.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.
diff --git a/outdoornav_user_manual_versioned_docs/version-0.9.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx b/outdoornav_user_manual_versioned_docs/version-0.9.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
index f8b6842ef..fe17d103a 100644
--- a/outdoornav_user_manual_versioned_docs/version-0.9.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
+++ b/outdoornav_user_manual_versioned_docs/version-0.9.0/integration_requirements/hardware_integration_requirements/starter_kit_hardware_checklist.mdx
@@ -13,7 +13,7 @@ The OutdoorNav Starter Kit from Clearpath Robotics contains:
- RealSense D435f (x2) Depth Camera
To integrate this kit onto your robot, ensure that all of the requirements below are satisfied for proper operation of the OutdoorNav software.
-Refer to the [OutdoorNav Starter Kit](/docs/robots/accessories/add-ons/outdoornav_starter_kit) for additional
+Refer to the [OutdoorNav Starter Kit](/docs_robots/accessories/add-ons/outdoornav_starter_kit) for additional
integration details.