Add gs build guide and create initial setup guide page, other minor fixes

Author: camspec

docs/astro.config.mjs

@@ -63,10 +63,6 @@ export default defineConfig({
           label: 'FreeRTOS Tasks',
           autogenerate: { directory: 'tasks' },
         },
-        {
-          label: 'Guides',
-          autogenerate: { directory: 'guides' },
-        },
       ],
     }),
   ],

docs/src/content/docs/builds/build-gs.mdx

@@ -3,8 +3,47 @@ title: Building the ground station
 description: On how to build for ground station
 sidebar:
   badge:
-    text: WIP
-    variant: caution
+    text: New
+    variant: success
   order: 2
 ---
+import { Steps } from '@astrojs/starlight/components';
+
 The following guide outlines a procedure to build the ground station.
+
+## Compiling for the ground station
+From the root directory, run the following commands:
+```shell
+mkdir -p build_gs && cd build_gs
+cmake .. -DCMAKE_BUILD_TYPE=GS
+cmake --build .
+```
+
+:::tip[Tip: Reducing Build Time]{icon="setting"}
+The `cmake --build .` takes some time to run since it is using a single thread to compile. To speed up the process we can replace it with one of the following commands:
+1. `make -j 16` (Recommended for most systems)
+2. `make -j 32` (This is faster but depends on if your system can handle 32 parallel jobs)
+:::
+
+## Setting up frontend development
+To run the frontend, Deno 2 must be installed. If it isn't, see [Initial setup](/OBC-firmware/start-here/setup/) and follow it to set up the database as well.
+
+Run all commands from the root directory.
+
+### Installing the frontend
+```shell
+cd gs/frontend
+deno install --frozen
+```
+### Running the ARO frontend
+This will start the frontend at `localhost:5173`.
+```shell
+cd gs/frontend/aro
+deno task dev
+```
+### Running the MCC frontend
+This will start the frontend at `localhost:5173`.
+```shell
+cd gs/frontend/mcc
+deno task dev
+```

docs/src/content/docs/builds/build-obc.mdx

@@ -10,19 +10,20 @@ The following is a simple guide for building the app for the OBC and flashing.
 
 ## Compiling for the OBC
 <Steps>
-1. From the root directory you can run the following commands
+1. Before compiling, ensure that the Python virtual environment is activated. If you do not have this configured, see [Initial setup](/OBC-firmware/start-here/setup/).
+2. From the root directory, run the following commands:
     ```shell
     mkdir -p build_arm && cd build_arm
     cmake .. -DCMAKE_BUILD_TYPE=OBC
     cmake --build .
     ```
 
     :::tip[Tip: Reducing Build Time]{icon="setting"}
-    The `cmake --build .` takes some time to run since it is using a single thread to compile. To speed up the process we can replace it with one of the following commands...
+    The `cmake --build .` takes some time to run since it is using a single thread to compile. To speed up the process we can replace it with one of the following commands:
     1. `make -j 16` (Recommended for most systems)
     2. `make -j 32` (This is faster but depends on if your system can handle 32 parallel jobs)
     :::
-2. There are also plenty of extra options that you can use besides `-DCMAKE_BUILD_TYPE` by appending them to the `cmake ..` command. Take a look at the [CMake Options Guide](/OBC-firmware/builds/cmake-options/).
+3. There are also plenty of extra options that you can use besides `-DCMAKE_BUILD_TYPE` by appending them to the `cmake ..` command. Take a look at the [CMake options guide](/OBC-firmware/builds/cmake-options/).
 
     :::caution
     Make sure to specify the `-DBOARD_TYPE=` option to avoid any unwanted behavior

docs/src/content/docs/comms/adding-commands.md

@@ -9,7 +9,7 @@ sidebar:
 ---
 The following is a guide to adding commands to ensure that they work in the python and c sections of this code base. (To navigate quickly, github provides a table of contents via the little list icon on the README header)
 
-## Adding commands to the C Side
+## Adding commands to the C side
 ### Step 1: Adding the command id
 1. Navigate to `obc_gs_command_id.h` and in the `cmd_callback_id_t` enum struct, add your command id. This must be **before** `NUM_CMD_CALLBACKS` (since we use it to count the number of commands throughout the codebase). The command should be written in uppercase with underscores as spaces and should be prefixed with `CMD`. As an example, `CMD_MAPLE_LEAFS` is correct but `CmdMapleLeafs`, `CMDMAPLELEAFS`, `cmd_maple_leafs` are not.
 ```c

docs/src/content/docs/guides/example.md

@@ -5,7 +5,7 @@ sidebar:
   badge:
     text: WIP
     variant: caution
-  order: 3
+  order: 4
 ---
 import { FileTree } from '@astrojs/starlight/components';
 

docs/src/content/docs/start-here/file-structure.mdx

@@ -0,0 +1,13 @@
+---
+title: Initial setup
+description: Initial setup for your development workflow
+sidebar:
+  order: 2
+  badge:
+    text: WIP
+    variant: caution
+---
+
+This setup guide will guide you through the process of setting up your development environment.
+
+Placeholder

docs/src/content/docs/start-here/setup.mdx

@@ -2,10 +2,7 @@
 title: Style guide
 description: Style guide for all firmware and ground station code
 sidebar:
-  badge:
-    text: New
-    variant: success
-  order: 2
+  order: 3
 ---
 
 This style guide outlines our team standards for writing firmware and ground station code.