Update docs for v3.4.0

Author: ZakaHaceCosas

docs/index.md

@@ -21,7 +21,7 @@
 
     Works with any NodeJS, Deno, or BunJS project. Even Go and Rust are partially supported![^1]
 
-    [:octicons-arrow-right-24: Cross-platform support](learn/cross-runtime-support.md)
+    [:octicons-arrow-right-24: Cross-runtime support](learn/cross-runtime-support.md)
 
 -   :material-speedometer:{ .lg .middle } **Speed up your workflow**
 

docs/learn/audit.md

@@ -118,11 +118,12 @@ F\*ckingNode audit should not be allowed to have the final say over whether brea
 
 ## Availability
 
-Where `EXP` indicates experimental, `CAVEAT` indicates partial support / support with known flaws, and `YES` and `NO` indicate the obvious.
+Where `EXP` indicates only experimental support, and `YES` and `NO` indicate the obvious.
 
 | Support    | NodeJS npm | NodeJS pnpm | NodeJS yarn | Deno | Bun | Go | Cargo |
 | :--------- | ---------- | ----------- | ----------- | ---- | --- | -- | ----- |
-| **v3.0.0** | EXP        | EXP         | EXP         | NO   | NO  | NO | NO    |
+| v3.3.0     | YES        | YES         | YES         | NO   | NO  | NO | NO    |
+| v3.0.0     | EXP        | EXP         | EXP         | NO   | NO  | NO | NO    |
 | v2.1.0     | EXP        | NO          | NO          | NO   | NO  | NO | NO    |
 
 *[RF]: Risk Factor; a percentage computed by us to estimate the joint impact of all vulnerabilities of a NodeJS project.

docs/learn/cross-runtime-support.md

@@ -7,7 +7,7 @@
 
 While FuckingNode can be a very powerful automation tool if properly used, in the end it's just an executable that _automates_ tasks; it doesn't do much on its own. Thus, **features that aren't supported by a runtime itself, won't work with us**. (Adding "polyfills" or "glue fixes" is not discarded as an idea, but not planned short-term anyway).
 
-You can run `compat` anytime from the CLI to see a table showing what works and what doesn't. **NodeJS is the only environment with 100% platform support.** As of version 3.3.0, that table looks like this:
+You can run `compat` anytime from the CLI to see a table showing what works and what doesn't. **NodeJS is the only environment with 100% platform support.** As of version 3.3.1, that table looks like this:
 
 | Feature    | NodeJS | Deno     | Bun      | Go       | Cargo    |
 |------------|--------|----------|----------|----------|----------|
@@ -19,6 +19,7 @@ You can run `compat` anytime from the CLI to see a table showing what works and
 | Surrender  | Yes    | Yes      | Yes      | Yes      | Yes      |
 | Setup      | Yes    | Yes      | Yes      | Yes      | Yes      |
 | Audit      | Yes    | No       | No       | No       | No       |
+| Launch     | Yes    | Yes      | Yes      | Yes      | Yes      |
 
 Reasons for not supporting a feature are the following.
 
@@ -38,18 +39,14 @@ We might add them in the future, for now they're not supported because they're h
 
 `commitCmd` is not supported by these platforms. This is because Cargo and Go don't have "JS-like `run`" tasks.
 
-## Partial Deno, Cargo & Go support for stats
+## Partial Go support for stats
 
-These platforms _do_ support it but don't support the Recommended Community Standards part.
-
-**Deno & Cargo**: It's planned to be added.
-
-**Go**: `go.mod` doesn't have any field that can be compared to anything. No module name, no author, no license, etc...
+Golang _do_ support it but doesn't support the Recommended Community Standards part. `go.mod` doesn't have any field that can be compared to anything. No module name, no author, no license, etc...
 
 ## No Cargo & Go support for migrate
 
 There's a single package manager for these platforms, `migrate` is useless.
 
 ## No audit support anywhere non NodeJS
 
-Deno and Bun do not offer an `audit` command, neither does Go.
+Deno and Bun do not offer an `audit` command, neither do Go nor Cargo.

docs/manual/kickstart.md

@@ -1,15 +1,13 @@
 # Using FuckingNode: Kickstart a project
 
-> `fuckingnode kickstart <repo-url> [file-path] [package manager]`
+> `fuckingnode kickstart <repo-url> [file-path] [package manager]`, or `fkstart <repo-url> [file-path] [package manager]`
 
-The `kickstart` command is an extra command that increases even more your productivity. It does the following, from a single command:
+The `kickstart` command is an extra command that increases your productivity by doing all of the following from a single command:
 
 - Clones a Git repo wherever you want
 - Installs dependencies automatically using the project's default package manager (or at your choice, another one).
-- Launches your favorite code editor (defaults to VSCode, as seen on settings).
-- Adds the project to F\*ckingNode.
-
-Of course, it only works with NodeJS (or Deno or Bun) projects.
+- Launches your favorite code editor (as defined by your user settings).
+- Adds the project to the F\*ckingNode list.
 
 ## Usage
 
@@ -21,7 +19,45 @@ fuckingnode kickstart < REPO-URL > [PATH] [PKG MANAGER]
 
 `REPO-URL` is obvious and mandatory. `PATH` is optional and defines the path where you want us to clone the project. If not provided, we'll create a directory in the CWD with the name of the repository (just as Git would do by default).
 
-`PKG MANAGER` only works with NodeJS projects and lets you override the project's package manager, so a project that's using `npm` gets cloned with, for example, `pnpm` instead. In Bun or Deno this is ignored, and their default install commands are used.
+`PKG MANAGER` lets you override the project's package manager, so a project that's using `npm` gets its dependencies installed with, for example, `pnpm` instead.
+
+## Git scopes / shorthands
+
+We make your workflow faster by making you type this:
+
+```bash
+fkstart https://github.com/jonathan/some_app.git
+```
+
+instead of this:
+
+```bash
+git clone https://github.com/jonathan/some_app.git
+cd dev-utils
+npm install
+code .
+```
+
+You can save a few extra seconds, however, by typing this instead:
+
+```bash
+fkstart gh:jonathan/some_app
+```
+
+and we'll convert that into `https://github.com/jonathan/some_app.git`. And it's not just GitHub that we support, there are plenty of shorthands:
+
+| Alias | Points to            | That means                         |
+|:------|:---------------------|:-----------------------------------|
+| gh    | GitHub               | github.com/USER/REPO               |
+| gl    | GitLab               | gitlab.com/USER/REPO               |
+| bb    | Bitbucket            | bitbucket.org/USER/REPO            |
+| sr    | SourceForge          | sourceforge.net/p/USER/REPO        |
+| bbp   | Bitbucket Pipelines  | bitbucket.org/USER/REPO/pipelines  |
+| gist  | GitHub Gist          | gist.github.com/USER/REPO          |
+| cb    | Codeberg             | codeberg.org/USER/REPO             |
+| gt    | Gitee                | gitee.com/USER/REPO                |
+| fg    | Framagit             | framagit.org/USER/REPO             |
+| op    | OpenPrivacy Git      | git.openprivacy.ca/USER/REPO       |
 
 ---
 

mkdocs.yml

@@ -102,6 +102,8 @@ plugins:
               "crossruntime.md": "learn/cross-runtime-support.md"
               "crossplatform.md": "learn/cross-runtime-support.md"
               "follow-us.md": "about/social.md"
+              "why.md": "about/why.md"
+              "motivation.md": "about/why.md"
 
 markdown_extensions:
     - abbr