Fix broken links

8BitJosh · 8BitJosh · commit 1da26c01fc02 · 2023-08-27T19:37:00.000+01:00
diff --git a/kit/brain_board/advanced.md b/kit/brain_board/advanced.md
@@ -5,7 +5,7 @@ title: Brain Board - Advanced
 
 # Brain Board - Advanced
 
-When connected to your [Brain Board WiFi]({{ site.baseurl }}/kit/wifi), it is possible to access the Brain Board via a terminal interface. The Brain Board is running Student Robotics OS, a purpose-built Linux distribution that does not have all of the conveniences of a usual Linux system.
+When connected to your [Brain Board WiFi]({{ site.baseurl }}/kit/brain_board/wifi), it is possible to access the Brain Board via a terminal interface. The Brain Board is running Student Robotics OS, a purpose-built Linux distribution that does not have all of the conveniences of a usual Linux system.
 
 <div class="warning">
 Proceed at your own risk. We only provide limited support for these advanced features.
diff --git a/kit/brain_board/index.md b/kit/brain_board/index.md
@@ -61,7 +61,7 @@ The SD card is located on the underside of the board underneath the green power
 
 To fully update your Brain Board's software, or refresh it if you think it's not working correctly, you can flash our SD card image onto the microSD card in your Brain Board.
 
-To update the SD card, you'll need to download our image from the [updates page]({{ site.baseurl }}/kit/brain_board/updates). The latest version is `{{ latest_version }}`.
+To update the SD card, you'll need to download our image from the [updates page]({{ site.baseurl }}/kit/brain_board/robot_os). The latest version is `{{ latest_version }}`.
 The flashing procedure is identical to flashing Raspberry Pi images.
 
 ### Etcher
diff --git a/kit/index.md b/kit/index.md
@@ -18,7 +18,7 @@ The boards provided are as follows; more details can be found on their individua
  * [Brain Board](/docs/kit/brain_board)
  * [Power Board](/docs/kit/power_board)
  * [Motor Board x2](/docs/kit/motor_board)
- * [Ruggeduino (including two screw shields)](/docs/kit/ruggeduino)
+ * [Ruggeduino (including two screw shields)](/docs/kit/arduino)
  * [Servo Board](/docs/kit/servo_board)
 
 Ancillary Parts
diff --git a/programming/arduino/custom_firmware.md b/programming/arduino/custom_firmware.md
@@ -10,15 +10,15 @@ Arduino custom firmware
 This documentation refers to a feature which is only available on the physical robot kits.
 </div>
 
