doccupine 0.0.89 → 0.0.91

package/dist/templates/mdx/platform/theme-settings.mdx.d.ts

@@ -1 +1 @@
-export declare const platformThemeSettingsMdxTemplate = "---\ntitle: \"Theme Settings\"\ndescription: \"Customize your documentation site's color palette, logos, and dark mode appearance.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 1\nsection: \"Platform\"\n---\n# Theme Settings\nThe Theme settings page gives you full control over your documentation site's visual appearance. Customize colors, upload logos, and configure separate light and dark mode palettes.\n\n## Color palette\nThe theme system uses an 18-color palette organized into groups:\n\n- **Primary** (light, base, dark) - your brand's main color, used for links, buttons, and accents\n- **Secondary** (light, base, dark) - complementary color for secondary elements\n- **Tertiary** (light, base, dark) - additional accent color\n- **Gray** (light, base, dark) - neutral tones for text, borders, and backgrounds\n- **Status colors** (success, error, warning, info) - used for callouts and status indicators\n- **Base colors** (dark, light) - the core background and foreground colors\n\nClick any color swatch to open a color picker and adjust the value.\n\n## Dark mode\nEnable the dark mode toggle to configure a separate palette for dark mode. When enabled, your site automatically switches based on the visitor's system preference.\n\nThe dark mode palette uses the same 18-color structure, letting you fine-tune every color for both appearances.\n\n## Logos\nUpload separate logo images for light and dark backgrounds:\n\n- **Light background logo** - shown when the site is in light mode\n- **Dark background logo** - shown when the site is in dark mode\n\n<Callout type=\"note\">\n  If you only upload one logo, it will be used for both modes.\n</Callout>\n\n## Reset to defaults\nEach palette section has a **Reset to defaults** button that restores the original Doccupine color values. This is useful if you want to start over after experimenting.\n\n## How it works\nTheme settings are stored in `theme.json` at the root of your repository. Like all configuration, changes are staged as pending and go live when you publish.";
+export declare const platformThemeSettingsMdxTemplate = "---\ntitle: \"Theme Settings\"\ndescription: \"Customize your documentation site's color palette, logos, and dark mode appearance.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 1\nsection: \"Platform\"\n---\n\n# Theme Settings\n\nThe Theme settings page gives you full control over your documentation site's visual appearance. Customize colors, upload logos, and configure separate light and dark mode palettes.\n\n## Color palette\n\nThe theme system uses an 18-color palette organized into groups:\n\n- **Primary** (light, base, dark) - your brand's main color, used for links, buttons, and accents\n- **Secondary** (light, base, dark) - complementary color for secondary elements\n- **Tertiary** (light, base, dark) - additional accent color\n- **Gray** (light, base, dark) - neutral tones for text, borders, and backgrounds\n- **Status colors** (success, error, warning, info) - used for callouts and status indicators\n- **Base colors** (dark, light) - the core background and foreground colors\n\nClick any color swatch to open a color picker and adjust the value.\n\n## Dark mode\n\nEnable the dark mode toggle to configure a separate palette for dark mode. When enabled, your site automatically switches based on the visitor's system preference.\n\nThe dark mode palette uses the same 18-color structure, letting you fine-tune every color for both appearances.\n\n## Logos\n\nUpload separate logo images for light and dark backgrounds:\n\n- **Light background logo** - shown when the site is in light mode\n- **Dark background logo** - shown when the site is in dark mode\n\n<Callout type=\"note\">\n  If you only upload one logo, it will be used for both modes.\n</Callout>\n\n## Reset to defaults\n\nEach palette section has a **Reset to defaults** button that restores the original Doccupine color values. This is useful if you want to start over after experimenting.\n\n## How it works\n\nTheme settings are stored in `theme.json` at the root of your repository. Like all configuration, changes are staged as pending and go live when you publish.";

package/dist/templates/mdx/platform/theme-settings.mdx.js

@@ -7,10 +7,13 @@ categoryOrder: 2
 order: 1
 section: "Platform"
 ---
+
 # Theme Settings
+
 The Theme settings page gives you full control over your documentation site's visual appearance. Customize colors, upload logos, and configure separate light and dark mode palettes.
 
 ## Color palette
+
 The theme system uses an 18-color palette organized into groups:
 
 - **Primary** (light, base, dark) - your brand's main color, used for links, buttons, and accents
@@ -23,11 +26,13 @@ The theme system uses an 18-color palette organized into groups:
 Click any color swatch to open a color picker and adjust the value.
 
 ## Dark mode
+
 Enable the dark mode toggle to configure a separate palette for dark mode. When enabled, your site automatically switches based on the visitor's system preference.
 
 The dark mode palette uses the same 18-color structure, letting you fine-tune every color for both appearances.
 
 ## Logos
+
 Upload separate logo images for light and dark backgrounds:
 
 - **Light background logo** - shown when the site is in light mode
@@ -38,7 +43,9 @@ Upload separate logo images for light and dark backgrounds:
 </Callout>
 
 ## Reset to defaults
+
 Each palette section has a **Reset to defaults** button that restores the original Doccupine color values. This is useful if you want to start over after experimenting.
 
 ## How it works
+
 Theme settings are stored in \`theme.json\` at the root of your repository. Like all configuration, changes are staged as pending and go live when you publish.`;

package/dist/templates/mdx/sections.mdx.d.ts

