diff --git a/content/docs/commander/hide-reveal.mdx b/content/docs/commander/hide-reveal.mdx
new file mode 100644
index 0000000..3c5da1f
--- /dev/null
+++ b/content/docs/commander/hide-reveal.mdx
@@ -0,0 +1,103 @@
+---
+title: Command Visibility
+description: Control command visibility in tab completion
+---
+
+# Hiding and Revealing Commands
+
+Hiding commands allows you to control which commands appear in tab completion,
+creating a cleaner experience for players while still allowing the commands to be executed by those who know them.
+
+## Commands
+
+### Hide a Command
+
+Usage: `/command hide <command>`  
+Hides a command from tab completion.
+
+**Examples:**
+```
+<gray># Hide specific commands</gray>
+/command hide <aqua>plugins</aqua>
+/command hide <aqua>pl</aqua>
+
+<gray># Hide all commands</gray>
+/command hide <aqua>"*"</aqua>
+
+<gray># Hide all bukkit namespaced commands</gray>
+/command hide <aqua>"bukkit:*"</aqua>
+
+<gray># Hide all namespaced commands</gray>
+/command hide <aqua>"*:*"</aqua>
+```
+
+<Callout type="warning">
+  Using `/command hide "*"` will hide literally **ALL** commands, including `/command` itself.  
+  Use `/command reveal "*"` to quickly restore all hidden commands.
+</Callout>
+
+### Reveal a Command
+Usage: `/command reveal <command>`
+Makes a previously hidden command visible again in tab completions.
+
+**Examples:**
+```
+<gray># Reveal specific commands</gray>
+/command reveal <aqua>plugins</aqua>
+/command reveal <aqua>pl</aqua>
+
+<gray># Reveal all hidden commands</gray>
+/command reveal <aqua>"*"</aqua>
+
+<gray># Reveal all bukkit namespaced commands</gray>
+/command reveal <aqua>"bukkit:*"</aqua>
+
+<gray># Reveal all namespaced commands</gray>
+/command reveal <aqua>"*:*"</aqua>
+```
+
+## Bypass Permission
+Players with the `commander.bypass` permission can see all hidden commands.
+
+<Callout type="info">
+  Wildcard permissions (like `*`) are ignored for the bypass permission.  
+  Players must have the explicit `commander.bypass` permission to see hidden commands.
+</Callout>
+
+## Use Cases
+
+### Clean Command Lists
+Hide administrative or utility commands that regular players shouldn't see:
+```
+/command hide <aqua>plugins</aqua>
+/command hide <aqua>pl</aqua>
+/command hide <aqua>version</aqua>
+/command hide <aqua>ver</aqua>
+```
+
+### Server-Specific Commands
+Hide commands that are only relevant to certain server types or gamemodes.
+
+### Development Commands
+Hide debugging or development commands from production environments.
+
+## Configuration
+
+Hidden commands are stored in a JSON configuration file.  
+The file contains a simple array of command names that should be hidden.
+
+`hidden-commands.json`:
+```json
+[
+  "plugins",
+  "pl",
+  "version",
+  "ver"
+]
+```
+
+## Tips
+
+- Commands are hidden without the `/` prefix in the configuration
+- Both the full command name and aliases should be hidden if desired
+- Use `/command reload` to reload the configuration if manually edited
\ No newline at end of file
diff --git a/content/docs/commander/index.mdx b/content/docs/commander/index.mdx
index d5bc629..ec241ae 100644
--- a/content/docs/commander/index.mdx
+++ b/content/docs/commander/index.mdx
@@ -4,4 +4,123 @@ description: Manage command visibility and permissions
 icon: BookMarked
 ---
 
