Restructure dev and user guides

docs/developer-guide/contribution-guidelines.md

@@ -8,11 +8,11 @@ Although we strive for complete in-code documentation, in practice this sometime
 
 Here is a summary of the key goals and philosophies behind ROSflight. As you look to make contributions to the project, keep these in mind.
 
-- Only include the things that most people will need. The goal of this would be to do most of the work so people can get a MAV in the air quickly and easily, but not overcomplicate the code with features that only a small portion of users would need.
+- **Only include the things that most people will need.** The goal of this would be to do most of the work so people can get a MAV in the air quickly and easily, but not overcomplicate the code with features that only a small portion of users would need.
 
-- Be modular and adaptable for many research-centric use cases. This will be accomplished by putting the majority of the autopilot in a well-designed ROS2 framework. That which needs to be on the microcontroller will need to be done so carefully with good coding practices. Additionally, microcontroller code that is the most likely to be expanded upon should include clear interfaces and instructions for doing so.
+- **Be modular and adaptable for many research-centric use cases.** This will be accomplished by putting the majority of the autopilot in a well-designed ROS2 framework. That which needs to be on the microcontroller will need to be done so carefully with good coding practices. Additionally, microcontroller code that is the most likely to be expanded upon should include clear interfaces and instructions for doing so.
 
-- Keep everything simple and well documented. The key goal here is to minimize the amount of time and effort it takes someone to go from knowing nothing about ROSflight to being able to implement their own features and making meaningful progress with their research.
+- **Keep everything simple and well documented.** The key goal here is to minimize the amount of time and effort it takes someone to go from knowing nothing about ROSflight to being able to implement their own features and making meaningful progress with their research.
 
 ## Communication
 

docs/developer-guide/firmware/debugging.md

@@ -12,9 +12,9 @@ This guide assumes you are running Ubuntu 22.04 LTS, which is the currently supp
 
 ## General Setup
 
-Follow the guide in [Building and Flashing](building-and-flashing.md) to install the compiler toolchain.
+Follow the guide in [Building and Flashing](../../user-guide/hardware-and-rosflight/flight-controller-setup.md#building-and-flashing-the-firmware) to install the compiler toolchain.
 
-Also make sure you have configured your computer as described in the [Serial Port Configuration](../../user-guide/concepts/flight-controller-setup.md#serial-port-configuration) section of the user guide.
+Also make sure you have configured your computer as described in the [Serial Port Configuration](../../user-guide/hardware-and-rosflight/flight-controller-setup.md#serial-port-configuration) section of the user guide.
 
 ### Connect debugger to flight controller
 

docs/developer-guide/firmware/unit-tests.md

@@ -41,7 +41,7 @@ If you want to manually build and run the unit tests, first build them with the
 cd <firmware_directory>
 mkdir build
 cd build
-cmake .. -DBUILD_TEST=TRUE
+cmake .. -DBOARD_TO_BUILD=test
 make
 ```
 

docs/stylesheets/extra.css

@@ -0,0 +1,3 @@
+.md-grid {
+  max-width: 1440px;
+}