@@ -1 +1 @@
-export declare const sectionsMdxTemplate = "---\ntitle: \"Sections\"\ndescription: \"Split your documentation into top-level sections with independent sidebars.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 3\n---\n# Sections\nSections let you divide your documentation into separate top-level areas - for example \"Guides\", \"API Reference\", and \"SDKs\". Each section gets its own sidebar and appears as a horizontal tab bar below the site header.\n\n<Callout type=\"note\">\n  Sections are entirely opt-in. If you don't configure them, nothing changes - your site works exactly as before with a single flat navigation.\n</Callout>\n\n## Automatic sections (frontmatter)\nThe simplest way to add sections is through page frontmatter. Add a `section` field to group pages, and an optional `sectionOrder` to control the order of sections in the bar.\n\n### Frontmatter fields\n- **section**: The display name for the section this page belongs to (e.g. \"API Reference\").\n- **sectionOrder**: Controls the position of the section in the bar. Lower numbers appear first.\n\nThe section slug is derived automatically from the label - lowercased with spaces replaced by hyphens. So \"API Reference\" becomes `api-reference`.\n\nPages without a `section` field stay at the root URL and appear under a default tab labeled \"Docs\". You can rename this tab with the `sectionLabel` field on your `index.mdx`:\n\n```text\n---\ntitle: \"Welcome\"\nsectionLabel: \"Guides\"\n---\n```\n\n### Directory-based organization\nYou can organize each section's files in a subdirectory that matches the section slug. When the directory name matches, Doccupine automatically assigns the files to that section and strips the directory from the URL.\n\n```text\ndocs/\n  index.mdx\n  getting-started.mdx\n  platform/\n    index.mdx        -> /platform\n    auth.mdx         -> /platform/auth\n```\n\nWhere `platform/index.mdx` has:\n\n```text\n---\ntitle: \"Platform Overview\"\nsection: \"Platform\"\nsectionOrder: 1\ncategory: \"Getting Started\"\n---\n```\n\nThe directory `platform/` matches the section slug `platform`, so it is stripped. `platform/index.mdx` serves at `/platform/` and `platform/auth.mdx` serves at `/platform/auth`.\n\n<Callout type=\"info\">\n  Once a section exists, any file placed in a matching directory is automatically assigned to it - even without a `section` field in its own frontmatter. Only the first file needs `section` and `sectionOrder` to create the section. After that, the directory does the work.\n</Callout>\n\nFiles at the root level with a `section` field work too - they keep their full slug under the section prefix.\n\n### Section index pages\nIf a section has no index page (no file at its root URL), Doccupine generates a redirect to the first page in that section, sorted by `categoryOrder` then `order`.\n\n<Callout type=\"note\">\n  You can override the auto-redirect by creating an `index.mdx` in the section's directory.\n</Callout>\n\n### Flat file example\nYou can also keep all files at the root and rely purely on frontmatter:\n\n```text\n---\ntitle: \"Authentication\"\nsection: \"API Reference\"\nsectionOrder: 2\ncategory: \"Auth\"\ncategoryOrder: 1\norder: 1\n---\n```\n\nThis page would be served at `/api-reference/authentication`.\n\n## Explicit sections with sections.json\nFor full control over slugs, create a `sections.json` file at your project root (the same folder where you run `npx doccupine`).\n\n### Minimal example\n\n```json\n[\n  { \"label\": \"Docs\", \"slug\": \"\" },\n  { \"label\": \"Platform\", \"slug\": \"platform\" }\n]\n```\n\nThis defines two sections. Pages are assigned automatically:\n- Files in a `platform/` directory belong to the \"Platform\" section (directory name matches slug).\n- Files with `section: \"Platform\"` in their frontmatter also belong to it.\n- Everything else stays in the root \"Docs\" section.\n\nNo `directory` field is needed when the directory name already matches the section slug.\n\n### Example with explicit directories\nWhen the directory name differs from the slug, use the `directory` field to map them:\n\n```json\n[\n  { \"label\": \"Guides\", \"slug\": \"\", \"directory\": \"guides\" },\n  { \"label\": \"API Reference\", \"slug\": \"api\", \"directory\": \"api-reference\" },\n  { \"label\": \"SDKs\", \"slug\": \"sdks\", \"directory\": \"sdks\" }\n]\n```\n\n### Fields\n- **label**: The display name shown in the section bar.\n- **slug**: The URL prefix for this section. Use an empty string `\"\"` for the default section that serves at the root.\n- **directory** (optional): The subdirectory under your watch directory that contains this section's MDX files. Only needed when the directory name differs from the slug.\n\n### Directory structure example\nWith the explicit directory config above and a watch directory of `docs`, your files would look like:\n\n```text\ndocs/\n  guides/\n    index.mdx\n    getting-started.mdx\n  api-reference/\n    authentication.mdx\n    endpoints.mdx\n  sdks/\n    javascript.mdx\n    python.mdx\n```\n\n## Section navigation\nEach section builds its own sidebar from the pages that belong to it. By default, pages are grouped by `category` and sorted by `categoryOrder` and `order` from frontmatter.\n\nFor explicit control, use `navigation.json` with the object format to define per-section navigation:\n\n```json\n{\n  \"\": [\n    { \"label\": \"General\", \"links\": [{ \"slug\": \"\", \"title\": \"Getting Started\" }] }\n  ],\n  \"platform\": [\n    { \"label\": \"API\", \"links\": [{ \"slug\": \"platform/auth\", \"title\": \"Auth\" }] }\n  ]\n}\n```\n\nKeys are section slugs. The root section uses `\"\"`. Sections without a key fall back to auto-generated navigation. See the Navigation page for the full format.\n\n## How pages are assigned to sections\nDoccupine checks these rules in order and uses the first match:\n\n1. **Explicit directory** - the file is inside a directory listed in a section's `directory` field.\n2. **Directory matches slug** - the file's parent directory matches a section slug (e.g. files in `platform/` match a section with `slug: \"platform\"`).\n3. **Frontmatter section field** - the file's `section` value matches a section label.\n4. **No match** - the page stays at the root.\n\n## Precedence for section discovery\n1. **sections.json exists** - Doccupine uses it to define available sections.\n2. **No sections.json but pages have `section` frontmatter** - Doccupine auto-discovers sections from the frontmatter. Sections update live as you add or remove the `section` field from files.\n3. **Neither** - No section bar appears. The site works exactly as before.\n\n## URL structure\nPages in the default section (with `slug: \"\"`) serve at the root:\n\n- Default section: `/getting-started`, `/installation`\n- Other sections: `/api/authentication`, `/sdks/javascript`\n\n<Callout type=\"info\">\n  When a file is in a directory that matches its section slug, the directory is stripped so it doesn't appear twice. For example, `platform/auth.mdx` in the \"Platform\" section serves at `/platform/auth`, not `/platform/platform/auth`.\n</Callout>\n\n## sections.json vs navigation.json\nThese two config files serve different purposes and complement each other:\n\n- **sections.json** defines which sections exist - their labels, slugs, directory mappings, and order in the tab bar.\n- **navigation.json** controls the sidebar within each section - page ordering and grouping.\n\nYou can use either one independently. `sections.json` without `navigation.json` gives you sections with auto-generated sidebars. `navigation.json` without `sections.json` gives you custom sidebar ordering with frontmatter-discovered sections (or no sections at all).\n\n## Tips\n- **Start simple**: Add `section` and `sectionOrder` to a few pages to try it out. No config files needed.\n- **Use directories**: Organize each section's files in a directory that matches the section slug for clean URLs and a tidy file tree.\n- **Rename the default tab**: Add `sectionLabel: \"Your Label\"` to your `index.mdx` frontmatter. Defaults to \"Docs\" if omitted.\n- **Switch to sections.json**: When you need custom slugs or directory mappings that don't match section names, `sections.json` gives full control.\n- **Per-section navigation**: Use the object format in `navigation.json` to define custom sidebar ordering for specific sections.\n- **Independent sidebars**: Each section has its own sidebar. Previous/next navigation stays within the active section.";
+export declare const sectionsMdxTemplate = "---\ntitle: \"Sections\"\ndescription: \"Split your documentation into top-level sections with independent sidebars.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 3\n---\n\n# Sections\n\nSections let you divide your documentation into separate top-level areas - for example \"Guides\", \"API Reference\", and \"SDKs\". Each section gets its own sidebar and appears as a horizontal tab bar below the site header.\n\n<Callout type=\"note\">\n  Sections are entirely opt-in. If you don't configure them, nothing changes - your site works exactly as before with a single flat navigation.\n</Callout>\n\n## Automatic sections (frontmatter)\n\nThe simplest way to add sections is through page frontmatter. Add a `section` field to group pages, and an optional `sectionOrder` to control the order of sections in the bar.\n\n### Frontmatter fields\n\n- **section**: The display name for the section this page belongs to (e.g. \"API Reference\").\n- **sectionOrder**: Controls the position of the section in the bar. Lower numbers appear first.\n\nThe section slug is derived automatically from the label - lowercased with spaces replaced by hyphens. So \"API Reference\" becomes `api-reference`.\n\nPages without a `section` field stay at the root URL and appear under a default tab labeled \"Docs\". You can rename this tab with the `sectionLabel` field on your `index.mdx`:\n\n```text\n---\ntitle: \"Welcome\"\nsectionLabel: \"Guides\"\n---\n```\n\n### Directory-based organization\n\nYou can organize each section's files in a subdirectory that matches the section slug. When the directory name matches, Doccupine automatically assigns the files to that section and strips the directory from the URL.\n\n```text\ndocs/\n  index.mdx\n  getting-started.mdx\n  platform/\n    index.mdx        -> /platform\n    auth.mdx         -> /platform/auth\n```\n\nWhere `platform/index.mdx` has:\n\n```text\n---\ntitle: \"Platform Overview\"\nsection: \"Platform\"\nsectionOrder: 1\ncategory: \"Getting Started\"\n---\n```\n\nThe directory `platform/` matches the section slug `platform`, so it is stripped. `platform/index.mdx` serves at `/platform/` and `platform/auth.mdx` serves at `/platform/auth`.\n\n<Callout type=\"info\">\n  Once a section exists, any file placed in a matching directory is automatically assigned to it - even without a `section` field in its own frontmatter. Only the first file needs `section` and `sectionOrder` to create the section. After that, the directory does the work.\n</Callout>\n\nFiles at the root level with a `section` field work too - they keep their full slug under the section prefix.\n\n### Section index pages\n\nIf a section has no index page (no file at its root URL), Doccupine generates a redirect to the first page in that section, sorted by `categoryOrder` then `order`.\n\n<Callout type=\"note\">\n  You can override the auto-redirect by creating an `index.mdx` in the section's directory.\n</Callout>\n\n### Flat file example\n\nYou can also keep all files at the root and rely purely on frontmatter:\n\n```text\n---\ntitle: \"Authentication\"\nsection: \"API Reference\"\nsectionOrder: 2\ncategory: \"Auth\"\ncategoryOrder: 1\norder: 1\n---\n```\n\nThis page would be served at `/api-reference/authentication`.\n\n## Explicit sections with sections.json\n\nFor full control over slugs, create a `sections.json` file at your project root (the same folder where you run `npx doccupine`).\n\n### Minimal example\n\n```json\n[\n  { \"label\": \"Docs\", \"slug\": \"\" },\n  { \"label\": \"Platform\", \"slug\": \"platform\" }\n]\n```\n\nThis defines two sections. Pages are assigned automatically:\n\n- Files in a `platform/` directory belong to the \"Platform\" section (directory name matches slug).\n- Files with `section: \"Platform\"` in their frontmatter also belong to it.\n- Everything else stays in the root \"Docs\" section.\n\nNo `directory` field is needed when the directory name already matches the section slug.\n\n### Example with explicit directories\n\nWhen the directory name differs from the slug, use the `directory` field to map them:\n\n```json\n[\n  { \"label\": \"Guides\", \"slug\": \"\", \"directory\": \"guides\" },\n  { \"label\": \"API Reference\", \"slug\": \"api\", \"directory\": \"api-reference\" },\n  { \"label\": \"SDKs\", \"slug\": \"sdks\", \"directory\": \"sdks\" }\n]\n```\n\n### Fields\n\n- **label**: The display name shown in the section bar.\n- **slug**: The URL prefix for this section. Use an empty string `\"\"` for the default section that serves at the root.\n- **directory** (optional): The subdirectory under your watch directory that contains this section's MDX files. Only needed when the directory name differs from the slug.\n\n### Directory structure example\n\nWith the explicit directory config above and a watch directory of `docs`, your files would look like:\n\n```text\ndocs/\n  guides/\n    index.mdx\n    getting-started.mdx\n  api-reference/\n    authentication.mdx\n    endpoints.mdx\n  sdks/\n    javascript.mdx\n    python.mdx\n```\n\n## Section navigation\n\nEach section builds its own sidebar from the pages that belong to it. By default, pages are grouped by `category` and sorted by `categoryOrder` and `order` from frontmatter.\n\nFor explicit control, use `navigation.json` with the object format to define per-section navigation:\n\n```json\n{\n  \"\": [\n    {\n      \"label\": \"General\",\n      \"links\": [{ \"slug\": \"\", \"title\": \"Getting Started\" }]\n    }\n  ],\n  \"platform\": [\n    { \"label\": \"API\", \"links\": [{ \"slug\": \"platform/auth\", \"title\": \"Auth\" }] }\n  ]\n}\n```\n\nKeys are section slugs. The root section uses `\"\"`. Sections without a key fall back to auto-generated navigation. See the Navigation page for the full format.\n\n## How pages are assigned to sections\n\nDoccupine checks these rules in order and uses the first match:\n\n1. **Explicit directory** - the file is inside a directory listed in a section's `directory` field.\n2. **Directory matches slug** - the file's parent directory matches a section slug (e.g. files in `platform/` match a section with `slug: \"platform\"`).\n3. **Frontmatter section field** - the file's `section` value matches a section label.\n4. **No match** - the page stays at the root.\n\n## Precedence for section discovery\n\n1. **sections.json exists** - Doccupine uses it to define available sections.\n2. **No sections.json but pages have `section` frontmatter** - Doccupine auto-discovers sections from the frontmatter. Sections update live as you add or remove the `section` field from files.\n3. **Neither** - No section bar appears. The site works exactly as before.\n\n## URL structure\n\nPages in the default section (with `slug: \"\"`) serve at the root:\n\n- Default section: `/getting-started`, `/installation`\n- Other sections: `/api/authentication`, `/sdks/javascript`\n\n<Callout type=\"info\">\n  When a file is in a directory that matches its section slug, the directory is stripped so it doesn't appear twice. For example, `platform/auth.mdx` in the \"Platform\" section serves at `/platform/auth`, not `/platform/platform/auth`.\n</Callout>\n\n## sections.json vs navigation.json\n\nThese two config files serve different purposes and complement each other:\n\n- **sections.json** defines which sections exist - their labels, slugs, directory mappings, and order in the tab bar.\n- **navigation.json** controls the sidebar within each section - page ordering and grouping.\n\nYou can use either one independently. `sections.json` without `navigation.json` gives you sections with auto-generated sidebars. `navigation.json` without `sections.json` gives you custom sidebar ordering with frontmatter-discovered sections (or no sections at all).\n\n## Tips\n\n- **Start simple**: Add `section` and `sectionOrder` to a few pages to try it out. No config files needed.\n- **Use directories**: Organize each section's files in a directory that matches the section slug for clean URLs and a tidy file tree.\n- **Rename the default tab**: Add `sectionLabel: \"Your Label\"` to your `index.mdx` frontmatter. Defaults to \"Docs\" if omitted.\n- **Switch to sections.json**: When you need custom slugs or directory mappings that don't match section names, `sections.json` gives full control.\n- **Per-section navigation**: Use the object format in `navigation.json` to define custom sidebar ordering for specific sections.\n- **Independent sidebars**: Each section has its own sidebar. Previous/next navigation stays within the active section.";

