refactor: touch up on the guide

Signed-off-by: BeepBot99 <74377508+BeepBot99@users.noreply.github.com>

Author: BeepBot99

.idea/vcs.xml

@@ -22,7 +22,9 @@ export default [
         items: [
             {text: "Autonomous", link: "/guide/opmodes/autonomous"},
             {text: "TeleOp", link: "/guide/opmodes/teleop"},
-            {text: "PedroPathing", link: "/guide/opmodes/pedropathing"}
+            {text: "Pedro Pathing", link: "/guide/opmodes/pedropathing"},
+            {text: "RoadRunner", link: "/guide/opmodes/roadrunner"},
+            {text: "Hermes", link: "/guide/opmodes/hermes"},
         ]
     },
     {

.idea/workspace.xml

@@ -2,8 +2,6 @@
     --vp-home-hero-name-color: #005bab;
     --vp-custom-block-tip-bg: #86bd86;
     --vp-custom-block-tip-text: #212a24;
-}
-
-.actions .action:first-child {
-    flex-basis: 100%;
+    --vp-c-tip-1: #2c4133;
+    --vp-custom-block-tip-code-bg: #7b9a7b;
 }

.vitepress/sidebar/guide.mts

@@ -57,12 +57,4 @@ each of our libraries is also on this site.
   falling edges, toggles, and state changes.
 - **Ranges** represent a numeric variable and can be used to create buttons on
   certain events, for example when it
