More general docs cleanup

Author: NotNite

src/content/docs/dev/core-extensions.md

@@ -0,0 +1,32 @@
+---
+title: Writing core extensions
+sidebar:
+  order: 6
+---
+
+Core extensions are extensions built into moonlight. They are usually libraries or important features.
+
+Core extensions cannot be uninstalled, but they can be disabled. Some core extensions are enabled by default when moonlight is installed for the first time.
+
+The biggest core extension is [Moonbase](https://github.com/moonlight-mod/moonlight/tree/main/packages/core-extensions/src/moonbase), which is responsible for installing and updating extensions, updating moonlight itself, and providing a UI to manage everything. moonlight's core does not contain any functionality for installing/updating extensions or updating moonlight, and it is instead implemented inside of Moonbase.
+
+## Developing core extensions
+
+Core extensions live in the `packages/core-extensions` folder in the moonlight repository. As such, adding new core extensions must be done in a [pull request](/dev/setup).
+
+Keep in mind that moonlight currently [uses a separate build system](/dev/project-structure#build-system) from other external extensions, so there may be more bugs, and some changes may not apply until you [restart the development server](/ext-dev/getting-started#edit-and-reload-your-extension).
+
+## Creating a new core extension
+
+Before you create a core extension, consider if your extension idea is a good fit for a core extension. An extension is a good fit for a core extension if it's a library or development tool, but actual features or tweaks should usually be distributed on a extension repository instead. This isn't a hard rule, though, so feel free to ask if you're considering making a core extension!
+
+After cloning moonlight, simply create a new folder with a `manifest.json` inside of it, and structure it like a normal moonlight extension. The extension manifest should not contain a `version` or `meta.source`.
+
+## Adding types
+
+The types for core extensions should be placed in the `types` package so other extensions can use them.
+
+- Create a new file in the `coreExtensions` folder, and export the types from there.
+- Re-export the types in `coreExtensions.ts`.
+- Register the type in the Webpack require function in `discord/require.ts`.
+- Register the type for module imports in `import.d.ts`.

src/content/docs/dev/project-structure.md

@@ -50,9 +50,7 @@ The types package is published alongside moonlight releases, but some moonlight
 
 ## Core extensions
 
-Core extensions are extensions built into moonlight. They cannot be uninstalled, but they can be disabled. A few core extensions are enabled by default when the config is created for the first time. An extension is a good fit for a core extension if it's a library or development tool, but actual features or tweaks should usually be distributed on a extension repository instead. This isn't a hard rule, though, so feel free to ask if you're considering making a core extension!
-
-The biggest core extension is [Moonbase](https://github.com/moonlight-mod/moonlight/tree/main/packages/core-extensions/src/moonbase), which is responsible for installing and updating extensions, updating moonlight itself, and providing a UI to manage everything. Unlike other client mods, Moonbase is just implemented as another extension, and can be disabled if the user wants. The core does not contain any functionality for installing/updating extensions or updating moonlight, and it is instead implemented inside of Moonbase.
+Core extensions are extensions built into moonlight. This section has moved into its own dedicated page, which you can see [here](/dev/core-extensions).
 
 ## Load stages
 

src/content/docs/dev/setup.md

@@ -5,20 +5,19 @@ sidebar:
   order: 1
 ---
 
+moonlight requires [Node.js](https://nodejs.org) 22 and [pnpm](https://pnpm.io) 10.
 
-You will need [pnpm](https://pnpm.io) 10, as moonlight uses it for dependency and workspace management.
-
-- Clone the repository.
-- Install dependencies with `pnpm i`.
-- Build the project with `pnpm run build`.
+- Clone the repository: `git clone https://github.com/moonlight-mod/moonlight.git`
+- Install dependencies: `pnpm install`.
+- Build the project: `pnpm run build`.
   - For working on moonlight, a watch mode is available with `pnpm run dev`.
 
 For more information on project structure, [see the dedicated page](/dev/project-structure).
 
 ## Contribution guidelines
 
 - Ensure your commits pass Prettier/ESLint. This is a requirement for merge.
-  - moonlight uses [husky](https://typicode.github.io/husky/) to check lints on commit.
+  - moonlight uses [husky](https://typicode.github.io/husky) to check lints on commit. This should have automatically been setup for you when running `pnpm install`.
 - Please make PRs to the `develop` branch instead of `main`.
   - `develop` is merged into `main` when moonlight updates happen. Our in-progress work resides on `develop`.
 - Don't break the existing API surface.

src/content/docs/ext-dev/api.md

@@ -14,36 +14,74 @@ The global types are available [here](https://github.com/moonlight-mod/moonlight
 - `moonlightNode`: available in the web *and* Node.js environments
   - Contains configuration details, browser checks
   - Polyfilled in the browser extension
-- `moonlightNodeSandboxed`: available in the Node.js environments (`node.ts`)
+- `moonlightNodeSandboxed`: available in the host and Node.js environments (`host.ts`, `node.ts`)
   - Contains filesystem APIs
 - `moonlightHost`: available in the host environment (`host.ts`)
   - Contains configuration details, `.asar` path
 
 ## Extension libraries
 
-Remember to [add the module as a dependency](/ext-dev/webpack#webpack-module-dependencies).
+These libraries are built into moonlight as [core extensions](/dev/core-extensions). Remember to [add the extension dependency](/ext-dev/cookbook#using-another-extension-as-a-library) and [add the module dependency](/ext-dev/webpack#webpack-module-dependencies) before using these libraries.
+
+### App Panels
+
+Add custom "app panels" next to the user area and mute buttons.
+
+- Module ID: `appPanels_appPanels`
+- Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/appPanels.ts)
+
+### Commands
+
+Register slash commands and perform text manipulation.
+
+- Module ID: `commands_commands`
+- Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/commands.ts)
+
+### Common
+
+Provides re-exports of Flux stores, and a custom error boundary component.
+
+- Module IDs: `common_stores`, `common_ErrorBoundary`
+- Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/common.ts)
+
+### Component Editor
+
+Add custom elements to commonly edited components.
+
+- Module IDs: `componentEditor_dmList`, `componentEditor_memberList`, `componentEditor_messages`
+- Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/componentEditor.ts)
 
 ### Context Menu
 
+Create additional items on existing context menus.
+
 - Module ID: `contextMenu_contextMenu`
 - Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/contextMenu.ts)
 
 ### Markdown
 
+Register custom Markdown rules for rendering chat messages.
+
 - Module ID: `markdown_markdown`
 - Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/markdown.ts)
 
 ### Notices
 
+Add banners (known as "notices") to the top of the client window.
+
 - Module ID: `notices_notices`
 - Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/notices.ts)
 
 ### Settings
 
+Add custom entries to Discord's settings page.
+
 - Module ID: `settings_settings`
 - Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/settings.ts)
 
 ### Spacepack
 
+Find and inspect existing Webpack modules.
+
 - Module ID: `spacepack_spacepack`
 - Types: [here](https://github.com/moonlight-mod/moonlight/blob/main/packages/types/src/coreExtensions/spacepack.ts)

src/content/docs/ext-dev/devtools.md

@@ -7,19 +7,19 @@ sidebar:
 
 The Chrome DevTools is a panel/window that offers several utilities for web development. Normally, it is intended for the creators of the target application, but it also serves as an excellent tool for client modders.
 
+To open DevTools, press `Ctrl + Shift + I`. If this keybind doesn't do anything, you may need to [enable DevTools](#enabling-devtools) first.
+
 ## Enabling DevTools
 
-In some branches of Discord, the following is required in the `settings.json` file (*not* the moonlight config file):
+In some branches of Discord, you must enable DevTools in Discord's config file. This is *not* the moonlight config file, and it is present in [Discord's config folder](/using/crash-recovery#finding-discords-logs). Add this entry to `settings.json`, then restart your client:
 
 ```json
 "DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING": true
 ```
 
-This can be located in `%AppData%/Discord` on Windows and `~/.config/discord` on Linux.
-
 ## Reading module sources
 
-See the [helpful extensions](/ext-dev/helpful-exts) page first for `patchAll` and how to use Spacepack.
+See the [helpful extensions](/ext-dev/helpful-exts) page first. You should enable "Patch all" and configure Spacepack.
 
 To see the source of a module, print the function with `spacepack.inspect`:
 
@@ -35,7 +35,11 @@ You can chain `inspect` with `findByCode` (or an equivalent) when trying to find
 spacepack.inspect(spacepack.findByCode(/* finds */)[0].id)
 ```
 
-Also see [this page](/ext-dev/webpack#common-patterns) for common patterns to look out for.
+Some patterns may stick out when reading minified Discord source code:
+
+- The pattern `n(/* some number */)` (or some other minified variable) represents a Webpack module require, and the function argument is the module ID. You can pass that module ID to `spacepack.inspect` to read the required module's source.
+- `Z` and `ZP` usually correspond to `default` exports. Despite being minified, these export names are stable.
+- Mentions of `jsx` and `createElement` imply construction of React components.
 
 ## Using the Sources tab
 
@@ -53,7 +57,7 @@ You can set breakpoints on Webpack modules to inspect the variables at runtime.
 
 React DevTools allows you to inspect the React component tree easier, instead of its representation with the DOM. You can view the sources of components and their props this way.
 
-Either [use the rehosted version](https://moon.light.pm/files/reactdevtools.zip) or [download the extension and extract it yourself](https://react.dev/learn/react-developer-tools). Use the "DevTools Extensions" extension to load it - remember to restart Discord fully after configuring it. A new Components tab will appear in DevTools.
+Either [use the rehosted version](https://moon.light.pm/files/reactdevtools.zip) or [download the extension and extract it yourself](https://react.dev/learn/react-developer-tools). Use the "DevTools Extensions" extension to load it, and remember to restart Discord fully after configuring it. Once loaded, a new Components tab will appear in DevTools.
 
 You can use the element picker to select components. Props are available on the right side. Click the bug icon to view data about the component. Click the bracket icon to view the source of the component.