package/dist/templates/mdx/sections.mdx.js

@@ -6,7 +6,9 @@ category: "Configuration"
 categoryOrder: 3
 order: 3
 ---
+
 # Sections
+
 Sections let you divide your documentation into separate top-level areas - for example "Guides", "API Reference", and "SDKs". Each section gets its own sidebar and appears as a horizontal tab bar below the site header.
 
 <Callout type="note">
@@ -14,9 +16,11 @@ Sections let you divide your documentation into separate top-level areas - for e
 </Callout>
 
 ## Automatic sections (frontmatter)
+
 The simplest way to add sections is through page frontmatter. Add a \`section\` field to group pages, and an optional \`sectionOrder\` to control the order of sections in the bar.
 
 ### Frontmatter fields
+
 - **section**: The display name for the section this page belongs to (e.g. "API Reference").
 - **sectionOrder**: Controls the position of the section in the bar. Lower numbers appear first.
 
@@ -32,6 +36,7 @@ sectionLabel: "Guides"
 \`\`\`
 
 ### Directory-based organization
+
 You can organize each section's files in a subdirectory that matches the section slug. When the directory name matches, Doccupine automatically assigns the files to that section and strips the directory from the URL.
 
 \`\`\`text
@@ -63,6 +68,7 @@ The directory \`platform/\` matches the section slug \`platform\`, so it is stri
 Files at the root level with a \`section\` field work too - they keep their full slug under the section prefix.
 
 ### Section index pages
+
 If a section has no index page (no file at its root URL), Doccupine generates a redirect to the first page in that section, sorted by \`categoryOrder\` then \`order\`.
 
 <Callout type="note">
@@ -70,6 +76,7 @@ If a section has no index page (no file at its root URL), Doccupine generates a
 </Callout>
 
 ### Flat file example
+
 You can also keep all files at the root and rely purely on frontmatter:
 
 \`\`\`text
@@ -86,6 +93,7 @@ order: 1
 This page would be served at \`/api-reference/authentication\`.
 
 ## Explicit sections with sections.json
+
 For full control over slugs, create a \`sections.json\` file at your project root (the same folder where you run \`npx doccupine\`).
 
 ### Minimal example
@@ -98,6 +106,7 @@ For full control over slugs, create a \`sections.json\` file at your project roo
 \`\`\`
 
 This defines two sections. Pages are assigned automatically:
+
 - Files in a \`platform/\` directory belong to the "Platform" section (directory name matches slug).
 - Files with \`section: "Platform"\` in their frontmatter also belong to it.
 - Everything else stays in the root "Docs" section.
@@ -105,6 +114,7 @@ This defines two sections. Pages are assigned automatically:
 No \`directory\` field is needed when the directory name already matches the section slug.
 
 ### Example with explicit directories
+
 When the directory name differs from the slug, use the \`directory\` field to map them:
 
 \`\`\`json
@@ -116,11 +126,13 @@ When the directory name differs from the slug, use the \`directory\` field to ma
 \`\`\`
 
 ### Fields
+
 - **label**: The display name shown in the section bar.
 - **slug**: The URL prefix for this section. Use an empty string \`""\` for the default section that serves at the root.
 - **directory** (optional): The subdirectory under your watch directory that contains this section's MDX files. Only needed when the directory name differs from the slug.
 
 ### Directory structure example
+
 With the explicit directory config above and a watch directory of \`docs\`, your files would look like:
 
 \`\`\`text
@@ -137,6 +149,7 @@ docs/
 \`\`\`
 
 ## Section navigation
+
 Each section builds its own sidebar from the pages that belong to it. By default, pages are grouped by \`category\` and sorted by \`categoryOrder\` and \`order\` from frontmatter.
 
 For explicit control, use \`navigation.json\` with the object format to define per-section navigation:
@@ -144,7 +157,10 @@ For explicit control, use \`navigation.json\` with the object format to define p
 \`\`\`json
 {
   "": [
-    { "label": "General", "links": [{ "slug": "", "title": "Getting Started" }] }
+    {
+      "label": "General",
+      "links": [{ "slug": "", "title": "Getting Started" }]
+    }
   ],
   "platform": [
     { "label": "API", "links": [{ "slug": "platform/auth", "title": "Auth" }] }
@@ -155,6 +171,7 @@ For explicit control, use \`navigation.json\` with the object format to define p
 Keys are section slugs. The root section uses \`""\`. Sections without a key fall back to auto-generated navigation. See the Navigation page for the full format.
 
 ## How pages are assigned to sections
+
 Doccupine checks these rules in order and uses the first match:
 
 1. **Explicit directory** - the file is inside a directory listed in a section's \`directory\` field.
@@ -163,11 +180,13 @@ Doccupine checks these rules in order and uses the first match:
 4. **No match** - the page stays at the root.
 
 ## Precedence for section discovery
+
 1. **sections.json exists** - Doccupine uses it to define available sections.
 2. **No sections.json but pages have \`section\` frontmatter** - Doccupine auto-discovers sections from the frontmatter. Sections update live as you add or remove the \`section\` field from files.
 3. **Neither** - No section bar appears. The site works exactly as before.
 
 ## URL structure
+
 Pages in the default section (with \`slug: ""\`) serve at the root:
 
 - Default section: \`/getting-started\`, \`/installation\`
@@ -178,6 +197,7 @@ Pages in the default section (with \`slug: ""\`) serve at the root:
 </Callout>
 
 ## sections.json vs navigation.json
+
 These two config files serve different purposes and complement each other:
 
 - **sections.json** defines which sections exist - their labels, slugs, directory mappings, and order in the tab bar.
@@ -186,6 +206,7 @@ These two config files serve different purposes and complement each other:
 You can use either one independently. \`sections.json\` without \`navigation.json\` gives you sections with auto-generated sidebars. \`navigation.json\` without \`sections.json\` gives you custom sidebar ordering with frontmatter-discovered sections (or no sections at all).
 
 ## Tips
+
 - **Start simple**: Add \`section\` and \`sectionOrder\` to a few pages to try it out. No config files needed.
 - **Use directories**: Organize each section's files in a directory that matches the section slug for clean URLs and a tidy file tree.
 - **Rename the default tab**: Add \`sectionLabel: "Your Label"\` to your \`index.mdx\` frontmatter. Defaults to "Docs" if omitted.

package/dist/templates/mdx/steps.mdx.d.ts

@@ -1 +1 @@
-export declare const stepsMdxTemplate = "---\ntitle: \"Steps\"\ndescription: \"Guide readers step-by-step using the Steps component.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 14\n---\n# Steps\nGuide readers step-by-step using the Steps component.\n\nThe Steps component is perfect for organizing procedures or workflows in a clear sequence. Include as many individual steps as necessary to outline your process.\n\n## Steps Usage\nYou can use the `Steps` component to create a step-by-step guide. Each step is represented by a `Step` component, which includes a title and content.\n\n```mdx\n<Steps>\n  <Step title=\"Step 1\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 2\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 3\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n</Steps>\n```\n\n<Steps>\n  <Step title=\"Step 1\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 2\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 3\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n</Steps>\n\n## Properties\n\n<Field value=\"title\" type=\"string\" required>\n  The title of the step.\n</Field>\n\n<Field value=\"icon\" type=\"string\">\n  A [Lucide](https://lucide.dev/icons) icon name shown next to the step title.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the step.\n</Field>\n";
+export declare const stepsMdxTemplate = "---\ntitle: \"Steps\"\ndescription: \"Guide readers step-by-step using the Steps component.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 14\n---\n\n# Steps\n\nGuide readers step-by-step using the Steps component.\n\nThe Steps component is perfect for organizing procedures or workflows in a clear sequence. Include as many individual steps as necessary to outline your process.\n\n## Steps Usage\n\nYou can use the `Steps` component to create a step-by-step guide. Each step is represented by a `Step` component, which includes a title and content.\n\n```mdx\n<Steps>\n  <Step title=\"Step 1\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n<Step title=\"Step 2\">\n  Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n</Step>\n\n  <Step title=\"Step 3\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n</Steps>\n```\n\n<Steps>\n  <Step title=\"Step 1\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 2\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n\n  <Step title=\"Step 3\">\n    Lorem ipsum dolor sit amet, consectetur adipiscing elit.\n  </Step>\n</Steps>\n\n## Properties\n\n<Field value=\"title\" type=\"string\" required>\n  The title of the step.\n</Field>\n\n<Field value=\"icon\" type=\"string\">\n  A [Lucide](https://lucide.dev/icons) icon name shown next to the step title.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the step.\n</Field>";

