doccupine 0.0.89 → 0.0.90

package/dist/templates/mdx/platform/build-and-deploy.mdx.d.ts

@@ -1 +1 @@
-export declare const platformBuildAndDeployMdxTemplate = "---\ntitle: \"Build & Deploy\"\ndescription: \"Monitor your documentation site's build status and deployment history.\"\ndate: \"2026-02-19\"\ncategory: \"Infrastructure\"\ncategoryOrder: 3\norder: 1\nsection: \"Platform\"\n---\n# Build & Deploy\nThe Build & Deploy page shows your documentation site's build and deployment history. Every time you publish changes or push to GitHub, a new deployment is created.\n\n## Deployment status\nThe project header always shows your current deployment status:\n\n- **Ready** - your site is live and up to date\n- **Building** - a new deployment is in progress\n- **Queued** - a deployment is waiting to start\n- **Error** - the build failed\n\n<Callout type=\"warning\">\n  If a deployment fails, check the build logs for error details. Common issues include MDX syntax errors or missing frontmatter fields.\n</Callout>\n\n## Build logs\nClick on any deployment to view its build logs. These show the full output of the build process, making it easy to diagnose issues.\n\n## Deployment triggers\nDeployments are triggered in three ways:\n\n1. **Publishing from Doccupine** - clicking Publish in the project header\n2. **Pushing to GitHub** - pushing to the `main` branch of your repository triggers an automatic deploy via webhook\n3. **Configuration changes** - saving AI assistant settings triggers a redeploy since those are stored as environment variables\n\n## Visiting your site\nClick the **Visit** button in the project header to open your live documentation site in a new tab.";
+export declare const platformBuildAndDeployMdxTemplate = "---\ntitle: \"Build & Deploy\"\ndescription: \"Monitor your documentation site's build status and deployment history.\"\ndate: \"2026-02-19\"\ncategory: \"Infrastructure\"\ncategoryOrder: 3\norder: 1\nsection: \"Platform\"\n---\n\n# Build & Deploy\n\nThe Build & Deploy page shows your documentation site's build and deployment history. Every time you publish changes or push to GitHub, a new deployment is created.\n\n## Deployment status\n\nThe project header always shows your current deployment status:\n\n- **Ready** - your site is live and up to date\n- **Building** - a new deployment is in progress\n- **Queued** - a deployment is waiting to start\n- **Error** - the build failed\n\n<Callout type=\"warning\">\n  If a deployment fails, check the build logs for error details. Common issues include MDX syntax errors or missing frontmatter fields.\n</Callout>\n\n## Build logs\n\nClick on any deployment to view its build logs. These show the full output of the build process, making it easy to diagnose issues.\n\n## Deployment triggers\n\nDeployments are triggered in three ways:\n\n1. **Publishing from Doccupine** - clicking Publish in the project header\n2. **Pushing to GitHub** - pushing to the `main` branch of your repository triggers an automatic deploy via webhook\n3. **Configuration changes** - saving AI assistant settings triggers a redeploy since those are stored as environment variables\n\n## Visiting your site\n\nClick the **Visit** button in the project header to open your live documentation site in a new tab.";

package/dist/templates/mdx/platform/build-and-deploy.mdx.js

@@ -7,10 +7,13 @@ categoryOrder: 3
 order: 1
 section: "Platform"
 ---
+
 # Build & Deploy
+
 The Build & Deploy page shows your documentation site's build and deployment history. Every time you publish changes or push to GitHub, a new deployment is created.
 
 ## Deployment status
+
 The project header always shows your current deployment status:
 
 - **Ready** - your site is live and up to date
@@ -23,9 +26,11 @@ The project header always shows your current deployment status:
 </Callout>
 
 ## Build logs
+
 Click on any deployment to view its build logs. These show the full output of the build process, making it easy to diagnose issues.
 
 ## Deployment triggers
+
 Deployments are triggered in three ways:
 
 1. **Publishing from Doccupine** - clicking Publish in the project header
@@ -33,4 +38,5 @@ Deployments are triggered in three ways:
 3. **Configuration changes** - saving AI assistant settings triggers a redeploy since those are stored as environment variables
 
 ## Visiting your site
