docs: Fix docs for latest loader & clean sections

Author: unrooot

docs/build.md

@@ -1,12 +1,12 @@
 ---
-title: Build
-sidebar_position: 3
+title: Contributing
+sidebar_position: 5
 ---
 
 # Build Nevermore locally
 This document is intended to help people submit bug patches, new features, and more to Nevermore. If you would simply like to consume Nevermore and not contribute to it, then this is not the correct article. Please see the [installation](/docs/install) docs for more.
 
-To provide a bit of background, Nevermore is a mono-repo. This means that it has a few hundred packages in one repository. In general, you should feel free to deploy Nevermore compatible packages to your own repository. This is part of what using npm empowers us to do. 
+To provide a bit of background, Nevermore is a mono-repo. This means that it has a few hundred packages in one repository. In general, you should feel free to deploy Nevermore compatible packages to your own repository. This is part of what using npm empowers us to do.
 
 ## What you need to be comfortable with
 Contributing to Nevermore is a little bit more difficult than consuming it. That being said, it shouldn't be too bad.
@@ -71,4 +71,4 @@ git clone https://github.com/Quenty/NevermoreEngine.git
 ## Why does building need a custom version of Rojo?
 Nevermore does not need a custom version of Rojo to be consumed, but it does need one to be built. This custom version of Rojo understands symlinks and turn them into ObjectValues. These symlinks link the packages together and means that a change to a transient dependency, or direct dependency will immediately be shown in the upstream package.
 
-As an added bonus, this custom version of Rojo also supports live-syncing mesh parts.
+As an added bonus, this custom version of Rojo also supports live-syncing mesh parts.

docs/design.md

@@ -1,6 +1,6 @@
 ---
 title: Design
-sidebar_position: 3
+sidebar_position: 4
 ---
 
 # Nevermore design principles
@@ -69,4 +69,3 @@ to as wide of an audience as possible, in many ways document and design notes ar
 ## Loading system
 
 Nevermore's loading system has changed over time, but is generally responsible for loading many modules.
-

docs/install.md

@@ -15,18 +15,17 @@ Nevermore should be installable within 2-3 minutes if you follow this guide.
   toc={toc.filter((node) => node.level <= 3)}
 />
 
