Fix broken link + Fix markdownlint

Author: ZakaHaceCosas

.markdownlint.yaml

@@ -0,0 +1,7 @@
+MD007:
+  indent: 4
+  start_indented: false
+MD010: false
+MD013: false
+MD025: false
+MD046: false

.vscode/settings.json

@@ -1,8 +1,10 @@
 {
     "cSpell.words": [
         "arithmatex",
+        "chdir",
         "ckers",
         "cking",
+        "codeberg",
         "crossplatform",
         "crossruntime",
         "fkadd",
@@ -21,24 +23,31 @@
         "fkstats",
         "fksurrender",
         "fontawesome",
+        "framagit",
         "fuckingnode",
         "gigachad",
+        "gitee",
         "gluefix",
         "googlecloudstorage",
         "HKCU",
         "kickstarting",
         "konbini",
         "linenums",
         "lockfiles",
+        "mkdocs",
         "nevermind",
+        "openprivacy",
         "personaplus",
         "pkgs",
         "preapp",
         "pymdownx",
         "SETTINGCHANGE",
         "sokora",
+        "squidfunk",
         "therf",
+        "twemoji",
         "vuelto",
+        "webp",
         "zaka",
         "zakahacecosas"
     ]

docs/about/branding.md

@@ -1,5 +1,3 @@
-<!-- markdownlint-disable md033 -->
-
 # FuckingNode branding guidelines
 
 Just in case you wanted to write an article or make a video about us (thank you!). We're not Nintendo, of course we won't sue you if you don't strictly follow these rules. We do appreciate you respecting them, though.

docs/about/roadmap.md

@@ -1,5 +1,3 @@
-<!-- markdownlint-disable md007 -->
-
 # Roadmap & release history
 
 What we're planning to do. Only includes minor and major releases, patch releases only fix errors, meaning they aren't planned, as our plan and hope is to write errorless code (which we'll never do, but we'll try our best to get as close as possible to that).
@@ -11,10 +9,10 @@ This page also lists all minor and major releases since 2.X. Patches aren't list
 ## 5.X (Upcoming)
 
 - [ ] Improve `setup`.
-  - [ ] Add many more setups (LICENSEs, gitignores, etc...).
-  - [ ] Make setups searchable.
+    - [ ] Add many more setups (LICENSEs, gitignores, etc...).
+    - [ ] Make setups searchable.
 - [x] Improve `commit`
-  - [x] ~~Commit prevention if compromised files (e.g. `.env` or `node_modules`) are staged.~~
+    - [x] Commit prevention if compromised files (e.g. `.env` or `node_modules`) are staged.
 - [ ] Setting to actually halt cleanup execution and notify if an error happens.
 - [ ] Dual release system.
 - [ ] Add `fuckingnode uncommit` - undoes commit and holds, letting the user modify stuff, then re-adds files from the prev commit, runs `commitCmd` if any, and commits with same message.
@@ -50,11 +48,11 @@ No important milestones for this release.
 ### Version 4.2 (Released)
 
 - [x] Add more system notification prompts.
-  - [x] Whenever a cleaning task (e.g. lint) fails.
-  - [x] When a build finishes.
+    - [x] Whenever a cleaning task (e.g. lint) fails.
+    - [x] When a build finishes.
 - [x] Bring back showing more details into the final report.
-  - [x] Show what features divineProtection prevented (if any).
-  - [x] (New idea) what features failed (if any).
+    - [x] Show what features divineProtection prevented (if any).
+    - [x] (New idea) what features failed (if any).
 
 ### Version 4.1 (Released)
 

docs/about/social.md

@@ -1,5 +1,4 @@
-<!-- markdownlint-disable md033 md030 -->
-# F\*ckingNode community
+# FuckingNode community
 
 <div class="grid cards" markdown>
 

docs/index.md

@@ -3,9 +3,6 @@ hide:
   - navigation
 ---
 
-<!-- markdownlint-disable md033 -->
-<!-- markdownlint-disable md030 -->
-
 # The f*cking chaos of maintaining JavaScript projects ends here
 
 **Because dev life is messy enough.**

docs/learn/clean.md

@@ -135,4 +135,4 @@ Where `PARTIAL` indicates partial / incomplete support, and `YES` and `NO` indic
 | v2.0.0     | YES        | YES         | YES         | PARTIAL | PARTIAL | NO      | NO      |
 | v1.0.0     | YES        | YES         | YES         | NO      | NO      | NO      | NO      |
 
-To learn more about cross-runtime compatibility, [refer to this page](./cross-runtime.md).
+To learn more about cross-runtime compatibility, [refer to this page](./cross-runtime-support.md).

docs/manual/kickstart.md

@@ -1,3 +1,9 @@
+---
+title: "Kickstart"
+description: "Get your projects cloned, launched, and prepared for use"
+icon: material/rocket-launch
+---
+
 # Using FuckingNode: Kickstart a project
 
 > `fuckingnode kickstart <repo-url> [file-path] [package manager]`, or `fkstart <repo-url> [file-path] [package manager]`

docs/manual/usage.md

@@ -4,8 +4,6 @@ description: "How to cleanup your projects - and fall in love with FuckingNode."
 icon: material/broom
 ---
 
-<!-- markdownlint-disable md010 md046 md033 -->
-
 # Using FuckingNode: the most important command
 
 > `fuckingnode clean [...many optional arguments]`, or `fkclean [...many optional arguments]`
@@ -139,11 +137,13 @@ Some of these features depend on `fknode.yaml` configuration, [as noted above](#
 
 ### Callouts
 
+<!-- todo -->
+
 !!! info "About errors"
 
     Any error from additional tasks will fail silently; this means they won't stop the execution flow and no logs will be made. Error logs are dumped into a log file; you're shown the path whenever an error of this kind happens.
 
-### Linting your code: `--lint`
+### Linting your code
 
 When linting, we will automatically run your linter. By default, we use ESLint - which in most cases should just work out of the box. Still, for convenience, you're able to choose a different linter.
 
@@ -163,7 +163,7 @@ scripts: {
 lintCmd: "linter"
 ```
 
-### Prettifying your code: `--pretty`
+### Prettifying your code
 
 When prettying, we will automatically run your prettifier. By default, we use Prettier - which just as ESLint should work, and just as ESLint can be changed anyway.
 
@@ -183,7 +183,7 @@ scripts: {
 prettyCmd: "prettifier"
 ```
 
-### Destroying your <s>code</s> files: `--destroy`
+### Destroying your files
 
 When destroying, we will automatically remove files and directories you specified.
 
@@ -212,7 +212,7 @@ destroy:
 
 You can use an asterisk (`*`) if you want to destroy with all intensities without typing all of that. _Due to how the CLI is designed, it must still be an array, so `["*"]` works and `"*"` doesn't._
 
-### Committing your code: `--commit`
+### Committing your code
 
 When committing, we will automatically commit our changes (updating, linting, prettifying) to Git, using a default commit message unless overridden.
 
@@ -233,7 +233,7 @@ For your own safety, we will commit ONLY IF ALL of the following conditions are
     commitActions: true # authorize commits
     ```
 
-### Updating your code: `--update`
+### Updating your code
 
 When updating, we will automatically update your dependencies using your project's package manager (we'll know that based on your lockfile). By default, the standard update command is used, though you can actually override this command too.