docs path thing

Author: macalinao

apps/docs/content/docs/configuration.mdx

@@ -27,15 +27,11 @@ This creates a `coda.config.mjs` file with helpful comments and examples.
 - **Default**: `"./src/generated"`
 - **Description**: Directory where generated TypeScript files will be placed
 
-### `docsPath`
-- **Type**: `string`
-- **Default**: `"./docs"`
-- **Description**: Directory where generated markdown documentation will be placed
-
 ### `docs`
-- **Type**: `{ npmPackageName?: string }`
+- **Type**: `{ path?: string, npmPackageName?: string }`
 - **Default**: `{}`
 - **Description**: Documentation-specific options
+  - `path`: Directory where generated markdown documentation will be placed (default: `"./docs"`)
   - `npmPackageName`: NPM package name to display badge and link in documentation
 
 ### `visitors`

apps/docs/content/docs/generating-docs.mdx

@@ -28,17 +28,28 @@ Documentation generation can be customized through `coda.config.mjs`. See the [C
 import { defineConfig } from "@macalinao/coda";
 
 export default defineConfig({
-  // Custom output directory for docs
-  docsPath: "./documentation",
-  
   // Documentation options
   docs: {
+    // Custom output directory for docs (default: "./docs")
+    path: "./documentation",
     // Add NPM package badge and link
     npmPackageName: "@my-org/my-solana-client",
   },
 });
 ```
 
+### Custom Output Directory
+
+To generate documentation to a different directory:
+
+```javascript
+export default defineConfig({
+  docs: {
+    path: "./my-custom-docs",
+  },
+});
+```
+
 ## NPM Package Integration
 
 If you've published a TypeScript client for your program, you can include NPM package information in your documentation:

packages/coda/src/bin/cli.ts

@@ -135,7 +135,7 @@ program
   .action(async (options: { idl: string; config: string }) => {
     try {
       const { codama, config } = await processIdls(options);
-      const outputPath = resolve(config.docsPath ?? "./docs");
+      const outputPath = resolve(config.docs?.path ?? "./docs");
 
       // Apply the markdown visitor with options from config
       console.log(`Generating documentation to ${outputPath}...`);

packages/coda/src/config.ts

@@ -34,16 +34,16 @@ export interface CodaConfig {
    */
   outputDir?: string;
 
-  /**
-   * Output directory for the generated documentation.
-   * @default "./docs"
-   */
-  docsPath?: string;
-
   /**
    * Documentation generation options.
    */
   docs?: {
+    /**
+     * Output directory for the generated documentation.
+     * @default "./docs"
+     */
+    path?: string;
+
     /**
      * NPM package name for the TypeScript client.
      * If provided, will add an NPM badge and link to the package in the generated documentation.