package/dist/templates/mdx/steps.mdx.js

@@ -6,12 +6,15 @@ category: "Components"
 categoryOrder: 1
 order: 14
 ---
+
 # Steps
+
 Guide readers step-by-step using the Steps component.
 
 The Steps component is perfect for organizing procedures or workflows in a clear sequence. Include as many individual steps as necessary to outline your process.
 
 ## Steps Usage
+
 You can use the \`Steps\` component to create a step-by-step guide. Each step is represented by a \`Step\` component, which includes a title and content.
 
 \`\`\`mdx
@@ -20,9 +23,9 @@ You can use the \`Steps\` component to create a step-by-step guide. Each step is
     Lorem ipsum dolor sit amet, consectetur adipiscing elit.
   </Step>
 
-  <Step title="Step 2">
-    Lorem ipsum dolor sit amet, consectetur adipiscing elit.
-  </Step>
+<Step title="Step 2">
+  Lorem ipsum dolor sit amet, consectetur adipiscing elit.
+</Step>
 
   <Step title="Step 3">
     Lorem ipsum dolor sit amet, consectetur adipiscing elit.
@@ -56,5 +59,4 @@ You can use the \`Steps\` component to create a step-by-step guide. Each step is
 
 <Field value="children" type="node" required>
   The content of the step.
-</Field>
-`;
+</Field>`;

package/dist/templates/mdx/tabs.mdx.d.ts

@@ -1 +1 @@
-export declare const tabsMdxTemplate = "---\ntitle: \"Tabs\"\ndescription: \"Use the Tabs component to display different content sections in a switchable panel layout.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 5\n---\n# Tabs\nUse the Tabs component to display different content sections in a switchable panel layout.\n\nTabs are useful for grouping related information while keeping the interface tidy. You can create as many tabs as needed, and each one can hold other components, text, or code snippets.\n\n## Tabs Usage\nYou can use the Tabs component directly within your MDX files without any import. The following example shows a basic usage:\n\n~~~mdx\n<Tabs>\n  <TabContent title=\"First tab\">\n    \u261D\uFE0F This is the content shown only when the first tab is active.\n\n    Tabs can include all kinds of components. For example, a simple Java program:\n    ```java\n      class HelloWorld {\n          public static void main(String[] args) {\n              System.out.println(\"Hello, World!\");\n          }\n      }\n    ```\n  </TabContent>\n  <TabContent title=\"Second tab\">\n    \u270C\uFE0F Content inside this second tab is separate from the first.\n  </TabContent>\n  <TabContent title=\"Third tab\">\n    \uD83D\uDCAA This third tab contains its own unique content.\n  </TabContent>\n</Tabs>\n~~~\n\n<Tabs>\n  <TabContent title=\"First tab\">\n    \u261D\uFE0F This is the content shown only when the first tab is active.\n\n    Tabs can include all kinds of components. For example, a simple Java program:\n    ```java\n    class HelloWorld {\n        public static void main(String[] args) {\n            System.out.println(\"Hello, World!\");\n        }\n    }\n    ```\n  </TabContent>\n  <TabContent title=\"Second tab\">\n    \u270C\uFE0F Content inside this second tab is separate from the first.\n  </TabContent>\n  <TabContent title=\"Third tab\">\n    \uD83D\uDCAA This third tab contains its own unique content.\n  </TabContent>\n</Tabs>\n\n## Properties\n\n<Field value=\"title\" type=\"string\">\n  The title of the tab.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the tabs.\n</Field>";
+export declare const tabsMdxTemplate = "---\ntitle: \"Tabs\"\ndescription: \"Use the Tabs component to display different content sections in a switchable panel layout.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 5\n---\n\n# Tabs\n\nUse the Tabs component to display different content sections in a switchable panel layout.\n\nTabs are useful for grouping related information while keeping the interface tidy. You can create as many tabs as needed, and each one can hold other components, text, or code snippets.\n\n## Tabs Usage\n\nYou can use the Tabs component directly within your MDX files without any import. The following example shows a basic usage:\n\n````mdx\n<Tabs>\n  <TabContent title=\"First tab\">\n    \u261D\uFE0F This is the content shown only when the first tab is active.\n\n    Tabs can include all kinds of components. For example, a simple Java program:\n    ```java\n      class HelloWorld {\n          public static void main(String[] args) {\n              System.out.println(\"Hello, World!\");\n          }\n      }\n    ```\n\n  </TabContent>\n  <TabContent title=\"Second tab\">\n    \u270C\uFE0F Content inside this second tab is separate from the first.\n  </TabContent>\n  <TabContent title=\"Third tab\">\n    \uD83D\uDCAA This third tab contains its own unique content.\n  </TabContent>\n</Tabs>\n````\n\n<Tabs>\n  <TabContent title=\"First tab\">\n    \u261D\uFE0F This is the content shown only when the first tab is active.\n\n    Tabs can include all kinds of components. For example, a simple Java program:\n    ```java\n    class HelloWorld {\n        public static void main(String[] args) {\n            System.out.println(\"Hello, World!\");\n        }\n    }\n    ```\n\n  </TabContent>\n  <TabContent title=\"Second tab\">\n    \u270C\uFE0F Content inside this second tab is separate from the first.\n  </TabContent>\n  <TabContent title=\"Third tab\">\n    \uD83D\uDCAA This third tab contains its own unique content.\n  </TabContent>\n</Tabs>\n\n## Properties\n\n<Field value=\"title\" type=\"string\">\n  The title of the tab.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the tabs.\n</Field>";

package/dist/templates/mdx/tabs.mdx.js

@@ -6,15 +6,18 @@ category: "Components"
 categoryOrder: 1
 order: 5
 ---
+
 # Tabs
+
 Use the Tabs component to display different content sections in a switchable panel layout.
 
 Tabs are useful for grouping related information while keeping the interface tidy. You can create as many tabs as needed, and each one can hold other components, text, or code snippets.
 
 ## Tabs Usage
+
 You can use the Tabs component directly within your MDX files without any import. The following example shows a basic usage:
 
-~~~mdx
+\`\`\`\`mdx
 <Tabs>
   <TabContent title="First tab">
     ☝️ This is the content shown only when the first tab is active.
@@ -27,6 +30,7 @@ You can use the Tabs component directly within your MDX files without any import
           }
       }
     \`\`\`
+
   </TabContent>
   <TabContent title="Second tab">
     ✌️ Content inside this second tab is separate from the first.
@@ -35,7 +39,7 @@ You can use the Tabs component directly within your MDX files without any import
     💪 This third tab contains its own unique content.
   </TabContent>
 </Tabs>
-~~~
+\`\`\`\`
 
 <Tabs>
   <TabContent title="First tab">
@@ -49,6 +53,7 @@ You can use the Tabs component directly within your MDX files without any import
         }
     }
     \`\`\`
+
   </TabContent>
   <TabContent title="Second tab">
     ✌️ Content inside this second tab is separate from the first.

package/dist/templates/mdx/theme.mdx.d.ts

@@ -1 +1 @@
-export declare const themeMdxTemplate = "---\ntitle: \"Theme\"\ndescription: \"Customize the documentation UI colors with a theme.json file.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 5\n---\n# Theme\nDefine your site\u2019s color system with a `theme.json` file. This lets you tailor the look and feel of your documentation without changing content.\n\n## theme.json\nPlace a `theme.json` at your project root (the same folder where you execute `npx doccupine`). It supports multiple modes. Define a `default` mode and a `dark` mode.\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#93c5fd\",\n    \"primary\": \"#2563eb\",\n    \"primaryDark\": \"#1e40af\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#9bcaff\",\n    \"primary\": \"#1e7ae0\",\n    \"primaryDark\": \"#033d7e\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  },\n  \"logo\": {\n    \"dark\": \"https://docs.doccupine.com/logo-dark.svg\",\n    \"light\": \"https://docs.doccupine.com/logo-light.svg\"\n  }\n}\n```\n\n## Modes\n- **default**: The base color palette for your site.\n- **dark**: Dark\u2011mode palette.\n\n## Fields\n- **primaryLight**: A lighter variant of your brand color, used for subtle accents and backgrounds.\n- **primary**: The main brand color.\n- **primaryDark**: A darker variant of your brand color for emphasis and hover states.\n- **secondaryLight**: A lighter variant of your secondary color, used for subtle accents and backgrounds.\n- **secondary**: The secondary brand color used for highlights and UI accents.\n- **secondaryDark**: A darker variant of your secondary color for emphasis and hover states.\n- **tertiaryLight**: A lighter variant of your tertiary color, used for subtle accents and backgrounds.\n- **tertiary**: The tertiary accent color.\n- **tertiaryDark**: A darker variant of your tertiary color for emphasis and hover states.\n- **grayLight**: Light gray for surfaces and borders.\n- **gray**: Neutral gray for text and UI elements.\n- **grayDark**: Dark gray for headings or high\u2011contrast text.\n- **success**: Positive/confirmation color.\n- **error**: Error/destructive color.\n- **warning**: Warning/attention color.\n- **info**: Informational/highlight color.\n- **dark**: The darkest/base color (often page background in dark mode).\n- **light**: The lightest/base color (often page background in light mode).\n- **logo.light**: Path or URL to the logo used on light backgrounds. Recommended size: 164\u00D730 px.\n- **logo.dark**: Path or URL to the logo used on dark backgrounds. Recommended size: 164\u00D730 px.\n\n## Behavior\n- **Placement**: Put `theme.json` in the project root alongside `config.json`.\n- **Partial palettes**: If a key is missing in a mode, consumers may fall back to the `default` value.\n- **Logo size**: Recommended dimensions are 164px width and 30px height.\n\n<Callout type=\"warning\">\n  Use valid hex colors (e.g., `#22c55e`). Invalid color values may cause unexpected rendering.\n</Callout>\n\n## Tips\n- **Contrast**: Ensure sufficient contrast between text and backgrounds for readability.\n- **Branding**: Start with your brand\u2019s `primary` color, then derive `primaryLight` and `primaryDark`.\n- **Iterate**: Adjust colors and refresh the site to preview changes quickly.\n\n# Demo\nIn the following demos, you can see how the theme can be changed. To override the theme, create a `theme.json` file in the project root and copy paste the code below.\n\n<DemoTheme variant=\"purple\" />\n<DemoTheme variant=\"green\" />\n<DemoTheme variant=\"yellow\" />\n<DemoTheme />\n\n## Purple\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#c4b5fd\",\n    \"primary\": \"#8b5cf6\",\n    \"primaryDark\": \"#5b21b6\",\n    \"secondaryLight\": \"#86efac\",\n    \"secondary\": \"#22c55e\",\n    \"secondaryDark\": \"#15803d\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#ddd6fe\",\n    \"primary\": \"#a78bfa\",\n    \"primaryDark\": \"#7c3aed\",\n    \"secondaryLight\": \"#6ee7b7\",\n    \"secondary\": \"#10b981\",\n    \"secondaryDark\": \"#065f46\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n<DemoTheme variant=\"purple\" />\n\n## Green\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#86efac\",\n    \"primary\": \"#22c55e\",\n    \"primaryDark\": \"#15803d\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#6ee7b7\",\n    \"primary\": \"#10b981\",\n    \"primaryDark\": \"#065f46\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n<DemoTheme variant=\"green\" />\n\n## Yellow\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#fbbf24\",\n    \"primary\": \"#f59e0b\",\n    \"primaryDark\": \"#d97706\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#86efac\",\n    \"tertiary\": \"#22c55e\",\n    \"tertiaryDark\": \"#15803d\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#fed7aa\",\n    \"primary\": \"#fb923c\",\n    \"primaryDark\": \"#ea580c\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#6ee7b7\",\n    \"tertiary\": \"#10b981\",\n    \"tertiaryDark\": \"#065f46\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n\n<DemoTheme variant=\"yellow\" />";
+export declare const themeMdxTemplate = "---\ntitle: \"Theme\"\ndescription: \"Customize the documentation UI colors with a theme.json file.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 5\n---\n\n# Theme\n\nDefine your site\u2019s color system with a `theme.json` file. This lets you tailor the look and feel of your documentation without changing content.\n\n## theme.json\n\nPlace a `theme.json` at your project root (the same folder where you execute `npx doccupine`). It supports multiple modes. Define a `default` mode and a `dark` mode.\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#93c5fd\",\n    \"primary\": \"#2563eb\",\n    \"primaryDark\": \"#1e40af\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#9bcaff\",\n    \"primary\": \"#1e7ae0\",\n    \"primaryDark\": \"#033d7e\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  },\n  \"logo\": {\n    \"dark\": \"https://docs.doccupine.com/logo-dark.svg\",\n    \"light\": \"https://docs.doccupine.com/logo-light.svg\"\n  }\n}\n```\n\n## Modes\n\n- **default**: The base color palette for your site.\n- **dark**: Dark\u2011mode palette.\n\n## Fields\n\n- **primaryLight**: A lighter variant of your brand color, used for subtle accents and backgrounds.\n- **primary**: The main brand color.\n- **primaryDark**: A darker variant of your brand color for emphasis and hover states.\n- **secondaryLight**: A lighter variant of your secondary color, used for subtle accents and backgrounds.\n- **secondary**: The secondary brand color used for highlights and UI accents.\n- **secondaryDark**: A darker variant of your secondary color for emphasis and hover states.\n- **tertiaryLight**: A lighter variant of your tertiary color, used for subtle accents and backgrounds.\n- **tertiary**: The tertiary accent color.\n- **tertiaryDark**: A darker variant of your tertiary color for emphasis and hover states.\n- **grayLight**: Light gray for surfaces and borders.\n- **gray**: Neutral gray for text and UI elements.\n- **grayDark**: Dark gray for headings or high\u2011contrast text.\n- **success**: Positive/confirmation color.\n- **error**: Error/destructive color.\n- **warning**: Warning/attention color.\n- **info**: Informational/highlight color.\n- **dark**: The darkest/base color (often page background in dark mode).\n- **light**: The lightest/base color (often page background in light mode).\n- **logo.light**: Path or URL to the logo used on light backgrounds. Recommended size: 164\u00D730 px.\n- **logo.dark**: Path or URL to the logo used on dark backgrounds. Recommended size: 164\u00D730 px.\n\n## Behavior\n\n- **Placement**: Put `theme.json` in the project root alongside `config.json`.\n- **Partial palettes**: If a key is missing in a mode, consumers may fall back to the `default` value.\n- **Logo size**: Recommended dimensions are 164px width and 30px height.\n\n<Callout type=\"warning\">\n  Use valid hex colors (e.g., `#22c55e`). Invalid color values may cause unexpected rendering.\n</Callout>\n\n## Tips\n\n- **Contrast**: Ensure sufficient contrast between text and backgrounds for readability.\n- **Branding**: Start with your brand\u2019s `primary` color, then derive `primaryLight` and `primaryDark`.\n- **Iterate**: Adjust colors and refresh the site to preview changes quickly.\n\n# Demo\n\nIn the following demos, you can see how the theme can be changed. To override the theme, create a `theme.json` file in the project root and copy paste the code below.\n\n<DemoTheme variant=\"purple\" />\n<DemoTheme variant=\"green\" />\n<DemoTheme variant=\"yellow\" />\n<DemoTheme />\n\n## Purple\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#c4b5fd\",\n    \"primary\": \"#8b5cf6\",\n    \"primaryDark\": \"#5b21b6\",\n    \"secondaryLight\": \"#86efac\",\n    \"secondary\": \"#22c55e\",\n    \"secondaryDark\": \"#15803d\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#ddd6fe\",\n    \"primary\": \"#a78bfa\",\n    \"primaryDark\": \"#7c3aed\",\n    \"secondaryLight\": \"#6ee7b7\",\n    \"secondary\": \"#10b981\",\n    \"secondaryDark\": \"#065f46\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n\n<DemoTheme variant=\"purple\" />\n\n## Green\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#86efac\",\n    \"primary\": \"#22c55e\",\n    \"primaryDark\": \"#15803d\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#fbbf24\",\n    \"tertiary\": \"#f59e0b\",\n    \"tertiaryDark\": \"#d97706\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#6ee7b7\",\n    \"primary\": \"#10b981\",\n    \"primaryDark\": \"#065f46\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#fed7aa\",\n    \"tertiary\": \"#fb923c\",\n    \"tertiaryDark\": \"#ea580c\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n\n<DemoTheme variant=\"green\" />\n\n## Yellow\n\n```json\n{\n  \"default\": {\n    \"primaryLight\": \"#fbbf24\",\n    \"primary\": \"#f59e0b\",\n    \"primaryDark\": \"#d97706\",\n    \"secondaryLight\": \"#c4b5fd\",\n    \"secondary\": \"#8b5cf6\",\n    \"secondaryDark\": \"#5b21b6\",\n    \"tertiaryLight\": \"#86efac\",\n    \"tertiary\": \"#22c55e\",\n    \"tertiaryDark\": \"#15803d\",\n    \"grayLight\": \"#f3f4f6\",\n    \"gray\": \"#9ca3af\",\n    \"grayDark\": \"#374151\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#000000\",\n    \"light\": \"#ffffff\"\n  },\n  \"dark\": {\n    \"primaryLight\": \"#fed7aa\",\n    \"primary\": \"#fb923c\",\n    \"primaryDark\": \"#ea580c\",\n    \"secondaryLight\": \"#ddd6fe\",\n    \"secondary\": \"#a78bfa\",\n    \"secondaryDark\": \"#7c3aed\",\n    \"tertiaryLight\": \"#6ee7b7\",\n    \"tertiary\": \"#10b981\",\n    \"tertiaryDark\": \"#065f46\",\n    \"grayLight\": \"#1f2937\",\n    \"gray\": \"#6b7280\",\n    \"grayDark\": \"#9ca3af\",\n    \"success\": \"#10b981\",\n    \"error\": \"#f43f5e\",\n    \"warning\": \"#f59e0b\",\n    \"info\": \"#3b82f6\",\n    \"dark\": \"#ffffff\",\n    \"light\": \"#000000\"\n  }\n}\n```\n\n<DemoTheme variant=\"yellow\" />";

package/dist/templates/mdx/theme.mdx.js

@@ -6,10 +6,13 @@ category: "Configuration"
 categoryOrder: 3
 order: 5
 ---
+
 # Theme
+
 Define your site’s color system with a \`theme.json\` file. This lets you tailor the look and feel of your documentation without changing content.
 
 ## theme.json
+
 Place a \`theme.json\` at your project root (the same folder where you execute \`npx doccupine\`). It supports multiple modes. Define a \`default\` mode and a \`dark\` mode.
 
 \`\`\`json
@@ -62,10 +65,12 @@ Place a \`theme.json\` at your project root (the same folder where you execute \
 \`\`\`
 
 ## Modes
+
 - **default**: The base color palette for your site.
 - **dark**: Dark‑mode palette.
 
 ## Fields
+
 - **primaryLight**: A lighter variant of your brand color, used for subtle accents and backgrounds.
 - **primary**: The main brand color.
 - **primaryDark**: A darker variant of your brand color for emphasis and hover states.
@@ -88,6 +93,7 @@ Place a \`theme.json\` at your project root (the same folder where you execute \
 - **logo.dark**: Path or URL to the logo used on dark backgrounds. Recommended size: 164×30 px.
 
 ## Behavior
+
 - **Placement**: Put \`theme.json\` in the project root alongside \`config.json\`.
 - **Partial palettes**: If a key is missing in a mode, consumers may fall back to the \`default\` value.
 - **Logo size**: Recommended dimensions are 164px width and 30px height.
@@ -97,11 +103,13 @@ Place a \`theme.json\` at your project root (the same folder where you execute \
 </Callout>
 
 ## Tips
+
 - **Contrast**: Ensure sufficient contrast between text and backgrounds for readability.
 - **Branding**: Start with your brand’s \`primary\` color, then derive \`primaryLight\` and \`primaryDark\`.
 - **Iterate**: Adjust colors and refresh the site to preview changes quickly.
 
 # Demo
+
 In the following demos, you can see how the theme can be changed. To override the theme, create a \`theme.json\` file in the project root and copy paste the code below.
 
 <DemoTheme variant="purple" />
@@ -155,6 +163,7 @@ In the following demos, you can see how the theme can be changed. To override th
   }
 }
 \`\`\`
+
 <DemoTheme variant="purple" />
 
 ## Green
@@ -203,6 +212,7 @@ In the following demos, you can see how the theme can be changed. To override th
   }
 }
 \`\`\`
+
 <DemoTheme variant="green" />
 
 ## Yellow

package/dist/templates/mdx/update.mdx.d.ts

@@ -1 +1 @@
-export declare const updateMdxTemplate = "---\ntitle: \"Update\"\ndescription: \"Easily manage and present change history.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 12\n---\n# Update\nEasily manage and present change history.\n\nThe `Update` component helps you display release notes, version details, and changelogs in a standardized format.\n\n<Update label=\"Example\" description=\"v0.0.1\">\n  ## Example entry\n\n  You can include anything here\u2014images, code snippets, or a bullet list of modifications.\n\n  ![Demo Image](https://docs.doccupine.com/demo.png)\n\n  ### Key additions\n\n  - Fully responsive layout\n  - Individual anchor for each update\n  - Automatic RSS feed entry generation\n</Update>\n\n## Update Usage\nYou can combine multiple `Update` components to build complete changelogs.\n\n```mdx\n<Update label=\"Example\" description=\"v0.0.1\">\n  ## Example entry\n\n  You can include anything here\u2014images, code snippets, or a bullet list of modifications.\n\n  ![Demo Image](https://docs.doccupine.com/demo.png)\n\n  ### Key additions\n\n  - Fully responsive layout\n  - Individual anchor for each update\n  - Automatic RSS feed entry generation\n</Update>\n```\n\n## Properties\n\n<Field value=\"label\" type=\"string\" required>\n  The label of the update.\n</Field>\n\n<Field value=\"description\" type=\"string\" required>\n  The description of the update.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the update.\n</Field>";
+export declare const updateMdxTemplate = "---\ntitle: \"Update\"\ndescription: \"Easily manage and present change history.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 12\n---\n\n# Update\n\nEasily manage and present change history.\n\nThe `Update` component helps you display release notes, version details, and changelogs in a standardized format.\n\n<Update label=\"Example\" description=\"v0.0.1\">\n  ## Example entry\n\nYou can include anything here\u2014images, code snippets, or a bullet list of modifications.\n\n![Demo Image](https://docs.doccupine.com/demo.png)\n\n### Key additions\n\n- Fully responsive layout\n- Individual anchor for each update\n- Automatic RSS feed entry generation\n\n</Update>\n\n## Update Usage\n\nYou can combine multiple `Update` components to build complete changelogs.\n\n```mdx\n<Update label=\"Example\" description=\"v0.0.1\">\n  ## Example entry\n\nYou can include anything here\u2014images, code snippets, or a bullet list of modifications.\n\n![Demo Image](https://docs.doccupine.com/demo.png)\n\n### Key additions\n\n- Fully responsive layout\n- Individual anchor for each update\n- Automatic RSS feed entry generation\n\n</Update>\n```\n\n## Properties\n\n<Field value=\"label\" type=\"string\" required>\n  The label of the update.\n</Field>\n\n<Field value=\"description\" type=\"string\" required>\n  The description of the update.\n</Field>\n\n<Field value=\"children\" type=\"node\" required>\n  The content of the update.\n</Field>";

package/dist/templates/mdx/update.mdx.js

@@ -6,7 +6,9 @@ category: "Components"
 categoryOrder: 1
 order: 12
 ---
+
 # Update
+
 Easily manage and present change history.
 
 The \`Update\` component helps you display release notes, version details, and changelogs in a standardized format.
@@ -14,33 +16,36 @@ The \`Update\` component helps you display release notes, version details, and c
 <Update label="Example" description="v0.0.1">
   ## Example entry
 
-  You can include anything here—images, code snippets, or a bullet list of modifications.
+You can include anything here—images, code snippets, or a bullet list of modifications.
+
+![Demo Image](https://docs.doccupine.com/demo.png)
 
-  ![Demo Image](https://docs.doccupine.com/demo.png)
+### Key additions
 
-  ### Key additions
+- Fully responsive layout
+- Individual anchor for each update
+- Automatic RSS feed entry generation
 
-  - Fully responsive layout
-  - Individual anchor for each update
-  - Automatic RSS feed entry generation
 </Update>
 
 ## Update Usage
+
 You can combine multiple \`Update\` components to build complete changelogs.
 
 \`\`\`mdx
 <Update label="Example" description="v0.0.1">
   ## Example entry
 
-  You can include anything here—images, code snippets, or a bullet list of modifications.
+You can include anything here—images, code snippets, or a bullet list of modifications.
+
+![Demo Image](https://docs.doccupine.com/demo.png)
 
-  ![Demo Image](https://docs.doccupine.com/demo.png)
+### Key additions
 
-  ### Key additions
+- Fully responsive layout
+- Individual anchor for each update
+- Automatic RSS feed entry generation
 
-  - Fully responsive layout
-  - Individual anchor for each update
-  - Automatic RSS feed entry generation
 </Update>
 \`\`\`
 

package/dist/templates/package.js

@@ -10,38 +10,38 @@ export const packageJsonTemplate = JSON.stringify({
         format: "prettier --write .",
     },
     dependencies: {
-        "@langchain/anthropic": "^1.3.27",
-        "@langchain/core": "^1.1.41",
-        "@langchain/google-genai": "^2.1.28",
-        "@langchain/openai": "^1.4.4",
+        "@langchain/anthropic": "^1.3.29",
+        "@langchain/core": "^1.1.45",
+        "@langchain/google-genai": "^2.1.30",
+        "@langchain/openai": "^1.4.5",
         "@mdx-js/react": "^3.1.1",
         "@modelcontextprotocol/sdk": "^1.29.0",
         "@posthog/react": "^1.9.0",
         "cherry-styled-components": "^0.1.17",
-        langchain: "^1.3.4",
-        "lucide-react": "^1.9.0",
+        langchain: "^1.4.0",
+        "lucide-react": "^1.14.0",
         minisearch: "^7.2.0",
-        next: "16.2.4",
+        next: "16.2.6",
         "next-mdx-remote": "^6.0.0",
-        "posthog-js": "^1.371.2",
-        "posthog-node": "^5.30.0",
-        react: "19.2.5",
-        "react-dom": "19.2.5",
+        "posthog-js": "^1.372.10",
+        "posthog-node": "^5.33.4",
+        react: "19.2.6",
+        "react-dom": "19.2.6",
         "rehype-highlight": "^7.0.2",
         "rehype-parse": "^9.0.1",
         "rehype-stringify": "^10.0.1",
         "remark-gfm": "^4.0.1",
         "styled-components": "^6.4.1",
         unified: "^11.0.5",
-        zod: "^4.3.6",
+        zod: "^4.4.3",
     },
     devDependencies: {
         "@types/node": "^25",
         "@types/react": "^19",
         "@types/react-dom": "^19",
-        "baseline-browser-mapping": "^2.10.21",
+        "baseline-browser-mapping": "^2.10.28",
         eslint: "^9",
-        "eslint-config-next": "16.2.4",
+        "eslint-config-next": "16.2.6",
         prettier: "^3.8.3",
         typescript: "^6",
     },

package/dist/templates/pnpmWorkspace.d.ts

@@ -0,0 +1 @@
+export declare const pnpmWorkspaceTemplate = "allowBuilds:\n  core-js: false\n  esbuild: false\n  protobufjs: false\n  sharp: false\n  unrs-resolver: false\n";

package/dist/templates/pnpmWorkspace.js

@@ -0,0 +1,7 @@
+export const pnpmWorkspaceTemplate = `allowBuilds:
+  core-js: false
+  esbuild: false
+  protobufjs: false
+  sharp: false
+  unrs-resolver: false
+`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "doccupine",
-  "version": "0.0.89",
+  "version": "0.0.91",
   "description": "Free and open-source documentation platform. Write MDX, get a production-ready site with AI chat, built-in components, and an MCP server - in one command.",
   "main": "dist/index.js",
   "bin": {
@@ -37,17 +37,16 @@
     "chalk": "^5.6.2",
     "chokidar": "^5.0.0",
     "commander": "^14.0.3",
-    "fs-extra": "^11.3.4",
+    "fs-extra": "^11.3.5",
     "gray-matter": "^4.0.3",
-    "next": "^16.2.4",
+    "next": "^16.2.6",
     "prompts": "^2.4.2",
-    "react": "^19.2.5",
-    "react-dom": "^19.2.5"
+    "react": "^19.2.6",
+    "react-dom": "^19.2.6"
   },
   "devDependencies": {
-    "@types/chokidar": "^2.1.7",
     "@types/fs-extra": "^11.0.4",
-    "@types/node": "^25.6.0",
+    "@types/node": "^25.6.2",
     "@types/prompts": "^2.4.9",
     "prettier": "^3.8.3",
     "typescript": "^6.0.3",