link to nextrunner kdoc

Signed-off-by: Zach Harel <zach.harel42@gmail.com>

Author: zachwaffle4

src/nextrunner/changes-from-rr.md

@@ -10,18 +10,28 @@ such as `com.acmerobotics.roadrunner.paths`.
 This is similar to, but not the same as, the RoadRunner 0.5 package layout.
 
 Unfortunately, due to this change, NextRunner is not backwards compatible
-with RoadRunner 1.0. 
+with RoadRunner 1.0 (though migration is very easy!).
 However, IntelliJ IDEA and Android Studio will automatically import classes,
 so you do not need to worry about the package locations.
 
 ## 2. Trajectory Creation
 
-The [`Drive` interface](https://javadoc.io/doc/dev.nextftc.nextrunner/ftc/latest/ftc/com.acmerobotics.roadrunner.ftc/-drive/index.html)
+The [`Drive` interface](http://rr.zharel.me/ftc/com.acmerobotics.roadrunner.ftc/-drive/index.html)
 has a `trajectoryBuilder` method, allowing you to create trajectories without `Action`s.
 The API of the [`TrajectoryBuilder` class](https://javadoc.io/doc/dev.nextftc.nextrunner/core/latest/core/com.acmerobotics.roadrunner.trajectories/-trajectory-builder/index.html)
 is very similar to that of `TrajectoryActionBuilder`, 
 but its `build` method returns a `List<Trajectory>` instead of an `Action`.
 Alternatively, the `buildToComposite` method returns a `CompositeTrajectory` object,
 which may be easier to use.
 
+We also offer methods to create and profile paths without a builder, 
+which is documented [here](traj-generation)
 
+## 3. Action Improvements
+
+NextRunner includes multiple improvements to RoadRunner's Action framework.
+Notably, it includes an `ActionRunner` object to manage asynchronous action queues,
+and requirements and interruption features for `Action`s themselves.
+
+The [Creating](actions/creating-actions) and [Using Actions](actions/using-actions)
+guides explain many of these features.

src/nextrunner/examples/action-builder.md

@@ -6,6 +6,8 @@ Both `TankDrive` and `MecanumDrive` have an `actionBuilder` method,
 with an optional `startPose: Pose2d` parameter.
 If `startPose` is not provided, it defaults to `localizer.pose`.
 
+[All of the `TrajectoryActionBuilder` functions are documented here.](http://rr.zharel.me/actions/com.acmerobotics.roadrunner.actions/-trajectory-action-builder/index.html)
+
 Here is an example of how to use `actionBuilder`:
 
 :::tabs key:code

src/nextrunner/examples/follower.md

@@ -16,6 +16,8 @@ which will eventually be discussed on a page of this guide.
 The following (haha) example uses `TimeFollower`, 
 but it can be switched out for `DisplacementFollower` with no other changes to the `OpMode`.
 
+[All of the `TrajectoryBuilder` functions are documented here](http://rr.zharel.me/core/com.acmerobotics.roadrunner.trajectories/-trajectory-builder/index.html).
+
 :::tabs key:code
 
 == Kotlin

src/nextrunner/index.md

@@ -69,8 +69,34 @@ Then, sync your project with Gradle files.
 > 
 > The compatibility module is currently compatible with NextFTC 0.6.1 and 0.6.2.
 
+## Updating From RoadRunner 1.0
+
+NextRunner's API is mostly compatible with RoadRunner code,
+though package locations were changed.
+Simply replace your RoadRunner imports with the following:
+
+```groovy
+    implementation 'dev.nextftc.nextrunner:core:<latest>>'
+    implementation 'dev.nextftc.nextrunner:actions:<latest>'
+    implementation 'dev.nextftc.nextrunner:ftc:<latest>'
+```
+
+And sync your project with Gradle files. 
+
+> [!WARNING]
+> You will need to remove all of the RoadRunner imports from your files
+> and replace them with NextRunner's.
+> Once you delete the import statements, IntelliJ and Android Studio
+> can automatically replace them.
+
 ## Tuning 
 
 If you are using the QuickStart, the tuning process is
 the exact same as the [RoadRunner 1.0 tuning process](https://rr.brott.dev/docs/v1-0/tuning/).
 Future changes to the tuning process will be listed here.
+
+## KDoc 
+
+[KDoc for NextRunner can be found here](http://rr.zharel.me/).
+We recommend checking the KDoc pages, 
+as they include many features not directly discussed here.

src/nextrunner/traj-generation.md

@@ -85,7 +85,7 @@ We recommend using the `trajectoryBuilder` API's
 
 ## Types of `PosePath`
 
-NextRunner also includes [three default functions](https://javadoc.io/static/dev.nextftc.nextrunner/core/2.4.0/core/com.acmerobotics.roadrunner.paths/-position-path/index.html#-1473791754%2FFunctions%2F-431355489)
+NextRunner also includes [three default functions](http://rr.zharel.me/core/com.acmerobotics.roadrunner.paths/-position-path/index.html#1182961430%2FFunctions%2F-431355489)
 in the `PositionPath` interface to add heading paths,
 which creates `PosePath` objects!