refactor: clean-up stuff

Author: notunderctrl

apps/docs/pages/guide/_meta.json

@@ -1,12 +1,12 @@
 {
     "installation": "Installation",
     "commandkit-setup": "CommandKit Setup",
-    "commandkit.config.js-options": "commandkit.config.js Options",
     "command-file-setup": "Commands Setup",
     "event-file-setup": "Events Setup",
     "validation-file-setup": "Validations Setup",
     "buttonkit": "Using ButtonKit",
     "using-cli": "Using CommandKit CLI",
+    "commandkit-config": "CommandKit Config",
     "using-signals": "Using Signals",
     "migrating-from-djs-commander": "Migrating from DJS-Commander"
 }

apps/docs/pages/guide/buttonkit.mdx

@@ -149,19 +149,19 @@ myButton.onClick(
 
 -   Type: [`Message`](https://old.discordjs.dev/#/docs/discord.js/main/class/Message)
 
-This is the message that ButtonKit uses to listen button clicks.
+The message object that ButtonKit uses to listen for button clicks (interactions).
 
 ### `time` (optional)
 
 -   Type: `number`
 
-This is the time you want the collector to run and listen for button clicks.
+The duration (in ms) the collector should run for and listen for button clicks.
 
 ### `autoReset` (optional)
 
 -   Type: `boolean`
 
-This determines if the collector should automatically reset the timer when a button is clicked.
+Whether or not the collector should automatically reset the timer when a button is clicked.
 
 ### Additional optional options
 

apps/docs/pages/guide/commandkit-config.mdx

@@ -0,0 +1,110 @@
+import { Callout } from 'nextra/components';
+
+# CommandKit Configuration
+
+CommandKit CLI can be configured using `commandkit.config` file in the root of your project directory (for example, by `package.json`). You can use either of the following files:
+
+-   `commandkit.js`
+-   `commandkit.config.js`
+-   `commandkit.mjs`
+-   `commandkit.config.mjs`
+-   `commandkit.cjs`
+-   `commandkit.config.cjs`
+-   `commandkit.json`
+-   `commandkit.config.json`
+
+Throughout this guide, we'll be using `commandkit.config.mjs` as an example.
+
+The following is the sample configuration required to run your bot:
+
+```js filename="commandkit.config.mjs" copy
+import { defineConfig } from 'commandkit';
+
+export default defineConfig({
+    src: 'src', // The source directory of your project.
+    main: 'index.mjs', // The JavaScript entry point of your project.
+});
+```
+
+## Options
+
+### `src`
+
+-   Type: `string`
+
+The source directory of the project where your source code lives.
+
+### `main`
+
+-   Type: `string`
+
+The entry point to your project.
+
+Example: If your source is structured as `src/index.ts`, this option must be set to `index.mjs`. This is because CommandKit always compiles your source code to esm format.
+
+<Callout type="warning">
+    The "src" part in this option isn't required because it's already defined in the `src` option.
+</Callout>
+
+### `watch` (optional)
+
+-   Type: `boolean`
+-   Default: `true`
+
+Whether to watch for file changes or not.
+
+### `outDir` (optional)
+
+-   Type: `string`
+-   Default: `"dist"`
+
+The output directory to emit the production build to.
+
+### `envExtra` (optional)
+
+-   Type: `boolean`
+-   Default: `true`
+
+Extra env utilities to load. This allows you to load environment variables in different formats, like `Date`, `JSON`, `Boolean`, etc.
+
+### `nodeOptions` (optional)
+
+-   Type: `string[]`
+-   Default: `[]`
+
+Options to pass to Node.js.
+
+### `clearRestartLogs` (optional)
+
+-   Type: `boolean`
+-   Default: `true`
+
+Whether or not to clear default restart logs.
+
+### `minify` (optional)
+
+-   Type: `boolean`
+-   Default: `false`
+
+Whether or not to minify the production build.
+
+### `sourcemap` (optional)
+
+-   Type: `boolean` | `"inline"`
+-   Default: `false`
+
+Whether or not to include sourcemaps in the production build.
+
+### `antiCrash` (optional)
+
+-   Type: `boolean`
+-   Default: `true`
+
+Whether or not to inject anti-crash script in the production build.
+
+### `requirePolyfill` (optional)
+
+-   Type: `boolean`
+-   Default: `true`
+
+Whether or not to polyfill `require` function.

apps/docs/pages/guide/commandkit.config.js-options.mdx

@@ -2,7 +2,7 @@ import { Callout } from 'nextra/components';
 
 # Using CommandKit CLI
 
-CommandKit CLI allows you to start and build your bot application.
+CommandKit CLI allows you to start, build, and manage your bot application. It also includes features such as anti-crash so you can be rest assured your bot won't crash and go offline during production.
 
 To get a list of the available CLI commands, run the following command inside your project directory:
 
@@ -30,18 +30,18 @@ Commands:
     <code>tsc --noEmit</code> command or any other tool of your choice.
 </Callout>
 
-# Available commands
+## Available commands
 
-## Build
+### Build
 
 `commandkit build` creates an optimized production build of your bot application. By default, commandkit emits the build to `dist/` directory in your project. It supports typescript out of the box.
 
 CommandKit also injects anti-crash script in your production build to prevent your bot from crashing due to cases like unhandled promise rejections. Although, it's recommended to handle these cases yourself. You can disable this behavior by setting `antiCrash: false` in your `commandkit.config.js` file.
 
-## Development
+### Development
 
 `commandkit dev` starts your bot in development mode. It supports hot reloading out of the box to automatically restart your bot when you make changes to your code. CommandKit automatically loads your environment variables from `.env` file in your project directory, without you having to worry about it. It also supports typescript out of the box.
 
-## Production
+### Production
 
 `commandkit start` starts your bot in production mode. You need to run `commandkit build` before running this command. This command also loads the environment variables from `.env` file in your project directory.