document @commandkit/legacy and @commandkit/redis

Author: notunderctrl

apps/website/docs/guide/05-official-plugins/06-commandkit-legacy.mdx

@@ -1,3 +1,71 @@
 ---
 title: '@commandkit/legacy'
 ---
+
+:::danger
+
+This plugin is not recommended as we do not plan to continue
+supporting the legacy structure. We only recommend this if you're
+trying to incrementally upgrade your application. If you prefer the
+old way, you can use v0.1.10, but please note, that version is not
+actively maintained.
+
+:::
+
+The `@commandkit/legacy` plugin enables support for legacy command and
+event handlers. This is particularly useful when migrating from an
+older version of CommandKit or another framework, as it allows you to
+incrementally upgrade your application without requiring immediate
+major changes to your existing code.
+
+## Installation
+
+```sh npm2yarn
+npm install @commandkit/legacy
+```
+
+## Usage
+
+Add the Legacy plugin to your CommandKit configuration:
+
+```js
+import { defineConfig } from 'commandkit';
+import { legacy } from '@commandkit/legacy';
+
+export default defineConfig({
+  plugins: [legacy()],
+});
+```
+
+## Features
+
+The Legacy plugin provides the following features:
+
+1. **Legacy Command Handler Support**: Enables support for older
+   command handler formats, making migration easier.
+
+2. **Legacy Event Handler Support**: Allows you to continue using your
+   existing event handler structure.
+
+3. **Legacy Validation Support**: Maintains compatibility with
+   existing validation methods.
+
+4. **Hot Module Replacement (HMR)**: The plugin automatically enables
+   HMR for legacy commands, events, and validations, improving the
+   development experience by allowing you to see changes without
+   restarting your bot.
+
+## Migration Strategy
+
+The Legacy plugin is designed as a transitional tool. While it allows
+you to continue using your existing code structure, it's recommended
+to gradually migrate your commands, events, and validators to the new
+CommandKit format over time.
+
+This approach enables you to:
+
+1. Upgrade your bot's framework immediately without breaking existing
+   functionality
+2. Incrementally refactor your code at your own pace
+3. Take advantage of new CommandKit features for new commands while
+   maintaining backward compatibility

apps/website/docs/guide/05-official-plugins/07-commandkit-redis.mdx

@@ -1,3 +1,68 @@
 ---
 title: '@commandkit/redis'
 ---
+
+The `@commandkit/redis` plugin provides a cache provider for
+CommandKit that allows you to store data in Redis. It works out of the
+box with the [`@commandkit/cache`](./03-commandkit-cache.mdx) plugin.
+
+## Installation
+
+```sh npm2yarn
+npm install @commandkit/redis
+```
+
+## Usage
+
+This plugin will automatically register the Redis cache provider with
+your CommandKit instance.
+
+```js
+import { defineConfig } from 'commandkit';
+import { redis } from '@commandkit/redis';
+
+export default defineConfig({
+  plugins: [redis()],
+});
+```
+
+Once configured, your cache functions will automatically use Redis as
+the storage backend:
+
+```ts
+async function getCachedData() {
+  'use cache'; // This directive enables caching for the function
+
+  // Your data retrieval logic
+  const data = await getFromDatabase('something');
+
+  return data;
+}
+```
+
+## Manual Configuration
+
+If you need more control over the Redis client configuration, you can
+set up the cache provider manually instead of using the plugin:
+
+```ts
+import { setCacheProvider } from '@commandkit/cache';
+import { RedisCacheProvider } from '@commandkit/redis';
+import { Redis } from 'ioredis';
+
+// Configure the Redis client with custom options
+const redis = new Redis({
+  host: 'your-redis-host',
+  port: 6379,
+  // Add other Redis options as needed
+});
+
+const redisProvider = new RedisCacheProvider(redis);
+
+// Register the provider with CommandKit
+setCacheProvider(redisProvider);
+```
+
+This approach gives you full control over the Redis client
+configuration while still integrating with CommandKit's caching
+system.