export declare const EN_GETTING_STARTED = "---\ntitle: Getting Started\norder: 1\n---\n\n# Getting Started\n\nWelcome to Monkey-Doc. This page is in **English** \u2014 use the language switcher in the top-right to switch to another language.\n\n## Installation\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\n## How it works\n\nMonkey-Doc scans your `docs/` folder and builds navigation automatically. Organize pages in subfolders to get breadcrumbs and sections.\n";
export declare const EN_INSTALLATION = "---\ntitle: Installation\norder: 2\n---\n\n# Installation\n\nAdd Monkey-Doc to any project in seconds.\n\n## Prerequisites\n\n\n \n Make sure you have Node.js 18 or higher installed.\n \n \n Navigate to the root of your project.\n \n\n\n## Quick start\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\nThat's it! Your documentation server starts at `http://localhost:5173`.\n\n## Manual install\n\n```bash\nnpm install -g monkey-doc\nmonkey-doc init\nmonkey-doc dev\n```\n\n\n Run `monkey-doc init` once per project. It creates a `/docs` folder with\n example files and a `monkey-doc.config.ts` configuration file.\n\n";
export declare const EN_WRITING_GUIDES = "---\ntitle: Writing Guides\norder: 3\n---\n\n# Writing Guides\n\nMonkey-Doc uses **MDX** \u2014 Markdown with JSX components.\n\nWrite plain Markdown and sprinkle in rich components wherever you need them.\n\n## Basic markdown\n\nAll standard Markdown syntax works out of the box:\n\n- **Bold**, _italic_, `inline code`\n- [Links](https://example.com)\n- Images: ``\n- Tables, blockquotes, horizontal rules\n\n## Frontmatter\n\nEvery page supports YAML frontmatter:\n\n```yaml\n---\ntitle: My Page Title\norder: 1\n---\n```\n\n- **title** \u2014 overrides the filename as the page title\n- **order** \u2014 controls navigation order (lower = first)\n\n## Using components\n\nImport is not required \u2014 all built-in components are globally available.\n\n```mdx\n\n Watch out for this edge case!\n\n```\n\nSee [Components](/en/components) for the full component reference.\n\n## Organizing with folders\n\nYou can nest pages inside folders to group related content. The folder structure maps directly to the sidebar navigation.\n\n\n \n \n \n \n \n \n \n \n \n \n \n\n\nEach folder automatically becomes a collapsible section in the sidebar. The section title is derived from the folder name (kebab-case is converted to title case).\n\nTo control the order of sections and pages, use the `order` frontmatter field \u2014 it works the same for files inside folders.\n\n\n Folders can be nested as deeply as you need. There is no limit on nesting depth.\n\n";
export declare const EN_COMPONENTS = "---\ntitle: Components\norder: 4\n---\n\n# Components\n\nMonkey-Doc ships with a set of built-in MDX components you can use anywhere.\n\n## Callout\n\nHighlight important information.\n\nThis is an **info** callout.\n\nThis is a **warning** callout.\n\nThis is a **success** callout.\n\n```mdx\nYour message here.\n```\n\n## Steps\n\nWalk users through a sequence.\n\n\n Do this first.\n Then do this.\n Finally, do this.\n\n\n```mdx\n\n Do this first.\n Then do this.\n\n```\n\n## Card\n\nGroup related content visually.\n\n\n\n```mdx\n\n```\n\n## Tabs\n\nDisplay content in tabbed panels.\n\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n\n```mdx\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n```\n\n## FileTree\n\nVisualize a folder structure.\n\n\n \n \n \n \n \n \n \n \n\n\nUse the `highlight` prop on a `` to draw attention to a specific file.\n\n```mdx\n\n \n \n \n \n \n \n\n```\n\n## CodeGroup\n\nShow multiple code snippets in tabs \u2014 ideal for package manager commands or multi-language examples.\n\n\n\n```bash\nnpm install monkey-doc\n```\n\n```bash\nyarn add monkey-doc\n```\n\n```bash\npnpm add monkey-doc\n```\n\n\n\n## Accordion\n\nCollapsible sections, great for FAQs or optional details.\n\n\n Monkey-Doc is a documentation tool focused on product guides and storytelling, as an alternative to Storybook.\n\n\n\n No \u2014 run `npx monkey-doc init` and you're ready to go. Zero configuration required.\n\n\n\n Yes, folders can be nested as deeply as needed. The sidebar is generated automatically from your file structure.\n\n\n```mdx\n\n Your answer here.\n\n\n\n This one starts expanded.\n\n```\n\n## Badge\n\nInline labels for status, versioning, or categorization.\n\n\n Default\n Info\n Success\n Warning\n Error\n New\n Beta\n Deprecated\n
\n\nUse badges inline in prose too \u2014 for example, this feature is New in v2.\n\n```mdx\nNew\nBeta\nDeprecated\n```\n\nAvailable variants: `default` \u00B7 `info` \u00B7 `success` \u00B7 `warning` \u00B7 `error` \u00B7 `new` \u00B7 `beta` \u00B7 `deprecated`\n\n## Mermaid\n\nRender diagrams from [Mermaid](https://mermaid.js.org) syntax.\n\n```mermaid\nflowchart LR\n A[Write MDX] --> B[Run monkey-doc dev]\n B --> C{Happy?}\n C -- Yes --> D[Ship it \uD83D\uDE80]\n C -- No --> A\n```\n\n```mermaid\nsequenceDiagram\n Developer->>monkey-doc: npx monkey-doc dev\n monkey-doc->>Browser: Serves docs at localhost:5173\n Browser-->>Developer: Live preview with hot reload\n```\n\n## Property\n\nDocument a prop, parameter, or configuration option with its type, default value, and description.\n\n\n \n The title of the page or section.\n \n \n Controls the position of the page in the sidebar. Lower values appear first.\n \n \n A short description shown in search results and meta tags.\n \n \n Sets the color theme for the documentation site.\n \n \n This prop is no longer used. Remove it from your config.\n \n\n\n```mdx\n\n \n The title of the page.\n \n \n Position in the sidebar.\n \n\n```\n\n## Video\n\nEmbed a video from a URL or a YouTube / Vimeo link.\n\n```mdx\n\n\n\n```\n\n## Breadcrumb\n\nAn inline breadcrumb trail for content pages.\n\n\n\n```mdx\n\n\n```\n\n## Diff\n\nShow a before/after code diff with green/red line highlighting.\n\n\n\n```mdx\n\n```\n\n## Stepper\n\nAn interactive checklist-style stepper. Click a step to mark it complete.\n\n\n \n Run `git clone https://github.com/your-org/your-project.git` to get a local copy.\n \n \n Navigate into the project folder and run `npm install`.\n \n \n Run `npm run dev` and open `http://localhost:5173` in your browser.\n \n\n\n```mdx\n\n \n Run `git clone ...`\n \n \n Run `npm install`.\n \n\n```\n\n## LinkButton\n\nA styled link that looks like a button. Three variants and three sizes \u2014 works great for CTAs, download links, or navigation.\n\n\n Get started\n Read the docs\n Learn more\n
\n\nExternal links automatically get a `\u2197` icon and open in a new tab:\n\nView on GitHub\n\n```mdx\nGet started\nRead more\nGitHub \u2197\n```\n\nProps: `href` \u00B7 `variant` (`default` / `outline` / `ghost`) \u00B7 `size` (`sm` / `md` / `lg`) \u00B7 `external` (auto-detected from URL)\n\n## Charts\n\nThree chart types powered by Chart.js. All adapt to dark mode automatically.\n\n### BarChart\n\n\n\n```mdx\n\n```\n\nAdd `horizontal` for a horizontal layout. Use `height` to adjust the chart height (default `280`).\n\n### DonutChart\n\n\n\n```mdx\n\n```\n\n### RadarChart\n\n\n\n```mdx\n\n```\n";
export declare const EN_BEST_PRACTICES = "---\ntitle: Best Practices\norder: 5\n---\n\n# Best Practices\n\nTips for writing great documentation with Monkey-Doc.\n\n## Structure your docs like a story\n\nGood documentation flows. Each page should answer one question clearly.\n\n\n Think of each guide as a short article \u2014 one idea, clear flow, concrete examples.\n\n\n## Use the right component\n\n| Need | Component |\n|------|-----------|\n| Important note | `` |\n| Sequential process | `` |\n| Multiple options | `` |\n| Feature highlight | `` |\n| Code sample | fenced code block |\n\n## Folder structure\n\nOrganise docs with folders for sections:\n\n```\ndocs/\n en/\n getting-started.mdx\n installation.mdx\n guides/\n writing-docs.mdx\n reference/\n api.mdx\n```\n\nFolders appear as collapsible sections in the sidebar.\n\n## Frontmatter matters\n\nAlways set `title` and `order` in frontmatter \u2014 they control what users see in navigation.\n";
export declare const FR_GETTING_STARTED = "---\ntitle: D\u00E9marrage\norder: 1\n---\n\n# D\u00E9marrage\n\nBienvenue sur Monkey-Doc. Cette page est en **fran\u00E7ais** \u2014 utilisez le s\u00E9lecteur de langue en haut \u00E0 droite pour changer de langue.\n\n## Installation\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\n## Comment \u00E7a marche\n\nMonkey-Doc scanne votre dossier `docs/` et construit la navigation automatiquement. Organisez vos pages dans des sous-dossiers pour obtenir le fil d'Ariane et les sections.\n";
export declare const FR_INSTALLATION = "---\ntitle: Installation\norder: 2\n---\n\n# Installation\n\nAjoutez Monkey-Doc \u00E0 n'importe quel projet en quelques secondes.\n\n## Pr\u00E9requis\n\n\n \n Assurez-vous d'avoir Node.js 18 ou sup\u00E9rieur install\u00E9.\n \n \n Naviguez jusqu'\u00E0 la racine de votre projet.\n \n\n\n## D\u00E9marrage rapide\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\nC'est tout ! Votre serveur de documentation d\u00E9marre sur `http://localhost:5173`.\n\n## Installation manuelle\n\n```bash\nnpm install -g monkey-doc\nmonkey-doc init\nmonkey-doc dev\n```\n\n\n Lancez `monkey-doc init` une seule fois par projet. Cela cr\u00E9e un dossier `/docs` avec\n des fichiers d'exemple et un fichier de configuration `monkey-doc.config.ts`.\n\n";
export declare const FR_WRITING_GUIDES = "---\ntitle: \u00C9crire des guides\norder: 3\n---\n\n# \u00C9crire des guides\n\nMonkey-Doc utilise **MDX** \u2014 du Markdown avec des composants JSX.\n\nR\u00E9digez du Markdown classique et int\u00E9grez des composants enrichis l\u00E0 o\u00F9 vous en avez besoin.\n\n## Markdown de base\n\nToute la syntaxe Markdown standard fonctionne nativement :\n\n- **Gras**, _italique_, `code en ligne`\n- [Liens](https://example.com)\n- Images : ``\n- Tableaux, citations, s\u00E9parateurs horizontaux\n\n## Frontmatter\n\nChaque page supporte le frontmatter YAML :\n\n```yaml\n---\ntitle: Titre de ma page\norder: 1\n---\n```\n\n- **title** \u2014 remplace le nom de fichier comme titre de la page\n- **order** \u2014 contr\u00F4le l'ordre de navigation (plus petit = en premier)\n\n## Utiliser les composants\n\nAucun import n\u00E9cessaire \u2014 tous les composants int\u00E9gr\u00E9s sont disponibles globalement.\n\n```mdx\n\n Attention \u00E0 ce cas limite !\n\n```\n\nConsultez [Composants](/fr/components) pour la r\u00E9f\u00E9rence compl\u00E8te des composants.\n\n## Organiser avec des dossiers\n\nVous pouvez imbriquer des pages dans des dossiers pour regrouper du contenu li\u00E9. La structure de dossiers se refl\u00E8te directement dans la navigation de la sidebar.\n\n\n \n \n \n \n \n \n \n \n \n \n \n\n\nChaque dossier devient automatiquement une section repliable dans la sidebar. Le titre de la section est d\u00E9riv\u00E9 du nom du dossier (le kebab-case est converti en titre lisible).\n\nPour contr\u00F4ler l'ordre des sections et des pages, utilisez le champ `order` en frontmatter \u2014 il fonctionne de la m\u00EAme fa\u00E7on pour les fichiers \u00E0 l'int\u00E9rieur des dossiers.\n\n\n Les dossiers peuvent \u00EAtre imbriqu\u00E9s aussi profond\u00E9ment que n\u00E9cessaire. Il n'y a pas de limite de profondeur.\n\n";
export declare const FR_COMPONENTS = "---\ntitle: Composants\norder: 4\n---\n\n# Composants\n\nMonkey-Doc est livr\u00E9 avec un ensemble de composants MDX int\u00E9gr\u00E9s utilisables partout.\n\n## Callout\n\nMettez en \u00E9vidence des informations importantes.\n\nCeci est un callout **info**.\n\nCeci est un callout **avertissement**.\n\nCeci est un callout **succ\u00E8s**.\n\n```mdx\nVotre message ici.\n```\n\n## Steps\n\nGuidez les utilisateurs \u00E0 travers une s\u00E9quence.\n\n\n Faites ceci en premier.\n Puis faites cela.\n Enfin, faites ceci.\n\n\n```mdx\n\n Faites ceci en premier.\n Puis faites cela.\n\n```\n\n## Card\n\nRegroupez visuellement du contenu li\u00E9.\n\n\n\n```mdx\n\n```\n\n## Tabs\n\nAffichez du contenu dans des panneaux \u00E0 onglets.\n\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n\n```mdx\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n```\n\n## FileTree\n\nVisualisez une structure de dossiers.\n\n\n \n \n \n \n \n \n \n \n\n\nUtilisez la prop `highlight` sur un `` pour attirer l'attention sur un fichier sp\u00E9cifique.\n\n```mdx\n\n \n \n \n\n```\n\n## CodeGroup\n\nAffichez plusieurs extraits de code dans des onglets.\n\n\n\n```bash\nnpm install monkey-doc\n```\n\n```bash\nyarn add monkey-doc\n```\n\n```bash\npnpm add monkey-doc\n```\n\n\n\n## Accordion\n\nSections repliables, id\u00E9ales pour les FAQ ou les d\u00E9tails optionnels.\n\n\n Monkey-Doc est un outil de documentation orient\u00E9 guides produit et storytelling, en alternative \u00E0 Storybook.\n\n\n\n Non \u2014 lancez `npx monkey-doc init` et c'est pr\u00EAt. Z\u00E9ro configuration requise.\n\n\n\n Oui, les dossiers peuvent \u00EAtre imbriqu\u00E9s aussi profond\u00E9ment que n\u00E9cessaire.\n\n\n```mdx\n\n Votre r\u00E9ponse ici.\n\n```\n\n## Badge\n\n\u00C9tiquettes inline pour le statut, le versioning ou la cat\u00E9gorisation.\n\n\n Default\n Info\n Succ\u00E8s\n Attention\n Erreur\n Nouveau\n Beta\n D\u00E9pr\u00E9ci\u00E9\n
\n\n```mdx\nNouveau\nBeta\nD\u00E9pr\u00E9ci\u00E9\n```\n\nVariantes disponibles : `default` \u00B7 `info` \u00B7 `success` \u00B7 `warning` \u00B7 `error` \u00B7 `new` \u00B7 `beta` \u00B7 `deprecated`\n\n## Mermaid\n\nRendu de diagrammes depuis la syntaxe [Mermaid](https://mermaid.js.org).\n\n```mermaid\nflowchart LR\n A[\u00C9crire du MDX] --> B[Lancer monkey-doc dev]\n B --> C{Satisfait ?}\n C -- Oui --> D[D\u00E9ployer \uD83D\uDE80]\n C -- Non --> A\n```\n\n## Property\n\nDocumentez une prop, un param\u00E8tre ou une option de configuration.\n\n\n \n Le titre de la page ou de la section.\n \n \n Contr\u00F4le la position de la page dans la sidebar.\n \n \n D\u00E9finit le th\u00E8me de couleur du site de documentation.\n \n \n Cette prop n'est plus utilis\u00E9e. Retirez-la de votre config.\n \n\n\n```mdx\n\n \n Le titre de la page.\n \n\n```\n\n## Video\n\nInt\u00E9grez une vid\u00E9o depuis une URL ou un lien YouTube / Vimeo.\n\n```mdx\n\n\n\n```\n\n## Breadcrumb\n\nUn fil d'Ariane embarqu\u00E9 dans le contenu.\n\n\n\n```mdx\n\n\n```\n\n## Diff\n\nAffiche un diff avant/apr\u00E8s avec highlighting vert/rouge.\n\n\n\n```mdx\n\n```\n\n## Stepper\n\nUn stepper interactif de type checklist.\n\n\n \n Lancez `git clone https://github.com/votre-org/votre-projet.git`.\n \n \n Naviguez dans le dossier du projet et lancez `npm install`.\n \n \n Lancez `npm run dev` et ouvrez `http://localhost:5173`.\n \n\n\n```mdx\n\n \n Lancez `git clone ...`\n \n\n```\n\n## LinkButton\n\nUn lien stylis\u00E9 en bouton. Trois variantes et trois tailles.\n\n\n Commencer\n Lire la doc\n En savoir plus\n
\n\nLes liens externes re\u00E7oivent automatiquement une ic\u00F4ne `\u2197` et s'ouvrent dans un nouvel onglet :\n\nVoir sur GitHub\n\n```mdx\nCommencer\nLire la suite\nGitHub \u2197\n```\n\nProps : `href` \u00B7 `variant` (`default` / `outline` / `ghost`) \u00B7 `size` (`sm` / `md` / `lg`) \u00B7 `external` (d\u00E9tect\u00E9 automatiquement)\n\n## Graphiques\n\nTrois types de graphiques propuls\u00E9s par Chart.js. Tous s'adaptent automatiquement au dark mode.\n\n### BarChart\n\n\n\n```mdx\n\n```\n\n### DonutChart\n\n\n\n```mdx\n\n```\n\n### RadarChart\n\n\n\n```mdx\n\n```\n";
export declare const FR_BEST_PRACTICES = "---\ntitle: Bonnes pratiques\norder: 5\n---\n\n# Bonnes pratiques\n\nConseils pour \u00E9crire une excellente documentation avec Monkey-Doc.\n\n## Structurez vos docs comme une histoire\n\nUne bonne documentation se lit naturellement. Chaque page doit r\u00E9pondre \u00E0 une seule question clairement.\n\n\n Consid\u00E9rez chaque guide comme un court article \u2014 une id\u00E9e, un fil directeur, des exemples concrets.\n\n\n## Utilisez le bon composant\n\n| Besoin | Composant |\n|--------|-----------|\n| Note importante | `` |\n| Processus s\u00E9quentiel | `` |\n| Plusieurs options | `` |\n| Mise en avant | `` |\n| Exemple de code | bloc de code d\u00E9limit\u00E9 |\n\n## Structure des dossiers\n\nOrganisez les docs avec des dossiers pour les sections :\n\n```\ndocs/\n fr/\n getting-started.mdx\n installation.mdx\n guides/\n writing-docs.mdx\n reference/\n api.mdx\n```\n\nLes dossiers apparaissent comme des sections repliables dans la barre lat\u00E9rale.\n\n## Le frontmatter est important\n\nD\u00E9finissez toujours `title` et `order` dans le frontmatter \u2014 ils contr\u00F4lent ce que les utilisateurs voient dans la navigation.\n";
export declare const DEPLOY_EN = "---\ntitle: Deploy\norder: 6\n---\n\n# Deploy\n\nMonkey-Doc builds a static site you can host anywhere \u2014 Vercel, Netlify, GitHub Pages, Cloudflare Pages, or any static file host.\n\n## Build your docs\n\n```bash\nnpx monkey-doc build\n```\n\nThis outputs a production-ready site to `./docs-dist`. You can change the output directory:\n\n```bash\nnpx monkey-doc build --output public\n```\n\nThe build automatically generates:\n- A `_redirects` file (Netlify / Cloudflare Pages SPA routing)\n- A `.nojekyll` file (GitHub Pages)\n\n\n Run `monkey-doc build` from the root of your project \u2014 the same directory where your `monkey-doc.config.ts` lives.\n\n\n---\n\n## Vercel\n\nThe fastest option. Zero configuration required.\n\n\n \n ```bash\n npm install -g vercel\n ```\n \n \n ```bash\n npx monkey-doc build\n vercel docs-dist --prod\n ```\n \n \n Vercel auto-detects the static output and deploys instantly. Your docs are live at a `*.vercel.app` URL.\n \n\n\n\n On subsequent deploys, just run `npx monkey-doc build && vercel docs-dist --prod` again.\n\n\n---\n\n## Netlify\n\n\n \n 1. Run `npx monkey-doc build`\n 2. Go to [app.netlify.com/drop](https://app.netlify.com/drop)\n 3. Drag the `docs-dist` folder into the browser window\n \n \n ```bash\n npm install -g netlify-cli\n npx monkey-doc build\n netlify deploy --dir docs-dist --prod\n ```\n \n\n\n---\n\n## GitHub Pages\n\n\n \n ```bash\n npx monkey-doc build --output docs-site\n ```\n \n \n ```bash\n git add docs-site\n git commit -m \"docs: build\"\n git subtree push --prefix docs-site origin gh-pages\n ```\n \n \n Go to your repo **Settings \u2192 Pages**, set the source to the `gh-pages` branch, root `/`.\n \n\n\n\n The `.nojekyll` file in the build output tells GitHub Pages not to process the files with Jekyll.\n\n\n---\n\n## Cloudflare Pages\n\n\n \n Go to [Cloudflare Pages](https://pages.cloudflare.com) and connect your GitHub or GitLab repository.\n \n \n | Setting | Value |\n |---|---|\n | Build command | `npx monkey-doc build` |\n | Build output directory | `docs-dist` |\n \n \n Cloudflare Pages builds and deploys automatically on every push.\n \n\n\n---\n\n## Automate with GitHub Actions\n\n```yaml\n# .github/workflows/docs.yml\nname: Deploy Docs\n\non:\n push:\n branches: [main]\n paths:\n - 'docs/**'\n - 'monkey-doc.config.ts'\n\njobs:\n deploy:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-node@v4\n with:\n node-version: 20\n - run: npm ci\n - run: npx monkey-doc build\n - name: Deploy to Vercel\n run: npx vercel docs-dist --prod --token ${{ secrets.VERCEL_TOKEN }}\n```\n\n\n Replace the last step with your platform's deploy action \u2014 Netlify, GitHub Pages (`actions/deploy-pages`), or Cloudflare Pages (`cloudflare/pages-action`).\n\n";
export declare const DEPLOY_FR = "---\ntitle: D\u00E9ployer\norder: 6\n---\n\n# D\u00E9ployer\n\nMonkey-Doc g\u00E9n\u00E8re un site statique que vous pouvez h\u00E9berger n'importe o\u00F9 \u2014 Vercel, Netlify, GitHub Pages, Cloudflare Pages, ou tout h\u00E9bergeur de fichiers statiques.\n\n## Construire la documentation\n\n```bash\nnpx monkey-doc build\n```\n\nLe site de production est g\u00E9n\u00E9r\u00E9 dans `./docs-dist`. Pour changer le dossier de sortie :\n\n```bash\nnpx monkey-doc build --output public\n```\n\nLe build g\u00E9n\u00E8re automatiquement :\n- Un fichier `_redirects` (routage SPA Netlify / Cloudflare Pages)\n- Un fichier `.nojekyll` (GitHub Pages)\n\n\n Ex\u00E9cutez `monkey-doc build` depuis la racine de votre projet \u2014 l\u00E0 o\u00F9 se trouve votre `monkey-doc.config.ts`.\n\n\n---\n\n## Vercel\n\nL'option la plus rapide. Z\u00E9ro configuration n\u00E9cessaire.\n\n\n \n ```bash\n npm install -g vercel\n ```\n \n \n ```bash\n npx monkey-doc build\n vercel docs-dist --prod\n ```\n \n \n Vercel d\u00E9tecte automatiquement le site statique. Vos docs sont en ligne sur une URL `*.vercel.app`.\n \n\n\n\n Pour les d\u00E9ploiements suivants, relancez simplement `npx monkey-doc build && vercel docs-dist --prod`.\n\n\n---\n\n## Netlify\n\n\n \n 1. Lancez `npx monkey-doc build`\n 2. Allez sur [app.netlify.com/drop](https://app.netlify.com/drop)\n 3. Faites glisser le dossier `docs-dist` dans la fen\u00EAtre du navigateur\n \n \n ```bash\n npm install -g netlify-cli\n npx monkey-doc build\n netlify deploy --dir docs-dist --prod\n ```\n \n\n\n---\n\n## GitHub Pages\n\n\n \n ```bash\n npx monkey-doc build --output docs-site\n ```\n \n \n ```bash\n git add docs-site\n git commit -m \"docs: build\"\n git subtree push --prefix docs-site origin gh-pages\n ```\n \n \n Allez dans **Settings \u2192 Pages** de votre d\u00E9p\u00F4t, d\u00E9finissez la source sur la branche `gh-pages`, racine `/`.\n \n\n\n\n Le fichier `.nojekyll` indique \u00E0 GitHub Pages de ne pas traiter les fichiers avec Jekyll.\n\n\n---\n\n## Cloudflare Pages\n\n\n \n Allez sur [Cloudflare Pages](https://pages.cloudflare.com) et connectez votre d\u00E9p\u00F4t GitHub ou GitLab.\n \n \n | Param\u00E8tre | Valeur |\n |---|---|\n | Commande de build | `npx monkey-doc build` |\n | Dossier de sortie | `docs-dist` |\n \n \n Cloudflare Pages build et d\u00E9ploie automatiquement \u00E0 chaque push.\n \n\n\n---\n\n## Automatiser avec GitHub Actions\n\n```yaml\n# .github/workflows/docs.yml\nname: Deploy Docs\n\non:\n push:\n branches: [main]\n paths:\n - 'docs/**'\n - 'monkey-doc.config.ts'\n\njobs:\n deploy:\n runs-on: ubuntu-latest\n steps:\n - uses: actions/checkout@v4\n - uses: actions/setup-node@v4\n with:\n node-version: 20\n - run: npm ci\n - run: npx monkey-doc build\n - name: D\u00E9ployer sur Vercel\n run: npx vercel docs-dist --prod --token ${{ secrets.VERCEL_TOKEN }}\n```\n\n\n Remplacez la derni\u00E8re \u00E9tape par l'action de d\u00E9ploiement de votre plateforme \u2014 Netlify, GitHub Pages (`actions/deploy-pages`), ou Cloudflare Pages (`cloudflare/pages-action`).\n\n";
export declare const CONFIG_FILE = "import { defineConfig } from 'monkey-doc';\n\nexport default defineConfig({\n title: 'My Documentation',\n description: 'Built with Monkey-Doc',\n // github: 'https://github.com/your-org/your-repo',\n // logo: '/logo.svg',\n // docsDir: 'docs',\n});\n";
export declare const GETTING_STARTED = "---\ntitle: Getting Started\norder: 1\n---\n\n# Getting Started\n\nWelcome to Monkey-Doc. This page is in **English** \u2014 use the language switcher in the top-right to switch to another language.\n\n## Installation\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\n## How it works\n\nMonkey-Doc scans your `docs/` folder and builds navigation automatically. Organize pages in subfolders to get breadcrumbs and sections.\n";
export declare const INSTALLATION = "---\ntitle: Installation\norder: 2\n---\n\n# Installation\n\nAdd Monkey-Doc to any project in seconds.\n\n## Prerequisites\n\n\n \n Make sure you have Node.js 18 or higher installed.\n \n \n Navigate to the root of your project.\n \n\n\n## Quick start\n\n```bash\nnpx monkey-doc init\nnpx monkey-doc dev\n```\n\nThat's it! Your documentation server starts at `http://localhost:5173`.\n\n## Manual install\n\n```bash\nnpm install -g monkey-doc\nmonkey-doc init\nmonkey-doc dev\n```\n\n\n Run `monkey-doc init` once per project. It creates a `/docs` folder with\n example files and a `monkey-doc.config.ts` configuration file.\n\n";
export declare const WRITING_GUIDES = "---\ntitle: Writing Guides\norder: 3\n---\n\n# Writing Guides\n\nMonkey-Doc uses **MDX** \u2014 Markdown with JSX components.\n\nWrite plain Markdown and sprinkle in rich components wherever you need them.\n\n## Basic markdown\n\nAll standard Markdown syntax works out of the box:\n\n- **Bold**, _italic_, `inline code`\n- [Links](https://example.com)\n- Images: ``\n- Tables, blockquotes, horizontal rules\n\n## Frontmatter\n\nEvery page supports YAML frontmatter:\n\n```yaml\n---\ntitle: My Page Title\norder: 1\n---\n```\n\n- **title** \u2014 overrides the filename as the page title\n- **order** \u2014 controls navigation order (lower = first)\n\n## Using components\n\nImport is not required \u2014 all built-in components are globally available.\n\n```mdx\n\n Watch out for this edge case!\n\n```\n\nSee [Components](/en/components) for the full component reference.\n\n## Organizing with folders\n\nYou can nest pages inside folders to group related content. The folder structure maps directly to the sidebar navigation.\n\n\n \n \n \n \n \n \n \n \n \n \n \n\n\nEach folder automatically becomes a collapsible section in the sidebar. The section title is derived from the folder name (kebab-case is converted to title case).\n\nTo control the order of sections and pages, use the `order` frontmatter field \u2014 it works the same for files inside folders.\n\n\n Folders can be nested as deeply as you need. There is no limit on nesting depth.\n\n";
export declare const COMPONENTS = "---\ntitle: Components\norder: 4\n---\n\n# Components\n\nMonkey-Doc ships with a set of built-in MDX components you can use anywhere.\n\n## Callout\n\nHighlight important information.\n\nThis is an **info** callout.\n\nThis is a **warning** callout.\n\nThis is a **success** callout.\n\n```mdx\nYour message here.\n```\n\n## Steps\n\nWalk users through a sequence.\n\n\n Do this first.\n Then do this.\n Finally, do this.\n\n\n```mdx\n\n Do this first.\n Then do this.\n\n```\n\n## Card\n\nGroup related content visually.\n\n\n\n```mdx\n\n```\n\n## Tabs\n\nDisplay content in tabbed panels.\n\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n\n```mdx\n\n npm install monkey-doc
\n yarn add monkey-doc
\n pnpm add monkey-doc
\n\n```\n\n## FileTree\n\nVisualize a folder structure.\n\n\n \n \n \n \n \n \n \n \n\n\nUse the `highlight` prop on a `` to draw attention to a specific file.\n\n```mdx\n\n \n \n \n \n \n \n\n```\n\n## CodeGroup\n\nShow multiple code snippets in tabs \u2014 ideal for package manager commands or multi-language examples.\n\n\n\n```bash\nnpm install monkey-doc\n```\n\n```bash\nyarn add monkey-doc\n```\n\n```bash\npnpm add monkey-doc\n```\n\n\n\n## Accordion\n\nCollapsible sections, great for FAQs or optional details.\n\n\n Monkey-Doc is a documentation tool focused on product guides and storytelling, as an alternative to Storybook.\n\n\n\n No \u2014 run `npx monkey-doc init` and you're ready to go. Zero configuration required.\n\n\n\n Yes, folders can be nested as deeply as needed. The sidebar is generated automatically from your file structure.\n\n\n```mdx\n\n Your answer here.\n\n\n\n This one starts expanded.\n\n```\n\n## Badge\n\nInline labels for status, versioning, or categorization.\n\n\n Default\n Info\n Success\n Warning\n Error\n New\n Beta\n Deprecated\n
\n\nUse badges inline in prose too \u2014 for example, this feature is New in v2.\n\n```mdx\nNew\nBeta\nDeprecated\n```\n\nAvailable variants: `default` \u00B7 `info` \u00B7 `success` \u00B7 `warning` \u00B7 `error` \u00B7 `new` \u00B7 `beta` \u00B7 `deprecated`\n\n## Mermaid\n\nRender diagrams from [Mermaid](https://mermaid.js.org) syntax.\n\n```mermaid\nflowchart LR\n A[Write MDX] --> B[Run monkey-doc dev]\n B --> C{Happy?}\n C -- Yes --> D[Ship it \uD83D\uDE80]\n C -- No --> A\n```\n\n```mermaid\nsequenceDiagram\n Developer->>monkey-doc: npx monkey-doc dev\n monkey-doc->>Browser: Serves docs at localhost:5173\n Browser-->>Developer: Live preview with hot reload\n```\n\n## Property\n\nDocument a prop, parameter, or configuration option with its type, default value, and description.\n\n\n \n The title of the page or section.\n \n \n Controls the position of the page in the sidebar. Lower values appear first.\n \n \n A short description shown in search results and meta tags.\n \n \n Sets the color theme for the documentation site.\n \n \n This prop is no longer used. Remove it from your config.\n \n\n\n```mdx\n\n \n The title of the page.\n \n \n Position in the sidebar.\n \n\n```\n\n## Video\n\nEmbed a video from a URL or a YouTube / Vimeo link.\n\n```mdx\n\n\n\n```\n\n## Breadcrumb\n\nAn inline breadcrumb trail for content pages.\n\n\n\n```mdx\n\n\n```\n\n## Diff\n\nShow a before/after code diff with green/red line highlighting.\n\n\n\n```mdx\n\n```\n\n## Stepper\n\nAn interactive checklist-style stepper. Click a step to mark it complete.\n\n\n \n Run `git clone https://github.com/your-org/your-project.git` to get a local copy.\n \n \n Navigate into the project folder and run `npm install`.\n \n \n Run `npm run dev` and open `http://localhost:5173` in your browser.\n \n\n\n```mdx\n\n \n Run `git clone ...`\n \n \n Run `npm install`.\n \n\n```\n\n## LinkButton\n\nA styled link that looks like a button. Three variants and three sizes \u2014 works great for CTAs, download links, or navigation.\n\n\n Get started\n Read the docs\n Learn more\n
\n\nExternal links automatically get a `\u2197` icon and open in a new tab:\n\nView on GitHub\n\n```mdx\nGet started\nRead more\nGitHub \u2197\n```\n\nProps: `href` \u00B7 `variant` (`default` / `outline` / `ghost`) \u00B7 `size` (`sm` / `md` / `lg`) \u00B7 `external` (auto-detected from URL)\n\n## Charts\n\nThree chart types powered by Chart.js. All adapt to dark mode automatically.\n\n### BarChart\n\n\n\n```mdx\n\n```\n\nAdd `horizontal` for a horizontal layout. Use `height` to adjust the chart height (default `280`).\n\n### DonutChart\n\n\n\n```mdx\n\n```\n\n### RadarChart\n\n\n\n```mdx\n\n```\n";
export declare const BEST_PRACTICES = "---\ntitle: Best Practices\norder: 5\n---\n\n# Best Practices\n\nTips for writing great documentation with Monkey-Doc.\n\n## Structure your docs like a story\n\nGood documentation flows. Each page should answer one question clearly.\n\n\n Think of each guide as a short article \u2014 one idea, clear flow, concrete examples.\n\n\n## Use the right component\n\n| Need | Component |\n|------|-----------|\n| Important note | `` |\n| Sequential process | `` |\n| Multiple options | `` |\n| Feature highlight | `` |\n| Code sample | fenced code block |\n\n## Folder structure\n\nOrganise docs with folders for sections:\n\n```\ndocs/\n en/\n getting-started.mdx\n installation.mdx\n guides/\n writing-docs.mdx\n reference/\n api.mdx\n```\n\nFolders appear as collapsible sections in the sidebar.\n\n## Frontmatter matters\n\nAlways set `title` and `order` in frontmatter \u2014 they control what users see in navigation.\n";