Update guides for Deno to Node.js migration, small changes

Author: camspec

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

@@ -23,30 +23,32 @@ The `cmake --build .` takes some time to run since it is using a single thread t
 :::
 
 ## Setting up frontend development
-To run the frontend, Deno must be installed. If it isn't, see [Initial setup](/OBC-firmware/start-here/initial-setup/) and follow it to set up the database as well.
-
-Run all commands from the root directory.
-
-:::note
-If you have issues running any Deno commands, try restarting your shell after installing Deno.
-:::
-
-
-### Installing the frontend
-```shell
-cd gs/frontend
-deno install --frozen
-```
+To run the frontend, Node.js must be installed. If it isn't, see [Initial setup](/OBC-firmware/start-here/initial-setup/) and follow it to set up the database as well.
 
 ### Running the ARO frontend
-This will start the frontend at `localhost:5173`.
+While in the root directory, run the following commands to start the ARO frontend:
 ```shell
 cd gs/frontend/aro
-deno task dev
+npm install
+npm run dev
 ```
+If you have Docker installed, you can instead run the following command:
+```shell
+docker compose up aro-frontend
+```
+
+After you install new dependencies, you will need to rebuild the container with `docker-compose up --build aro-frontend`.
+
 ### Running the MCC frontend
-This will start the frontend at `localhost:5173`.
+While in the root directory, run the following commands to start the MCC frontend:
 ```shell
 cd gs/frontend/mcc
-deno task dev
+npm install
+npm run dev
 ```
+If you have Docker installed, you can instead run the following command:
+```shell
+docker compose up mcc-frontend
+```
+
+After you install new dependencies, you will need to rebuild the container with `docker-compose up --build mcc-frontend`.

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

@@ -25,6 +25,6 @@ The following is a simple guide on building the app for the OBC.
 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
+    Make sure to specify the `-DBOARD_TYPE=` option to avoid any unwanted behaviour.
     :::
 </Steps>

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

@@ -38,7 +38,7 @@ Make sure you follow the [Initial setup](/OBC-firmware/start-here/initial-setup)
     ```shell
     # Connect to PostgreSQL CLI as the postgres superuser
     sudo -u postgres psql
-    # Replace 'your_username' and 'your_password' with your desired values
+    # Replace your_username and your_password with your desired values
     CREATE USER your_username WITH PASSWORD 'your_password' SUPERUSER;
     CREATE DATABASE gs;
     ```
@@ -47,7 +47,7 @@ Make sure you follow the [Initial setup](/OBC-firmware/start-here/initial-setup)
 
     ```shell
     \q # Log out
-    # Replace 'your_username' with your actual username
+    # Replace your_username with your actual username
     psql -U your_username -d gs
     # You should be logged into the database
     \q # Log out again

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

@@ -26,8 +26,15 @@ For command-line work, it's recommended to use **Windows Terminal** (in Windows,
 
 You can also work with WSL in VS Code. To open VS Code in WSL, install the WSL extension, then either run `code .` from a WSL directory or use the Remote Explorer in VS Code.
 :::
+
+:::caution
+Clone the repository and do all work in the Linux home directory (e.g. `~/projects/OBC-firmware`). Don't store your code on Windows and access it via the `mnt` directory. This will help with performance and compatibility.
+:::
+
 ## Linux/WSL
 
+### Standard setup
+
 <Steps>
 1. Ensure you have Git installed. If you are using Ubuntu 24.04 LTS or later, or installed the default WSL distribution, you should already have it installed.
 If not, open a terminal and run the following commands to install Git:
@@ -75,17 +82,32 @@ If not, open a terminal and run the following commands to install Git:
     pip install -r requirements.txt
     pip install -e .
 
-7. Setup the pre-commit by running the following commands in the repository's root directory. You may need to install `unzip` in order to install Deno. If you do not have `unzip`, run `sudo apt install unzip`.
+7. Setup the pre-commit by running the following command in the repository's root directory:
 
     ```shell
-    # The first command installs Deno, which is required for our pre-commit
-    curl -fsSL https://deno.land/install.sh | sh
     pre-commit install
     ```
 
-8. 
-    :::note[Ground station only]
-    Set up the PostgreSQL database with the [Database setup](/OBC-firmware/start-here/database-setup) guide.
-    :::
+</Steps>
+
+### Ground station (optional)
+If you'll also be working on the ground station, complete these extra steps:
+<Steps>
+1. Install `nvm`:
+
+    ```shell
+    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
+    ```
+
+2. Restart your shell or run `source ~/.bashrc` (only works on Bash).
+
+3. Install Node.js v22:
+    ```shell
+    nvm install 22
+    # Verify the Node.js version
+    node -v
+    ```
+
+4. Set up the PostgreSQL database with the [Database setup](/OBC-firmware/start-here/database-setup) guide.
 </Steps>
 

docs/src/content/docs/start-here/style-guide.mdx

@@ -280,6 +280,7 @@ Variable and function names should be descriptive enough to understand even with
 #### Function comments
 
 Function comments should follow the format shown below:
+
 ```typescript
 /**
  * @brief Adds two numbers together
@@ -301,6 +302,6 @@ File comments are not required.
 
 -   `variableNames` in camelCase
 -   `functionNames()` in camelCase
--   `CONSTANT_NAME` in CAPITAL_SNAKE_CASE
--   `file_names` in snake_case
+-   `CONSTANT_NAME` in SCREAMING_SNAKE_CASE
+-   `file-names` in kebab-case
 -   `ClassName` and `ComponentName` in PascalCase