+
 Click the **Visit** button in the project header to open your live documentation site in a new tab.`;

package/dist/templates/mdx/platform/creating-a-project.mdx.d.ts

@@ -1 +1 @@
-export declare const platformCreatingAProjectMdxTemplate = "---\ntitle: \"Creating a Project\"\ndescription: \"Set up a new documentation project with a managed or user-connected GitHub repository.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 1\nsection: \"Platform\"\n---\n# Creating a Project\nFrom your dashboard, click **Create new project** to get started. You'll name your project and choose how its Git repository is managed.\n\n## Repository modes\nDoccupine needs a GitHub repository to store your documentation files. You have two options:\n\n### Managed repository\nChoose **Use managed repository** and Doccupine creates and manages the GitHub repo for you under its own organization. This is the simplest option - no GitHub account required on your end.\n\n### User repository\nChoose **Connect to GitHub** to link your own GitHub account via OAuth. Doccupine creates the repo in your account, giving you full ownership and direct access to the source files.\n\n<Callout type=\"note\">\n  You can connect your GitHub account at any time. If you're not sure, start with a managed repository - you can always migrate later.\n</Callout>\n\n## What happens during setup\nAfter you choose a repository mode, Doccupine runs an automated setup process:\n\n1. Creates a GitHub repository\n2. Commits a starter template with example documentation files\n3. Creates a hosting project on the deployment platform\n4. Runs the initial build and deployment\n5. Sets up a webhook so future pushes to the `main` branch trigger automatic deploys\n\nThis takes about a minute. Once complete, you're redirected to your new project's file explorer.\n\n<Callout type=\"success\">\n  Your site is live immediately after setup. Visit it using the **Visit** button in the project header.\n</Callout>\n\n## Project limits\nThe number of projects you can create depends on your plan:\n\n- **Pro** - 1 project, up to 5 team members\n- **Enterprise** - 6 projects, unlimited team members\n\nIf you've reached your limit, you'll see a prompt to upgrade your plan.";
+export declare const platformCreatingAProjectMdxTemplate = "---\ntitle: \"Creating a Project\"\ndescription: \"Set up a new documentation project with a managed or user-connected GitHub repository.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 1\nsection: \"Platform\"\n---\n\n# Creating a Project\n\nFrom your dashboard, click **Create new project** to get started. You'll name your project and choose how its Git repository is managed.\n\n## Repository modes\n\nDoccupine needs a GitHub repository to store your documentation files. You have two options:\n\n### Managed repository\n\nChoose **Use managed repository** and Doccupine creates and manages the GitHub repo for you under its own organization. This is the simplest option - no GitHub account required on your end.\n\n### User repository\n\nChoose **Connect to GitHub** to link your own GitHub account via OAuth. Doccupine creates the repo in your account, giving you full ownership and direct access to the source files.\n\n<Callout type=\"note\">\n  You can connect your GitHub account at any time. If you're not sure, start with a managed repository - you can always migrate later.\n</Callout>\n\n## What happens during setup\n\nAfter you choose a repository mode, Doccupine runs an automated setup process:\n\n1. Creates a GitHub repository\n2. Commits a starter template with example documentation files\n3. Creates a hosting project on the deployment platform\n4. Runs the initial build and deployment\n5. Sets up a webhook so future pushes to the `main` branch trigger automatic deploys\n\nThis takes about a minute. Once complete, you're redirected to your new project's file explorer.\n\n<Callout type=\"success\">\n  Your site is live immediately after setup. Visit it using the **Visit** button in the project header.\n</Callout>\n\n## Project limits\n\nThe number of projects you can create depends on your plan:\n\n- **Pro** - 1 project, up to 5 team members\n- **Enterprise** - 6 projects, unlimited team members\n\nIf you've reached your limit, you'll see a prompt to upgrade your plan.";

package/dist/templates/mdx/platform/creating-a-project.mdx.js

@@ -7,16 +7,21 @@ categoryOrder: 0
 order: 1
 section: "Platform"
 ---
+
 # Creating a Project
+
 From your dashboard, click **Create new project** to get started. You'll name your project and choose how its Git repository is managed.
 
 ## Repository modes
+
 Doccupine needs a GitHub repository to store your documentation files. You have two options:
 
 ### Managed repository
+
 Choose **Use managed repository** and Doccupine creates and manages the GitHub repo for you under its own organization. This is the simplest option - no GitHub account required on your end.
 
 ### User repository
+
 Choose **Connect to GitHub** to link your own GitHub account via OAuth. Doccupine creates the repo in your account, giving you full ownership and direct access to the source files.
 
 <Callout type="note">
@@ -24,6 +29,7 @@ Choose **Connect to GitHub** to link your own GitHub account via OAuth. Doccupin
 </Callout>
 
 ## What happens during setup
+
 After you choose a repository mode, Doccupine runs an automated setup process:
 
 1. Creates a GitHub repository
@@ -39,6 +45,7 @@ This takes about a minute. Once complete, you're redirected to your new project'
 </Callout>
 
 ## Project limits
+
 The number of projects you can create depends on your plan:
 
 - **Pro** - 1 project, up to 5 team members

package/dist/templates/mdx/platform/custom-domains.mdx.d.ts

@@ -1 +1 @@
-export declare const platformCustomDomainsMdxTemplate = "---\ntitle: \"Custom Domains\"\ndescription: \"Connect your own domain to your documentation site with automatic HTTPS.\"\ndate: \"2026-02-19\"\ncategory: \"Infrastructure\"\ncategoryOrder: 3\norder: 0\nsection: \"Platform\"\n---\n# Custom Domains\nBy default, your documentation site is available at a `.doccupine.app` subdomain. You can connect your own custom domain for a branded experience.\n\n## Adding a domain\n\n1. Navigate to your project's **Domains** page from the sidebar.\n2. Enter your custom domain (e.g., `docs.yourcompany.com`).\n3. Click **Add Domain**.\n\nDoccupine will provide DNS records that you need to configure with your domain registrar.\n\n## DNS configuration\nAfter adding your domain, you'll see the required DNS records. Typically this involves adding a **CNAME** record pointing to your Doccupine deployment.\n\nConfigure the records with your domain registrar (Cloudflare, Namecheap, GoDaddy, Route 53, etc.) and return to the Domains page to check verification status.\n\n<Callout type=\"note\">\n  DNS changes can take up to 48 hours to propagate, though most resolve within a few minutes.\n</Callout>\n\n## Verification\nDoccupine periodically checks whether your DNS records are configured correctly. The Domains page shows the current verification status. Once verified, your custom domain is active and serves your documentation with automatic HTTPS.\n\n## Removing a domain\nClick the remove button next to your domain to disconnect it. Your site will continue to be available at its `.doccupine.app` URL.";
+export declare const platformCustomDomainsMdxTemplate = "---\ntitle: \"Custom Domains\"\ndescription: \"Connect your own domain to your documentation site with automatic HTTPS.\"\ndate: \"2026-02-19\"\ncategory: \"Infrastructure\"\ncategoryOrder: 3\norder: 0\nsection: \"Platform\"\n---\n\n# Custom Domains\n\nBy default, your documentation site is available at a `.doccupine.app` subdomain. You can connect your own custom domain for a branded experience.\n\n## Adding a domain\n\n1. Navigate to your project's **Domains** page from the sidebar.\n2. Enter your custom domain (e.g., `docs.yourcompany.com`).\n3. Click **Add Domain**.\n\nDoccupine will provide DNS records that you need to configure with your domain registrar.\n\n## DNS configuration\n\nAfter adding your domain, you'll see the required DNS records. Typically this involves adding a **CNAME** record pointing to your Doccupine deployment.\n\nConfigure the records with your domain registrar (Cloudflare, Namecheap, GoDaddy, Route 53, etc.) and return to the Domains page to check verification status.\n\n<Callout type=\"note\">\n  DNS changes can take up to 48 hours to propagate, though most resolve within a few minutes.\n</Callout>\n\n## Verification\n\nDoccupine periodically checks whether your DNS records are configured correctly. The Domains page shows the current verification status. Once verified, your custom domain is active and serves your documentation with automatic HTTPS.\n\n## Removing a domain\n\nClick the remove button next to your domain to disconnect it. Your site will continue to be available at its `.doccupine.app` URL.";

package/dist/templates/mdx/platform/custom-domains.mdx.js

@@ -7,7 +7,9 @@ categoryOrder: 3
 order: 0
 section: "Platform"
 ---
+
 # Custom Domains
+
 By default, your documentation site is available at a \`.doccupine.app\` subdomain. You can connect your own custom domain for a branded experience.
 
 ## Adding a domain
@@ -19,6 +21,7 @@ By default, your documentation site is available at a \`.doccupine.app\` subdoma
 Doccupine will provide DNS records that you need to configure with your domain registrar.
 
 ## DNS configuration
+
 After adding your domain, you'll see the required DNS records. Typically this involves adding a **CNAME** record pointing to your Doccupine deployment.
 
 Configure the records with your domain registrar (Cloudflare, Namecheap, GoDaddy, Route 53, etc.) and return to the Domains page to check verification status.
@@ -28,7 +31,9 @@ Configure the records with your domain registrar (Cloudflare, Namecheap, GoDaddy
 </Callout>
 
 ## Verification
+
 Doccupine periodically checks whether your DNS records are configured correctly. The Domains page shows the current verification status. Once verified, your custom domain is active and serves your documentation with automatic HTTPS.
 
 ## Removing a domain
+
 Click the remove button next to your domain to disconnect it. Your site will continue to be available at its \`.doccupine.app\` URL.`;

package/dist/templates/mdx/platform/external-links.mdx.d.ts

@@ -1 +1 @@
-export declare const platformExternalLinksMdxTemplate = "---\ntitle: \"External Links\"\ndescription: \"Add quick-access link buttons to your site's footer for GitHub, Discord, and other external resources.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 5\nsection: \"Platform\"\n---\n# External Links\nThe External Links settings page lets you add external link buttons to your documentation site's footer. These provide quick access to your project's GitHub repository, Discord server, social profiles, and other resources.\n\n## Adding a link\nClick **Add Link** and configure:\n\n- **Icon** (optional) - search and pick from any [Lucide](https://lucide.dev/) icon\n- **Title** - the display text for the link\n- **URL** - the target URL\n\n## Choosing an icon\nThe icon picker lets you search through the full [Lucide](https://lucide.dev/) icon set. Type a keyword to filter (e.g. \"git-branch\", \"mail\", \"globe\") and click to select.\n\nLeave the icon unset for a text-only link.\n\nIf you edit `links.json` directly, use Lucide icon names in kebab-case (e.g. `git-branch`, `message-circle`, `heart`).\n\n## How it works\nLink settings are stored in `links.json` at the root of your repository:\n\n```json\n[\n  {\n    \"title\": \"GitHub\",\n    \"url\": \"https://github.com/your-org/your-repo\",\n    \"icon\": \"git-branch\"\n  },\n  {\n    \"title\": \"Discord\",\n    \"url\": \"https://discord.gg/your-invite\",\n    \"icon\": \"discord\"\n  }\n]\n```";
+export declare const platformExternalLinksMdxTemplate = "---\ntitle: \"External Links\"\ndescription: \"Add quick-access link buttons to your site's footer for GitHub, Discord, and other external resources.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 5\nsection: \"Platform\"\n---\n\n# External Links\n\nThe External Links settings page lets you add external link buttons to your documentation site's footer. These provide quick access to your project's GitHub repository, Discord server, social profiles, and other resources.\n\n## Adding a link\n\nClick **Add Link** and configure:\n\n- **Icon** (optional) - search and pick from any [Lucide](https://lucide.dev/) icon\n- **Title** - the display text for the link\n- **URL** - the target URL\n\n## Choosing an icon\n\nThe icon picker lets you search through the full [Lucide](https://lucide.dev/) icon set. Type a keyword to filter (e.g. \"git-branch\", \"mail\", \"globe\") and click to select.\n\nLeave the icon unset for a text-only link.\n\nIf you edit `links.json` directly, use Lucide icon names in kebab-case (e.g. `git-branch`, `message-circle`, `heart`).\n\n## How it works\n\nLink settings are stored in `links.json` at the root of your repository:\n\n```json\n[\n  {\n    \"title\": \"GitHub\",\n    \"url\": \"https://github.com/your-org/your-repo\",\n    \"icon\": \"git-branch\"\n  },\n  {\n    \"title\": \"Discord\",\n    \"url\": \"https://discord.gg/your-invite\",\n    \"icon\": \"discord\"\n  }\n]\n```";

