doccupine 0.0.89 → 0.0.91

package/dist/templates/mdx/deployment-and-hosting.mdx.js

@@ -6,7 +6,9 @@ category: "Configuration"
 categoryOrder: 3
 order: 11
 ---
+
 # Deployment & Hosting
+
 The fastest way to deploy your documentation is with the [Doccupine Platform](https://www.doccupine.com). If you prefer to manage your own infrastructure, you can self-host the generated Next.js app on any platform.
 
 ## Doccupine Platform
@@ -18,6 +20,7 @@ Sign up at [doccupine.com](https://www.doccupine.com) and connect your repositor
 </Callout>
 
 ### What you get
+
 - **Automatic deployments** on every push to your repository
 - **Site customization** through a visual dashboard - no code changes needed
 - **Team collaboration** so your whole team can manage docs together
@@ -26,6 +29,7 @@ Sign up at [doccupine.com](https://www.doccupine.com) and connect your repositor
 - **Zero maintenance** - no servers, no build pipelines, no dependency updates
 
 ### Getting started
+
 1. Create an account at [doccupine.com](https://www.doccupine.com).
 2. Connect your GitHub repository.
 3. Your site is deployed automatically.
@@ -56,6 +60,7 @@ Doccupine generates a standard Next.js app, so you can deploy it anywhere that s
 - **Node.js server** - run \`next build && next start\` on any server or VPS with Node.js installed.
 
 ### Sitemap and robots.txt
+
 Doccupine generates \`sitemap.xml\` and \`robots.txt\` automatically when you set a site URL. This is required for search engine indexing and is strongly recommended for any public deployment.
 
 Set the URL in \`config.json\`:
@@ -75,6 +80,7 @@ NEXT_PUBLIC_SITE_URL=https://staging.example.com
 The generated sitemap includes every page from every [section](/sections), with \`lastModified\` derived from each page's frontmatter \`date\` or the file's modification time. When no URL is configured, the sitemap is skipped and \`robots.txt\` is emitted without a sitemap reference.
 
 ### Troubleshooting
+
 - **Build failed** - check build logs. Ensure your lockfile and correct Node.js version are present.
 - **Missing content** - verify your MDX files and assets are in the repository.
 - **SSR issues on edge platforms** - some features (like the AI chat API routes) require a Node.js runtime. Check your platform's documentation for SSR/API route support.`;

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

@@ -1 +1 @@
-export declare const fieldsMdxTemplate = "---\ntitle: \"Fields\"\ndescription: \"Configure parameters for your API or SDK documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 11\n---\n# Fields\nConfigure parameters for your API or SDK documentation.\n\nFields allow you to describe both the **inputs** (parameters) and **outputs** (responses) of your API. The main field component is available: `Field` for parameters and for responses.\n\n## Fields Usage\nUse the `<Field>` component to declare API or SDK parameters, or define the return values of an API.\n\n<Field value=\"param\" type=\"string\" required>\n  Example definition of a parameter field.\n</Field>\n\n```mdx\n<Field value=\"param\" type=\"string\" required>\n  Example definition of a parameter field.\n</Field>\n```\n\n## Properties\n\n<Field value=\"value\" type=\"string\" required>\n  The name of the field.\n</Field>\n\n<Field value=\"type\" type=\"string\" required>\n  The type of the field.\n</Field>\n\n<Field value=\"required\" type=\"boolean\">\n  Whether the field is required.\n</Field>";
+export declare const fieldsMdxTemplate = "---\ntitle: \"Fields\"\ndescription: \"Configure parameters for your API or SDK documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 11\n---\n\n# Fields\n\nConfigure parameters for your API or SDK documentation.\n\nFields allow you to describe both the **inputs** (parameters) and **outputs** (responses) of your API. The main field component is available: `Field` for parameters and for responses.\n\n## Fields Usage\n\nUse the `<Field>` component to declare API or SDK parameters, or define the return values of an API.\n\n<Field value=\"param\" type=\"string\" required>\n  Example definition of a parameter field.\n</Field>\n\n```mdx\n<Field value=\"param\" type=\"string\" required>\n  Example definition of a parameter field.\n</Field>\n```\n\n## Properties\n\n<Field value=\"value\" type=\"string\" required>\n  The name of the field.\n</Field>\n\n<Field value=\"type\" type=\"string\" required>\n  The type of the field.\n</Field>\n\n<Field value=\"required\" type=\"boolean\">\n  Whether the field is required.\n</Field>";

package/dist/templates/mdx/fields.mdx.js

@@ -6,12 +6,15 @@ category: "Components"
 categoryOrder: 1
 order: 11
 ---
+
 # Fields
+
 Configure parameters for your API or SDK documentation.
 
 Fields allow you to describe both the **inputs** (parameters) and **outputs** (responses) of your API. The main field component is available: \`Field\` for parameters and for responses.
 
 ## Fields Usage
+
 Use the \`<Field>\` component to declare API or SDK parameters, or define the return values of an API.
 
 <Field value="param" type="string" required>

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

@@ -1 +1 @@
-export declare const fontsMdxTemplate = "---\ntitle: \"Fonts\"\ndescription: \"Customize the documentation typography with a fonts.json file (Google Fonts or local custom fonts).\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 7\n---\n# Fonts\nDefine your site\u2019s typography with a `fonts.json` file. You can load fonts from Google Fonts or from local font files bundled with your project.\n\n## fonts.json\nPlace a `fonts.json` at your project root (the same folder where you execute `npx doccupine`). Choose one of the following configurations depending on the source of your fonts.\n\n## Google Fonts\nUse this when your font is hosted by Google Fonts.\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": \"400\"\n  }\n}\n```\n\n### Rules\n- **fontName**: Capitalize each word. If the name contains spaces, replace them with `_`.\n  - Example: \"Work Sans\" \u2192 `Work_Sans`\n- **subsets**: Pick the subsets you need (for example, `latin`).\n- **weight**: The font weight to load - a single string (for example, `\"400\"`) or an array of strings (for example, `[\"400\", \"500\", \"700\"]`).\n\n<Callout type=\"warning\">\n  The `fontName` must match the Google Fonts name exactly - capitalize each word and replace spaces with underscores.\n</Callout>\n\n### Tips\n- **One primary family**: Start with a single family and weight, then add more if needed.\n- **Readability**: Choose readable body fonts; reserve display fonts for headings.\n\n## Local custom fonts\nUse this when you want to ship your own font files. Upload your font files to the Next.js `public` directory, then reference them with relative paths.\n\n```json\n{\n  \"localFonts\": {\n    \"src\": [\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"400\",\n        \"style\": \"normal\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"400\",\n        \"style\": \"italic\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"700\",\n        \"style\": \"normal\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"700\",\n        \"style\": \"italic\"\n      }\n    ]\n  }\n}\n```\n\n### Single file shorthand\nIf you have only one file, you can use:\n\n```json\n{\n  \"localFonts\": \"../public/font.woff\"\n}\n```\n\n### Rules\n- **Upload files**: Place `font.woff` (and any additional weights/styles) in your Next.js `public` directory.\n- **path**: Use a relative path to the file from where it is consumed by your build tooling; the example above uses `../public/font.woff`.\n- **weight**: String value of the font weight (for example, `\"400\"`, `\"700\"`).\n- **style**: `\"normal\"` or `\"italic\"`.\n\n### Tips\n- **Provide only what you need**: Include the minimal set of weights/styles to keep bundle size small.\n- **File formats**: `.woff` is broadly supported and recommended for the web.\n\n## Behavior\n- **Placement**: Put `fonts.json` in the project root alongside `config.json` and (optionally) `theme.json`.\n- **Validation**: Follow the naming rule for `googleFont.fontName` (capitalize, replace spaces with `_`).\n\n<Callout type=\"note\">\n  When using local fonts, ensure the referenced files exist under the Next.js `public` directory. The paths in `fonts.json` are relative to where they are consumed by the build tooling.\n</Callout>\n\n## Examples\n- **Google Fonts (single weight)**\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": \"400\"\n  }\n}\n```\n\n- **Google Fonts (multiple weights)**\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": [\"400\", \"500\", \"600\", \"700\"]\n  }\n}\n```\n\n- **Local fonts (multiple weights/styles)**\n\n```json\n{\n  \"localFonts\": {\n    \"src\": [\n      { \"path\": \"../public/font.woff\", \"weight\": \"400\", \"style\": \"normal\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"400\", \"style\": \"italic\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"700\", \"style\": \"normal\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"700\", \"style\": \"italic\" }\n    ]\n  }\n}\n```\n";
+export declare const fontsMdxTemplate = "---\ntitle: \"Fonts\"\ndescription: \"Customize the documentation typography with a fonts.json file (Google Fonts or local custom fonts).\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 7\n---\n\n# Fonts\n\nDefine your site\u2019s typography with a `fonts.json` file. You can load fonts from Google Fonts or from local font files bundled with your project.\n\n## fonts.json\n\nPlace a `fonts.json` at your project root (the same folder where you execute `npx doccupine`). Choose one of the following configurations depending on the source of your fonts.\n\n## Google Fonts\n\nUse this when your font is hosted by Google Fonts.\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": \"400\"\n  }\n}\n```\n\n### Rules\n\n- **fontName**: Capitalize each word. If the name contains spaces, replace them with `_`.\n  - Example: \"Work Sans\" \u2192 `Work_Sans`\n- **subsets**: Pick the subsets you need (for example, `latin`).\n- **weight**: The font weight to load - a single string (for example, `\"400\"`) or an array of strings (for example, `[\"400\", \"500\", \"700\"]`).\n\n<Callout type=\"warning\">\n  The `fontName` must match the Google Fonts name exactly - capitalize each word and replace spaces with underscores.\n</Callout>\n\n### Tips\n\n- **One primary family**: Start with a single family and weight, then add more if needed.\n- **Readability**: Choose readable body fonts; reserve display fonts for headings.\n\n## Local custom fonts\n\nUse this when you want to ship your own font files. Upload your font files to the Next.js `public` directory, then reference them with relative paths.\n\n```json\n{\n  \"localFonts\": {\n    \"src\": [\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"400\",\n        \"style\": \"normal\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"400\",\n        \"style\": \"italic\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"700\",\n        \"style\": \"normal\"\n      },\n      {\n        \"path\": \"../public/font.woff\",\n        \"weight\": \"700\",\n        \"style\": \"italic\"\n      }\n    ]\n  }\n}\n```\n\n### Single file shorthand\n\nIf you have only one file, you can use:\n\n```json\n{\n  \"localFonts\": \"../public/font.woff\"\n}\n```\n\n### Rules\n\n- **Upload files**: Place `font.woff` (and any additional weights/styles) in your Next.js `public` directory.\n- **path**: Use a relative path to the file from where it is consumed by your build tooling; the example above uses `../public/font.woff`.\n- **weight**: String value of the font weight (for example, `\"400\"`, `\"700\"`).\n- **style**: `\"normal\"` or `\"italic\"`.\n\n### Tips\n\n- **Provide only what you need**: Include the minimal set of weights/styles to keep bundle size small.\n- **File formats**: `.woff` is broadly supported and recommended for the web.\n\n## Behavior\n\n- **Placement**: Put `fonts.json` in the project root alongside `config.json` and (optionally) `theme.json`.\n- **Validation**: Follow the naming rule for `googleFont.fontName` (capitalize, replace spaces with `_`).\n\n<Callout type=\"note\">\n  When using local fonts, ensure the referenced files exist under the Next.js `public` directory. The paths in `fonts.json` are relative to where they are consumed by the build tooling.\n</Callout>\n\n## Examples\n\n- **Google Fonts (single weight)**\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": \"400\"\n  }\n}\n```\n\n- **Google Fonts (multiple weights)**\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Work_Sans\",\n    \"subsets\": [\"latin\"],\n    \"weight\": [\"400\", \"500\", \"600\", \"700\"]\n  }\n}\n```\n\n- **Local fonts (multiple weights/styles)**\n\n```json\n{\n  \"localFonts\": {\n    \"src\": [\n      { \"path\": \"../public/font.woff\", \"weight\": \"400\", \"style\": \"normal\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"400\", \"style\": \"italic\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"700\", \"style\": \"normal\" },\n      { \"path\": \"../public/font.woff\", \"weight\": \"700\", \"style\": \"italic\" }\n    ]\n  }\n}\n```";

package/dist/templates/mdx/fonts.mdx.js

@@ -6,13 +6,17 @@ category: "Configuration"
 categoryOrder: 3
 order: 7
 ---
+
 # Fonts
+
 Define your site’s typography with a \`fonts.json\` file. You can load fonts from Google Fonts or from local font files bundled with your project.
 
 ## fonts.json
+
 Place a \`fonts.json\` at your project root (the same folder where you execute \`npx doccupine\`). Choose one of the following configurations depending on the source of your fonts.
 
 ## Google Fonts
+
 Use this when your font is hosted by Google Fonts.
 
 \`\`\`json
@@ -26,6 +30,7 @@ Use this when your font is hosted by Google Fonts.
 \`\`\`
 
 ### Rules
+
 - **fontName**: Capitalize each word. If the name contains spaces, replace them with \`_\`.
   - Example: "Work Sans" → \`Work_Sans\`
 - **subsets**: Pick the subsets you need (for example, \`latin\`).
@@ -36,10 +41,12 @@ Use this when your font is hosted by Google Fonts.
 </Callout>
 
 ### Tips
+
 - **One primary family**: Start with a single family and weight, then add more if needed.
 - **Readability**: Choose readable body fonts; reserve display fonts for headings.
 
 ## Local custom fonts
+
 Use this when you want to ship your own font files. Upload your font files to the Next.js \`public\` directory, then reference them with relative paths.
 
 \`\`\`json
@@ -72,6 +79,7 @@ Use this when you want to ship your own font files. Upload your font files to th
 \`\`\`
 
 ### Single file shorthand
+
 If you have only one file, you can use:
 
 \`\`\`json
@@ -81,16 +89,19 @@ If you have only one file, you can use:
 \`\`\`
 
 ### Rules
+
 - **Upload files**: Place \`font.woff\` (and any additional weights/styles) in your Next.js \`public\` directory.
 - **path**: Use a relative path to the file from where it is consumed by your build tooling; the example above uses \`../public/font.woff\`.
 - **weight**: String value of the font weight (for example, \`"400"\`, \`"700"\`).
 - **style**: \`"normal"\` or \`"italic"\`.
 
 ### Tips
+
 - **Provide only what you need**: Include the minimal set of weights/styles to keep bundle size small.
 - **File formats**: \`.woff\` is broadly supported and recommended for the web.
 
 ## Behavior
+
 - **Placement**: Put \`fonts.json\` in the project root alongside \`config.json\` and (optionally) \`theme.json\`.
 - **Validation**: Follow the naming rule for \`googleFont.fontName\` (capitalize, replace spaces with \`_\`).
 
@@ -99,6 +110,7 @@ If you have only one file, you can use:
 </Callout>
 
 ## Examples
+
 - **Google Fonts (single weight)**
 
 \`\`\`json
@@ -136,5 +148,4 @@ If you have only one file, you can use:
     ]
   }
 }
-\`\`\`
-`;
+\`\`\``;

package/dist/templates/mdx/footer-links.mdx.d.ts

@@ -1 +1 @@
-export declare const footerLinksMdxTemplate = "---\ntitle: \"Footer Links\"\ndescription: \"Add static links at the bottom of the documentation pages.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 4\n---\n# Footer Links\nAdd a row of static links at the bottom of your documentation pages, just above the footer. Links open in a new tab and are useful for pointing users to related resources, repositories, or external docs.\n\n## links.json\nPlace a `links.json` at your project root (the same folder where you execute `npx doccupine`). When present, Doccupine displays the links at the bottom of each page. You can add as many links as you need.\n\n### Example links.json\n\n```json\n[\n  {\n    \"title\": \"Back to Home\",\n    \"url\": \"https://doccupine.com\",\n    \"icon\": \"arrow-left\"\n  },\n  {\n    \"title\": \"GitHub\",\n    \"url\": \"https://github.com/doccupine\",\n    \"icon\": \"git-branch\"\n  },\n  {\n    \"title\": \"Discord\",\n    \"url\": \"https://discord.gg/E9BufYGPhG\",\n    \"icon\": \"message-circle\"\n  }\n]\n```\n\n### Fields\n- **title**: The label shown for the link.\n- **url**: The destination URL. Links open in a new tab with `target=\"_blank\"` and `rel=\"noopener noreferrer\"`.\n- **icon**: The icon to display next to the label. Icons are from [Lucide](https://lucide.dev/).\n\n## Behavior\n- **Empty or missing file**: If `links.json` is empty or not present, the footer links are hidden.\n- **Order**: Links appear in the same order as in the array.\n- **No limit**: Add as many links as you want; they wrap automatically on smaller screens.";
+export declare const footerLinksMdxTemplate = "---\ntitle: \"Footer Links\"\ndescription: \"Add static links at the bottom of the documentation pages.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 4\n---\n\n# Footer Links\n\nAdd a row of static links at the bottom of your documentation pages, just above the footer. Links open in a new tab and are useful for pointing users to related resources, repositories, or external docs.\n\n## links.json\n\nPlace a `links.json` at your project root (the same folder where you execute `npx doccupine`). When present, Doccupine displays the links at the bottom of each page. You can add as many links as you need.\n\n### Example links.json\n\n```json\n[\n  {\n    \"title\": \"Back to Home\",\n    \"url\": \"https://doccupine.com\",\n    \"icon\": \"arrow-left\"\n  },\n  {\n    \"title\": \"GitHub\",\n    \"url\": \"https://github.com/doccupine\",\n    \"icon\": \"git-branch\"\n  },\n  {\n    \"title\": \"Discord\",\n    \"url\": \"https://discord.gg/E9BufYGPhG\",\n    \"icon\": \"message-circle\"\n  }\n]\n```\n\n### Fields\n\n- **title**: The label shown for the link.\n- **url**: The destination URL. Links open in a new tab with `target=\"_blank\"` and `rel=\"noopener noreferrer\"`.\n- **icon**: The icon to display next to the label. Icons are from [Lucide](https://lucide.dev/).\n\n## Behavior\n\n- **Empty or missing file**: If `links.json` is empty or not present, the footer links are hidden.\n- **Order**: Links appear in the same order as in the array.\n- **No limit**: Add as many links as you want; they wrap automatically on smaller screens.";

package/dist/templates/mdx/footer-links.mdx.js

@@ -6,10 +6,13 @@ category: "Configuration"
 categoryOrder: 3
 order: 4
 ---
+
 # Footer Links
+
 Add a row of static links at the bottom of your documentation pages, just above the footer. Links open in a new tab and are useful for pointing users to related resources, repositories, or external docs.
 
 ## links.json
+
 Place a \`links.json\` at your project root (the same folder where you execute \`npx doccupine\`). When present, Doccupine displays the links at the bottom of each page. You can add as many links as you need.
 
 ### Example links.json
@@ -35,11 +38,13 @@ Place a \`links.json\` at your project root (the same folder where you execute \
 \`\`\`
 
 ### Fields
+
 - **title**: The label shown for the link.
 - **url**: The destination URL. Links open in a new tab with \`target="_blank"\` and \`rel="noopener noreferrer"\`.
 - **icon**: The icon to display next to the label. Icons are from [Lucide](https://lucide.dev/).
 
 ## Behavior
+
 - **Empty or missing file**: If \`links.json\` is empty or not present, the footer links are hidden.
 - **Order**: Links appear in the same order as in the array.
 - **No limit**: Add as many links as you want; they wrap automatically on smaller screens.`;

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

@@ -1 +1 @@
-export declare const globalsMdxTemplate = "---\ntitle: \"Globals\"\ndescription: \"Configure global settings for your documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 1\n---\n# Global Configuration\nUse a `config.json` file to define project\u2011wide metadata for your documentation site. These values are applied to every generated page unless a page overrides them in its own frontmatter.\n\n## config.json\nPlace a `config.json` at your project root (the same folder where you execute `npx doccupine`) to define global metadata for your documentation site.\n\n```json\n{\n  \"name\": \"Doccupine\",\n  \"description\": \"Doccupine is a 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.\",\n  \"icon\": \"https://docs.doccupine.com/favicon.ico\",\n  \"image\": \"https://docs.doccupine.com/preview.png\",\n  \"url\": \"https://docs.example.com\"\n}\n```\n\n## Fields\nAll fields are optional. Doccupine uses sensible defaults when a field is not set.\n\n- **name**: The primary name of your documentation website. Displayed in the site title and used in various UI elements.\n- **description**: A concise summary of your project, used in site metadata (e.g., HTML meta description) and social previews when not overridden.\n- **icon**: The favicon for your site. You can provide a full URL or a relative path to an asset in your project.\n- **image**: The Open Graph image used when links to your docs are shared on social platforms. Accepts a full URL or a relative path.\n- **url**: The public URL of your deployed site. Used as the base URL for `sitemap.xml` and `robots.txt`. When omitted, no sitemap is generated. Can be overridden at deploy time with the `NEXT_PUBLIC_SITE_URL` environment variable.\n\n## Per-page overrides\nAny page can override global values by defining the matching key in its frontmatter. When present, the page's value takes precedence over `config.json` for that page only.\n\n| Frontmatter field | Overrides | Effect |\n|---|---|---|\n| **title** | - | Page title in metadata and Open Graph |\n| **description** | `description` | Meta description and Open Graph description |\n| **name** | `name` | Site name shown in the title suffix (e.g. \"Page - My Docs\") |\n| **icon** | `icon` | Favicon for this page |\n| **image** | `image` | Open Graph preview image |\n| **section** | - | Assigns the page to a [section](/sections) |\n| **sectionOrder** | - | Controls section position in the tab bar |\n| **sectionLabel** | - | Renames the default \"Docs\" tab (use on `index.mdx`) |\n\n<Callout type=\"note\">\n  If a key is not specified in a page's frontmatter, Doccupine falls back to the corresponding value in `config.json`.\n</Callout>\n\nExample frontmatter in an `.mdx` file:\n\n```text\n---\ntitle: \"My Feature\"\ndescription: \"A focused description just for this page.\"\nname: \"My Product Docs\"\nicon: \"/custom-favicon.ico\"\nimage: \"/custom-preview.png\"\ndate: \"2026-02-19\"\ncategory: \"Guides\"\n---\n```\n\n";
+export declare const globalsMdxTemplate = "---\ntitle: \"Globals\"\ndescription: \"Configure global settings for your documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 3\norder: 1\n---\n\n# Global Configuration\n\nUse a `config.json` file to define project\u2011wide metadata for your documentation site. These values are applied to every generated page unless a page overrides them in its own frontmatter.\n\n## config.json\n\nPlace a `config.json` at your project root (the same folder where you execute `npx doccupine`) to define global metadata for your documentation site.\n\n```json\n{\n  \"name\": \"Doccupine\",\n  \"description\": \"Doccupine is a 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.\",\n  \"icon\": \"https://docs.doccupine.com/favicon.ico\",\n  \"image\": \"https://docs.doccupine.com/preview.png\",\n  \"url\": \"https://docs.example.com\"\n}\n```\n\n## Fields\n\nAll fields are optional. Doccupine uses sensible defaults when a field is not set.\n\n- **name**: The primary name of your documentation website. Displayed in the site title and used in various UI elements.\n- **description**: A concise summary of your project, used in site metadata (e.g., HTML meta description) and social previews when not overridden.\n- **icon**: The favicon for your site. You can provide a full URL or a relative path to an asset in your project.\n- **image**: The Open Graph image used when links to your docs are shared on social platforms. Accepts a full URL or a relative path.\n- **url**: The public URL of your deployed site. Used as the base URL for `sitemap.xml` and `robots.txt`. When omitted, no sitemap is generated. Can be overridden at deploy time with the `NEXT_PUBLIC_SITE_URL` environment variable.\n\n## Per-page overrides\n\nAny page can override global values by defining the matching key in its frontmatter. When present, the page's value takes precedence over `config.json` for that page only.\n\n| Frontmatter field | Overrides     | Effect                                                      |\n| ----------------- | ------------- | ----------------------------------------------------------- |\n| **title**         | -             | Page title in metadata and Open Graph                       |\n| **description**   | `description` | Meta description and Open Graph description                 |\n| **name**          | `name`        | Site name shown in the title suffix (e.g. \"Page - My Docs\") |\n| **icon**          | `icon`        | Favicon for this page                                       |\n| **image**         | `image`       | Open Graph preview image                                    |\n| **section**       | -             | Assigns the page to a [section](/sections)                  |\n| **sectionOrder**  | -             | Controls section position in the tab bar                    |\n| **sectionLabel**  | -             | Renames the default \"Docs\" tab (use on `index.mdx`)         |\n\n<Callout type=\"note\">\n  If a key is not specified in a page's frontmatter, Doccupine falls back to the corresponding value in `config.json`.\n</Callout>\n\nExample frontmatter in an `.mdx` file:\n\n```text\n---\ntitle: \"My Feature\"\ndescription: \"A focused description just for this page.\"\nname: \"My Product Docs\"\nicon: \"/custom-favicon.ico\"\nimage: \"/custom-preview.png\"\ndate: \"2026-02-19\"\ncategory: \"Guides\"\n---\n```";

package/dist/templates/mdx/globals.mdx.js

@@ -7,10 +7,13 @@ category: "Configuration"
 categoryOrder: 3
 order: 1
 ---
+
 # Global Configuration
+
 Use a \`config.json\` file to define project‑wide metadata for your documentation site. These values are applied to every generated page unless a page overrides them in its own frontmatter.
 
 ## config.json
+
 Place a \`config.json\` at your project root (the same folder where you execute \`npx doccupine\`) to define global metadata for your documentation site.
 
 \`\`\`json
@@ -24,6 +27,7 @@ Place a \`config.json\` at your project root (the same folder where you execute
 \`\`\`
 
 ## Fields
+
 All fields are optional. Doccupine uses sensible defaults when a field is not set.
 
 - **name**: The primary name of your documentation website. Displayed in the site title and used in various UI elements.
@@ -33,18 +37,19 @@ All fields are optional. Doccupine uses sensible defaults when a field is not se
 - **url**: The public URL of your deployed site. Used as the base URL for \`sitemap.xml\` and \`robots.txt\`. When omitted, no sitemap is generated. Can be overridden at deploy time with the \`NEXT_PUBLIC_SITE_URL\` environment variable.
 
 ## Per-page overrides
+
 Any page can override global values by defining the matching key in its frontmatter. When present, the page's value takes precedence over \`config.json\` for that page only.
 
-| Frontmatter field | Overrides | Effect |
-|---|---|---|
-| **title** | - | Page title in metadata and Open Graph |
-| **description** | \`description\` | Meta description and Open Graph description |
-| **name** | \`name\` | Site name shown in the title suffix (e.g. "Page - My Docs") |
-| **icon** | \`icon\` | Favicon for this page |
-| **image** | \`image\` | Open Graph preview image |
-| **section** | - | Assigns the page to a [section](/sections) |
-| **sectionOrder** | - | Controls section position in the tab bar |
-| **sectionLabel** | - | Renames the default "Docs" tab (use on \`index.mdx\`) |
+| Frontmatter field | Overrides     | Effect                                                      |
+| ----------------- | ------------- | ----------------------------------------------------------- |
+| **title**         | -             | Page title in metadata and Open Graph                       |
+| **description**   | \`description\` | Meta description and Open Graph description                 |
+| **name**          | \`name\`        | Site name shown in the title suffix (e.g. "Page - My Docs") |
+| **icon**          | \`icon\`        | Favicon for this page                                       |
+| **image**         | \`image\`       | Open Graph preview image                                    |
+| **section**       | -             | Assigns the page to a [section](/sections)                  |
+| **sectionOrder**  | -             | Controls section position in the tab bar                    |
+| **sectionLabel**  | -             | Renames the default "Docs" tab (use on \`index.mdx\`)         |
 
 <Callout type="note">
   If a key is not specified in a page's frontmatter, Doccupine falls back to the corresponding value in \`config.json\`.
@@ -62,6 +67,4 @@ image: "/custom-preview.png"
 date: "2026-02-19"
 category: "Guides"
 ---
-\`\`\`
-
-`;
+\`\`\``;

package/dist/templates/mdx/headers-and-text.mdx.d.ts

@@ -1 +1 @@
-export declare const headersAndTextMdxTemplate = "---\ntitle: \"Headers and Text\"\ndescription: \"Learn how to structure and style your content with headers, formatting, and links.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 1\n---\n# Headers and Text\nLearn how to structure and style your content with headers, formatting, and links.\n\n## Headers\nHeaders define the hierarchy of your content and automatically generate navigation anchors. They also appear in the table of contents, helping readers quickly scan through documentation.\n\n### Creating headers\nAdd `#` symbols before text to create headers at various levels:\n\n```text\n## Main section header\n### Subsection header\n#### Nested subsection header\n```\n\n## Text Formatting\nMarkdown text styling is supported for emphasis, highlighting, and readability.\n\n### Basic formatting\nUse these common syntax options:\n\n- Bold: `**bold text**` \u2192 **bold text**\n- Italic: `*italic text*` \u2192 *italic text*\n- Strikethrough: `~~strikethrough~~` \u2192 ~~strikethrough~~\n\n### Combining formats\nYou can mix multiple styles at once for clarity:\n\n```text\n**_bold and italic_**\n**~~bold and strikethrough~~**\n*~~italic and strikethrough~~**\n```\n\n## Superscript and subscript\nFor formulas, notes, or variables, use HTML tags:\n\n- Superscript `X<sup>2</sup>` \u2192 X<sup>2</sup>\n- Subscript `H<sub>2</sub>O` \u2192 H<sub>2</sub>O\n\n## Links\nLinks connect users to internal pages or external resources. Always use descriptive link text for better accessibility.\n\n### Internal links\nReference other docs with root-relative paths:\n\n```text\n[Getting Started](/)\n[Commands](/commands)\n```\n\n- [Getting Started](/)\n- [Commands](/commands)\n\n### External links\nPoint to external pages by including full URLs:\n\n```text\n[Markdown Guide](https://www.markdownguide.org/)\n```\n\n[Markdown Guide](https://www.markdownguide.org/)\n\n## Blockquotes\nBlockquotes are used to visually highlight key information, quotations, or examples.\n\n### Single line blockquotes\nPrefix text with `>` for a single-line blockquote:\n\n```text\n> Highlighted message or quote\n```\n\n> Highlighted message or quote\n\n### Multi-line blockquotes\nFor larger quotes spanning more than one paragraph:\n\n```text\n> This is a blockquote that spans multiple lines.\n> It can include several paragraphs of text.\n> Each new line starts with a `>` symbol.\n```\n\n> This is a blockquote that spans multiple lines.\n> It can include several paragraphs of text.\n> Each new line starts with a `>` symbol.\n\n## Line Breaks and Spacing\nControl spacing to improve readability and layout.\n\n### Paragraph breaks\nSeparate paragraphs with blank lines:\n\n```text\nFirst paragraph.\n\nSecond paragraph.\n```\n\nFirst paragraph.\n\nSecond paragraph.\n\n## Manual line breaks\nFor shorter breaks inside the same paragraph, use `<br />`:\n\n```text\nThis is one line.<br />\nThis is the next line.\n```\n\nThis is one line.<br />\nThis is the next line.\n\n# Best Practices\n\n## Organizing content\n- Use headers to establish hierarchy\n- Maintain logical order (avoid skipping levels, e.g., H2 \u2192 H4)\n- Always write meaningful, descriptive headers\n\n## Formatting text\n- Use **bold** for key emphasis only\n- Use *italics* for emphasis or technical terms\n- Limit formatting combinations to maintain readability\n\n## Links usage\n- Avoid vague text like \u201Cclick here\u201D\n- Prefer root-relative paths for internal links\n- Regularly validate links to ensure they are not broken";
+export declare const headersAndTextMdxTemplate = "---\ntitle: \"Headers and Text\"\ndescription: \"Learn how to structure and style your content with headers, formatting, and links.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 1\n---\n\n# Headers and Text\n\nLearn how to structure and style your content with headers, formatting, and links.\n\n## Headers\n\nHeaders define the hierarchy of your content and automatically generate navigation anchors. They also appear in the table of contents, helping readers quickly scan through documentation.\n\n### Creating headers\n\nAdd `#` symbols before text to create headers at various levels:\n\n```text\n## Main section header\n### Subsection header\n#### Nested subsection header\n```\n\n## Text Formatting\n\nMarkdown text styling is supported for emphasis, highlighting, and readability.\n\n### Basic formatting\n\nUse these common syntax options:\n\n- Bold: `**bold text**` \u2192 **bold text**\n- Italic: `*italic text*` \u2192 _italic text_\n- Strikethrough: `~~strikethrough~~` \u2192 ~~strikethrough~~\n\n### Combining formats\n\nYou can mix multiple styles at once for clarity:\n\n```text\n**_bold and italic_**\n**~~bold and strikethrough~~**\n*~~italic and strikethrough~~**\n```\n\n## Superscript and subscript\n\nFor formulas, notes, or variables, use HTML tags:\n\n- Superscript `X<sup>2</sup>` \u2192 X<sup>2</sup>\n- Subscript `H<sub>2</sub>O` \u2192 H<sub>2</sub>O\n\n## Links\n\nLinks connect users to internal pages or external resources. Always use descriptive link text for better accessibility.\n\n### Internal links\n\nReference other docs with root-relative paths:\n\n```text\n[Getting Started](/)\n[Commands](/commands)\n```\n\n- [Getting Started](/)\n- [Commands](/commands)\n\n### External links\n\nPoint to external pages by including full URLs:\n\n```text\n[Markdown Guide](https://www.markdownguide.org/)\n```\n\n[Markdown Guide](https://www.markdownguide.org/)\n\n## Blockquotes\n\nBlockquotes are used to visually highlight key information, quotations, or examples.\n\n### Single line blockquotes\n\nPrefix text with `>` for a single-line blockquote:\n\n```text\n> Highlighted message or quote\n```\n\n> Highlighted message or quote\n\n### Multi-line blockquotes\n\nFor larger quotes spanning more than one paragraph:\n\n```text\n> This is a blockquote that spans multiple lines.\n> It can include several paragraphs of text.\n> Each new line starts with a `>` symbol.\n```\n\n> This is a blockquote that spans multiple lines.\n> It can include several paragraphs of text.\n> Each new line starts with a `>` symbol.\n\n## Line Breaks and Spacing\n\nControl spacing to improve readability and layout.\n\n### Paragraph breaks\n\nSeparate paragraphs with blank lines:\n\n```text\nFirst paragraph.\n\nSecond paragraph.\n```\n\nFirst paragraph.\n\nSecond paragraph.\n\n## Manual line breaks\n\nFor shorter breaks inside the same paragraph, use `<br />`:\n\n```text\nThis is one line.<br />\nThis is the next line.\n```\n\nThis is one line.<br />\nThis is the next line.\n\n# Best Practices\n\n## Organizing content\n\n- Use headers to establish hierarchy\n- Maintain logical order (avoid skipping levels, e.g., H2 \u2192 H4)\n- Always write meaningful, descriptive headers\n\n## Formatting text\n\n- Use **bold** for key emphasis only\n- Use _italics_ for emphasis or technical terms\n- Limit formatting combinations to maintain readability\n\n## Links usage\n\n- Avoid vague text like \u201Cclick here\u201D\n- Prefer root-relative paths for internal links\n- Regularly validate links to ensure they are not broken";

package/dist/templates/mdx/headers-and-text.mdx.js

@@ -6,13 +6,17 @@ category: "Components"
 categoryOrder: 1
 order: 1
 ---
+
 # Headers and Text
+
 Learn how to structure and style your content with headers, formatting, and links.
 
 ## Headers
+
 Headers define the hierarchy of your content and automatically generate navigation anchors. They also appear in the table of contents, helping readers quickly scan through documentation.
 
 ### Creating headers
+
 Add \`#\` symbols before text to create headers at various levels:
 
 \`\`\`text
@@ -22,16 +26,19 @@ Add \`#\` symbols before text to create headers at various levels:
 \`\`\`
 
 ## Text Formatting
+
 Markdown text styling is supported for emphasis, highlighting, and readability.
 
 ### Basic formatting
+
 Use these common syntax options:
 
 - Bold: \`**bold text**\` → **bold text**
-- Italic: \`*italic text*\` → *italic text*
+- Italic: \`*italic text*\` → _italic text_
 - Strikethrough: \`~~strikethrough~~\` → ~~strikethrough~~
 
 ### Combining formats
+
 You can mix multiple styles at once for clarity:
 
 \`\`\`text
@@ -41,15 +48,18 @@ You can mix multiple styles at once for clarity:
 \`\`\`
 
 ## Superscript and subscript
+
 For formulas, notes, or variables, use HTML tags:
 
 - Superscript \`X<sup>2</sup>\` → X<sup>2</sup>
 - Subscript \`H<sub>2</sub>O\` → H<sub>2</sub>O
 
 ## Links
+
 Links connect users to internal pages or external resources. Always use descriptive link text for better accessibility.
 
 ### Internal links
+
 Reference other docs with root-relative paths:
 
 \`\`\`text
@@ -61,6 +71,7 @@ Reference other docs with root-relative paths:
 - [Commands](/commands)
 
 ### External links
+
 Point to external pages by including full URLs:
 
 \`\`\`text
@@ -70,9 +81,11 @@ Point to external pages by including full URLs:
 [Markdown Guide](https://www.markdownguide.org/)
 
 ## Blockquotes
+
 Blockquotes are used to visually highlight key information, quotations, or examples.
 
 ### Single line blockquotes
+
 Prefix text with \`>\` for a single-line blockquote:
 
 \`\`\`text
@@ -82,6 +95,7 @@ Prefix text with \`>\` for a single-line blockquote:
 > Highlighted message or quote
 
 ### Multi-line blockquotes
+
 For larger quotes spanning more than one paragraph:
 
 \`\`\`text
@@ -95,9 +109,11 @@ For larger quotes spanning more than one paragraph:
 > Each new line starts with a \`>\` symbol.
 
 ## Line Breaks and Spacing
+
 Control spacing to improve readability and layout.
 
 ### Paragraph breaks
+
 Separate paragraphs with blank lines:
 
 \`\`\`text
@@ -111,6 +127,7 @@ First paragraph.
 Second paragraph.
 
 ## Manual line breaks
+
 For shorter breaks inside the same paragraph, use \`<br />\`:
 
 \`\`\`text
@@ -124,16 +141,19 @@ This is the next line.
 # Best Practices
 
 ## Organizing content
+
 - Use headers to establish hierarchy
 - Maintain logical order (avoid skipping levels, e.g., H2 → H4)
 - Always write meaningful, descriptive headers
 
 ## Formatting text
+
 - Use **bold** for key emphasis only
-- Use *italics* for emphasis or technical terms
+- Use _italics_ for emphasis or technical terms
 - Limit formatting combinations to maintain readability
 
 ## Links usage
+
 - Avoid vague text like “click here”
 - Prefer root-relative paths for internal links
 - Regularly validate links to ensure they are not broken`;

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

@@ -1 +1 @@
-export declare const iconsMdxTemplate = "---\ntitle: \"Icons\"\ndescription: \"Integrate visual icons from well-known libraries to enrich your documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 10\n---\n# Icons\nIntegrate visual icons from well-known libraries to enrich your documentation.\n\nIcons can be sourced from Lucide, SVG elements, external URLs, or local files within your project directory.\n\n<Icon name=\"flag\" size={32} />\n\n```mdx\n<Icon name=\"flag\" size={32} />\n```\n\n## Inline icons\nYou can use icons directly within text to highlight information or add visual context.\n\n<Icon name=\"flag\" size={16} /> Build your documentation seamlessly.\n\n```mdx\n<Icon name=\"flag\" size={16} /> Build your documentation seamlessly.\n```\n\n## Properties\n\n<Field value=\"name\" type=\"string\" required>\n  The icon to display.\n</Field>\n\n- [**Lucide icon**](https://lucide.dev/icons) name\n\n<Field value=\"size\" type=\"number\">\n  The size of the icon in pixels.\n</Field>\n\n<Field value=\"color\" type=\"string\">\n  The color of the icon as a hex code (for example, `#FF5733`).\n</Field>";
+export declare const iconsMdxTemplate = "---\ntitle: \"Icons\"\ndescription: \"Integrate visual icons from well-known libraries to enrich your documentation.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 10\n---\n\n# Icons\n\nIntegrate visual icons from well-known libraries to enrich your documentation.\n\nIcons can be sourced from Lucide, SVG elements, external URLs, or local files within your project directory.\n\n<Icon name=\"flag\" size={32} />\n\n```mdx\n<Icon name=\"flag\" size={32} />\n```\n\n## Inline icons\n\nYou can use icons directly within text to highlight information or add visual context.\n\n<Icon name=\"flag\" size={16} /> Build your documentation seamlessly.\n\n```mdx\n<Icon name=\"flag\" size={16} /> Build your documentation seamlessly.\n```\n\n## Properties\n\n<Field value=\"name\" type=\"string\" required>\n  The icon to display.\n</Field>\n\n- [**Lucide icon**](https://lucide.dev/icons) name\n\n<Field value=\"size\" type=\"number\">\n  The size of the icon in pixels.\n</Field>\n\n<Field value=\"color\" type=\"string\">\n  The color of the icon as a hex code (for example, `#FF5733`).\n</Field>";

package/dist/templates/mdx/icons.mdx.js

@@ -6,7 +6,9 @@ category: "Components"
 categoryOrder: 1
 order: 10
 ---
+
 # Icons
+
 Integrate visual icons from well-known libraries to enrich your documentation.
 
 Icons can be sourced from Lucide, SVG elements, external URLs, or local files within your project directory.
@@ -18,6 +20,7 @@ Icons can be sourced from Lucide, SVG elements, external URLs, or local files wi
 \`\`\`
 
 ## Inline icons
+
 You can use icons directly within text to highlight information or add visual context.
 
 <Icon name="flag" size={16} /> Build your documentation seamlessly.

package/dist/templates/mdx/image-and-embeds.mdx.d.ts

@@ -1 +1 @@
-export declare const imageAndEmbedsMdxTemplate = "---\ntitle: \"Images and embeds\"\ndescription: \"Enrich your documentation with visuals, videos, and interactive embeds.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 9\n---\n# Images and embeds\nEnrich your documentation with visuals, videos, and interactive embeds.\n\nDisplay images, embed video content, or add interactive frames via iframes to supplement your docs.\n\n![Demo Image](https://docs.doccupine.com/demo.png)\n\n## Images\nImages enhance documentation with context, illustration, or decorative visual cues.\n\n### Basic Image Syntax\nInclude an image in Markdown using the syntax below:\n\n```md\n![Alt text](https://docs.doccupine.com/demo.png)\n```\n\n<Callout type=\"note\">\n  Use clear, descriptive alt text for accessibility and better SEO. Alt text should describe the image\u2019s appearance or content.\n</Callout>\n\n### HTML image embeds\nEmbed images in your Markdown content using HTML syntax.\n\n```md\n<img src=\"https://docs.doccupine.com/demo.png\" alt=\"Alt text\">\n```\n\n### Theme-aware images\nShow different images depending on whether the user is in light or dark mode. Add the `light-only` or `dark-only` className to display an image exclusively in that theme.\n\n```md\n<img className=\"light-only\" src=\"/images/diagram-light.png\" alt=\"Diagram\">\n<img className=\"dark-only\" src=\"/images/diagram-dark.png\" alt=\"Diagram\">\n```\n\n<img className=\"light-only\" src=\"https://docs.doccupine.com/demo.png\" alt=\"This image is only visible in light mode\" />\n<img className=\"dark-only\" src=\"https://docs.doccupine.com/demo.png\" alt=\"This image is only visible in dark mode\" style={{ filter: \"invert(1)\" }} />\n\n<Callout type=\"note\">\n  The `light-only` and `dark-only` classes work on any element, not just images. You can use them on videos, iframes, or wrapper divs too.\n</Callout>\n\n## Videos\nVideos add a dynamic element to your documentation, engaging your audience and providing a more immersive experience.\n\n### YouTube Embed\nTo embed a YouTube video, use the following syntax:\n\n```html\n<iframe\n  className=\"aspect-video\"\n  src=\"https://www.youtube.com/embed/ResP_eVPYQo\"\n  title=\"YouTube video player\"\n  frameBorder=\"0\"\n  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\"\n  allowFullScreen\n></iframe>\n```\n\n<iframe\n  className=\"aspect-video\"\n  src=\"https://www.youtube.com/embed/ResP_eVPYQo\"\n  title=\"YouTube video player\"\n  frameBorder=\"0\"\n  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\"\n  allowFullScreen\n></iframe>\n\n### Self-hosted videos\nServe up your own video content using the `<video>` tag:\n\n```html\n<video\n  controls\n  className=\"aspect-video\"\n  src=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n></video>\n```\n\n<video\n  controls\n  className=\"aspect-video\"\n  src=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n></video>\n\n\n#### Autoplay and Looping\nFor demonstration videos that loop or start automatically, add attributes as shown:\n\n```html\n<video\n  controls\n  className=\"aspect-video\"\n  src=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n  autoPlay\n  muted\n  loop\n  playsInline\n></video>\n```\n";
+export declare const imageAndEmbedsMdxTemplate = "---\ntitle: \"Images and embeds\"\ndescription: \"Enrich your documentation with visuals, videos, and interactive embeds.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 9\n---\n\n# Images and embeds\n\nEnrich your documentation with visuals, videos, and interactive embeds.\n\nDisplay images, embed video content, or add interactive frames via iframes to supplement your docs.\n\n![Demo Image](https://docs.doccupine.com/demo.png)\n\n## Images\n\nImages enhance documentation with context, illustration, or decorative visual cues.\n\n### Basic Image Syntax\n\nInclude an image in Markdown using the syntax below:\n\n```md\n![Alt text](https://docs.doccupine.com/demo.png)\n```\n\n<Callout type=\"note\">\n  Use clear, descriptive alt text for accessibility and better SEO. Alt text should describe the image\u2019s appearance or content.\n</Callout>\n\n### HTML image embeds\n\nEmbed images in your Markdown content using HTML syntax.\n\n```md\n<img src=\"https://docs.doccupine.com/demo.png\" alt=\"Alt text\">\n```\n\n### Theme-aware images\n\nShow different images depending on whether the user is in light or dark mode. Add the `light-only` or `dark-only` className to display an image exclusively in that theme.\n\n```md\n<img className=\"light-only\" src=\"/images/diagram-light.png\" alt=\"Diagram\">\n<img className=\"dark-only\" src=\"/images/diagram-dark.png\" alt=\"Diagram\">\n```\n\n<img className=\"light-only\" src=\"https://docs.doccupine.com/demo.png\" alt=\"This image is only visible in light mode\" />\n<img className=\"dark-only\" src=\"https://docs.doccupine.com/demo.png\" alt=\"This image is only visible in dark mode\" style={{ filter: \"invert(1)\" }} />\n\n<Callout type=\"note\">\n  The `light-only` and `dark-only` classes work on any element, not just images. You can use them on videos, iframes, or wrapper divs too.\n</Callout>\n\n## Videos\n\nVideos add a dynamic element to your documentation, engaging your audience and providing a more immersive experience.\n\n### YouTube Embed\n\nTo embed a YouTube video, use the following syntax:\n\n```html\n<iframe\n  className=\"aspect-video\"\n  src=\"https://www.youtube.com/embed/ResP_eVPYQo\"\n  title=\"YouTube video player\"\n  frameborder=\"0\"\n  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\"\n  allowfullscreen\n></iframe>\n```\n\n<iframe\n  className=\"aspect-video\"\n  src=\"https://www.youtube.com/embed/ResP_eVPYQo\"\n  title=\"YouTube video player\"\n  frameBorder=\"0\"\n  allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture\"\n  allowFullScreen\n></iframe>\n\n### Self-hosted videos\n\nServe up your own video content using the `<video>` tag:\n\n```html\n<video\n  controls\n  className=\"aspect-video\"\n  src=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n></video>\n```\n\n<video\ncontrols\nclassName=\"aspect-video\"\nsrc=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n\n> </video>\n\n#### Autoplay and Looping\n\nFor demonstration videos that loop or start automatically, add attributes as shown:\n\n```html\n<video\n  controls\n  className=\"aspect-video\"\n  src=\"https://samplelib.com/lib/preview/mp4/sample-20s.mp4\"\n  autoplay\n  muted\n  loop\n  playsinline\n></video>\n```";

package/dist/templates/mdx/image-and-embeds.mdx.js

@@ -6,7 +6,9 @@ category: "Components"
 categoryOrder: 1
 order: 9
 ---
+
 # Images and embeds
+
 Enrich your documentation with visuals, videos, and interactive embeds.
 
 Display images, embed video content, or add interactive frames via iframes to supplement your docs.
@@ -14,9 +16,11 @@ Display images, embed video content, or add interactive frames via iframes to su
 ![Demo Image](https://docs.doccupine.com/demo.png)
 
 ## Images
+
 Images enhance documentation with context, illustration, or decorative visual cues.
 
 ### Basic Image Syntax
+
 Include an image in Markdown using the syntax below:
 
 \`\`\`md
@@ -28,6 +32,7 @@ Include an image in Markdown using the syntax below:
 </Callout>
 
 ### HTML image embeds
+
 Embed images in your Markdown content using HTML syntax.
 
 \`\`\`md
@@ -35,6 +40,7 @@ Embed images in your Markdown content using HTML syntax.
 \`\`\`
 
 ### Theme-aware images
+
 Show different images depending on whether the user is in light or dark mode. Add the \`light-only\` or \`dark-only\` className to display an image exclusively in that theme.
 
 \`\`\`md
@@ -50,9 +56,11 @@ Show different images depending on whether the user is in light or dark mode. Ad
 </Callout>
 
 ## Videos
+
 Videos add a dynamic element to your documentation, engaging your audience and providing a more immersive experience.
 
 ### YouTube Embed
+
 To embed a YouTube video, use the following syntax:
 
 \`\`\`html
@@ -60,9 +68,9 @@ To embed a YouTube video, use the following syntax:
   className="aspect-video"
   src="https://www.youtube.com/embed/ResP_eVPYQo"
   title="YouTube video player"
-  frameBorder="0"
+  frameborder="0"
   allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
-  allowFullScreen
+  allowfullscreen
 ></iframe>
 \`\`\`
 
@@ -76,6 +84,7 @@ To embed a YouTube video, use the following syntax:
 ></iframe>
 
 ### Self-hosted videos
+
 Serve up your own video content using the \`<video>\` tag:
 
 \`\`\`html
@@ -87,13 +96,14 @@ Serve up your own video content using the \`<video>\` tag:
 \`\`\`
 
 <video
-  controls
-  className="aspect-video"
-  src="https://samplelib.com/lib/preview/mp4/sample-20s.mp4"
-></video>
+controls
+className="aspect-video"
+src="https://samplelib.com/lib/preview/mp4/sample-20s.mp4"
 
+> </video>
 
 #### Autoplay and Looping
+
 For demonstration videos that loop or start automatically, add attributes as shown:
 
 \`\`\`html
@@ -101,10 +111,9 @@ For demonstration videos that loop or start automatically, add attributes as sho
   controls
   className="aspect-video"
   src="https://samplelib.com/lib/preview/mp4/sample-20s.mp4"
-  autoPlay
+  autoplay
   muted
   loop
-  playsInline
+  playsinline
 ></video>
-\`\`\`
-`;
+\`\`\``;

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

@@ -1 +1 @@
-export declare const indexMdxTemplate = "---\ntitle: \"Introduction\"\ndescription: \"Doccupine is a 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.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 0\n---\n# Welcome to Doccupine\n\nDoccupine turns a folder of MDX files into a beautiful, production-ready documentation website. Write in standard Markdown, use any of the built-in components, and get a fully themed site with AI-powered search and automatic navigation - all from one command.\n\n```bash\nnpx doccupine\n```\n\nThat's it. Doccupine prompts you for a source directory, generates your site, and starts a dev server at `http://localhost:3000`. Every edit rebuilds instantly.\n\n<Callout type=\"info\">\n  Want a managed experience instead? The [Doccupine Platform](/platform) gives you a browser-based editor, one-click publishing, custom domains, and team collaboration - no local setup needed.\n</Callout>\n\n## How it works\n\nYou write `.mdx` files using Markdown and built-in components like this one. Doccupine watches your files, generates pages, builds the sidebar from your frontmatter, and handles theming, AI chat, and deployment config for you.\n\nEverything on this page - the callout above, the cards below, the code block - is a live example of what your docs can look like out of the box.\n\n<Columns cols={2}>\n  <Card title=\"Start writing\" icon=\"pencil\" href=\"/components\">\n    Rich docs from day one. 14+ components work out of the box - no imports needed.\n  </Card>\n  <Card title=\"Ship it\" icon=\"rocket\" href=\"/deployment-and-hosting\">\n    Deploy to the Doccupine Platform or self-host on any platform that supports Next.js.\n  </Card>\n</Columns>\n\n## Configure your site\n\nDoccupine works with no configuration, but when you're ready to customize, everything is controlled through simple JSON files in your project root.\n\n- [Global settings](/globals) - Site name, description, favicon, and preview image via `config.json`\n- [Navigation](/navigation) - Override the auto-generated sidebar with `navigation.json`\n- [Theme](/theme) - Colors, logos, and dark mode palette via `theme.json`\n- [Fonts](/fonts) - Google Fonts or local font files via `fonts.json`\n- [AI Assistant](/ai-assistant) - Enable the built-in chat with your own API key\n- [MCP Server](/model-context-protocol) - Let AI tools search your docs through `/api/mcp`\n";
+export declare const indexMdxTemplate = "---\ntitle: \"Introduction\"\ndescription: \"Doccupine is a 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.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 0\n---\n\n# Welcome to Doccupine\n\nDoccupine turns a folder of MDX files into a beautiful, production-ready documentation website. Write in standard Markdown, use any of the built-in components, and get a fully themed site with AI-powered search and automatic navigation - all from one command.\n\n```bash\nnpx doccupine\n```\n\nThat's it. Doccupine prompts you for a source directory, generates your site, and starts a dev server at `http://localhost:3000`. Every edit rebuilds instantly.\n\n<Callout type=\"info\">\n  Want a managed experience instead? The [Doccupine Platform](/platform) gives you a browser-based editor, one-click publishing, custom domains, and team collaboration - no local setup needed.\n</Callout>\n\n## How it works\n\nYou write `.mdx` files using Markdown and built-in components like this one. Doccupine watches your files, generates pages, builds the sidebar from your frontmatter, and handles theming, AI chat, and deployment config for you.\n\nEverything on this page - the callout above, the cards below, the code block - is a live example of what your docs can look like out of the box.\n\n<Columns cols={2}>\n  <Card title=\"Start writing\" icon=\"pencil\" href=\"/components\">\n    Rich docs from day one. 14+ components work out of the box - no imports needed.\n  </Card>\n  <Card title=\"Ship it\" icon=\"rocket\" href=\"/deployment-and-hosting\">\n    Deploy to the Doccupine Platform or self-host on any platform that supports Next.js.\n  </Card>\n</Columns>\n\n## Configure your site\n\nDoccupine works with no configuration, but when you're ready to customize, everything is controlled through simple JSON files in your project root.\n\n- [Global settings](/globals) - Site name, description, favicon, and preview image via `config.json`\n- [Navigation](/navigation) - Override the auto-generated sidebar with `navigation.json`\n- [Theme](/theme) - Colors, logos, and dark mode palette via `theme.json`\n- [Fonts](/fonts) - Google Fonts or local font files via `fonts.json`\n- [AI Assistant](/ai-assistant) - Enable the built-in chat with your own API key\n- [MCP Server](/model-context-protocol) - Let AI tools search your docs through `/api/mcp`";

package/dist/templates/mdx/index.mdx.js

@@ -7,6 +7,7 @@ category: "Getting Started"
 categoryOrder: 0
 order: 0
 ---
+
 # Welcome to Doccupine
 
 Doccupine turns a folder of MDX files into a beautiful, production-ready documentation website. Write in standard Markdown, use any of the built-in components, and get a fully themed site with AI-powered search and automatic navigation - all from one command.
@@ -45,5 +46,4 @@ Doccupine works with no configuration, but when you're ready to customize, every
 - [Theme](/theme) - Colors, logos, and dark mode palette via \`theme.json\`
 - [Fonts](/fonts) - Google Fonts or local font files via \`fonts.json\`
 - [AI Assistant](/ai-assistant) - Enable the built-in chat with your own API key
-- [MCP Server](/model-context-protocol) - Let AI tools search your docs through \`/api/mcp\`
-`;
+- [MCP Server](/model-context-protocol) - Let AI tools search your docs through \`/api/mcp\``;

package/dist/templates/mdx/lists-and-tables.mdx.d.ts

@@ -1 +1 @@
-export declare const listsAndTablesMdxTemplate = "---\ntitle: \"Lists and tables\"\ndescription: \"Present structured information using lists or tables.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 2\n---\n# Lists and Tables\nPresent structured information using lists or tables.\n\n## Lists\nMarkdown supports both *ordered* and *unordered* lists, as well as nested list structures.\n\n### Ordered List\nStart each item with a number followed by a period to create an ordered list.\n\n```md\n1. First item\n2. Second item\n3. Third item\n4. Fourth item\n```\n\n1. First item\n2. Second item\n3. Third item\n4. Fourth item\n\n\n### Unordered List\nUse dashes (`-`), asterisks (`*`), or plus signs (`+`) before each item for unordered lists.\n\n```md\n- First item\n- Second item\n- Third item\n- Fourth item\n```\n\n- First item\n- Second item\n- Third item\n- Fourth item\n\n### Nested List\nIndent items under another to create nested lists.\n\n```md\n- First item\n- Second item\n  - Additional item\n  - Additional item\n- Third item\n```\n\n- First item\n- Second item\n  - Additional item\n  - Additional item\n- Third item\n\n## Tables\nMarkdown tables use pipes (`|`) to separate columns and hyphens (`---`) to define the header row. Place a pipe at the start and end of each row for better compatibility.\n\n```md\n| Property | Description                            |\n| -------- | -------------------------------------- |\n| Name     | Full name of the user                  |\n| Age      | Age in years                           |\n| Joined   | Indicates if user joined the community |\n```\n\n| Property | Description                            |\n| -------- | -------------------------------------- |\n| Name     | Full name of the user                  |\n| Age      | Age in years                           |\n| Joined   | Indicates if user joined the community |";
+export declare const listsAndTablesMdxTemplate = "---\ntitle: \"Lists and tables\"\ndescription: \"Present structured information using lists or tables.\"\ndate: \"2026-02-19\"\ncategory: \"Components\"\ncategoryOrder: 1\norder: 2\n---\n\n# Lists and Tables\n\nPresent structured information using lists or tables.\n\n## Lists\n\nMarkdown supports both _ordered_ and _unordered_ lists, as well as nested list structures.\n\n### Ordered List\n\nStart each item with a number followed by a period to create an ordered list.\n\n```md\n1. First item\n2. Second item\n3. Third item\n4. Fourth item\n```\n\n1. First item\n2. Second item\n3. Third item\n4. Fourth item\n\n### Unordered List\n\nUse dashes (`-`), asterisks (`*`), or plus signs (`+`) before each item for unordered lists.\n\n```md\n- First item\n- Second item\n- Third item\n- Fourth item\n```\n\n- First item\n- Second item\n- Third item\n- Fourth item\n\n### Nested List\n\nIndent items under another to create nested lists.\n\n```md\n- First item\n- Second item\n  - Additional item\n  - Additional item\n- Third item\n```\n\n- First item\n- Second item\n  - Additional item\n  - Additional item\n- Third item\n\n## Tables\n\nMarkdown tables use pipes (`|`) to separate columns and hyphens (`---`) to define the header row. Place a pipe at the start and end of each row for better compatibility.\n\n```md\n| Property | Description                            |\n| -------- | -------------------------------------- |\n| Name     | Full name of the user                  |\n| Age      | Age in years                           |\n| Joined   | Indicates if user joined the community |\n```\n\n| Property | Description                            |\n| -------- | -------------------------------------- |\n| Name     | Full name of the user                  |\n| Age      | Age in years                           |\n| Joined   | Indicates if user joined the community |";