-Coming soon!
+# Commander
+
+Commander is a powerful Minecraft server plugin that gives you complete control over command visibility,
+permissions, and registration.
+Clean up your command list, enhance security, and customize your server's command experience.
+
+## Features
+
+### Command Management
+
+- **Hide Commands**: Control which commands appear in tab completion
+- **Unregister Commands**: Completely remove commands from the server
+
+### Permission Control
+
+- **Override Permissions**: Set custom permissions on any command
+- **Query Permissions**: Check current permission settings
+- **Add Security**: Restrict commands that originally had no permissions
+
+### Configuration
+
+- **JSON Configuration**: Simple, human-readable configuration files
+- **Hot Reload**: Apply changes without server restart
+- **Manual Editing**: Direct configuration file access
+
+## Quick Start
+
+### Basic Usage
+
+The main command of Commander is `/command` (or `/commandv` on the proxy),  
+and requires the permission `commander.admin`:
+
+```
+<gray># Hide commands from players</gray>
+/command hide <aqua>plugins</aqua>
+/command hide <aqua>pl</aqua>
+
+<gray># Add permissions to unrestricted commands</gray>
+/command permission set <aqua>luckperms</aqua> <yellow>luckperms.use</yellow>
+
+<gray># Remove dangerous commands entirely</gray>
+/command unregister <aqua>op</aqua>
+/command unregister <aqua>deop</aqua>
+
+<gray># Save your changes (not required)</gray>
+/command save
+```
+
+### Common Scenarios
+
+#### Clean Command List
+
+Hide administrative commands from regular players:
+```
+/command hide <aqua>plugins</aqua>
+/command hide <aqua>version</aqua>
+```
+
+#### Security Hardening
+
+Remove dangerous commands:
+```
+/command unregister <aqua>op</aqua>
+/command unregister <aqua>deop</aqua>
+```
+
+#### Plugin Integration
+
+Add permissions to plugin commands that lack them:
+```
+/command permission set <aqua>luckperms</aqua> <yellow>luckperms.use</yellow>
+/command permission set <aqua>eco</aqua> <yellow>economy.admin</yellow>
+```
+
+## Permission System
+
+### Required Permissions
+
+- `commander.admin` - Access to all Commander commands
+- `commander.bypass` - See hidden commands (wildcard permissions ignored)
+
+### Permission Override
+
+Commander can override permissions on (almost) any command, even those from other plugins.  
+This allows you to:
+- Add permissions to unrestricted commands
+- Change existing permissions
+- Create world-specific or group-specific command access
+
+## Wildcard Support
+
+Commander supports powerful wildcard patterns for bulk operations on commands:
+
+### Wildcard Patterns
+
+- `*` - Matches any command name
+- `*:*` - Matches any namespaced command (commands with colons)
+- `prefix:*` - Matches all commands with a specific namespace prefix
+- `*suffix` - Matches all commands ending with a specific suffix
+
+<Callout type="warning">
+  Wildcard operations affect many commands at once.  
+  Test carefully and consider using `/command save` before bulk operations.  
+  _To restore from a saved configuration, use `/command reload`._
+</Callout>
+
+## Configuration Files
+
+Commander stores settings in three JSON files:
+
+- **`hidden-commands.json`** - List of hidden commands
+- **`unregistered-commands.json`** - List of unregistered commands
+- **`permission-overrides.json`** - Command permission overrides
+
+## Use Cases
+
+- Clean up command clutter for players
+- Remove dangerous commands like `/op` and `/deop`
+- Add security layers to plugin commands
+- Create context-specific command access
diff --git a/content/docs/commander/meta.json b/content/docs/commander/meta.json
index 63a2148..5fa375f 100644
--- a/content/docs/commander/meta.json
+++ b/content/docs/commander/meta.json
@@ -13,6 +13,11 @@
     "index",
     "faq",
     "---Guide---",
+    "hide-reveal",
+    "unregister-register",
+    "permissions",
+    "reset",
+    "reload-save",
     "---For Developers---",
     "api/repository",
     "api/index"