package/dist/templates/mdx/platform/external-links.mdx.js

@@ -7,10 +7,13 @@ categoryOrder: 2
 order: 5
 section: "Platform"
 ---
+
 # External Links
+
 The External Links settings page lets you add external link buttons to your documentation site's footer. These provide quick access to your project's GitHub repository, Discord server, social profiles, and other resources.
 
 ## Adding a link
+
 Click **Add Link** and configure:
 
 - **Icon** (optional) - search and pick from any [Lucide](https://lucide.dev/) icon
@@ -18,6 +21,7 @@ Click **Add Link** and configure:
 - **URL** - the target URL
 
 ## Choosing an icon
+
 The icon picker lets you search through the full [Lucide](https://lucide.dev/) icon set. Type a keyword to filter (e.g. "git-branch", "mail", "globe") and click to select.
 
 Leave the icon unset for a text-only link.
@@ -25,6 +29,7 @@ Leave the icon unset for a text-only link.
 If you edit \`links.json\` directly, use Lucide icon names in kebab-case (e.g. \`git-branch\`, \`message-circle\`, \`heart\`).
 
 ## How it works
+
 Link settings are stored in \`links.json\` at the root of your repository:
 
 \`\`\`json

package/dist/templates/mdx/platform/file-editor.mdx.d.ts

@@ -1 +1 @@
-export declare const platformFileEditorMdxTemplate = "---\ntitle: \"File Editor\"\ndescription: \"Browse, create, and edit your documentation files directly in the browser.\"\ndate: \"2026-02-19\"\ncategory: \"Editing\"\ncategoryOrder: 1\norder: 0\nsection: \"Platform\"\n---\n# File Editor\nThe file editor is the main workspace for your documentation project. It provides a browser-based file explorer and editor for working with your MDX files and assets.\n\n## File explorer\nThe left panel has three tabs:\n\n- **Files** - browse your repository's file tree, create and manage files and folders\n- **Media** - manage uploaded images and binary assets\n- **Navigation** - open the [Navigation Builder](/platform/navigation-settings) to configure your sidebar structure with drag-and-drop\n\nIn the Files tab, you can:\n\n- **Browse** directories and files\n- **Create** new files and folders\n- **Rename** and **delete** existing files\n- **Upload** binary assets like images, favicons, and font files\n\nClick any file to open it in the editor panel.\n\n## Editing files\nThe editor supports MDX files with full syntax highlighting. Changes you make are saved as **pending changes** - they aren't committed to your repository until you publish.\n\n<Callout type=\"note\">\n  Pending changes are stored in Doccupine's database, not in your Git repository. This means you can make edits across multiple sessions before publishing.\n</Callout>\n\n## Version history\nFor any file, you can view its commit history to see how it has changed over time. This lets you:\n\n- See when changes were made and what the commit messages were\n- View the file's content at any previous commit\n- Compare past versions to understand what changed\n\n## Binary files\nYou can upload images and other binary assets (PNG, JPG, SVG, WOFF2, etc.) directly through the file explorer. These are stored temporarily in Doccupine's storage and committed to your repository when you publish.\n\n## Read-only mode\nTeam members with the **Viewer** or **Billing** role can browse files but cannot make edits. The editor will display content in read-only mode for these users.";
+export declare const platformFileEditorMdxTemplate = "---\ntitle: \"File Editor\"\ndescription: \"Browse, create, and edit your documentation files directly in the browser.\"\ndate: \"2026-02-19\"\ncategory: \"Editing\"\ncategoryOrder: 1\norder: 0\nsection: \"Platform\"\n---\n\n# File Editor\n\nThe file editor is the main workspace for your documentation project. It provides a browser-based file explorer and editor for working with your MDX files and assets.\n\n## File explorer\n\nThe left panel has three tabs:\n\n- **Files** - browse your repository's file tree, create and manage files and folders\n- **Media** - manage uploaded images and binary assets\n- **Navigation** - open the [Navigation Builder](/platform/navigation-settings) to configure your sidebar structure with drag-and-drop\n\nIn the Files tab, you can:\n\n- **Browse** directories and files\n- **Create** new files and folders\n- **Rename** and **delete** existing files\n- **Upload** binary assets like images, favicons, and font files\n\nClick any file to open it in the editor panel.\n\n## Editing files\n\nThe editor supports MDX files with full syntax highlighting. Changes you make are saved as **pending changes** - they aren't committed to your repository until you publish.\n\n<Callout type=\"note\">\n  Pending changes are stored in Doccupine's database, not in your Git repository. This means you can make edits across multiple sessions before publishing.\n</Callout>\n\n## Version history\n\nFor any file, you can view its commit history to see how it has changed over time. This lets you:\n\n- See when changes were made and what the commit messages were\n- View the file's content at any previous commit\n- Compare past versions to understand what changed\n\n## Binary files\n\nYou can upload images and other binary assets (PNG, JPG, SVG, WOFF2, etc.) directly through the file explorer. These are stored temporarily in Doccupine's storage and committed to your repository when you publish.\n\n## Read-only mode\n\nTeam members with the **Viewer** or **Billing** role can browse files but cannot make edits. The editor will display content in read-only mode for these users.";

package/dist/templates/mdx/platform/file-editor.mdx.js

@@ -7,10 +7,13 @@ categoryOrder: 1
 order: 0
 section: "Platform"
 ---
+
 # File Editor
+
 The file editor is the main workspace for your documentation project. It provides a browser-based file explorer and editor for working with your MDX files and assets.
 
 ## File explorer
+
 The left panel has three tabs:
 
 - **Files** - browse your repository's file tree, create and manage files and folders
@@ -27,6 +30,7 @@ In the Files tab, you can:
 Click any file to open it in the editor panel.
 
 ## Editing files
+
 The editor supports MDX files with full syntax highlighting. Changes you make are saved as **pending changes** - they aren't committed to your repository until you publish.
 
 <Callout type="note">
@@ -34,6 +38,7 @@ The editor supports MDX files with full syntax highlighting. Changes you make ar
 </Callout>
 
 ## Version history
+
 For any file, you can view its commit history to see how it has changed over time. This lets you:
 
 - See when changes were made and what the commit messages were
@@ -41,7 +46,9 @@ For any file, you can view its commit history to see how it has changed over tim
 - Compare past versions to understand what changed
 
 ## Binary files
+
 You can upload images and other binary assets (PNG, JPG, SVG, WOFF2, etc.) directly through the file explorer. These are stored temporarily in Doccupine's storage and committed to your repository when you publish.
 
 ## Read-only mode
+
 Team members with the **Viewer** or **Billing** role can browse files but cannot make edits. The editor will display content in read-only mode for these users.`;

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

@@ -1 +1 @@
-export declare const platformFontsSettingsMdxTemplate = "---\ntitle: \"Fonts Settings\"\ndescription: \"Configure custom typography with Google Fonts or local font files.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 4\nsection: \"Platform\"\n---\n# Fonts Settings\nThe Fonts settings page lets you customize your documentation site's typography using Google Fonts or locally uploaded font files.\n\n## Google Fonts\nSelect a font from the full Google Fonts library:\n\n1. Type a font name to search the library.\n2. Select the **weights** you need (e.g., 400 for regular, 700 for bold). You can select multiple weights.\n3. Choose **subsets** for language support (latin, cyrillic, greek, vietnamese, etc.).\n\n<Callout type=\"note\">\n  Only include the weights and subsets you actually use. Each addition increases page load time.\n</Callout>\n\n## Local fonts\nUpload your own font files for complete typographic control:\n\n1. Click **Add Font Source** to add a font file entry.\n2. Upload a font file (WOFF2, WOFF, TTF, OTF, or EOT format).\n3. Set the **weight** (e.g., 400, 700) and **style** (normal or italic).\n4. Add more sources for additional weights and styles.\n\nWOFF2 is recommended for the best compression and browser support.\n\n## How it works\nFont settings are stored in `fonts.json` at the root of your repository. Here's an example using Google Fonts:\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Inter\",\n    \"subsets\": [\"latin\"],\n    \"weight\": [\"400\", \"500\", \"600\", \"700\"]\n  }\n}\n```\n\nSee the [Fonts](/fonts) page for the full configuration format, including local font support.";
+export declare const platformFontsSettingsMdxTemplate = "---\ntitle: \"Fonts Settings\"\ndescription: \"Configure custom typography with Google Fonts or local font files.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 4\nsection: \"Platform\"\n---\n\n# Fonts Settings\n\nThe Fonts settings page lets you customize your documentation site's typography using Google Fonts or locally uploaded font files.\n\n## Google Fonts\n\nSelect a font from the full Google Fonts library:\n\n1. Type a font name to search the library.\n2. Select the **weights** you need (e.g., 400 for regular, 700 for bold). You can select multiple weights.\n3. Choose **subsets** for language support (latin, cyrillic, greek, vietnamese, etc.).\n\n<Callout type=\"note\">\n  Only include the weights and subsets you actually use. Each addition increases page load time.\n</Callout>\n\n## Local fonts\n\nUpload your own font files for complete typographic control:\n\n1. Click **Add Font Source** to add a font file entry.\n2. Upload a font file (WOFF2, WOFF, TTF, OTF, or EOT format).\n3. Set the **weight** (e.g., 400, 700) and **style** (normal or italic).\n4. Add more sources for additional weights and styles.\n\nWOFF2 is recommended for the best compression and browser support.\n\n## How it works\n\nFont settings are stored in `fonts.json` at the root of your repository. Here's an example using Google Fonts:\n\n```json\n{\n  \"googleFont\": {\n    \"fontName\": \"Inter\",\n    \"subsets\": [\"latin\"],\n    \"weight\": [\"400\", \"500\", \"600\", \"700\"]\n  }\n}\n```\n\nSee the [Fonts](/fonts) page for the full configuration format, including local font support.";

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

@@ -7,10 +7,13 @@ categoryOrder: 2
 order: 4
 section: "Platform"
 ---
+
 # Fonts Settings
+
 The Fonts settings page lets you customize your documentation site's typography using Google Fonts or locally uploaded font files.
 
 ## Google Fonts
+
 Select a font from the full Google Fonts library:
 
 1. Type a font name to search the library.
@@ -22,6 +25,7 @@ Select a font from the full Google Fonts library:
 </Callout>
 
 ## Local fonts
+
 Upload your own font files for complete typographic control:
 
 1. Click **Add Font Source** to add a font file entry.
@@ -32,6 +36,7 @@ Upload your own font files for complete typographic control:
 WOFF2 is recommended for the best compression and browser support.
 
 ## How it works
+
 Font settings are stored in \`fonts.json\` at the root of your repository. Here's an example using Google Fonts:
 
 \`\`\`json

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

@@ -1 +1 @@
-export declare const platformIndexMdxTemplate = "---\ntitle: \"Platform Overview\"\ndescription: \"Learn how to use the Doccupine platform to create, customize, and deploy documentation websites.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 0\nsection: \"Platform\"\n---\n# Platform Overview\nThe Doccupine platform gives you everything you need to create, customize, and host beautiful documentation websites - all from your browser. No local setup, no CI pipelines, no infrastructure to manage.\n\n## What you get\n- **Browser-based editor** for writing and managing your documentation files\n- **One-click publishing** that commits to GitHub and deploys automatically\n- **Visual configuration** for themes, navigation, fonts, links, and more\n- **Custom domains** with automatic HTTPS\n- **AI assistant** built into every deployed site\n- **Team collaboration** with role-based access control\n\n## How it works\nDoccupine connects two core pieces behind the scenes:\n\n1. **GitHub** stores your documentation source files in a Git repository\n2. **Doccupine** builds, hosts, and serves your site globally - plus provides a dashboard for editing, configuring, and managing your project\n\nYou write MDX files, configure your site through visual settings pages, and hit Publish. Doccupine handles the rest.\n\n## Getting started\n\n1. **Sign up** at Doccupine and start your free 30-day trial - no credit card required.\n2. **Create a project** from the dashboard. Choose between a managed repository or connecting your own GitHub account.\n3. **Edit your docs** using the built-in file explorer and editor.\n4. **Configure your site** through the settings pages - theme, navigation, fonts, and more.\n5. **Publish** your changes with a single click.\n\n<Callout type=\"success\">\n  Your documentation site is live the moment you create a project. Doccupine deploys a starter site automatically so you can see results immediately.\n</Callout>\n\n## Dashboard\nAfter signing in, the dashboard shows all your projects. You'll see two sections:\n\n- **Your Projects** - documentation sites you own, plus a button to create new ones\n- **Shared Projects** - sites that other users have invited you to collaborate on\n\nClick any project card to open it and start working.\n\n<Columns cols={2}>\n  <Card title=\"Sign Up\" icon=\"user-plus\" href=\"https://doccupine.com/sign-up\">\n    Create your free account and start building documentation in minutes.\n  </Card>\n  <Card title=\"Sign In\" icon=\"log-in\" href=\"https://doccupine.com/sign-in\">\n    Already have an account? Sign in to your dashboard.\n  </Card>\n</Columns>";
+export declare const platformIndexMdxTemplate = "---\ntitle: \"Platform Overview\"\ndescription: \"Learn how to use the Doccupine platform to create, customize, and deploy documentation websites.\"\ndate: \"2026-02-19\"\ncategory: \"Getting Started\"\ncategoryOrder: 0\norder: 0\nsection: \"Platform\"\n---\n\n# Platform Overview\n\nThe Doccupine platform gives you everything you need to create, customize, and host beautiful documentation websites - all from your browser. No local setup, no CI pipelines, no infrastructure to manage.\n\n## What you get\n\n- **Browser-based editor** for writing and managing your documentation files\n- **One-click publishing** that commits to GitHub and deploys automatically\n- **Visual configuration** for themes, navigation, fonts, links, and more\n- **Custom domains** with automatic HTTPS\n- **AI assistant** built into every deployed site\n- **Team collaboration** with role-based access control\n\n## How it works\n\nDoccupine connects two core pieces behind the scenes:\n\n1. **GitHub** stores your documentation source files in a Git repository\n2. **Doccupine** builds, hosts, and serves your site globally - plus provides a dashboard for editing, configuring, and managing your project\n\nYou write MDX files, configure your site through visual settings pages, and hit Publish. Doccupine handles the rest.\n\n## Getting started\n\n1. **Sign up** at Doccupine and start your free 30-day trial - no credit card required.\n2. **Create a project** from the dashboard. Choose between a managed repository or connecting your own GitHub account.\n3. **Edit your docs** using the built-in file explorer and editor.\n4. **Configure your site** through the settings pages - theme, navigation, fonts, and more.\n5. **Publish** your changes with a single click.\n\n<Callout type=\"success\">\n  Your documentation site is live the moment you create a project. Doccupine deploys a starter site automatically so you can see results immediately.\n</Callout>\n\n## Dashboard\n\nAfter signing in, the dashboard shows all your projects. You'll see two sections:\n\n- **Your Projects** - documentation sites you own, plus a button to create new ones\n- **Shared Projects** - sites that other users have invited you to collaborate on\n\nClick any project card to open it and start working.\n\n<Columns cols={2}>\n  <Card title=\"Sign Up\" icon=\"user-plus\" href=\"https://doccupine.com/sign-up\">\n    Create your free account and start building documentation in minutes.\n  </Card>\n  <Card title=\"Sign In\" icon=\"log-in\" href=\"https://doccupine.com/sign-in\">\n    Already have an account? Sign in to your dashboard.\n  </Card>\n</Columns>";

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

@@ -7,10 +7,13 @@ categoryOrder: 0
 order: 0
 section: "Platform"
 ---
+
 # Platform Overview
+
 The Doccupine platform gives you everything you need to create, customize, and host beautiful documentation websites - all from your browser. No local setup, no CI pipelines, no infrastructure to manage.
 
 ## What you get
+
 - **Browser-based editor** for writing and managing your documentation files
 - **One-click publishing** that commits to GitHub and deploys automatically
 - **Visual configuration** for themes, navigation, fonts, links, and more
@@ -19,6 +22,7 @@ The Doccupine platform gives you everything you need to create, customize, and h
 - **Team collaboration** with role-based access control
 
 ## How it works
+
 Doccupine connects two core pieces behind the scenes:
 
 1. **GitHub** stores your documentation source files in a Git repository
@@ -39,6 +43,7 @@ You write MDX files, configure your site through visual settings pages, and hit
 </Callout>
 
 ## Dashboard
+
 After signing in, the dashboard shows all your projects. You'll see two sections:
 
 - **Your Projects** - documentation sites you own, plus a button to create new ones

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

@@ -1 +1 @@
-export declare const platformNavigationSettingsMdxTemplate = "---\ntitle: \"Navigation Settings\"\ndescription: \"Define the sidebar structure for your documentation site using the drag-and-drop Navigation Builder.\"\ndate: \"2026-02-24\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 2\nsection: \"Platform\"\n---\n# Navigation Settings\nThe Navigation Builder lets you define your sidebar structure through a visual, drag-and-drop interface. It lives inside the **File Explorer** as a dedicated **Navigation** tab, alongside the Files and Media tabs.\n\n## Structure\nNavigation is organized into three levels:\n\n- **Section** - a top-level area of your site (e.g., \"Docs\", \"API Reference\"). Each section appears as a tab below the site header and has its own sidebar. Sections are defined by a label, URL slug, and docs directory.\n- **Category** - a group label within a section's sidebar (e.g., \"Getting Started\")\n- **Link** - an individual page entry within a category, defined by a slug and title\n\n## Drag-and-drop reordering\nYou can reorder items at every level by dragging their handles:\n\n- **Drag categories** between sections or within the same section to change their position\n- **Drag links** between categories or within the same category to reorder them\n\n## Managing sections\n- Click **Add Section** in the toolbar to create a new section. Fill in the label, slug, and directory fields.\n- Click the **edit** button on a section header to open its edit modal, where you can update the label, slug, and directory.\n- Delete a section from its edit modal using the delete button. The root section cannot be deleted.\n\n### The default section\nOne section should have an empty slug (`\"\"`). This is the default/root section that serves pages at the root URL. Pages not assigned to any other section belong here.\n\n### Frontmatter-based sections\nYou can also define sections purely through page frontmatter without using the Navigation Builder. Add a `section` field to your MDX frontmatter and Doccupine will create sections automatically. See the [Sections documentation](/sections) for details.\n\n## Managing categories\n- Click **Add Category** within a section to create a new group\n- Click the **edit** button on a category to open its edit modal, where you can rename it or delete it\n\n## Adding links\nWithin each category, click **Add files** to open a popover that lists available MDX files not yet included in the navigation. You can:\n\n- **Search** by file name to filter the list\n- **Select** one or more files using checkboxes\n- Click **Add** to insert them as links in the category\n\nTo remove a link, click the **delete** button next to it.\n\n## Regenerate from files\nThe toolbar includes a **Regenerate** button that rebuilds the entire navigation tree from your MDX files' frontmatter (`category`, `categoryOrder`, and `order` fields). A confirmation modal appears before any existing manual navigation is replaced.\n\n<Callout type=\"warning\">\n  Regenerating from files replaces your current navigation structure. This cannot be undone.\n</Callout>\n\n## Auto-generated vs. manual\nIf you don't configure navigation at all, Doccupine automatically builds your sidebar from page frontmatter. The Navigation Builder is only needed when you want explicit control over the order and grouping.\n\n## How it works\nWhen you save, the Navigation Builder writes two files to your repository as pending changes:\n\n- `navigation.json` - the category and link structure for each section\n- `sections.json` - the list of sections with their labels, slugs, and directories\n\n**Array format** for single-section sites (`navigation.json`):\n```json\n[\n  {\n    \"label\": \"Getting Started\",\n    \"links\": [\n      { \"slug\": \"getting-started\", \"title\": \"Quick Start\" }\n    ]\n  }\n]\n```\n\n**Object format** for multi-section sites (`navigation.json`):\n```json\n{\n  \"\": [\n    { \"label\": \"General\", \"links\": [{ \"slug\": \"\", \"title\": \"Introduction\" }] }\n  ],\n  \"api\": [\n    { \"label\": \"Auth\", \"links\": [{ \"slug\": \"api/auth\", \"title\": \"Authentication\" }] }\n  ]\n}\n```\n\n**Sections** (`sections.json`):\n```json\n[\n  { \"label\": \"Docs\", \"slug\": \"\" },\n  { \"label\": \"API Reference\", \"slug\": \"api\" }\n]\n```";
+export declare const platformNavigationSettingsMdxTemplate = "---\ntitle: \"Navigation Settings\"\ndescription: \"Define the sidebar structure for your documentation site using the drag-and-drop Navigation Builder.\"\ndate: \"2026-02-24\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 2\nsection: \"Platform\"\n---\n\n# Navigation Settings\n\nThe Navigation Builder lets you define your sidebar structure through a visual, drag-and-drop interface. It lives inside the **File Explorer** as a dedicated **Navigation** tab, alongside the Files and Media tabs.\n\n## Structure\n\nNavigation is organized into three levels:\n\n- **Section** - a top-level area of your site (e.g., \"Docs\", \"API Reference\"). Each section appears as a tab below the site header and has its own sidebar. Sections are defined by a label, URL slug, and docs directory.\n- **Category** - a group label within a section's sidebar (e.g., \"Getting Started\")\n- **Link** - an individual page entry within a category, defined by a slug and title\n\n## Drag-and-drop reordering\n\nYou can reorder items at every level by dragging their handles:\n\n- **Drag categories** between sections or within the same section to change their position\n- **Drag links** between categories or within the same category to reorder them\n\n## Managing sections\n\n- Click **Add Section** in the toolbar to create a new section. Fill in the label, slug, and directory fields.\n- Click the **edit** button on a section header to open its edit modal, where you can update the label, slug, and directory.\n- Delete a section from its edit modal using the delete button. The root section cannot be deleted.\n\n### The default section\n\nOne section should have an empty slug (`\"\"`). This is the default/root section that serves pages at the root URL. Pages not assigned to any other section belong here.\n\n### Frontmatter-based sections\n\nYou can also define sections purely through page frontmatter without using the Navigation Builder. Add a `section` field to your MDX frontmatter and Doccupine will create sections automatically. See the [Sections documentation](/sections) for details.\n\n## Managing categories\n\n- Click **Add Category** within a section to create a new group\n- Click the **edit** button on a category to open its edit modal, where you can rename it or delete it\n\n## Adding links\n\nWithin each category, click **Add files** to open a popover that lists available MDX files not yet included in the navigation. You can:\n\n- **Search** by file name to filter the list\n- **Select** one or more files using checkboxes\n- Click **Add** to insert them as links in the category\n\nTo remove a link, click the **delete** button next to it.\n\n## Regenerate from files\n\nThe toolbar includes a **Regenerate** button that rebuilds the entire navigation tree from your MDX files' frontmatter (`category`, `categoryOrder`, and `order` fields). A confirmation modal appears before any existing manual navigation is replaced.\n\n<Callout type=\"warning\">\n  Regenerating from files replaces your current navigation structure. This cannot be undone.\n</Callout>\n\n## Auto-generated vs. manual\n\nIf you don't configure navigation at all, Doccupine automatically builds your sidebar from page frontmatter. The Navigation Builder is only needed when you want explicit control over the order and grouping.\n\n## How it works\n\nWhen you save, the Navigation Builder writes two files to your repository as pending changes:\n\n- `navigation.json` - the category and link structure for each section\n- `sections.json` - the list of sections with their labels, slugs, and directories\n\n**Array format** for single-section sites (`navigation.json`):\n\n```json\n[\n  {\n    \"label\": \"Getting Started\",\n    \"links\": [{ \"slug\": \"getting-started\", \"title\": \"Quick Start\" }]\n  }\n]\n```\n\n**Object format** for multi-section sites (`navigation.json`):\n\n```json\n{\n  \"\": [\n    { \"label\": \"General\", \"links\": [{ \"slug\": \"\", \"title\": \"Introduction\" }] }\n  ],\n  \"api\": [\n    {\n      \"label\": \"Auth\",\n      \"links\": [{ \"slug\": \"api/auth\", \"title\": \"Authentication\" }]\n    }\n  ]\n}\n```\n\n**Sections** (`sections.json`):\n\n```json\n[\n  { \"label\": \"Docs\", \"slug\": \"\" },\n  { \"label\": \"API Reference\", \"slug\": \"api\" }\n]\n```";

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

@@ -7,10 +7,13 @@ categoryOrder: 2
 order: 2
 section: "Platform"
 ---
+
 # Navigation Settings
+
 The Navigation Builder lets you define your sidebar structure through a visual, drag-and-drop interface. It lives inside the **File Explorer** as a dedicated **Navigation** tab, alongside the Files and Media tabs.
 
 ## Structure
+
 Navigation is organized into three levels:
 
 - **Section** - a top-level area of your site (e.g., "Docs", "API Reference"). Each section appears as a tab below the site header and has its own sidebar. Sections are defined by a label, URL slug, and docs directory.
@@ -18,27 +21,33 @@ Navigation is organized into three levels:
 - **Link** - an individual page entry within a category, defined by a slug and title
 
 ## Drag-and-drop reordering
+
 You can reorder items at every level by dragging their handles:
 
 - **Drag categories** between sections or within the same section to change their position
 - **Drag links** between categories or within the same category to reorder them
 
 ## Managing sections
+
 - Click **Add Section** in the toolbar to create a new section. Fill in the label, slug, and directory fields.
 - Click the **edit** button on a section header to open its edit modal, where you can update the label, slug, and directory.
 - Delete a section from its edit modal using the delete button. The root section cannot be deleted.
 
 ### The default section
+
 One section should have an empty slug (\`""\`). This is the default/root section that serves pages at the root URL. Pages not assigned to any other section belong here.
 
 ### Frontmatter-based sections
+
 You can also define sections purely through page frontmatter without using the Navigation Builder. Add a \`section\` field to your MDX frontmatter and Doccupine will create sections automatically. See the [Sections documentation](/sections) for details.
 
 ## Managing categories
+
 - Click **Add Category** within a section to create a new group
 - Click the **edit** button on a category to open its edit modal, where you can rename it or delete it
 
 ## Adding links
+
 Within each category, click **Add files** to open a popover that lists available MDX files not yet included in the navigation. You can:
 
 - **Search** by file name to filter the list
@@ -48,6 +57,7 @@ Within each category, click **Add files** to open a popover that lists available
 To remove a link, click the **delete** button next to it.
 
 ## Regenerate from files
+
 The toolbar includes a **Regenerate** button that rebuilds the entire navigation tree from your MDX files' frontmatter (\`category\`, \`categoryOrder\`, and \`order\` fields). A confirmation modal appears before any existing manual navigation is replaced.
 
 <Callout type="warning">
@@ -55,39 +65,45 @@ The toolbar includes a **Regenerate** button that rebuilds the entire navigation
 </Callout>
 
 ## Auto-generated vs. manual
+
 If you don't configure navigation at all, Doccupine automatically builds your sidebar from page frontmatter. The Navigation Builder is only needed when you want explicit control over the order and grouping.
 
 ## How it works
+
 When you save, the Navigation Builder writes two files to your repository as pending changes:
 
 - \`navigation.json\` - the category and link structure for each section
 - \`sections.json\` - the list of sections with their labels, slugs, and directories
 
 **Array format** for single-section sites (\`navigation.json\`):
+
 \`\`\`json
 [
   {
     "label": "Getting Started",
-    "links": [
-      { "slug": "getting-started", "title": "Quick Start" }
-    ]
+    "links": [{ "slug": "getting-started", "title": "Quick Start" }]
   }
 ]
 \`\`\`
 
 **Object format** for multi-section sites (\`navigation.json\`):
+
 \`\`\`json
 {
   "": [
     { "label": "General", "links": [{ "slug": "", "title": "Introduction" }] }
   ],
   "api": [
-    { "label": "Auth", "links": [{ "slug": "api/auth", "title": "Authentication" }] }
+    {
+      "label": "Auth",
+      "links": [{ "slug": "api/auth", "title": "Authentication" }]
+    }
   ]
 }
 \`\`\`
 
 **Sections** (\`sections.json\`):
+
 \`\`\`json
 [
   { "label": "Docs", "slug": "" },

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

@@ -1 +1 @@
-export declare const platformProjectSettingsMdxTemplate = "---\ntitle: \"Project Settings\"\ndescription: \"Rename or delete your documentation project.\"\ndate: \"2026-02-19\"\ncategory: \"Account\"\ncategoryOrder: 4\norder: 2\nsection: \"Platform\"\n---\n# Project Settings\nThe Project settings page provides basic project management options including renaming and deletion.\n\n## Renaming a project\nEnter a new name for your project and click **Save**. The project name is used in the dashboard and sidebar - it does not affect your site's URL or domain.\n\n## Deleting a project\n\n<Callout type=\"warning\">\n  Deleting a project is permanent and cannot be undone.\n</Callout>\n\nTo delete a project:\n\n1. Navigate to the **Project** settings page.\n2. In the **Danger Zone** section, click **Delete Project**.\n3. Type your project's name to confirm.\n4. Click **Delete**.\n\nDeletion removes:\n- The GitHub repository (if managed by Doccupine)\n- The hosted deployment\n- All pending changes\n- All team member associations\n- The project record\n\nIf you're using a user-connected GitHub repository, the repo in your GitHub account is preserved - only the Doccupine project and its deployment are removed.";
+export declare const platformProjectSettingsMdxTemplate = "---\ntitle: \"Project Settings\"\ndescription: \"Rename or delete your documentation project.\"\ndate: \"2026-02-19\"\ncategory: \"Account\"\ncategoryOrder: 4\norder: 2\nsection: \"Platform\"\n---\n\n# Project Settings\n\nThe Project settings page provides basic project management options including renaming and deletion.\n\n## Renaming a project\n\nEnter a new name for your project and click **Save**. The project name is used in the dashboard and sidebar - it does not affect your site's URL or domain.\n\n## Deleting a project\n\n<Callout type=\"warning\">\n  Deleting a project is permanent and cannot be undone.\n</Callout>\n\nTo delete a project:\n\n1. Navigate to the **Project** settings page.\n2. In the **Danger Zone** section, click **Delete Project**.\n3. Type your project's name to confirm.\n4. Click **Delete**.\n\nDeletion removes:\n\n- The GitHub repository (if managed by Doccupine)\n- The hosted deployment\n- All pending changes\n- All team member associations\n- The project record\n\nIf you're using a user-connected GitHub repository, the repo in your GitHub account is preserved - only the Doccupine project and its deployment are removed.";

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

@@ -7,10 +7,13 @@ categoryOrder: 4
 order: 2
 section: "Platform"
 ---
+
 # Project Settings
+
 The Project settings page provides basic project management options including renaming and deletion.
 
 ## Renaming a project
+
 Enter a new name for your project and click **Save**. The project name is used in the dashboard and sidebar - it does not affect your site's URL or domain.
 
 ## Deleting a project
@@ -27,6 +30,7 @@ To delete a project:
 4. Click **Delete**.
 
 Deletion removes:
+
 - The GitHub repository (if managed by Doccupine)
 - The hosted deployment
 - All pending changes

package/dist/templates/mdx/platform/publishing.mdx.d.ts

@@ -1 +1 @@
-export declare const platformPublishingMdxTemplate = "---\ntitle: \"Publishing Changes\"\ndescription: \"Commit your edits to GitHub and deploy your documentation site with one click.\"\ndate: \"2026-02-19\"\ncategory: \"Editing\"\ncategoryOrder: 1\norder: 1\nsection: \"Platform\"\n---\n# Publishing Changes\nWhen you edit files in Doccupine, your changes are staged as pending. Nothing goes live until you explicitly publish.\n\n## The publish workflow\n\n1. Make edits to your files using the file editor.\n2. Click the **Publish** button in the project header. A badge shows the number of pending changes.\n3. Review the list of modified, deleted, and new files in the publish modal.\n4. Optionally write a custom commit message (defaults to \"Update docs via Doccupine\").\n5. Click **Publish Changes**.\n\nDoccupine then:\n- Commits all pending changes to your GitHub repository\n- Triggers a new deployment\n- Clears all pending changes from the staging area\n\n<Callout type=\"note\">\n  The deployment status badge in the project header updates as your site builds. It cycles through **queued**, **building**, and **ready** (or **error** if something went wrong).\n</Callout>\n\n## Discarding changes\nIf you want to undo your pending edits, click **Discard All Changes** in the publish modal. This removes all staged changes without committing anything.\n\n## File status badges\nIn the publish modal, each file shows a badge indicating what changed:\n\n- **mod** - the file was modified\n- **del** - the file was deleted\n- **bin** - the file is a binary asset (image, font, etc.)\n\n## Auto-deploy from GitHub\nIf you're using a user-connected GitHub repository and push changes directly (outside of Doccupine), the webhook triggers an automatic redeploy. This means you can use Doccupine's editor and Git-based workflows interchangeably.";
+export declare const platformPublishingMdxTemplate = "---\ntitle: \"Publishing Changes\"\ndescription: \"Commit your edits to GitHub and deploy your documentation site with one click.\"\ndate: \"2026-02-19\"\ncategory: \"Editing\"\ncategoryOrder: 1\norder: 1\nsection: \"Platform\"\n---\n\n# Publishing Changes\n\nWhen you edit files in Doccupine, your changes are staged as pending. Nothing goes live until you explicitly publish.\n\n## The publish workflow\n\n1. Make edits to your files using the file editor.\n2. Click the **Publish** button in the project header. A badge shows the number of pending changes.\n3. Review the list of modified, deleted, and new files in the publish modal.\n4. Optionally write a custom commit message (defaults to \"Update docs via Doccupine\").\n5. Click **Publish Changes**.\n\nDoccupine then:\n\n- Commits all pending changes to your GitHub repository\n- Triggers a new deployment\n- Clears all pending changes from the staging area\n\n<Callout type=\"note\">\n  The deployment status badge in the project header updates as your site builds. It cycles through **queued**, **building**, and **ready** (or **error** if something went wrong).\n</Callout>\n\n## Discarding changes\n\nIf you want to undo your pending edits, click **Discard All Changes** in the publish modal. This removes all staged changes without committing anything.\n\n## File status badges\n\nIn the publish modal, each file shows a badge indicating what changed:\n\n- **mod** - the file was modified\n- **del** - the file was deleted\n- **bin** - the file is a binary asset (image, font, etc.)\n\n## Auto-deploy from GitHub\n\nIf you're using a user-connected GitHub repository and push changes directly (outside of Doccupine), the webhook triggers an automatic redeploy. This means you can use Doccupine's editor and Git-based workflows interchangeably.";

package/dist/templates/mdx/platform/publishing.mdx.js

@@ -7,7 +7,9 @@ categoryOrder: 1
 order: 1
 section: "Platform"
 ---
+
 # Publishing Changes
+
 When you edit files in Doccupine, your changes are staged as pending. Nothing goes live until you explicitly publish.
 
 ## The publish workflow
@@ -19,6 +21,7 @@ When you edit files in Doccupine, your changes are staged as pending. Nothing go
 5. Click **Publish Changes**.
 
 Doccupine then:
+
 - Commits all pending changes to your GitHub repository
 - Triggers a new deployment
 - Clears all pending changes from the staging area
@@ -28,9 +31,11 @@ Doccupine then:
 </Callout>
 
 ## Discarding changes
+
 If you want to undo your pending edits, click **Discard All Changes** in the publish modal. This removes all staged changes without committing anything.
 
 ## File status badges
+
 In the publish modal, each file shows a badge indicating what changed:
 
 - **mod** - the file was modified
@@ -38,4 +43,5 @@ In the publish modal, each file shows a badge indicating what changed:
 - **bin** - the file is a binary asset (image, font, etc.)
 
 ## Auto-deploy from GitHub
+
 If you're using a user-connected GitHub repository and push changes directly (outside of Doccupine), the webhook triggers an automatic redeploy. This means you can use Doccupine's editor and Git-based workflows interchangeably.`;

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

@@ -1 +1 @@
-export declare const platformSiteSettingsMdxTemplate = "---\ntitle: \"Site Settings\"\ndescription: \"Configure your documentation site's name, description, icon, and image.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 0\nsection: \"Platform\"\n---\n# Site Settings\nThe Site settings page lets you configure the core metadata for your documentation site. These values are stored in `config.json` at the root of your repository.\n\n## Fields\n\n### Name\nThe name of your documentation site. This appears in the site header and browser tab title.\n\n### Description\nA short description of your documentation. Used in meta tags for search engine optimization and social media previews.\n\n### Favicon\nUpload a favicon image that appears in browser tabs. Supported formats include PNG, ICO, and SVG. Use the file upload button to select an image from your computer.\n\n### Preview image\nUpload an image used for social media and OpenGraph previews. This is the image that appears when your documentation URL is shared on platforms like Twitter, Slack, or Discord.\n\n### Site URL\nThe public URL of your deployed documentation site, such as `https://docs.example.com`. This value is used as the base URL when generating `sitemap.xml` and `robots.txt`, so search engines can discover and index your pages correctly. You can override this at deploy time by setting the `NEXT_PUBLIC_SITE_URL` environment variable.\n\n<Callout type=\"note\">\n  Changes to site settings are staged as pending changes, just like file edits. Click **Publish** to commit them to your repository and trigger a deploy.\n</Callout>\n\n## How it works\nBehind the scenes, the Site settings page reads and writes `config.json` in your repository. You can also edit this file directly in the file editor if you prefer. See the [Globals](/globals) page for the full configuration reference.\n\n```json\n{\n  \"name\": \"My Documentation\",\n  \"description\": \"Documentation for my project\",\n  \"icon\": \"/favicon.png\",\n  \"image\": \"/preview.png\",\n  \"url\": \"https://docs.example.com\"\n}\n```";
+export declare const platformSiteSettingsMdxTemplate = "---\ntitle: \"Site Settings\"\ndescription: \"Configure your documentation site's name, description, icon, and image.\"\ndate: \"2026-02-19\"\ncategory: \"Configuration\"\ncategoryOrder: 2\norder: 0\nsection: \"Platform\"\n---\n\n# Site Settings\n\nThe Site settings page lets you configure the core metadata for your documentation site. These values are stored in `config.json` at the root of your repository.\n\n## Fields\n\n### Name\n\nThe name of your documentation site. This appears in the site header and browser tab title.\n\n### Description\n\nA short description of your documentation. Used in meta tags for search engine optimization and social media previews.\n\n### Favicon\n\nUpload a favicon image that appears in browser tabs. Supported formats include PNG, ICO, and SVG. Use the file upload button to select an image from your computer.\n\n### Preview image\n\nUpload an image used for social media and OpenGraph previews. This is the image that appears when your documentation URL is shared on platforms like Twitter, Slack, or Discord.\n\n### Site URL\n\nThe public URL of your deployed documentation site, such as `https://docs.example.com`. This value is used as the base URL when generating `sitemap.xml` and `robots.txt`, so search engines can discover and index your pages correctly. You can override this at deploy time by setting the `NEXT_PUBLIC_SITE_URL` environment variable.\n\n<Callout type=\"note\">\n  Changes to site settings are staged as pending changes, just like file edits. Click **Publish** to commit them to your repository and trigger a deploy.\n</Callout>\n\n## How it works\n\nBehind the scenes, the Site settings page reads and writes `config.json` in your repository. You can also edit this file directly in the file editor if you prefer. See the [Globals](/globals) page for the full configuration reference.\n\n```json\n{\n  \"name\": \"My Documentation\",\n  \"description\": \"Documentation for my project\",\n  \"icon\": \"/favicon.png\",\n  \"image\": \"/preview.png\",\n  \"url\": \"https://docs.example.com\"\n}\n```";

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

@@ -7,24 +7,31 @@ categoryOrder: 2
 order: 0
 section: "Platform"
 ---
+
 # Site Settings
+
 The Site settings page lets you configure the core metadata for your documentation site. These values are stored in \`config.json\` at the root of your repository.
 
 ## Fields
 
 ### Name
+
 The name of your documentation site. This appears in the site header and browser tab title.
 
 ### Description
+
 A short description of your documentation. Used in meta tags for search engine optimization and social media previews.
 
 ### Favicon
+
 Upload a favicon image that appears in browser tabs. Supported formats include PNG, ICO, and SVG. Use the file upload button to select an image from your computer.
 
 ### Preview image
+
 Upload an image used for social media and OpenGraph previews. This is the image that appears when your documentation URL is shared on platforms like Twitter, Slack, or Discord.
 
 ### Site URL
+
 The public URL of your deployed documentation site, such as \`https://docs.example.com\`. This value is used as the base URL when generating \`sitemap.xml\` and \`robots.txt\`, so search engines can discover and index your pages correctly. You can override this at deploy time by setting the \`NEXT_PUBLIC_SITE_URL\` environment variable.
 
 <Callout type="note">
@@ -32,6 +39,7 @@ The public URL of your deployed documentation site, such as \`https://docs.examp
 </Callout>
 
 ## How it works
+
 Behind the scenes, the Site settings page reads and writes \`config.json\` in your repository. You can also edit this file directly in the file editor if you prefer. See the [Globals](/globals) page for the full configuration reference.
 
 \`\`\`json

package/dist/templates/mdx/platform/team-members.mdx.d.ts

@@ -1 +1 @@
-export declare const platformTeamMembersMdxTemplate = "---\ntitle: \"Team Members\"\ndescription: \"Invite collaborators and manage roles for your documentation project.\"\ndate: \"2026-02-19\"\ncategory: \"Account\"\ncategoryOrder: 4\norder: 0\nsection: \"Platform\"\n---\n# Team Members\nThe Members settings page lets project owners invite collaborators and manage their access levels. Team members can view, edit, or manage billing depending on their assigned role.\n\n## Inviting members\n1. Navigate to your project's **Members** settings.\n2. Enter the collaborator's email address.\n3. Select a role.\n4. Click **Add Member**.\n\nThe invited user will see the project under **Shared Projects** on their dashboard.\n\n## Roles\n\n### Viewer\nCan browse files and view the project, but cannot make edits or publish changes. Useful for stakeholders who need read access.\n\n### Editor\nCan edit files and publish changes. Can also modify site configuration (theme, navigation, fonts, etc.). Cannot manage team members or billing.\n\n### Billing\nCan access the billing management page and Stripe billing portal. Cannot edit files or site configuration.\n\n<Callout type=\"note\">\n  The project **owner** has full access to everything - editing, publishing, configuration, member management, billing, and project deletion.\n</Callout>\n\n## Member limits\nThe number of team members depends on your plan:\n\n- **Pro** - up to 5 members\n- **Enterprise** - unlimited members\n\nThe Members page shows your current count against your plan's limit.\n\n## Removing members\nProject owners can remove any member by clicking the remove button next to their name. Members can also remove themselves from a project by clicking **Leave Project**.";
+export declare const platformTeamMembersMdxTemplate = "---\ntitle: \"Team Members\"\ndescription: \"Invite collaborators and manage roles for your documentation project.\"\ndate: \"2026-02-19\"\ncategory: \"Account\"\ncategoryOrder: 4\norder: 0\nsection: \"Platform\"\n---\n\n# Team Members\n\nThe Members settings page lets project owners invite collaborators and manage their access levels. Team members can view, edit, or manage billing depending on their assigned role.\n\n## Inviting members\n\n1. Navigate to your project's **Members** settings.\n2. Enter the collaborator's email address.\n3. Select a role.\n4. Click **Add Member**.\n\nThe invited user will see the project under **Shared Projects** on their dashboard.\n\n## Roles\n\n### Viewer\n\nCan browse files and view the project, but cannot make edits or publish changes. Useful for stakeholders who need read access.\n\n### Editor\n\nCan edit files and publish changes. Can also modify site configuration (theme, navigation, fonts, etc.). Cannot manage team members or billing.\n\n### Billing\n\nCan access the billing management page and Stripe billing portal. Cannot edit files or site configuration.\n\n<Callout type=\"note\">\n  The project **owner** has full access to everything - editing, publishing, configuration, member management, billing, and project deletion.\n</Callout>\n\n## Member limits\n\nThe number of team members depends on your plan:\n\n- **Pro** - up to 5 members\n- **Enterprise** - unlimited members\n\nThe Members page shows your current count against your plan's limit.\n\n## Removing members\n\nProject owners can remove any member by clicking the remove button next to their name. Members can also remove themselves from a project by clicking **Leave Project**.";

package/dist/templates/mdx/platform/team-members.mdx.js

@@ -7,10 +7,13 @@ categoryOrder: 4
 order: 0
 section: "Platform"
 ---
+
 # Team Members
+
 The Members settings page lets project owners invite collaborators and manage their access levels. Team members can view, edit, or manage billing depending on their assigned role.
 
 ## Inviting members
+
 1. Navigate to your project's **Members** settings.
 2. Enter the collaborator's email address.
 3. Select a role.
@@ -21,12 +24,15 @@ The invited user will see the project under **Shared Projects** on their dashboa
 ## Roles
 
 ### Viewer
+
 Can browse files and view the project, but cannot make edits or publish changes. Useful for stakeholders who need read access.
 
 ### Editor
+
 Can edit files and publish changes. Can also modify site configuration (theme, navigation, fonts, etc.). Cannot manage team members or billing.
 
 ### Billing
+
 Can access the billing management page and Stripe billing portal. Cannot edit files or site configuration.
 
 <Callout type="note">
@@ -34,6 +40,7 @@ Can access the billing management page and Stripe billing portal. Cannot edit fi
 </Callout>
 
 ## Member limits
+
 The number of team members depends on your plan:
 
 - **Pro** - up to 5 members
@@ -42,4 +49,5 @@ The number of team members depends on your plan:
 The Members page shows your current count against your plan's limit.
 
 ## Removing members
+
 Project owners can remove any member by clicking the remove button next to their name. Members can also remove themselves from a project by clicking **Leave Project**.`;