Match robotgoat: update docusaurus.config.ts, drop stale anchors via heading validation

Author: sensei-hacker

docusaurus.config.ts

@@ -25,9 +25,6 @@ const config: Config = {
   organizationName: "iNavFlight", // Usually your GitHub org/user name.
   projectName: "iNavFlight.github.io", // Usually your repo name.
 
-  // "warn" rather than "throw": versioned docs naturally accumulate broken links
-  // as pages are renamed/reorganized across INAV releases. Broken links are
-  // logged during build so they can be addressed incrementally.
   onBrokenLinks: "warn",
   // onBrokenMarkdownLinks: "warn", #deprecated comment out for now
 
@@ -72,23 +69,21 @@ const config: Config = {
             "https://github.com/iNavFlight/iNavFlight.github.io/tree/master/",
         },
         blog: false,
-        /*
-        blog: {
-          showReadingTime: true,
-          feedOptions: {
-            type: ["rss", "atom"],
-            xslt: true,
-          },
-          // Please change this to your repo.
-          // Remove this to remove the "edit this page" links.
-          editUrl:
-            "https://github.com/iNavFlight/iNavFlight.github.io/tree/master/",
-          // Useful options to enforce blogging best practices
-          onInlineTags: "warn",
-          onInlineAuthors: "warn",
-          onUntruncatedBlogPosts: "warn",
-        },
-        */
+        // blog: {
+        //   showReadingTime: true,
+        //   feedOptions: {
+        //     type: ["rss", "atom"],
+        //     xslt: true,
+        //   },
+        //   // Please change this to your repo.
+        //   // Remove this to remove the "edit this page" links.
+        //   editUrl:
+        //     "https://github.com/iNavFlight/iNavFlight.github.io/tree/master/",
+        //   // Useful options to enforce blogging best practices
+        //   onInlineTags: "warn",
+        //   onInlineAuthors: "warn",
+        //   onUntruncatedBlogPosts: "warn",
+        // },
         theme: {
           customCss: "./src/css/custom.css",
         },
@@ -136,6 +131,7 @@ const config: Config = {
           label: "Download",
           position: "left",
         },
+        // { to: "/blog", label: "Blog", position: "left" },
         {
           to: "/about",
           label: "About",
@@ -196,6 +192,10 @@ const config: Config = {
         {
           title: "More",
           items: [
+            // {
+            //   label: "Blog",
+            //   to: "/blog",
+            // },
             {
               label: "GitHub",
               href: "https://github.com/iNavFlight/inav",

versioned_docs/version-7.1.2/Release-Notes.md

@@ -111,7 +111,7 @@ If a user does decide to omit the use of a compass for a multirotor, be mindful
 
 Example [Video](https://www.youtube.com/watch?v=iopZfH-DdTI)
 
-For more details see [here](./quickstart/GPS-and-Compass-setup.md#inav-71-changes)
+For more details see [here](./quickstart/GPS-and-Compass-setup.md)
 
 ## Tailsitter Support for VTOL
 Tailsitter builds are now natively supported to allow proper Board Orientation switching during transition. [Details](https://github.com/iNavFlight/inav/pull/9347)

versioned_docs/version-7.1.2/advanced/INAV-for-BetaFlight-users.md

@@ -23,7 +23,7 @@ Let's then review the differences:
 * The accelerometer and gyroscope calibration is mandatory on INAV, and it’s a 6-step process (different from BetaFlight, which is an optional single-step process). Follow the on-screen instructions and you’ll be fine.
 * For a fully autonomous multirotor (with automatic navigation capabilities like RTH, Poshold and WP Missions). The Flight Controller board should have an onboard barometer sensor. INAV's multicopter navigation altitude precision will suffer without one.
 * Also, you have to cover the barometer sensor with a small piece of open-cell foam, because the wind affects the sensor readings. This is the most common cause of altitude holding problems.
-* Prior to 7.1 release. The GNSS module should be fitted with a magnetometer sensor for best navigation precision. GNSS modules without a mag sensor will work from 7.1 on-wards for copter navigation. [See requirements](../quickstart/GPS-and-Compass-setup.md#inav-71-changes)
+* Prior to 7.1 release. The GNSS module should be fitted with a magnetometer sensor for best navigation precision. GNSS modules without a mag sensor will work from 7.1 on-wards for copter navigation. [See requirements](../quickstart/GPS-and-Compass-setup.md)
 
 * The GPS module should be mounted on a small mast pole to avoid magnetic interference from motors on the compass; 5 or 6 centimeters above motors should be fine.
 

versioned_docs/version-7.1.2/features/Navigation-Mode:-Return-to-Home.md

@@ -154,4 +154,4 @@ It is possible to override the default RTH Altitude and Climb First settings dur
 Allows an emergency landing to be triggered manually as required.
 Landing is started or ended by toggling the POSHOLD mode switch at least 5 times at a minimum rate of 1Hz.
 Provided sensor position data is available. The aircraft will commence descent, holding the target position above which it was activated.
-Failsafe is inhibited during manual emergency landing, to allow the landing to continue if the RX signal is lost. Under this condition, aborting  manual emergency landing must be done before a FS occurs. Manual emergency landing can also be triggered by use of the [multi-function utility](./Modes.md#multi-function)
+Failsafe is inhibited during manual emergency landing, to allow the landing to continue if the RX signal is lost. Under this condition, aborting  manual emergency landing must be done before a FS occurs. Manual emergency landing can also be triggered by use of the [multi-function utility](./Modes.md)

versioned_docs/version-7.1.2/features/Navigation-modes.md

@@ -271,7 +271,7 @@ Loss of GPS during navigation will have the following affect on the different mo
 ## Emergency Landing
 An emergency landing will be triggered during WP and RTH modes if navigation sensors fail or in the case of RTH if the craft heads off in the wrong direction.
 
-It is also possible to manually trigger an emergency landing at any time using [MULTIFUNCTION](./Modes.md#multi-function) mode or by using [POSHOLD](#nav-poshold---position-hold) mode. To trigger using POSHOLD mode rapidly toggle the mode ON/OFF at least 5 times. Repeat this action to cancel the emergency landing once started.
+It is also possible to manually trigger an emergency landing at any time using [MULTIFUNCTION](./Modes.md) mode or by using [POSHOLD](#nav-poshold---position-hold) mode. To trigger using POSHOLD mode rapidly toggle the mode ON/OFF at least 5 times. Repeat this action to cancel the emergency landing once started.
 
 ## Mode switch diagram
 

versioned_docs/version-7.1.2/quickstart/Fixed-Wing-Guide.md

@@ -141,7 +141,7 @@ At this point everything should work as expected.
 
 * Use Airmode mode to get full stabilization and servo throw with no throttle applied.
 
-* [Setting up failsafe with return to home.](../features/Failsafe.md#setting-up-failsafe-for-rth)
+* [Setting up failsafe with return to home.](../features/Failsafe.md)
 
 * If your compass is not 100% properly setup just disable it instead. **A calibrated compass can cause orientation drift during flight that may not show up in the configurator** (especially built-in ones on your FC). Really consider disabling it unless you need it. INAV uses GPS heading normally, Only on ground before GPS speed has been high enough or if error between GPS heading and compass heading exceed 60deg will it use compass heading
 

versioned_docs/version-7.1.2/quickstart/Multirotor-guide.md

@@ -11,7 +11,7 @@ title: Multirotor Guide
 * Download latest configurator from [here](https://github.com/iNavFlight/inav-configurator/releases)
 * Flash newest INAV with full chip erase option selected
 * Do the advanced 6-point [sensor calibration](./Calibration-Tab.md)
-* Select your Mixer. Most common ones are already available as presets. For exotic setups, see [Custom mixes for exotic setups](../advanced/Custom-mixes-for-exotic-setups.md#setups-that-can-be-implemented-with-custom-mixer); if you don't do this, you will not see any motors in the motors tab.
+* Select your Mixer. Most common ones are already available as presets. For exotic setups, see [Custom mixes for exotic setups](../advanced/Custom-mixes-for-exotic-setups.md); if you don't do this, you will not see any motors in the motors tab.
 * Be sure the model moves on the configurator as it is moving on the bench. If not, adjust board alignment from the Configuration tab
 * If you have a magnetometer, you may need to attach a battery for magnetometer calibration. Rotate the quadcopter 360 degrees on all 3 axes.
 
@@ -37,7 +37,7 @@ You can use RX stick combination to trim the quadcopter: [Controls](https://gith
 Having a good compass reading is **crucial** for navigation function to work correctly.
 
 ## 6. Setup and verify failsafe on TX and INAV
-[Guide for setting up failsafe](../features/Failsafe.md#setting-up-failsafe-for-rth)
+[Guide for setting up failsafe](../features/Failsafe.md)
 
 ## 7. Determine and set hover throttle
 To let the altitude hold controller work correctly, you need to input your hover throttle (the throttle you need to apply to make the multirotor hover) into the **nav_mc_hover_thr** CLI variable or just set it via the configurator configuration tab.