-
-## Fast track: Installing via NPM and the Nevermore CLI
-If you want to just try out Nevermore, making a new templated game can be the easiest way to do this. For this reason, there is now a Nevermore CLI that can be used. A CLI stands for command line interface. 
+## Fast track: Installing via NPM and the Nevermore CLI (recommended)
+If you want to just try out Nevermore, making a new templated game can be the easiest way to do this. For this reason, there is now a Nevermore CLI that can be used. A CLI stands for command line interface.
 
 * Install [Node.js](https://nodejs.org/en/download/) v14+ on your computer.
 * Install [rojo](https://rojo.space/docs/v7/getting-started/installation/) v7+ on your computer.
 
-We can then use the npm command line to generate a working directory. 
+We can then use the npm command line to generate a working directory.
 
-1. Open a terminal, like Command Prompt, Powershell, or [Windows Terminal](https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701) (recommended). 
+1. Open a terminal, like Command Prompt, PowerShell, or [Windows Terminal](https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701) (recommended).
 2. Change directory to the location you would like to initialize and create files. You can do this by typing `mkdir MyGame` and then `cd MyGame`. You can use `dir` or `ls` to list out the current directory.
-2. Run the command `npx nevermore init` to generate a new game. 
+2. Run the command `npx nevermore init` to generate a new game.
 3. Run the command `npm install @quenty/maid` or whatever package you want.
 
 :::tip
@@ -42,7 +41,7 @@ This will install the current version of Maid and all dependencies into the `nod
 [npm](https://www.npmjs.com/) is a package manager. Nevermore uses npm to manage package versions and install transient dependencies. A transient dependency is a dependency of a dependency (for example, [Blend](/api/Blend) depends upon [Maid](/api/Maid).
 
 ### How do I install additional packages?
-The default installation comes with very few packages. This is normal. You can see which packages are installed by looking at the `package.json` file in a text editor. To install additional packages, simply run the following command in a terminal
+The default installation comes with very few packages. This is normal. You can see which packages are installed by looking at the `package.json` file in a text editor. To install additional packages, simply run the following command in a terminal:
 
 ```bash
 npm install @quenty/servicebag
@@ -57,7 +56,7 @@ When you run `npm install` you end up with a `package-lock.json`. You should com
 
 Nevermore is designed to work with games with existing architecture. If you're using Knit, a multi-script architecture, a custom framework or a single-script architecture, Nevermore provides a lot of utility modules that are useful in any of these scenarios. Nevermore's latest version also supports multiple copies of Nevermore running at once as long as bootstrapping is carefully managed. This can allow you to develop your game in an isolated way, or introduce Nevermore dependencies slowly as you need them.
 
- If you want to install this into an existing game follow these instructions.
+If you want to install this into an existing game follow these instructions:
 
 Ensure that you have [Node.js](https://nodejs.org/en/download/) v14+ installed on your computer.
 
@@ -67,48 +66,70 @@ Ensure that you have [rojo](https://rojo.space/docs/v7/getting-started/installat
 1. Install `npm install @quenty/loader`
 2. Sync in the `node_modules` folder using Rojo. A common file format is something like this:
 
-This is a rojo `project.json` file:
+This is an example of a Rojo `project.json` file that is generated by the Nevermore CLI:
 ```json
 {
-  "name": "GameName",
+  "name": "MyGame",
   "globIgnorePaths": [ "**/.package-lock.json" ],
   "tree": {
     "$className": "DataModel",
     "ServerScriptService": {
-      "integration": {
-        "$path": "node_modules"
+      "MyGame": {
+        "$className": "Folder",
+        "game": {
+          "$path": "src/modules"
+        },
+        "node_modules": {
+          "$path": "node_modules"
+        }
+      },
+      "GameNameScripts": {
+        "$path": "src/scripts/Server"
+      }
+    },
+    "StarterPlayer": {
+      "StarterPlayerScripts": {
+        "GameNameScripts": {
+          "$path": "src/scripts/Client"
+        }
       }
     }
   }
 }
 ```
 
-You can put the `node_modules` folder whereever you want, but the recommended location is `ServerScriptService`. 
+You can put the `MyGame` folder wherever you want, but the recommended location is `ServerScriptService`.
 
-In your main script you will need to "bootstrap" the components such that `script.Parent.loader` is defined. To do this the following snippet will work.
+In your main script you will need to "bootstrap" the components such that `script.Parent.loader` is defined. To do this the following snippet will work, and is generated by the Nevermore CLI as `ServerMain.server.lua`:
 
 ```lua
 local ServerScriptService = game:GetService("ServerScriptService")
 
-local loader = ServerScriptService.Path.To.NodeModules:FindFirstChild("LoaderUtils", true).Parent
-local packages = require(loader).bootstrapGame(ServerScriptService.Path.To.NodeModules)
+local loader = ServerScriptService.MyGame:FindFirstChild("LoaderUtils", true).Parent
+local require = require(loader).bootstrapGame(ServerScriptService.MyGame)
 ```
 
-This will create the following components which you can rename if you want.
+This will create the following folders in ReplicatedStorage when the game loads:
+1. MyGame
+	* game
+		* Client
+		* Shared
+		* Server
+	* node_modules
 
-1. ReplicatedStorage.Packages
-2. ReplicatedStorage.SharedPackages
-3. ServerScriptService.Packages
+:::caution
+You might notice that the Server folder is also cloned to the `game` folder in ReplicatedStorage. This is an intentional optimization that only happens in Studio.
+:::
 
-From here, every exported package will exist in the packages folder root, with only modules needed to be replicated.
+From here, every exported package will exist in the `node_modules` folder, populated only by modules that need to be replicated to that context.
 
-To access the exported packages on the client, you perform the same bootstrap operation on the new replicated location.
+To access the exported packages on the client, you perform the same bootstrap operation on the new replicated location (also generated, as `ClientMain.client.lua`):
 
 ```lua
 local ReplicatedStorage = game:GetService("ReplicatedStorage")
 
-local loader = ReplicatedStorage.Path.To.Replicated.NodeModules:FindFirstChild("LoaderUtils", true).Parent
-local packages = require(loader).bootstrapGame(ReplicatedStorage.Path.To.Replicated.NodeModules)
+local loader = ReplicatedStorage:WaitForChild("MyGame"):WaitForChild("loader")
+local require = require(loader).bootstrapGame(loader.Parent)
 ```
 
 Assuming you've changed nothing, the path to the replicated modules should be the same as the one used on the server, just indexed under ReplicatedStorage instead.
@@ -123,7 +144,7 @@ Ensure that you have [rojo](https://rojo.space/docs/v7/getting-started/installat
 1. Run `npm init`
 2. Run `npm install @quenty/loader` and whatever packages you want.
 
-In your bootstrapping code you can write something like this for your server code. 
+In your bootstrapping code you can write something like this for your server code.
 
 Notice we manually transform and parent our returned loader components. this allows us to bootstrap the
 components. We then parent the client component into ReplicatedFirst with dependencies.
@@ -177,6 +198,12 @@ serviceBag:Start()
 ```
 
 ## Manually installing with NPM for Plugins
+You can use the Nevermore CLI to generate a project structure for a new plugin.
+
 Ensure that you have [Node.js](https://nodejs.org/en/download/) v14+ installed on your computer.
 
 Ensure that you have [rojo](https://rojo.space/docs/v7/getting-started/installation/) v7+ installed on your computer.
+
+```bash
+npx nevermore init-plugin
+```