Update website for 5.2.0

Author: ZakaHaceCosas

docs/_index.md

@@ -16,7 +16,7 @@ _And the list goes on..._
 
 ## What we fixed, and how
 
-I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into five major releases, thirteen separate utilities (`clean`, `kickstart`, `release`, `commit`, `uncommit`, `surrender`, `setup`, `stats`, `launch`, `build`, `migrate`, `audit`, `terminate`), DenoJS & BunJS support, and even a small amount of features bridged to Go and Cargo.
+I initially created FuckingNode as a `.ps1` script to automate `npm prune` and `pnpm store prune` across a fixed list of personal projects, and as you can see, it has grown into five major releases, more than 12 separate utilities (like `clean`, `kickstart`, `release`, `commit`, `uncommit`, `surrender`, `setup`, `stats`, `launch`, `build`, `migrate`, `audit`, `terminate`), Deno & Bun support, and even a small amount of features bridged to Go and Cargo.
 
 FuckingNode exists because it fixes all of the issues mentioned above.
 

docs/about/why.md

@@ -123,7 +123,8 @@ This table is only updated when compatibility changes, don't mind the version nu
 
 | Support    | NodeJS npm | NodeJS pnpm | NodeJS yarn | Deno | Bun | Go | Cargo |
 | :--------- | ---------- | ----------- | ----------- | ---- | --- | -- | ----- |
-| **v4.0.0** | YES        | YES         | YES         | NO   | YES | NO | NO    |
+| **v5.2.0** | YES        | YES         | YES         | YES  | YES | NO | NO    |
+| v4.0.0     | YES        | YES         | YES         | NO   | YES | 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    |

docs/learn/audit.md

@@ -125,12 +125,14 @@ Currently supported settings are the following. Change them with `settings chang
 | :--- | :--- | ---: |
 | `default-intensity` | `normal`, `hard`, `hard-only`, `maxim`, or `maxim-only` | Changes the default intensity for the `clean` command. `normal` by default. |
 | `update-freq` | A fixed number, represents DAYS. | Changes how frequently the CLI sends an HTTP request for updates. Recommend to be high, as we don't frequently update. Defaults to `5`. |
-| `fav-editor`  | `vscode`, `sublime`, `emacs`, `atom`, `vscodium`, `notepad++` | Your favorite code editor. Used by `kickstart` and `launch`. VSCode by default. |
+| `fav-editor` | `vscode`, `sublime`, `emacs`, `atom`, `vscodium`, `notepad++` | Your favorite code editor. Used by `kickstart` and `launch`. VSCode by default. |
 | `default-manager` | `npm`, `pnpm`, `yarn`, `deno`, `bun`, `go`, or `cargo` | Default package manager, for use when we can't guess what to use. Makes most sense to set to a JS one; defaults to `npm`. |
-| `notifications`  | `true`, `false` | Whether to [use system notifications](../learn/notifications.md). Highly recommended, enabled by default. |
-| `notification-threshold`  | `true`, `false` | Disabled by default, makes system notifications only fire up if the task to be notified about takes less than the threshold value. |
-| `notification-threshold-value`  | A fixed number, represents MILLISECONDS. | Threshold value. Defaults to `10000` (10 seconds). |
+| `notifications` | `true`, `false` | Whether to [use system notifications](../learn/notifications.md). Highly recommended, enabled by default. |
+| `notification-threshold` | `true`, `false` | Disabled by default, makes system notifications only fire up if the task to be notified about takes less than the threshold value. |
+| `notification-threshold-value` | A fixed number, represents MILLISECONDS. | Threshold value. Defaults to `10000` (10 seconds). |
 | `always-short-circuit-cleanup` | `true`, `false` | Disabled by default, makes `clean` immediately halt if an error happens. See [this](usage.md#note-about-error-handling). |
+| `kickstart-root` | A file path | Unset by default, automatically roots kickstarted projects to there instead of the current working directory. Useful if you have a main "projects" folder or something similar. |
+| `workspace-policy` | `standalone` or `unified` | Unset by default. If set, when adding a project with workspaces, you won't be prompted for how to handle them; `standalone` handling will add each workspace individually and `unified` handling will add just the root. |
 
 ### View current settings
 

docs/manual/configuration.md

@@ -281,6 +281,19 @@ releaseCmd:
   - $release # e.g. 'npm run release'
 ```
 
+### kickstartCmd
+
+Specifies a CmdSet to be executed upon cloning the project with the `kickstart`.
+
+- **Type**: `CmdSet`
+- **Example**:
+
+```yaml
+kickstartCmd:
+  - =tasks/setup-env.mjs
+  - ~echo 'project is now ready to work on!'
+```
+
 ---
 
 ## Full sample
@@ -318,6 +331,9 @@ buildCmd:
   - =build.ts
   - ~mv ./out ./dist
 buildForRelease: true
+kickstartCmd:
+  - =tasks/setup-env.mjs
+  - ~echo 'project is now ready to work on!'
 ```
 
 ---