-  is greater than a certain number. Ranges can also be mapped.
-
-[**NextPedro is our integration with PedroPathing**](/pedro)
-
-- [**PedroPathing**](https://pedropathing.com) is an advanced reactive vector
-  follower for FTC.
-- **Follow paths** and `PathChains` with the `FollowPath` command.
-- **Turn your robot** with the `Turn` and `TurnTo` commands.
-- **Position-based timing** with `ProximityDelay` and `DisplacementDelay`.
+  is greater than a certain number. Ranges can also be mapped.

.vitepress/theme/custom.css

@@ -6,7 +6,6 @@ libraries for more specific documentation on every aspect of NextFTC there is:
 - [NextFTC](/nextftc)
 - [NextControl](/control)
 - [NextBindings](/bindings)
-- [NextPedro](/pedro)
 
 Anything that is not on the docs can be found in our
 [Dokka documentation](https://javadoc.io/doc/dev.nextftc).

src/guide/about.md

@@ -4,62 +4,30 @@ next: Subsystems
 
 # Installation
 
-The first step to using NextFTC is installing it. There are two ways to install
-it.
+The first step to using NextFTC is installing it.
 
-## Method 1: Quickstart Repo (new project)
-
-The easiest way to install NextFTC is by using the quickstart. In addition to
-having NextFTC preinstalled, it also has
-all the example code created in the guides on these docs. To install the
-quickstart, do one of the following:
-
-1. In Android Studio, go to
-   `Main Menu -> File -> New -> Project from Version Control`. For URL, enter
-   `https://github.com/NextFTC/Quickstart.git`.
-2. **OR** in the directory you want to install it in, run
-   `git clone https://github.com/NextFTC/Quickstart.git`.
-   Make
-   sure you have [git](https://git-scm.com/) installed first.
-
-> [!NOTE]
-> If you are using PedroPathing, use the `nextftc-and-pedro` branch instead.
-
-## Method 2: Manually using Gradle (existing project)
-
-Installing NextFTC using Gradle is fairly simple.
-
-In the `build.dependencies.gradle` file, go to the `dependencies` block.
+In the TeamCode `build.gradle` file, go to the `dependencies` 
+block.
 Add the following lines to the bottom:
 
 ::: tabs key:gradle
 
 == .gradle
 
 ```groovy
-implementation 'dev.nextftc:core:1.0.0'
 implementation 'dev.nextftc:ftc:1.0.0'
 implementation 'dev.nextftc:hardware:1.0.0'
-implementation 'dev.nextftc:control:1.0.0'
-implementation 'dev.nextftc:bindings:1.0.0'
-implementation 'dev.nextftc:pedro:1.0.0' // If you would like to use NextPedro
 ```
 
 == .gradle.kts
 
 ```kotlin
-implementation("dev.nextftc:core:1.0.0")
 implementation("dev.nextftc:ftc:1.0.0")
 implementation("dev.nextftc:hardware:1.0.0")
-implementation("dev.nextftc:control:1.0.0")
-implementation("dev.nextftc:bindings:1.0.0")
-implementation("dev.nextftc:pedro:1.0.0") // If you would like to use NextPedro
 ```
 
 :::
 
-### Step 3: Sync Gradle
-
 Press the `Sync Now` button that appeared as a banner at the top of your Gradle
 file.
 

src/guide/further-reading.md

@@ -1,9 +1,9 @@
 # Autonomous
 
-Creating an autonomous in NextFTC is fairly straightforward. This page will walk
-you through creating an autonomous. Usage of PedroPathing will not be covered in
-this page; refer to the [PedroPathing page](/guide/opmodes/pedropathing)for
-details on that.
+This page will walk you through creating an autonomous program using NextFTC.
+Usage of RoadRunner, Pedro Pathing, or Hermes will not be covered in this guide;
+see
+the guides for those libraries on the following pages.
 
 This autonomous program will introduce you to some core features of NextFTC such
 as command groups, delays, and running the commands you created in your
@@ -13,7 +13,7 @@ Let's get started!
 
 ## Step 1: Create your OpMode
 
-OpModes in NextFTC will extend the `NextFTCOpMode` superclass. Here is the basic
+OpModes in NextFTC extend the `NextFTCOpMode` superclass. Here is the basic
 structure for every autonomous OpMode:
 
 :::tabs key:code
@@ -60,7 +60,7 @@ init {
 ```java
 @Autonomous(name = "NextFTC Autonomous Program Java")
 public class AutonomousProgram extends NextFTCOpMode {
-    {
+    public AutonomousProgram() {
         addComponents(
             new SubsystemComponent(Lift.INSTANCE, Claw.INSTANCE)
         );
@@ -76,17 +76,14 @@ and will initialize them accordingly.
 ### A Quick Note on Components
 
 Components are NextFTC's approach to making OpModes more modular and
-customizable. Each component has 10 functions that
-get run before and after each OpMode function (`onInit`, `onWaitForStart`,
-`onStartButtonPressed`, `onUpdate`, and
-`onStop`). This means that components are extremely versatile and can be used to
-accomplish a wide range of
-functions when they're used in your OpModes.
+customizable. Each component has 10 functions that get run before and after each
+OpMode function (`onInit`, `onWaitForStart`,`onStartButtonPressed`, `onUpdate`,
+and`onStop`). This means that components are extremely versatile and can be used
+to achieve a wide range of functions when they're used in your OpModes.
 
 We already have used a component: `SubsystemComponent`! Let's add one more
-component to our OpMode:
-`BulkReadComponent`. This component automatically adds bulk reading to our
-OpMode.
+component to our OpMode:`BulkReadComponent`. This component automatically adds
+bulk reading to our OpMode.
 
 :::tabs key:code
 
@@ -96,7 +93,7 @@ OpMode.
 init {
     addComponents(
         SubsystemComponent(Lift, Claw),
-        BulkReadComponent()
+        BulkReadComponent
     )
 }
 ```
@@ -106,12 +103,10 @@ init {
 ```java
 @Autonomous(name = "NextFTC Autonomous Program Java")
 public class AutonomousProgram extends NextFTCOpMode {
-   
-    // if you've never seen this before, it's called an instance initialization block, or IIB.
-    {
+    public AutonomousProgram() {
         addComponents(
             new SubsystemComponent(Lift.INSTANCE, Claw.INSTANCE),
-            new BulkReadComponent()
+            BulkReadComponent.INSTANCE
         );
     }
 }
@@ -122,18 +117,18 @@ public class AutonomousProgram extends NextFTCOpMode {
 ## Step 2: Creating a routine
 
 You've already learned how to create individual commands, such as motor and
-servo movements. Now, it's time to group
-them together into useful behaviors. This is where `CommandGroups` and routines
-come into play. Before we can create our
-own, we first need to understand how commands are run behind the scenes.
+servo movements. Now, it's time to group them together into useful behaviors.
+This is where command groups come into play. Before we can create our own, we
+first need to understand how commands are run behind the scenes.
 
 The `CommandManager` stores an internal list of actively running commands. It
 goes through each command and calls its
 `update()` function every single loop. It also determines which commands to
 cancel, handles subsystem conflicts, and
 offers additional functionality as well. The important thing to note is that all
 commands that are directly stored by
-the CommandManager run _simultaneously_. Knowing that, you may be wondering why
+the `CommandManager` run _simultaneously_. Knowing that, you may be wondering
+why
 `ParallelGroups` exist, if you can just
 schedule commands directly. Trust me, we'll get there. Before that, we need to
 understand what a `SequentialGroup` does.
@@ -144,7 +139,7 @@ at once, it schedules the first one, and then waits to schedule the next one
 until the first has completed, then
 continues scheduling them one by one until they've all completed. If you think
 about it a little bit, it may become
-apparent what a `ParallelGroup` is for. If you are using a `SequentialGroup`,
+clear what a `ParallelGroup` is for. If you are using a `SequentialGroup`,
 you may have things you want to happen
 simultaneously _within_ that group. For example:
 
@@ -154,10 +149,10 @@ simultaneously _within_ that group. For example:
 4. _Simultaneously_ lower the lift, reset the arm, and drive to a different
    location
 
-This could only be accomplished using `ParallelGroups` in conjunction with
+This could only be done using `ParallelGroups` in conjunction with
 `SequentialGroups`.
 
-Now that we know what `CommandGroups` do, let's learn how to create them. For
+Now that we know what command groups do, let's learn how to create them. For
 this example, we will create a routine that
 does the following:
 
@@ -191,21 +186,9 @@ public Command autonomousRoutine() {
 
 :::
 
-I've made an empty SequentialGroup here, for demonstration purposes.
-
-> [!CAUTION]
-> Do not attempt to use empty `SequentialGroups` in your code. They will cause
-> errors that break your OpMode. If you
-> need a placeholder, use a [
-`NullCommand`](https://nextftc.dev/reference/core/com.rowanmcalpin.nextftc.core.command.utility/-null-command/).
->
-> The above snippet is incomplete and that's why it appears to create an empty
-`SequentialGroup`. That won't work in
-> practice.
-
-As mentioned above, we need to put something in our sequential group in order to
-avoid errors. In our list, we said the
-first thing we want to do is raise the lift to the high position. We can add the
+However, an empty `SequentialGroup` won't do much. Let's add some stuff to it.
+In our list, we said the first thing we want to do is raise the lift to the high
+position. We can add the
 `Lift.toHigh` command into our group
 very easily:
 
@@ -265,9 +248,8 @@ public Command autonomousRoutine() {
 
 :::
 
-Just like with `SequentialGroups`, you shouldn't create empty `ParallelGroups`.
-Let's populate it with our
-`Lift.toMiddle` and `Claw.close` commands:
+Let's populate the `ParallelGroup` with our `Lift.toMiddle` and `Claw.close`
+commands:
 
 :::tabs key:code
 
@@ -328,7 +310,7 @@ val autonomousRoutine: Command
             Lift.toMiddle,
             Claw.close
         ),
-        Delay(0.5.sec)
+        Delay(0.5.seconds)
     )
 ```
 
@@ -364,7 +346,7 @@ private val autonomousRoutine: Command
             Lift.toMiddle,
             Claw.close
         ),
-        Delay(0.5.sec),
+        Delay(0.5.seconds),
         ParallelGroup(
             Claw.open,
             Lift.toLow
@@ -445,7 +427,7 @@ class AutonomousProgram : NextFTCOpMode() {
     init {
         addComponents(
             SubsystemComponent(Lift, Claw),
-            BulkReadComponent()
+            BulkReadComponent
         )
     }
 
@@ -456,7 +438,7 @@ class AutonomousProgram : NextFTCOpMode() {
                 Lift.toMiddle,
                 Claw.close
             ),
-            Delay(0.5.sec),
+            Delay(0.5.seconds),
             ParallelGroup(
                 Claw.open,
                 Lift.toLow
@@ -474,10 +456,10 @@ class AutonomousProgram : NextFTCOpMode() {
 ```java
 @Autonomous(name = "NextFTC Autonomous Program Java")
 public class AutonomousProgram extends NextFTCOpMode {
-    {
+    public AutonomousProgram() {
         addComponents(
             new SubsystemComponent(Lift.INSTANCE, Claw.INSTANCE),
-            new BulkReadComponent()
+            BulkReadComponent.INSTANCE
         );
     }
 

src/guide/installation.md

@@ -0,0 +1,5 @@
+# Hermes
+
+This is a guide for NextFTC's integration with [Hermes](https://hermes.zharel.gay).
+
+🚧 This page is under construction. 🚧