-The Ruggeduino that came as part of your kit was shipped with a firmware that provides the functionality outlined in the [Ruggeduino](/docs/programming/sr/ruggeduinos) page.
+The Ruggeduino that came as part of your kit was shipped with a firmware that provides the functionality outlined in the [Ruggeduino](/docs/programming/arduino) page.
 You may wish to extend the functionality of this firmware, or completely replace it.
 The `sr.robot3` library provides support for three Ruggeduino firmware scenarios:
 
  1. Default SR firmware
  2. [Extended SR firmware](#extension): Firmwares that add commands to the default SR firmware.
  3. [Completely custom](#completely): Any firmware not derived from the SR firmware.
 
-By default, the [`sr.robot3`](/docs/programming/sr/) library assumes that all connected Ruggeduinos are running the SR firmware
+By default, the [`sr.robot3`](/docs/programming/robot_api/) library assumes that all connected Ruggeduinos are running the SR firmware
 or firmware which is compatible with the SR Ruggeduino firmware.
 If you're using completely custom firmware, you'll need to tell the kit to ignore the ruggeduino so that you're able to define your own setup logic.
 
@@ -27,7 +27,7 @@ If you're using completely custom firmware, you'll need to tell the kit to ignor
 
 <div class="warning" markdown="1">
 Because the API sets all pins to inputs when the robot is initialised, you cannot set pin modes in the setup function as these will be overridden.
-In order to setup pins you can either create a function on the ruggeduino that you call after your robot is initialised or use the [Python functions](/docs/programming/sr/ruggeduinos/#pin-modes) to setup the pins.
+In order to setup pins you can either create a function on the ruggeduino that you call after your robot is initialised or use the [Python functions](/docs/programming/arduino/#pin-modes) to setup the pins.
 </div>
 
 You may wish to extend the SR firmware with additional functionality.
diff --git a/programming/index.md b/programming/index.md
@@ -6,18 +6,18 @@ title: Programming
 Programming Your Robot
 ======================
 
-Robots that are made using the SR kit are programmed with [Python](/docs/programming/python/) which is made possible with a custom-built Python library, `sr.robot3`; see [here](/docs/programming/sr/) for more details. The pages under this section should contain all of the information you need to know to successfully code for your robot.
+<!-- Robots that are made using the SR kit are programmed with [Python](/docs/programming/python/) which is made possible with a custom-built Python library, `sr.robot3`; see [here](/docs/programming/robot_api/) for more details. The pages under this section should contain all of the information you need to know to successfully code for your robot.
 
 * In order to develop the code for your robot, we recommend that you use a code
   editor. For more information about this, including some suggestions for
   suitable editors, see the [Code Editors](/docs/programming/editors/) section.
 
 * Under the [Python](/docs/programming/python/) section, some of the more intricate features of Python are explained in sufficient detail to program a robot. Links to tutorials are also provided to introduce a new programmer to Python.
 
-* Under the [sr](/docs/programming/sr/) section is an API reference for the Student Robotics module, used to interface with the hardware.
-
+* Under the [sr](/docs/programming/sr/) section is an API reference for the Student Robotics module, used to interface with the hardware. -->
 
 
+<!--
 TODO - below is from python page
 
 Student Robotics robots are all programmed in [Python 3.10](https://www.python.org);
@@ -36,4 +36,4 @@ There are a number of tutorials out there which might help you to learn to progr
 * A number of tutorials for beginners are linked to from [here](https://wiki.python.org/moin/BeginnersGuide/NonProgrammers).
     [Wikibooks Tutorial](https://en.wikibooks.org/wiki/Non-Programmer%27s_Tutorial_for_Python_3) seems like a good one.
 
-* [The Official Docs](https://docs.python.org/3.10/), for the version of python on the [Brain Board](/docs/kit/brain_board).
+* [The Official Docs](https://docs.python.org/3.10/), for the version of python on the [Brain Board](/docs/kit/brain_board). -->
diff --git a/programming/radio.md b/programming/radio.md
@@ -129,4 +129,4 @@ station_code
 owned_by
 : The zone id of the robot that currently owns the stations territory. A `None` value indicates an unclaimed territory.
   <br>
-  Remember that you can find out which zone your robot is in using <a href="/docs/programming/sr/#OtherRobotAttributes"><code>R.zone</code></a>.
+  Remember that you can find out which zone your robot is in using <a href="/docs/programming/robot_api/"><code>R.zone</code></a>.
diff --git a/programming/robot_api/index.md b/programming/robot_api/index.md
@@ -34,11 +34,11 @@ R = Robot()
 
 Within your `Robot` (`R` in this case), you then have access to the following attributes:
 
-* [motors](/docs/programming/sr/motors/)
-* [power](/docs/programming/sr/power/)
-* [servos](/docs/programming/sr/servos/)
-* [ruggeduinos](/docs/programming/sr/ruggeduinos/)
-* [vision](/docs/programming/sr/vision/)
+* [motors](/docs/programming/motors)
+* [power](/docs/programming/power)
+* [servos](/docs/programming/servos)
+* [ruggeduinos](/docs/programming/arduino/)
+* [vision](/docs/programming/vision/)
 
 They can be used in your code just like the example above.
 Note that `motors`, `ruggeduinos`, and `servos` are Python lists, and so should be accessed as such.
diff --git a/programming/simulator_programming.md b/programming/simulator_programming.md
@@ -126,7 +126,7 @@ information about other objects within the simulation. This simulates the
 system of fiducial markers which the physical robot's camera can detect.
 
 The information returned by the simulated vision API is similar to the physical
-robot's [vision API](/docs/programming/sr/vision/), however there are a number
+robot's [vision API](/docs/programming/vision/), however there are a number
 of differences as are noted in the vision docs.
 
 ### Pressure sensing
diff --git a/simulator/index.md b/simulator/index.md
diff --git a/tutorials/assembly.md b/tutorials/assembly.md
@@ -25,7 +25,7 @@ Each of the modules in the kit needs to be provided with both a control signal a
 All the boards use USB to connect to the [Brain Board](/docs/kit/brain_board) so it can tell them what to do.
 If you run out of USB ports on the Brain Board itself, then you can use the provided USB hubs to provide more ports.
 
-Most of the boards (with the exception of the [Ruggeduino](/docs/kit/ruggeduino)) also need an additional power connection.
+Most of the boards (with the exception of the [Ruggeduino](/docs/kit/arduino)) also need an additional power connection.
 This should be provided from the [Power Board](/docs/kit/power_board).
 
 The following table summarises the connections which need to be made for each board.
@@ -35,7 +35,7 @@ Board                                   | Power
 [Brain Board](/docs/kit/brain_board)    | 12V, must be connected to L2
 [Power Board](/docs/kit/power_board)    | 12V, via the yellow XT60 to the [battery](/docs/kit/batteries)
 [Motor Board](/docs/kit/motor_board)    | 12V
-[Ruggeduino](/docs/kit/ruggeduino)      | via USB
+[Ruggeduino](/docs/kit/arduino)      | via USB
 [Servo Board](/docs/kit/servo_board)    | 12V
 
 In order to connect the Brain, Motor and Servo Boards to the Power Board, you will need to create some power cables.
diff --git a/tutorials/basic_motor_control.md b/tutorials/basic_motor_control.md
@@ -127,7 +127,7 @@ while True:
 ~~~~~
 
 You're familiar with the first few lines; in fact, the only lines you may not be familiar with are the `R.motor_board...` lines.
-For a comprehensive reference to the `motor` object, see the `sr.robot3` module's [Motors](/docs/programming/sr/motors/) page.
+For a comprehensive reference to the `motor` object, see the `sr.robot3` module's [Motors](/docs/programming/motors) page.
 But, to summarise:
 
 <div class="info" markdown="1">
diff --git a/tutorials/editors/vscode.md b/tutorials/editors/vscode.md
@@ -42,7 +42,7 @@ you'll need to make the library available within the Python environment that you
 This documentation refers to a feature which is only available from software version <code>2023.1.0</code> and later.
 </div>
 
-When connected to the [robot's WiFi hotspot]({{ site.baseurl }}/kit/wifi), it is possible to attach VS Code's
+When connected to the [robot's WiFi hotspot]({{ site.baseurl }}/kit/brain_board/wifi), it is possible to attach VS Code's
 debugger to the robot by performing the following steps:
 
 1. Ensure the [Python extension](#python-extension) is installed.
diff --git a/tutorials/setting_up_simulator.md b/tutorials/setting_up_simulator.md
@@ -24,7 +24,7 @@ You will also need Python installed.
 | macOS    | 3.8-3.10                 |
 | Linux    | 3.8-3.10                 |
 
-There are a small number of [external libraries]({{ site.baseurl }}/programming/python/libraries#simulator)
+There are a small number of [external libraries]({{ site.baseurl }}/kit/brain_board/python_libraries#simulator)
 which will be available to your robot code during the competition. Note that for
 local development you will need to install these yourself.
 
diff --git a/tutorials/using_the_simulator.md b/tutorials/using_the_simulator.md
@@ -38,8 +38,8 @@ speeds (▶▶ and ▶▶▶).
 
 These differences mean that your code will need to use a different mechanism to
 find the current time or to sleep within the simulation. Find out more by
-heading over to the [simulator programming docs](./programming).
+heading over to the [simulator programming docs](/docs/programming/simulator_programming).
 
 ## Programming
 
-Once you have the simulator installed you can begin [programming your robot](./programming) in the simulator.
+Once you have the simulator installed you can begin [programming your robot](/docs/programming/simulator_programming) in the simulator.
