Update URLs and improve writing in some places

ZakaHaceCosas · ZakaHaceCosas · commit 9a1660d6faf6 · 2025-03-09T10:03:00.000+01:00
diff --git a/README.md b/README.md
@@ -1,2 +1,3 @@
-# documentation
-Documentation website for the FuckingNode CLI tool.
+# FuckingNode documentation
+
+Live at [this URL](https://fuckingnode.github.io/). Documentation website for the FuckingNode CLI tool. Also includes installer scripts.
diff --git a/docs/about/branding.md b/docs/about/branding.md
@@ -6,15 +6,13 @@ Just in case you wanted to write an article or make a video about us (thank you!
 
 ## The logo
 
-You can use our logo just as you'd use any app's logo in a post, video, or any kind of visual content that requires it. With proper attribution, of course. A PNG is available from our main repository.
-
-Please don't alter it however. Only valid change is making it full black (`#000`) instead of full white (`#FFF`) for usage over light backgrounds.
+You can use our logo just as you'd use any app's logo in a post, video, or any kind of visual content that requires it (with proper attribution, of course). Black and white PNGs are available from this website's repository.
 
 ## The name
 
-Ideally, capitalize it as FuckingNode. The asterisk (F*ckingNode) is optional. If used, censor the U and not any other letter (<s>F\*ckingNode</s>).
+Ideally, capitalize it as FuckingNode. The asterisk (F*ckingNode) is optional. If used, censor the U and not any other letter (avoid things like <s>F\*\*kingNode</s>).
 
-There isn't any preference towards font families to be used. We recommend a `monospace` font.
+There isn't a real preference towards font families to be used. We recommend a `monospace` font.
 
 ### Can acronyms or abbreviations be used?
 
@@ -24,9 +22,9 @@ There isn't any preference towards font families to be used. We recommend a `mon
 
 **Keep the logo white or black.** If you _really_ want to color it, go for either light green (like this documentation site's accent color), or orange. `#FCA737` (our classic orange) or `#65BA4F` (lightened NodeJS' logo green) could do.
 
-## Something needless to say
+## Needless to say
 
-Our logo, name, and branding are _ours_. They're made with love and effort and they may not be used anywhere without either crediting us or having our explicit consent. Copyright actions might be taken if we see them necessary; we hope you'll be able to abide by such a simple rule.
+Our logo, name, and branding are _ours_. They're made with love and effort and they may not be used anywhere without either crediting us or having our explicit consent. Copyright actions may be taken if we see them necessary; so we hope you'll be able to abide by such a simple rule.
 
 ---
 
diff --git a/docs/about/roadmap.md b/docs/about/roadmap.md
@@ -68,15 +68,13 @@ We'll expand (and rarely, but not impossibly, shrink) this roadmap as we make pr
 
 ### Version 3.3
 
-- [ ] Stabilize `audit` feature and support it everywhere NodeJS.
-  - [ ] Stabilize it
-      - [ ] Fix known issues (see TODO.md at the repository).
-      - [ ] Expand vector string lists.
-  - [x] Support it
-      - [x] pnpm
-      - [x] yarn
-- [ ] Extend the FuckingNode Interop Layer
-    - [ ] Auditer (this is a bit special, you'll see what we mean soon).
+- [ ] Rewrite `audit` feature.
+    - [ ] Stabilize it
+        - [ ] Fix known issues (see TODO.md at the repository).
+        - [ ] Expand vector string lists & question list.
+    - [x] Support it everywhere NodeJS
+        - [x] pnpm
+        - [x] yarn
 
 ---
 
diff --git a/docs/about/social.md b/docs/about/social.md
@@ -1,6 +1,38 @@
+<!-- markdownlint-disable md033 md030 -->
 # Follow us
 
-- [Discord server](https://discord.gg/AA2jYAFNmq) - Our community server is probably the most important part of the community. Sneak peeks, feature suggestions, and important announcements live here.
-- [Bluesky](https://bsky.app/profile/fknode.bsky.social) - Twitter, but better because these guys kept their "bird" (well it's a butterfly but you get my point).
-- [Twitter](https://x.com/FuckingNode) - Users who refer to this platform as "X" instead of "Twitter" will be prohibited from using FuckingNode.
-- [YouTube](https://youtube.com/watch?v=_lppvGYUXNk) - This one isn't really _our own_, as this is my (the creator's) personal channel and has unrelated stuff. Still, major release trailers will live here so it's worth noting.
+<div class="grid cards" markdown>
+
+-   :fontawesome-brands-discord:{ .lg .middle } __[Discord server](https://discord.gg/AA2jYAFNmq)__
+
+    ---
+
+    Our community server is probably the most important part of the community. Sneak peeks, feature suggestions, and important announcements live here.
+
+    [:octicons-arrow-right-24: Join us](https://discord.gg/AA2jYAFNmq)
+
+-   :fontawesome-brands-bluesky:{ .lg .middle } __[Bluesky](https://bsky.app/profile/fknode.bsky.social)__
+
+    ---
+
+    Basically Twitter but better because these guys kept their bird (I mean it's a butterfly not a bird but you get my point).
+
+    [:octicons-arrow-right-24: Follow us](https://bsky.app/profile/fknode.bsky.social)
+
+-   :fontawesome-brands-twitter:{ .lg .middle } __[Twitter](https://x.com/FuckingNode)__
+
+    ---
+
+    Users who refer to this platform as "X" instead of "Twitter" will be prohibited from using FuckingNode.
+
+    [:octicons-arrow-right-24: Follow us](https://x.com/FuckingNode)
+
+-   :fontawesome-brands-youtube:{ .lg .middle } __[YouTube](https://youtube.com/watch?v=_lppvGYUXNk)__
+
+    ---
+
+    This isn't really _our own YouTube_, it's the creator's personal channel and has unrelated stuff. Still, major release trailers will be here (and a trailer for V3 is work in progress).
+
+    [:octicons-arrow-right-24: Watch us](https://youtube.com/watch?v=_lppvGYUXNk)
+
+</div>
diff --git a/docs/about/why.md b/docs/about/why.md
@@ -65,6 +65,6 @@ FuckingNode is a thing because it fixes all of the issues mentioned above.
 
 ---
 
-That is why FuckingNode is a thing; because it's a single tool to fix everything. And if there's something we didn't fix yet, just [join our Discord server](https://discord.gg/AA2jYAFNmq), mention us on [Twitter](https://x.com/FuckingNode) or [Bluesky](https://bsky.app/FuckingNode), or [raise an issue on GitHub](https://github.com/ZakaHaceCosas/FuckingNode/issues) telling us what else you'd like to see within our tooling, and we'll add it (if possible).
+That is why FuckingNode is a thing; because it's a single tool to fix everything. And if there's something we didn't fix yet, just [join our Discord server](https://discord.gg/AA2jYAFNmq), mention us on [Twitter](https://x.com/FuckingNode) or [Bluesky](https://bsky.app/profile/fknode.bsky.social), or [raise an issue on GitHub](https://github.com/FuckingNode/FuckingNode/issues) telling us what else you'd like to see within our tooling, and we'll add it (if possible).
 
 *[CWD]: Current Working Directory
diff --git a/docs/index.md b/docs/index.md
@@ -37,23 +37,23 @@
 
     Never again make a commit without running your test-suite test.
 
-    [:octicons-arrow-right-24: Safe commits](https://zakahacecosas.github.io/FuckingNode/manual/commit/)
+    [:octicons-arrow-right-24: Safe commits](./manual/commit.md)
 
 -   :fontawesome-solid-skull:{ .lg .middle } **Be prepared for anything**
 
     ---
 
     With the world’s only chad-enough JavaScript CLI to auto-deprecate projects at will.
 
-    [:octicons-arrow-right-24: Automated deprecations](https://zakahacecosas.github.io/FuckingNode/manual/surrender/)
+    [:octicons-arrow-right-24: Automated deprecations](./manual/surrender.md)
 
 -   :material-arm-flex:{ .lg .middle } **Flex about it**
 
     ---
 
     Your friends waste lots of their time manually maintaining never-releasing JS projects. Show 'em the F\*ckingNode way.
 
-    [:octicons-arrow-right-24: Download now](https://github.com/ZakaHaceCosas/FuckingNode/releases/latest)
+    [:octicons-arrow-right-24: Download now](https://github.com/FuckingNode/FuckingNode/releases/latest)
 
 </div>
 
diff --git a/docs/learn/audit.md b/docs/learn/audit.md
@@ -85,7 +85,7 @@ $$
 There is a `--strict` flag that can be passed to the audit command that adds an additional **risk bump**, based on the severity of the most-severe identified vulnerability, as follows:
 
 $$
-Strict R.B. = \frac{R.F. + (R.B. \times 100)}{2}
+Strict R.F. = \frac{R.F. + (R.B. \times 100)}{2}
 $$
 
 RB values are as follows:
diff --git a/docs/learn/cross-runtime-support.md b/docs/learn/cross-runtime-support.md
@@ -23,7 +23,7 @@ Reasons for not supporting a feature are the following.
 
 ## Partial Deno, Bun, Cargo & Go support for cleanup
 
-In both runtimes, the kind of cleanup commands we'd use (`prune`, `dedupe`...) aren't available.
+In both runtimes, the kind of cleanup commands we'd use (`prune`, `dedupe`...) aren't available, so the _cleanup itself_ isn't available. `clean` will still work with them, as lintage, prettification, or updates may work. Run `fuckingnode compat cleaner`.
 
 ## No Deno support for hard cleanup
 
diff --git a/docs/learn/index.md b/docs/learn/index.md
@@ -1,14 +1,14 @@
 # Learn: How does F*ckingNode work from the inside?
 
-For wannabe contributors or people curious / bored enough, all pages in here explain in detail how does each feature work from an insider perspective.
+For wannabe contributors or curious / bored enough people, pages in here explain in detail how do our most important features work from an insider perspective.
 
 Only features worth including are mentioned - not because other features are worthless, but because some of them simply don't need a page.
 
 > `fuckingnode setup` for example is simple enough to be understood; a list of templates, you give it a name, and if a template with that name exists, it creates a file and writes the template to it (or overwrites an existing one, deep-merging if possible).
-> It's simplicity saves us a few pages up.
+>
+> Its simplicity removes the need to make a "learning page", saving a few pages up.
 
 ## Table of Contents
 
 - [Clean](clean.md)
-- [Kickstart](kickstart.md)
 - [(Experimental) Audit](audit.md)
diff --git a/docs/learn/kickstart.md b/docs/learn/kickstart.md
diff --git a/docs/manual/configuration.md b/docs/manual/configuration.md
@@ -82,7 +82,7 @@ Just run `fuckingnode manager list`. It'll beautifully show you all of your proj
 💡 Here are the m*therf*ckers you added so far:
 
 personaplus@0.0.6-preapp.29 C:\\Users\\Zaka\\personaplus
-@zakahacecosas/fuckingnode@3.0.0-rc.1 C:\\Users\\Zaka\\FuckingNode
+@zakahacecosas/fuckingnode@3.1.0 C:\\Users\\Zaka\\FuckingNode
 @zakahacecosas/string-utils@1.11.0 C:\\Users\\Zaka\\string-utils
 ...
 ```
diff --git a/docs/manual/index.md b/docs/manual/index.md
@@ -13,6 +13,7 @@ These are links to individual pages. For the full manual, click the first one, t
 - [Extra - Kickstart](kickstart.md)
 - [Extra - Commit](commit.md)
 - [Extra - Release](release.md)
+- [Extra - Launch](launch.md)
 - [Extra - Surrender](surrender.md)
 - [Extra - Setup](setup.md)
 - [Extra - Stats](stats.md)
@@ -26,40 +27,43 @@ For further learning:
 
 ### Step 1
 
-Add all of your projects. This is done manually with the `fuckingnode manager add <path>` command. Path can be relative, absolute, or the `--self` flag to use the CWD.
+Add your projects to FuckingNode's project list. This is done manually with the `fuckingnode manager add <path>` (or `fkadd <path>`) command. `<path>` can be any file path, or `--self` to use the CWD.
 
 ```bash
 # relative
 fuckingnode manager add "../projects/project1"
 # absolute
-fuckingnode manager add "/home/engin/projects/project2"
+fuckingnode manager add "/home/me/projects/project2"
 # self path
 cd project3
 fuckingnode manager add --self
 ```
 
-It's recommended that from now on you run `manager add --self` immediately after running `npm init` (or `pnpm init` or whatever) each time you create a project.
+It's recommended that from now on you run `fkadd --self` immediately after running `npm init` (or `pnpm init` or whatever) each time you create a project.
 
 ### Step 2
 
 A basic cleanup is invoked by running this command, with no arguments.
 
 ```bash
 fuckingnode clean
+# or "fkclean"
 ```
 
-It's simple, and while it doesn't recover gigabytes, it's fast and it gets the job done. Additional flags can be passed for using more advanced features.
+While it doesn't recover gigabytes of storage, it's simple, fast and gets the job done. Flags can be passed for using extra features.
 
-Keep in mind it's a global command; it'll run the cleanup (with the same flags if passed) across all the projects you've added, saving you time.
+Keep in mind cleanup is global by default; it'll run (with the same flags if passed) across all the projects you've added, saving you time.
 
-A config file `fknode.yaml` can be created at the root of an added project to override this some behaviors.
+A config file `fknode.yaml` can be created at the root of a project to customize behavior. Learn more [here](fknode-yaml.md).
 
 You can also clean a specific project providing it's path, or it's name from the `package.json`.
 
 ```bash
-fuckingnode clean ../project1 # only clean /home/users/me/project1, for example
-# or
-fuckingnode clean my-framework # only clean the project with "my-framework" in the "name" field
+# only clean /home/users/me/project1, for example
+fuckingnode clean ../project1
+
+# only clean the project with "my-framework" in the "name" field
+fuckingnode clean my-framework
 ```
 
 ### Step 3
@@ -70,9 +74,9 @@ For increased intensity, use this.
 fuckingnode clean hard
 ```
 
-Immediately after cleaning all of your projects, it'll now clear global caches of all your installed package managers.
+When cleaning like this, global caches from all your installed package managers will be cleared immediately after cleaning all of your projects.
 
-If you only wish to clear global caches without waiting for individual cleanup of all projects, use `fuckingnode clean hard-only`, or a shortcut (`fuckingnode global-clean` or `fuckingnode hard-clean`).
+If you only wish to clear global caches without waiting for individual cleanup of all of your projects, use `fuckingnode clean hard-only`, or a shortcut (`fuckingnode global-clean` or `fuckingnode hard-clean`).
 
 ### Step 4
 
@@ -84,16 +88,16 @@ For the best experience, you can pass flags to the clean command for using addit
 - `--update` updates dependencies
 - `--commit` commits changes made by us (e.g. changes to your lockfile because of updating)
 
-Each flag can be invoked with the 1st letter for faster typing (`-l` = `--lint`, `-p` = `--pretty`...)
+Each flag can be invoked with its 1st letter for faster typing (`-l` = `--lint`, `-p` = `--pretty`...).
 
-As outlined [before](#step-2) cleaning is global. When running with `--lint` all your projects will be automatically linted (unless overridden, as said), greatly increasing your productivity.
+As outlined [before](#step-2) cleaning is global. When running with `--lint` all your projects will be automatically linted (unless overridden via an [`fknode.yaml` file](fknode-yaml.md)), greatly increasing your productivity.
 
-Behavior itself can also be overridden, in case you use a different linter than ESLint, or a different prettifier than Prettier. All flags support their custom configuration.
+Behavior itself can also be overridden via an `fknode.yaml` file, in case you'd like to use a different linter than ESLint, or a different prettifier than Prettier.
 
-There are two exceptions to the "global cleaning" rule mentioned earlier:
+Note `--destroy` and `--commit` _are_ effected by the global cleaning rule, however they won't run by default as they require configuration via an `fknode.yaml` file:
 
-- `--destroy` requires per-project configuration via `fknode.yaml` (you shall specify what you want to be removed). We don't have "default" directories to auto-remove like `dist/`, to avoid removing something you _might_ need.
-- `--commit` requires per-project configuration via `fknode.yaml`. Making a commit is a sensible action, as we could potentially commit something you did _not_ intend to commit yet. Committing requires explicit allowance from you, and additional safety checks are performed as outlined [here](../manual/usage.md#committing-your-code-commit).
+- `--destroy` requires you to specify what you want to be removed. We don't have "default" directories to auto-remove like `dist/`, to avoid removing something you _might_ need.
+- `--commit` requires you to specify permission to run. Making a commit is a sensible action, as we could potentially commit something you did _not_ intend to commit yet. Hence, committing requires explicit allowance from you, and additional safety checks are performed as outlined [here](../manual/usage.md#committing-your-code-commit).
 
 ---
 
diff --git a/docs/manual/install.md b/docs/manual/install.md
@@ -9,15 +9,15 @@ First thing first, install the CLI:
 Copy and paste the following code in a terminal session.
 
 ```powershell
-powershell -c "irm zakahacecosas.github.io/FuckingNode/install.ps1 | iex"
+powershell -c "irm fuckingnode.github.io/install.ps1 | iex"
 ```
 
 ### Linux and macOS
 
 Copy and paste the following code in a terminal session.
 
 ```bash
-curl -fsSL zakahacecosas.github.io/FuckingNode/install.sh | bash
+curl -fsSL fuckingnode.github.io/install.sh | bash
 ```
 
 ### NixOS
@@ -26,7 +26,7 @@ Add the repo to your `flake.nix`.
 
 ```nix
 inputs = {
-    fuckingnode.url = "github:ZakaHaceCosas/FuckingNode";
+    fuckingnode.url = "github:FuckingNode/FuckingNode";
 }
 ```
 
diff --git a/docs/manual/surrender.md b/docs/manual/surrender.md
diff --git a/docs/manual/whats-next.md b/docs/manual/whats-next.md
diff --git a/mkdocs.yml b/mkdocs.yml