diff --git a/content/docs/commander/permissions.mdx b/content/docs/commander/permissions.mdx
new file mode 100644
index 0000000..628e1d5
--- /dev/null
+++ b/content/docs/commander/permissions.mdx
@@ -0,0 +1,171 @@
+---
+title: Managing Permissions
+description: Manage and override command permissions
+---
+
+# Managing Permissions
+
+Command permission management allows you to override the default permissions of commands,
+set new permissions on commands that originally had none, and query current permission settings.
+
+## Commands
+
+### Set Command Permission
+Usage: `/command permission set <command> <permission>`  
+Sets or overrides the permission required to execute a command.
+
+**Examples:**
+```
+<gray># Set permission on specific commands</gray>
+/command permission set <aqua>luckperms</aqua> <yellow>luckperms.use</yellow>
+/command permission set <aqua>fly</aqua> <yellow>essentials.fly</yellow>
+/command permission set <aqua>gamemode</aqua> <yellow>server.admin.gamemode</yellow>
+
+<gray># Set permission on all commands</gray>
+/command permission set <aqua>"*"</aqua> <yellow>server.admin.all</yellow>
+
+<gray># Set permission on all bukkit namespaced commands</gray>
+/command permission set <aqua>"bukkit:*"</aqua> <yellow>server.admin.bukkit</yellow>
+
+<gray># Set permission on all namespaced commands</gray>
+/command permission set <aqua>"*:*"</aqua> <yellow>plugin.commands</yellow>
+```
+
+### Query Command Permission
+
+Usage: `/command permission query <command>`  
+Displays the current permission setting for a command.
+
+**Examples:**
+```
+<gray># Query specific commands</gray>
+/command permission query <aqua>luckperms</aqua>
+/command permission query <aqua>fly</aqua>
+
+<gray># Query all commands</gray>
+/command permission query <aqua>"*"</aqua>
+
+<gray># Query all bukkit namespaced commands</gray>
+/command permission query <aqua>"bukkit:*"</aqua>
+
+<gray># Query all namespaced commands</gray>
+/command permission query <aqua>"*:*"</aqua>
+```
+
+### Reset Command Permission
+Usage: `/command permission reset <command>`  
+Removes any permission override and restores the command's original permission.
+
+**Examples:**
+```
+<gray># Reset specific commands</gray>
+/command permission reset <aqua>luckperms</aqua>
+/command permission reset <aqua>fly</aqua>
+
+<gray># Reset all permission overrides</gray>
+/command permission reset <aqua>"*"</aqua>
+
+<gray># Reset all bukkit namespaced commands</gray>
+/command permission reset <aqua>"bukkit:*"</aqua>
+
+<gray># Reset all namespaced commands</gray>
+/command permission reset <aqua>"*:*"</aqua>
+```
+
+### Unset Command Permission
+
+Usage: `/command permission unset <command>`  
+Removes the permission requirement from a command, making it usable by everyone.
+
+**Examples:**
+```
+<gray># Unset permission on specific commands</gray>
+/command permission unset <aqua>help</aqua>
+/command permission unset <aqua>rules</aqua>
+
+<gray># Unset permissions on all commands</gray>
+/command permission unset <aqua>"*"</aqua>
+
+<gray># Unset permissions on all bukkit namespaced commands</gray>
+/command permission unset <aqua>"bukkit:*"</aqua>
+
+<gray># Unset permissions on all namespaced commands</gray>
+/command permission unset <aqua>"*:*"</aqua>
+```
+
+<Callout type="warning">
+  Be careful when unsetting permissions from commands that should be restricted.
+</Callout>
+
+## Use Cases
+
+### Adding Permissions to Unrestricted Commands
+
+Many plugins provide commands without permission requirements. Add security:
+
+```
+<gray># Add permission to LuckPerms commands</gray>
+/command permission set <aqua>luckperms</aqua> <yellow>luckperms.admin</yellow>
+/command permission set <aqua>perms</aqua> <yellow>luckperms.admin</yellow>
+
+<gray># Add permission to economy commands</gray>
+/command permission set <aqua>eco</aqua> <yellow>economy.admin</yellow>
+/command permission set <aqua>balance</aqua> <yellow>economy.user</yellow>
+```
+
+### Restricting Powerful Commands
+
+Add additional security layers:
+
+```
+<gray># Make gamemode command require admin permission</gray>
+/command permission set <aqua>gamemode</aqua> <yellow>server.admin.gamemode</yellow>
+
+<gray># Make world management commands require specific permissions</gray>
+/command permission set <aqua>world</aqua> <yellow>server.admin.world</yellow>
+/command permission set <aqua>mv</aqua> <yellow>server.admin.multiverse</yellow>
+```
+
+### World/Server-Specific Permissions
+
+Use permission plugins to grant command access only in certain contexts:
+
+```
+<gray># Set a permission that's only granted in creative world</gray>
+/command permission set <aqua>fly</aqua> <yellow>creative.fly</yellow>
+
+<gray># Set a permission that's only granted on specific servers</gray>
+/command permission set <aqua>tp</aqua> <yellow>hub.teleport</yellow>
+```
+
+### Debugging Permission Issues
+
+Check what permissions are actually being enforced:
+
+```
+/command permission query <aqua>fly</aqua>
+/command permission query <aqua>gamemode</aqua>
+/command permission query <aqua>home</aqua>
+```
+
+## Configuration
+
+Permission overrides are stored in a JSON configuration file.  
+The file maps command names to their permission overrides.
+
+```json
+{
+  "luckperms": "luckperms.admin",
+  "fly": "essentials.fly",
+  "gamemode": "server.admin.gamemode",
+  "eco": "economy.admin"
+}
+```
+
+## Tips
+
+- Commands are referenced without the `/` prefix in the configuration
+- Use `/command reload` to reload the configuration if manually edited
+- Use `/command save` to ensure changes are persisted to disk
+- Query permissions before making changes to understand the current state
+- Use permission plugins to grant the new permissions to specific users, groups, or worlds
\ No newline at end of file
diff --git a/content/docs/commander/reload-save.mdx b/content/docs/commander/reload-save.mdx
new file mode 100644
index 0000000..a6bfbee
--- /dev/null
+++ b/content/docs/commander/reload-save.mdx
@@ -0,0 +1,84 @@
+---
+title: Reloading/Saving Configs
+description: Manage Commander configuration files
+---
+
+# Reloading/Saving Configs
+
+Configuration management allows you to reload Commander settings from disk and manually save changes to ensure persistence.
+
+<Callout type="tip">
+  Manual editing requires proper JSON syntax.  
+  Use a JSON validator when editing configuration files manually.
+</Callout>
+
+## Commands
+
+### Reload Configuration
+
+Usage: `/command reload`  
+Reload all Commander configuration files from disk, applying any changes made manually to the configuration files.
+
+<Callout type="warning">
+  Reloading will overwrite any unsaved changes in memory.
+</Callout>
+
+### Save Configuration
+
+Usage: `/command save`  
+Manually saves all current Commander settings to the configuration files, ensuring all changes are persisted.
+
+## Configuration Files
+
+Commander uses three separate JSON configuration files to store different types of command modifications:
+
+<Callout type="warning">
+  Configuration files are case-sensitive. Use exact command names.
+</Callout>
+
+### Hidden Commands
+
+Stores commands that are hidden from tab completions.
+
+`hidden-commands.json`:
+```json
+[
+  "plugins",
+  "pl",
+  "version",
+  "ver"
+]
+```
+
+### Unregistered Commands
+
+Stores commands that are completely removed from the server.
+
+`unregistered-commands.json`:
+```json
+[
+  "op",
+  "deop",
+  "stop",
+  "reload"
+]
+```
+
+### Permission Overrides
+
+Stores custom permission settings for commands.
+
+`permission-overrides.json`:
+```json
+{
+  "luckperms": "luckperms.admin",
+  "fly": "essentials.fly",
+  "gamemode": "server.admin.gamemode"
+}
+```
+
+## Tips
+
+- Reload after manual edits to apply changes
+- Test changes in a development environment first
+- Use JSON linters/validators when editing manually
\ No newline at end of file
diff --git a/content/docs/commander/reset.mdx b/content/docs/commander/reset.mdx
new file mode 100644
index 0000000..36b3633
--- /dev/null
+++ b/content/docs/commander/reset.mdx
@@ -0,0 +1,62 @@
+---
+title: Resetting Commands
+description: Reset commands to their original state
+---
+
+# Resetting Commands
+
+The reset command allows you to completely restore a command to its original state,
+removing all Commander modifications including hiding, unregistering, and permission overrides.
+
+## Command
+
+### Reset a Command
+
+Usage: `/command reset <command>`  
+Completely resets a command to its original state, removing all modifications made by Commander.
+
+**Examples:**
+```
+<gray># Reset specific commands</gray>
+/command reset <aqua>luckperms</aqua>
+/command reset <aqua>fly</aqua>
+/command reset <aqua>plugins</aqua>
+/command reset <aqua>op</aqua>
+
+<gray># Reset ALL commands (restore everything to original state)</gray>
+/command reset <aqua>"*"</aqua>
+
+<gray># Reset all bukkit namespaced commands</gray>
+/command reset <aqua>"bukkit:*"</aqua>
+
+<gray># Reset all namespaced commands</gray>
+/command reset <aqua>"*:*"</aqua>
+```
+
+<Callout type="warning">
+  Resetting a command will remove ALL Commander modifications.  
+  If you only want to remove specific modifications, use the appropriate command instead:
+  - Use `/command reveal` to only unhide a command
+  - Use `/command register` to only restore an unregistered command
+  - Use `/command permission reset` to only remove a permission override
+</Callout>
+
+<Callout type="warning">
+  Resetting commands that were unregistered for security reasons may expose them to all players again.
+</Callout>
+
+## Configuration Changes
+
+When you reset a command, Commander will:
+
+1. Remove the command from all configuration files
+2. Update the hidden commands list
+3. Update the unregistered commands list
+4. Update the permission overrides list
+5. Apply the changes immediately
+
+## Tips
+
+- Use reset when you want to completely start over with a command
+- Consider the security implications of resetting unregistered commands
+- Test the command after resetting to ensure it works as expected
\ No newline at end of file
diff --git a/content/docs/commander/unregister-register.mdx b/content/docs/commander/unregister-register.mdx
new file mode 100644
index 0000000..f185d67
--- /dev/null
+++ b/content/docs/commander/unregister-register.mdx
@@ -0,0 +1,122 @@
+---
+title: Command Registration
+description: Completely remove or restore commands from the server
+---
+
+# Unregistering Commands
+
+Unregistering a command allows you to completely remove commands from the server.  
+Unlike hiding, unregistered commands cannot be executed by anyone.
+
+## Commands
+
+### Unregister a Command
+
+Usage: `/command unregister <command>`  
+Completely removes a command from the server.
+
+**Examples:**
+```
+<gray># Unregister specific commands</gray>
+/command unregister <aqua>op</aqua>
+/command unregister <aqua>deop</aqua>
+/command unregister <aqua>stop</aqua>
+
+<gray># Unregister all commands (use with extreme caution!)</gray>
+/command unregister <aqua>"*"</aqua>
+
+<gray># Unregister all bukkit namespaced commands</gray>
+/command unregister <aqua>"bukkit:*"</aqua>
+
+<gray># Unregister all namespaced commands</gray>
+/command unregister <aqua>"*:*"</aqua>
+```
+
+<Callout type="warning">
+  Using `/command unregister "*"` will remove **ALL** commands from the server, including `/command` itself.  
+  For this reason the fallback command `/commander:command` is exempt from unregistering.  
+  _If you messed up, you can use `/commander:command register "*"` to restore all commands._
+</Callout>
+
+### Register a Command
+
+Usage: `/command register <command>`  
+Restores a previously unregistered command, making it available again.
+
+**Examples:**
+```
+<gray># Register specific commands</gray>
+/command register <aqua>op</aqua>
+/command register <aqua>deop</aqua>
+
+<gray># Register all unregistered commands</gray>
+/command register <aqua>"*"</aqua>
+
+<gray># Register all bukkit namespaced commands</gray>
+/command register <aqua>"bukkit:*"</aqua>
+
+<gray># Register all namespaced commands</gray>
+/command register <aqua>"*:*"</aqua>
+```
+
+## Use Cases
+
+### Security Hardening
+
+Remove dangerous commands that should never be used:
+```
+/command unregister <aqua>op</aqua>
+/command unregister <aqua>deop</aqua>
+/command unregister <aqua>stop</aqua>
+/command unregister <aqua>reload</aqua>
+```
+
+### Temporary Disabling
+
+Unregister commands temporarily during events or maintenance:
+```
+/command unregister <aqua>tpa</aqua>
+/command unregister <aqua>home</aqua>
+/command unregister <aqua>warp</aqua>
+/command unregister <aqua>plotmenu</aqua>
+```
+
+### Server-Specific Commands
+
+Unregister commands that don't apply to your server type:
+```
+/command unregister <aqua>gamemode</aqua>
+/command unregister <aqua>heal</aqua>
+/command unregister <aqua>fly</aqua>
+```
+
+## Configuration
+
+Unregistered commands are stored in a JSON configuration file.  
+The file contains a simple array of command names that should be unregistered.
+
+```json
+[
+  "op",
+  "deop",
+  "stop",
+  "reload"
+]
+```
+
+## Tips
+
+- Commands are unregistered without the `/` prefix in the configuration
+- Both the main command and aliases should be unregistered if desired
+- Use `/command reload` to reload the configuration if manually edited
+- Use `/command save` to ensure changes are persisted to disk
+- Consider using command hiding instead of unregistering if you still want administrators to use the command
+
+## Difference from Hiding
+
+| Feature              | Hide                | Unregister         |
+|----------------------|---------------------|--------------------|
+| Command execution    | Still possible      | Completely removed |
+| Who can use          | Anyone who knows it | Nobody             |
+| Administrator access | Yes (with bypass)   | No                 |
+| Use case             | Clean UI            | Security/Disabling |
\ No newline at end of file