remove obsolete boards from Wiki nav (#439)

* removed obsolete boards

* fix existing errors

* fix existing errors

* rename file with special chars [] in file name to prevent issues

* Delete [Process]-Software-Development-Life-Cycle-SDLC.md

* fix existing error

* fix existing errors

Build-Server-and-Automation.md

@@ -16,10 +16,8 @@ Github Actions is currently in charge of:
 * Generating Hardware PCB visual diffs
 * Updating date stamps for builds
 * Synchronizing between rusefi/rusefi/wiki to rusefi_documentation repo
+  * TL,DR see https://github.com/rusefi/rusefi/tree/master/.github/workflows
 
-TL,DR see https://github.com/rusefi/rusefi/tree/master/.github/workflows
+See also [Software-Development-Life-Cycle](Process-Software-Development-Life-Cycle-SDLC)
 
-See also [Software-Development-Life-Cycle](%5BProcess%5D-Software-Development-Life-Cycle-SDLC) 
-
-
-[Build-Server-and-Automation-Legacy-Jenkins-notes](Build-Server-and-Automation-Legacy-Jenkins-notes)
+[Build-Server-and-Automation-Legacy-Jenkins-notes](Build-Server-and-Automation-Legacy-Jenkins-notes)

HOWTO-quick-start.md

@@ -44,7 +44,7 @@ This guide is written for the firmware released August 6th 2020. The further awa
 
    **Your laptop should give you an audible notification when you plug in the ECU with the ignition turned on. That means that it "sees" a new device connected to a USB port.**
 
-5. In TunerStudio apply correct "Communication Settings" [for detailed instructions see here.](Tunerstudio-Connectivity.md)
+5. In TunerStudio apply correct "Communication Settings" [for detailed instructions see here.](Tunerstudio-Connectivity)
    **Note: If your computer is running Linux, you might have to [fix issues with ModemManager](Linux-Connectivity).**
 
 6. With this your TunerStudio screen should come to life! You should see sensor inputs and some output values like ignition timing and dwell. Of course the values displayed might not make a lot of sense, since your ECU is lacking a car, but at least you can see that TunerStudio and your computer are communicating.

Process-Software-Development-Life-Cycle-SDLC.md

@@ -0,0 +1,5 @@
+# Process - Software Development Life Cycle (SDLC)
+
+[Dev-Quality-Control](Dev-Quality-Control)
+
+[Build-Server-and-Automation](Build-Server-and-Automation)

[Process]-Software-Development-Life-Cycle-SDLC.md

@@ -1,5 +0,0 @@
-
-
-[Dev-Quality-Control](Dev-Quality-Control)
-
-[Build-Server-and-Automation](Build-Server-and-Automation)

mkdocs/mkdocs.yaml

@@ -65,11 +65,9 @@ nav:
     - 'rusEFI Hardware Overview': Hardware.md
     - 'Wiring & Connectivity Overview': FAQ-Basic-Wiring-and-Connections.md
     - 'Boards':
-      - 'Hellen': Hellen-One-Platform.md
       - 'Proteus': Proteus.md
       - 'MicroRusEFI (MRE)': Hardware-microRusEFI.md
-      - 'Frankenso': Hardware-Frankenso.md
-      - 'Frankenstein': Hardware-Frankenstein.md
+      - 'Hellen': Hellen-One-Platform.md
     - 'Plug & Play Hardware':
       - 'Hellen Miata 90-95': Hellen64-Miata-NA6-94.md
       - 'Hellen Miata 01-05 VVT': Hellen-NB2.md