From 7cd7caf0a994d2f111cfbc25a5a7b43a2331ef66 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 10:27:39 +0200
Subject: [PATCH 001/199] Create German index for VitePress documentation

Added German documentation for VitePress with features and hero section.
---
 docs/de/index.md | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)
 create mode 100644 docs/de/index.md

diff --git a/docs/de/index.md b/docs/de/index.md
new file mode 100644
index 000000000..a3c487bb8
--- /dev/null
+++ b/docs/de/index.md
@@ -0,0 +1,36 @@
+---
+description: VitePress ist ein auf Vite und Vue basierender Generator für statische Websites, mit dem man aus Markdown ansprechende Dokumentationen erstellen kann.
+layout: home
+
+hero:
+  name: VitePress
+  text: Vite & Vue basierender Generator für statische Websites
+  tagline: Markdown zu wunderschönen Docs in Minuten
+  actions:
+    - theme: brand
+      text: Was ist VitePress?
+      link: ./guide/what-is-vitepress
+    - theme: alt
+      text: Schnellstart
+      link: ./guide/getting-started
+    - theme: alt
+      text: GitHub
+      link: https://github.com/vuejs/vitepress
+  image:
+    src: /vitepress-logo-large.svg
+    alt: VitePress
+
+features:
+  - icon: <span class="memo"></span>
+    title: Fokussieren auf den Inhalt
+    details: Erstelle mühelos wunderschöne Dokumentationsseiten mit Markdown.
+  - icon: <span class="vite"></span>
+    title: Genieße Vite DX
+    details: Sofortiger Serverstart, blitzschnelle Hot-Updates und Plugins aus dem Vite-Ökosystem.
+  - icon: <span class="vue"></span>
+    title: Anpassen mit Vue
+    details: Nutze Vue-Syntax und Komponenten direkt in Markdown, oder eigene Themes mit Vhe.
+  - icon: <span class="rocket"></span>
+    title: Liefer schnelle Seitem
+    details: Schneller Initial-Load mit statischem HTML, schnellem Post-Load und Navigation mit Client-Side Routing.
+---

From ba94f35c351253dbb50bcff8792ecdb1cd45ef51 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 10:38:07 +0200
Subject: [PATCH 002/199] Add guide on handling static assets in VitePress

This document explains how to reference and manage static assets like images, media, and fonts in VitePress. It covers topics such as referencing static assets, the public directory, base URL configuration, and serving assets via a CDN.
---
 docs/de/guide/asset-handling.md | 82 +++++++++++++++++++++++++++++++++
 1 file changed, 82 insertions(+)
 create mode 100644 docs/de/guide/asset-handling.md

diff --git a/docs/de/guide/asset-handling.md b/docs/de/guide/asset-handling.md
new file mode 100644
index 000000000..30a38c318
--- /dev/null
+++ b/docs/de/guide/asset-handling.md
@@ -0,0 +1,82 @@
+---
+description: Erfahre, wie man in VitePress auf statische Assets wie Bilder, Medien und Schriftarten verweisen und diese handhaben kann.
+---
+
+# Asset-Handhabung
+
+## Referenzieren statischer Assets
+
+Alle Markdown-Dateien werden in Vue-Komponenten kompiliert und von [Vite](https://vite.dev/guide/assets.html) verarbeitet. Sie können – **und sollten** – Assets über relative URLs referenzieren:
+
+```md
+![Ein Bild](./image.png)
+```
+
+Sie können in Ihren Markdown-Dateien, `*.vue`-Komponenten des Themes, Styles und reinen `.css`-Dateien auf statische Assets verweisen – entweder über absolute Public-Pfade (ausgehend vom Projektstammverzeichnis) oder über relative Pfade (bezogen auf das Dateisystem). Letzteres entspricht dem Verhalten, das Sie bereits von Vite, der Vue CLI oder dem `file-loader` von webpack kennen.
+
+Gängige Datei-Formate für Bilder, Medien und Schriftarten werden automatisch erkannt und als Assets eingebunden.
+
+::: tip Verlinkte Dateien werden nicht als Assets behandelt
+PDFs oder andere Dokumente, auf die in Markdown-Dateien verlinkt wird, werden nicht automatisch als Assets behandelt. Um verlinkte Dateien verfügbar zu machen, müssen Sie diese manuell im [`public`](#the-public-directory)-Verzeichnis Ihres Projekts ablegen.
+:::
+
+Alle referenzierten Assets – einschließlich derer, die absolute Pfade verwenden – werden im Produktions-Build mit einem Hash-Dateinamen in das Ausgabeverzeichnis kopiert. Assets, auf die nicht verwiesen wird, werden nicht kopiert. Bild-Assets, die kleiner als 4 KB sind, werden als Base64 eingebettet; dieses Verhalten lässt sich über die Konfigurationsoption [`vite`](../reference/site-config#vite) anpassen.
+
+Alle **statischen** Pfadreferenzen, einschließlich absoluter Pfade, sollten auf der Struktur Ihres Arbeitsverzeichnisses basieren.
+
+## Das öffentliche Verzeichnis
+
+Manchmal müssen statische Assets bereitgestellt werden, auf die in Ihren Markdown- oder Theme-Komponenten nicht direkt verwiesen wird, oder Sie möchten bestimmte Dateien unter ihrem ursprünglichen Dateinamen ausliefern. Beispiele für solche Dateien sind `robots.txt`, Favicons und PWA-Icons.
+
+Sie können diese Dateien im `public`-Verzeichnis innerhalb des [Quellverzeichnisses](./routing#source-directory) ablegen. Wenn sich das Stammverzeichnis Ihres Projekts beispielsweise unter `./docs` befindet und Sie den Standardpfad für das Quellverzeichnis verwenden, lautet der Pfad zu Ihrem `public`-Verzeichnis `./docs/public`.
+
+Im Ordner `public` abgelegte Assets werden unverändert in das Stammverzeichnis des Ausgabeordners kopiert.
+
+Beachten Sie, dass Dateien aus dem Ordner `public` über einen absoluten Pfad ausgehend vom Stammverzeichnis referenziert werden sollten – so sollte beispielsweise `public/icon.png` im Quellcode stets als `/icon.png` angesprochen werden.
+
+## Basis-URL
+
+Wenn Ihre Website unter einer URL bereitgestellt wird, die nicht das Stammverzeichnis (Root) ist, legen Sie die Option [`base`](../reference/site-config#base) fest. Wenn Sie Ihre Website beispielsweise unter `https://foo.github.io/bar/` bereitstellen möchten, sollte `base` auf `'/bar/'` gesetzt werden.
+
+Verweise auf statische Assets werden automatisch an die Basis (Base) angepasst; daher funktioniert ein absoluter Verweis auf eine Datei im Ordner `public` mit jeder beliebigen Basis und muss nie aktualisiert werden:
+
+```md
+![Ein Bild](/bild-in-public.png)
+```
+
+Nur dynamisch erstellte Pfade erfordern besondere Aufmerksamkeit – zum Beispiel ein Bild, dessen `src`-Attribut auf einem Konfigurationswert des Themes basiert. Umschließe diese mit dem [`withBase`-Hilfsprogramm](../reference/runtime-api#withbase), damit der Basis-Pfad zur Laufzeit vorangestellt wird:
+
+```vue
+<script setup>
+import { withBase, useData } from 'vitepress'
+
+const { theme } = useData()
+</script>
+
+<template>
+  <img :src="withBase(theme.logoPath)" />
+</template>
+```
+
+## Bereitstellung von Assets über ein CDN
+
+Um die generierten Assets – Skripte, Styles, Schriftarten und Bilder, die aus Markdown oder Komponenten importiert wurden – von einem anderen Ursprung (Origin) als die Seiten bereitzustellen, konfigurieren Sie [`assetsBase`](../reference/site-config#assetsbase):
+
+```ts
+export default {
+  base: '/',
+  assetsBase: 'https://cdn.beispiel.de/'
+}
+```
+
+Laden Sie das Verzeichnis `assets` aus der Build-Ausgabe auf das CDN hoch, sodass es unter `https://cdn.example.com/assets/` erreichbar ist, und stellen Sie den Rest der Ausgabe wie gewohnt auf Ihrer Website bereit. Dateien im Ordner `public` werden von `base` aus referenziert und verbleiben bei den Seiten.
+
+Da der Wert oft umgebungsspezifisch ist, kann er auch über die Befehlszeile übergeben werden:
+
+```sh
+vitepress build docs --assetsBase "$CDN_URL"
+```
+
+::: warning CORS erforderlich
+Modul-Skripte werden immer im CORS-Modus geladen; daher muss ein Cross-Origin-CDN mit einem entsprechenden `Access-Control-Allow-Origin`-Header antworten.
+:::

From f55c63244d92a454e8895db9bd6b578e3693edc6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 10:43:36 +0200
Subject: [PATCH 003/199] Create VitePress configuration file

Added configuration for VitePress with markdown options, navigation, sidebar, and search settings.
---
 docs/de/config.ts | 347 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 347 insertions(+)
 create mode 100644 docs/de/config.ts

diff --git a/docs/de/config.ts b/docs/de/config.ts
new file mode 100644
index 000000000..9224ac417
--- /dev/null
+++ b/docs/de/config.ts
@@ -0,0 +1,347 @@
+import {
+  defineAdditionalConfig,
+  type DefaultTheme,
+  type MarkdownLocaleOptions
+} from 'vitepress'
+import pkg from 'vitepress/package.json' with { type: 'json' }
+
+export const markdown: MarkdownLocaleOptions = {
+  container: {
+    tipLabel: 'TIP',
+    infoLabel: 'INFO',
+    warningLabel: 'WARNING',
+    dangerLabel: 'DANGER',
+    detailsLabel: 'DETAILS',
+    noteLabel: 'NOTE',
+    importantLabel: 'IMPORTANT',
+    cautionLabel: 'CAUTION'
+  },
+  codeCopyButton: {
+    tooltipText: 'Copy code',
+    copiedText: 'Copied'
+  }
+}
+
+export default defineAdditionalConfig({
+  description: 'Static site generator with Vite and Vue',
+
+  head: [
+    [
+      'link',
+      // for the vazirmatn font-face defined in .vitepress/theme/styles.css
+      { rel: 'preconnect', href: 'https://cdn.jsdelivr.net', crossorigin: '' }
+    ]
+  ],
+
+  themeConfig: {
+    nav: nav(),
+
+    search: { options: searchOptions() },
+
+    sidebar: {
+      '/fa/guide/': { base: '/fa/guide/', items: sidebarGuide() },
+      '/fa/reference/': { base: '/fa/reference/', items: sidebarReference() }
+    },
+
+    editLink: {
+      pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
+      text: 'Edit this page on GitHub'
+    },
+
+    footer: {
+      message: 'Released under the MIT License',
+      copyright: 'Copyright © 2019-present Evan You'
+    },
+
+    docFooter: {
+      prev: 'Previous',
+      next: 'Next'
+    },
+
+    outline: {
+      label: 'On this page'
+    },
+
+    lastUpdated: {
+      text: 'Last updated'
+    },
+
+    notFound: {
+      title: 'Page not found',
+      quote:
+        'But if you do not change your direction, and if you keep looking, you may end up where you are heading.',
+      linkLabel: 'Go to home',
+      linkText: 'Take me home'
+    },
+
+    langMenuLabel: 'Change language',
+    returnToTopLabel: 'Return to top',
+    sidebarMenuLabel: 'Sidebar menu',
+    darkModeSwitchLabel: 'Dark mode',
+    lightModeSwitchTitle: 'Switch to light mode',
+    darkModeSwitchTitle: 'Switch to dark mode',
+    siteTitle: 'VitePress'
+  }
+})
+
+function nav(): DefaultTheme.NavItem[] {
+  return [
+    {
+      text: 'Guide',
+      link: 'fa/guide/what-is-vitepress',
+      activeMatch: '/guide/'
+    },
+    {
+      text: 'Reference',
+      link: 'fa/reference/site-config',
+      activeMatch: '/reference/'
+    },
+    {
+      text: pkg.version,
+      items: [
+        {
+          text: '1.6.4',
+          link: 'https://vuejs.github.io/vitepress/v1/fa/'
+        },
+        {
+          text: 'Changelog',
+          link: 'https://github.com/vuejs/vitepress/blob/main/CHANGELOG.md'
+        },
+        {
+          text: 'Contributing',
+          link: 'https://github.com/vuejs/vitepress/blob/main/.github/contributing.md'
+        }
+      ]
+    }
+  ]
+}
+
+function sidebarGuide(): DefaultTheme.SidebarItem[] {
+  return [
+    {
+      text: 'Introduction',
+      collapsed: false,
+      items: [
+        { text: 'What is VitePress?', link: 'what-is-vitepress' },
+        { text: 'Getting Started', link: 'getting-started' },
+        { text: 'Routing', link: 'routing' },
+        { text: 'Deployment', link: 'deploy' }
+      ]
+    },
+    {
+      text: 'Writing',
+      collapsed: false,
+      items: [
+        { text: 'Markdown Extensions', link: 'markdown' },
+        { text: 'Asset Handling', link: 'asset-handling' },
+        { text: 'Frontmatter', link: 'frontmatter' },
+        { text: 'Using Vue in Markdown', link: 'using-vue' },
+        { text: 'Internationalization', link: 'i18n' }
+      ]
+    },
+    {
+      text: 'Customization',
+      collapsed: false,
+      items: [
+        { text: 'Using a Custom Theme', link: 'custom-theme' },
+        {
+          text: 'Extending the Default Theme',
+          link: 'extending-default-theme'
+        },
+        { text: 'Data Loading', link: 'data-loading' },
+        { text: 'SSR Compatibility', link: 'ssr-compat' },
+        { text: 'Connecting to a CMS', link: 'cms' }
+      ]
+    },
+    {
+      text: 'Experimental',
+      collapsed: false,
+      items: [
+        { text: 'MPA Mode', link: 'mpa-mode' },
+        { text: 'Sitemap Generation', link: 'sitemap-generation' }
+      ]
+    },
+    { text: 'Configuration and API Reference', base: 'fa/reference/', link: 'site-config' }
+  ]
+}
+
+function sidebarReference(): DefaultTheme.SidebarItem[] {
+  return [
+    {
+      text: 'Reference',
+      base: 'fa/reference/',
+      items: [
+        { text: 'Site Config', link: 'site-config' },
+        { text: 'Frontmatter Config', link: 'frontmatter-config' },
+        { text: 'Runtime API', link: 'runtime-api' },
+        { text: 'CLI', link: 'cli' },
+        {
+          text: 'Default Theme',
+          base: 'fa/reference/default-theme-',
+          items: [
+            { text: 'Overview', link: 'config' },
+            { text: 'Navigation', link: 'nav' },
+            { text: 'Sidebar', link: 'sidebar' },
+            { text: 'Home Page', link: 'home-page' },
+            { text: 'Footer', link: 'footer' },
+            { text: 'Layout', link: 'layout' },
+            { text: 'Badge', link: 'badge' },
+            { text: 'Team Page', link: 'team-page' },
+            { text: 'Prev / Next Links', link: 'prev-next-links' },
+            { text: 'Edit Link', link: 'edit-link' },
+            { text: 'Last Updated Timestamp', link: 'last-updated' },
+            { text: 'Search', link: 'search' },
+            { text: 'Carbon Ads', link: 'carbon-ads' }
+          ]
+        }
+      ]
+    }
+  ]
+}
+
+function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
+  return {
+    translations: {
+      button: {
+        buttonText: 'Search',
+        buttonAriaLabel: 'Search'
+      },
+      modal: {
+        searchBox: {
+          clearButtonTitle: 'Clear',
+          clearButtonAriaLabel: 'Clear search query',
+          closeButtonText: 'Close',
+          closeButtonAriaLabel: 'Close',
+          placeholderText: 'Search the documentation or ask AI',
+          placeholderTextAskAi: 'Ask another question...',
+          placeholderTextAskAiStreaming: 'Generating answer...',
+          searchInputLabel: 'Search',
+          backToKeywordSearchButtonText: 'Back to keyword search',
+          backToKeywordSearchButtonAriaLabel: 'Back to keyword search',
+          newConversationPlaceholder: 'Ask a question',
+          conversationHistoryTitle: 'My conversation history',
+          startNewConversationText: 'Start a new conversation',
+          viewConversationHistoryText: 'Conversation history',
+          threadDepthErrorPlaceholder: 'Conversation limit reached'
+        },
+        newConversation: {
+          newConversationTitle: 'How can I help you today?',
+          newConversationDescription:
+            'I’ll search your documentation to quickly find setup guides, feature details, and troubleshooting tips.'
+        },
+        footer: {
+          selectText: 'Select',
+          submitQuestionText: 'Submit question',
+          selectKeyAriaLabel: 'Enter key',
+          navigateText: 'Navigate',
+          navigateUpKeyAriaLabel: 'Arrow up',
+          navigateDownKeyAriaLabel: 'Arrow down',
+          closeText: 'Close',
+          backToSearchText: 'Back to search',
+          closeKeyAriaLabel: 'Escape key',
+          poweredByText: 'Powered by'
+        },
+        errorScreen: {
+          titleText: 'Unable to retrieve results',
+          helpText: 'You may need to check your network connection.'
+        },
+        startScreen: {
+          recentSearchesTitle: 'Recent',
+          noRecentSearchesText: 'No recent searches',
+          saveRecentSearchButtonTitle: 'Save this search',
+          removeRecentSearchButtonTitle: 'Remove this search from history',
+          favoriteSearchesTitle: 'Favorites',
+          removeFavoriteSearchButtonTitle: 'Remove this search from favorites',
+          recentConversationsTitle: 'Recent conversations',
+          removeRecentConversationButtonTitle:
+            'Remove this conversation from history'
+        },
+        noResultsScreen: {
+          noResultsText: 'No results for',
+          suggestedQueryText: 'Try searching for',
+          reportMissingResultsText:
+            'Think this search should have results?',
+          reportMissingResultsLinkText: 'Let us know.'
+        },
+        resultsScreen: {
+          askAiPlaceholder: 'Ask AI: ',
+          noResultsAskAiPlaceholder:
+            'Couldn’t find it in the documentation? Ask AI: '
+        },
+        askAiScreen: {
+          disclaimerText:
+            'Answers are generated by AI and may be inaccurate. Please verify.',
+          relatedSourcesText: 'Related sources',
+          thinkingText: 'Thinking...',
+          copyButtonText: 'Copy',
+          copyButtonCopiedText: 'Copied!',
+          copyButtonTitle: 'Copy',
+          likeButtonTitle: 'Helpful',
+          dislikeButtonTitle: 'Not helpful',
+          thanksForFeedbackText: 'Thanks for your feedback!',
+          preToolCallText: 'Searching...',
+          duringToolCallText: 'Searching...',
+          afterToolCallText: 'Search for',
+          stoppedStreamingText: 'You stopped this response',
+          errorTitleText: 'Conversation error',
+          startNewConversationButtonText: 'Start a new conversation'
+        }
+      }
+    },
+    askAi: {
+      sidePanel: {
+        button: {
+          translations: {
+            buttonText: 'Ask AI',
+            buttonAriaLabel: 'Ask AI'
+          }
+        },
+        panel: {
+          translations: {
+            header: {
+              title: 'Ask AI',
+              conversationHistoryTitle: 'My conversation history',
+              newConversationText: 'Start a new conversation',
+              viewConversationHistoryText: 'Conversation history'
+            },
+            promptForm: {
+              promptPlaceholderText: 'Ask a question',
+              promptAnsweringText: 'Generating answer...',
+              promptAskAnotherQuestionText: 'Ask another question',
+              promptDisclaimerText:
+                'Answers are generated by AI and may be inaccurate.',
+              promptLabelText:
+                'Press Enter to submit, or Shift+Enter for a new line.',
+              promptAriaLabelText: 'Question input'
+            },
+            conversationScreen: {
+              preToolCallText: 'Searching...',
+              searchingText: 'Searching...',
+              toolCallResultText: 'Search for',
+              conversationDisclaimer:
+                'Answers are generated by AI and may be inaccurate. Please verify.',
+              reasoningText: 'Reasoning...',
+              thinkingText: 'Thinking...',
+              relatedSourcesText: 'Related sources',
+              stoppedStreamingText: 'You stopped this response',
+              copyButtonText: 'Copy',
+              copyButtonCopiedText: 'Copied!',
+              likeButtonTitle: 'Helpful',
+              dislikeButtonTitle: 'Not helpful',
+              thanksForFeedbackText: 'Thanks for your feedback!',
+              errorTitleText: 'Conversation error'
+            },
+            newConversationScreen: {
+              titleText: 'How can I help you today?',
+              introductionText:
+                'I’ll search your documentation to quickly find setup guides, feature details, and troubleshooting tips.'
+            },
+            logo: {
+              poweredByText: 'Powered by'
+            }
+          }
+        }
+      }
+    }
+  }
+}

From 8b92b3ed9edfd5af7fdf907ce5c976ef9ed93ecb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 10:56:37 +0200
Subject: [PATCH 004/199] Improve German localization in config.ts

Updated German localization for various labels and messages in the config file.
---
 docs/de/config.ts | 164 +++++++++++++++++++++++-----------------------
 1 file changed, 82 insertions(+), 82 deletions(-)

diff --git a/docs/de/config.ts b/docs/de/config.ts
index 9224ac417..d1da68eb1 100644
--- a/docs/de/config.ts
+++ b/docs/de/config.ts
@@ -7,23 +7,23 @@ import pkg from 'vitepress/package.json' with { type: 'json' }
 
 export const markdown: MarkdownLocaleOptions = {
   container: {
-    tipLabel: 'TIP',
+    tipLabel: 'TIPP',
     infoLabel: 'INFO',
-    warningLabel: 'WARNING',
-    dangerLabel: 'DANGER',
+    warningLabel: 'WARNUNG',
+    dangerLabel: 'GEFAHR',
     detailsLabel: 'DETAILS',
-    noteLabel: 'NOTE',
-    importantLabel: 'IMPORTANT',
-    cautionLabel: 'CAUTION'
+    noteLabel: 'NOTIZ',
+    importantLabel: 'WICHTIG',
+    cautionLabel: 'VORSICHT'
   },
   codeCopyButton: {
-    tooltipText: 'Copy code',
-    copiedText: 'Copied'
+    tooltipText: 'Code kopieren',
+    copiedText: 'Kopiert'
   }
 }
 
 export default defineAdditionalConfig({
-  description: 'Static site generator with Vite and Vue',
+  description: 'Static-Site-Generator mit Vue und Vite',
 
   head: [
     [
@@ -39,47 +39,47 @@ export default defineAdditionalConfig({
     search: { options: searchOptions() },
 
     sidebar: {
-      '/fa/guide/': { base: '/fa/guide/', items: sidebarGuide() },
-      '/fa/reference/': { base: '/fa/reference/', items: sidebarReference() }
+      '/de/guide/': { base: '/de/guide/', items: sidebarGuide() },
+      '/de/reference/': { base: '/de/reference/', items: sidebarReference() }
     },
 
     editLink: {
       pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
-      text: 'Edit this page on GitHub'
+      text: 'Bearbeite diese Seite auf GitHub'
     },
 
     footer: {
-      message: 'Released under the MIT License',
-      copyright: 'Copyright © 2019-present Evan You'
+      message: 'Freigegeben unter MIT License',
+      copyright: 'Copyright © 2019-heute Evan You'
     },
 
     docFooter: {
-      prev: 'Previous',
-      next: 'Next'
+      prev: 'Vorheriger',
+      next: 'Nächster'
     },
 
     outline: {
-      label: 'On this page'
+      label: 'Auf dieser Seite'
     },
 
     lastUpdated: {
-      text: 'Last updated'
+      text: 'Zuletzt geupdated'
     },
 
     notFound: {
-      title: 'Page not found',
+      title: 'Seite nicht gefunden',
       quote:
-        'But if you do not change your direction, and if you keep looking, you may end up where you are heading.',
-      linkLabel: 'Go to home',
-      linkText: 'Take me home'
+        'Doch wenn du deine Richtung nicht änderst und weiter in diese Richtung blickst, könntest du tatsächlich dort landen, worauf du zusteuerst.',
+      linkLabel: 'Zur Startseite',
+      linkText: 'Bring mich zur Startseite'
     },
 
-    langMenuLabel: 'Change language',
-    returnToTopLabel: 'Return to top',
-    sidebarMenuLabel: 'Sidebar menu',
-    darkModeSwitchLabel: 'Dark mode',
-    lightModeSwitchTitle: 'Switch to light mode',
-    darkModeSwitchTitle: 'Switch to dark mode',
+    langMenuLabel: 'Sprache ändern',
+    returnToTopLabel: 'Zurück nach oben',
+    sidebarMenuLabel: 'Seitenleiste',
+    darkModeSwitchLabel: 'Dunkelmodus',
+    lightModeSwitchTitle: 'Zum Hellmodus wechseln',
+    darkModeSwitchTitle: 'Zum Dunkelmodus wechseln',
     siteTitle: 'VitePress'
   }
 })
@@ -88,12 +88,12 @@ function nav(): DefaultTheme.NavItem[] {
   return [
     {
       text: 'Guide',
-      link: 'fa/guide/what-is-vitepress',
+      link: 'de/guide/what-is-vitepress',
       activeMatch: '/guide/'
     },
     {
-      text: 'Reference',
-      link: 'fa/reference/site-config',
+      text: 'Referenz',
+      link: 'de/reference/site-config',
       activeMatch: '/reference/'
     },
     {
@@ -104,11 +104,11 @@ function nav(): DefaultTheme.NavItem[] {
           link: 'https://vuejs.github.io/vitepress/v1/fa/'
         },
         {
-          text: 'Changelog',
+          text: 'Änderungen',
           link: 'https://github.com/vuejs/vitepress/blob/main/CHANGELOG.md'
         },
         {
-          text: 'Contributing',
+          text: 'Mitwirken',
           link: 'https://github.com/vuejs/vitepress/blob/main/.github/contributing.md'
         }
       ]
@@ -119,78 +119,78 @@ function nav(): DefaultTheme.NavItem[] {
 function sidebarGuide(): DefaultTheme.SidebarItem[] {
   return [
     {
-      text: 'Introduction',
+      text: 'Einführung',
       collapsed: false,
       items: [
-        { text: 'What is VitePress?', link: 'what-is-vitepress' },
-        { text: 'Getting Started', link: 'getting-started' },
+        { text: 'Was ist VitePress?', link: 'what-is-vitepress' },
+        { text: 'Erste Schritte', link: 'getting-started' },
         { text: 'Routing', link: 'routing' },
         { text: 'Deployment', link: 'deploy' }
       ]
     },
     {
-      text: 'Writing',
+      text: 'Schreiben',
       collapsed: false,
       items: [
-        { text: 'Markdown Extensions', link: 'markdown' },
-        { text: 'Asset Handling', link: 'asset-handling' },
+        { text: 'Markdown Erweiterungen', link: 'markdown' },
+        { text: 'Asset-Handhabung', link: 'asset-handling' },
         { text: 'Frontmatter', link: 'frontmatter' },
-        { text: 'Using Vue in Markdown', link: 'using-vue' },
-        { text: 'Internationalization', link: 'i18n' }
+        { text: 'Vue in Markdown benutzen', link: 'using-vue' },
+        { text: 'Internationalisierung', link: 'i18n' }
       ]
     },
     {
-      text: 'Customization',
+      text: 'Anpassung',
       collapsed: false,
       items: [
-        { text: 'Using a Custom Theme', link: 'custom-theme' },
+        { text: 'Ein eigenes Theme nutzen', link: 'custom-theme' },
         {
-          text: 'Extending the Default Theme',
+          text: 'Standart-Theme erweitern',
           link: 'extending-default-theme'
         },
-        { text: 'Data Loading', link: 'data-loading' },
-        { text: 'SSR Compatibility', link: 'ssr-compat' },
-        { text: 'Connecting to a CMS', link: 'cms' }
+        { text: 'Datenladen', link: 'data-loading' },
+        { text: 'SSR-Kompatibilität', link: 'ssr-compat' },
+        { text: 'Mit einem CMS verbinden', link: 'cms' }
       ]
     },
     {
       text: 'Experimental',
       collapsed: false,
       items: [
-        { text: 'MPA Mode', link: 'mpa-mode' },
-        { text: 'Sitemap Generation', link: 'sitemap-generation' }
+        { text: 'MPA-Modus', link: 'mpa-mode' },
+        { text: 'Sitemap-Generation', link: 'sitemap-generation' }
       ]
     },
-    { text: 'Configuration and API Reference', base: 'fa/reference/', link: 'site-config' }
+    { text: 'Konfiguration und API-Referenz', base: 'de/reference/', link: 'site-config' }
   ]
 }
 
 function sidebarReference(): DefaultTheme.SidebarItem[] {
   return [
     {
-      text: 'Reference',
-      base: 'fa/reference/',
+      text: 'Referenz',
+      base: 'de/reference/',
       items: [
-        { text: 'Site Config', link: 'site-config' },
-        { text: 'Frontmatter Config', link: 'frontmatter-config' },
-        { text: 'Runtime API', link: 'runtime-api' },
+        { text: 'Seiten-Konfiguration', link: 'site-config' },
+        { text: 'Frontmatter-Konfiguration', link: 'frontmatter-config' },
+        { text: 'Runtime-API', link: 'runtime-api' },
         { text: 'CLI', link: 'cli' },
         {
-          text: 'Default Theme',
-          base: 'fa/reference/default-theme-',
+          text: 'Standart-Theme',
+          base: 'de/reference/default-theme-',
           items: [
-            { text: 'Overview', link: 'config' },
+            { text: 'Übersicht', link: 'config' },
             { text: 'Navigation', link: 'nav' },
-            { text: 'Sidebar', link: 'sidebar' },
-            { text: 'Home Page', link: 'home-page' },
+            { text: 'Seitenleiste', link: 'sidebar' },
+            { text: 'Startseite', link: 'home-page' },
             { text: 'Footer', link: 'footer' },
             { text: 'Layout', link: 'layout' },
             { text: 'Badge', link: 'badge' },
-            { text: 'Team Page', link: 'team-page' },
-            { text: 'Prev / Next Links', link: 'prev-next-links' },
-            { text: 'Edit Link', link: 'edit-link' },
-            { text: 'Last Updated Timestamp', link: 'last-updated' },
-            { text: 'Search', link: 'search' },
+            { text: 'Team-Seite', link: 'team-page' },
+            { text: 'Vorher / Nachher Links', link: 'prev-next-links' },
+            { text: 'Link bearbeiten', link: 'edit-link' },
+            { text: 'Zuletzt geupdated Zeitstempel', link: 'last-updated' },
+            { text: 'Suche', link: 'search' },
             { text: 'Carbon Ads', link: 'carbon-ads' }
           ]
         }
@@ -203,26 +203,26 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
   return {
     translations: {
       button: {
-        buttonText: 'Search',
-        buttonAriaLabel: 'Search'
+        buttonText: 'Suche',
+        buttonAriaLabel: 'Suche'
       },
       modal: {
         searchBox: {
-          clearButtonTitle: 'Clear',
-          clearButtonAriaLabel: 'Clear search query',
-          closeButtonText: 'Close',
-          closeButtonAriaLabel: 'Close',
-          placeholderText: 'Search the documentation or ask AI',
-          placeholderTextAskAi: 'Ask another question...',
-          placeholderTextAskAiStreaming: 'Generating answer...',
-          searchInputLabel: 'Search',
-          backToKeywordSearchButtonText: 'Back to keyword search',
-          backToKeywordSearchButtonAriaLabel: 'Back to keyword search',
-          newConversationPlaceholder: 'Ask a question',
-          conversationHistoryTitle: 'My conversation history',
-          startNewConversationText: 'Start a new conversation',
-          viewConversationHistoryText: 'Conversation history',
-          threadDepthErrorPlaceholder: 'Conversation limit reached'
+          clearButtonTitle: 'Löschen',
+          clearButtonAriaLabel: 'Suchverlauf löschen',
+          closeButtonText: 'Schließen',
+          closeButtonAriaLabel: 'Schließen',
+          placeholderText: 'Dokumentation durchsuchen oder KI fragen',
+          placeholderTextAskAi: 'Stell noch eine Frage...',
+          placeholderTextAskAiStreaming: 'Antwort generieren...',
+          searchInputLabel: 'Suche',
+          backToKeywordSearchButtonText: 'Zurück zur Stichwortsuche',
+          backToKeywordSearchButtonAriaLabel: 'Zurück zur Stichwortsuche',
+          newConversationPlaceholder: 'Eine Frage stellen',
+          conversationHistoryTitle: 'Mein Gesprächsverlauf',
+          startNewConversationText: 'Neue Konversation beginnen',
+          viewConversationHistoryText: 'Gesprächsverlauf',
+          threadDepthErrorPlaceholder: 'Gesprächslimit erreicht'
         },
         newConversation: {
           newConversationTitle: 'How can I help you today?',

From d954bb506879cf54d6842362e8e624908567ef5a Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:07:59 +0200
Subject: [PATCH 005/199] Update German translations in config.ts

Updated German translations for various UI elements in the config file.
---
 docs/de/config.ts | 144 +++++++++++++++++++++++-----------------------
 1 file changed, 72 insertions(+), 72 deletions(-)

diff --git a/docs/de/config.ts b/docs/de/config.ts
index d1da68eb1..299606a21 100644
--- a/docs/de/config.ts
+++ b/docs/de/config.ts
@@ -225,66 +225,66 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
           threadDepthErrorPlaceholder: 'Gesprächslimit erreicht'
         },
         newConversation: {
-          newConversationTitle: 'How can I help you today?',
+          newConversationTitle: 'Wie kann ich dir heute helfen?',
           newConversationDescription:
-            'I’ll search your documentation to quickly find setup guides, feature details, and troubleshooting tips.'
+            'Ich werde die Dokumentation durchsuchen, um schnell Einrichtungsanleitungen, Details zu Funktionen und Tipps zur Fehlerbehebung zu finden.'
         },
         footer: {
-          selectText: 'Select',
-          submitQuestionText: 'Submit question',
-          selectKeyAriaLabel: 'Enter key',
-          navigateText: 'Navigate',
-          navigateUpKeyAriaLabel: 'Arrow up',
-          navigateDownKeyAriaLabel: 'Arrow down',
-          closeText: 'Close',
-          backToSearchText: 'Back to search',
-          closeKeyAriaLabel: 'Escape key',
-          poweredByText: 'Powered by'
+          selectText: 'Auswählen',
+          submitQuestionText: 'Frage absenden',
+          selectKeyAriaLabel: 'Eingabetaste', //unsure
+          navigateText: 'Navigieren',
+          navigateUpKeyAriaLabel: 'Pfeil hoch',
+          navigateDownKeyAriaLabel: 'Pfeil runter',
+          closeText: 'Schließen',
+          backToSearchText: 'Zurück zur Suche',
+          closeKeyAriaLabel: 'Escape-Taste',
+          poweredByText: 'Angetrieben von'
         },
         errorScreen: {
-          titleText: 'Unable to retrieve results',
-          helpText: 'You may need to check your network connection.'
+          titleText: 'Ergebnisse konnten nicht abgerufen werden.',
+          helpText: 'Möglicherweise müssen Sie Ihre Netzwerkverbindung überprüfen.'
         },
         startScreen: {
-          recentSearchesTitle: 'Recent',
-          noRecentSearchesText: 'No recent searches',
-          saveRecentSearchButtonTitle: 'Save this search',
-          removeRecentSearchButtonTitle: 'Remove this search from history',
-          favoriteSearchesTitle: 'Favorites',
-          removeFavoriteSearchButtonTitle: 'Remove this search from favorites',
-          recentConversationsTitle: 'Recent conversations',
+          recentSearchesTitle: 'Zuletzt',
+          noRecentSearchesText: 'Keine kürzlichen Suchanfragen',
+          saveRecentSearchButtonTitle: 'Diese Suche speichern',
+          removeRecentSearchButtonTitle: 'Diese Suche aus dem Verlauf entfernen',
+          favoriteSearchesTitle: 'Favoriten',
+          removeFavoriteSearchButtonTitle: 'Diese Suche von Favoriten entfernen',
+          recentConversationsTitle: 'Kürzliche Konversationen',
           removeRecentConversationButtonTitle:
-            'Remove this conversation from history'
+            'Diese Unterhaltung aus dem Verlauf entfernen'
         },
         noResultsScreen: {
-          noResultsText: 'No results for',
-          suggestedQueryText: 'Try searching for',
+          noResultsText: 'Keine Ergebnisse für',
+          suggestedQueryText: 'Versuchen Sie',
           reportMissingResultsText:
-            'Think this search should have results?',
-          reportMissingResultsLinkText: 'Let us know.'
+            'Glaubst du, diese Suche sollte Ergebnisse liefern?',
+          reportMissingResultsLinkText: 'Lass es uns wissen.'
         },
         resultsScreen: {
-          askAiPlaceholder: 'Ask AI: ',
+          askAiPlaceholder: 'Frag KI: ',
           noResultsAskAiPlaceholder:
-            'Couldn’t find it in the documentation? Ask AI: '
+            'Nicht in der Dokumentation fündig geworden? Fragen Sie die KI: '
         },
         askAiScreen: {
           disclaimerText:
-            'Answers are generated by AI and may be inaccurate. Please verify.',
-          relatedSourcesText: 'Related sources',
-          thinkingText: 'Thinking...',
-          copyButtonText: 'Copy',
-          copyButtonCopiedText: 'Copied!',
-          copyButtonTitle: 'Copy',
-          likeButtonTitle: 'Helpful',
-          dislikeButtonTitle: 'Not helpful',
-          thanksForFeedbackText: 'Thanks for your feedback!',
-          preToolCallText: 'Searching...',
-          duringToolCallText: 'Searching...',
-          afterToolCallText: 'Search for',
-          stoppedStreamingText: 'You stopped this response',
-          errorTitleText: 'Conversation error',
-          startNewConversationButtonText: 'Start a new conversation'
+            'Die Antworten werden von einer KI generiert und können ungenau sein. Bitte überprüfen Sie diese.',
+          relatedSourcesText: 'Verwandte Quellen',
+          thinkingText: 'Denken...',
+          copyButtonText: 'Kopieren',
+          copyButtonCopiedText: 'Kopiert!',
+          copyButtonTitle: 'Kopieren',
+          likeButtonTitle: 'Hilfreich',
+          dislikeButtonTitle: 'Nicht Hilfreich',
+          thanksForFeedbackText: 'Danke für Ihr Feedback!',
+          preToolCallText: 'Suchen...',
+          duringToolCallText: 'Suchen...',
+          afterToolCallText: 'Suche nach',
+          stoppedStreamingText: 'Du hast diese Antwort angehalten',
+          errorTitleText: 'Konversationsfehler',
+          startNewConversationButtonText: 'Neue Konversation beginnen'
         }
       }
     },
@@ -292,52 +292,52 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
       sidePanel: {
         button: {
           translations: {
-            buttonText: 'Ask AI',
-            buttonAriaLabel: 'Ask AI'
+            buttonText: 'Frag KI',
+            buttonAriaLabel: 'Frag KI'
           }
         },
         panel: {
           translations: {
             header: {
-              title: 'Ask AI',
-              conversationHistoryTitle: 'My conversation history',
-              newConversationText: 'Start a new conversation',
-              viewConversationHistoryText: 'Conversation history'
+              title: 'Frag KI',
+              conversationHistoryTitle: 'Mein Gesprächsverlauf',
+              newConversationText: 'Neue Konversation beginnen',
+              viewConversationHistoryText: 'Gesprächsverlauf'
             },
             promptForm: {
-              promptPlaceholderText: 'Ask a question',
-              promptAnsweringText: 'Generating answer...',
-              promptAskAnotherQuestionText: 'Ask another question',
+              promptPlaceholderText: 'Frage eine Frage',
+              promptAnsweringText: 'Antwort generieren...',
+              promptAskAnotherQuestionText: 'Frage eine weitere Frage',
               promptDisclaimerText:
-                'Answers are generated by AI and may be inaccurate.',
+                'Die Antworten werden von einer KI generiert und können ungenau sein.',
               promptLabelText:
-                'Press Enter to submit, or Shift+Enter for a new line.',
-              promptAriaLabelText: 'Question input'
+                'Drücken Sie die Eingabetaste zum Absenden oder Umschalt+Eingabetaste für eine neue Zeile.',
+              promptAriaLabelText: 'Frageeingabe'
             },
             conversationScreen: {
-              preToolCallText: 'Searching...',
-              searchingText: 'Searching...',
-              toolCallResultText: 'Search for',
+              preToolCallText: 'Suchen...',
+              searchingText: 'Suchen...',
+              toolCallResultText: 'Siche nach',
               conversationDisclaimer:
-                'Answers are generated by AI and may be inaccurate. Please verify.',
-              reasoningText: 'Reasoning...',
-              thinkingText: 'Thinking...',
-              relatedSourcesText: 'Related sources',
-              stoppedStreamingText: 'You stopped this response',
-              copyButtonText: 'Copy',
-              copyButtonCopiedText: 'Copied!',
-              likeButtonTitle: 'Helpful',
-              dislikeButtonTitle: 'Not helpful',
-              thanksForFeedbackText: 'Thanks for your feedback!',
-              errorTitleText: 'Conversation error'
+                'Die Antworten werden von einer KI generiert und können ungenau sein. Bitte überprüfen Sie diese.',
+              reasoningText: 'Nachdenken...',
+              thinkingText: 'Denken...',
+              relatedSourcesText: 'Ähnliche Quellen',
+              stoppedStreamingText: 'Du hast diese Antwort angehalten',
+              copyButtonText: 'Kopieren',
+              copyButtonCopiedText: 'Kopiert!',
+              likeButtonTitle: 'Hilfreich',
+              dislikeButtonTitle: 'Nicht Hilfreich',
+              thanksForFeedbackText: 'Danke für dein Feedback!',
+              errorTitleText: 'Konversationsfehler'
             },
             newConversationScreen: {
-              titleText: 'How can I help you today?',
+              titleText: 'Wie kann ich dir heute helfen?',
               introductionText:
-                'I’ll search your documentation to quickly find setup guides, feature details, and troubleshooting tips.'
+                'Ich werde Ihre Dokumentation durchsuchen, um schnell Einrichtungsanleitungen, Details zu Funktionen und Tipps zur Fehlerbehebung zu finden.'
             },
             logo: {
-              poweredByText: 'Powered by'
+              poweredByText: 'Angetrieben von'
             }
           }
         }

From 6f2d1563dc484a9137c3bc2d1d7db5c338db1159 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:31:39 +0200
Subject: [PATCH 006/199] Add German localization support to VitePress config

---
 docs/.vitepress/config.ts | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/.vitepress/config.ts b/docs/.vitepress/config.ts
index 64158acfe..19bbe4e7c 100644
--- a/docs/.vitepress/config.ts
+++ b/docs/.vitepress/config.ts
@@ -10,6 +10,7 @@ import {
 } from 'vitepress-plugin-group-icons'
 import llmstxt from 'vitepress-plugin-llms'
 
+import { markdown as deMarkdown } from '../de/config.ts'
 import { markdown as esMarkdown } from '../es/config.ts'
 import { markdown as faMarkdown } from '../fa/config.ts'
 import { markdown as jaMarkdown } from '../ja/config.ts'
@@ -31,7 +32,8 @@ const localeToOgLocaleMap: Record<string, string> = {
   es: 'es_ES',
   ko: 'ko_KR',
   fa: 'fa_IR',
-  ja: 'ja_JP'
+  ja: 'ja_JP',
+  de: 'de_DE'
 }
 
 export default defineConfig({
@@ -103,6 +105,7 @@ export default defineConfig({
   // prettier-ignore
   locales: {
     root: { label: 'English', lang: 'en-US', dir: 'ltr' },
+    de: { label: 'Deutsch', lang:'de-DE', dir: 'ltr', markdown: deMarkdown },
     zh: { label: '简体中文', lang: 'zh-Hans', dir: 'ltr', markdown: zhMarkdown },
     pt: { label: 'Português', lang: 'pt-BR', dir: 'ltr', markdown: ptMarkdown },
     ru: { label: 'Русский', lang: 'ru-RU', dir: 'ltr', markdown: ruMarkdown },

From a05350a9d0dda05204d3415f906727ad59d0d4e8 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:33:25 +0200
Subject: [PATCH 007/199] Add German locale to lunaria.config.json

---
 docs/lunaria.config.json | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/lunaria.config.json b/docs/lunaria.config.json
index 2de958b9e..453919ce3 100644
--- a/docs/lunaria.config.json
+++ b/docs/lunaria.config.json
@@ -21,6 +21,10 @@
     "lang": "en"
   },
   "locales": [
+    {
+      "label": "Deutsch",
+      "lang": "de"
+    },
     {
       "label": "简体中文",
       "lang": "zh"

From 4e78e2d9bdd67c97015b04bf9a3518ab830079fc Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:40:46 +0200
Subject: [PATCH 008/199] docs(de): improve German translation

---
 docs/de/index.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/index.md b/docs/de/index.md
index a3c487bb8..978e2e820 100644
--- a/docs/de/index.md
+++ b/docs/de/index.md
@@ -1,11 +1,11 @@
 ---
-description: VitePress ist ein auf Vite und Vue basierender Generator für statische Websites, mit dem man aus Markdown ansprechende Dokumentationen erstellen kann.
+description: VitePress ist ein auf Vite und Vue basierender Generator für statische Websites, mit dem du aus Markdown ansprechende Dokumentationen erstellen kannst.
 layout: home
 
 hero:
   name: VitePress
-  text: Vite & Vue basierender Generator für statische Websites
-  tagline: Markdown zu wunderschönen Docs in Minuten
+  text: Generator für statische Websites mit Vite & Vue
+  tagline: Von Markdown zu ansprechender Dokumentation in wenigen Minuten
   actions:
     - theme: brand
       text: Was ist VitePress?
@@ -22,15 +22,15 @@ hero:
 
 features:
   - icon: <span class="memo"></span>
-    title: Fokussieren auf den Inhalt
-    details: Erstelle mühelos wunderschöne Dokumentationsseiten mit Markdown.
+    title: Konzentriere dich auf deine Inhalte
+    details: Erstelle mühelos ansprechende Dokumentationsseiten mit einfachem Markdown.
   - icon: <span class="vite"></span>
-    title: Genieße Vite DX
-    details: Sofortiger Serverstart, blitzschnelle Hot-Updates und Plugins aus dem Vite-Ökosystem.
+    title: Die Vite-DX nutzen
+    details: Sofortiger Serverstart, blitzschnelle Hot-Updates und Zugriff auf Plugins aus dem Vite-Ökosystem.
   - icon: <span class="vue"></span>
-    title: Anpassen mit Vue
-    details: Nutze Vue-Syntax und Komponenten direkt in Markdown, oder eigene Themes mit Vhe.
+    title: Mit Vue anpassen
+    details: Verwende Vue-Syntax und -Komponenten direkt in Markdown oder erstelle eigene Themes mit Vue.
   - icon: <span class="rocket"></span>
-    title: Liefer schnelle Seitem
-    details: Schneller Initial-Load mit statischem HTML, schnellem Post-Load und Navigation mit Client-Side Routing.
----
+    title: Schnelle Websites ausliefern
+    details: Schneller initialer Ladevorgang mit statischem HTML und schnelle Navigation nach dem Laden dank clientseitigem Routing.
+---
\ No newline at end of file

From 23535965913d466fad79d0034e64cb80e9455612 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:40:48 +0200
Subject: [PATCH 009/199] docs(de): improve German translation

---
 docs/de/guide/asset-handling.md | 70 ++++++++++++++++-----------------
 1 file changed, 35 insertions(+), 35 deletions(-)

diff --git a/docs/de/guide/asset-handling.md b/docs/de/guide/asset-handling.md
index 30a38c318..2a7e49a5d 100644
--- a/docs/de/guide/asset-handling.md
+++ b/docs/de/guide/asset-handling.md
@@ -1,52 +1,52 @@
 ---
-description: Erfahre, wie man in VitePress auf statische Assets wie Bilder, Medien und Schriftarten verweisen und diese handhaben kann.
+description: Erfahre, wie du statische Assets wie Bilder, Medien und Schriftarten in VitePress referenzierst und verwaltest.
 ---
 
-# Asset-Handhabung
+# Asset-Verwaltung
 
-## Referenzieren statischer Assets
+## Statische Assets referenzieren
 
-Alle Markdown-Dateien werden in Vue-Komponenten kompiliert und von [Vite](https://vite.dev/guide/assets.html) verarbeitet. Sie können – **und sollten** – Assets über relative URLs referenzieren:
+Alle Markdown-Dateien werden in Vue-Komponenten kompiliert und von [Vite](https://vite.dev/guide/assets.html) verarbeitet. Du kannst und solltest Assets über relative URLs referenzieren:
 
-```md
+\`\`\`md
 ![Ein Bild](./image.png)
-```
+\`\`\`
 
-Sie können in Ihren Markdown-Dateien, `*.vue`-Komponenten des Themes, Styles und reinen `.css`-Dateien auf statische Assets verweisen – entweder über absolute Public-Pfade (ausgehend vom Projektstammverzeichnis) oder über relative Pfade (bezogen auf das Dateisystem). Letzteres entspricht dem Verhalten, das Sie bereits von Vite, der Vue CLI oder dem `file-loader` von webpack kennen.
+Du kannst statische Assets in deinen Markdown-Dateien, deinen \`*.vue\`-Komponenten im Theme, Styles und normalen \`.css\`-Dateien entweder über absolute öffentliche Pfade (bezogen auf das Projektverzeichnis) oder über relative Pfade (bezogen auf dein Dateisystem) referenzieren. Letzteres funktioniert ähnlich wie bei Vite, Vue CLI oder Webpacks \`file-loader\`.
 
-Gängige Datei-Formate für Bilder, Medien und Schriftarten werden automatisch erkannt und als Assets eingebunden.
+Gängige Bild-, Medien- und Schriftdateitypen werden automatisch erkannt und als Assets eingebunden.
 
-::: tip Verlinkte Dateien werden nicht als Assets behandelt
-PDFs oder andere Dokumente, auf die in Markdown-Dateien verlinkt wird, werden nicht automatisch als Assets behandelt. Um verlinkte Dateien verfügbar zu machen, müssen Sie diese manuell im [`public`](#the-public-directory)-Verzeichnis Ihres Projekts ablegen.
+::: tip Verknüpfte Dateien werden nicht als Assets behandelt
+PDFs oder andere Dokumente, auf die in Markdown-Dateien verlinkt wird, werden nicht automatisch als Assets behandelt. Damit verknüpfte Dateien zugänglich sind, musst du sie manuell im Verzeichnis [\`public\`](#das-public-verzeichnis) deines Projekts ablegen.
 :::
 
-Alle referenzierten Assets – einschließlich derer, die absolute Pfade verwenden – werden im Produktions-Build mit einem Hash-Dateinamen in das Ausgabeverzeichnis kopiert. Assets, auf die nicht verwiesen wird, werden nicht kopiert. Bild-Assets, die kleiner als 4 KB sind, werden als Base64 eingebettet; dieses Verhalten lässt sich über die Konfigurationsoption [`vite`](../reference/site-config#vite) anpassen.
+Alle referenzierten Assets, einschließlich solcher mit absoluten Pfaden, werden beim Produktions-Build mit einem gehashten Dateinamen in das Ausgabeverzeichnis kopiert. Nicht referenzierte Assets werden nicht kopiert. Bild-Assets unter 4 KB werden als Base64 eingebettet. Dies kann über die [\`vite\`](../reference/site-config#vite)-Konfigurationsoption angepasst werden.
 
-Alle **statischen** Pfadreferenzen, einschließlich absoluter Pfade, sollten auf der Struktur Ihres Arbeitsverzeichnisses basieren.
+Alle **statischen** Pfadangaben, einschließlich absoluter Pfade, sollten auf deiner Arbeitsverzeichnisstruktur basieren.
 
-## Das öffentliche Verzeichnis
+## Das Public-Verzeichnis
 
-Manchmal müssen statische Assets bereitgestellt werden, auf die in Ihren Markdown- oder Theme-Komponenten nicht direkt verwiesen wird, oder Sie möchten bestimmte Dateien unter ihrem ursprünglichen Dateinamen ausliefern. Beispiele für solche Dateien sind `robots.txt`, Favicons und PWA-Icons.
+Manchmal musst du statische Assets bereitstellen, die in keiner deiner Markdown-Dateien oder Theme-Komponenten direkt referenziert werden, oder bestimmte Dateien unter ihrem ursprünglichen Dateinamen ausliefern. Beispiele hierfür sind \`robots.txt\`, Favicons und PWA-Icons.
 
-Sie können diese Dateien im `public`-Verzeichnis innerhalb des [Quellverzeichnisses](./routing#source-directory) ablegen. Wenn sich das Stammverzeichnis Ihres Projekts beispielsweise unter `./docs` befindet und Sie den Standardpfad für das Quellverzeichnis verwenden, lautet der Pfad zu Ihrem `public`-Verzeichnis `./docs/public`.
+Du kannst diese Dateien im Verzeichnis \`public\` unterhalb des [Quellverzeichnisses](./routing#quellverzeichnis) ablegen. Wenn dein Projektverzeichnis beispielsweise \`./docs\` ist und das Standard-Quellverzeichnis verwendet wird, lautet dein Public-Verzeichnis \`./docs/public\`.
 
-Im Ordner `public` abgelegte Assets werden unverändert in das Stammverzeichnis des Ausgabeordners kopiert.
+Assets im Verzeichnis \`public\` werden unverändert in das Stammverzeichnis des Ausgabeverzeichnisses kopiert.
 
-Beachten Sie, dass Dateien aus dem Ordner `public` über einen absoluten Pfad ausgehend vom Stammverzeichnis referenziert werden sollten – so sollte beispielsweise `public/icon.png` im Quellcode stets als `/icon.png` angesprochen werden.
+Beachte, dass du Dateien aus \`public\` mit einem absoluten Pfad vom Stammverzeichnis referenzieren solltest. \`public/icon.png\` sollte im Quellcode beispielsweise immer als \`/icon.png\` referenziert werden.
 
 ## Basis-URL
 
-Wenn Ihre Website unter einer URL bereitgestellt wird, die nicht das Stammverzeichnis (Root) ist, legen Sie die Option [`base`](../reference/site-config#base) fest. Wenn Sie Ihre Website beispielsweise unter `https://foo.github.io/bar/` bereitstellen möchten, sollte `base` auf `'/bar/'` gesetzt werden.
+Wenn deine Website unter einer URL bereitgestellt wird, die nicht dem Stammverzeichnis entspricht, setze die Option [\`base\`](../reference/site-config#base). Wenn du deine Website beispielsweise unter \`https://foo.github.io/bar/\` bereitstellen möchtest, sollte \`base\` auf \`'/bar/'\` gesetzt werden.
 
-Verweise auf statische Assets werden automatisch an die Basis (Base) angepasst; daher funktioniert ein absoluter Verweis auf eine Datei im Ordner `public` mit jeder beliebigen Basis und muss nie aktualisiert werden:
+Referenzen auf statische Assets werden automatisch an \`base\` angepasst. Eine absolute Referenz auf eine Datei in \`public\` funktioniert daher mit jedem \`base\` und muss nicht aktualisiert werden:
 
-```md
-![Ein Bild](/bild-in-public.png)
-```
+\`\`\`md
+![Ein Bild](/image-inside-public.png)
+\`\`\`
 
-Nur dynamisch erstellte Pfade erfordern besondere Aufmerksamkeit – zum Beispiel ein Bild, dessen `src`-Attribut auf einem Konfigurationswert des Themes basiert. Umschließe diese mit dem [`withBase`-Hilfsprogramm](../reference/runtime-api#withbase), damit der Basis-Pfad zur Laufzeit vorangestellt wird:
+Nur dynamisch erzeugte Pfade benötigen besondere Behandlung – beispielsweise ein Bild, dessen \`src\` auf einem Wert aus der Theme-Konfiguration basiert. Um den Basis-Pfad zur Laufzeit voranzustellen, umschließe solche Pfade mit dem [\`withBase\`-Helper](../reference/runtime-api#withbase):
 
-```vue
+\`\`\`vue
 <script setup>
 import { withBase, useData } from 'vitepress'
 
@@ -56,27 +56,27 @@ const { theme } = useData()
 <template>
   <img :src="withBase(theme.logoPath)" />
 </template>
-```
+\`\`\`
 
-## Bereitstellung von Assets über ein CDN
+## Assets über ein CDN ausliefern
 
-Um die generierten Assets – Skripte, Styles, Schriftarten und Bilder, die aus Markdown oder Komponenten importiert wurden – von einem anderen Ursprung (Origin) als die Seiten bereitzustellen, konfigurieren Sie [`assetsBase`](../reference/site-config#assetsbase):
+Um generierte Assets – Skripte, Styles, Schriftarten und aus Markdown oder Komponenten importierte Bilder – von einer anderen Origin als den Seiten auszuliefern, setze [\`assetsBase\`](../reference/site-config#assetsbase):
 
-```ts
+\`\`\`ts
 export default {
   base: '/',
-  assetsBase: 'https://cdn.beispiel.de/'
+  assetsBase: 'https://cdn.example.com/'
 }
-```
+\`\`\`
 
-Laden Sie das Verzeichnis `assets` aus der Build-Ausgabe auf das CDN hoch, sodass es unter `https://cdn.example.com/assets/` erreichbar ist, und stellen Sie den Rest der Ausgabe wie gewohnt auf Ihrer Website bereit. Dateien im Ordner `public` werden von `base` aus referenziert und verbleiben bei den Seiten.
+Lade das Verzeichnis \`assets\` aus dem Build-Ausgabeverzeichnis auf das CDN hoch, sodass es unter \`https://cdn.example.com/assets/\` erreichbar ist, und stelle den restlichen Output wie gewohnt auf deiner Website bereit. Dateien in \`public\` werden relativ zu \`base\` referenziert und bleiben bei den Seiten.
 
-Da der Wert oft umgebungsspezifisch ist, kann er auch über die Befehlszeile übergeben werden:
+Da der Wert häufig von der Umgebung abhängt, kann er auch über die Kommandozeile übergeben werden:
 
-```sh
+\`\`\`sh
 vitepress build docs --assetsBase "$CDN_URL"
-```
+\`\`\`
 
 ::: warning CORS erforderlich
-Modul-Skripte werden immer im CORS-Modus geladen; daher muss ein Cross-Origin-CDN mit einem entsprechenden `Access-Control-Allow-Origin`-Header antworten.
+Modul-Skripte werden immer im CORS-Modus geladen. Daher muss ein CDN über verschiedene Origins einen passenden \`Access-Control-Allow-Origin\`-Header zurückgeben.
 :::

From a4eba681b45be3886e9cc2ef6d5bf5a71281cfdb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:16 +0200
Subject: [PATCH 010/199] docs(de): add missing documentation pages

---
 docs/de/guide/cms.md | 57 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 docs/de/guide/cms.md

diff --git a/docs/de/guide/cms.md b/docs/de/guide/cms.md
new file mode 100644
index 000000000..0bff6746f
--- /dev/null
+++ b/docs/de/guide/cms.md
@@ -0,0 +1,57 @@
+---
+outline: deep
+description: Connect VitePress to a headless CMS using dynamic routes and data loaders.
+---
+
+# Connecting to a CMS
+
+## General Workflow
+
+Connecting VitePress to a CMS will largely revolve around [Dynamic Routes](./routing#dynamic-routes). Make sure to understand how it works before proceeding.
+
+Since each CMS will work differently, here we can only provide a generic workflow that you will need to adapt to your specific scenario.
+
+1. If your CMS requires authentication, create an `.env` file to store your API tokens and load it so:
+
+    ```js
+    // posts/[id].paths.js
+    import { loadEnv } from 'vitepress'
+
+    const env = loadEnv('', process.cwd())
+    ```
+
+2. Fetch the necessary data from the CMS and format it into proper paths data:
+
+    ```js
+    export default {
+      async paths() {
+        // use respective CMS client library if needed
+        const data = await (await fetch('https://my-cms-api', {
+          headers: {
+            // token if necessary
+          }
+        })).json()
+
+        return data.map(entry => {
+          return {
+            params: { id: entry.id, /* title, authors, date etc. */ },
+            content: entry.content
+          }
+        })
+      }
+    }
+    ```
+
+3. Render the content in the page:
+
+    ```md
+    # {{ $params.title }}
+
+    - by {{ $params.author }} on {{ $params.date }}
+
+    <!-- @content -->
+    ```
+
+## Integration Guides
+
+If you have written a guide on integrating VitePress with a specific CMS, please use the "Edit this page" link below to submit it here!

From c82b80bc6d730932e18448aa1d42a7585fddac9e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:18 +0200
Subject: [PATCH 011/199] docs(de): add missing documentation pages

---
 docs/de/guide/custom-theme.md | 266 ++++++++++++++++++++++++++++++++++
 1 file changed, 266 insertions(+)
 create mode 100644 docs/de/guide/custom-theme.md

diff --git a/docs/de/guide/custom-theme.md b/docs/de/guide/custom-theme.md
new file mode 100644
index 000000000..21cf4e264
--- /dev/null
+++ b/docs/de/guide/custom-theme.md
@@ -0,0 +1,266 @@
+---
+description: Create and use a custom theme in VitePress to fully control the look and feel of your site.
+---
+
+# Using a Custom Theme
+
+## Theme Resolving
+
+You can enable a custom theme by creating a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (the "theme entry file"):
+
+```
+.
+├─ docs                # project root
+│  ├─ .vitepress
+│  │  ├─ theme
+│  │  │  └─ index.js   # theme entry
+│  │  └─ config.js     # config file
+│  └─ index.md
+└─ package.json
+```
+
+VitePress will always use the custom theme instead of the default theme when it detects presence of a theme entry file. You can, however, [extend the default theme](./extending-default-theme) to perform advanced customizations on top of it.
+
+## Theme Interface
+
+A VitePress custom theme is defined as an object with the following interface:
+
+```ts
+interface Theme {
+  /**
+   * Root layout component for every page
+   * @required
+   */
+  Layout: Component
+  /**
+   * Enhance Vue app instance
+   * @optional
+   */
+  enhanceApp?: (ctx: EnhanceAppContext) => Awaitable<void>
+  /**
+   * Runs inside the root component's `setup()`
+   * @optional
+   */
+  setup?: () => void
+  /**
+   * Extend another theme, calling its `enhanceApp` and `setup` before ours
+   * @optional
+   */
+  extends?: Theme
+}
+
+interface EnhanceAppContext {
+  app: App // Vue app instance
+  router: Router // VitePress router instance
+  siteData: Ref<SiteData> // Site-level metadata
+}
+```
+
+The theme entry file should export the theme as its default export:
+
+```js [.vitepress/theme/index.js]
+
+// You can directly import Vue files in the theme entry
+// VitePress is pre-configured with @vitejs/plugin-vue.
+import Layout from './Layout.vue'
+
+export default {
+  Layout,
+  enhanceApp({ app, router, siteData }) {
+    // app.component(...)
+    // app.use(...)
+  }
+}
+```
+
+The `enhanceApp` hook allows you to access the [Vue app instance](https://vuejs.org/api/application.html) and other runtime data, which can be used to [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
+
+The `router` value is the same VitePress router instance returned by [`useRouter()`](../reference/runtime-api#userouter). To listen for route changes, assign handlers on the router:
+
+```ts [.vitepress/theme/index.ts]
+export default {
+  enhanceApp({ router }) {
+    router.onBeforeRouteChange = (to) => {
+      console.log('navigating to', to)
+    }
+
+    router.onAfterRouteChange = (to) => {
+      console.log('navigated to', to)
+    }
+  }
+}
+```
+
+Return `false` from `onBeforeRouteChange` or `onBeforePageLoad` to cancel navigation.
+
+The `setup` hook runs inside the root component's `setup()`, so Composition API calls (`onMounted`, `watch`, composables, ...) work there without wrapping the layout component:
+
+```ts [.vitepress/theme/index.ts]
+import { watch } from 'vue'
+import { useData } from 'vitepress'
+import DefaultTheme from 'vitepress/theme'
+
+export default {
+  extends: DefaultTheme,
+  setup() {
+    const { page } = useData()
+    watch(() => page.value.relativePath, (path) => {
+      console.log('now viewing', path)
+    })
+  }
+}
+```
+
+With `extends`, each theme's `setup` runs base-first, like `enhanceApp`. It also runs during SSR/SSG rendering, so keep browser-only work inside `onMounted`.
+
+The default export is the only contract for a custom theme, and only the `Layout` property is required. So technically, a VitePress theme can be as simple as a single Vue component.
+
+Inside your layout component, it works just like a normal Vite + Vue 3 application. Do note the theme also needs to be [SSR-compatible](./ssr-compat).
+
+## Building a Layout
+
+The most basic layout component needs to contain a [`<Content />`](../reference/runtime-api#content) component:
+
+```vue [.vitepress/theme/Layout.vue]
+<template>
+  <h1>Custom Layout!</h1>
+
+  <!-- this is where markdown content will be rendered -->
+  <Content />
+</template>
+```
+
+The above layout simply renders every page's markdown as HTML. The first improvement we can add is to handle 404 errors:
+
+```vue{1-4,9-12}
+<script setup>
+import { useData } from 'vitepress'
+const { page } = useData()
+</script>
+
+<template>
+  <h1>Custom Layout!</h1>
+
+  <div v-if="page.isNotFound">
+    Custom 404 page!
+  </div>
+  <Content v-else />
+</template>
+```
+
+The [`useData()`](../reference/runtime-api#usedata) helper provides us with all the runtime data we need to conditionally render different layouts. One of the other data we can access is the current page's frontmatter. We can leverage this to allow the end user to control the layout in each page. For example, the user can indicate the page should use a special home page layout with:
+
+```md
+---
+layout: home
+---
+```
+
+And we can adjust our theme to handle this:
+
+```vue{3,12-14}
+<script setup>
+import { useData } from 'vitepress'
+const { page, frontmatter } = useData()
+</script>
+
+<template>
+  <h1>Custom Layout!</h1>
+
+  <div v-if="page.isNotFound">
+    Custom 404 page!
+  </div>
+  <div v-if="frontmatter.layout === 'home'">
+    Custom home page!
+  </div>
+  <Content v-else />
+</template>
+```
+
+You can, of course, split the layout into more components:
+
+```vue{3-5,12-15}
+<script setup>
+import { useData } from 'vitepress'
+import NotFound from './NotFound.vue'
+import Home from './Home.vue'
+import Page from './Page.vue'
+
+const { page, frontmatter } = useData()
+</script>
+
+<template>
+  <h1>Custom Layout!</h1>
+
+  <NotFound v-if="page.isNotFound" />
+  <Home v-if="frontmatter.layout === 'home'" />
+  <Page v-else /> <!-- <Page /> renders <Content /> -->
+</template>
+```
+
+Consult the [Runtime API Reference](../reference/runtime-api) for everything available in theme components. In addition, you can leverage [Build-Time Data Loading](./data-loading) to generate data-driven layout - for example, a page that lists all blog posts in the current project.
+
+## Distributing a Custom Theme
+
+The easiest way to distribute a custom theme is by providing it as a [template repository on GitHub](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository).
+
+If you wish to distribute the theme as an npm package, follow these steps:
+
+1. Export the theme object as the default export in your package entry.
+
+2. If applicable, export your theme config type definition as `ThemeConfig`.
+
+3. If your theme requires adjusting the VitePress config, export that config under a package sub-path (e.g. `my-theme/config`) so the user can extend it.
+
+4. Document the theme config options (both via config file and frontmatter).
+
+5. Provide clear instructions on how to consume your theme (see below).
+
+## Consuming a Custom Theme
+
+To consume an external theme, import and re-export it from the custom theme entry:
+
+```js [.vitepress/theme/index.js]
+import Theme from 'awesome-vitepress-theme'
+
+export default Theme
+```
+
+If the theme needs to be extended:
+
+```js [.vitepress/theme/index.js]
+import Theme from 'awesome-vitepress-theme'
+
+export default {
+  extends: Theme,
+  enhanceApp(ctx) {
+    // ...
+  }
+}
+```
+
+If the theme requires special VitePress config, you will need to also extend it in your own config:
+
+```ts [.vitepress/config.ts]
+import baseConfig from 'awesome-vitepress-theme/config'
+
+export default {
+  // extend theme base config (if needed)
+  extends: baseConfig
+}
+```
+
+Finally, if the theme provides types for its theme config:
+
+```ts [.vitepress/config.ts]
+import baseConfig from 'awesome-vitepress-theme/config'
+import { defineConfig } from 'vitepress'
+import type { ThemeConfig } from 'awesome-vitepress-theme'
+
+export default defineConfig<ThemeConfig>({
+  extends: baseConfig,
+  themeConfig: {
+    // Type is `ThemeConfig`
+  }
+})
+```

From 4c11fb1e76ccb258698a493ffdb18d39cb377654 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:20 +0200
Subject: [PATCH 012/199] docs(de): add missing documentation pages

---
 docs/de/guide/data-loading.md | 248 ++++++++++++++++++++++++++++++++++
 1 file changed, 248 insertions(+)
 create mode 100644 docs/de/guide/data-loading.md

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
new file mode 100644
index 000000000..1c11e4698
--- /dev/null
+++ b/docs/de/guide/data-loading.md
@@ -0,0 +1,248 @@
+---
+description: Load arbitrary data at build time using VitePress data loaders and import it from pages or components.
+---
+
+# Build-Time Data Loading
+
+VitePress provides a feature called **data loaders** that allows you to load arbitrary data and import it from pages or components. The data loading is executed **only at build time**: the resulting data will be serialized as JSON in the final JavaScript bundle.
+
+Data loaders can be used to fetch remote data, or generate metadata based on local files. For example, you can use data loaders to parse all your local API pages and automatically generate an index of all API entries.
+
+## Basic Usage
+
+A data loader file must end with either `.data.js` or `.data.ts`. The file should provide a default export of an object with the `load()` method:
+
+```js [example.data.js]
+export default {
+  load() {
+    return {
+      hello: 'world'
+    }
+  }
+}
+```
+
+The loader module is evaluated only in Node.js, so you can import Node APIs and npm dependencies as needed.
+
+You can then import data from this file in `.md` pages and `.vue` components using the `data` named export:
+
+```vue
+<script setup>
+import { data } from './example.data.js'
+</script>
+
+<pre>{{ data }}</pre>
+```
+
+Output:
+
+```json
+{
+  "hello": "world"
+}
+```
+
+You'll notice the data loader itself does not export the `data`. It is VitePress calling the `load()` method behind the scenes and implicitly exposing the result via the `data` named export.
+
+This works even if the loader is async:
+
+```js
+export default {
+  async load() {
+    // fetch remote data
+    return (await fetch('...')).json()
+  }
+}
+```
+
+## Data from Local Files
+
+When you need to generate data based on local files, you should use the `watch` option in the data loader so that changes made to these files can trigger hot updates.
+
+The `watch` option is also convenient in that you can use [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match multiple files. The patterns can be relative to the loader file itself, and the `load()` function will receive the matched files as absolute paths.
+
+The following example shows loading CSV files and transforming them into JSON using [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Because this file only executes at build time, you will not be shipping the CSV parser to the client!
+
+```js
+import fs from 'node:fs'
+import { parse } from 'csv-parse/sync'
+
+export default {
+  watch: ['./data/*.csv'],
+  load(watchedFiles) {
+    // watchedFiles will be an array of absolute paths of the matched files.
+    // generate an array of blog post metadata that can be used to render
+    // a list in the theme layout
+    return watchedFiles.map((file) => {
+      return parse(fs.readFileSync(file, 'utf-8'), {
+        columns: true,
+        skip_empty_lines: true
+      })
+    })
+  }
+}
+```
+
+## `createContentLoader`
+
+When building a content focused site, we often need to create an "archive" or "index" page: a page where we list all available entries in our content collection, for example blog posts or API pages. We **can** implement this directly with the data loader API, but since this is such a common use case, VitePress also provides a `createContentLoader` helper to simplify this:
+
+```js [posts.data.js]
+import { createContentLoader } from 'vitepress'
+
+export default createContentLoader('posts/*.md', /* options */)
+```
+
+The helper takes a glob pattern relative to the [source directory](./routing#source-directory), and returns a `{ watch, load }` data loader object that can be used as the default export in a data loader file. It also implements caching based on file modified timestamps to improve dev performance.
+
+Note the loader only works with Markdown files - matched non-Markdown files will be skipped.
+
+The loaded data will be an array with the type of `ContentData[]`:
+
+```ts
+interface ContentData {
+  // mapped URL for the page. e.g. /posts/hello.html (does not include base)
+  // manually iterate or use custom `transform` to normalize the paths
+  url: string
+  // frontmatter data of the page
+  frontmatter: Record<string, any>
+
+  // the following are only present if relevant options are enabled
+  // we will discuss them below
+  src: string | undefined
+  html: string | undefined
+  excerpt: string | undefined
+}
+```
+
+By default, only `url` and `frontmatter` are provided. This is because the loaded data will be inlined as JSON in the client bundle, so we need to be cautious about its size. Here's an example using the data to build a minimal blog index page:
+
+```vue
+<script setup>
+import { data as posts } from './posts.data.js'
+</script>
+
+<template>
+  <h1>All Blog Posts</h1>
+  <ul>
+    <li v-for="post of posts">
+      <a :href="post.url">{{ post.frontmatter.title }}</a>
+      <span>by {{ post.frontmatter.author }}</span>
+    </li>
+  </ul>
+</template>
+```
+
+### Options
+
+The default data may not suit all needs - you can opt-in to transform the data using options:
+
+```js [posts.data.js]
+import { createContentLoader } from 'vitepress'
+
+export default createContentLoader('posts/*.md', {
+  includeSrc: true, // include raw markdown source?
+  render: true,     // include rendered full page HTML?
+  excerpt: true,    // include excerpt?
+  transform(rawData) {
+    // map, sort, or filter the raw data as you wish.
+    // the final result is what will be shipped to the client.
+    return rawData.sort((a, b) => {
+      return +new Date(b.frontmatter.date) - +new Date(a.frontmatter.date)
+    }).map((page) => {
+      page.src     // raw markdown source
+      page.html    // rendered full page HTML
+      page.excerpt // rendered excerpt HTML (content above first `---`)
+      return {/* ... */}
+    })
+  }
+})
+```
+
+Check out how it is used in the [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
+
+The `createContentLoader` API can also be used inside [build hooks](../reference/site-config#build-hooks):
+
+```js [.vitepress/config.js]
+export default {
+  async buildEnd() {
+    const posts = await createContentLoader('posts/*.md').load()
+    // generate files based on posts metadata, e.g. RSS feed
+  }
+}
+```
+
+**Types**
+
+```ts
+interface ContentOptions<T = ContentData[]> {
+  /**
+   * Include src?
+   * @default false
+   */
+  includeSrc?: boolean
+
+  /**
+   * Render src to HTML and include in data?
+   * @default false
+   */
+  render?: boolean
+
+  /**
+   * If `boolean`, whether to parse and include excerpt? (rendered as HTML)
+   *
+   * If `function`, control how the excerpt is extracted from the content.
+   *
+   * If `string`, define a custom separator to be used for extracting the
+   * excerpt. Default separator is `---` if `excerpt` is `true`.
+   *
+   * @see https://github.com/jonschlinkert/gray-matter#optionsexcerpt
+   * @see https://github.com/jonschlinkert/gray-matter#optionsexcerpt_separator
+   *
+   * @default false
+   */
+  excerpt?:
+    | boolean
+    | ((file: { data: { [key: string]: any }; content: string; excerpt?: string }, options?: any) => void)
+    | string
+
+  /**
+   * Transform the data. Note the data will be inlined as JSON in the client
+   * bundle if imported from components or markdown files.
+   */
+  transform?: (data: ContentData[]) => T | Promise<T>
+}
+```
+
+## Typed Data Loaders
+
+When using TypeScript, you can type your loader and `data` export like so:
+
+```ts
+import { defineLoader } from 'vitepress'
+
+export interface Data {
+  // data type
+}
+
+declare const data: Data
+export { data }
+
+export default defineLoader({
+  // type checked loader options
+  watch: ['...'],
+  async load(): Promise<Data> {
+    // ...
+  }
+})
+```
+
+## Configuration
+
+To get the configuration information inside a loader, you can use some code like this:
+
+```ts
+import type { SiteConfig } from 'vitepress'
+
+const config: SiteConfig = (globalThis as any).VITEPRESS_CONFIG
+```

From 319708844469dec0b7b3fa579a9df9e6949b5581 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:22 +0200
Subject: [PATCH 013/199] docs(de): add missing documentation pages

---
 docs/de/guide/deploy.md | 406 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 406 insertions(+)
 create mode 100644 docs/de/guide/deploy.md

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
new file mode 100644
index 000000000..d3d05cec4
--- /dev/null
+++ b/docs/de/guide/deploy.md
@@ -0,0 +1,406 @@
+---
+outline: deep
+description: Deploy your VitePress site to popular platforms like Netlify, Vercel, GitHub Pages, and more.
+---
+
+# Deploy Your VitePress Site
+
+The following guides are based on some shared assumptions:
+
+- The VitePress site is inside the `docs` directory of your project.
+- You are using the default build output directory (`.vitepress/dist`).
+- VitePress is installed as a local dependency in your project, and you have set up the following scripts in your `package.json`:
+
+  ```json [package.json]
+  {
+    "scripts": {
+      "docs:build": "vitepress build docs",
+      "docs:preview": "vitepress preview docs"
+    }
+  }
+  ```
+
+## Build and Test Locally
+
+1. Run this command to build the docs:
+
+   ```sh
+   $ npm run docs:build
+   ```
+
+2. Once built, preview it locally by running:
+
+   ```sh
+   $ npm run docs:preview
+   ```
+
+   The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. You can use this to make sure everything looks good before pushing to production.
+
+3. You can configure the port of the server by passing `--port` as an argument.
+
+   ```json
+   {
+     "scripts": {
+       "docs:preview": "vitepress preview docs --port 8080"
+     }
+   }
+   ```
+
+   Now the `docs:preview` method will launch the server at `http://localhost:8080`.
+
+## Setting a Public Base Path
+
+By default, we assume the site is going to be deployed at the root path of a domain (`/`). If your site is going to be served at a sub-path, e.g. `https://mywebsite.com/blog/`, then you need to set the [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
+
+**Example:** If you're using Github (or GitLab) Pages and deploying to `user.github.io/repo/`, then set your `base` to `/repo/`.
+
+## Relocatable Builds (Relative Base) {#relocatable-builds-relative-base}
+
+When the final URL of the site isn't known at build time — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled into an app — set `base` to `'./'`:
+
+```ts
+export default {
+  base: './'
+}
+```
+
+Every page then references assets and other pages relative to its own location, and the client runtime recovers the real mount point when the page loads. The same build works from **any** sub path without rebuilding — including several at once — with routing, search and prefetching fully functional.
+
+Opening the generated HTML files straight from the file system (`file://`) also works as a styled, fully navigable static site. Browsers block JavaScript modules over `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
+
+A few things to know:
+
+- Keep [`cleanUrls`](../reference/site-config#cleanurls) off (the default): portable output needs links that end in `.html`, since there is no server to rewrite pretty URLs.
+- `404.html` is generated for the root depth. Hosts that serve it as a fallback for arbitrarily deep URLs will render it without styles (there is no correct relative prefix for an unknown depth).
+- [`head`](../reference/site-config#head) entries are emitted verbatim, as always — avoid root-absolute paths like `/favicon.ico` there and prefer absolute URLs or `transformHead`.
+- Raw HTML `<a>` tags in Markdown keep their `href` as written — use Markdown link syntax for site-absolute links (embedded `<img>` sources go through the asset pipeline and are handled).
+- Links created by [`createContentLoader`](./data-loading#createcontentloader) content stay site-absolute (their HTML is embedded into other pages, so no single relative prefix is correct) — they resolve only for a root mount.
+- Serve pages at their canonical URLs: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
+- The dev server always serves at `/`; the relative behavior applies to the production build.
+
+## HTTP Cache Headers
+
+If you have control over the HTTP headers on your production server, you can configure `cache-control` headers to achieve better performance on repeated visits.
+
+The production build uses hashed file names for static assets (JavaScript, CSS and other imported assets not in `public`). If you inspect the production preview using your browser devtools' network tab, you will see files like `app.4f283b18.js`.
+
+This `4f283b18` hash is generated from the content of this file. The same hashed URL is guaranteed to serve the same file content - if the contents change, the URLs change too. This means you can safely use the strongest cache headers for these files. All such files will be placed under `assets/` in the output directory, so you can configure the following header for them:
+
+```
+Cache-Control: max-age=31536000,immutable
+```
+
+::: details Example Netlify `_headers` file
+
+```
+/assets/*
+  cache-control: max-age=31536000
+  cache-control: immutable
+```
+
+Note: the `_headers` file should be placed in the [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - so that it is copied verbatim to the output directory.
+
+[Netlify custom headers documentation](https://docs.netlify.com/routing/headers/)
+
+:::
+
+::: details Example Vercel config in `vercel.json`
+
+```json
+{
+  "headers": [
+    {
+      "source": "/assets/(.*)",
+      "headers": [
+        {
+          "key": "Cache-Control",
+          "value": "max-age=31536000, immutable"
+        }
+      ]
+    }
+  ]
+}
+```
+
+Note: the `vercel.json` file should be placed at the root of your **repository**.
+
+[Vercel documentation on headers config](https://vercel.com/docs/concepts/projects/project-configuration#headers)
+
+:::
+
+## Platform Guides
+
+### Netlify / Vercel / Cloudflare Pages / AWS Amplify / Render {#generic}
+
+Set up a new project and change these settings using your dashboard:
+
+- **Build Command:** `npm run docs:build`
+- **Output Directory:** `docs/.vitepress/dist`
+- **Node Version:** `20` (or above)
+
+::: warning
+Don't enable options like _Auto Minify_ for HTML code. It will remove comments from output which have meaning to Vue. You may see hydration mismatch errors if they get removed.
+:::
+
+### GitHub Pages
+
+1. Create a file named `deploy.yml` inside `.github/workflows` directory of your project with some content like this:
+
+   ```yaml [.github/workflows/deploy.yml]
+   # Sample workflow for building and deploying a VitePress site to GitHub Pages
+   #
+   name: Deploy VitePress site to Pages
+
+   on:
+     # Runs on pushes targeting the `main` branch. Change this to `master` if you're
+     # using the `master` branch as the default branch.
+     push:
+       branches: [main]
+
+     # Allows you to run this workflow manually from the Actions tab
+     workflow_dispatch:
+
+   # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+   permissions:
+     contents: read
+     pages: write
+     id-token: write
+
+   # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
+   # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+   concurrency:
+     group: pages
+     cancel-in-progress: false
+
+   jobs:
+     # Build job
+     build:
+       runs-on: ubuntu-latest
+       steps:
+         - name: Checkout
+           uses: actions/checkout@v5
+           with:
+             fetch-depth: 0 # Not needed if lastUpdated is not enabled
+         # - uses: pnpm/action-setup@v4 # Uncomment this block if you're using pnpm
+         #   with:
+         #     version: 9 # Not needed if you've set "packageManager" in package.json
+         # - uses: oven-sh/setup-bun@v1 # Uncomment this if you're using Bun
+         - name: Setup Node
+           uses: actions/setup-node@v6
+           with:
+             node-version: 24
+             cache: npm # or pnpm / yarn
+         - name: Cache VitePress
+           uses: actions/cache@v4
+           with:
+             path: docs/.vitepress/cache
+             key: ${{ runner.os }}-vitepress-${{ hashFiles('docs/**', 'package-lock.json', 'pnpm-lock.yaml', 'yarn.lock', 'bun.lockb') }}
+             restore-keys: |
+               ${{ runner.os }}-vitepress-
+         - name: Setup Pages
+           uses: actions/configure-pages@v4
+         - name: Install dependencies
+           run: npm ci # or pnpm install / yarn install / bun install
+         - name: Build with VitePress
+           run: npm run docs:build # or pnpm docs:build / yarn docs:build / bun run docs:build
+         - name: Upload artifact
+           uses: actions/upload-pages-artifact@v3
+           with:
+             path: docs/.vitepress/dist
+
+     # Deployment job
+     deploy:
+       environment:
+         name: github-pages
+         url: ${{ steps.deployment.outputs.page_url }}
+       needs: build
+       runs-on: ubuntu-latest
+       name: Deploy
+       steps:
+         - name: Deploy to GitHub Pages
+           id: deployment
+           uses: actions/deploy-pages@v4
+   ```
+
+   ::: warning
+   Make sure the `base` option in your VitePress is properly configured. See [Setting a Public Base Path](#setting-a-public-base-path) for more details.
+   :::
+
+2. In your repository's settings under "Pages" menu item, select "GitHub Actions" in "Build and deployment > Source".
+
+3. Push your changes to the `main` branch and wait for the GitHub Actions workflow to complete. You should see your site deployed to `https://<username>.github.io/[repository]/` or `https://<custom-domain>/` depending on your settings. Your site will automatically be deployed on every push to the `main` branch.
+
+### GitLab Pages
+
+1. Set `outDir` in VitePress config to `../public`. Configure `base` option to `'/<repository>/'` if you want to deploy to `https://<username>.gitlab.io/<repository>/`. You don't need `base` if you're deploying to custom domain, user or group pages, or have "Use unique domain" setting enabled in GitLab.
+
+2. Create a file named `.gitlab-ci.yml` in the root of your project with the content below. This will build and deploy your site whenever you make changes to your content:
+
+   ```yaml [.gitlab-ci.yml]
+   image: node:24
+   pages:
+     cache:
+       paths:
+         - node_modules/
+     script:
+       # - apk add git # Uncomment this if you're using small docker images like alpine and have lastUpdated enabled
+       - npm install
+       - npm run docs:build
+     artifacts:
+       paths:
+         - public
+     only:
+       - main
+   ```
+
+<!-- keep headings sorted alphabetically, leave nginx at the end -->
+
+### Azure
+
+1. Follow the [official documentation](https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration).
+
+2. Set these values in your configuration file (and remove the ones you don't require, like `api_location`):
+
+   - **`app_location`**: `/`
+   - **`output_location`**: `docs/.vitepress/dist`
+   - **`app_build_command`**: `npm run docs:build`
+
+### CloudRay
+
+You can deploy your VitePress project with [CloudRay](https://cloudray.io/) by following these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
+
+### Firebase
+
+1. Create `firebase.json` and `.firebaserc` at the root of your project:
+
+   `firebase.json`:
+
+   ```json [firebase.json]
+   {
+     "hosting": {
+       "public": "docs/.vitepress/dist",
+       "ignore": []
+     }
+   }
+   ```
+
+   `.firebaserc`:
+
+   ```json [.firebaserc]
+   {
+     "projects": {
+       "default": "<YOUR_FIREBASE_ID>"
+     }
+   }
+   ```
+
+2. After running `npm run docs:build`, run this command to deploy:
+
+   ```sh
+   firebase deploy
+   ```
+
+### Heroku
+
+1. Follow documentation and guide given in [`heroku-buildpack-static`](https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static).
+
+2. Create a file called `static.json` in the root of your project with the below content:
+
+   ```json [static.json]
+   {
+     "root": "docs/.vitepress/dist"
+   }
+   ```
+
+### Hostinger
+
+You can deploy your VitePress project with [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/support/how-to-deploy-a-nodejs-website-in-hostinger/). While configuring build settings, choose VitePress as the framework and adjust the root directory to `./docs`.
+
+### Lizard
+
+[Lizard (lizard.build)](https://lizard.build) builds VitePress sites from source and serves the generated HTML. For the layout used in this guide, it detects `docs:build` and serves `docs/.vitepress/dist` on port `80`.
+
+Install the [Lizard CLI](https://lizard.build/docs/cli) and sign in with `lizard login`. To deploy a local source directory, run these commands from the project root containing `package.json`:
+
+```sh
+lizard init --name vitepress-docs
+lizard add --service web
+lizard up --service web --port 80
+```
+
+Leave build and start command overrides unset to use automatic detection. For GitHub deployments or other layouts, see the [Lizard VitePress guide](https://lizard.build/docs/framework-guides/vitepress).
+
+### Stormkit
+
+You can deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
+
+### Surge
+
+After running `npm run docs:build`, run this command to deploy to [Surge](https://surge.sh):
+
+```sh
+npx surge docs/.vitepress/dist
+```
+
+### harvis
+
+After running `npm run docs:build`, run this command to deploy to [harvis](https://harvis.dev):
+
+```sh
+npx harvis docs/.vitepress/dist
+```
+
+### nginx
+
+Here is a example of an nginx server block configuration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files with proper caching headers as well as handling `cleanUrls: true`.
+
+```nginx
+map $uri $cache_control {
+    ~^/assets/  "public, max-age=31536000, immutable";
+    default     "no-cache";
+}
+
+server {
+    listen 8080;
+    listen [::]:8080;
+    server_name _;
+
+    root /usr/share/nginx/html;
+    index index.html;
+    charset utf-8;
+    server_tokens off;
+
+    absolute_redirect off;
+
+    gzip on;
+    gzip_vary on;
+    gzip_comp_level 5;
+    gzip_min_length 1024;
+    gzip_types
+        application/javascript
+        application/json
+        application/manifest+json
+        image/svg+xml
+        text/css
+        text/javascript
+        text/plain;
+
+    add_header Cache-Control $cache_control always;
+    add_header X-Content-Type-Options "nosniff" always;
+    add_header X-Frame-Options "SAMEORIGIN" always;
+    add_header Referrer-Policy "strict-origin-when-cross-origin" always;
+
+    location / {
+        try_files $uri $uri.html $uri/index.html =404;
+    }
+
+    location ~ ^(?<page>.+)/$ {
+        if (-f $document_root$page.html) {
+            return 301 $page$is_args$args;
+        }
+        try_files $page/index.html =404;
+    }
+
+    error_page 404 /404.html;
+}
+```

From fc23a66f066c8e6509a7e3127f0ea26a6acdcbbd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:24 +0200
Subject: [PATCH 014/199] docs(de): add missing documentation pages

---
 docs/de/guide/extending-default-theme.md | 302 +++++++++++++++++++++++
 1 file changed, 302 insertions(+)
 create mode 100644 docs/de/guide/extending-default-theme.md

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
new file mode 100644
index 000000000..1758d19b1
--- /dev/null
+++ b/docs/de/guide/extending-default-theme.md
@@ -0,0 +1,302 @@
+---
+outline: deep
+description: Customize and extend the VitePress default theme with custom CSS, components, layouts, and slots.
+---
+
+# Extending the Default Theme
+
+VitePress' default theme is optimized for documentation, and can be customized. Consult the [Default Theme Config Overview](../reference/default-theme-config) for a comprehensive list of options.
+
+However, there are a number of cases where configuration alone won't be enough. For example:
+
+1. You need to tweak the CSS styling;
+2. You need to modify the Vue app instance, for example to register global components;
+3. You need to inject custom content into the theme via layout slots.
+
+These advanced customizations will require using a custom theme that "extends" the default theme.
+
+::: tip
+Before proceeding, make sure to first read [Using a Custom Theme](./custom-theme) to understand how custom themes work.
+:::
+
+## Customizing CSS
+
+The default theme CSS is customizable by overriding root level CSS variables:
+
+```js [.vitepress/theme/index.js]
+import DefaultTheme from 'vitepress/theme'
+import './custom.css'
+
+export default DefaultTheme
+```
+
+```css
+/* .vitepress/theme/custom.css */
+:root {
+  --vp-c-brand-1: #646cff;
+  --vp-c-brand-2: #747bff;
+}
+```
+
+See [default theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css) that can be overridden.
+
+### Navbar
+
+The navbar draws a single background surface controlled by CSS variables, so its look can be changed without touching component internals:
+
+```css
+:root {
+  /* bar height and background */
+  --vp-nav-height: 4rem;
+  --vp-nav-bg-color: var(--vp-c-bg);
+
+  /* background while on top of the home page (unscrolled);
+     set to var(--vp-nav-bg-color) to opt out of the transparent treatment */
+  --vp-nav-home-bg-color: transparent;
+
+  /* filter applied to the content behind the bar */
+  --vp-nav-backdrop-filter: none;
+
+  /* the bar's bottom rule and the mobile menu background */
+  --vp-nav-divider-color: var(--vp-c-gutter);
+  --vp-nav-screen-bg-color: var(--vp-c-bg);
+}
+```
+
+For example, a frosted-glass navbar:
+
+```css
+:root {
+  --vp-nav-bg-color: color-mix(in srgb, var(--vp-c-bg) 65%, transparent);
+  --vp-nav-backdrop-filter: saturate(180%) blur(8px);
+}
+```
+
+The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color by default, and where the two bars meet they share a single blurred surface, so the glass stays continuous across them.
+
+::: warning
+`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. When using a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color without the blur.
+:::
+
+When the nav items don't fit the available width, they move into the `⋯` menu at the end of the navbar instead of being clipped, starting with the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized with [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
+
+## Using Different Fonts
+
+VitePress uses [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build output. The font is also auto preloaded in production. However, this may not be desirable if you want to use a different main font.
+
+To avoid including Inter in the build output, import the theme from `vitepress/theme-without-fonts` instead:
+
+```js [.vitepress/theme/index.js]
+import DefaultTheme from 'vitepress/theme-without-fonts'
+import './my-fonts.css'
+
+export default DefaultTheme
+```
+
+```css
+/* .vitepress/theme/my-fonts.css */
+:root {
+  --vp-font-family-base: /* normal text font */
+  --vp-font-family-mono: /* code font */
+}
+```
+
+::: warning
+If you are using optional components like the [Team Page](../reference/default-theme-team-page) components, make sure to also import them from `vitepress/theme-without-fonts`!
+:::
+
+If your font is a local file referenced via `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` with hashed filename. To preload this file, use the [transformHead](../reference/site-config#transformhead) build hook:
+
+```js [.vitepress/config.js]
+export default {
+  transformHead({ assets }) {
+    // adjust the regex accordingly to match your font
+    const myFontFile = assets.find(file => /font-name\.[\w-]+\.woff2/.test(file))
+    if (myFontFile) {
+      return [
+        [
+          'link',
+          {
+            rel: 'preload',
+            href: myFontFile,
+            as: 'font',
+            type: 'font/woff2',
+            crossorigin: ''
+          }
+        ]
+      ]
+    }
+  }
+}
+```
+
+## Registering Global Components
+
+```js [.vitepress/theme/index.js]
+import DefaultTheme from 'vitepress/theme'
+
+/** @type {import('vitepress').Theme} */
+export default {
+  extends: DefaultTheme,
+  enhanceApp({ app }) {
+    // register your custom global components
+    app.component('MyGlobalComponent' /* ... */)
+  }
+}
+```
+
+If you're using TypeScript:
+```ts [.vitepress/theme/index.ts]
+import type { Theme } from 'vitepress'
+import DefaultTheme from 'vitepress/theme'
+
+export default {
+  extends: DefaultTheme,
+  enhanceApp({ app }) {
+    // register your custom global components
+    app.component('MyGlobalComponent' /* ... */)
+  }
+} satisfies Theme
+```
+
+Since we are using Vite, you can also leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of components.
+
+## Layout Slots
+
+The default theme's `<Layout/>` component has a few slots that can be used to inject content at certain locations of the page. Here's an example of injecting a component into the before outline:
+
+```js [.vitepress/theme/index.js]
+import DefaultTheme from 'vitepress/theme'
+import MyLayout from './MyLayout.vue'
+
+export default {
+  extends: DefaultTheme,
+  // override the Layout with a wrapper component that
+  // injects the slots
+  Layout: MyLayout
+}
+```
+
+```vue [.vitepress/theme/MyLayout.vue]
+<script setup>
+import DefaultTheme from 'vitepress/theme'
+
+const { Layout } = DefaultTheme
+</script>
+
+<template>
+  <Layout>
+    <template #aside-outline-before>
+      My custom sidebar top content
+    </template>
+  </Layout>
+</template>
+```
+
+Or you could use render function as well.
+
+```js [.vitepress/theme/index.js]
+import { h } from 'vue'
+import DefaultTheme from 'vitepress/theme'
+import MyComponent from './MyComponent.vue'
+
+export default {
+  extends: DefaultTheme,
+  Layout() {
+    return h(DefaultTheme.Layout, null, {
+      'aside-outline-before': () => h(MyComponent)
+    })
+  }
+}
+```
+
+Full list of slots available in the default theme layout:
+
+- When `layout: 'doc'` (default) is enabled via frontmatter:
+  - `doc-top`
+  - `doc-bottom`
+  - `doc-footer-before`
+  - `doc-before`
+  - `doc-after`
+  - `sidebar-nav-before`
+  - `sidebar-nav-after`
+  - `aside-top`
+  - `aside-bottom`
+  - `aside-outline-before`
+  - `aside-outline-after`
+  - `aside-ads-before`
+  - `aside-ads-after`
+- When `layout: 'home'` is enabled via frontmatter:
+  - `home-hero-before`
+  - `home-hero-info-before`
+  - `home-hero-info`
+  - `home-hero-info-after`
+  - `home-hero-actions-before-actions`
+  - `home-hero-actions-after`
+  - `home-hero-image`
+  - `home-hero-after`
+  - `home-features-before`
+  - `home-features-after`
+- When `layout: 'page'` is enabled via frontmatter:
+  - `page-top`
+  - `page-bottom`
+- On not found (404) page:
+  - `not-found`
+- Always:
+  - `layout-top`
+  - `layout-bottom`
+  - `nav-bar-title-before`
+  - `nav-bar-title-after`
+  - `nav-bar-content-before`
+  - `nav-bar-content-after`
+  - `nav-screen-content-before`
+  - `nav-screen-content-after`
+
+## Using View Transitions API
+
+### On Appearance Toggle
+
+You can extend the default theme to provide a custom transition when the color mode is toggled. An example:
+
+<<< @/components/AppearanceToggleTransition.vue [.vitepress/theme/Layout.vue]
+
+Result (**warning!**: flashing colors, sudden movements, bright lights):
+
+<details>
+<summary>Demo</summary>
+
+![Appearance Toggle Transition Demo](/appearance-toggle-transition.webp)
+
+</details>
+
+Refer [Chrome Docs](https://developer.chrome.com/docs/web-platform/view-transitions/) from more details on view transitions.
+
+### On Route Change
+
+Coming soon.
+
+## Overriding Internal Components
+
+You can use Vite's [aliases](https://vite.dev/config/shared-options.html#resolve-alias) to replace default theme components with your custom ones:
+
+```ts
+import { fileURLToPath, URL } from 'node:url'
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  vite: {
+    resolve: {
+      alias: [
+        {
+          find: /^.*\/VPNavBar\.vue$/,
+          replacement: fileURLToPath(
+            new URL('./theme/components/CustomNavBar.vue', import.meta.url)
+          )
+        }
+      ]
+    }
+  }
+})
+```
+
+To know the exact name of the component refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/theme-default/components). Since the components are internal, there is a slight chance their name is updated between minor releases.

From e4aca759240c01453098d1ae8a6df8b86ee2d25d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:26 +0200
Subject: [PATCH 015/199] docs(de): add missing documentation pages

---
 docs/de/guide/frontmatter.md | 54 ++++++++++++++++++++++++++++++++++++
 1 file changed, 54 insertions(+)
 create mode 100644 docs/de/guide/frontmatter.md

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
new file mode 100644
index 000000000..e8dd329a3
--- /dev/null
+++ b/docs/de/guide/frontmatter.md
@@ -0,0 +1,54 @@
+---
+description: Learn how to use YAML frontmatter in VitePress Markdown files to control page-level metadata and behavior.
+---
+
+# Frontmatter
+
+## Usage
+
+VitePress supports YAML frontmatter in all Markdown files, parsing them with [gray-matter](https://github.com/jonschlinkert/gray-matter). The frontmatter must be at the top of the Markdown file (before any elements including `<script>` tags), and must take the form of valid YAML set between triple-dashed lines. Example:
+
+```md
+---
+title: Docs with VitePress
+editLink: true
+---
+```
+
+Many site or default theme config options have corresponding options in frontmatter. You can use frontmatter to override specific behavior for the current page only. For details, see [Frontmatter Config Reference](../reference/frontmatter-config).
+
+You can also define custom frontmatter data of your own, to be used in dynamic Vue expressions on the page.
+
+## Accessing Frontmatter Data
+
+Frontmatter data can be accessed via the special `$frontmatter` global variable:
+
+Here's an example of how you could use it in your Markdown file:
+
+```md
+---
+title: Docs with VitePress
+editLink: true
+---
+
+# {{ $frontmatter.title }}
+
+Guide content
+```
+
+Property accesses like `{{ $frontmatter.title }}` are resolved while the Markdown is rendered, so the value also ends up in the local search index, in [content loader](./data-loading#createcontentloader) output, in heading anchors - the heading above gets `id="docs-with-vitepress"` - and in link targets written without spaces around the expression, like `[text]({{$frontmatter.link}})`. Other expressions are evaluated by Vue at runtime as usual, and wrapping an expression in [`v-pre`](./using-vue#escaping) shows it literally.
+
+You can also access current page's frontmatter data in `<script setup>` with the [`useData()`](../reference/runtime-api#usedata) helper.
+
+## Alternative Frontmatter Formats
+
+VitePress also supports JSON frontmatter syntax, starting and ending in curly braces:
+
+```json
+---
+{
+  "title": "Blogging Like a Hacker",
+  "editLink": true
+}
+---
+```

From 3cbedafcd3bd234ee4d11a12fd20415ce23cfdad Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:28 +0200
Subject: [PATCH 016/199] docs(de): add missing documentation pages

---
 docs/de/guide/getting-started.md | 207 +++++++++++++++++++++++++++++++
 1 file changed, 207 insertions(+)
 create mode 100644 docs/de/guide/getting-started.md

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
new file mode 100644
index 000000000..a181192d0
--- /dev/null
+++ b/docs/de/guide/getting-started.md
@@ -0,0 +1,207 @@
+---
+description: Get up and running with VitePress. Learn how to install, scaffold, and start developing your documentation site.
+---
+
+# Getting Started
+
+## Try It Online
+
+You can try VitePress directly in your browser on [StackBlitz](https://vitepress.new).
+
+## Installation
+
+### Prerequisites
+
+- [Node.js](https://nodejs.org/) version 22 or higher.
+- Terminal for accessing VitePress via its command line interface (CLI).
+- Text Editor with [Markdown](https://en.wikipedia.org/wiki/Markdown) syntax support.
+  - [VSCode](https://code.visualstudio.com/) is recommended, along with the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar).
+
+VitePress can be used on its own, or be installed into an existing project. In both cases, you can install it with:
+
+::: code-group
+
+```sh [npm]
+$ npm add -D vitepress@next
+```
+
+```sh [pnpm]
+$ pnpm add -D vitepress@next
+```
+
+```sh [yarn]
+$ yarn add -D vitepress@next vue
+```
+
+```sh [bun]
+$ bun add -D vitepress@next
+```
+
+```sh [deno]
+$ deno add -D vitepress@next
+```
+
+:::
+
+::: tip NOTE
+
+VitePress is an ESM-only package. Don't use `require()` to import it, and make sure your nearest `package.json` contains `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Refer to [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) for more details. Also, inside async CJS contexts, you can use `await import('vitepress')` instead.
+
+:::
+
+### Setup Wizard
+
+VitePress ships with a command line setup wizard that will help you scaffold a basic project. After installation, start the wizard by running:
+
+::: code-group
+
+```sh [npm]
+$ npx vitepress init
+```
+
+```sh [pnpm]
+$ pnpm vitepress init
+```
+
+```sh [yarn]
+$ yarn vitepress init
+```
+
+```sh [bun]
+$ bun vitepress init
+```
+
+:::
+
+You will be greeted with a few simple questions:
+
+<<< @/snippets/init.ansi
+
+::: tip Vue as Peer Dependency
+If you intend to perform customization that uses Vue components or APIs, you should also explicitly install `vue` as a dependency.
+:::
+
+## File Structure
+
+If you are building a standalone VitePress site, you can scaffold the site in your current directory (`./`). However, if you are installing VitePress in an existing project alongside other source code, it is recommended to scaffold the site in a nested directory (e.g. `./docs`) so that it is separate from the rest of the project.
+
+Assuming you chose to scaffold the VitePress project in `./docs`, the generated file structure should look like this:
+
+```
+.
+├─ docs
+│  ├─ .vitepress
+│  │  └─ config.js
+│  ├─ api-examples.md
+│  ├─ markdown-examples.md
+│  └─ index.md
+└─ package.json
+```
+
+The `docs` directory is considered the **project root** of the VitePress site. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+
+::: tip
+By default, VitePress stores its dev server cache in `.vitepress/cache`, and the production build output in `.vitepress/dist`. If using Git, you should add them to your `.gitignore` file. These locations can also be [configured](../reference/site-config#outdir).
+:::
+
+### The Config File
+
+The config file (`.vitepress/config.js`) allows you to customize various aspects of your VitePress site, with the most basic options being the title and description of the site:
+
+```js [.vitepress/config.js]
+export default {
+  // site-level options
+  title: 'VitePress',
+  description: 'Just playing around.',
+
+  themeConfig: {
+    // theme-level options
+  }
+}
+```
+
+You can also configure the behavior of the theme via the `themeConfig` option. Consult the [Config Reference](../reference/site-config) for full details on all config options.
+
+### Source Files
+
+Markdown files outside the `.vitepress` directory are considered **source files**.
+
+VitePress uses **file-based routing**: each `.md` file is compiled into a corresponding `.html` file with the same path. For example, `index.md` will be compiled into `index.html`, and can be visited at the root path `/` of the resulting VitePress site.
+
+VitePress also provides the ability to generate clean URLs, rewrite paths, and dynamically generate pages. These will be covered in the [Routing Guide](./routing).
+
+## Up and Running
+
+The tool should have also injected the following npm scripts to your `package.json` if you allowed it to do so during the setup process:
+
+```json [package.json]
+{
+  ...
+  "scripts": {
+    "docs:dev": "vitepress dev docs",
+    "docs:build": "vitepress build docs",
+    "docs:preview": "vitepress preview docs"
+  },
+  ...
+}
+```
+
+The `docs:dev` script will start a local dev server with instant hot updates. Run it with the following command:
+
+::: code-group
+
+```sh [npm]
+$ npm run docs:dev
+```
+
+```sh [pnpm]
+$ pnpm run docs:dev
+```
+
+```sh [yarn]
+$ yarn docs:dev
+```
+
+```sh [bun]
+$ bun run docs:dev
+```
+
+:::
+
+Instead of npm scripts, you can also invoke VitePress directly with:
+
+::: code-group
+
+```sh [npm]
+$ npx vitepress dev docs
+```
+
+```sh [pnpm]
+$ pnpm vitepress dev docs
+```
+
+```sh [yarn]
+$ yarn vitepress dev docs
+```
+
+```sh [bun]
+$ bun vitepress dev docs
+```
+
+:::
+
+More command line usage is documented in the [CLI Reference](../reference/cli).
+
+The dev server should be running at `http://localhost:5173`. Visit the URL in your browser to see your new site in action!
+
+## What's Next?
+
+- To better understand how markdown files are mapped to generated HTML, proceed to the [Routing Guide](./routing).
+
+- To discover more about what you can do on the page, such as writing markdown content or using Vue Components, refer to the "Writing" section of the guide. A great place to start would be to learn about [Markdown Extensions](./markdown).
+
+- To explore the features provided by the default documentation theme, check out the [Default Theme Config Reference](../reference/default-theme-config).
+
+- If you want to further customize the appearance of your site, explore how to either [Extend the Default Theme](./extending-default-theme) or [Build a Custom Theme](./custom-theme).
+
+- Once your documentation site takes shape, make sure to read the [Deployment Guide](./deploy).

From 6aee2ff88bac5a91b7e2dac911dc2cd5f5d43110 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:31 +0200
Subject: [PATCH 017/199] docs(de): add missing documentation pages

---
 docs/de/guide/i18n.md | 163 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 163 insertions(+)
 create mode 100644 docs/de/guide/i18n.md

diff --git a/docs/de/guide/i18n.md b/docs/de/guide/i18n.md
new file mode 100644
index 000000000..ff0bcff08
--- /dev/null
+++ b/docs/de/guide/i18n.md
@@ -0,0 +1,163 @@
+---
+description: Set up internationalization (i18n) in VitePress to support multiple languages for your site.
+---
+
+# Internationalization
+
+To use the built-in i18n features, one needs to create a directory structure as follows:
+
+```
+docs/
+├─ es/
+│  ├─ foo.md
+├─ fr/
+│  ├─ foo.md
+├─ foo.md
+```
+
+Then in `docs/.vitepress/config.ts`:
+
+```ts [docs/.vitepress/config.ts]
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  // shared properties and other top-level stuff...
+
+  locales: {
+    root: {
+      label: 'English',
+      lang: 'en'
+    },
+    fr: {
+      label: 'French',
+      lang: 'fr', // optional, will be added  as `lang` attribute on `html` tag
+      link: '/fr/guide' // default /fr/ -- shows on navbar translations menu, can be external
+
+      // other locale specific properties...
+    }
+  }
+})
+```
+
+The following properties can be overridden for each locale (including root):
+
+```ts
+interface LocaleSpecificConfig<ThemeConfig = any> {
+  lang?: string
+  dir?: string
+  title?: string
+  titleTemplate?: string | boolean
+  description?: string
+  head?: HeadConfig[] // will be merged with existing head entries, duplicate meta tags are automatically removed
+  themeConfig?: ThemeConfig // will be shallow merged, common stuff can be put in top-level themeConfig entry
+}
+```
+
+Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-theme.d.ts) interface for details on customizing the placeholder texts of the default theme. Don't override `themeConfig.algolia` or `themeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-theme-search#algolia-search-i18n) for using multilingual search.
+
+**Pro tip:** Config file can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a configuration file per locale and then merge and export them from `index.ts`.
+
+## Per-locale Markdown Strings
+
+Strings baked into pages by the markdown renderer - the default titles of [custom containers](./markdown#custom-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale with the `markdown` key of a locale entry:
+
+```ts [docs/.vitepress/config.ts]
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  locales: {
+    root: { label: 'English', lang: 'en' },
+    zh: {
+      label: '简体中文',
+      lang: 'zh-Hans',
+      markdown: {
+        container: {
+          tipLabel: '提示',
+          warningLabel: '警告'
+          // ...the other labels, and titles of `customContainers`
+        },
+        codeCopyButton: {
+          tooltipText: '复制代码',
+          copiedText: '已复制'
+        }
+      }
+    }
+  }
+})
+```
+
+Values fall back to the root-level `markdown` options when a locale leaves them unset. Locale entries can only override the titles of containers registered at the root level - registering new containers per locale is not supported. Also note that since the markdown renderer is created once for the whole site, these can only be declared in the main config file, not in additional configs.
+
+## Separate directory for each locale
+
+The following is a perfectly fine structure:
+
+```
+docs/
+├─ en/
+│  ├─ foo.md
+├─ es/
+│  ├─ foo.md
+├─ fr/
+   ├─ foo.md
+```
+
+However, VitePress won't redirect `/` to `/en/` by default. You'll need to configure your server for that. For example, on Netlify, you can add a `docs/public/_redirects` file like this:
+
+```
+/*  /es/:splat  302  Language=es
+/*  /fr/:splat  302  Language=fr
+/*  /en/:splat  302
+```
+
+**Pro tip:** If using the above approach, you can use `nf_lang` cookie to persist user's language choice:
+
+```ts [docs/.vitepress/theme/index.ts]
+import DefaultTheme from 'vitepress/theme'
+import Layout from './Layout.vue'
+
+export default {
+  extends: DefaultTheme,
+  Layout
+}
+```
+
+```vue [docs/.vitepress/theme/Layout.vue]
+<script setup lang="ts">
+import DefaultTheme from 'vitepress/theme'
+import { useData, inBrowser } from 'vitepress'
+import { watchEffect } from 'vue'
+
+const { lang } = useData()
+watchEffect(() => {
+  if (inBrowser) {
+    document.cookie = `nf_lang=${lang.value}; expires=Mon, 1 Jan 2030 00:00:00 UTC; path=/`
+  }
+})
+</script>
+
+<template>
+  <DefaultTheme.Layout />
+</template>
+```
+
+## RTL Support
+
+For right-to-left languages, set `dir: 'rtl'` in the config. The default theme is laid out with [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_values), so the layout, the navigation and directional icons follow the document direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
+
+```ts [docs/.vitepress/config.ts]
+export default {
+  lang: 'fa-IR',
+  dir: 'rtl'
+}
+```
+
+For a multilingual site, set `dir` per locale in `locales`. It can also be overridden for a single page with the [`dir`](../reference/frontmatter-config#dir) frontmatter option. Code blocks always stay left-to-right.
+
+When adding your own styles, prefer logical properties such as `margin-inline-start` over `margin-left`, and mirror your own directional icons in right-to-left layouts:
+
+```css
+[dir='rtl'] .my-arrow-icon {
+  scale: -1 1;
+}
+```

From 798b287d98c67365c64afe3df9e9484596f24339 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:41:33 +0200
Subject: [PATCH 018/199] docs(de): add missing documentation pages

---
 docs/de/guide/markdown.md | 1195 +++++++++++++++++++++++++++++++++++++
 1 file changed, 1195 insertions(+)
 create mode 100644 docs/de/guide/markdown.md

diff --git a/docs/de/guide/markdown.md b/docs/de/guide/markdown.md
new file mode 100644
index 000000000..574e9626a
--- /dev/null
+++ b/docs/de/guide/markdown.md
@@ -0,0 +1,1195 @@
+---
+description: VitePress built-in Markdown extensions including custom containers, code blocks with syntax highlighting, line highlighting, code groups, and more.
+outline: deep
+---
+
+# Markdown Extensions
+
+VitePress comes with built in Markdown Extensions.
+
+## Header Anchors
+
+Headers automatically get anchor links applied. Rendering of anchors can be configured using the `markdown.anchor` option.
+
+### Custom anchors
+
+To specify a custom anchor tag for a heading instead of using the auto-generated one, add a suffix to the heading:
+
+```
+# Using custom anchors {#my-anchor}
+```
+
+This allows you to link to the heading as `#my-anchor` instead of the default `#using-custom-anchors`.
+
+## Links
+
+Both internal and external links get special treatment.
+
+### Internal Links
+
+Internal links are converted to router links for SPA navigation. Also, every `index.md` contained in each sub-directory will automatically be converted to `index.html`, with corresponding URL `/`.
+
+For example, given the following directory structure:
+
+```
+.
+├─ index.md
+├─ foo
+│  ├─ index.md
+│  ├─ one.md
+│  └─ two.md
+└─ bar
+   ├─ index.md
+   ├─ three.md
+   └─ four.md
+```
+
+And providing you are in `foo/one.md`:
+
+```md
+[Home](/) <!-- sends the user to the root index.md -->
+[foo](/foo/) <!-- sends the user to index.html of directory foo -->
+[foo heading](./#heading) <!-- anchors user to a heading in the foo index file -->
+[bar - three](../bar/three) <!-- you can omit extension -->
+[bar - three](../bar/three.md) <!-- you can append .md -->
+[bar - four](../bar/four.html) <!-- or you can append .html -->
+```
+
+### Page Suffix
+
+Pages and internal links get generated with the `.html` suffix by default.
+
+### External Links
+
+Outbound links automatically get `target="_blank" rel="noreferrer"`:
+
+- [vuejs.org](https://vuejs.org)
+- [VitePress on GitHub](https://github.com/vuejs/vitepress)
+
+## Frontmatter
+
+[YAML frontmatter](https://jekyllrb.com/docs/front-matter/) is supported out of the box:
+
+```yaml
+---
+title: Blogging Like a Hacker
+lang: en-US
+---
+```
+
+This data will be available to the rest of the page, along with all custom and theming components.
+
+For more details, see [Frontmatter](../reference/frontmatter-config).
+
+## GitHub-Style Tables
+
+**Input**
+
+```md
+| Tables        |      Are      |  Cool |
+| ------------- | :-----------: | ----: |
+| col 3 is      | right-aligned | $1600 |
+| col 2 is      |   centered    |   $12 |
+| zebra stripes |   are neat    |    $1 |
+```
+
+**Output**
+
+| Tables        |      Are      |   Cool |
+| ------------- | :-----------: | -----: |
+| col 3 is      | right-aligned | \$1600 |
+| col 2 is      |   centered    |   \$12 |
+| zebra stripes |   are neat    |    \$1 |
+
+## Task Lists
+
+**Input**
+
+```md
+- [ ] Write the press release
+- [x] Update the website
+```
+
+**Output**
+
+- [ ] Write the press release
+- [x] Update the website
+
+## Footnotes
+
+**Input**
+
+```md
+Footnotes are supported[^1], including inline ones^[This is an inline footnote.].
+
+[^1]: Definitions can contain **markdown** and are rendered at the end of the page.
+```
+
+**Output**
+
+Footnotes are supported[^1], including inline ones^[This is an inline footnote.].
+
+[^1]: Definitions can contain **markdown** and are rendered at the end of the page.
+
+## Emoji :tada:
+
+**Input**
+
+```
+:tada: :100:
+```
+
+**Output**
+
+:tada: :100:
+
+A [list of all emojis](https://github.com/mdit-plugins/mdit-plugins/blob/main/packages/plugin-emoji/src/data/full.ts) is available.
+
+## Table of Contents
+
+**Input**
+
+```
+[[toc]]
+```
+
+**Output**
+
+[[toc]]
+
+Rendering of the TOC can be configured using the `markdown.toc` option.
+
+## Custom Containers
+
+Custom containers can be defined by their types, titles, and contents.
+
+### Default Title
+
+**Input**
+
+```md
+::: info
+This is an info box.
+:::
+
+::: tip
+This is a tip.
+:::
+
+::: warning
+This is a warning.
+:::
+
+::: danger
+This is a dangerous warning.
+:::
+
+::: details
+This is a details block.
+:::
+```
+
+**Output**
+
+::: info
+This is an info box.
+:::
+
+::: tip
+This is a tip.
+:::
+
+::: warning
+This is a warning.
+:::
+
+::: danger
+This is a dangerous warning.
+:::
+
+::: details
+This is a details block.
+:::
+
+### Custom Title
+
+You may set custom title by appending the text right after the "type" of the container.
+
+**Input**
+
+````md
+::: danger STOP
+Danger zone, do not proceed
+:::
+
+::: details Click me to toggle the code
+```js
+console.log('Hello, VitePress!')
+```
+:::
+````
+
+**Output**
+
+::: danger STOP
+Danger zone, do not proceed
+:::
+
+::: details Click me to toggle the code
+```js
+console.log('Hello, VitePress!')
+```
+:::
+
+Also, you may set custom titles globally by adding the following content in site config, helpful if not writing in English:
+
+```ts
+// config.ts
+export default defineConfig({
+  // ...
+  markdown: {
+    container: {
+      tipLabel: '提示',
+      warningLabel: '警告',
+      dangerLabel: '危险',
+      infoLabel: '信息',
+      detailsLabel: '详细信息'
+    }
+  }
+  // ...
+})
+```
+
+On multilingual sites, these labels can also be overridden per locale - see [Per-locale Markdown Strings](./i18n#per-locale-markdown-strings).
+
+### Registering New Containers
+
+Beyond the built-in types, you can register additional containers by mapping their names to their default titles:
+
+```ts
+// config.ts
+export default defineConfig({
+  // ...
+  markdown: {
+    container: {
+      customContainers: {
+        success: 'SUCCESS'
+      }
+    }
+  }
+  // ...
+})
+```
+
+Registered names work like the built-in ones - including custom titles, attributes, and the [GitHub-style alert syntax](#github-flavored-alerts):
+
+```md
+::: success
+You have completed the walkthrough!
+:::
+
+> [!SUCCESS] Custom title
+> This renders the same way.
+```
+
+New containers ship without any styling, so add some in your theme using the container name as the class. For this example, the default theme's palette already provides fitting colors:
+
+```css
+/* .vitepress/theme/custom.css */
+.custom-block.success {
+  border-color: transparent;
+  color: var(--vp-c-text-1);
+  background-color: var(--vp-c-success-soft);
+}
+```
+
+### Nesting
+
+The `:::` markers follow the same rules as fenced code blocks (` ``` `): a fence is only closed by a matching fence that is **at least as long** as the one that opened it. To nest containers (or to mix them with [code groups](#code-groups)) make the outer fence longer than the ones inside it.
+
+**Input**
+
+`````md
+:::: info Outer container
+This box contains another container.
+
+::: details Inner container
+```js
+console.log('Hello, VitePress!')
+```
+:::
+::::
+`````
+
+**Output**
+
+:::: info Outer container
+This box contains another container.
+
+::: details Inner container
+```js
+console.log('Hello, VitePress!')
+```
+:::
+::::
+
+### Additional Attributes
+
+You can add additional attributes to the custom containers. We use [@mdit/plugin-attrs](https://mdit-plugins.github.io/attrs.html) for this feature, and it is supported on almost all markdown elements. For example, you can set the `open` attribute to make the details block open by default:
+
+**Input**
+
+````md
+::: details Click me to toggle the code {open}
+```js
+console.log('Hello, VitePress!')
+```
+:::
+````
+
+**Output**
+
+::: details Click me to toggle the code {open}
+```js
+console.log('Hello, VitePress!')
+```
+:::
+
+The special `no-title` attribute renders a container without a title element (it has no effect on `details`, which always needs its summary):
+
+**Input**
+
+```md
+::: tip {no-title}
+Just want to try it out? Skip to the [Quickstart](./getting-started).
+:::
+```
+
+**Output**
+
+::: tip {no-title}
+Just want to try it out? Skip to the [Quickstart](./getting-started).
+:::
+
+### `raw`
+
+This is a special container that can be used to prevent style and router conflicts with VitePress. This is especially useful when you're documenting component libraries.
+
+**Syntax**
+
+```md
+::: raw
+Wraps in a `<div class="vp-raw">`
+:::
+```
+
+`vp-raw` class can be directly used on elements too. Style isolation is currently opt-in:
+
+- Install `postcss` with your preferred package manager:
+
+  ```sh
+  $ npm add -D postcss
+  ```
+
+- Create a file named `docs/postcss.config.mjs` and add this to it:
+
+  ```js
+  import { postcssIsolateStyles } from 'vitepress'
+
+  export default {
+    plugins: [postcssIsolateStyles()]
+  }
+  ```
+
+  You can pass its options like this:
+
+  ```js
+  postcssIsolateStyles({
+    includeFiles: [/custom\.css/] // defaults to [/vp-doc\.css/, /base\.css/]
+  })
+  ```
+
+## GitHub-flavored Alerts
+
+VitePress also supports [GitHub-flavored alerts](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts) to render as callouts. They will be rendered the same as the [custom containers](#custom-containers). Unlike on GitHub, text placed right after the marker becomes the title of the alert (`> [!NOTE] Custom Title`), and [containers you registered yourself](#registering-new-containers) work here too.
+
+```md
+> [!NOTE]
+> Highlights information that users should take into account, even when skimming.
+
+> [!TIP]
+> Optional information to help a user be more successful.
+
+> [!IMPORTANT]
+> Crucial information necessary for users to succeed.
+
+> [!WARNING]
+> Critical content demanding immediate user attention due to potential risks.
+
+> [!CAUTION]
+> Negative potential consequences of an action.
+```
+
+> [!NOTE]
+> Highlights information that users should take into account, even when skimming.
+
+> [!TIP]
+> Optional information to help a user be more successful.
+
+> [!IMPORTANT]
+> Crucial information necessary for users to succeed.
+
+> [!WARNING]
+> Critical content demanding immediate user attention due to potential risks.
+
+> [!CAUTION]
+> Negative potential consequences of an action.
+
+By default, alert colors match GitHub's, with caution and danger both rendering in red. Enable [`themeConfig.gradedContainers`](../reference/default-theme-config#gradedcontainers) to use a graded severity scale: danger (red), warning (orange), and caution (yellow). Note that `[!DANGER]` is a VitePress extension and will render as a regular blockquote on GitHub.
+
+## Syntax Highlighting in Code Blocks
+
+VitePress uses [Shiki](https://github.com/shikijs/shiki) to highlight language syntax in Markdown code blocks, using coloured text. Shiki supports a wide variety of programming languages. All you need to do is append a valid language alias to the beginning backticks for the code block:
+
+**Input**
+
+````
+```js
+export default {
+  name: 'MyComponent',
+  // ...
+}
+```
+````
+
+````
+```html
+<ul>
+  <li v-for="todo in todos" :key="todo.id">
+    {{ todo.text }}
+  </li>
+</ul>
+```
+````
+
+**Output**
+
+```js
+export default {
+  name: 'MyComponent'
+  // ...
+}
+```
+
+```html
+<ul>
+  <li v-for="todo in todos" :key="todo.id">
+    {{ todo.text }}
+  </li>
+</ul>
+```
+
+A [list of valid languages](https://shiki.style/languages) is available on Shiki's repository.
+
+You may also customize syntax highlight theme, configure language aliases, and set custom language labels in app config. Please see [`markdown` options](../reference/site-config#markdown) for more details.
+
+## Line Highlighting in Code Blocks
+
+**Input**
+
+````
+```js{4}
+export default {
+  data () {
+    return {
+      msg: 'Highlighted!'
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js{4}
+export default {
+  data () {
+    return {
+      msg: 'Highlighted!'
+    }
+  }
+}
+```
+
+In addition to a single line, you can also specify multiple single lines, ranges, or both:
+
+- Line ranges: for example `{5-8}`, `{3-10}`, `{10-17}`
+- Multiple single lines: for example `{4,7,9}`
+- Line ranges and single lines: for example `{4,7-13,16,23-27,40}`
+
+**Input**
+
+````
+```js{1,4,6-8}
+export default { // Highlighted
+  data () {
+    return {
+      msg: `Highlighted!
+      This line isn't highlighted,
+      but this and the next 2 are.`,
+      motd: 'VitePress is awesome',
+      lorem: 'ipsum'
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js{1,4,6-8}
+export default { // Highlighted
+  data () {
+    return {
+      msg: `Highlighted!
+      This line isn't highlighted,
+      but this and the next 2 are.`,
+      motd: 'VitePress is awesome',
+      lorem: 'ipsum',
+    }
+  }
+}
+```
+
+Alternatively, it's possible to highlight directly in the line by using the `// [!code highlight]` comment.
+
+**Input**
+
+````
+```js
+export default {
+  data () {
+    return {
+      msg: 'Highlighted!' // [!!code highlight]
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js
+export default {
+  data() {
+    return {
+      msg: 'Highlighted!' // [!code highlight]
+    }
+  }
+}
+```
+
+## Focus in Code Blocks
+
+Adding the `// [!code focus]` comment on a line will focus it and blur the other parts of the code.
+
+Additionally, you can define a number of lines to focus using `// [!code focus:<lines>]`.
+
+**Input**
+
+````
+```js
+export default {
+  data () {
+    return {
+      msg: 'Focused!' // [!!code focus]
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js
+export default {
+  data() {
+    return {
+      msg: 'Focused!' // [!code focus]
+    }
+  }
+}
+```
+
+## Colored Diffs in Code Blocks
+
+Adding the `// [!code --]` or `// [!code ++]` comments on a line will create a diff of that line, while keeping the colors of the codeblock.
+
+**Input**
+
+````
+```js
+export default {
+  data () {
+    return {
+      msg: 'Removed' // [!!code --]
+      msg: 'Added' // [!!code ++]
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js
+export default {
+  data () {
+    return {
+      msg: 'Removed' // [!code --]
+      msg: 'Added' // [!code ++]
+    }
+  }
+}
+```
+
+## Errors and Warnings in Code Blocks
+
+Adding the `// [!code warning]` or `// [!code error]` comments on a line will color it accordingly.
+
+**Input**
+
+````
+```js
+export default {
+  data () {
+    return {
+      msg: 'Error', // [!!code error]
+      msg: 'Warning' // [!!code warning]
+    }
+  }
+}
+```
+````
+
+**Output**
+
+```js
+export default {
+  data() {
+    return {
+      msg: 'Error', // [!code error]
+      msg: 'Warning' // [!code warning]
+    }
+  }
+}
+```
+
+## Line Numbers
+
+You can enable line numbers for each code blocks via config:
+
+```js
+export default {
+  markdown: {
+    lineNumbers: true
+  }
+}
+```
+
+Please see [`markdown` options](../reference/site-config#markdown) for more details.
+
+You can add `:line-numbers` / `:no-line-numbers` mark in your fenced code blocks to override the value set in config.
+
+You can also customize the starting line number by adding `=` after `:line-numbers`. For example, `:line-numbers=2` means the line numbers in code blocks will start from `2`.
+
+**Input**
+
+````md
+```ts {1}
+// line-numbers is disabled by default
+const line2 = 'This is line 2'
+const line3 = 'This is line 3'
+```
+
+```ts:line-numbers {1}
+// line-numbers is enabled
+const line2 = 'This is line 2'
+const line3 = 'This is line 3'
+```
+
+```ts:line-numbers=2 {1}
+// line-numbers is enabled and start from 2
+const line3 = 'This is line 3'
+const line4 = 'This is line 4'
+```
+````
+
+**Output**
+
+```ts {1}
+// line-numbers is disabled by default
+const line2 = 'This is line 2'
+const line3 = 'This is line 3'
+```
+
+```ts:line-numbers {1}
+// line-numbers is enabled
+const line2 = 'This is line 2'
+const line3 = 'This is line 3'
+```
+
+```ts:line-numbers=2 {1}
+// line-numbers is enabled and start from 2
+const line3 = 'This is line 3'
+const line4 = 'This is line 4'
+```
+
+## Import Code Snippets
+
+You can import code snippets from existing files via following syntax:
+
+```md
+<<< @/filepath
+```
+
+It also supports [line highlighting](#line-highlighting-in-code-blocks):
+
+```md
+<<< @/filepath{highlightLines}
+```
+
+**Input**
+
+```md
+<<< @/snippets/snippet.js{2}
+```
+
+**Code file**
+
+<<< @/snippets/snippet.js
+
+**Output**
+
+<<< @/snippets/snippet.js{2}
+
+::: tip
+The value of `@` corresponds to the source root. By default it's the VitePress project root, unless `srcDir` is configured. Alternatively, you can also import from relative paths:
+
+```md
+<<< ../snippets/snippet.js
+```
+
+:::
+
+You can also use a [VS Code region](https://code.visualstudio.com/docs/editor/codebasics#_folding) to only include the corresponding part of the code file. You can provide a custom region name after a `#` following the filepath:
+
+**Input**
+
+```md
+<<< @/snippets/snippet-with-region.js#snippet{1}
+```
+
+**Code file**
+
+<<< @/snippets/snippet-with-region.js
+
+**Output**
+
+<<< @/snippets/snippet-with-region.js#snippet{1}
+
+If a file contains multiple regions with the same name, all of them are imported and concatenated — including regions written in different comment styles, such as a `<!-- #region -->` in the template and a `// #region` in the script of the same Vue SFC. The marker comments delimiting them are removed from the output; set `markdown.snippet.stripRegionMarkers` to `'all'` to also remove markers of other comment styles nested inside the region, or to `false` to keep all of them.
+
+::: tip
+Region names may contain letters, digits, `_`, `-` and `.`. Since the name is taken from the end of the path, a file whose name itself contains a `#` needs an explicit region — write `<<< ./my#file.js#region` rather than `<<< ./my#file.js`.
+:::
+
+::: warning
+Importing a file or region that does not exist throws a build error. Set `markdown.snippet.silent: true` to log a warning and render nothing instead.
+:::
+
+You can also specify the language inside the braces (`{}`) like this:
+
+```md
+<<< @/snippets/snippet.cs{c#}
+
+<!-- with line highlighting: -->
+
+<<< @/snippets/snippet.cs{1,2,4-6 c#}
+
+<!-- with line numbers: -->
+
+<<< @/snippets/snippet.cs{1,2,4-6 c#:line-numbers}
+```
+
+This is helpful if source language cannot be inferred from your file extension. Only alphanumeric extensions are inferred, so files like `main.c++` or `scss.code-snippets` need the language spelled out this way.
+
+Anything after the language inside the braces is passed along to the code block as extra attributes — for example, `<<< @/snippets/snippet.ts{ts twoslash}` enables twoslash processing when [`@shikijs/vitepress-twoslash`](https://shiki.style/packages/vitepress#twoslash) is configured. Note that attributes may not contain square brackets.
+
+## Code Groups
+
+You can group multiple code blocks like this:
+
+**Input**
+
+````md
+::: code-group
+
+```js [config.js]
+/**
+ * @type {import('vitepress').UserConfig}
+ */
+const config = {
+  // ...
+}
+
+export default config
+```
+
+```ts [config.ts]
+import type { UserConfig } from 'vitepress'
+
+const config: UserConfig = {
+  // ...
+}
+
+export default config
+```
+
+:::
+````
+
+**Output**
+
+::: code-group
+
+```js [config.js]
+/**
+ * @type {import('vitepress').UserConfig}
+ */
+const config = {
+  // ...
+}
+
+export default config
+```
+
+```ts [config.ts]
+import type { UserConfig } from 'vitepress'
+
+const config: UserConfig = {
+  // ...
+}
+
+export default config
+```
+
+:::
+
+You can also [import snippets](#import-code-snippets) in code groups:
+
+**Input**
+
+```md
+::: code-group
+
+<!-- filename is used as title by default -->
+
+<<< @/snippets/snippet.js
+
+<!-- you can provide a custom one too -->
+
+<<< @/snippets/snippet-with-region.js#snippet{1,2 ts:line-numbers} [snippet with region]
+
+:::
+```
+
+**Output**
+
+::: code-group
+
+<<< @/snippets/snippet.js
+
+<<< @/snippets/snippet-with-region.js#snippet{1,2 ts:line-numbers} [snippet with region]
+
+:::
+
+## Markdown File Inclusion
+
+You can include a markdown file in another markdown file, even nested.
+
+::: tip
+You can also prefix the markdown path with `@`, and it will act as the source root. By default, the source root is the VitePress project root, unless `srcDir` is configured.
+:::
+
+For example, you can include a relative markdown file using this:
+
+**Input**
+
+```md
+# Docs
+
+## Basics
+
+<!--@@include: ./parts/basics.md-->
+```
+
+**Part file** (`parts/basics.md`)
+
+```md
+Some getting started stuff.
+
+### Configuration
+
+Can be created using `.foorc.json`.
+```
+
+**Equivalent code**
+
+```md
+# Docs
+
+## Basics
+
+Some getting started stuff.
+
+### Configuration
+
+Can be created using `.foorc.json`.
+```
+
+It also supports selecting a line range:
+
+**Input**
+
+```md:line-numbers
+# Docs
+
+## Basics
+
+<!--@@include: ./parts/basics.md{3,}-->
+```
+
+**Part file** (`parts/basics.md`)
+
+```md:line-numbers
+Some getting started stuff.
+
+### Configuration
+
+Can be created using `.foorc.json`.
+```
+
+**Equivalent code**
+
+```md:line-numbers
+# Docs
+
+## Basics
+
+### Configuration
+
+Can be created using `.foorc.json`.
+```
+
+The format of the selected line range can be: `{3,}`, `{,10}`, `{1,10}`
+
+You can also use a [VS Code region](https://code.visualstudio.com/docs/editor/codebasics#_folding) to only include the corresponding part of the code file. You can provide a custom region name after a `#` following the filepath:
+
+**Input**
+
+```md:line-numbers
+# Docs
+
+## Basics
+
+<!--@@include: ./parts/basics.md#basic-usage{,2}-->
+<!--@@include: ./parts/basics.md#basic-usage{5,}-->
+```
+
+**Part file** (`parts/basics.md`)
+
+```md:line-numbers
+<!-- #region basic-usage -->
+## Usage Line 1
+
+## Usage Line 2
+
+## Usage Line 3
+<!-- #endregion basic-usage -->
+```
+
+**Equivalent code**
+
+```md:line-numbers
+# Docs
+
+## Basics
+
+## Usage Line 1
+
+## Usage Line 3
+```
+
+::: warning
+Including a missing file, region, heading anchor, or an out-of-range line selection throws a build error. Set `markdown.include.silent: true` to log a warning and skip the inclusion instead.
+:::
+
+Instead of VS Code regions, you can also use header anchors to include a specific section of the file. For example, if you have a header in your markdown file like this:
+
+```md
+## My Base Section
+
+Some content here.
+
+### My Sub Section
+
+Some more content here.
+
+## Another Section
+
+Content outside `My Base Section`.
+```
+
+You can include the `My Base Section` section like this:
+
+```md
+## My Extended Section
+<!--@@include: ./parts/basics.md#my-base-section-->
+```
+
+**Equivalent code**
+
+```md
+## My Extended Section
+
+Some content here.
+
+### My Sub Section
+
+Some more content here.
+```
+
+Here, `my-base-section` is the generated id of the heading element. In case it's not easily guessable, you can open the part file in your browser and click on the heading anchor (`#` symbol left to the heading when hovered) to see the id in the URL bar. Or use browser dev tools to inspect the element. Alternatively, you can also specify the id to the part file like this:
+
+```md
+## My Base Section {#custom-id}
+```
+
+and include it like this:
+
+```md
+<!--@@include: ./parts/basics.md#custom-id-->
+```
+
+Relative links and images inside included files resolve from the _included_ file's location, so a partial can link to its neighbors no matter which page includes it. Set `markdown.include.rebaseRelativeUrls: false` to leave them resolving relative to the including page instead.
+
+### Including Code Files {#including-code-files}
+
+Since inclusion happens before code blocks are parsed, the directive also works inside fences. Combined with a line range, this lets you show only part of a code file — an alternative to [importing snippets](#import-code-snippets) when regions are not an option:
+
+**Input**
+
+````md
+```js
+<!--@@include: @/snippets/snippet-with-region.js{2,4}-->
+```
+````
+
+**Output**
+
+```js
+<!--@include: @/snippets/snippet-with-region.js{2,4}-->
+```
+
+Note that the included lines are inserted verbatim (indentation is preserved), and content containing backticks needs a longer outer fence.
+
+## Math Equations
+
+This is currently opt-in. To enable it, you need to install `markdown-it-mathjax3` and set `markdown.math` to `true` in your config file:
+
+```sh
+npm add -D markdown-it-mathjax3@^4
+```
+
+```ts [.vitepress/config.ts]
+export default {
+  markdown: {
+    math: true
+  }
+}
+```
+
+**Input**
+
+```md
+When $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are
+$$ x = {-b \pm \sqrt{b^2-4ac} \over 2a} $$
+
+**Maxwell's equations:**
+
+| equation                                                                                                                                                                  | description                                                                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
+| $\nabla \cdot \vec{\mathbf{B}}  = 0$                                                                                                                                      | divergence of $\vec{\mathbf{B}}$ is zero                                               |
+| $\nabla \times \vec{\mathbf{E}}\, +\, \frac1c\, \frac{\partial\vec{\mathbf{B}}}{\partial t}  = \vec{\mathbf{0}}$                                                          | curl of $\vec{\mathbf{E}}$ is proportional to the rate of change of $\vec{\mathbf{B}}$ |
+| $\nabla \times \vec{\mathbf{B}} -\, \frac1c\, \frac{\partial\vec{\mathbf{E}}}{\partial t} = \frac{4\pi}{c}\vec{\mathbf{j}}    \nabla \cdot \vec{\mathbf{E}} = 4 \pi \rho$ | _wha?_                                                                                 |
+```
+
+**Output**
+
+When $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are
+$$ x = {-b \pm \sqrt{b^2-4ac} \over 2a} $$
+
+**Maxwell's equations:**
+
+| equation                                                                                                                                                                  | description                                                                            |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
+| $\nabla \cdot \vec{\mathbf{B}}  = 0$                                                                                                                                      | divergence of $\vec{\mathbf{B}}$ is zero                                               |
+| $\nabla \times \vec{\mathbf{E}}\, +\, \frac1c\, \frac{\partial\vec{\mathbf{B}}}{\partial t}  = \vec{\mathbf{0}}$                                                          | curl of $\vec{\mathbf{E}}$ is proportional to the rate of change of $\vec{\mathbf{B}}$ |
+| $\nabla \times \vec{\mathbf{B}} -\, \frac1c\, \frac{\partial\vec{\mathbf{E}}}{\partial t} = \frac{4\pi}{c}\vec{\mathbf{j}}    \nabla \cdot \vec{\mathbf{E}} = 4 \pi \rho$ | _wha?_                                                                                 |
+
+## Image Lazy Loading
+
+You can enable lazy loading for each image added via markdown by setting `lazyLoad` to `true` in your config file:
+
+```js
+export default {
+  markdown: {
+    image: {
+      // image lazy loading is disabled by default
+      lazyLoad: true
+    }
+  }
+}
+```
+
+## Advanced Configuration
+
+VitePress uses [markdown-it](https://github.com/markdown-it/markdown-it) as the Markdown renderer. A lot of the extensions above are implemented via custom plugins. You can further customize the `markdown-it` instance using the `markdown` option in `.vitepress/config.js`:
+
+```js
+import { defineConfig } from 'vitepress'
+import { headerLink } from '@mdit/plugin-anchor'
+import markdownItFoo from 'markdown-it-foo'
+
+export default defineConfig({
+  markdown: {
+    // options for @mdit/plugin-anchor
+    // https://mdit-plugins.github.io/anchor.html
+    anchor: {
+      permalink: headerLink()
+    },
+
+    // options for @mdit-vue/plugin-toc
+    // https://github.com/mdit-vue/mdit-vue/tree/main/packages/plugin-toc#options
+    toc: { level: [1, 2] },
+
+    config: (md) => {
+      // use more markdown-it plugins!
+      md.use(markdownItFoo)
+    }
+  }
+})
+```
+
+See full list of configurable properties in [Config Reference: App Config](../reference/site-config#markdown).

From efd3cf73d2f61b60673bce5fe42273d6b0bcedcd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:14 +0200
Subject: [PATCH 019/199] docs(de): add missing localized documentation

---
 docs/de/guide/migration-from-vitepress-0.md | 23 +++++++++++++++++++++
 1 file changed, 23 insertions(+)
 create mode 100644 docs/de/guide/migration-from-vitepress-0.md

diff --git a/docs/de/guide/migration-from-vitepress-0.md b/docs/de/guide/migration-from-vitepress-0.md
new file mode 100644
index 000000000..18268da48
--- /dev/null
+++ b/docs/de/guide/migration-from-vitepress-0.md
@@ -0,0 +1,23 @@
+# Migration von VitePress 0.x
+
+If you're coming from VitePress 0.x version, there're several breaking changes due to new features and enhancement. Please follow this guide to see how to migrate your app over to the latest VitePress.
+
+## App Config
+
+- The internationalization feature is not yet implemented.
+
+## Theme Config
+
+- `sidebar` option has changed its structure.
+  - `children` key is now named `items`.
+  - Top level item may not contain `link` at the moment. We're planning to bring it back.
+- `repo`, `repoLabel`, `docsDir`, `docsBranch`, `editLinks`, `editLinkText` are removed in favor of more flexible api.
+  - For adding GitHub link with icon to the nav, use [Social Links](../reference/default-theme-nav#navigation-links) feature.
+  - For adding "Edit this page" feature, use [Edit Link](../reference/default-theme-edit-link) feature.
+- `lastUpdated` option is now split into `config.lastUpdated` and `themeConfig.lastUpdated.text`.
+- `carbonAds.carbon` is changed to `carbonAds.code`.
+
+## Frontmatter-Konfiguration
+
+- `home: true` option has changed to `layout: home`. Also, many Homepage related settings have been modified to provide additional features. See [Home Page guide](../reference/default-theme-home-page) for details.
+- `footer` option is moved to [`themeConfig.footer`](../reference/default-theme-config#footer).

From aa5cea6151118a22ed570afb6ad15d32c412450f Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:16 +0200
Subject: [PATCH 020/199] docs(de): add missing localized documentation

---
 docs/de/guide/migration-from-vuepress.md | 30 ++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 docs/de/guide/migration-from-vuepress.md

diff --git a/docs/de/guide/migration-from-vuepress.md b/docs/de/guide/migration-from-vuepress.md
new file mode 100644
index 000000000..cfbc8f28a
--- /dev/null
+++ b/docs/de/guide/migration-from-vuepress.md
@@ -0,0 +1,30 @@
+# Migration von VuePress
+
+## Konfiguration
+
+### Seitenleiste
+
+The sidebar is no longer automatically populated from frontmatter. You can [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
+
+## Markdown
+
+### Bilder
+
+Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatically when you use static image.
+
+Hence, now you can render images without `img` tag.
+
+```diff
+- <img :src="$withBase('/foo.png')" alt="foo">
++ ![foo](/foo.png)
+```
+
+::: warning
+For dynamic images you still need `withBase` as shown in [Base URL guide](./asset-handling#base-url).
+:::
+
+Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex to find and replace it with `![$2]($1)` to replace all the images with `![](...)` syntax.
+
+---
+
+more to follow...

From d9419fffce21c6fabe5a39b07b2170225414f006 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:18 +0200
Subject: [PATCH 021/199] docs(de): add missing localized documentation

---
 docs/de/guide/mpa-mode.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 docs/de/guide/mpa-mode.md

diff --git a/docs/de/guide/mpa-mode.md b/docs/de/guide/mpa-mode.md
new file mode 100644
index 000000000..5e0fc24cb
--- /dev/null
+++ b/docs/de/guide/mpa-mode.md
@@ -0,0 +1,27 @@
+---
+description: MPA (Multi-Page Application) mode in VitePress for zero-JavaScript pages with better initial performance.
+---
+
+# MPA-Modus <Badge type="warning" text="experimental" />
+
+MPA (Multi-Page Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
+
+In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit tools.
+
+However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-load navigations in MPA mode will not feel as instant as in SPA mode.
+
+Also note that no-JS-by-default means you are essentially using Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To load client-side JavaScript, you will need to use the special `<script client>` tag:
+
+```html
+<script client>
+document.querySelector('h1').addEventListener('click', () => {
+  console.log('client side JavaScript!')
+})
+</script>
+
+# Hello
+```
+
+`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme components will be bundled together, while client script for a specific page will be split for that page only.
+
+Note that `<script client>` is **not evaluated as Vue component code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be used if your site requires absolutely minimal client-side interactivity.

From 0a7e8998ee535bac63fd001de149c531e16a6366 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:21 +0200
Subject: [PATCH 022/199] docs(de): add missing localized documentation

---
 docs/de/guide/routing.md | 451 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 451 insertions(+)
 create mode 100644 docs/de/guide/routing.md

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
new file mode 100644
index 000000000..845ef04ff
--- /dev/null
+++ b/docs/de/guide/routing.md
@@ -0,0 +1,451 @@
+---
+outline: deep
+description: Understand VitePress file-based routing, dynamic routes, clean URLs, and path rewrites.
+---
+
+# Routing
+
+## Dateibasierte Routen
+
+VitePress uses file-based routing, which means the generated HTML pages are mapped from the directory structure of the source Markdown files. For example, given the following directory structure:
+
+```
+.
+├─ guide
+│  ├─ getting-started.md
+│  └─ index.md
+├─ index.md
+└─ prologue.md
+```
+
+The generated HTML pages will be:
+
+```
+index.md                  -->  /index.html (accessible as /)
+prologue.md               -->  /prologue.html
+guide/index.md            -->  /guide/index.html (accessible as /guide/)
+guide/getting-started.md  -->  /guide/getting-started.html
+```
+
+The resulting HTML can be hosted on any web server that can serve static files.
+
+## Stamm- und Quellverzeichnis
+
+There are two important concepts in the file structure of a VitePress project: the **project root** and the **source directory**.
+
+### Projektverzeichnis
+
+Project root is where VitePress will try to look for the `.vitepress` special directory. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+
+When you run `vitepress dev` or `vitepress build` from the command line, VitePress will use the current working directory as project root. To specify a sub-directory as root, you will need to pass the relative path to the command. For example, if your VitePress project is located in `./docs`, you should run `vitepress dev docs`:
+
+```
+.
+├─ docs                    # project root
+│  ├─ .vitepress           # config dir
+│  ├─ getting-started.md
+│  └─ index.md
+└─ ...
+```
+
+```sh
+vitepress dev docs
+```
+
+This is going to result in the following source-to-HTML mapping:
+
+```
+docs/index.md            -->  /index.html (accessible as /)
+docs/getting-started.md  -->  /getting-started.html
+```
+
+### Quellverzeichnis
+
+Source directory is where your Markdown source files live. By default, it is the same as the project root. However, you can configure it via the [`srcDir`](../reference/site-config#srcdir) config option.
+
+The `srcDir` option is resolved relative to project root. For example, with `srcDir: 'src'`, your file structure will look like this:
+
+```
+.                          # project root
+├─ .vitepress              # config dir
+└─ src                     # source dir
+   ├─ getting-started.md
+   └─ index.md
+```
+
+The resulting source-to-HTML mapping:
+
+```
+src/index.md            -->  /index.html (accessible as /)
+src/getting-started.md  -->  /getting-started.html
+```
+
+## Zwischen Seiten verlinken
+
+You can use both absolute and relative paths when linking between pages. Note that although both `.md` and `.html` extensions will work, the best practice is to omit file extensions so that VitePress can generate the final URLs based on your config.
+
+```md
+<!-- Do -->
+[Getting Started](./getting-started)
+[Getting Started](../guide/getting-started)
+
+<!-- Don't -->
+[Getting Started](./getting-started.md)
+[Getting Started](./getting-started.html)
+```
+
+Learn more about linking to assets such images in [Asset Handling](./asset-handling).
+
+### Auf Nicht-VitePress-Seiten verlinken
+
+If you want to link to a page in your site that is not generated by VitePress, you'll either need to use the full URL (opens in a new tab) or explicitly specify the target:
+
+**Input**
+
+```md
+[Link to pure.html](/pure.html){target="_self"}
+```
+
+**Output**
+
+[Link to pure.html](/pure.html){target="_self"}
+
+::: tip Note
+
+In Markdown links, the `base` is automatically prepended to the URL. This means that if you want to link to a page outside of your base, you'd need something like `../../pure.html` in the link (resolved relative to the current page by the browser).
+
+Alternatively, you can directly use the anchor tag syntax:
+
+```md
+<a href="/pure.html" target="_self">Link to pure.html</a>
+```
+
+:::
+
+## Generating Clean URLs
+
+::: warning Server Support Required
+To serve clean URLs with VitePress, server-side support is required.
+:::
+
+By default, VitePress resolves inbound links to URLs ending with `.html`. However, some users may prefer "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
+
+Some servers or hosting platforms (for example Netlify, Vercel, GitHub Pages) provide the ability to map a URL like `/foo` to `/foo.html` if it exists, without a redirect:
+
+- Netlify and GitHub Pages support this by default.
+- Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
+
+If this feature is available to you, you can then also enable VitePress' own [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
+
+- Inbound links between pages are generated without the `.html` extension.
+- If current path ends with `.html`, the router will perform a client-side redirect to the extension-less path.
+
+If, however, you cannot configure your server with such support, you will have to manually resort to the following directory structure:
+
+```
+.
+├─ getting-started
+│  └─ index.md
+├─ installation
+│  └─ index.md
+└─ index.md
+```
+
+## Route Rewrites
+
+You can customize the mapping between the source directory structure and the generated pages. It's useful when you have a complex project structure. For example, let's say you have a monorepo with multiple packages, and would like to place documentations along with the source files like this:
+
+```
+.
+└─ packages
+   ├─ pkg-a
+   │  └─ src
+   │     ├─ foo.md
+   │     └─ index.md
+   └─ pkg-b
+      └─ src
+         ├─ bar.md
+         └─ index.md
+```
+
+And you want the VitePress pages to be generated like this:
+
+```
+packages/pkg-a/src/index.md  -->  /pkg-a/index.html
+packages/pkg-a/src/foo.md    -->  /pkg-a/foo.html
+packages/pkg-b/src/index.md  -->  /pkg-b/index.html
+packages/pkg-b/src/bar.md    -->  /pkg-b/bar.html
+```
+
+You can achieve this by configuring the [`rewrites`](../reference/site-config#rewrites) option like this:
+
+```ts [.vitepress/config.js]
+export default {
+  rewrites: {
+    'packages/pkg-a/src/index.md': 'pkg-a/index.md',
+    'packages/pkg-a/src/foo.md': 'pkg-a/foo.md',
+    'packages/pkg-b/src/index.md': 'pkg-b/index.md',
+    'packages/pkg-b/src/bar.md': 'pkg-b/bar.md'
+  }
+}
+```
+
+The `rewrites` option also supports dynamic route parameters. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
+
+```ts
+export default {
+  rewrites: {
+    'packages/:pkg/src/:slug*': ':pkg/:slug*'
+  }
+}
+```
+
+The rewrite paths are compiled using the `path-to-regexp` package - consult [its documentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
+
+`rewrites` can also be a function that receives the original path and returns the new path:
+
+```ts
+export default {
+  rewrites(id) {
+    return id.replace(/^packages\/([^/]+)\/src\//, '$1/')
+  }
+}
+```
+
+::: warning Relative Links with Rewrites
+
+When rewrites are enabled, **relative links should be based on the rewritten paths**. For example, in order to create a relative link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
+
+```md
+[Link to PKG B](../pkg-b/pkg-b-code)
+```
+:::
+
+## Dynamische Routen
+
+You can generate many pages using a single Markdown file and dynamic data. For example, you can create a `packages/[pkg].md` file that generates a corresponding page for every package in a project. Here, the `[pkg]` segment is a route **parameter** that differentiates each page from the others.
+
+### Pfad-Loader-Datei
+
+Since VitePress is a static site generator, the possible page paths must be determined at build time. Therefore, a dynamic route page **must** be accompanied by a **paths loader file**. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
+
+```
+.
+└─ packages
+   ├─ [pkg].md         # route template
+   └─ [pkg].paths.js   # route paths loader
+```
+
+The paths loader should provide an object with a `paths` method as its default export. The `paths` method should return an array of objects with a `params` property. Each of these objects will generate a corresponding page.
+
+Given the following `paths` array:
+
+```js
+// packages/[pkg].paths.js
+export default {
+  paths() {
+    return [
+      { params: { pkg: 'foo' }},
+      { params: { pkg: 'bar' }}
+    ]
+  }
+}
+```
+
+The generated HTML pages will be:
+
+```
+.
+└─ packages
+   ├─ foo.html
+   └─ bar.html
+```
+
+### Type-safe loader with `defineRoutes`
+
+If you are using TypeScript, you can wrap the loader with `defineRoutes` from `vitepress` to get type hints for route hooks such as `paths`, `watch`, and `transformPageData`:
+
+```ts
+// packages/[pkg].paths.ts
+import { defineRoutes } from 'vitepress'
+
+export default defineRoutes({
+  watch: ['../data/**/*.json'],
+  async paths() {
+    return [
+      { params: { pkg: 'foo' } },
+      { params: { pkg: 'bar' } }
+    ]
+  },
+  async transformPageData(pageData) {
+    pageData.title = `${pageData.title} · Packages`
+  }
+})
+```
+
+`defineRoutes` is optional, but recommended when authoring `.paths.ts` files.
+
+### Mehrere Parameter
+
+A dynamic route can contain multiple params:
+
+**File Structure**
+
+```
+.
+└─ packages
+   ├─ [pkg]-[version].md
+   └─ [pkg]-[version].paths.js
+```
+
+**Paths Loader**
+
+```js
+export default {
+  paths: () => [
+    { params: { pkg: 'foo', version: '1.0.0' }},
+    { params: { pkg: 'foo', version: '2.0.0' }},
+    { params: { pkg: 'bar', version: '1.0.0' }},
+    { params: { pkg: 'bar', version: '2.0.0' }}
+  ]
+}
+```
+
+**Output**
+
+```
+.
+└─ packages
+   ├─ foo-1.0.0.html
+   ├─ foo-2.0.0.html
+   ├─ bar-1.0.0.html
+   └─ bar-2.0.0.html
+```
+
+### Pfade dynamisch erzeugen
+
+The paths loader module is run in Node.js and only executed during build time. You can dynamically generate the paths array using any data, either local or remote.
+
+Generating paths from local files:
+
+```js
+import fs from 'node:fs'
+
+export default {
+  paths() {
+    return fs
+      .readdirSync('packages')
+      .map((pkg) => {
+        return { params: { pkg }}
+      })
+  }
+}
+```
+
+Generating paths from remote data:
+
+```js
+export default {
+  async paths() {
+    const pkgs = await (await fetch('https://my-api.com/packages')).json()
+
+    return pkgs.map((pkg) => {
+      return {
+        params: {
+          pkg: pkg.name,
+          version: pkg.version
+        }
+      }
+    })
+  }
+}
+```
+
+### Watching Template and Data Files
+
+When generating page content from templates or external data sources, you can use the watch option to automatically rebuild pages when those files change during development:
+
+```js
+// posts/[slug].paths.js
+import fs from 'node:fs'
+import { renderTemplate } from './templates/renderer.js'
+
+export default {
+  // Watch for changes to template files and data sources
+  watch: [
+    './templates/**/*.njk',     // Template files
+    '../data/**/*.json'         // Data files
+  ],
+
+  paths(watchedFiles) {
+    // watchedFiles will be an array of absolute paths of the matched files
+    // Read data files to generate routes
+    const dataFiles = watchedFiles.filter(file => file.endsWith('.json'))
+
+    return dataFiles.map(file => {
+      const data = JSON.parse(fs.readFileSync(file, 'utf-8'))
+
+      return {
+        params: { slug: data.slug },
+        content: renderTemplate(data)  // Use template to generate content
+      }
+    })
+  }
+}
+```
+
+The `watch` option works the same way as in [data loaders](./data-loading#data-from-local-files):
+
+- Accepts [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
+- Patterns are relative to the `.paths.js` file itself
+- Changes to watched files trigger page regeneration and HMR during development
+- In production builds, all pages are generated once regardless of watch configuration
+
+### Auf Parameter in Seiten zugreifen
+
+You can use the params to pass additional data to each page. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
+
+```md
+- package name: {{ $params.pkg }}
+- version: {{ $params.version }}
+```
+
+You can also access the current page's params via the [`useData`](../reference/runtime-api#usedata) runtime API. This is available in both Markdown files and Vue components:
+
+```vue
+<script setup>
+import { useData } from 'vitepress'
+
+// params is a Vue ref
+const { params } = useData()
+
+console.log(params.value)
+</script>
+```
+
+### Rohinhalt rendern
+
+Params passed to the page will be serialized in the client JavaScript payload, so you should avoid passing heavy data in params, for example raw Markdown or HTML content fetched from a remote CMS.
+
+Instead, you can pass such content to each page using the `content` property on each path object:
+
+```js
+export default {
+  async paths() {
+    const posts = await (await fetch('https://my-cms.com/blog-posts')).json()
+
+    return posts.map((post) => {
+      return {
+        params: { id: post.id },
+        content: post.content // raw Markdown or HTML
+      }
+    })
+  }
+}
+```
+
+Then, use the following special syntax to render the content as part of the Markdown file itself:
+
+```md
+<!-- @content -->
+```

From 51cfc7d314a399b3d69146ac313ab1e2e68757c3 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:23 +0200
Subject: [PATCH 023/199] docs(de): add missing localized documentation

---
 docs/de/guide/sitemap-generation.md | 62 +++++++++++++++++++++++++++++
 1 file changed, 62 insertions(+)
 create mode 100644 docs/de/guide/sitemap-generation.md

diff --git a/docs/de/guide/sitemap-generation.md b/docs/de/guide/sitemap-generation.md
new file mode 100644
index 000000000..5bef11fa7
--- /dev/null
+++ b/docs/de/guide/sitemap-generation.md
@@ -0,0 +1,62 @@
+---
+description: a sitemap.xml file for your VitePress site to improve search engine discoverability.
+---
+
+# Sitemap-Generierung
+
+VitePress comes with out-of-the-box support for generating a `sitemap.xml` file for your site. To enable it, add the following to your `.vitepress/config.js`:
+
+```ts
+export default {
+  sitemap: {
+    hostname: 'https://example.com'
+  }
+}
+```
+
+To have `<lastmod>` tags in your `sitemap.xml`, you can enable the [`lastUpdated`](../reference/default-theme-last-updated) option.
+
+## Optionen
+
+Sitemap support is powered by the [`sitemap`](https://www.npmjs.com/package/sitemap) module. You can pass any options supported by it to the `sitemap` option in your config file. These will be passed directly to the `SitemapStream` constructor. Refer to the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for more details. Example:
+
+```ts
+export default {
+  sitemap: {
+    hostname: 'https://example.com',
+    lastmodDateOnly: false
+  }
+}
+```
+
+If you're using `base` in your config, you should append it to the `hostname` option:
+
+```ts
+export default {
+  base: '/my-site/',
+  sitemap: {
+    hostname: 'https://example.com/my-site/'
+  }
+}
+```
+
+## `transformItems` Hook
+
+You can use the `sitemap.transformItems` hook to modify the sitemap items before they are written to the `sitemap.xml` file. This hook is called with an array of sitemap items and expects an array of sitemap items to be returned. Example:
+
+```ts
+export default {
+  sitemap: {
+    hostname: 'https://example.com',
+    transformItems: (items) => {
+      // add new items or modify/filter existing items
+      items.push({
+        url: '/extra-page',
+        changefreq: 'monthly',
+        priority: 0.8
+      })
+      return items
+    }
+  }
+}
+```

From de2f7fb1934b8b797a99133963e3eed3a9ca43ba Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:25 +0200
Subject: [PATCH 024/199] docs(de): add missing localized documentation

---
 docs/de/guide/ssr-compat.md | 135 ++++++++++++++++++++++++++++++++++++
 1 file changed, 135 insertions(+)
 create mode 100644 docs/de/guide/ssr-compat.md

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
new file mode 100644
index 000000000..879a56092
--- /dev/null
+++ b/docs/de/guide/ssr-compat.md
@@ -0,0 +1,135 @@
+---
+outline: deep
+description: your VitePress theme components and custom code are compatible with server-side rendering.
+---
+
+# SSR-Kompatibilität
+
+VitePress pre-renders the app in Node.js during the production build, using Vue's Server-Side Rendering (SSR) capabilities. This means all custom code in theme components are subject to SSR Compatibility.
+
+The [SSR section in official Vue docs](https://vuejs.org/guide/scaling-up/ssr.html) provides more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is to only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue components.
+
+## `<ClientOnly>`
+
+If you are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the built-in `<ClientOnly>` component:
+
+```md
+<ClientOnly>
+  <NonSSRFriendlyComponent />
+</ClientOnly>
+```
+
+## Libraries that Access Browser API on Import
+
+Some components or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need to dynamically import them.
+
+### Importing in Mounted Hook
+
+```vue
+<script setup>
+import { onMounted } from 'vue'
+
+onMounted(() => {
+  import('./lib-that-access-window-on-import').then((module) => {
+    // use code
+  })
+})
+</script>
+```
+
+### Conditional Import
+
+You can also conditionally import a dependency using the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
+
+```js
+if (!import.meta.env.SSR) {
+  import('./lib-that-access-window-on-import').then((module) => {
+    // use code
+  })
+}
+```
+
+Since [`Theme.enhanceApp`](./custom-theme#theme-interface) can be async, you can conditionally import and register Vue plugins that access browser APIs on import:
+
+```js [.vitepress/theme/index.js]
+/** @type {import('vitepress').Theme} */
+export default {
+  // ...
+  async enhanceApp({ app }) {
+    if (!import.meta.env.SSR) {
+      const plugin = await import('plugin-that-access-window-on-import')
+      app.use(plugin.default)
+    }
+  }
+}
+```
+
+If you're using TypeScript:
+```ts [.vitepress/theme/index.ts]
+import type { Theme } from 'vitepress'
+
+export default {
+  // ...
+  async enhanceApp({ app }) {
+    if (!import.meta.env.SSR) {
+      const plugin = await import('plugin-that-access-window-on-import')
+      app.use(plugin.default)
+    }
+  }
+} satisfies Theme
+```
+
+### `defineClientComponent`
+
+VitePress provides a convenience helper for importing Vue components that access browser APIs on import.
+
+```vue
+<script setup>
+import { defineClientComponent } from 'vitepress'
+
+const ClientComp = defineClientComponent(() => {
+  return import('component-that-access-window-on-import')
+})
+</script>
+
+<template>
+  <ClientComp />
+</template>
+```
+
+You can also pass props/children/slots to the target component:
+
+```vue
+<script setup>
+import { ref } from 'vue'
+import { defineClientComponent } from 'vitepress'
+
+const clientCompRef = ref(null)
+const ClientComp = defineClientComponent(
+  () => import('component-that-access-window-on-import'),
+
+  // args are passed to h() - https://vuejs.org/api/render-function.html#h
+  [
+    {
+      ref: clientCompRef
+    },
+    {
+      default: () => 'default slot',
+      foo: () => h('div', 'foo'),
+      bar: () => [h('span', 'one'), h('span', 'two')]
+    }
+  ],
+
+  // callback after the component is loaded, can be async
+  () => {
+    console.log(clientCompRef.value)
+  }
+)
+</script>
+
+<template>
+  <ClientComp />
+</template>
+```
+
+The target component will only be imported in the mounted hook of the wrapper component.

From 0800ece6179de0fc44290b5b1d1fc2c0fd4a50e3 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:28 +0200
Subject: [PATCH 025/199] docs(de): add missing localized documentation

---
 docs/de/guide/using-vue.md | 295 +++++++++++++++++++++++++++++++++++++
 1 file changed, 295 insertions(+)
 create mode 100644 docs/de/guide/using-vue.md

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
new file mode 100644
index 000000000..ef3f57085
--- /dev/null
+++ b/docs/de/guide/using-vue.md
@@ -0,0 +1,295 @@
+---
+description: Vue components and dynamic templating features directly inside Markdown files in VitePress.
+---
+
+# Vue in Markdown verwenden
+
+In VitePress, each Markdown file is compiled into HTML and then processed as a [Vue Single-File Component](https://vuejs.org/guide/scaling-up/sfc.html). This means you can use any Vue features inside the Markdown, including dynamic templating, using Vue components, or arbitrary in-page Vue component logic by adding a `<script>` tag.
+
+It's worth noting that VitePress leverages Vue's compiler to automatically detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. In short, you only pay for the dynamic parts on any given page.
+
+::: tip SSR Compatibility
+All Vue usage needs to be SSR-compatible. See [SSR Compatibility](./ssr-compat) for details and common workarounds.
+:::
+
+## Templating
+
+### Interpolation
+
+Each Markdown file is first compiled into HTML and then passed on as a Vue component to the Vite process pipeline. This means you can use Vue-style interpolation in text:
+
+**Input**
+
+```md
+{{ 1 + 1 }}
+```
+
+**Output**
+
+<div class="language-text"><pre><code>{{ 1 + 1 }}</code></pre></div>
+
+### Directives
+
+Directives also work (note that by design, raw HTML is also valid in Markdown):
+
+**Input**
+
+```html
+<span v-for="i in 3">{{ i }}</span>
+```
+
+**Output**
+
+<div class="language-text"><pre><code><span v-for="i in 3">{{ i }} </span></code></pre></div>
+
+## `<script>` and `<style>`
+
+Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<template>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
+
+```html
+---
+hello: world
+---
+
+<script setup>
+import { ref } from 'vue'
+
+const count = ref(0)
+</script>
+
+## Markdown Content
+
+The count is: {{ count }}
+
+<button :class="$style.button" @click="count++">Increment</button>
+
+<style module>
+.button {
+  color: red;
+  font-weight: bold;
+}
+</style>
+```
+
+::: warning Avoid `<style scoped>` in Markdown
+When used in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
+:::
+
+You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which provides access to current page's metadata:
+
+**Input**
+
+```html
+<script setup>
+import { useData } from 'vitepress'
+
+const { page } = useData()
+</script>
+
+<pre>{{ page }}</pre>
+```
+
+**Output**
+
+```json
+{
+  "path": "/using-vue.html",
+  "title": "Using Vue in Markdown",
+  "frontmatter": {},
+  ...
+}
+```
+
+## Using Components
+
+You can import and use Vue components directly in Markdown files.
+
+### Importing in Markdown
+
+If a component is only used by a few pages, it's recommended to explicitly import them where they are used. This allows them to be properly code-split and only loaded when the relevant pages are shown:
+
+```md
+<script setup>
+import CustomComponent from '../components/CustomComponent.vue'
+</script>
+
+# Docs
+
+This is a .md using a custom component
+
+<CustomComponent />
+
+## More docs
+
+...
+```
+
+### Registering Components Globally
+
+If a component is going to be used on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Default Theme](./extending-default-theme#registering-global-components) for an example.
+
+::: warning IMPORTANT
+Make sure a custom component's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
+:::
+
+### Using Components In Headers <ComponentInHeader />
+
+You can use Vue components in the headers, but note the difference between the following syntaxes:
+
+| Markdown                                                | Output HTML                               | Parsed Header |
+| ------------------------------------------------------- | ----------------------------------------- | ------------- |
+| <pre v-pre><code> # text &lt;Tag/&gt; </code></pre>     | `<h1>text <Tag/></h1>`                    | `text`        |
+| <pre v-pre><code> # text \`&lt;Tag/&gt;\` </code></pre> | `<h1>text <code>&lt;Tag/&gt;</code></h1>` | `text <Tag/>` |
+
+The HTML wrapped by `<code>` will be displayed as-is; only the HTML that is **not** wrapped will be parsed by Vue.
+
+::: tip
+The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and used for both the sidebar and document title).
+:::
+
+
+## Escaping
+
+You can escape Vue interpolations by wrapping them in a `<span>` or other elements with the `v-pre` directive:
+
+**Input**
+
+```md
+This <span v-pre>{{ will be displayed as-is }}</span>
+```
+
+**Output**
+
+<div class="escape-demo">
+  <p>This <span v-pre>{{ will be displayed as-is }}</span></p>
+</div>
+
+Alternatively, you can wrap the entire paragraph in a `v-pre` custom container:
+
+```md
+::: v-pre
+{{ This will be displayed as-is }}
+:::
+```
+
+**Output**
+
+<div class="escape-demo">
+
+::: v-pre
+{{ This will be displayed as-is }}
+:::
+
+</div>
+
+## Unescape in Code Blocks
+
+By default, all fenced code blocks are automatically wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
+
+**Input**
+
+````md
+```js-vue
+Hello {{ 1 + 1 }}
+```
+````
+
+**Output**
+
+```js-vue
+Hello {{ 1 + 1 }}
+```
+
+Note that this might prevent certain tokens from being syntax highlighted properly.
+
+## Using CSS Pre-processors
+
+VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need to install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
+
+```
+# .scss and .sass
+npm install -D sass
+
+# .less
+npm install -D less
+
+# .styl and .stylus
+npm install -D stylus
+```
+
+Then you can use the following in Markdown and theme components:
+
+```vue
+<style lang="sass">
+.title
+  font-size: 20px
+</style>
+```
+
+## Using Teleports
+
+VitePress currently has SSG support for teleports to body only. For other targets, you can wrap them inside the built-in `<ClientOnly>` component or inject the teleport markup into the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
+
+<ModalDemo />
+
+::: details
+<<< @/components/ModalDemo.vue
+:::
+
+```md
+<ClientOnly>
+  <Teleport to="#modal">
+    <div>
+      // ...
+    </div>
+  </Teleport>
+</ClientOnly>
+```
+
+<script setup>
+import ModalDemo from '../../components/ModalDemo.vue'
+import ComponentInHeader from '../../components/ComponentInHeader.vue'
+</script>
+
+<style>
+.escape-demo {
+  border: 1px solid var(--vp-c-border);
+  border-radius: 8px;
+  padding: 0 20px;
+}
+</style>
+
+
+## VS Code IntelliSense Support
+
+<!-- Based on https://github.com/vuejs/language-tools/pull/4321 -->
+
+Vue provides IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, to enable it for `.md` files, you need to make some adjustments to the configuration files.
+
+
+1. Add `.md` pattern to the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:
+
+::: code-group
+```json [tsconfig.json]
+{
+  "include": [
+    "docs/**/*.ts",
+    "docs/**/*.vue",
+    "docs/**/*.md",
+  ],
+  "vueCompilerOptions": {
+    "vitePressExtensions": [".md"],
+  },
+}
+```
+:::
+
+2. Add `markdown` to the `vue.server.includeLanguages` option in the VS Code setting:
+
+::: code-group
+```json [.vscode/settings.json]
+{
+  "vue.server.includeLanguages": ["vue", "markdown"]
+}
+```
+:::

From 6146b2ad0d6ccbbf3445387ad51a5ffa54cd2a7d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:30 +0200
Subject: [PATCH 026/199] docs(de): add missing localized documentation

---
 docs/de/guide/what-is-vitepress.md | 59 ++++++++++++++++++++++++++++++
 1 file changed, 59 insertions(+)
 create mode 100644 docs/de/guide/what-is-vitepress.md

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
new file mode 100644
index 000000000..662611786
--- /dev/null
+++ b/docs/de/guide/what-is-vitepress.md
@@ -0,0 +1,59 @@
+---
+description: a static site generator designed for building fast, content-centric websites powered by Vite and Vue.
+---
+
+# Was ist VitePress?
+
+VitePress is a [Static Site Generator](https://en.wikipedia.org/wiki/Static_site_generator) (SSG) designed for building fast, content-centric websites. In a nutshell, VitePress takes your source content written in [Markdown](https://en.wikipedia.org/wiki/Markdown), applies a theme to it, and generates static HTML pages that can be easily deployed anywhere.
+
+::: tip {no-title}
+Just want to try it out? Skip to the [Quickstart](./getting-started).
+:::
+
+## Anwendungsfälle
+
+- **Documentation**
+
+  VitePress ships with a default theme designed for technical documentation. It powers this page you are reading right now, along with the documentation for [Vite](https://vite.dev/), [Rollup](https://rollupjs.org/), [Pinia](https://pinia.vuejs.org/), [VueUse](https://vueuse.org/), [Vitest](https://vitest.dev/), [D3](https://d3js.org/), [UnoCSS](https://unocss.dev/), [Iconify](https://iconify.design/) and [many more](https://github.com/search?q=/%22vitepress%22:+/+path:/(?:package%7Cdeno)%5C.jsonc?$/+NOT+is:fork+NOT+is:archived&type=code).
+
+  The [official Vue.js documentation](https://vuejs.org/) is also based on VitePress, but uses a custom theme shared between multiple translations.
+
+- **Blogs, Portfolios, and Marketing Sites**
+
+  VitePress supports [fully customized themes](./custom-theme), with the developer experience of a standard Vite + Vue application. Being built on Vite also means you can directly leverage Vite plugins from its rich ecosystem. In addition, VitePress provides flexible APIs to [load data](./data-loading) (local or remote) and [dynamically generate routes](./routing#dynamic-routes). You can use it to build almost anything as long as the data can be determined at build time.
+
+  The official [Vue.js blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
+
+## Entwicklererfahrung
+
+VitePress aims to provide a great Developer Experience (DX) when working with Markdown content.
+
+- **[Vite-Powered:](https://vite.dev/)** instant server start, with edits always instantly reflected (<100ms) without page reload.
+
+- **[Built-in Markdown Extensions:](./markdown)** Frontmatter, tables, syntax highlighting... you name it. Specifically, VitePress provides many advanced features for working with code blocks, making it ideal for highly technical documentation.
+
+- **[Vue-Enhanced Markdown:](./using-vue)** each Markdown page is also a Vue [Single-File Component](https://vuejs.org/guide/scaling-up/sfc.html), thanks to Vue template's 100% syntax compatibility with HTML. You can embed interactivity in your static content using Vue templating features or imported Vue components.
+
+## Performance
+
+Unlike many traditional SSGs where each navigation results in a full page reload, a website generated by VitePress serves static HTML on the initial visit, but becomes a [Single Page Application](https://en.wikipedia.org/wiki/Single-page_application) (SPA) for subsequent navigation within the site. This model, in our opinion, provides an optimal balance for performance:
+
+- **Fast Initial Load**
+
+  The initial visit to any page will be served the static, pre-rendered HTML for fast loading speed and optimal SEO. The page then loads a JavaScript bundle that turns the page into a Vue SPA ("hydration"). Contrary to common assumptions of SPA hydration being slow, this process is actually extremely fast thanks to Vue 3's raw performance and compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
+
+- **Fast Post-load Navigation**
+
+  More importantly, the SPA model leads to better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched and dynamically updated. VitePress also automatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
+
+- **Interactivity Without Penalty**
+
+  To be able to hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue component and compiled into JavaScript. This may sound inefficient, but the Vue compiler is smart enough to separate the static and dynamic parts, minimizing both the hydration cost and payload size. For the initial page load, the static parts are automatically eliminated from the JavaScript payload and skipped during hydration.
+
+## What About VuePress?
+
+VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 and webpack. With Vue 3 and Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, and a more flexible customization API.
+
+The API difference between VitePress and VuePress 1 mostly lies in theming and customization. If you are using VuePress 1 with the default theme, it should be relatively straightforward to migrate to VitePress.
+
+Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided to focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, and VuePress 2 has been handed over to the VuePress community team for further development and maintenance.

From 1573d5ce1fd28706db19ad31b5eefb98c4f908fb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:43:32 +0200
Subject: [PATCH 027/199] docs(de): add missing localized documentation

---
 docs/de/reference/cli.md | 79 ++++++++++++++++++++++++++++++++++++++++
 1 file changed, 79 insertions(+)
 create mode 100644 docs/de/reference/cli.md

diff --git a/docs/de/reference/cli.md b/docs/de/reference/cli.md
new file mode 100644
index 000000000..2c221d3fe
--- /dev/null
+++ b/docs/de/reference/cli.md
@@ -0,0 +1,79 @@
+---
+description: of VitePress CLI commands including dev, build, preview, and init.
+---
+
+# Kommandozeilenschnittstelle
+
+## `vitepress dev`
+
+Start VitePress dev server using designated directory as root. Defaults to current directory. The `dev` command can also be omitted when running in current directory.
+
+### Verwendung
+
+```sh
+# start in current directory, omitting `dev`
+vitepress
+
+# start in sub directory
+vitepress dev [root]
+```
+
+### Optionen
+
+| Option          | Description                                                       |
+| --------------- | ----------------------------------------------------------------- |
+| `--open [path]` | Open browser on startup (`boolean \| string`)                     |
+| `--port <port>` | Specify port (`number`)                                           |
+| `--base <path>` | Public base path (default: `/`) (`string`)                        |
+| `--cors`        | Enable CORS                                                       |
+| `--strictPort`  | Exit if specified port is already in use (`boolean`)              |
+| `--force`       | Force the optimizer to ignore the cache and re-bundle (`boolean`) |
+
+## `vitepress build`
+
+Build the VitePress site for production.
+
+### Verwendung
+
+```sh
+vitepress build [root]
+```
+
+### Optionen
+
+| Option                         | Description                                                                                                         |
+| ------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
+| `--mpa` (experimental)         | Build in [MPA mode](../guide/mpa-mode) without client-side hydration (`boolean`)                                    |
+| `--base <path>`                | Public base path (default: `/`) (`string`)                                                                          |
+| `--assetsBase <url>`           | URL prefix the generated assets are served from, e.g. a CDN (`string`)                                              |
+| `--target <target>`            | Transpile target (default: `"modules"`) (`string`)                                                                  |
+| `--outDir <dir>`               | Output directory relative to **cwd** (default: `<root>/.vitepress/dist`) (`string`)                                 |
+| `--assetsInlineLimit <number>` | Static asset base64 inline threshold in bytes (default: `4096`) (`number`)                                          |
+
+## `vitepress preview`
+
+Locally preview the production build.
+
+### Verwendung
+
+```sh
+vitepress preview [root]
+```
+
+### Optionen
+
+| Option          | Description                                |
+| --------------- | ------------------------------------------ |
+| `--base <path>` | Public base path (default: `/`) (`string`) |
+| `--assetsBase <url>` | URL prefix the generated assets are served from, e.g. a CDN (`string`) |
+| `--port <port>` | Specify port (`number`)                    |
+
+## `vitepress init`
+
+Start the [Setup Wizard](../guide/getting-started#setup-wizard) in current directory.
+
+### Verwendung
+
+```sh
+vitepress init
+```

From 2df49bd107c1b16e8c73ddbee6274a7dc4b054cb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:00 +0200
Subject: [PATCH 028/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-badge.md | 85 ++++++++++++++++++++++++
 1 file changed, 85 insertions(+)
 create mode 100644 docs/de/reference/default-theme-badge.md

diff --git a/docs/de/reference/default-theme-badge.md b/docs/de/reference/default-theme-badge.md
new file mode 100644
index 000000000..d1468a43f
--- /dev/null
+++ b/docs/de/reference/default-theme-badge.md
@@ -0,0 +1,85 @@
+---
+description: Use the Badge component to add status labels to headers in VitePress documentation.
+---
+
+# Badge
+
+The badge lets you add status to your headers. For example, it could be useful to specify the section's type, or supported version.
+
+## Verwendung
+
+You may use the `Badge` component which is globally available.
+
+```html
+### Title <Badge type="info" text="default" />
+### Title <Badge type="tip" text="^1.9.0" />
+### Title <Badge type="warning" text="beta" />
+### Title <Badge type="danger" text="deprecated" />
+```
+
+Code above renders like:
+
+### Title <Badge type="info" text="default" />
+### Title <Badge type="tip" text="^1.9.0" />
+### Title <Badge type="warning" text="beta" />
+### Title <Badge type="danger" text="deprecated" />
+
+## Custom Children
+
+`<Badge>` accept `children`, which will be displayed in the badge.
+
+```html
+### Title <Badge type="info">custom element</Badge>
+```
+
+### Title <Badge type="info">custom element</Badge>
+
+## Anpassen Type Color
+
+You can customize the style of badges by overriding css variables. The following are the default values:
+
+```css
+:root {
+  --vp-badge-info-border: transparent;
+  --vp-badge-info-text: var(--vp-c-text-2);
+  --vp-badge-info-bg: var(--vp-c-default-soft);
+
+  --vp-badge-note-border: transparent;
+  --vp-badge-note-text: var(--vp-c-note-1);
+  --vp-badge-note-bg: var(--vp-c-note-soft);
+
+  --vp-badge-tip-border: transparent;
+  --vp-badge-tip-text: var(--vp-c-tip-1);
+  --vp-badge-tip-bg: var(--vp-c-tip-soft);
+
+  --vp-badge-important-border: transparent;
+  --vp-badge-important-text: var(--vp-c-important-1);
+  --vp-badge-important-bg: var(--vp-c-important-soft);
+
+  --vp-badge-caution-border: transparent;
+  --vp-badge-caution-text: var(--vp-c-caution-1);
+  --vp-badge-caution-bg: var(--vp-c-caution-soft);
+
+  --vp-badge-warning-border: transparent;
+  --vp-badge-warning-text: var(--vp-c-warning-1);
+  --vp-badge-warning-bg: var(--vp-c-warning-soft);
+
+  --vp-badge-danger-border: transparent;
+  --vp-badge-danger-text: var(--vp-c-danger-1);
+  --vp-badge-danger-bg: var(--vp-c-danger-soft);
+}
+```
+
+## `<Badge>`
+
+`<Badge>` component accepts following props:
+
+```ts
+interface Props {
+  // When `<slot>` is passed, this value gets ignored.
+  text?: string
+
+  // Defaults to `tip`. Matches markdown containers/alerts colors.
+  type?: 'info' | 'note' | 'tip' | 'important' | 'caution' | 'warning' | 'danger'
+}
+```

From 6f7b08a8f1eb50c80b5b4230ac4afdfa8fd36aee Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:03 +0200
Subject: [PATCH 029/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-carbon-ads.md | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 docs/de/reference/default-theme-carbon-ads.md

diff --git a/docs/de/reference/default-theme-carbon-ads.md b/docs/de/reference/default-theme-carbon-ads.md
new file mode 100644
index 000000000..e12f6b12e
--- /dev/null
+++ b/docs/de/reference/default-theme-carbon-ads.md
@@ -0,0 +1,29 @@
+---
+description: Integrate Carbon Ads into your VitePress site using the default theme's built-in support.
+---
+
+# Carbon Ads
+
+VitePress has built in native support for [Carbon Ads](https://www.carbonads.net/). By defining the Carbon Ads credentials in config, VitePress will display ads on the page.
+
+```js
+export default {
+  themeConfig: {
+    carbonAds: {
+      code: 'your-carbon-code',
+      placement: 'your-carbon-placement',
+      format: 'classic'
+    }
+  }
+}
+```
+
+These values are used to call carbon CDN script as shown below.
+
+The `format` option supports `classic`, `responsive`, and `cover`.
+
+```js
+`//cdn.carbonads.com/carbon.js?serve=${code}&placement=${placement}&format=${format}`
+```
+
+To learn more about Carbon Ads configuration, please visit [Carbon Ads website](https://www.carbonads.net/).

From 327990adcd496fa18aae7da054cd7af53d220bab Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:06 +0200
Subject: [PATCH 030/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-config.md | 552 ++++++++++++++++++++++
 1 file changed, 552 insertions(+)
 create mode 100644 docs/de/reference/default-theme-config.md

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
new file mode 100644
index 000000000..28e09d79b
--- /dev/null
+++ b/docs/de/reference/default-theme-config.md
@@ -0,0 +1,552 @@
+---
+description: Reference of all configuration options available for the VitePress default theme.
+---
+
+# Konfiguration des Standard-Themes
+
+Theme config lets you customize your theme. You can define theme config via the `themeConfig` option in the config file:
+
+```ts
+export default {
+  lang: 'en-US',
+  title: 'VitePress',
+  description: 'Vite & Vue powered static site generator.',
+
+  // Theme related configurations.
+  themeConfig: {
+    logo: '/logo.svg',
+    nav: [...],
+    sidebar: { ... }
+  }
+}
+```
+
+**The options documented on this page only apply to the default theme.** Different themes expect different theme config. When using a custom theme, the theme config object will be passed to the theme so the theme can define conditional behavior based on it.
+
+## i18nRouting
+
+- Type: `boolean | ((data: VitePressData<DefaultTheme.Config>, route: Route, targetLocale: string) => string)`
+
+Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. You can disable this behavior by setting `themeConfig.i18nRouting` to `false`.
+
+Set `themeConfig.i18nRouting` to a function to customize the locale link. The function receives the current VitePress data, the current route, and the target locale key, and returns the target link.
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    i18nRouting(data, route, targetLocale) {
+      const target = data.site.value.locales[targetLocale]
+      const targetLink =
+        target.link || (targetLocale === 'root' ? '/' : `/${targetLocale}/`)
+
+      return `${targetLink}${route.data.relativePath.replace(/\.md$/, '')}${route.hash}`
+    }
+  }
+})
+```
+
+## logo
+
+- Type: `ThemeableImage`
+
+Logo file to display in nav bar, right before the site title. Accepts a path string, or an object to set a different logo for light/dark mode.
+
+```ts
+export default {
+  themeConfig: {
+    logo: '/logo.svg'
+  }
+}
+```
+
+```ts
+type ThemeableImage =
+  | string
+  | { src: string; alt?: string }
+  | { light: string; dark: string; alt?: string }
+```
+
+## siteTitle
+
+- Type: `string | false`
+
+You can customize this item to replace the default site title (`title` in app config) in nav. When set to `false`, title in nav will be disabled. Useful when you have `logo` that already contains the site title text.
+
+```ts
+export default {
+  themeConfig: {
+    siteTitle: 'Hello World'
+  }
+}
+```
+
+## nav
+
+- Type: `NavItem`
+
+The configuration for the nav menu item. More details in [Default Theme: Nav](./default-theme-nav#navigation-links).
+
+```ts
+export default {
+  themeConfig: {
+    nav: [
+      { text: 'Guide', link: '/guide' },
+      {
+        text: 'Dropdown Menu',
+        items: [
+          { text: 'Item A', link: '/item-1' },
+          { text: 'Item B', link: '/item-2' },
+          { text: 'Item C', link: '/item-3' }
+        ]
+      }
+    ]
+  }
+}
+```
+
+```ts
+type NavItem = NavItemWithLink | NavItemWithChildren
+
+interface NavItemWithLink {
+  text: string
+  link: string | ((payload: PageData) => string)
+  activeMatch?: string
+  target?: string
+  rel?: string
+  noIcon?: boolean
+}
+
+interface NavItemChildren {
+  text?: string
+  items: NavItemWithLink[]
+}
+
+interface NavItemWithChildren {
+  text?: string
+  items: (NavItemChildren | NavItemWithLink)[]
+  activeMatch?: string
+}
+```
+
+## sidebar
+
+- Type: `Sidebar`
+
+The configuration for the sidebar menu item. More details in [Default Theme: Sidebar](./default-theme-sidebar).
+
+```ts
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Guide',
+        items: [
+          { text: 'Introduction', link: '/introduction' },
+          { text: 'Getting Started', link: '/getting-started' },
+          ...
+        ]
+      }
+    ]
+  }
+}
+```
+
+```ts
+export type Sidebar = SidebarItem[] | SidebarMulti
+
+export interface SidebarMulti {
+  [path: string]: SidebarItem[] | { items: SidebarItem[]; base: string }
+}
+
+export type SidebarItem = {
+  /**
+   * The text label of the item.
+   */
+  text?: string
+
+  /**
+   * The link of the item.
+   */
+  link?: string
+
+  /**
+   * The children of the item.
+   */
+  items?: SidebarItem[]
+
+  /**
+   * If not specified, group is not collapsible.
+   *
+   * If `true`, group is collapsible and collapsed by default
+   *
+   * If `false`, group is collapsible but expanded by default
+   */
+  collapsed?: boolean
+
+  /**
+   * Base path for the children items.
+   */
+  base?: string
+
+  /**
+   * Anpassen text that appears on the footer of previous/next page.
+   */
+  docFooterText?: string
+
+  rel?: string
+  target?: string
+}
+```
+
+## aside
+
+- Type: `boolean | 'left'`
+- Default: `true`
+- Can be overridden per page via [frontmatter](./frontmatter-config#aside)
+
+Setting this value to `false` prevents rendering of aside container.\
+Setting this value to `true` renders the aside to the right.\
+Setting this value to `left` renders the aside to the left.\
+In right-to-left layouts, both sides are mirrored.
+
+If you want to disable it for all viewports, you should use `outline: false` instead.
+
+## outline
+
+- Type: `Outline | Outline['level'] | false`
+- Level can be overridden per page via [frontmatter](./frontmatter-config#outline)
+
+Setting this value to `false` prevents rendering of outline container. Refer this interface for more details:
+
+```ts
+interface Outline {
+  /**
+   * The levels of headings to be displayed in the outline.
+   * Single number means only headings of that level will be displayed.
+   * If a tuple is passed, the first number is the minimum level and the second number is the maximum level.
+   * `'deep'` is same as `[2, 6]`, which means all headings from `<h2>` to `<h6>` will be displayed.
+   *
+   * @default 2
+   */
+  level?: number | [number, number] | 'deep'
+
+  /**
+   * The title to be displayed on the outline.
+   *
+   * @default 'On this page'
+   */
+  label?: string
+}
+```
+
+## socialLinks
+
+- Type: `SocialLink[]`
+
+You may define this option to show your social account links with icons in nav.
+
+```ts
+export default {
+  themeConfig: {
+    socialLinks: [
+      // You can add any icon from simple-icons (https://simpleicons.org/):
+      { icon: 'github', link: 'https://github.com/vuejs/vitepress' },
+      { icon: 'twitter', link: '...' },
+      { icon: 'discord', link: '/community', target: '_self' },
+      // You can use any other iconify collection installed in your project
+      // as `collection:name` (e.g. after `npm add -D @iconify-json/lucide`):
+      { icon: 'lucide:rss', link: '/feed.rss' },
+      // You can also add custom icons by passing SVG as string:
+      {
+        icon: {
+          svg: '<svg role="img" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg"><title>Dribbble</title><path d="M12...6.38z"/></svg>'
+        },
+        link: '...',
+        // You can include a custom label for accessibility too (optional but recommended):
+        ariaLabel: 'cool link'
+      }
+    ]
+  }
+}
+```
+
+```ts
+interface SocialLink {
+  icon: string | { svg: string }
+  link: string
+  ariaLabel?: string
+  target?: string
+}
+```
+
+## footer
+
+- Type: `Fußzeile`
+- Can be overridden per page via [frontmatter](./frontmatter-config#footer)
+
+Fußzeile configuration. You can add a message or copyright text on the footer, however, it will only be displayed when the page doesn't contain a sidebar. This is due to design concerns.
+
+```ts
+export default {
+  themeConfig: {
+    footer: {
+      message: 'Released under the MIT License.',
+      copyright: 'Copyright © 2019-present Evan You'
+    }
+  }
+}
+```
+
+```ts
+export interface Fußzeile {
+  message?: string
+  copyright?: string
+}
+```
+
+## editLink
+
+- Type: `EditLink`
+- Can be overridden per page via [frontmatter](./frontmatter-config#editlink)
+
+Bearbeitungslink lets you display a link to edit the page on Git management services such as GitHub, or GitLab. See [Default Theme: Bearbeitungslink](./default-theme-edit-link) for more details.
+
+```ts
+export default {
+  themeConfig: {
+    editLink: {
+      pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
+      text: 'Edit this page on GitHub'
+    }
+  }
+}
+```
+
+```ts
+export interface EditLink {
+  pattern: string
+  text?: string
+}
+```
+
+## lastUpdated
+
+- Type: `LastUpdatedOptions`
+
+Allows customization for the last updated text and date format.
+
+```ts
+export default {
+  themeConfig: {
+    lastUpdated: {
+      text: 'Updated at',
+      formatOptions: {
+        dateStyle: 'full',
+        timeStyle: 'medium'
+      }
+    }
+  }
+}
+```
+
+```ts
+export interface LastUpdatedOptions {
+  /**
+   * @default 'Last updated'
+   */
+  text?: string
+
+  /**
+   * @default
+   * { dateStyle: 'short',  timeStyle: 'short' }
+   */
+  formatOptions?: Intl.DateTimeFormatOptions & { forceLocale?: boolean }
+}
+```
+
+## algolia
+
+- Type: `AlgoliaSearch`
+
+An option to support searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Learn more in [Default Theme: Search](./default-theme-search)
+
+```ts
+export interface AlgoliaSearchOptions extends DocSearchProps {
+  locales?: Record<string, Partial<DocSearchProps>>
+}
+```
+
+View full options [here](https://github.com/vuejs/vitepress/blob/main/types/docsearch.d.ts).
+
+## carbonAds {#carbon-ads}
+
+- Type: `CarbonAdsOptions`
+
+An option to display [Carbon Ads](https://www.carbonads.net/).
+
+```ts
+export default {
+  themeConfig: {
+    carbonAds: {
+      code: 'your-carbon-code',
+      placement: 'your-carbon-placement'
+      format: 'classic'
+    }
+  }
+}
+```
+
+```ts
+export interface CarbonAdsOptions {
+  code: string
+  placement: string
+  format?: 'classic' | 'responsive' | 'cover'
+}
+```
+
+Learn more in [Default Theme: Carbon Ads](./default-theme-carbon-ads)
+
+## docFooter
+
+- Type: `DocFooter`
+
+Can be used to customize text appearing above previous and next links. Helpful if not writing docs in English. Also can be used to disable prev/next links globally. If you want to selectively enable/disable prev/next links, you can use [frontmatter](./default-theme-prev-next-links).
+
+```ts
+export default {
+  themeConfig: {
+    docFooter: {
+      prev: 'Pagina prior',
+      next: 'Proxima pagina'
+    }
+  }
+}
+```
+
+```ts
+export interface DocFooter {
+  prev?: string | false
+  next?: string | false
+}
+```
+
+## darkModeSwitchLabel
+
+- Type: `string`
+- Default: `Appearance`
+
+Can be used to customize the dark mode switch label. This label is only displayed in the mobile view.
+
+## lightModeSwitchTitle
+
+- Type: `string`
+- Default: `Switch to light theme`
+
+Can be used to customize the light mode switch title that appears on hovering.
+
+## darkModeSwitchTitle
+
+- Type: `string`
+- Default: `Switch to dark theme`
+
+Can be used to customize the dark mode switch title that appears on hovering.
+
+## sidebarMenuLabel
+
+- Type: `string`
+- Default: `Menu`
+
+Can be used to customize the sidebar menu label. This label is only displayed in the mobile view.
+
+## returnToTopLabel
+
+- Type: `string`
+- Default: `Return to top`
+
+Can be used to customize the label of the return to top button. This label is only displayed in the mobile view.
+
+## langMenuLabel
+
+- Type: `string`
+- Default: `Change language`
+
+Can be used to customize the aria-label of the language toggle button in navbar. This is only used if you're using [i18n](../guide/i18n).
+
+## navMenuLabel
+
+- Type: `string`
+- Default: `Main Navigation`
+
+Can be used to customize the accessible label of the main navigation landmarks (the navbar menu and the mobile menu).
+
+## mobileMenuLabel
+
+- Type: `string`
+- Default: `Menu`
+
+Can be used to customize the aria-label of the mobile menu (hamburger) button.
+
+## extraMenuLabel
+
+- Type: `string`
+- Default: `More options`
+
+Can be used to customize the aria-label of the `⋯` menu button in the navbar. That menu collects the nav items and controls that don't fit in the bar at the current viewport size.
+
+## skipToContentLabel
+
+- Type: `string`
+- Default: `Skip to content`
+
+Can be used to customize the label of the skip to content link. This link is shown when the user is navigating the site using a keyboard.
+
+## externalLinkIcon
+
+- Type: `boolean`
+- Default: `false`
+
+Whether to show an external link icon next to external links in markdown.
+
+## gradedContainers
+
+- Type: `boolean`
+- Default: `false`
+
+Whether to color [custom containers](../guide/markdown#custom-containers), [GitHub-flavored alerts](../guide/markdown#github-flavored-alerts), and badges on a graded severity scale — danger red, warning orange, caution yellow. By default, colors match GitHub's alerts, where caution shares danger's red and warning is yellow.
+
+## `useLayout` <Badge type="info" text="composable" />
+
+Returns layout-related data. The returned object has the following type:
+
+```ts
+interface {
+  isHome: ComputedRef<boolean>
+
+  sidebar: Readonly<ShallowRef<DefaultTheme.SidebarItem[]>>
+  sidebarGroups: ComputedRef<DefaultTheme.SidebarItem[]>
+  hasSidebar: ComputedRef<boolean>
+  isSidebarEnabled: ComputedRef<boolean>
+
+  hasAside: ComputedRef<boolean>
+  leftAside: ComputedRef<boolean>
+
+  headers: Readonly<ShallowRef<DefaultTheme.OutlineItem[]>>
+  hasLocalNav: ComputedRef<boolean>
+}
+```
+
+**Beispiel:**
+
+```vue
+<script setup>
+import { useLayout } from 'vitepress/theme'
+
+const { hasSidebar } = useLayout()
+</script>
+
+<template>
+  <div v-if="hasSidebar">Only show when sidebar exists</div>
+</template>
+```

From f21673dc96d18861ebb80c8979bff091462bc58e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:09 +0200
Subject: [PATCH 031/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-edit-link.md | 64 ++++++++++++++++++++
 1 file changed, 64 insertions(+)
 create mode 100644 docs/de/reference/default-theme-edit-link.md

diff --git a/docs/de/reference/default-theme-edit-link.md b/docs/de/reference/default-theme-edit-link.md
new file mode 100644
index 000000000..0c12bfc18
--- /dev/null
+++ b/docs/de/reference/default-theme-edit-link.md
@@ -0,0 +1,64 @@
+---
+description: Display an edit link on doc pages to let users suggest changes on GitHub or GitLab.
+---
+
+# Bearbeitungslink
+
+## Site-Level Config
+
+Bearbeitungslink lets you display a link to edit the page on Git management services such as GitHub, or GitLab. To enable it, add `themeConfig.editLink` options to your config.
+
+```js
+export default {
+  themeConfig: {
+    editLink: {
+      pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path'
+    }
+  }
+}
+```
+
+The `pattern` option defines the URL structure for the link, and `:path` is going to be replaced with the page path.
+
+You can also put a pure function that accepts [`PageData`](./runtime-api#usedata) as the argument and returns the URL string.
+
+```js
+export default {
+  themeConfig: {
+    editLink: {
+      pattern: ({ filePath }) => {
+        if (filePath.startsWith('packages/')) {
+          return `https://github.com/acme/monorepo/edit/main/${filePath}`
+        } else {
+          return `https://github.com/acme/monorepo/edit/main/docs/${filePath}`
+        }
+      }
+    }
+  }
+}
+```
+
+It should not have side-effects nor access anything outside of its scope since it will be serialized and executed in the browser.
+
+By default, this will add the link text "Edit this page" at the bottom of the doc page. You may customize this text by defining the `text` option.
+
+```js
+export default {
+  themeConfig: {
+    editLink: {
+      pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
+      text: 'Edit this page on GitHub'
+    }
+  }
+}
+```
+
+## Frontmatter Config
+
+This can be disabled per-page using the `editLink` option on frontmatter:
+
+```yaml
+---
+editLink: false
+---
+```

From dd161c4b84513d901216ba51c09f546b32537459 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:12 +0200
Subject: [PATCH 032/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-footer.md | 57 +++++++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 docs/de/reference/default-theme-footer.md

diff --git a/docs/de/reference/default-theme-footer.md b/docs/de/reference/default-theme-footer.md
new file mode 100644
index 000000000..7070e220e
--- /dev/null
+++ b/docs/de/reference/default-theme-footer.md
@@ -0,0 +1,57 @@
+---
+description: Configure the global footer displayed at the bottom of VitePress pages.
+---
+
+# Fußzeile
+
+VitePress will display global footer at the bottom of the page when `themeConfig.footer` is present.
+
+```ts
+export default {
+  themeConfig: {
+    footer: {
+      message: 'Released under the MIT License.',
+      copyright: 'Copyright © 2019-present Evan You'
+    }
+  }
+}
+```
+
+```ts
+export interface Fußzeile {
+  // The message shown right before copyright.
+  message?: string
+
+  // The actual copyright text.
+  copyright?: string
+}
+```
+
+The above configuration also supports HTML strings. So, for example, if you want to configure footer text to have some links, you can adjust the configuration as follows:
+
+```ts
+export default {
+  themeConfig: {
+    footer: {
+      message: 'Released under the <a href="https://github.com/vuejs/vitepress/blob/main/LICENSE">MIT License</a>.',
+      copyright: 'Copyright © 2019-present <a href="https://github.com/yyx990803">Evan You</a>'
+    }
+  }
+}
+```
+
+::: warning
+Only inline elements can be used in `message` and `copyright` as they are rendered inside a `<p>` element. If you want to add block elements, consider using [`layout-bottom`](../guide/extending-default-theme#layout-slots) slot instead.
+:::
+
+Note that footer will not be displayed when the [SideBar](./default-theme-sidebar) is visible.
+
+## Frontmatter Config
+
+This can be disabled per-page using the `footer` option on frontmatter:
+
+```yaml
+---
+footer: false
+---
+```

From e7c82563283d3a7ac98b6fc6b66d7ccd3951ad99 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:14 +0200
Subject: [PATCH 033/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-home-page.md | 199 +++++++++++++++++++
 1 file changed, 199 insertions(+)
 create mode 100644 docs/de/reference/default-theme-home-page.md

diff --git a/docs/de/reference/default-theme-home-page.md b/docs/de/reference/default-theme-home-page.md
new file mode 100644
index 000000000..a1a27b964
--- /dev/null
+++ b/docs/de/reference/default-theme-home-page.md
@@ -0,0 +1,199 @@
+---
+description: Configure the VitePress default theme home page layout with hero sections, features, and custom content.
+---
+
+# Startseite
+
+VitePress default theme provides a homepage layout, which you can also see used on [the homepage of this site](../). You may use it on any of your pages by specifying `layout: home` in the [frontmatter](./frontmatter-config).
+
+```yaml
+---
+layout: home
+---
+```
+
+However, this option alone wouldn't do much. You can add several different pre templated "sections" to the homepage by setting additional other options such as `hero` and `features`.
+
+## Hero Section
+
+The Hero section comes at the top of the homepage. Here's how you can configure the Hero section.
+
+```yaml
+---
+layout: home
+
+hero:
+  name: VitePress
+  text: Vite & Vue powered static site generator.
+  tagline: Lorem ipsum...
+  image:
+    src: /logo.png
+    alt: VitePress
+  actions:
+    - theme: brand
+      text: Get Started
+      link: /guide/what-is-vitepress
+    - theme: alt
+      text: View on GitHub
+      link: https://github.com/vuejs/vitepress
+---
+```
+
+```ts
+interface Hero {
+  // The string shown top of `text`. Comes with brand color
+  // and expected to be short, such as product name.
+  name?: string
+
+  // The main text for the hero section. This will be defined
+  // as `h1` tag.
+  text: string
+
+  // Tagline displayed below `text`.
+  tagline?: string
+
+  // The image is displayed next to the text and tagline area.
+  image?: ThemeableImage
+
+  // Action buttons to display in home hero section.
+  actions?: HeroAction[]
+}
+
+type ThemeableImage =
+  | string
+  | { src: string; alt?: string }
+  | { light: string; dark: string; alt?: string }
+
+interface HeroAction {
+  // Color theme of the button. Defaults to `brand`.
+  theme?: 'brand' | 'alt'
+
+  // Label of the button.
+  text: string
+
+  // Destination link of the button.
+  link: string
+
+  // Link target attribute.
+  target?: string
+
+  // Link rel attribute.
+  rel?: string
+}
+```
+
+### Customizing the name color
+
+VitePress uses the brand color (`--vp-c-brand-1`) for the `name`. However, you may customize this color by overriding `--vp-home-hero-name-color` variable.
+
+```css
+:root {
+  --vp-home-hero-name-color: blue;
+}
+```
+
+Also you may customize it further by combining `--vp-home-hero-name-background` to give the `name` gradient color.
+
+```css
+:root {
+  --vp-home-hero-name-color: transparent;
+  --vp-home-hero-name-background: -webkit-linear-gradient(120deg, #bd34fe, #41d1ff);
+}
+```
+
+## Features Section
+
+In Features section, you can list any number of features you would like to show right after the Hero section. To configure it, pass `features` option to the frontmatter.
+
+You can provide an icon for each feature, which can be an emoji or any type of image. When the configured icon is an image (svg, png, jpeg...), you must provide the icon with the proper width and height; you can also provide the description, its intrinsic size as well as its variants for dark and light theme when required.
+
+```yaml
+---
+layout: home
+
+features:
+  - icon: 🛠️
+    title: Simple and minimal, always
+    details: Lorem ipsum...
+  - icon:
+      src: /cool-feature-icon.svg
+    title: Another cool feature
+    details: Lorem ipsum...
+  - icon:
+      dark: /dark-feature-icon.svg
+      light: /light-feature-icon.svg
+    title: Another cool feature
+    details: Lorem ipsum...
+---
+```
+
+```ts
+interface Feature {
+  // Show icon on each feature box.
+  icon?: FeatureIcon
+
+  // Title of the feature.
+  title: string
+
+  // Details of the feature.
+  details: string
+
+  // Link when clicked on feature component. The link can
+  // be both internal or external.
+  //
+  // e.g. `guide/reference/default-theme-home-page` or `https://example.com`
+  link?: string
+
+  // Link text to be shown inside feature component. Best
+  // used with `link` option.
+  //
+  // e.g. `Learn more`, `Visit page`, etc.
+  linkText?: string
+
+  // Link rel attribute for the `link` option.
+  //
+  // e.g. `external`
+  rel?: string
+
+  // Link target attribute for the `link` option.
+  target?: string
+}
+
+type FeatureIcon =
+  | string
+  | { src: string; alt?: string; width?: string; height: string }
+  | {
+      light: string
+      dark: string
+      alt?: string
+      width?: string
+      height: string
+    }
+```
+
+## Markdown Content
+
+You can add additional content to your site's homepage just by adding Markdown below the `---` frontmatter divider.
+
+````md
+---
+layout: home
+
+hero:
+  name: VitePress
+  text: Vite & Vue powered static site generator.
+---
+
+## Getting Started
+
+You can get started using VitePress right away using `npx`!
+
+```sh
+npm init
+npx vitepress init
+```
+````
+
+::: info
+VitePress didn't always auto-style the extra content of the `layout: home` page. To revert to older behavior, you can add `markdownStyles: false` to the frontmatter.
+:::

From 7a5534aa84d1dd4597beea3a924fdb87f3a84ae4 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:17 +0200
Subject: [PATCH 034/199] docs(de): add German reference page

---
 .../reference/default-theme-last-updated.md   | 50 +++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 docs/de/reference/default-theme-last-updated.md

diff --git a/docs/de/reference/default-theme-last-updated.md b/docs/de/reference/default-theme-last-updated.md
new file mode 100644
index 000000000..e2d2d6356
--- /dev/null
+++ b/docs/de/reference/default-theme-last-updated.md
@@ -0,0 +1,50 @@
+---
+description: Show the last updated timestamp on VitePress pages based on Git commit history.
+---
+
+# Letzte Aktualisierung
+
+The update time of the last content will be displayed in the lower right corner of the page. To enable it, add `lastUpdated` options to your config.
+
+::: info
+VitePress displays the "last updated" time using the timestamp of the most recent Git commit for each file. To enable this, the Markdown file must be committed to Git.
+
+Internally, VitePress runs `git log -1 --pretty="%ai"` on each file to retrieve its timestamp. If all pages show the same update time, it's likely due to shallow cloning (common in CI environments), which limits Git history.
+
+To fix this in **GitHub Actions**, use the following in your workflow:
+
+```yaml{4}
+- name: Checkout
+  uses: actions/checkout@v5
+  with:
+    fetch-depth: 0
+```
+
+Other CI/CD platforms have similar settings.
+
+If such options aren't available, you can prepend the `docs:build` command in your `package.json` with a manual fetch:
+
+```json
+"docs:build": "git fetch --unshallow && vitepress build docs"
+```
+:::
+
+## Site-Level Config
+
+```js
+export default {
+  lastUpdated: true
+}
+```
+
+## Frontmatter Config
+
+This can be disabled per-page using the `lastUpdated` option on frontmatter:
+
+```yaml
+---
+lastUpdated: false
+---
+```
+
+Also refer [Default Theme: Letzte Aktualisierung](./default-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly disabled at site or page level.

From beedbc4c6975f33ac9c2fb306b51b240d675307c Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:19 +0200
Subject: [PATCH 035/199] docs(de): add German reference page

---
 docs/de/reference/default-theme-layout.md | 66 +++++++++++++++++++++++
 1 file changed, 66 insertions(+)
 create mode 100644 docs/de/reference/default-theme-layout.md

diff --git a/docs/de/reference/default-theme-layout.md b/docs/de/reference/default-theme-layout.md
new file mode 100644
index 000000000..d15e4330c
--- /dev/null
+++ b/docs/de/reference/default-theme-layout.md
@@ -0,0 +1,66 @@
+---
+description: Choose between doc, page, and home layouts in the VitePress default theme.
+---
+
+# Layout
+
+You may choose the page layout by setting `layout` option to the page [frontmatter](./frontmatter-config). There are 3 layout options, `doc`, `page`, and `home`. If nothing is specified, then the page is treated as `doc` page.
+
+```yaml
+---
+layout: doc
+---
+```
+
+## Doc Layout
+
+Option `doc` is the default layout and it styles the whole Markdown content into "documentation" look. It works by wrapping whole content within `vp-doc` css class, and applying styles to elements underneath it.
+
+Almost all generic elements such as `p`, or `h2` get special styling. Therefore, keep in mind that if you add any custom HTML inside a Markdown content, those will get affected by those styles as well.
+
+It also provides documentation specific features listed below. These features are only enabled in this layout.
+
+- Bearbeitungslink
+- Prev Next Link
+- Outline
+- [Carbon Ads](./default-theme-carbon-ads)
+
+## Page Layout
+
+Option `page` is treated as "blank page". The Markdown will still be parsed, and all of the [Markdown Extensions](../guide/markdown) work as same as `doc` layout, but it wouldn't get any default stylings.
+
+The page layout will let you style everything by you without VitePress theme affecting the markup. This is useful when you want to create your own custom page.
+
+Note that even in this layout, sidebar will still show up if the page has a matching sidebar config.
+
+## Home Layout
+
+Option `home` will generate templated "Homepage". In this layout, you can set extra options such as `hero` and `features` to customize the content further. Please visit [Default Theme: Startseite](./default-theme-home-page) for more details.
+
+## No Layout
+
+If you don't want any layout, you can pass `layout: false` through frontmatter. This option is helpful if you want a fully-customizable landing page (without any sidebar, navbar, or footer by default).
+
+## Custom Layout
+
+You can also use a custom layout:
+
+```md
+---
+layout: foo
+---
+```
+
+This will look for a component named `foo` registered in context. For example, you can register your component globally in `.vitepress/theme/index.ts`:
+
+```ts
+import DefaultTheme from 'vitepress/theme'
+import Foo from './Foo.vue'
+
+export default {
+  extends: DefaultTheme,
+  enhanceApp({ app }) {
+    app.component('foo', Foo)
+  }
+}
+```

From b1b3939fcdeb6fc0d8e0faf0f9aaac253d56677c Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:26 +0200
Subject: [PATCH 036/199] docs(de): add German reference pages

---
 docs/de/reference/default-theme-nav.md | 221 +++++++++++++++++++++++++
 1 file changed, 221 insertions(+)
 create mode 100644 docs/de/reference/default-theme-nav.md

diff --git a/docs/de/reference/default-theme-nav.md b/docs/de/reference/default-theme-nav.md
new file mode 100644
index 000000000..02caac415
--- /dev/null
+++ b/docs/de/reference/default-theme-nav.md
@@ -0,0 +1,221 @@
+---
+description: Configure the navigation bar in the VitePress default theme including site title, logo, and menu links.
+---
+
+# Nav
+
+The Nav is the navigation bar displayed on top of the page. It contains the site title, global menu links, etc.
+
+## Site Title and Logo
+
+By default, nav shows the title of the site referencing [`config.title`](./site-config#title) value. If you would like to change what's displayed on nav, you may define custom text in `themeConfig.siteTitle` option.
+
+```js
+export default {
+  themeConfig: {
+    siteTitle: 'My Custom Title'
+  }
+}
+```
+
+If you have a logo for your site, you can display it by passing in the path to the image. You should place the logo within `public` directly, and define the absolute path to it.
+
+```js
+export default {
+  themeConfig: {
+    logo: '/my-logo.svg'
+  }
+}
+```
+
+When adding a logo, it gets displayed along with the site title. If your logo is all you need and if you would like to hide the site title text, set `false` to the `siteTitle` option.
+
+```js
+export default {
+  themeConfig: {
+    logo: '/my-logo.svg',
+    siteTitle: false
+  }
+}
+```
+
+You can also pass an object as logo if you want to add `alt` attribute or customize it based on dark/light mode. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
+
+## Navigation Links
+
+You may define `themeConfig.nav` option to add links to your nav.
+
+```js
+export default {
+  themeConfig: {
+    nav: [
+      { text: 'Guide', link: '/guide' },
+      { text: 'Config', link: '/config' },
+      { text: 'Changelog', link: 'https://github.com/...' }
+    ]
+  }
+}
+```
+
+The `text` is the actual text displayed in nav, and the `link` is the link that will be navigated to when the text is clicked. For the link, set path to the actual file without `.md` prefix, and always start with `/`.
+
+The `link` can also be a function that accepts [`PageData`](./runtime-api#usedata) as the argument and returns the path.
+
+Nav links can also be dropdown menus. To do this, set `items` key on link option.
+
+```js
+export default {
+  themeConfig: {
+    nav: [
+      { text: 'Guide', link: '/guide' },
+      {
+        text: 'Dropdown Menu',
+        items: [
+          { text: 'Item A', link: '/item-1' },
+          { text: 'Item B', link: '/item-2' },
+          { text: 'Item C', link: '/item-3' }
+        ]
+      }
+    ]
+  }
+}
+```
+
+Note that dropdown menu title (`Dropdown Menu` in the above example) can not have `link` property since it becomes a button to open dropdown dialog.
+
+You may further add "sections" to the dropdown menu items as well by passing in more nested items.
+
+```js
+export default {
+  themeConfig: {
+    nav: [
+      { text: 'Guide', link: '/guide' },
+      {
+        text: 'Dropdown Menu',
+        items: [
+          {
+            // Title for the section.
+            text: 'Section A Title',
+            items: [
+              { text: 'Section A Item A', link: '...' },
+              { text: 'Section B Item B', link: '...' }
+            ]
+          }
+        ]
+      },
+      {
+        text: 'Dropdown Menu',
+        items: [
+          {
+            // You may also omit the title.
+            items: [
+              { text: 'Section A Item A', link: '...' },
+              { text: 'Section B Item B', link: '...' }
+            ]
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+### Customize link's "active" state
+
+Nav menu items will be highlighted when the current page is under the matching path. if you would like to customize the path to be matched, define `activeMatch` property and regex as a string value.
+
+```js
+export default {
+  themeConfig: {
+    nav: [
+      // This link gets active state when the user is
+      // on `/config/` path.
+      {
+        text: 'Guide',
+        link: '/guide',
+        activeMatch: '/config/'
+      }
+    ]
+  }
+}
+```
+
+::: warning
+`activeMatch` is expected to be a regex string, but you must define it as a string. We can't use actual RegExp object here because it isn't serializable during the build time.
+:::
+
+### Customize link's "target" and "rel" attributes
+
+By default, VitePress automatically determines `target` and `rel` attributes based on whether the link is an external link. But if you want, you can customize them too.
+
+```js
+export default {
+  themeConfig: {
+    nav: [
+      {
+        text: 'Merchandise',
+        link: 'https://www.thegithubshop.com/',
+        target: '_self',
+        rel: 'sponsored'
+      }
+    ]
+  }
+}
+```
+
+## Social Links
+
+Refer [`socialLinks`](./default-theme-config#sociallinks).
+
+## Custom Components
+
+You can include custom components in the navigation bar by using the `component` option. The `component` key should be the Vue component name, and must be registered globally using [Theme.enhanceApp](../guide/custom-theme#theme-interface).
+
+```js [.vitepress/config.js]
+export default {
+  themeConfig: {
+    nav: [
+      {
+        text: 'My Menu',
+        items: [
+          {
+            component: 'MyCustomComponent',
+            // Optional props to pass to the component
+            props: {
+              title: 'My Custom Component'
+            }
+          }
+        ]
+      },
+      {
+        component: 'AnotherCustomComponent'
+      }
+    ]
+  }
+}
+```
+
+Then, you need to register the component globally:
+
+```js [.vitepress/theme/index.js]
+import DefaultTheme from 'vitepress/theme'
+
+import MyCustomComponent from './components/MyCustomComponent.vue'
+import AnotherCustomComponent from './components/AnotherCustomComponent.vue'
+
+/** @type {import('vitepress').Theme} */
+export default {
+  extends: DefaultTheme,
+  enhanceApp({ app }) {
+    app.component('MyCustomComponent', MyCustomComponent)
+    app.component('AnotherCustomComponent', AnotherCustomComponent)
+  }
+}
+```
+
+Your component will be rendered in the navigation bar. VitePress will provide the following additional props to the component:
+
+- `screenMenu`: an optional boolean indicating whether the component is inside mobile navigation menu
+- `menu`: an optional boolean indicating whether the component is inside a dropdown panel — for example, the `⋯` menu that nav items collapse into when they don't fit the bar. In both these contexts, render a flat list instead of a floating flyout, which would end up nested inside the panel
+
+You can check an example in the e2e tests [here](https://github.com/vuejs/vitepress/tree/main/__tests__/e2e/.vitepress).

From a42dace7b16661e8ac840886f6594743455d6db0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:29 +0200
Subject: [PATCH 037/199] docs(de): add German reference pages

---
 .../default-theme-prev-next-links.md          | 47 +++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 docs/de/reference/default-theme-prev-next-links.md

diff --git a/docs/de/reference/default-theme-prev-next-links.md b/docs/de/reference/default-theme-prev-next-links.md
new file mode 100644
index 000000000..e57360b46
--- /dev/null
+++ b/docs/de/reference/default-theme-prev-next-links.md
@@ -0,0 +1,47 @@
+---
+description: Customize the previous and next page links displayed at the bottom of doc pages in VitePress.
+---
+
+# Prev Next Links
+
+You can customize the text and link for the previous and next pages (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
+
+## prev
+
+- Type: `string | false | { text?: string; link?: string }`
+
+- Details:
+
+  Specifies the text/link to show on the link to the previous page. If you don't set this in frontmatter, the text/link will be inferred from the sidebar config.
+
+- Beispiele:
+
+  - To customize only the text:
+
+    ```yaml
+    ---
+    prev: 'Get Started | Markdown'
+    ---
+    ```
+
+  - To customize both text and link:
+
+    ```yaml
+    ---
+    prev:
+      text: 'Markdown'
+      link: '/guide/markdown'
+    ---
+    ```
+
+  - To hide previous page:
+
+    ```yaml
+    ---
+    prev: false
+    ---
+    ```
+
+## next
+
+Same as `prev` but for the next page.

From 4e1be8907ab40d69091d13413710fe1e4e3cc8e9 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:31 +0200
Subject: [PATCH 038/199] docs(de): add German reference pages

---
 docs/de/reference/default-theme-search.md | 371 ++++++++++++++++++++++
 1 file changed, 371 insertions(+)
 create mode 100644 docs/de/reference/default-theme-search.md

diff --git a/docs/de/reference/default-theme-search.md b/docs/de/reference/default-theme-search.md
new file mode 100644
index 000000000..0c81da715
--- /dev/null
+++ b/docs/de/reference/default-theme-search.md
@@ -0,0 +1,371 @@
+---
+outline: deep
+description: Set up local or Algolia-powered search for your VitePress site.
+---
+
+# Suche
+
+## Local Suche
+
+VitePress supports fuzzy full-text search using an in-browser index thanks to [minisearch](https://github.com/lucaong/minisearch/). To enable this feature, simply set the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local'
+    }
+  }
+})
+```
+
+Beispiel result:
+
+![screenshot of the search modal](/search.png)
+
+Alternatively, you can use [Algolia DocSearch](#algolia-search) or some community plugins like:
+
+- <https://npmx.dev/package/vitepress-plugin-pagefind>
+- <https://npmx.dev/package/vitepress-plugin-typesense>
+- <https://npmx.dev/package/vitepress-plugin-cloudflare-ai-search>
+
+<!-- - <https://npmx.dev/package/@orama/plugin-vitepress> -- replace with zbsearch one when published -->
+
+### i18n {#local-search-i18n}
+
+You can use a config like this to use multilingual search:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local',
+      options: {
+        locales: {
+          zh: { // make this `root` if you want to translate the default locale
+            translations: {
+              button: {
+                buttonText: '搜索',
+                buttonAriaLabel: '搜索'
+              },
+              modal: {
+                displayDetails: '显示详细列表',
+                resetButtonTitle: '重置搜索',
+                backButtonTitle: '关闭搜索',
+                noResultsText: '没有结果',
+                footer: {
+                  selectText: '选择',
+                  selectKeyAriaLabel: '输入',
+                  navigateText: '导航',
+                  navigateUpKeyAriaLabel: '上箭头',
+                  navigateDownKeyAriaLabel: '下箭头',
+                  closeText: '关闭',
+                  closeKeyAriaLabel: 'esc'
+                }
+              }
+            }
+          }
+        }
+      }
+    }
+  }
+})
+```
+
+### miniSearch options
+
+You can configure MiniSearch like this:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local',
+      options: {
+        miniSearch: {
+          /**
+           * @type {Pick<import('minisearch').Optionen, 'extractField' | 'tokenize' | 'processTerm'>}
+           */
+          options: {
+            /* ... */
+          },
+          /**
+           * @type {import('minisearch').SearchOptions}
+           * @default
+           * { fuzzy: 0.2, prefix: true, boost: { title: 4, text: 2, titles: 1 } }
+           */
+          searchOptions: {
+            /* ... */
+          }
+        }
+      }
+    }
+  }
+})
+```
+
+Learn more in [MiniSearch docs](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
+
+::: info Document IDs
+Suche document IDs (as seen by `searchOptions.filter`, `boostDocument`, and in the raw index) are site-relative paths like `/guide/page.html#section` — they do not include [`base`](../reference/site-config#base). The theme resolves them against the base when rendering results.
+:::
+
+### Custom content renderer
+
+You can customize the function used to render the markdown content before indexing it:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local',
+      options: {
+        /**
+         * @param {string} src
+         * @param {import('vitepress').MarkdownEnv} env
+         * @param {import('markdown-it-async')} md
+         */
+        async _render(src, env, md) {
+          // return html string
+        }
+      }
+    }
+  }
+})
+```
+
+This function will be stripped from client-side site data, so you can use Node.js APIs in it.
+
+#### Beispiel: Excluding pages from search
+
+You can exclude pages from search by adding `search: false` to the frontmatter of the page. Alternatively:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local',
+      options: {
+        async _render(src, env, md) {
+          const html = await md.renderAsync(src, env)
+          if (env.frontmatter?.search === false) return ''
+          if (env.relativePath.startsWith('some/path')) return ''
+          return html
+        }
+      }
+    }
+  }
+})
+```
+
+::: warning Note
+In case a custom `_render` function is provided, you need to handle the `search: false` frontmatter yourself. Also, the `env` object won't be completely populated before `md.renderAsync` is called, so any checks on optional `env` properties like `frontmatter` should be done after that.
+:::
+
+#### Beispiel: Transforming content - adding anchors
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'local',
+      options: {
+        async _render(src, env, md) {
+          const html = await md.renderAsync(src, env)
+          if (env.frontmatter?.title)
+            return (await md.renderAsync(`# ${env.frontmatter.title}`)) + html
+          return html
+        }
+      }
+    }
+  }
+})
+```
+
+## Algolia Suche
+
+VitePress supports searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Refer to their getting started guide. In your `.vitepress/config.ts` you'll need to provide at least the following to make it work:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'algolia',
+      options: {
+        appId: '...',
+        apiKey: '...',
+        indexName: '...'
+      }
+    }
+  }
+})
+```
+
+### i18n {#algolia-search-i18n}
+
+You can use a config like this to use multilingual search:
+
+<details>
+<summary>View full example</summary>
+
+<<< @/snippets/algolia-i18n.ts
+
+</details>
+
+Refer [official Algolia docs](https://docsearch.algolia.com/docs/api#translations) to learn more about them. To quickly get started, you can also copy the translations used by this site from [our GitHub repo](https://github.com/search?q=repo:vuejs/vitepress+%22function+searchOptions%22&type=code).
+
+### Algolia Ask AI Support {#ask-ai}
+
+If you would like to include **Ask AI**, pass the `askAi` option (or any of the partial fields) inside `options`:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'algolia',
+      options: {
+        appId: '...',
+        apiKey: '...',
+        indexName: '...',
+        // askAi: "YOUR-ASSISTANT-ID"
+        // OR
+        askAi: {
+          // at minimum you must provide the assistantId you received from Algolia
+          assistantId: 'XXXYYY',
+          // optional overrides – if omitted, the top-level appId/apiKey/indexName values are reused
+          // apiKey: '...',
+          // appId: '...',
+          // indexName: '...'
+        }
+      }
+    }
+  }
+})
+```
+
+::: warning Note
+If you want to default to keyword search and do not want to use Ask AI, omit the `askAi` property.
+:::
+
+### Ask AI Side Panel {#ask-ai-side-panel}
+
+DocSearch v4.5+ supports an optional **Ask AI side panel**. When enabled, it can be opened with **Ctrl/Cmd+I** by default. The [Sidepanel API Reference](https://docsearch.algolia.com/docs/sidepanel/api-reference) contains the full list of options.
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'algolia',
+      options: {
+        appId: '...',
+        apiKey: '...',
+        indexName: '...',
+        askAi: {
+          assistantId: 'XXXYYY',
+          sidePanel: {
+            panel: {
+              variant: 'floating', // or 'inline'
+              side: 'right',
+              width: '360px',
+              expandedWidth: '580px',
+              suggestedQuestions: true
+            }
+          }
+        }
+      }
+    }
+  }
+})
+```
+
+Use `askAi.sidePanel.panel.suggestedQuestions` for side panel suggested
+questions. Algolia's standalone Ask AI examples also mention
+`askAi.suggestedQuestions`, but that top-level option is not enough for
+VitePress side panel mode and does not make the integrated keyword-search
+modal display suggested questions on first open.
+
+If you need to disable the keyboard shortcut, use the `keyboardShortcuts` option at the sidepanel root level:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'algolia',
+      options: {
+        appId: '...',
+        apiKey: '...',
+        indexName: '...',
+        askAi: {
+          assistantId: 'XXXYYY',
+          sidePanel: {
+            keyboardShortcuts: {
+              'Ctrl/Cmd+I': false
+            }
+          }
+        }
+      }
+    }
+  }
+})
+```
+
+#### Mode (auto / sidePanel / hybrid / modal) {#ask-ai-mode}
+
+You can optionally control how VitePress integrates keyword search and Ask AI:
+
+- `mode: 'auto'` (default): infer `hybrid` when keyword search is configured, otherwise `sidePanel` when Ask AI side panel is configured.
+- `mode: 'sidePanel'`: force side panel only (hides the keyword search button).
+- `mode: 'hybrid'`: enable keyword search modal + Ask AI side panel (requires keyword search configuration).
+- `mode: 'modal'`: keep Ask AI inside the DocSearch modal (even if you configured the side panel).
+
+#### Ask AI only (no keyword search) {#ask-ai-only}
+
+If you want to use **Ask AI side panel only**, you can omit top-level keyword search config and provide credentials under `askAi`:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    search: {
+      provider: 'algolia',
+      options: {
+        mode: 'sidePanel',
+        askAi: {
+          assistantId: 'XXXYYY',
+          appId: '...',
+          apiKey: '...',
+          indexName: '...',
+          sidePanel: true
+        }
+      }
+    }
+  }
+})
+```
+
+### Crawler Config
+
+Here is an example config based on what this site uses:
+
+<<< @/snippets/algolia-crawler.js

From e962979ba7f573d8da94abb28a45e6fb56107864 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:34 +0200
Subject: [PATCH 039/199] docs(de): add German reference pages

---
 docs/de/reference/default-theme-sidebar.md | 246 +++++++++++++++++++++
 1 file changed, 246 insertions(+)
 create mode 100644 docs/de/reference/default-theme-sidebar.md

diff --git a/docs/de/reference/default-theme-sidebar.md b/docs/de/reference/default-theme-sidebar.md
new file mode 100644
index 000000000..52bccc783
--- /dev/null
+++ b/docs/de/reference/default-theme-sidebar.md
@@ -0,0 +1,246 @@
+---
+description: Configure the sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
+---
+
+# Seitenleiste
+
+The sidebar is the main navigation block for your documentation. You can configure the sidebar menu in [`themeConfig.sidebar`](./default-theme-config#sidebar).
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Guide',
+        items: [
+          { text: 'Introduction', link: '/introduction' },
+          { text: 'Getting Started', link: '/getting-started' },
+          ...
+        ]
+      }
+    ]
+  }
+}
+```
+
+## The Basics
+
+The simplest form of the sidebar menu is passing in a single array of links. The first level item defines the "section" for the sidebar. It should contain `text`, which is the title of the section, and `items` which are the actual navigation links.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Section Title A',
+        items: [
+          { text: 'Item A', link: '/item-a' },
+          { text: 'Item B', link: '/item-b' },
+          ...
+        ]
+      },
+      {
+        text: 'Section Title B',
+        items: [
+          { text: 'Item C', link: '/item-c' },
+          { text: 'Item D', link: '/item-d' },
+          ...
+        ]
+      }
+    ]
+  }
+}
+```
+
+Each `link` should specify the path to the actual file starting with `/`. If you add trailing slash to the end of link, it will show `index.md` of the corresponding directory.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Guide',
+        items: [
+          // This shows `/guide/index.md` page.
+          { text: 'Introduction', link: '/guide/' }
+        ]
+      }
+    ]
+  }
+}
+```
+
+You may further nest the sidebar items up to 6 level deep counting up from the root level. Note that deeper than 6 level of nested items gets ignored and will not be displayed on the sidebar.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Level 1',
+        items: [
+          {
+            text: 'Level 2',
+            items: [
+              {
+                text: 'Level 3',
+                items: [
+                  ...
+                ]
+              }
+            ]
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+## Multiple Sidebars
+
+You may show different sidebar depending on the page path. For example, as shown on this site, you might want to create a separate sections of content in your documentation like "Guide" page and "Config" page.
+
+To do so, first organize your pages into directories for each desired section:
+
+```
+.
+├─ guide/
+│  ├─ index.md
+│  ├─ one.md
+│  └─ two.md
+└─ config/
+   ├─ index.md
+   ├─ three.md
+   └─ four.md
+```
+
+Then, update your configuration to define your sidebar for each section. This time, you should pass an object instead of an array.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: {
+      // This sidebar gets displayed when a user
+      // is on `guide` directory.
+      '/guide/': [
+        {
+          text: 'Guide',
+          items: [
+            { text: 'Index', link: '/guide/' },
+            { text: 'One', link: '/guide/one' },
+            { text: 'Two', link: '/guide/two' }
+          ]
+        }
+      ],
+
+      // This sidebar gets displayed when a user
+      // is on `config` directory.
+      '/config/': [
+        {
+          text: 'Config',
+          items: [
+            { text: 'Index', link: '/config/' },
+            { text: 'Three', link: '/config/three' },
+            { text: 'Four', link: '/config/four' }
+          ]
+        }
+      ]
+    }
+  }
+}
+```
+
+## Collapsible Seitenleiste Groups
+
+By adding `collapsed` option to the sidebar group, it shows a toggle button to hide/show each section.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Section Title A',
+        collapsed: false,
+        items: [...]
+      }
+    ]
+  }
+}
+```
+
+All sections are "open" by default. If you would like them to be "closed" on initial page load, set `collapsed` option to `true`.
+
+```js
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Section Title A',
+        collapsed: true,
+        items: [...]
+      }
+    ]
+  }
+}
+```
+
+## Path Prefix
+
+When your documentation structure has deep directories or groups located under the same subdirectory, you can use the `base` option to automatically prepend a path prefix to all nested `items` inside that group. This avoids repeating the same path prefix for every `link`.
+
+The `base` option is supported in both multiple sidebar configurations and nested sidebar groups.
+
+### In Multiple Sidebars
+
+You can define `base` at the root of a sidebar section configuration:
+
+```js {5}
+export default {
+  themeConfig: {
+    sidebar: {
+      '/guide/': {
+        base: '/guide/',
+        items: [
+          // This link is resolved to `/guide/introduction`
+          { text: 'Introduction', link: 'introduction' },
+          // This link is resolved to `/guide/getting-started`
+          { text: 'Getting Started', link: 'getting-started' }
+        ]
+      }
+    }
+  }
+}
+```
+
+### In Nested Groups
+
+You can also use `base` inside nested sidebar groups. It will apply to the immediate children of that group:
+
+```js{6,13}
+export default {
+  themeConfig: {
+    sidebar: [
+      {
+        text: 'Reference',
+        base: '/reference/',
+        items: [
+          // This link is resolved to `/reference/site-config`
+          { text: 'Site-Konfiguration', link: 'site-config' },
+          {
+            text: 'Standard-Theme',
+            // Nested base overrides the parent path prefix
+            base: '/reference/default-theme-',
+            items: [
+              // This link is resolved to `/reference/default-theme-nav`
+              { text: 'Nav', link: 'nav' },
+              // This link is resolved to `/reference/default-theme-sidebar`
+              { text: 'Seitenleiste', link: 'sidebar' }
+            ]
+          }
+        ]
+      }
+    ]
+  }
+}
+```

From fee1681a9fd2008f162fe5b40796cbfacf658008 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:36 +0200
Subject: [PATCH 040/199] docs(de): add German reference pages

---
 docs/de/reference/default-theme-team-page.md | 260 +++++++++++++++++++
 1 file changed, 260 insertions(+)
 create mode 100644 docs/de/reference/default-theme-team-page.md

diff --git a/docs/de/reference/default-theme-team-page.md b/docs/de/reference/default-theme-team-page.md
new file mode 100644
index 000000000..99bed39cd
--- /dev/null
+++ b/docs/de/reference/default-theme-team-page.md
@@ -0,0 +1,260 @@
+---
+description: Create team pages with member profiles using VitePress built-in team components.
+---
+
+<script setup>
+import { VPTeamMembers } from 'vitepress/theme'
+
+const members = [
+  {
+    avatar: 'https://github.com/yyx990803.png',
+    name: 'Evan You',
+    title: 'Creator',
+    links: [
+      { icon: 'github', link: 'https://github.com/yyx990803' },
+      { icon: 'twitter', link: 'https://twitter.com/youyuxi' }
+    ]
+  },
+  {
+    avatar: 'https://github.com/kiaking.png',
+    name: 'Kia King Ishii',
+    title: 'Developer',
+    links: [
+      { icon: 'github', link: 'https://github.com/kiaking' },
+      { icon: 'twitter', link: 'https://twitter.com/KiaKing85' }
+    ]
+  }
+]
+</script>
+
+# Teamseite
+
+If you would like to introduce your team, you may use Team components to construct the Teamseite. There are two ways of using these components. One is to embed it in doc page, and another is to create a full Teamseite.
+
+## Show team members in a page
+
+You may use `<VPTeamMembers>` component exposed from `vitepress/theme` to display a list of team members on any page.
+
+```html
+<script setup>
+import { VPTeamMembers } from 'vitepress/theme'
+
+const members = [
+  {
+    avatar: 'https://www.github.com/yyx990803.png',
+    name: 'Evan You',
+    title: 'Creator',
+    links: [
+      { icon: 'github', link: 'https://github.com/yyx990803' },
+      { icon: 'twitter', link: 'https://twitter.com/youyuxi' }
+    ]
+  },
+  ...
+]
+</script>
+
+# Our Team
+
+Say hello to our awesome team.
+
+<VPTeamMembers size="small" :members />
+```
+
+The above will display a team member in card looking element. It should display something similar to below.
+
+<VPTeamMembers size="small" :members />
+
+`<VPTeamMembers>` component comes in 2 different sizes, `small` and `medium`. While it boils down to your preference, usually `small` size should fit better when used in doc page. Also, you may add more properties to each member such as adding "description" or "sponsor" button. Learn more about it in [`<VPTeamMembers>`](#vpteammembers).
+
+Embedding team members in doc page is good for small size team where having dedicated full team page might be too much, or introducing partial members as a reference to documentation context.
+
+If you have large number of members, or simply would like to have more space to show team members, consider [creating a full team page](#create-a-full-team-page).
+
+## Create a full Teamseite
+
+Instead of adding team members to doc page, you may also create a full Teamseite, similar to how you can create a custom [Startseite](./default-theme-home-page).
+
+To create a team page, first, create a new md file. The file name doesn't matter, but here lets call it `team.md`. In this file, set frontmatter option `layout: page`, and then you may compose your page structure using `TeamPage` components.
+
+```html
+---
+layout: page
+---
+<script setup>
+import {
+  VPTeamPage,
+  VPTeamPageTitle,
+  VPTeamMembers
+} from 'vitepress/theme'
+
+const members = [
+  {
+    avatar: 'https://www.github.com/yyx990803.png',
+    name: 'Evan You',
+    title: 'Creator',
+    links: [
+      { icon: 'github', link: 'https://github.com/yyx990803' },
+      { icon: 'twitter', link: 'https://twitter.com/youyuxi' }
+    ]
+  },
+  ...
+]
+</script>
+
+<VPTeamPage>
+  <VPTeamPageTitle>
+    <template #title>
+      Our Team
+    </template>
+    <template #lead>
+      The development of VitePress is guided by an international
+      team, some of whom have chosen to be featured below.
+    </template>
+  </VPTeamPageTitle>
+  <VPTeamMembers :members />
+</VPTeamPage>
+```
+
+When creating a full team page, remember to wrap all components with `<VPTeamPage>` component. This component will ensure all nested team related components get the proper layout structure like spacings.
+
+`<VPPageTitle>` component adds the page title section. The title being `<h1>` heading. Use `#title` and `#lead` slot to document about your team.
+
+`<VPMembers>` works as same as when used in a doc page. It will display list of members.
+
+### Add sections to divide team members
+
+You may add "sections" to the team page. For example, you may have different types of team members such as Core Team Members and Community Partners. You can divide these members into sections to better explain the roles of each group.
+
+To do so, add `<VPTeamPageSection>` component to the `team.md` file we created previously.
+
+```html
+---
+layout: page
+---
+<script setup>
+import {
+  VPTeamPage,
+  VPTeamPageTitle,
+  VPTeamMembers,
+  VPTeamPageSection
+} from 'vitepress/theme'
+
+const coreMembers = [...]
+const partners = [...]
+</script>
+
+<VPTeamPage>
+  <VPTeamPageTitle>
+    <template #title>Our Team</template>
+    <template #lead>...</template>
+  </VPTeamPageTitle>
+  <VPTeamMembers size="medium" :members="coreMembers" />
+  <VPTeamPageSection>
+    <template #title>Partners</template>
+    <template #lead>...</template>
+    <template #members>
+      <VPTeamMembers size="small" :members="partners" />
+    </template>
+  </VPTeamPageSection>
+</VPTeamPage>
+```
+
+The `<VPTeamPageSection>` component can have `#title` and `#lead` slot similar to `VPTeamPageTitle` component, and also `#members` slot for displaying team members.
+
+Remember to put in `<VPTeamMembers>` component within `#members` slot.
+
+## `<VPTeamMembers>`
+
+The `<VPTeamMembers>` component displays a given list of members.
+
+```html
+<VPTeamMembers
+  size="medium"
+  :members="[
+    { avatar: '...', name: '...' },
+    { avatar: '...', name: '...' },
+    ...
+  ]"
+/>
+```
+
+```ts
+interface Props {
+  // Size of each members. Defaults to `medium`.
+  size?: 'small' | 'medium'
+
+  // List of members to display.
+  members: TeamMember[]
+}
+
+interface TeamMember {
+  // Avatar image for the member.
+  avatar: string
+
+  // Name of the member.
+  name: string
+
+  // Title to be shown below member's name.
+  // e.g. Developer, Software Engineer, etc.
+  title?: string
+
+  // Organization that the member belongs.
+  org?: string
+
+  // URL for the organization.
+  orgLink?: string
+
+  // Description for the member.
+  desc?: string
+
+  // Social links. e.g. GitHub, Twitter, etc. You may pass in
+  // the Social Links object here.
+  // See: https://vitepress.dev/reference/default-theme-config.html#sociallinks
+  links?: SocialLink[]
+
+  // URL for the sponsor page for the member.
+  sponsor?: string
+
+  // Text for the sponsor link. Defaults to 'Sponsor'.
+  actionText?: string
+}
+```
+
+## `<VPTeamPage>`
+
+The root component when creating a full team page. It only accepts a single slot. It will style all passed in team related components.
+
+## `<VPTeamPageTitle>`
+
+Adds "title" section of the page. Best use at the very beginning under `<VPTeamPage>`. It accepts `#title` and `#lead` slot.
+
+```html
+<VPTeamPage>
+  <VPTeamPageTitle>
+    <template #title>
+      Our Team
+    </template>
+    <template #lead>
+      The development of VitePress is guided by an international
+      team, some of whom have chosen to be featured below.
+    </template>
+  </VPTeamPageTitle>
+</VPTeamPage>
+```
+
+## `<VPTeamPageSection>`
+
+Creates a "section" with in team page. It accepts `#title`, `#lead`, and `#members` slot. You may add as many sections as you like inside `<VPTeamPage>`.
+
+```html
+<VPTeamPage>
+  ...
+  <VPTeamPageSection>
+    <template #title>Partners</template>
+    <template #lead>Lorem ipsum...</template>
+    <template #members>
+      <VPTeamMembers :members="data" />
+    </template>
+  </VPTeamPageSection>
+</VPTeamPage>
+```

From e401d162248aa7d581e2acfc1b2dfa4f68bc54fb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:39 +0200
Subject: [PATCH 041/199] docs(de): add German reference pages

---
 docs/de/reference/frontmatter-config.md | 253 ++++++++++++++++++++++++
 1 file changed, 253 insertions(+)
 create mode 100644 docs/de/reference/frontmatter-config.md

diff --git a/docs/de/reference/frontmatter-config.md b/docs/de/reference/frontmatter-config.md
new file mode 100644
index 000000000..1fb437338
--- /dev/null
+++ b/docs/de/reference/frontmatter-config.md
@@ -0,0 +1,253 @@
+---
+outline: deep
+description: Reference of all available frontmatter configuration options for VitePress Markdown pages.
+---
+
+# Frontmatter-Konfiguration
+
+Frontmatter enables page based configuration. In every markdown file, you can use frontmatter config to override site-level or theme-level config options. Also, there are config options which you can only define in frontmatter.
+
+Beispiel usage:
+
+```md
+---
+title: Docs with VitePress
+editLink: true
+---
+```
+
+You can access frontmatter data via the `$frontmatter` global in Vue expressions:
+
+```md
+{{ $frontmatter.title }}
+```
+
+## title
+
+- Type: `string`
+
+Title for the page. It's same as [config.title](./site-config#title), and it overrides the site-level config.
+
+```yaml
+---
+title: VitePress
+---
+```
+
+## titleTemplate
+
+- Type: `string | boolean`
+
+The suffix for the title. It's same as [config.titleTemplate](./site-config#titletemplate), and it overrides the site-level config.
+
+```yaml
+---
+title: VitePress
+titleTemplate: Vite & Vue powered static site generator
+---
+```
+
+## description
+
+- Type: `string`
+
+Description for the page. It's same as [config.description](./site-config#description), and it overrides the site-level config.
+
+```yaml
+---
+description: VitePress
+---
+```
+
+## head
+
+- Type: `HeadConfig[]`
+
+Specify extra head tags to be injected for the current page. They are [merged](./site-config#head) with the head tags injected by site-level config.
+
+```yaml
+---
+head:
+  - - meta
+    - name: description
+      content: hello
+  - - meta
+    - name: keywords
+      content: super duper SEO
+---
+```
+
+```ts
+type HeadConfig =
+  | [string, Record<string, string>]
+  | [string, Record<string, string>, string]
+```
+
+## dir
+
+- Type: `'ltr' | 'rtl' | 'auto'`
+
+Overrides the [text direction](./site-config#dir) of the site for the current page.
+
+```yaml
+---
+dir: rtl
+---
+```
+
+## Standard-Theme Only
+
+The following frontmatter options are only applicable when using the default theme.
+
+### layout
+
+- Type: `doc | home | page`
+- Default: `doc`
+
+Determines the layout of the page.
+
+- `doc` - It applies default documentation styles to the markdown content.
+- `home` - Special layout for "Startseite". You may add extra options such as `hero` and `features` to rapidly create beautiful landing page.
+- `page` - Behave similar to `doc` but it applies no styles to the content. Useful when you want to create a fully custom page.
+
+```yaml
+---
+layout: doc
+---
+```
+
+### hero <Badge type="info" text="home page only" />
+
+Defines contents of home hero section when `layout` is set to `home`. More details in [Standard-Theme: Startseite](./default-theme-home-page).
+
+### features <Badge type="info" text="home page only" />
+
+Defines items to display in features section when `layout` is set to `home`. More details in [Standard-Theme: Startseite](./default-theme-home-page).
+
+### navbar
+
+- Type: `boolean`
+- Default: `true`
+
+Whether to display [navbar](./default-theme-nav).
+
+```yaml
+---
+navbar: false
+---
+```
+
+### sidebar
+
+- Type: `boolean`
+- Default: `true`
+
+Whether to display [sidebar](./default-theme-sidebar).
+
+```yaml
+---
+sidebar: false
+---
+```
+
+### aside
+
+- Type: `boolean | 'left'`
+- Default: `true`
+
+Defines the location of the aside component in the `doc` layout.
+
+Setting this value to `false` prevents rendering of aside container.\
+Setting this value to `true` renders the aside to the right.\
+Setting this value to `'left'` renders the aside to the left.
+
+```yaml
+---
+aside: false
+---
+```
+
+### outline
+
+- Type: `number | [number, number] | 'deep' | false`
+- Default: `2`
+
+The levels of header in the outline to display for the page. It's same as [config.themeConfig.outline.level](./default-theme-config#outline), and it overrides the value set in site-level config.
+
+```yaml
+---
+outline: [2, 4]
+---
+```
+
+### lastUpdated
+
+- Type: `boolean | Date`
+- Default: `true`
+
+Whether to display [last updated](./default-theme-last-updated) text in the footer of the current page. If a datetime is specified, it will be displayed instead of the last git modified timestamp.
+
+```yaml
+---
+lastUpdated: false
+---
+```
+
+### editLink
+
+- Type: `boolean`
+- Default: `true`
+
+Whether to display [edit link](./default-theme-edit-link) in the footer of the current page.
+
+```yaml
+---
+editLink: false
+---
+```
+
+### footer
+
+- Type: `boolean`
+- Default: `true`
+
+Whether to display [footer](./default-theme-footer).
+
+```yaml
+---
+footer: false
+---
+```
+
+### pageClass
+
+- Type: `string`
+
+Add extra class name to a specific page.
+
+```yaml
+---
+pageClass: custom-page-class
+---
+```
+
+Then you can customize styles of this specific page in `.vitepress/theme/custom.css` file:
+
+```css
+.custom-page-class {
+  /* page-specific styles */
+}
+```
+
+### isHome
+
+- Type: `boolean`
+
+The default theme relies on checks like `frontmatter.layout === 'home'` to determine if the current page is the home page.\
+This is useful when you want to force show the home page elements in a custom layout.
+
+```yaml
+---
+isHome: true
+---
+```

From 21751f4e52a3bb797a18a230aaa47c31eaef2f57 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:41 +0200
Subject: [PATCH 042/199] docs(de): add German reference pages

---
 docs/de/reference/runtime-api.md | 223 +++++++++++++++++++++++++++++++
 1 file changed, 223 insertions(+)
 create mode 100644 docs/de/reference/runtime-api.md

diff --git a/docs/de/reference/runtime-api.md b/docs/de/reference/runtime-api.md
new file mode 100644
index 000000000..aaab22aac
--- /dev/null
+++ b/docs/de/reference/runtime-api.md
@@ -0,0 +1,223 @@
+---
+description: Reference of VitePress runtime APIs including composables, helper functions, and built-in components.
+---
+
+# Runtime API
+
+VitePress offers several built-in APIs to let you access app data. VitePress also comes with a few built-in components that can be used globally.
+
+The helper methods are globally importable from `vitepress` and are typically used in custom theme Vue components. However, they are also usable inside `.md` pages because markdown files are compiled into Vue [Single-File Components](https://vuejs.org/guide/scaling-up/sfc.html).
+
+Methods that start with `use*` indicates that it is a [Vue 3 Composition API](https://vuejs.org/guide/introduction.html#composition-api) function ("Composable") that can only be used inside `setup()` or `<script setup>`.
+
+## `useData` <Badge type="info" text="composable" />
+
+Returns page-specific data. The returned object has the following type:
+
+```ts
+interface VitePressData<T = any> {
+  /**
+   * Site-level metadata
+   */
+  site: Ref<SiteData<T>>
+  /**
+   * themeConfig from .vitepress/config.js
+   */
+  theme: Ref<T>
+  /**
+   * Page-level metadata
+   */
+  page: Ref<PageData>
+  /**
+   * Page frontmatter
+   */
+  frontmatter: Ref<PageData['frontmatter']>
+  /**
+   * Dynamic route params
+   */
+  params: Ref<PageData['params']>
+  title: Ref<string>
+  description: Ref<string>
+  lang: Ref<string>
+  isDark: Ref<boolean>
+  dir: Ref<'ltr' | 'rtl' | 'auto'>
+  localeIndex: Ref<string>
+  /**
+   * Current location hash
+   */
+  hash: Ref<string>
+}
+
+interface PageData {
+  title: string
+  titleTemplate?: string | boolean
+  description: string
+  relativePath: string
+  filePath: string
+  headers: Header[]
+  frontmatter: Record<string, any>
+  params?: Record<string, any>
+  isNotFound?: boolean
+  lastUpdated?: number
+}
+```
+
+`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) is enabled. Without that option, it remains an empty array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
+
+**Beispiel:**
+
+```vue
+<script setup>
+import { useData } from 'vitepress'
+
+const { theme } = useData()
+</script>
+
+<template>
+  <h1>{{ theme.footer.copyright }}</h1>
+</template>
+```
+
+## `useRoute` <Badge type="info" text="composable" />
+
+Returns the current route object with the following type:
+
+```ts
+interface Route {
+  path: string
+  data: PageData
+  component: Component | null
+}
+```
+
+## `useRouter` <Badge type="info" text="composable" />
+
+Returns the VitePress router instance so you can programmatically navigate to another page.
+
+```ts
+interface Router {
+  /**
+   * Current route.
+   */
+  route: Route
+  /**
+   * Navigate to a new URL.
+   */
+  go: (to?: string) => Promise<void>
+  /**
+   * Called before the route changes. Return `false` to cancel the navigation.
+   */
+  onBeforeRouteChange?: (to: string) => Awaitable<void | boolean>
+  /**
+   * Called before the page component is loaded (after the history state is updated).
+   * Return `false` to cancel the navigation.
+   */
+  onBeforePageLoad?: (to: string) => Awaitable<void | boolean>
+  /**
+   * Called after the page component is loaded (before the page component is updated).
+   */
+  onAfterPageLoad?: (to: string) => Awaitable<void>
+  /**
+   * Called after the route changes.
+   */
+  onAfterRouteChange?: (to: string) => Awaitable<void>
+}
+```
+
+Assign route-change handlers on the router instance:
+
+```ts
+const router = useRouter()
+
+router.onBeforeRouteChange = (to) => {
+  console.log('navigating to', to)
+}
+```
+
+For custom themes, the same router is available from [`enhanceApp`](../guide/custom-theme#theme-interface).
+
+## `useIcon` <Badge type="info" text="composable" />
+
+- **Type**: `(icon: MaybeRefOrGetter<string | { svg: string } | undefined>, el?: MaybeRefOrGetter<HTMLElement | null>) => ComputedRef<string | undefined>`
+
+Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Takes a fully qualified `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) and returns the class to put on the element — `vpi-<collection>-<name>`.
+
+During SSR the name is registered on the page's [`SSGContext`](./site-config#postrender), so the build emits the icon's styles into the generated stylesheet; in dev, icons are served on demand by the dev server from the locally installed collections. No icon is ever fetched from an external service.
+
+```vue
+<script setup>
+import { useIcon } from 'vitepress'
+import { useTemplateRef } from 'vue'
+
+const el = useTemplateRef('el')
+const iconClass = useIcon('lucide:rocket', el)
+</script>
+
+<template>
+  <span ref="el" :class="iconClass" />
+</template>
+```
+
+Pass the template ref of the element carrying the class so dev mode can resolve the icon on it. The element needs the mask rules the default theme ships; in a custom theme without them, dev applies an inline equivalent and the generated stylesheet includes zero-specificity base rules for production.
+
+When using the default theme, the `VPIcon` component from `vitepress/theme` wraps this composable (and also accepts a raw `{ svg }` string):
+
+```vue-html
+<VPIcon icon="lucide:rocket" />
+```
+
+Icons rendered only on the client (e.g. inside `<ClientOnly />`) can't be collected during the build — list them in [`icons.include`](./site-config#icons) instead.
+
+## `withBase` <Badge type="info" text="helper" />
+
+- **Type**: `(path: string) => string`
+
+Prepends the configured [`base`](./site-config#base) to a given URL path. Also see [Base URL](../guide/asset-handling#base-url).
+
+## `<Content />` <Badge type="info" text="component" />
+
+The `<Content />` component displays the rendered markdown contents. Useful [when creating your own theme](../guide/custom-theme).
+
+```vue
+<template>
+  <h1>Custom Layout!</h1>
+  <Content />
+</template>
+```
+
+## `<ClientOnly />` <Badge type="info" text="component" />
+
+The `<ClientOnly />` component renders its slot only at client side.
+
+Because VitePress applications are server-rendered in Node.js when generating static builds, any Vue usage must conform to the universal code requirements. In short, make sure to only access Browser / DOM APIs in beforeMount or mounted hooks.
+
+If you are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the `ClientOnly` component.
+
+```vue-html
+<ClientOnly>
+  <NonSSRFriendlyComponent />
+</ClientOnly>
+```
+
+- Related: [SSR Compatibility](../guide/ssr-compat)
+
+## `$frontmatter` <Badge type="info" text="template global" />
+
+Directly access current page's [frontmatter](../guide/frontmatter) data in Vue expressions.
+
+```md
+---
+title: Hello
+---
+
+# {{ $frontmatter.title }}
+```
+
+## `$params` <Badge type="info" text="template global" />
+
+Directly access current page's [dynamic route params](../guide/routing#dynamic-routes) in Vue expressions.
+
+```md
+- package name: {{ $params.pkg }}
+- version: {{ $params.version }}
+```

From bd72e1797835820e66eda28fd3e86afbbb097ede Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:44:44 +0200
Subject: [PATCH 043/199] docs(de): add German reference pages

---
 docs/de/reference/site-config.md | 862 +++++++++++++++++++++++++++++++
 1 file changed, 862 insertions(+)
 create mode 100644 docs/de/reference/site-config.md

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
new file mode 100644
index 000000000..6eddae7a2
--- /dev/null
+++ b/docs/de/reference/site-config.md
@@ -0,0 +1,862 @@
+---
+outline: deep
+description: Complete reference of VitePress site configuration options including app-level settings, theming, and build options.
+---
+
+# Site-Konfiguration
+
+Site config is where you can define the global settings of the site. App config options define settings that apply to every VitePress site, regardless of what theme it is using. For example, the base directory or the title of the site.
+
+## Übersicht
+
+### Config Resolution
+
+The config file is always resolved from `<root>/.vitepress/config.[ext]`, where `<root>` is your VitePress [project root](../guide/routing#root-and-source-directory), and `[ext]` is one of the supported file extensions. TypeScript is supported out of the box. Supported extensions include `.js`, `.ts`, `.mjs`, and `.mts`.
+
+It is recommended to use ES modules syntax in config files. The config file should default export an object:
+
+```ts
+export default {
+  // app level config options
+  lang: 'en-US',
+  title: 'VitePress',
+  description: 'Vite & Vue powered static site generator.',
+  ...
+}
+```
+
+::: details Dynamic (Async) Config
+
+If you need to dynamically generate the config, you can also default export a function. For example:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default async () => {
+  const posts = await (await fetch('https://my-cms.com/blog-posts')).json()
+
+  return defineConfig({
+    // app level config options
+    lang: 'en-US',
+    title: 'VitePress',
+    description: 'Vite & Vue powered static site generator.',
+
+    // theme level config options
+    themeConfig: {
+      sidebar: [
+        ...posts.map((post) => ({
+          text: post.name,
+          link: `/posts/${post.name}`
+        }))
+      ]
+    }
+  })
+}
+```
+
+You can also use top-level `await`. For example:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+const posts = await (await fetch('https://my-cms.com/blog-posts')).json()
+
+export default defineConfig({
+  // app level config options
+  lang: 'en-US',
+  title: 'VitePress',
+  description: 'Vite & Vue powered static site generator.',
+
+  // theme level config options
+  themeConfig: {
+    sidebar: [
+      ...posts.map((post) => ({
+        text: post.name,
+        link: `/posts/${post.name}`
+      }))
+    ]
+  }
+})
+```
+
+:::
+
+### Config Intellisense
+
+Using the `defineConfig` helper will provide TypeScript-powered intellisense for config options. Assuming your IDE supports it, this should work in both JavaScript and TypeScript.
+
+```js
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  // ...
+})
+```
+
+### Typed Theme Config
+
+By default, `defineConfig` helper expects the theme config type from default theme:
+
+```ts
+import { defineConfig } from 'vitepress'
+
+export default defineConfig({
+  themeConfig: {
+    // Type is `DefaultTheme.Config`
+  }
+})
+```
+
+If you use a custom theme and want type checks for the theme config, you'll need to use `defineConfigWithTheme` instead, and pass the config type for your custom theme via a generic argument:
+
+```ts
+import { defineConfigWithTheme } from 'vitepress'
+import type { ThemeConfig } from 'your-theme'
+
+export default defineConfigWithTheme<ThemeConfig>({
+  themeConfig: {
+    // Type is `ThemeConfig`
+  }
+})
+```
+
+### Vite, Vue & Markdown Config
+
+- **Vite**
+
+  You can configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. No need to create a separate Vite config file.
+
+- **Vue**
+
+  VitePress already includes the official Vue plugin for Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). You can configure its options using the [vue](#vue) option in your VitePress config.
+
+- **Markdown**
+
+  You can configure the underlying [Markdown-It](https://github.com/markdown-it/markdown-it) instance using the [markdown](#markdown) option in your VitePress config.
+
+### Page-Level Overrides
+
+Some settings can be overridden for specific pages using frontmatter.
+
+See [Frontmatter-Konfiguration](./frontmatter-config) for details.
+
+### Directory-Level Overrides
+
+Some config settings can be overridden at the directory level, allowing all pages in that directory to share settings without needing to repeat them in the frontmatter of each page.
+
+This is achieved by adding a file called `config.ts` (or `.js`, `.mjs`, or `.mts`) in the relevant directory. This file should export a config object using `export default`, similar to the main config file.
+
+Nested directories inherit settings from their parent directory, with configuration overrides being merged accordingly.
+
+The `defineAdditionalConfig` helper can be used to get TypeScript-powered intellisense for the available options, though as with `defineConfig` its use is optional.
+
+For example, for a site with multiple languages we might want a different `description` for each language. We could add `es/config.ts` with the following content:
+
+```ts
+import { defineAdditionalConfig } from 'vitepress'
+
+export default defineAdditionalConfig({
+  description: 'Generador de Sitios Estáticos desarrollado con Vite y Vue.'
+})
+```
+
+This `description` would then be used for all pages in the `es` directory.
+
+Alternatively, when using the built-in i18n features, the settings for a locale directory can be overridden via the `locales` setting in the main configuration file. See [Internationalization](../guide/i18n) for details.
+
+## Site Metadata
+
+### title
+
+- Type: `string`
+- Default: `VitePress`
+- Can be overridden per page via [frontmatter](./frontmatter-config#title) or at the [directory level](#directory-level-overrides)
+
+Title for the site. When using the default theme, this will be displayed in the nav bar.
+
+It will also be used as the default suffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. For example with the following config and page content:
+
+```ts
+export default {
+  title: 'My Awesome Site'
+}
+```
+
+```md
+# Hello
+```
+
+The title of the page will be `Hello | My Awesome Site`.
+
+### titleTemplate
+
+- Type: `string | boolean`
+- Can be overridden per page via [frontmatter](./frontmatter-config#titletemplate) or at the [directory level](#directory-level-overrides)
+
+Allows customizing each page's title suffix or the entire title. For example:
+
+```ts
+export default {
+  title: 'My Awesome Site',
+  titleTemplate: 'Custom Suffix'
+}
+```
+
+```md
+# Hello
+```
+
+The title of the page will be `Hello | Custom Suffix`.
+
+To completely customize how the title should be rendered, you can use the `:title` symbol in `titleTemplate`:
+
+```ts
+export default {
+  titleTemplate: ':title - Custom Suffix'
+}
+```
+
+Here `:title` will be replaced with the text inferred from the page's first `<h1>` header. The title of the previous example page will be `Hello - Custom Suffix`.
+
+The option can be set to `false` to disable title suffixes.
+
+### description
+
+- Type: `string`
+- Default: `A VitePress site`
+- Can be overridden per page via [frontmatter](./frontmatter-config#description) or at the [directory level](#directory-level-overrides)
+
+Description for the site. This will render as a `<meta>` tag in the page HTML.
+
+```ts
+export default {
+  description: 'A VitePress site'
+}
+```
+
+### head
+
+- Type: `HeadConfig[]`
+- Default: `[]`
+- Can be appended per page via [frontmatter](./frontmatter-config#head) or at the [directory level](#directory-level-overrides)
+
+Additional elements to render in the `<head>` tag in the page HTML. The user-added tags are rendered before the closing `head` tag, after VitePress tags.
+
+```ts
+type HeadConfig =
+  | [string, Record<string, string>]
+  | [string, Record<string, string>, string]
+```
+
+Head entries from the site config, [locale config](../guide/i18n), [directory-level config](#directory-level-overrides), [frontmatter](./frontmatter-config#head) and [`transformHead`](#transformhead) are merged in that order. A later entry replaces an earlier one with the same key instead of being appended:
+
+- Any element with an `id` attribute is keyed by its `id`.
+- A `meta` element without an `id` is keyed by its first attribute other than `content` (e.g. `name`, `property`, `http-equiv`) and that attribute's value.
+
+Other elements are never deduplicated. To render multiple `meta` tags that would share a key, like several `<meta name="author">`, give each of them a unique `id`.
+
+#### Beispiel: Adding a favicon
+
+```ts
+export default {
+  head: [['link', { rel: 'icon', href: '/favicon.ico' }]]
+} // put favicon.ico in public directory, if base is set, use /base/favicon.ico
+
+/* Would render:
+  <link rel="icon" href="/favicon.ico">
+*/
+```
+
+#### Beispiel: Adding Google Fonts
+
+```ts
+export default {
+  head: [
+    [
+      'link',
+      { rel: 'preconnect', href: 'https://fonts.googleapis.com' }
+    ],
+    [
+      'link',
+      { rel: 'preconnect', href: 'https://fonts.gstatic.com', crossorigin: '' }
+    ],
+    [
+      'link',
+      { href: 'https://fonts.googleapis.com/css2?family=Roboto&display=swap', rel: 'stylesheet' }
+    ]
+  ]
+}
+
+/* Would render:
+  <link rel="preconnect" href="https://fonts.googleapis.com">
+  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
+  <link href="https://fonts.googleapis.com/css2?family=Roboto&display=swap" rel="stylesheet">
+*/
+```
+
+#### Beispiel: Registering a service worker
+
+```ts
+export default {
+  head: [
+    [
+      'script',
+      { id: 'register-sw' },
+      `;(() => {
+        if ('serviceWorker' in navigator) {
+          navigator.serviceWorker.register('/sw.js')
+        }
+      })()`
+    ]
+  ]
+}
+
+/* Would render:
+  <script id="register-sw">
+    ;(() => {
+      if ('serviceWorker' in navigator) {
+        navigator.serviceWorker.register('/sw.js')
+      }
+    })()
+  </script>
+*/
+```
+
+#### Beispiel: Using Google Analytics
+
+```ts
+export default {
+  head: [
+    [
+      'script',
+      { async: '', src: 'https://www.googletagmanager.com/gtag/js?id=TAG_ID' }
+    ],
+    [
+      'script',
+      {},
+      `window.dataLayer = window.dataLayer || [];
+      function gtag(){dataLayer.push(arguments);}
+      gtag('js', new Date());
+      gtag('config', 'TAG_ID');`
+    ]
+  ]
+}
+
+/* Would render:
+  <script async src="https://www.googletagmanager.com/gtag/js?id=TAG_ID"></script>
+  <script>
+    window.dataLayer = window.dataLayer || [];
+    function gtag(){dataLayer.push(arguments);}
+    gtag('js', new Date());
+    gtag('config', 'TAG_ID');
+  </script>
+*/
+```
+
+### lang
+
+- Type: `string`
+- Default: `en-US`
+- Can be overridden at the [directory level](#directory-level-overrides)
+
+The lang attribute for the site. This will render as a `<html lang="en-US">` tag in the page HTML.
+
+```ts
+export default {
+  lang: 'en-US'
+}
+```
+
+### dir
+
+- Type: `'ltr' | 'rtl' | 'auto'`
+- Default: `ltr`
+- Can be overridden at the [directory level](#directory-level-overrides)
+
+The text direction of the site. This will render as a `<html dir="rtl">` tag in the page HTML, and the default theme mirrors its layout for right-to-left languages. It can also be overridden per page via [frontmatter](./frontmatter-config#dir). See [RTL Support](../guide/i18n#rtl-support).
+
+```ts
+export default {
+  dir: 'rtl'
+}
+```
+
+### base
+
+- Type: `string`
+- Default: `/`
+
+The base URL the site will be deployed at. You will need to set this if you plan to deploy your site under a sub path, for example, GitHub pages. If you plan to deploy your site to `https://foo.github.io/bar/`, then you should set base to `'/bar/'`. It should always start and end with a slash.
+
+The one exception is `'./'`, which produces a [relocatable build](../guide/deploy#relocatable-builds-relative-base): pages reference everything relative to their own location, so the same output works from any sub path (IPFS gateways, archives) without rebuilding and stays browsable when opened directly from the file system.
+
+The base is automatically prepended to all the URLs that start with / in other options, so you only need to specify it once.
+
+```ts
+export default {
+  base: '/base/'
+}
+```
+
+Can also be set per build with `vitepress build --base /base/`.
+
+## Routing
+
+### cleanUrls
+
+- Type: `boolean`
+- Default: `false`
+
+When set to `true`, VitePress will remove the trailing `.html` from URLs. Also see [Generating Clean URLs](../guide/routing#generating-clean-urls).
+
+::: warning Server Support Required
+Enabling this may require additional configuration on your hosting platform. For it to work, your server must be able to serve `/foo.html` when visiting `/foo` **without a redirect**.
+:::
+
+### rewrites
+
+- Type: `Record<string, string>`
+
+Defines custom directory &lt;-&gt; URL mappings. See [Routing: Route Rewrites](../guide/routing#route-rewrites) for more details.
+
+```ts
+export default {
+  rewrites: {
+    'source/:page': 'destination/:page'
+  }
+}
+```
+
+## Build
+
+### srcDir
+
+- Type: `string`
+- Default: `.`
+
+The directory where your markdown pages are stored, relative to project root. Also see [Root and Source Directory](../guide/routing#root-and-source-directory).
+
+```ts
+export default {
+  srcDir: './src'
+}
+```
+
+### srcExclude
+
+- Type: `string[]`
+- Default: `undefined`
+
+A [glob pattern](https://github.com/mrmlnc/fast-glob#pattern-syntax) for matching markdown files that should be excluded as source content.
+
+```ts
+export default {
+  srcExclude: ['**/README.md', '**/TODO.md']
+}
+```
+
+### outDir
+
+- Type: `string`
+- Default: `./.vitepress/dist`
+
+The build output location for the site, relative to [project root](../guide/routing#root-and-source-directory).
+
+```ts
+export default {
+  outDir: '../public'
+}
+```
+
+### assetsDir
+
+- Type: `string`
+- Default: `assets`
+
+Specify the directory to nest generated assets under. The path should be inside [`outDir`](#outdir) and is resolved relative to it.
+
+```ts
+export default {
+  assetsDir: 'static'
+}
+```
+
+### assetsBase
+
+- Type: `string`
+- Default: `undefined`
+
+URL prefix the generated assets (everything under [`assetsDir`](#assetsdir)) are served from — typically a CDN. Must be an absolute URL, a protocol-relative URL, or a root-absolute path; a trailing slash is appended if missing.
+
+```ts
+export default {
+  base: '/',
+  assetsBase: 'https://cdn.example.com/'
+  // scripts, styles, fonts and imported images resolve to
+  // https://cdn.example.com/assets/*
+}
+```
+
+The emitted asset URL is `assetsBase` joined with the output-relative file path, so the CDN should mirror the layout of `outDir` (upload `outDir/assets` so it is reachable at `<assetsBase>/assets/*`). HTML pages, Markdown links, [`public`](../guide/asset-handling#the-public-directory) files and `hashmap.json` stay on [`base`](#base).
+
+When `assetsBase` points at another origin, VitePress adds `crossorigin` to the emitted script and preload tags — the CDN must send `Access-Control-Allow-Origin` for your site's origin (module scripts are always fetched in CORS mode).
+
+Only production builds are affected. `vitepress preview` serves a root-absolute `assetsBase` (like `/cdn/`) from the local dist; an external one is requested from the real URL. Can also be set per build with `vitepress build --assetsBase https://cdn.example.com/`.
+
+### assetsShards
+
+- Type: `number`
+- Default: `undefined`
+
+Spreads the generated assets over this many subdirectories of [`assetsDir`](#assetsdir), `assets/0/` through `assets/N-1/`, instead of one flat directory. Use it when the host caps the number of files per directory; Netlify, for example, allows 54,000. Each page emits two JavaScript files, so a site with 60,000 pages needs at least three shards, plus some headroom because files are distributed by a hash of their name.
+
+```ts
+export default {
+  assetsShards: 4
+}
+```
+
+Shared chunks stay in `assets/chunks/`. A file's shard depends only on its name, so unchanged files keep their URL between builds. Only production builds are affected.
+
+### icons
+
+- Type: `{ include?: string[] }`
+
+Optionen for the generated icon styles. The build collects every iconify icon rendered during SSR. Names are fully qualified as `collection:name`, resolved against the `@iconify-json/*` packages declared in your project's dependencies.
+
+Icons rendered only on the client — inside `<ClientOnly>`, or after hydration — are invisible to SSR collection. List them in `include` to force them into the stylesheet:
+
+```ts
+export default {
+  icons: {
+    include: ['mdi:home', 'simple-icons:discord']
+  }
+}
+```
+
+### cacheDir
+
+- Type: `string`
+- Default: `./.vitepress/cache`
+
+The directory for cache files, relative to [project root](../guide/routing#root-and-source-directory). See also: [cacheDir](https://vite.dev/config/shared-options.html#cachedir).
+
+```ts
+export default {
+  cacheDir: './.vitepress/.vite'
+}
+```
+
+### ignoreDeadLinks
+
+- Type: `boolean | 'localhostLinks' | (string | RegExp | ((link: string, source: string) => boolean))[]`
+- Default: `false`
+
+When set to `true`, VitePress will not fail builds due to dead links.
+
+When set to `'localhostLinks'`, the build will fail on dead links, but won't check `localhost` links.
+
+```ts
+export default {
+  ignoreDeadLinks: true
+}
+```
+
+It can also be an array of exact url string, regex patterns, or custom filter functions.
+
+```ts
+export default {
+  ignoreDeadLinks: [
+    // ignore exact url "/playground"
+    '/playground',
+    // ignore all localhost links
+    /^https?:\/\/localhost/,
+    // ignore all links include "/repl/""
+    /\/repl\//,
+    // custom function, ignore all links include "ignore"
+    (url) => {
+      return url.toLowerCase().includes('ignore')
+    }
+  ]
+}
+```
+
+### mpa <Badge type="warning" text="experimental" />
+
+- Type: `boolean`
+- Default: `false`
+
+When set to `true`, the production app will be built in [MPA Mode](../guide/mpa-mode). MPA mode ships 0kb JavaScript by default, at the cost of disabling client-side navigation and requires explicit opt-in for interactivity.
+
+## Theming
+
+### appearance
+
+- Type: `boolean | 'dark' | 'force-dark' | 'force-auto' | import('@vueuse/core').UseDarkOptions`
+- Default: `true`
+
+Whether to enable dark mode (by adding the `.dark` class to the `<html>` element).
+
+- If the option is set to `true`, the default theme will be determined by the user's preferred color scheme.
+- If the option is set to `dark`, the theme will be dark by default, unless the user manually toggles it.
+- If the option is set to `false`, users will not be able to toggle the theme.
+- If the option is set to `'force-dark'`, the theme will always be dark and users will not be able to toggle it.
+- If the option is set to `'force-auto'`, the theme will always be determined by the user's preferred color scheme and users will not be able to toggle it.
+
+This option injects an inline script that restores users settings from local storage using the `vitepress-theme-appearance` key. This ensures the `.dark` class is applied before the page is rendered to avoid flickering.
+
+`appearance.initialValue` can only be `'dark' | undefined`. Refs or getters are not supported.
+
+### lastUpdated
+
+- Type: `boolean`
+- Default: `false`
+
+Whether to get the last updated timestamp for each page using Git. The timestamp will be included in each page's page data, accessible via [`useData`](./runtime-api#usedata).
+
+When using the default theme, enabling this option will display each page's last updated time. You can customize the text via [`themeConfig.lastUpdated.text`](./default-theme-config#lastupdated) option.
+
+## Customization
+
+### markdown
+
+- Type: `MarkdownOption`
+
+Configure Markdown parser options. VitePress uses [Markdown-it](https://github.com/markdown-it/markdown-it) as the parser, and [Shiki](https://github.com/shikijs/shiki) to highlight language syntax. Inside this option, you may pass various Markdown related options to fit your needs.
+
+```js
+export default {
+  markdown: {...}
+}
+```
+
+Check the [type declaration and jsdocs](https://github.com/vuejs/vitepress/blob/main/src/node/markdown/markdown.ts) for all the options available.
+
+Set `markdown.headers` to `true` or pass [`@mdit-vue/plugin-headers`](https://github.com/mdit-vue/mdit-vue/tree/main/packages/plugin-headers) options to collect headings into [`useData().page.headers`](./runtime-api#usedata). This option is disabled by default.
+
+### vite
+
+- Type: `import('vite').UserConfig`
+
+Pass raw [Vite Config](https://vite.dev/config/) to internal Vite dev server / bundler.
+
+```js
+export default {
+  vite: {
+    // Vite config options
+  }
+}
+```
+
+### vue
+
+- Type: `import('@vitejs/plugin-vue').Optionen`
+
+Pass raw [`@vitejs/plugin-vue` options](https://github.com/vitejs/vite-plugin-vue/tree/main/packages/plugin-vue#options) to the internal plugin instance.
+
+```js
+export default {
+  vue: {
+    // @vitejs/plugin-vue options
+  }
+}
+```
+
+## Build Hooks
+
+VitePress build hooks allow you to add new functionality and behaviors to your website:
+
+- Sitemap
+- Suche Indexing
+- PWA
+- Teleports
+
+### buildEnd
+
+- Type: `(siteConfig: SiteConfig) => Awaitable<void>`
+
+`buildEnd` is a build CLI hook, it will run after build (SSG) finish but before VitePress CLI process exits.
+
+```ts
+export default {
+  async buildEnd(siteConfig) {
+    // ...
+  }
+}
+```
+
+### postRender
+
+- Type: `(context: SSGContext) => Awaitable<SSGContext | void>`
+
+`postRender` is a build hook, called when SSG rendering is done. It will allow you to handle the teleports content during SSG.
+
+```ts
+export default {
+  async postRender(context) {
+    // ...
+  }
+}
+```
+
+```ts
+interface SSGContext {
+  content: string
+  teleports?: Record<string, string>
+  vpIcons: Set<string>
+  [key: string]: any
+}
+```
+
+### transformHead
+
+- Type: `(context: TransformContext) => Awaitable<HeadConfig[]>`
+
+`transformHead` is a build hook to add extra tags to the `<head>` of each page. It allows you to add head entries that cannot be statically added to your VitePress config. You only need to return extra entries, they will be merged automatically with the existing ones.
+
+::: warning
+Don't mutate anything inside the `context`.
+:::
+
+```ts
+export default {
+  async transformHead(context) {
+    // ...
+  }
+}
+```
+
+```ts
+interface TransformContext {
+  page: string // e.g. index.md (relative to srcDir)
+  assets: string[] // all non-js/css assets as fully resolved public URL
+  siteConfig: SiteConfig
+  siteData: SiteData
+  pageData: PageData
+  title: string
+  description: string
+  head: HeadConfig[]
+  content: string
+}
+```
+
+This hook is only called when performing a build, it is not called during dev.
+
+The extra tags will be added to the static HTML files generated by the build. They will not be updated during client-side navigation.
+
+In many cases, using the [`transformPageData`](#transformpagedata) hook is a cleaner solution. That hook will also be applied to both client-side navigation and during dev. But if generating the head tags is computationally expensive then `transformHead` will avoid that overhead during dev.
+
+#### Beispiel: Adding `og:image` meta
+
+```ts
+export default {
+  async transformHead(context) {
+    if (context.page === '404.md') {
+      return
+    }
+
+    // The implementation details of `generatePageImage` would depend
+    // on your requirements. Here we assume it generates a suitable
+    // image for each page and returns the image URL.
+    const imageUrl = await generatePageImage(context)
+    
+    return [[
+      'meta',
+      { name: 'og:image', content: imageUrl }
+    ]]
+  }
+}
+```
+
+Here we're assuming that the image URL is dynamic and time-consuming to generate. Using `transformHead` avoids that overhead during development.
+
+For simpler cases, it may be possible to use the [`head`](./frontmatter-config#head) setting in frontmatter, or [`transformPageData`](#transformpagedata).
+
+### transformHtml
+
+- Type: `(code: string, id: string, context: TransformContext) => Awaitable<string | void>`
+
+`transformHtml` is a build hook to transform the content of each page before saving to disk.
+
+::: warning
+Don't mutate anything inside the `context`. Also, modifying the html content may cause hydration problems in runtime.
+:::
+
+::: note
+The icon stylesheet link still carries its `vp-icons.__VP_ICONS_HASH__.css` placeholder at this point — the content hash only exists once every page has rendered, and it is substituted right after. Hooks that inline or fingerprint head assets should skip that tag.
+:::
+
+```ts
+export default {
+  async transformHtml(code, id, context) {
+    // ...
+  }
+}
+```
+
+### transformPageData
+
+- Type: `(pageData: PageData, context: TransformPageContext) => Awaitable<Partial<PageData> | { [key: string]: any } | void>`
+
+`transformPageData` is a hook to transform the `pageData` of each page. You can directly mutate `pageData` or return changed values which will be merged into the page data.
+
+::: warning
+Don't mutate anything inside the `context` and be careful that this might impact the performance of dev server, especially if you have some network requests or heavy computations (like generating images) in the hook. You can check for `process.env.NODE_ENV === 'production'` for conditional logic.
+:::
+
+```ts
+export default {
+  async transformPageData(pageData, { siteConfig }) {
+    pageData.contributors = await getPageContributors(pageData.relativePath)
+  }
+
+  // or return data to be merged
+  async transformPageData(pageData, { siteConfig }) {
+    return {
+      contributors: await getPageContributors(pageData.relativePath)
+    }
+  }
+}
+```
+
+```ts
+interface TransformPageContext {
+  siteConfig: SiteConfig
+}
+```
+
+#### Beispiel: Adding a `<meta name="og:title">`
+
+```ts
+export default {
+  transformPageData(pageData) {
+    const title = pageData.frontmatter.layout === 'home'
+      ? 'VitePress'
+      : `${pageData.title} | VitePress`
+
+    pageData.frontmatter.head ??= []
+    pageData.frontmatter.head.push([
+      'meta',
+      { name: 'og:title', content: title }
+    ])
+  }
+}
+```
+
+#### Beispiel: Adding a canonical URL `<link>`
+
+```ts
+export default {
+  transformPageData(pageData) {
+    const canonicalUrl = `https://example.com/${pageData.relativePath}`
+      .replace(/index\.md$/, '')
+      .replace(/\.md$/, '.html')
+
+    pageData.frontmatter.head ??= []
+    pageData.frontmatter.head.push([
+      'link',
+      { rel: 'canonical', href: canonicalUrl }
+    ])
+  }
+}
+```

From dd610a3853a0eac90e1ca56bb1596f6b126b2625 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:10 +0200
Subject: [PATCH 044/199] docs(de): translate guide text

---
 docs/de/guide/asset-handling.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/asset-handling.md b/docs/de/guide/asset-handling.md
index 2a7e49a5d..36da2d87c 100644
--- a/docs/de/guide/asset-handling.md
+++ b/docs/de/guide/asset-handling.md
@@ -41,14 +41,14 @@ Wenn deine Website unter einer URL bereitgestellt wird, die nicht dem Stammverze
 Referenzen auf statische Assets werden automatisch an \`base\` angepasst. Eine absolute Referenz auf eine Datei in \`public\` funktioniert daher mit jedem \`base\` und muss nicht aktualisiert werden:
 
 \`\`\`md
-![Ein Bild](/image-inside-public.png)
+![Ein Bild](/image-innerhalb-public.png)
 \`\`\`
 
 Nur dynamisch erzeugte Pfade benötigen besondere Behandlung – beispielsweise ein Bild, dessen \`src\` auf einem Wert aus der Theme-Konfiguration basiert. Um den Basis-Pfad zur Laufzeit voranzustellen, umschließe solche Pfade mit dem [\`withBase\`-Helper](../reference/runtime-api#withbase):
 
 \`\`\`vue
 <script setup>
-import { withBase, useData } from 'vitepress'
+import { withBase, useData } von 'vitepress'
 
 const { theme } = useData()
 </script>

From a250581c52d725e4ea9c7b30189748e87bf32fd0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:12 +0200
Subject: [PATCH 045/199] docs(de): translate guide text

---
 docs/de/guide/cms.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/guide/cms.md b/docs/de/guide/cms.md
index 0bff6746f..b627c2d08 100644
--- a/docs/de/guide/cms.md
+++ b/docs/de/guide/cms.md
@@ -1,13 +1,13 @@
 ---
 outline: deep
-description: Connect VitePress to a headless CMS using dynamic routes and data loaders.
+description: Connect VitePress to a headless CMS Verwendung dynamic routes and data loaders.
 ---
 
-# Connecting to a CMS
+# Mit einem CMS verbinden
 
 ## General Workflow
 
-Connecting VitePress to a CMS will largely revolve around [Dynamic Routes](./routing#dynamic-routes). Make sure to understand how it works before proceeding.
+Connecting VitePress to a CMS will largely revolve around [Dynamisch Routes](./routing#dynamic-routes). Stelle sicher to understand how it works bevor proceeding.
 
 Since each CMS will work differently, here we can only provide a generic workflow that you will need to adapt to your specific scenario.
 
@@ -20,7 +20,7 @@ Since each CMS will work differently, here we can only provide a generic workflo
     const env = loadEnv('', process.cwd())
     ```
 
-2. Fetch the necessary data from the CMS and format it into proper paths data:
+2. Fetch the necessary data von the CMS and format it in proper paths data:
 
     ```js
     export default {
@@ -54,4 +54,4 @@ Since each CMS will work differently, here we can only provide a generic workflo
 
 ## Integration Guides
 
-If you have written a guide on integrating VitePress with a specific CMS, please use the "Edit this page" link below to submit it here!
+Wenn du have written a guide on integrating VitePress mit a specific CMS, please use the "Edit this page" link below to submit it here!

From f2f9ab8d69099e13087eacb2391a8fcac1b4748d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:15 +0200
Subject: [PATCH 046/199] docs(de): translate guide text

---
 docs/de/guide/data-loading.md | 44 +++++++++++++++++------------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index 1c11e4698..0b81fd98b 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -1,16 +1,16 @@
 ---
-description: Load arbitrary data at build time using VitePress data loaders and import it from pages or components.
+description: Load arbitrary data at build time Verwendung VitePress data loaders and import it von pages or components.
 ---
 
-# Build-Time Data Loading
+# Build-Time Daten laden
 
-VitePress provides a feature called **data loaders** that allows you to load arbitrary data and import it from pages or components. The data loading is executed **only at build time**: the resulting data will be serialized as JSON in the final JavaScript bundle.
+VitePress stellt bereit a feature genannt **data loaders** that ermöglicht you to load arbitrary data and import it von pages or components. The data loading is executed **only at build time**: the resulting data will be serialized as JSON in the final JavaScript bundle.
 
-Data loaders can be used to fetch remote data, or generate metadata based on local files. For example, you can use data loaders to parse all your local API pages and automatically generate an index of all API entries.
+Data loaders can be verwendet to fetch remote data, or generate metadata based on local files. Zum Beispiel, you can use data loaders to parse all your local API pages and automatisch generate an index of all API entries.
 
-## Basic Usage
+## Basic Verwendung
 
-A data loader file must end with either `.data.js` or `.data.ts`. The file should provide a default export of an object with the `load()` method:
+A data loader file must end mit either `.data.js` or `.data.ts`. The file should provide a default export of an object mit the `load()` method:
 
 ```js [example.data.js]
 export default {
@@ -24,7 +24,7 @@ export default {
 
 The loader module is evaluated only in Node.js, so you can import Node APIs and npm dependencies as needed.
 
-You can then import data from this file in `.md` pages and `.vue` components using the `data` named export:
+Du kannst then import data von this file in `.md` pages and `.vue` components Verwendung the `data` named export:
 
 ```vue
 <script setup>
@@ -55,13 +55,13 @@ export default {
 }
 ```
 
-## Data from Local Files
+## Data von Local Dateien
 
-When you need to generate data based on local files, you should use the `watch` option in the data loader so that changes made to these files can trigger hot updates.
+Wenn du need to generate data based on local files, you should use the `watch` option in the data loader so that changes made to these files can trigger hot updates.
 
 The `watch` option is also convenient in that you can use [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match multiple files. The patterns can be relative to the loader file itself, and the `load()` function will receive the matched files as absolute paths.
 
-The following example shows loading CSV files and transforming them into JSON using [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Because this file only executes at build time, you will not be shipping the CSV parser to the client!
+The following example shows loading CSV files and transforming them in JSON Verwendung [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Because this file only executes at build time, you will not be shipping the CSV parser to the client!
 
 ```js
 import fs from 'node:fs'
@@ -85,7 +85,7 @@ export default {
 
 ## `createContentLoader`
 
-When building a content focused site, we often need to create an "archive" or "index" page: a page where we list all available entries in our content collection, for example blog posts or API pages. We **can** implement this directly with the data loader API, but since this is such a common use case, VitePress also provides a `createContentLoader` helper to simplify this:
+When building a content focused site, we often need to create an "archive" or "index" page: a page where we list all verfügbar entries in our content collection, for example blog posts or API pages. We **can** implement this directly mit the data loader API, but since this is such a common use case, VitePress also stellt bereit a `createContentLoader` helper to simplify this:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
@@ -93,11 +93,11 @@ import { createContentLoader } from 'vitepress'
 export default createContentLoader('posts/*.md', /* options */)
 ```
 
-The helper takes a glob pattern relative to the [source directory](./routing#source-directory), and returns a `{ watch, load }` data loader object that can be used as the default export in a data loader file. It also implements caching based on file modified timestamps to improve dev performance.
+The helper takes a glob pattern relative to the [source directory](./routing#source-directory), and gibt zurück a `{ watch, load }` data loader object that can be verwendet as the default export in a data loader file. It also implements caching based on file modified timestamps to improve dev performance.
 
-Note the loader only works with Markdown files - matched non-Markdown files will be skipped.
+Hinweis the loader only works mit Markdown files - matched non-Markdown files will be skipped.
 
-The loaded data will be an array with the type of `ContentData[]`:
+The loaded data will be an array mit the type of `ContentData[]`:
 
 ```ts
 interface ContentData {
@@ -115,7 +115,7 @@ interface ContentData {
 }
 ```
 
-By default, only `url` and `frontmatter` are provided. This is because the loaded data will be inlined as JSON in the client bundle, so we need to be cautious about its size. Here's an example using the data to build a minimal blog index page:
+Standardmäßig, only `url` and `frontmatter` are provided. This is because the loaded data will be inlined as JSON in the client bundle, so we need to be cautious about its size. Here's an example Verwendung the data to build a minimal blog index page:
 
 ```vue
 <script setup>
@@ -133,9 +133,9 @@ import { data as posts } from './posts.data.js'
 </template>
 ```
 
-### Options
+### Optionen
 
-The default data may not suit all needs - you can opt-in to transform the data using options:
+The default data may not suit all needs - you can opt-in to transform the data Verwendung options:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
@@ -159,9 +159,9 @@ export default createContentLoader('posts/*.md', {
 })
 ```
 
-Check out how it is used in the [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
+Check out how it is verwendet in the [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
 
-The `createContentLoader` API can also be used inside [build hooks](../reference/site-config#build-hooks):
+The `createContentLoader` API can also be verwendet innerhalb [build hooks](../reference/site-config#build-hooks):
 
 ```js [.vitepress/config.js]
 export default {
@@ -216,7 +216,7 @@ interface ContentOptions<T = ContentData[]> {
 
 ## Typed Data Loaders
 
-When using TypeScript, you can type your loader and `data` export like so:
+When Verwendung TypeScript, you can type your loader and `data` export like so:
 
 ```ts
 import { defineLoader } from 'vitepress'
@@ -237,9 +237,9 @@ export default defineLoader({
 })
 ```
 
-## Configuration
+## Konfiguration
 
-To get the configuration information inside a loader, you can use some code like this:
+To get the Konfiguration information innerhalb a loader, you can use some code like this:
 
 ```ts
 import type { SiteConfig } from 'vitepress'

From bcb09ad56ad62c3e07f4d9b881a62e11d1bed537 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:17 +0200
Subject: [PATCH 047/199] docs(de): translate guide text

---
 docs/de/guide/deploy.md | 86 ++++++++++++++++++++---------------------
 1 file changed, 43 insertions(+), 43 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index d3d05cec4..d72b523e2 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -1,14 +1,14 @@
 ---
 outline: deep
-description: Deploy your VitePress site to popular platforms like Netlify, Vercel, GitHub Pages, and more.
+description: Deploy your VitePress site to popular platforms like Netlify, Vercel, GitHub Seiten, and more.
 ---
 
 # Deploy Your VitePress Site
 
 The following guides are based on some shared assumptions:
 
-- The VitePress site is inside the `docs` directory of your project.
-- You are using the default build output directory (`.vitepress/dist`).
+- The VitePress site is innerhalb the `docs` directory of your project.
+- You are Verwendung the default build output directory (`.vitepress/dist`).
 - VitePress is installed as a local dependency in your project, and you have set up the following scripts in your `package.json`:
 
   ```json [package.json]
@@ -34,9 +34,9 @@ The following guides are based on some shared assumptions:
    $ npm run docs:preview
    ```
 
-   The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. You can use this to make sure everything looks good before pushing to production.
+   The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. Du kannst use this to make sure everything looks good bevor pushing to production.
 
-3. You can configure the port of the server by passing `--port` as an argument.
+3. Du kannst configure the port of the server by passing `--port` as an argument.
 
    ```json
    {
@@ -50,13 +50,13 @@ The following guides are based on some shared assumptions:
 
 ## Setting a Public Base Path
 
-By default, we assume the site is going to be deployed at the root path of a domain (`/`). If your site is going to be served at a sub-path, e.g. `https://mywebsite.com/blog/`, then you need to set the [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
+Standardmäßig, we assume the site is going to be deployed at the root path of a domain (`/`). If your site is going to be served at a sub-path, e.g. `https://mywebsite.com/blog/`, then you need to set the [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
 
-**Example:** If you're using Github (or GitLab) Pages and deploying to `user.github.io/repo/`, then set your `base` to `/repo/`.
+**Beispiel:** Wenn du're Verwendung Github (or GitLab) Seiten and deploying to `user.github.io/repo/`, then set your `base` to `/repo/`.
 
 ## Relocatable Builds (Relative Base) {#relocatable-builds-relative-base}
 
-When the final URL of the site isn't known at build time — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled into an app — set `base` to `'./'`:
+When the final URL of the site isn't known at build time — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled in an app — set `base` to `'./'`:
 
 ```ts
 export default {
@@ -64,33 +64,33 @@ export default {
 }
 ```
 
-Every page then references assets and other pages relative to its own location, and the client runtime recovers the real mount point when the page loads. The same build works from **any** sub path without rebuilding — including several at once — with routing, search and prefetching fully functional.
+Every page then references assets and other pages relative to its own location, and the client runtime recovers the real mount point when the page loads. The same build works von **any** sub path ohne rebuilding — including several at once — mit routing, search and prefetching fully functional.
 
-Opening the generated HTML files straight from the file system (`file://`) also works as a styled, fully navigable static site. Browsers block JavaScript modules over `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
+Opening the generated HTML files straight von the file system (`file://`) also works as a styled, fully navigable static site. Browsers block JavaScript modules over `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
 
 A few things to know:
 
 - Keep [`cleanUrls`](../reference/site-config#cleanurls) off (the default): portable output needs links that end in `.html`, since there is no server to rewrite pretty URLs.
-- `404.html` is generated for the root depth. Hosts that serve it as a fallback for arbitrarily deep URLs will render it without styles (there is no correct relative prefix for an unknown depth).
+- `404.html` is generated for the root depth. Hosts that serve it as a fallback for arbitrarily deep URLs will render it ohne styles (there is no correct relative prefix for an unknown depth).
 - [`head`](../reference/site-config#head) entries are emitted verbatim, as always — avoid root-absolute paths like `/favicon.ico` there and prefer absolute URLs or `transformHead`.
-- Raw HTML `<a>` tags in Markdown keep their `href` as written — use Markdown link syntax for site-absolute links (embedded `<img>` sources go through the asset pipeline and are handled).
-- Links created by [`createContentLoader`](./data-loading#createcontentloader) content stay site-absolute (their HTML is embedded into other pages, so no single relative prefix is correct) — they resolve only for a root mount.
+- Raw HTML `<a>` tags in Markdown keep their `href` as written — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
+- Links erstellt by [`createContentLoader`](./data-loading#createcontentloader) content stay site-absolute (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
 - Serve pages at their canonical URLs: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
 - The dev server always serves at `/`; the relative behavior applies to the production build.
 
 ## HTTP Cache Headers
 
-If you have control over the HTTP headers on your production server, you can configure `cache-control` headers to achieve better performance on repeated visits.
+Wenn du have control over the HTTP headers on your production server, you can configure `cache-control` headers to achieve better performance on repeated visits.
 
-The production build uses hashed file names for static assets (JavaScript, CSS and other imported assets not in `public`). If you inspect the production preview using your browser devtools' network tab, you will see files like `app.4f283b18.js`.
+The production build verwendet hashed file names for static assets (JavaScript, CSS and other imported assets not in `public`). Wenn du inspect the production preview Verwendung your browser devtools' network tab, you will see files like `app.4f283b18.js`.
 
-This `4f283b18` hash is generated from the content of this file. The same hashed URL is guaranteed to serve the same file content - if the contents change, the URLs change too. This means you can safely use the strongest cache headers for these files. All such files will be placed under `assets/` in the output directory, so you can configure the following header for them:
+This `4f283b18` hash is generated von the content of this file. The same hashed URL is guaranteed to serve the same file content - if the contents change, the URLs change too. Das bedeutet you can safely use the strongest cache headers for these files. All such files will be placed under `assets/` in the output directory, so you can configure the following header for them:
 
 ```
 Cache-Control: max-age=31536000,immutable
 ```
 
-::: details Example Netlify `_headers` file
+::: details Beispiel Netlify `_headers` file
 
 ```
 /assets/*
@@ -98,13 +98,13 @@ Cache-Control: max-age=31536000,immutable
   cache-control: immutable
 ```
 
-Note: the `_headers` file should be placed in the [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - so that it is copied verbatim to the output directory.
+Hinweis: the `_headers` file should be placed in the [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - so that it is copied verbatim to the output directory.
 
 [Netlify custom headers documentation](https://docs.netlify.com/routing/headers/)
 
 :::
 
-::: details Example Vercel config in `vercel.json`
+::: details Beispiel Vercel config in `vercel.json`
 
 ```json
 {
@@ -122,29 +122,29 @@ Note: the `_headers` file should be placed in the [public directory](./asset-han
 }
 ```
 
-Note: the `vercel.json` file should be placed at the root of your **repository**.
+Hinweis: the `vercel.json` file should be placed at the root of your **repository**.
 
-[Vercel documentation on headers config](https://vercel.com/docs/concepts/projects/project-configuration#headers)
+[Vercel documentation on headers config](https://vercel.com/docs/concepts/projects/project-Konfiguration#headers)
 
 :::
 
 ## Platform Guides
 
-### Netlify / Vercel / Cloudflare Pages / AWS Amplify / Render {#generic}
+### Netlify / Vercel / Cloudflare Seiten / AWS Amplify / Render {#generic}
 
-Set up a new project and change these settings using your dashboard:
+Set up a new project and change these settings Verwendung your dashboard:
 
 - **Build Command:** `npm run docs:build`
-- **Output Directory:** `docs/.vitepress/dist`
+- **Output Verzeichnis:** `docs/.vitepress/dist`
 - **Node Version:** `20` (or above)
 
 ::: warning
-Don't enable options like _Auto Minify_ for HTML code. It will remove comments from output which have meaning to Vue. You may see hydration mismatch errors if they get removed.
+Don't enable options like _Auto Minify_ for HTML code. It will remove comments von output which have meaning to Vue. You may see hydration mismatch errors if they get removed.
 :::
 
-### GitHub Pages
+### GitHub Seiten
 
-1. Create a file named `deploy.yml` inside `.github/workflows` directory of your project with some content like this:
+1. Erstellen a file named `deploy.yml` innerhalb `.github/workflows` directory of your project mit some content like this:
 
    ```yaml [.github/workflows/deploy.yml]
    # Sample workflow for building and deploying a VitePress site to GitHub Pages
@@ -223,18 +223,18 @@ Don't enable options like _Auto Minify_ for HTML code. It will remove comments f
    ```
 
    ::: warning
-   Make sure the `base` option in your VitePress is properly configured. See [Setting a Public Base Path](#setting-a-public-base-path) for more details.
+   Stelle sicher the `base` option in your VitePress is properly konfiguriert. See [Setting a Public Base Path](#setting-a-public-base-path) for more details.
    :::
 
-2. In your repository's settings under "Pages" menu item, select "GitHub Actions" in "Build and deployment > Source".
+2. In your repository's settings under "Seiten" menu item, select "GitHub Actions" in "Build and deployment > Source".
 
-3. Push your changes to the `main` branch and wait for the GitHub Actions workflow to complete. You should see your site deployed to `https://<username>.github.io/[repository]/` or `https://<custom-domain>/` depending on your settings. Your site will automatically be deployed on every push to the `main` branch.
+3. Push your changes to the `main` branch and wait for the GitHub Actions workflow to complete. Du solltest see your site deployed to `https://<username>.github.io/[repository]/` or `https://<custom-domain>/` depending on your settings. Your site will automatisch be deployed on every push to the `main` branch.
 
-### GitLab Pages
+### GitLab Seiten
 
-1. Set `outDir` in VitePress config to `../public`. Configure `base` option to `'/<repository>/'` if you want to deploy to `https://<username>.gitlab.io/<repository>/`. You don't need `base` if you're deploying to custom domain, user or group pages, or have "Use unique domain" setting enabled in GitLab.
+1. Set `outDir` in VitePress config to `../public`. Konfigurieren `base` option to `'/<repository>/'` if you want to deploy to `https://<username>.gitlab.io/<repository>/`. You don't need `base` if you're deploying to custom domain, user or group pages, or have "Verwenden unique domain" setting enabled in GitLab.
 
-2. Create a file named `.gitlab-ci.yml` in the root of your project with the content below. This will build and deploy your site whenever you make changes to your content:
+2. Erstellen a file named `.gitlab-ci.yml` in the root of your project mit the content below. This will build and deploy your site whenever you make changes to your content:
 
    ```yaml [.gitlab-ci.yml]
    image: node:24
@@ -257,9 +257,9 @@ Don't enable options like _Auto Minify_ for HTML code. It will remove comments f
 
 ### Azure
 
-1. Follow the [official documentation](https://docs.microsoft.com/en-us/azure/static-web-apps/build-configuration).
+1. Follow the [official documentation](https://docs.microsoft.com/en-us/azure/static-web-apps/build-Konfiguration).
 
-2. Set these values in your configuration file (and remove the ones you don't require, like `api_location`):
+2. Set these values in your Konfiguration file (and remove the ones you don't require, like `api_location`):
 
    - **`app_location`**: `/`
    - **`output_location`**: `docs/.vitepress/dist`
@@ -267,11 +267,11 @@ Don't enable options like _Auto Minify_ for HTML code. It will remove comments f
 
 ### CloudRay
 
-You can deploy your VitePress project with [CloudRay](https://cloudray.io/) by following these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
+Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by following these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
 
 ### Firebase
 
-1. Create `firebase.json` and `.firebaserc` at the root of your project:
+1. Erstellen `firebase.json` and `.firebaserc` at the root of your project:
 
    `firebase.json`:
 
@@ -304,7 +304,7 @@ You can deploy your VitePress project with [CloudRay](https://cloudray.io/) by f
 
 1. Follow documentation and guide given in [`heroku-buildpack-static`](https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static).
 
-2. Create a file called `static.json` in the root of your project with the below content:
+2. Erstellen a file genannt `static.json` in the root of your project mit the below content:
 
    ```json [static.json]
    {
@@ -314,13 +314,13 @@ You can deploy your VitePress project with [CloudRay](https://cloudray.io/) by f
 
 ### Hostinger
 
-You can deploy your VitePress project with [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/support/how-to-deploy-a-nodejs-website-in-hostinger/). While configuring build settings, choose VitePress as the framework and adjust the root directory to `./docs`.
+Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). While configuring build settings, choose VitePress as the framework and adjust the root directory to `./docs`.
 
 ### Lizard
 
-[Lizard (lizard.build)](https://lizard.build) builds VitePress sites from source and serves the generated HTML. For the layout used in this guide, it detects `docs:build` and serves `docs/.vitepress/dist` on port `80`.
+[Lizard (lizard.build)](https://lizard.build) builds VitePress sites von source and serves the generated HTML. For the layout verwendet in this guide, it detects `docs:build` and serves `docs/.vitepress/dist` on port `80`.
 
-Install the [Lizard CLI](https://lizard.build/docs/cli) and sign in with `lizard login`. To deploy a local source directory, run these commands from the project root containing `package.json`:
+Install the [Lizard CLI](https://lizard.build/docs/cli) and sign in mit `lizard login`. To deploy a local source directory, run these commands von the project root containing `package.json`:
 
 ```sh
 lizard init --name vitepress-docs
@@ -332,7 +332,7 @@ Leave build and start command overrides unset to use automatic detection. For Gi
 
 ### Stormkit
 
-You can deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
+Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
 
 ### Surge
 
@@ -352,7 +352,7 @@ npx harvis docs/.vitepress/dist
 
 ### nginx
 
-Here is a example of an nginx server block configuration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files with proper caching headers as well as handling `cleanUrls: true`.
+Here is a example of an nginx server block Konfiguration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files mit proper caching headers as well as handling `cleanUrls: wahr`.
 
 ```nginx
 map $uri $cache_control {

From 340ea8a35eb0cccef4b9f5485aad0e92fb64fa71 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:19 +0200
Subject: [PATCH 048/199] docs(de): translate guide text

---
 docs/de/guide/extending-default-theme.md | 94 ++++++++++++------------
 1 file changed, 47 insertions(+), 47 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index 1758d19b1..01bdf63e8 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -1,25 +1,25 @@
 ---
 outline: deep
-description: Customize and extend the VitePress default theme with custom CSS, components, layouts, and slots.
+description: Anpassen and extend the VitePress default theme mit custom CSS, components, layouts, and slots.
 ---
 
-# Extending the Default Theme
+# Standard-Theme erweitern
 
-VitePress' default theme is optimized for documentation, and can be customized. Consult the [Default Theme Config Overview](../reference/default-theme-config) for a comprehensive list of options.
+VitePress' default theme is optimized for documentation, and can be customized. Consult the [Standard-Theme Config Übersicht](../reference/default-theme-config) for a comprehensive list of options.
 
-However, there are a number of cases where configuration alone won't be enough. For example:
+However, there are a number of cases where Konfiguration alone won't be enough. Zum Beispiel:
 
 1. You need to tweak the CSS styling;
 2. You need to modify the Vue app instance, for example to register global components;
-3. You need to inject custom content into the theme via layout slots.
+3. You need to inject custom content in the theme via layout slots.
 
-These advanced customizations will require using a custom theme that "extends" the default theme.
+These advanced customizations will require Verwendung a custom theme that "extends" the default theme.
 
 ::: tip
-Before proceeding, make sure to first read [Using a Custom Theme](./custom-theme) to understand how custom themes work.
+Before proceeding, make sure to first read [Using a Eigenes Theme](./custom-theme) to understand how custom themes work.
 :::
 
-## Customizing CSS
+## Anpassen CSS
 
 The default theme CSS is customizable by overriding root level CSS variables:
 
@@ -42,7 +42,7 @@ See [default theme CSS variables](https://github.com/vuejs/vitepress/blob/main/s
 
 ### Navbar
 
-The navbar draws a single background surface controlled by CSS variables, so its look can be changed without touching component internals:
+The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching component internals:
 
 ```css
 :root {
@@ -63,7 +63,7 @@ The navbar draws a single background surface controlled by CSS variables, so its
 }
 ```
 
-For example, a frosted-glass navbar:
+Zum Beispiel, a frosted-glass navbar:
 
 ```css
 :root {
@@ -75,16 +75,16 @@ For example, a frosted-glass navbar:
 The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color by default, and where the two bars meet they share a single blurred surface, so the glass stays continuous across them.
 
 ::: warning
-`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. When using a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color without the blur.
+`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. When Verwendung a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
 :::
 
-When the nav items don't fit the available width, they move into the `⋯` menu at the end of the navbar instead of being clipped, starting with the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized with [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
+When the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar instead of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
 
 ## Using Different Fonts
 
-VitePress uses [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build output. The font is also auto preloaded in production. However, this may not be desirable if you want to use a different main font.
+VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build output. The font is also auto preloaded in production. However, this may not be desirable if you want to use a different main font.
 
-To avoid including Inter in the build output, import the theme from `vitepress/theme-without-fonts` instead:
+To avoid including Inter in the build output, import the theme von `vitepress/theme-ohne-fonts` instead:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme-without-fonts'
@@ -102,10 +102,10 @@ export default DefaultTheme
 ```
 
 ::: warning
-If you are using optional components like the [Team Page](../reference/default-theme-team-page) components, make sure to also import them from `vitepress/theme-without-fonts`!
+Wenn du are Verwendung optional components like the [Team Seite](../reference/default-theme-team-page) components, make sure to also import them von `vitepress/theme-ohne-fonts`!
 :::
 
-If your font is a local file referenced via `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` with hashed filename. To preload this file, use the [transformHead](../reference/site-config#transformhead) build hook:
+If your font is a local file referenced via `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` mit hashed filename. To preload this file, use the [transformHead](../reference/site-config#transformhead) build hook:
 
 ```js [.vitepress/config.js]
 export default {
@@ -145,7 +145,7 @@ export default {
 }
 ```
 
-If you're using TypeScript:
+Wenn du're Verwendung TypeScript:
 ```ts [.vitepress/theme/index.ts]
 import type { Theme } from 'vitepress'
 import DefaultTheme from 'vitepress/theme'
@@ -159,11 +159,11 @@ export default {
 } satisfies Theme
 ```
 
-Since we are using Vite, you can also leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of components.
+Since we are Verwendung Vite, you can also leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of components.
 
 ## Layout Slots
 
-The default theme's `<Layout/>` component has a few slots that can be used to inject content at certain locations of the page. Here's an example of injecting a component into the before outline:
+The default theme's `<Layout/>` component has a few slots that can be verwendet to inject content at certain locations of the page. Here's an example of injecting a component in the bevor outline:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -210,33 +210,33 @@ export default {
 }
 ```
 
-Full list of slots available in the default theme layout:
+Full list of slots verfügbar in the default theme layout:
 
 - When `layout: 'doc'` (default) is enabled via frontmatter:
   - `doc-top`
   - `doc-bottom`
-  - `doc-footer-before`
-  - `doc-before`
-  - `doc-after`
-  - `sidebar-nav-before`
-  - `sidebar-nav-after`
+  - `doc-footer-bevor`
+  - `doc-bevor`
+  - `doc-nach`
+  - `sidebar-nav-bevor`
+  - `sidebar-nav-nach`
   - `aside-top`
   - `aside-bottom`
-  - `aside-outline-before`
-  - `aside-outline-after`
-  - `aside-ads-before`
-  - `aside-ads-after`
+  - `aside-outline-bevor`
+  - `aside-outline-nach`
+  - `aside-ads-bevor`
+  - `aside-ads-nach`
 - When `layout: 'home'` is enabled via frontmatter:
-  - `home-hero-before`
-  - `home-hero-info-before`
+  - `home-hero-bevor`
+  - `home-hero-info-bevor`
   - `home-hero-info`
-  - `home-hero-info-after`
-  - `home-hero-actions-before-actions`
-  - `home-hero-actions-after`
+  - `home-hero-info-nach`
+  - `home-hero-actions-bevor-actions`
+  - `home-hero-actions-nach`
   - `home-hero-image`
-  - `home-hero-after`
-  - `home-features-before`
-  - `home-features-after`
+  - `home-hero-nach`
+  - `home-features-bevor`
+  - `home-features-nach`
 - When `layout: 'page'` is enabled via frontmatter:
   - `page-top`
   - `page-bottom`
@@ -245,18 +245,18 @@ Full list of slots available in the default theme layout:
 - Always:
   - `layout-top`
   - `layout-bottom`
-  - `nav-bar-title-before`
-  - `nav-bar-title-after`
-  - `nav-bar-content-before`
-  - `nav-bar-content-after`
-  - `nav-screen-content-before`
-  - `nav-screen-content-after`
+  - `nav-bar-title-bevor`
+  - `nav-bar-title-nach`
+  - `nav-bar-content-bevor`
+  - `nav-bar-content-nach`
+  - `nav-screen-content-bevor`
+  - `nav-screen-content-nach`
 
 ## Using View Transitions API
 
 ### On Appearance Toggle
 
-You can extend the default theme to provide a custom transition when the color mode is toggled. An example:
+Du kannst extend the default theme to provide a custom transition when the color mode is toggled. An example:
 
 <<< @/components/AppearanceToggleTransition.vue [.vitepress/theme/Layout.vue]
 
@@ -269,7 +269,7 @@ Result (**warning!**: flashing colors, sudden movements, bright lights):
 
 </details>
 
-Refer [Chrome Docs](https://developer.chrome.com/docs/web-platform/view-transitions/) from more details on view transitions.
+Refer [Chrome Docs](https://developer.chrome.com/docs/web-platform/view-transitions/) von more details on view transitions.
 
 ### On Route Change
 
@@ -277,7 +277,7 @@ Coming soon.
 
 ## Overriding Internal Components
 
-You can use Vite's [aliases](https://vite.dev/config/shared-options.html#resolve-alias) to replace default theme components with your custom ones:
+Du kannst use Vite's [aliases](https://vite.dev/config/shared-options.html#resolve-alias) to replace default theme components mit your custom ones:
 
 ```ts
 import { fileURLToPath, URL } from 'node:url'
@@ -299,4 +299,4 @@ export default defineConfig({
 })
 ```
 
-To know the exact name of the component refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/theme-default/components). Since the components are internal, there is a slight chance their name is updated between minor releases.
+To know the exact name of the component refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/theme-default/components). Since the components are internal, there is a slight chance their name is updated zwischen minor releases.

From 2d7c001601191e4b59dadbaa3588ce832694c307 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:22 +0200
Subject: [PATCH 049/199] docs(de): translate guide text

---
 docs/de/guide/frontmatter.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
index e8dd329a3..be1e481d2 100644
--- a/docs/de/guide/frontmatter.md
+++ b/docs/de/guide/frontmatter.md
@@ -1,12 +1,12 @@
 ---
-description: Learn how to use YAML frontmatter in VitePress Markdown files to control page-level metadata and behavior.
+description: Erfahre how to use YAML frontmatter in VitePress Markdown files to control page-level metadata and behavior.
 ---
 
 # Frontmatter
 
-## Usage
+## Verwendung
 
-VitePress supports YAML frontmatter in all Markdown files, parsing them with [gray-matter](https://github.com/jonschlinkert/gray-matter). The frontmatter must be at the top of the Markdown file (before any elements including `<script>` tags), and must take the form of valid YAML set between triple-dashed lines. Example:
+VitePress unterstützt YAML frontmatter in all Markdown files, parsing them mit [gray-matter](https://github.com/jonschlinkert/gray-matter). The frontmatter must be at the top of the Markdown file (bevor any elements including `<script>` tags), and must take the form of valid YAML set zwischen triple-dashed lines. Beispiel:
 
 ```md
 ---
@@ -15,9 +15,9 @@ editLink: true
 ---
 ```
 
-Many site or default theme config options have corresponding options in frontmatter. You can use frontmatter to override specific behavior for the current page only. For details, see [Frontmatter Config Reference](../reference/frontmatter-config).
+Many site or default theme config options have corresponding options in frontmatter. Du kannst use frontmatter to override specific behavior for the current page only. For details, see [Frontmatter Config Referenz](../reference/frontmatter-config).
 
-You can also define custom frontmatter data of your own, to be used in dynamic Vue expressions on the page.
+Du kannst also define custom frontmatter data of your own, to be verwendet in dynamic Vue expressions on the page.
 
 ## Accessing Frontmatter Data
 
@@ -36,13 +36,13 @@ editLink: true
 Guide content
 ```
 
-Property accesses like `{{ $frontmatter.title }}` are resolved while the Markdown is rendered, so the value also ends up in the local search index, in [content loader](./data-loading#createcontentloader) output, in heading anchors - the heading above gets `id="docs-with-vitepress"` - and in link targets written without spaces around the expression, like `[text]({{$frontmatter.link}})`. Other expressions are evaluated by Vue at runtime as usual, and wrapping an expression in [`v-pre`](./using-vue#escaping) shows it literally.
+Property accesses like `{{ $frontmatter.title }}` are resolved while the Markdown is rendered, so the value also ends up in the local search index, in [content loader](./data-loading#createcontentloader) output, in heading anchors - the heading above gets `id="docs-mit-vitepress"` - and in link targets written ohne spaces around the expression, like `[text]({{$frontmatter.link}})`. Other expressions are evaluated by Vue at runtime as usual, and wrapping an expression in [`v-pre`](./Verwendung-vue#escaping) shows it literally.
 
-You can also access current page's frontmatter data in `<script setup>` with the [`useData()`](../reference/runtime-api#usedata) helper.
+Du kannst also access current page's frontmatter data in `<script setup>` mit the [`useData()`](../reference/runtime-api#usedata) helper.
 
 ## Alternative Frontmatter Formats
 
-VitePress also supports JSON frontmatter syntax, starting and ending in curly braces:
+VitePress also unterstützt JSON frontmatter syntax, starting and ending in curly braces:
 
 ```json
 ---

From 4d6601ed60b27cf5ab36bf8d0195f29f9a06d966 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:24 +0200
Subject: [PATCH 050/199] docs(de): translate guide text

---
 docs/de/guide/getting-started.md | 68 ++++++++++++++++----------------
 1 file changed, 34 insertions(+), 34 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index a181192d0..d42f83d2c 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -1,23 +1,23 @@
 ---
-description: Get up and running with VitePress. Learn how to install, scaffold, and start developing your documentation site.
+description: Get up and running mit VitePress. Erfahre how to install, scaffold, and start developing your documentation site.
 ---
 
-# Getting Started
+# Erste Schritte
 
-## Try It Online
+## Online ausprobieren
 
-You can try VitePress directly in your browser on [StackBlitz](https://vitepress.new).
+Du kannst try VitePress directly in your browser on [StackBlitz](https://vitepress.new).
 
 ## Installation
 
-### Prerequisites
+### Voraussetzungen
 
 - [Node.js](https://nodejs.org/) version 22 or higher.
 - Terminal for accessing VitePress via its command line interface (CLI).
-- Text Editor with [Markdown](https://en.wikipedia.org/wiki/Markdown) syntax support.
-  - [VSCode](https://code.visualstudio.com/) is recommended, along with the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar).
+- Text Editor mit [Markdown](https://en.wikipedia.org/wiki/Markdown) syntax Unterstützung.
+  - [VSCode](https://code.visualstudio.com/) is recommended, along mit the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar).
 
-VitePress can be used on its own, or be installed into an existing project. In both cases, you can install it with:
+VitePress can be verwendet on its own, or be installed in an existing project. In both cases, you can install it mit:
 
 ::: code-group
 
@@ -45,13 +45,13 @@ $ deno add -D vitepress@next
 
 ::: tip NOTE
 
-VitePress is an ESM-only package. Don't use `require()` to import it, and make sure your nearest `package.json` contains `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Refer to [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) for more details. Also, inside async CJS contexts, you can use `await import('vitepress')` instead.
+VitePress is an ESM-only package. Don't use `require()` to import it, and make sure your nearest `package.json` contains `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Refer to [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) for more details. Also, innerhalb async CJS contexts, you can use `await import('vitepress')` instead.
 
 :::
 
-### Setup Wizard
+### Einrichtungsassistent
 
-VitePress ships with a command line setup wizard that will help you scaffold a basic project. After installation, start the wizard by running:
+VitePress ships mit a command line setup wizard that will help you scaffold a basic project. After installation, start the wizard by running:
 
 ::: code-group
 
@@ -73,17 +73,17 @@ $ bun vitepress init
 
 :::
 
-You will be greeted with a few simple questions:
+You will be greeted mit a few simple questions:
 
 <<< @/snippets/init.ansi
 
 ::: tip Vue as Peer Dependency
-If you intend to perform customization that uses Vue components or APIs, you should also explicitly install `vue` as a dependency.
+Wenn du intend to perform customization that verwendet Vue components or APIs, you should also explicitly install `vue` as a dependency.
 :::
 
-## File Structure
+## Dateistruktur
 
-If you are building a standalone VitePress site, you can scaffold the site in your current directory (`./`). However, if you are installing VitePress in an existing project alongside other source code, it is recommended to scaffold the site in a nested directory (e.g. `./docs`) so that it is separate from the rest of the project.
+Wenn du are building a standalone VitePress site, you can scaffold the site in your current directory (`./`). However, if you are installing VitePress in an existing project alongside other source code, it is recommended to scaffold the site in a nested directory (e.g. `./docs`) so that it is separate von the rest of the project.
 
 Assuming you chose to scaffold the VitePress project in `./docs`, the generated file structure should look like this:
 
@@ -101,12 +101,12 @@ Assuming you chose to scaffold the VitePress project in `./docs`, the generated
 The `docs` directory is considered the **project root** of the VitePress site. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
 
 ::: tip
-By default, VitePress stores its dev server cache in `.vitepress/cache`, and the production build output in `.vitepress/dist`. If using Git, you should add them to your `.gitignore` file. These locations can also be [configured](../reference/site-config#outdir).
+Standardmäßig, VitePress stores its dev server cache in `.vitepress/cache`, and the production build output in `.vitepress/dist`. If Verwendung Git, you should add them to your `.gitignore` file. These locations can also be [konfiguriert](../reference/site-config#outdir).
 :::
 
-### The Config File
+### Die Konfigurationsdatei
 
-The config file (`.vitepress/config.js`) allows you to customize various aspects of your VitePress site, with the most basic options being the title and description of the site:
+The config file (`.vitepress/config.js`) ermöglicht you to customize various aspects of your VitePress site, mit the most basic options being the title and description of the site:
 
 ```js [.vitepress/config.js]
 export default {
@@ -120,19 +120,19 @@ export default {
 }
 ```
 
-You can also configure the behavior of the theme via the `themeConfig` option. Consult the [Config Reference](../reference/site-config) for full details on all config options.
+Du kannst also configure the behavior of the theme via the `themeConfig` option. Consult the [Config Referenz](../reference/site-config) for full details on all config options.
 
-### Source Files
+### Quelldateien
 
-Markdown files outside the `.vitepress` directory are considered **source files**.
+Markdown files außerhalb the `.vitepress` directory are considered **source files**.
 
-VitePress uses **file-based routing**: each `.md` file is compiled into a corresponding `.html` file with the same path. For example, `index.md` will be compiled into `index.html`, and can be visited at the root path `/` of the resulting VitePress site.
+VitePress verwendet **file-based routing**: each `.md` file is compiled in a corresponding `.html` file mit the same path. Zum Beispiel, `index.md` will be compiled in `index.html`, and can be visited at the root path `/` of the resulting VitePress site.
 
-VitePress also provides the ability to generate clean URLs, rewrite paths, and dynamically generate pages. These will be covered in the [Routing Guide](./routing).
+VitePress also stellt bereit the ability to generate clean URLs, rewrite paths, and dynamically generate pages. These will be covered in the [Routing Anleitung](./routing).
 
-## Up and Running
+## Loslegen
 
-The tool should have also injected the following npm scripts to your `package.json` if you allowed it to do so during the setup process:
+The tool should have also injected the following npm scripts to your `package.json` if you allowed it to do so während the setup process:
 
 ```json [package.json]
 {
@@ -146,7 +146,7 @@ The tool should have also injected the following npm scripts to your `package.js
 }
 ```
 
-The `docs:dev` script will start a local dev server with instant hot updates. Run it with the following command:
+The `docs:dev` script will start a local dev server mit instant hot updates. Run it mit the following command:
 
 ::: code-group
 
@@ -168,7 +168,7 @@ $ bun run docs:dev
 
 :::
 
-Instead of npm scripts, you can also invoke VitePress directly with:
+Instead of npm scripts, you can also invoke VitePress directly mit:
 
 ::: code-group
 
@@ -190,18 +190,18 @@ $ bun vitepress dev docs
 
 :::
 
-More command line usage is documented in the [CLI Reference](../reference/cli).
+More command line usage is documented in the [CLI Referenz](../reference/cli).
 
 The dev server should be running at `http://localhost:5173`. Visit the URL in your browser to see your new site in action!
 
-## What's Next?
+## What's Weiter?
 
-- To better understand how markdown files are mapped to generated HTML, proceed to the [Routing Guide](./routing).
+- To better understand how markdown files are mapped to generated HTML, proceed to the [Routing Anleitung](./routing).
 
-- To discover more about what you can do on the page, such as writing markdown content or using Vue Components, refer to the "Writing" section of the guide. A great place to start would be to learn about [Markdown Extensions](./markdown).
+- To discover more about what you can do on the page, such as writing markdown content or Verwendung Vue Components, refer to the "Schreiben" section of the guide. A great place to start would be to learn about [Markdown Extensions](./markdown).
 
-- To explore the features provided by the default documentation theme, check out the [Default Theme Config Reference](../reference/default-theme-config).
+- To explore the features provided by the default documentation theme, check out the [Standard-Theme Config Referenz](../reference/default-theme-config).
 
-- If you want to further customize the appearance of your site, explore how to either [Extend the Default Theme](./extending-default-theme) or [Build a Custom Theme](./custom-theme).
+- Wenn du want to further customize the appearance of your site, explore how to either [Extend the Standard-Theme](./extending-default-theme) or [Build a Eigenes Theme](./custom-theme).
 
-- Once your documentation site takes shape, make sure to read the [Deployment Guide](./deploy).
+- Once your documentation site takes shape, make sure to read the [Bereitstellung Anleitung](./deploy).

From 56db08dedb325ce9ace5cdc4c11dd20a704ea086 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:26 +0200
Subject: [PATCH 051/199] docs(de): translate guide text

---
 docs/de/guide/i18n.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/i18n.md b/docs/de/guide/i18n.md
index ff0bcff08..1ad6db3af 100644
--- a/docs/de/guide/i18n.md
+++ b/docs/de/guide/i18n.md
@@ -1,8 +1,8 @@
 ---
-description: Set up internationalization (i18n) in VitePress to support multiple languages for your site.
+description: Set up internationalization (i18n) in VitePress to Unterstützung multiple languages for your site.
 ---
 
-# Internationalization
+# Internationalisierung
 
 To use the built-in i18n features, one needs to create a directory structure as follows:
 
@@ -53,13 +53,13 @@ interface LocaleSpecificConfig<ThemeConfig = any> {
 }
 ```
 
-Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-theme.d.ts) interface for details on customizing the placeholder texts of the default theme. Don't override `themeConfig.algolia` or `themeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-theme-search#algolia-search-i18n) for using multilingual search.
+Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-theme.d.ts) interface for details on customizing the placeholder texts of the default theme. Don't override `themeConfig.algolia` or `themeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-theme-search#algolia-search-i18n) for Verwendung multilingual search.
 
-**Pro tip:** Config file can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a configuration file per locale and then merge and export them from `index.ts`.
+**Pro tip:** Config file can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a Konfiguration file per locale and then merge and export them von `index.ts`.
 
 ## Per-locale Markdown Strings
 
-Strings baked into pages by the markdown renderer - the default titles of [custom containers](./markdown#custom-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale with the `markdown` key of a locale entry:
+Strings baked in pages by the markdown renderer - the default titles of [custom containers](./markdown#custom-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale mit the `markdown` key of a locale entry:
 
 ```ts [docs/.vitepress/config.ts]
 import { defineConfig } from 'vitepress'
@@ -86,7 +86,7 @@ export default defineConfig({
 })
 ```
 
-Values fall back to the root-level `markdown` options when a locale leaves them unset. Locale entries can only override the titles of containers registered at the root level - registering new containers per locale is not supported. Also note that since the markdown renderer is created once for the whole site, these can only be declared in the main config file, not in additional configs.
+Values fall back to the root-level `markdown` options when a locale leaves them unset. Locale entries can only override the titles of containers registered at the root level - registering new containers per locale is not supported. Also note that since the markdown renderer is erstellt once for the whole site, these can only be declared in the main config file, not in additional configs.
 
 ## Separate directory for each locale
 
@@ -102,7 +102,7 @@ docs/
    ├─ foo.md
 ```
 
-However, VitePress won't redirect `/` to `/en/` by default. You'll need to configure your server for that. For example, on Netlify, you can add a `docs/public/_redirects` file like this:
+However, VitePress won't redirect `/` to `/en/` by default. You'll need to configure your server for that. Zum Beispiel, on Netlify, you can add a `docs/public/_redirects` file like this:
 
 ```
 /*  /es/:splat  302  Language=es
@@ -110,7 +110,7 @@ However, VitePress won't redirect `/` to `/en/` by default. You'll need to confi
 /*  /en/:splat  302
 ```
 
-**Pro tip:** If using the above approach, you can use `nf_lang` cookie to persist user's language choice:
+**Pro tip:** If Verwendung the above approach, you can use `nf_lang` cookie to persist user's language choice:
 
 ```ts [docs/.vitepress/theme/index.ts]
 import DefaultTheme from 'vitepress/theme'
@@ -143,7 +143,7 @@ watchEffect(() => {
 
 ## RTL Support
 
-For right-to-left languages, set `dir: 'rtl'` in the config. The default theme is laid out with [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_values), so the layout, the navigation and directional icons follow the document direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
+For right-to-left languages, set `dir: 'rtl'` in the config. The default theme is laid out mit [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_values), so the layout, the navigation and directional icons follow the dokumentieren direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
 
 ```ts [docs/.vitepress/config.ts]
 export default {
@@ -152,7 +152,7 @@ export default {
 }
 ```
 
-For a multilingual site, set `dir` per locale in `locales`. It can also be overridden for a single page with the [`dir`](../reference/frontmatter-config#dir) frontmatter option. Code blocks always stay left-to-right.
+For a multilingual site, set `dir` per locale in `locales`. It can also be overridden for a single page mit the [`dir`](../reference/frontmatter-config#dir) frontmatter option. Code blocks always stay left-to-right.
 
 When adding your own styles, prefer logical properties such as `margin-inline-start` over `margin-left`, and mirror your own directional icons in right-to-left layouts:
 

From f9e4777f39fa42ac6ca41ddb33c2ee8c0ba036f0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:32 +0200
Subject: [PATCH 052/199] docs(de): translate remaining guide text

---
 docs/de/guide/markdown.md | 130 +++++++++++++++++++-------------------
 1 file changed, 65 insertions(+), 65 deletions(-)

diff --git a/docs/de/guide/markdown.md b/docs/de/guide/markdown.md
index 574e9626a..36e10117e 100644
--- a/docs/de/guide/markdown.md
+++ b/docs/de/guide/markdown.md
@@ -3,23 +3,23 @@ description: VitePress built-in Markdown extensions including custom containers,
 outline: deep
 ---
 
-# Markdown Extensions
+# Markdown-Erweiterungen
 
-VitePress comes with built in Markdown Extensions.
+VitePress comes with built in Markdown-Erweiterungen.
 
 ## Header Anchors
 
-Headers automatically get anchor links applied. Rendering of anchors can be configured using the `markdown.anchor` option.
+Headers automatisch get anchor links applied. Rendering of anchors can be configured Verwendung the `markdown.anchor` option.
 
-### Custom anchors
+### Eigenes anchors
 
-To specify a custom anchor tag for a heading instead of using the auto-generated one, add a suffix to the heading:
+To specify a custom anchor tag for a heading instead of Verwendung the auto-generated one, add a suffix to the heading:
 
 ```
 # Using custom anchors {#my-anchor}
 ```
 
-This allows you to link to the heading as `#my-anchor` instead of the default `#using-custom-anchors`.
+Dies ermöglicht you to link to the heading as `#my-anchor` instead of the default `#Verwendung-custom-anchors`.
 
 ## Links
 
@@ -27,9 +27,9 @@ Both internal and external links get special treatment.
 
 ### Internal Links
 
-Internal links are converted to router links for SPA navigation. Also, every `index.md` contained in each sub-directory will automatically be converted to `index.html`, with corresponding URL `/`.
+Internal links are converted to router links for SPA navigation. Also, every `index.md` contained in each sub-directory will automatisch be converted to `index.html`, with corresponding URL `/`.
 
-For example, given the following directory structure:
+Zum Beispiel, given the following directory structure:
 
 ```
 .
@@ -55,13 +55,13 @@ And providing you are in `foo/one.md`:
 [bar - four](../bar/four.html) <!-- or you can append .html -->
 ```
 
-### Page Suffix
+### Seite Suffix
 
-Pages and internal links get generated with the `.html` suffix by default.
+Seiten and internal links get generated with the `.html` suffix by default.
 
 ### External Links
 
-Outbound links automatically get `target="_blank" rel="noreferrer"`:
+Outbound links automatisch get `target="_blank" rel="noreferrer"`:
 
 - [vuejs.org](https://vuejs.org)
 - [VitePress on GitHub](https://github.com/vuejs/vitepress)
@@ -77,7 +77,7 @@ lang: en-US
 ---
 ```
 
-This data will be available to the rest of the page, along with all custom and theming components.
+This Daten will be verfügbar to the rest of the page, along with all custom and theming Komponenten.
 
 For more details, see [Frontmatter](../reference/frontmatter-config).
 
@@ -93,7 +93,7 @@ For more details, see [Frontmatter](../reference/frontmatter-config).
 | zebra stripes |   are neat    |    $1 |
 ```
 
-**Output**
+**Ausgabe**
 
 | Tables        |      Are      |   Cool |
 | ------------- | :-----------: | -----: |
@@ -110,7 +110,7 @@ For more details, see [Frontmatter](../reference/frontmatter-config).
 - [x] Update the website
 ```
 
-**Output**
+**Ausgabe**
 
 - [ ] Write the press release
 - [x] Update the website
@@ -125,9 +125,9 @@ Footnotes are supported[^1], including inline ones^[This is an inline footnote.]
 [^1]: Definitions can contain **markdown** and are rendered at the end of the page.
 ```
 
-**Output**
+**Ausgabe**
 
-Footnotes are supported[^1], including inline ones^[This is an inline footnote.].
+Footnotes are supported[^1], including inline ones^[Dies ist an inline footnote.].
 
 [^1]: Definitions can contain **markdown** and are rendered at the end of the page.
 
@@ -139,11 +139,11 @@ Footnotes are supported[^1], including inline ones^[This is an inline footnote.]
 :tada: :100:
 ```
 
-**Output**
+**Ausgabe**
 
 :tada: :100:
 
-A [list of all emojis](https://github.com/mdit-plugins/mdit-plugins/blob/main/packages/plugin-emoji/src/data/full.ts) is available.
+A [list of all emojis](https://github.com/mdit-plugins/mdit-plugins/blob/main/packages/plugin-emoji/src/Daten/full.ts) is verfügbar.
 
 ## Table of Contents
 
@@ -153,15 +153,15 @@ A [list of all emojis](https://github.com/mdit-plugins/mdit-plugins/blob/main/pa
 [[toc]]
 ```
 
-**Output**
+**Ausgabe**
 
 [[toc]]
 
-Rendering of the TOC can be configured using the `markdown.toc` option.
+Rendering of the TOC can be configured Verwendung the `markdown.toc` option.
 
-## Custom Containers
+## Eigenes Containers
 
-Custom containers can be defined by their types, titles, and contents.
+Eigenes containers can be defined by their types, titles, and contents.
 
 ### Default Title
 
@@ -189,29 +189,29 @@ This is a details block.
 :::
 ```
 
-**Output**
+**Ausgabe**
 
 ::: info
-This is an info box.
+Dies ist an info box.
 :::
 
 ::: tip
-This is a tip.
+Dies ist a tip.
 :::
 
 ::: warning
-This is a warning.
+Dies ist a warning.
 :::
 
 ::: danger
-This is a dangerous warning.
+Dies ist a dangerous warning.
 :::
 
 ::: details
-This is a details block.
+Dies ist a details block.
 :::
 
-### Custom Title
+### Eigenes Title
 
 You may set custom title by appending the text right after the "type" of the container.
 
@@ -229,7 +229,7 @@ console.log('Hello, VitePress!')
 :::
 ````
 
-**Output**
+**Ausgabe**
 
 ::: danger STOP
 Danger zone, do not proceed
@@ -292,7 +292,7 @@ You have completed the walkthrough!
 > This renders the same way.
 ```
 
-New containers ship without any styling, so add some in your theme using the container name as the class. For this example, the default theme's palette already provides fitting colors:
+New containers ship without any styling, so add some in your theme Verwendung the container name as the class. For this example, the default theme's palette already stellt bereit fitting colors:
 
 ```css
 /* .vitepress/theme/custom.css */
@@ -513,8 +513,8 @@ export default {
 
 ```js{4}
 export default {
-  data () {
-    return {
+  Daten () {
+    zurückgeben {
       msg: 'Highlighted!'
     }
   }
@@ -549,8 +549,8 @@ export default { // Highlighted
 
 ```js{1,4,6-8}
 export default { // Highlighted
-  data () {
-    return {
+  Daten () {
+    zurückgeben {
       msg: `Highlighted!
       This line isn't highlighted,
       but this and the next 2 are.`,
@@ -581,8 +581,8 @@ export default {
 
 ```js
 export default {
-  data() {
-    return {
+  Daten() {
+    zurückgeben {
       msg: 'Highlighted!' // [!code highlight]
     }
   }
@@ -613,8 +613,8 @@ export default {
 
 ```js
 export default {
-  data() {
-    return {
+  Daten() {
+    zurückgeben {
       msg: 'Focused!' // [!code focus]
     }
   }
@@ -644,8 +644,8 @@ export default {
 
 ```js
 export default {
-  data () {
-    return {
+  Daten () {
+    zurückgeben {
       msg: 'Removed' // [!code --]
       msg: 'Added' // [!code ++]
     }
@@ -676,10 +676,10 @@ export default {
 
 ```js
 export default {
-  data() {
-    return {
+  Daten() {
+    zurückgeben {
       msg: 'Error', // [!code error]
-      msg: 'Warning' // [!code warning]
+      msg: 'Warnung' // [!code warning]
     }
   }
 }
@@ -729,20 +729,20 @@ const line4 = 'This is line 4'
 
 ```ts {1}
 // line-numbers is disabled by default
-const line2 = 'This is line 2'
-const line3 = 'This is line 3'
+const line2 = 'Dies ist line 2'
+const line3 = 'Dies ist line 3'
 ```
 
 ```ts:line-numbers {1}
 // line-numbers is enabled
-const line2 = 'This is line 2'
-const line3 = 'This is line 3'
+const line2 = 'Dies ist line 2'
+const line3 = 'Dies ist line 3'
 ```
 
 ```ts:line-numbers=2 {1}
 // line-numbers is enabled and start from 2
-const line3 = 'This is line 3'
-const line4 = 'This is line 4'
+const line3 = 'Dies ist line 3'
+const line4 = 'Dies ist line 4'
 ```
 
 ## Import Code Snippets
@@ -893,7 +893,7 @@ You can also [import snippets](#import-code-snippets) in code groups:
 ```md
 ::: code-group
 
-<!-- filename is used as title by default -->
+<!-- filename is verwendet as title by default -->
 
 <<< @/snippets/snippet.js
 
@@ -939,9 +939,9 @@ For example, you can include a relative markdown file using this:
 ```md
 Some getting started stuff.
 
-### Configuration
+### Konfiguration
 
-Can be created using `.foorc.json`.
+Can be erstellt Verwendung `.foorc.json`.
 ```
 
 **Equivalent code**
@@ -953,9 +953,9 @@ Can be created using `.foorc.json`.
 
 Some getting started stuff.
 
-### Configuration
+### Konfiguration
 
-Can be created using `.foorc.json`.
+Can be erstellt Verwendung `.foorc.json`.
 ```
 
 It also supports selecting a line range:
@@ -975,9 +975,9 @@ It also supports selecting a line range:
 ```md:line-numbers
 Some getting started stuff.
 
-### Configuration
+### Konfiguration
 
-Can be created using `.foorc.json`.
+Can be erstellt Verwendung `.foorc.json`.
 ```
 
 **Equivalent code**
@@ -987,9 +987,9 @@ Can be created using `.foorc.json`.
 
 ## Basics
 
-### Configuration
+### Konfiguration
 
-Can be created using `.foorc.json`.
+Can be erstellt Verwendung `.foorc.json`.
 ```
 
 The format of the selected line range can be: `{3,}`, `{,10}`, `{1,10}`
@@ -1011,11 +1011,11 @@ You can also use a [VS Code region](https://code.visualstudio.com/docs/editor/co
 
 ```md:line-numbers
 <!-- #region basic-usage -->
-## Usage Line 1
+## Verwendung Line 1
 
-## Usage Line 2
+## Verwendung Line 2
 
-## Usage Line 3
+## Verwendung Line 3
 <!-- #endregion basic-usage -->
 ```
 
@@ -1026,9 +1026,9 @@ You can also use a [VS Code region](https://code.visualstudio.com/docs/editor/co
 
 ## Basics
 
-## Usage Line 1
+## Verwendung Line 1
 
-## Usage Line 3
+## Verwendung Line 3
 ```
 
 ::: warning
@@ -1048,7 +1048,7 @@ Some more content here.
 
 ## Another Section
 
-Content outside `My Base Section`.
+Inhalt outside `My Base Section`.
 ```
 
 You can include the `My Base Section` section like this:

From fcce64e1c608eed498ffacffc6bc31ce47d9f0b6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:34 +0200
Subject: [PATCH 053/199] docs(de): translate remaining guide text

---
 docs/de/guide/mpa-mode.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/mpa-mode.md b/docs/de/guide/mpa-mode.md
index 5e0fc24cb..4f11b5ccd 100644
--- a/docs/de/guide/mpa-mode.md
+++ b/docs/de/guide/mpa-mode.md
@@ -1,16 +1,16 @@
 ---
-description: MPA (Multi-Page Application) mode in VitePress for zero-JavaScript pages with better initial performance.
+description: MPA (Multi-Seite Application) mode in VitePress for zero-JavaScript pages with better initial performance.
 ---
 
 # MPA-Modus <Badge type="warning" text="experimental" />
 
-MPA (Multi-Page Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
+MPA (Multi-Seite Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
 
 In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit tools.
 
-However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-load navigations in MPA mode will not feel as instant as in SPA mode.
+However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
 
-Also note that no-JS-by-default means you are essentially using Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To load client-side JavaScript, you will need to use the special `<script client>` tag:
+Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need to use the special `<script client>` tag:
 
 ```html
 <script client>
@@ -22,6 +22,6 @@ document.querySelector('h1').addEventListener('click', () => {
 # Hello
 ```
 
-`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme components will be bundled together, while client script for a specific page will be split for that page only.
+`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled together, while client script for a specific page will be split for that page only.
 
-Note that `<script client>` is **not evaluated as Vue component code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be used if your site requires absolutely minimal client-side interactivity.
+Beachte, dass `<script client>` is **not evaluated as Vue Komponente code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be verwendet if your site requires absolutely minimal client-side interactivity.

From c5951e5bb2af9f51c4d955b8437e634c9622c353 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:37 +0200
Subject: [PATCH 054/199] docs(de): translate remaining guide text

---
 docs/de/guide/migration-from-vitepress-0.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/migration-from-vitepress-0.md b/docs/de/guide/migration-from-vitepress-0.md
index 18268da48..86a747f9c 100644
--- a/docs/de/guide/migration-from-vitepress-0.md
+++ b/docs/de/guide/migration-from-vitepress-0.md
@@ -1,6 +1,6 @@
 # Migration von VitePress 0.x
 
-If you're coming from VitePress 0.x version, there're several breaking changes due to new features and enhancement. Please follow this guide to see how to migrate your app over to the latest VitePress.
+Wenn du're coming von VitePress 0.x version, there're several breaking changes due to new features and enhancement. Please follow this guide to see how to migrate your app over to the latest VitePress.
 
 ## App Config
 
@@ -13,11 +13,11 @@ If you're coming from VitePress 0.x version, there're several breaking changes d
   - Top level item may not contain `link` at the moment. We're planning to bring it back.
 - `repo`, `repoLabel`, `docsDir`, `docsBranch`, `editLinks`, `editLinkText` are removed in favor of more flexible api.
   - For adding GitHub link with icon to the nav, use [Social Links](../reference/default-theme-nav#navigation-links) feature.
-  - For adding "Edit this page" feature, use [Edit Link](../reference/default-theme-edit-link) feature.
+  - For adding "Edit this page" feature, use [Bearbeitungslink](../reference/default-theme-edit-link) feature.
 - `lastUpdated` option is now split into `config.lastUpdated` and `themeConfig.lastUpdated.text`.
 - `carbonAds.carbon` is changed to `carbonAds.code`.
 
 ## Frontmatter-Konfiguration
 
-- `home: true` option has changed to `layout: home`. Also, many Homepage related settings have been modified to provide additional features. See [Home Page guide](../reference/default-theme-home-page) for details.
+- `home: true` option has changed to `layout: home`. Also, many Homepage related settings have been modified to provide additional features. See [Home Seite guide](../reference/default-theme-home-page) for details.
 - `footer` option is moved to [`themeConfig.footer`](../reference/default-theme-config#footer).

From 5150bc8b7827035619361aaa97eb199e33f70071 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:39 +0200
Subject: [PATCH 055/199] docs(de): translate remaining guide text

---
 docs/de/guide/migration-from-vuepress.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/migration-from-vuepress.md b/docs/de/guide/migration-from-vuepress.md
index cfbc8f28a..da390deed 100644
--- a/docs/de/guide/migration-from-vuepress.md
+++ b/docs/de/guide/migration-from-vuepress.md
@@ -4,13 +4,13 @@
 
 ### Seitenleiste
 
-The sidebar is no longer automatically populated from frontmatter. You can [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
+The sidebar is no longer automatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
 
 ## Markdown
 
 ### Bilder
 
-Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatically when you use static image.
+Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatisch when you use static image.
 
 Hence, now you can render images without `img` tag.
 

From 2b4610adef8923dbff5e4540de8057eb45bc0876 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:41 +0200
Subject: [PATCH 056/199] docs(de): translate remaining guide text

---
 docs/de/guide/routing.md | 72 ++++++++++++++++++++--------------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 845ef04ff..b8e175a74 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -7,7 +7,7 @@ description: Understand VitePress file-based routing, dynamic routes, clean URLs
 
 ## Dateibasierte Routen
 
-VitePress uses file-based routing, which means the generated HTML pages are mapped from the directory structure of the source Markdown files. For example, given the following directory structure:
+VitePress uses file-based routing, which means the generated HTML pages are mapped from the directory structure of the source Markdown files. Zum Beispiel, given the following directory structure:
 
 ```
 .
@@ -35,9 +35,9 @@ There are two important concepts in the file structure of a VitePress project: t
 
 ### Projektverzeichnis
 
-Project root is where VitePress will try to look for the `.vitepress` special directory. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+Projekt root is where VitePress will try to look for the `.vitepress` special directory. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
 
-When you run `vitepress dev` or `vitepress build` from the command line, VitePress will use the current working directory as project root. To specify a sub-directory as root, you will need to pass the relative path to the command. For example, if your VitePress project is located in `./docs`, you should run `vitepress dev docs`:
+Wenn du run `vitepress dev` or `vitepress build` from the command line, VitePress will use the current working directory as project root. To specify a sub-directory as root, you will need to pass the relative path to the command. Zum Beispiel, if your VitePress project is located in `./docs`, you should run `vitepress dev docs`:
 
 ```
 .
@@ -52,7 +52,7 @@ When you run `vitepress dev` or `vitepress build` from the command line, VitePre
 vitepress dev docs
 ```
 
-This is going to result in the following source-to-HTML mapping:
+Dies ist going to result in the following source-to-HTML mapping:
 
 ```
 docs/index.md            -->  /index.html (accessible as /)
@@ -61,9 +61,9 @@ docs/getting-started.md  -->  /getting-started.html
 
 ### Quellverzeichnis
 
-Source directory is where your Markdown source files live. By default, it is the same as the project root. However, you can configure it via the [`srcDir`](../reference/site-config#srcdir) config option.
+Quelle directory is where your Markdown source files live. Standardmäßig, it is the same as the project root. However, you can configure it via the [`srcDir`](../reference/site-config#srcdir) config option.
 
-The `srcDir` option is resolved relative to project root. For example, with `srcDir: 'src'`, your file structure will look like this:
+The `srcDir` option is resolved relative to project root. Zum Beispiel, with `srcDir: 'src'`, your file structure will look like this:
 
 ```
 .                          # project root
@@ -82,7 +82,7 @@ src/getting-started.md  -->  /getting-started.html
 
 ## Zwischen Seiten verlinken
 
-You can use both absolute and relative paths when linking between pages. Note that although both `.md` and `.html` extensions will work, the best practice is to omit file extensions so that VitePress can generate the final URLs based on your config.
+Du kannst use both absolute and relative paths when linking between pages. Beachte, dass although both `.md` and `.html` extensions will work, the best practice is to omit file extensions so that VitePress can generate the final URLs based on your config.
 
 ```md
 <!-- Do -->
@@ -94,11 +94,11 @@ You can use both absolute and relative paths when linking between pages. Note th
 [Getting Started](./getting-started.html)
 ```
 
-Learn more about linking to assets such images in [Asset Handling](./asset-handling).
+Mehr erfahren about linking to assets such images in [Asset Handling](./asset-handling).
 
 ### Auf Nicht-VitePress-Seiten verlinken
 
-If you want to link to a page in your site that is not generated by VitePress, you'll either need to use the full URL (opens in a new tab) or explicitly specify the target:
+Wenn du want to link to a page in your site that is not generated by VitePress, you'll either need to use the full URL (opens in a new tab) or explicitly specify the target:
 
 **Input**
 
@@ -106,13 +106,13 @@ If you want to link to a page in your site that is not generated by VitePress, y
 [Link to pure.html](/pure.html){target="_self"}
 ```
 
-**Output**
+**Ausgabe**
 
 [Link to pure.html](/pure.html){target="_self"}
 
 ::: tip Note
 
-In Markdown links, the `base` is automatically prepended to the URL. This means that if you want to link to a page outside of your base, you'd need something like `../../pure.html` in the link (resolved relative to the current page by the browser).
+In Markdown links, the `base` is automatisch prepended to the URL. Das bedeutet that if you want to link to a page outside of your base, you'd need something like `../../pure.html` in the link (resolved relative to the current page by the browser).
 
 Alternatively, you can directly use the anchor tag syntax:
 
@@ -125,17 +125,17 @@ Alternatively, you can directly use the anchor tag syntax:
 ## Generating Clean URLs
 
 ::: warning Server Support Required
-To serve clean URLs with VitePress, server-side support is required.
+To serve clean URLs with VitePress, server-side support is erforderlich.
 :::
 
-By default, VitePress resolves inbound links to URLs ending with `.html`. However, some users may prefer "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
+Standardmäßig, VitePress resolves inbound links to URLs ending with `.html`. However, some users may prefer "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
 
-Some servers or hosting platforms (for example Netlify, Vercel, GitHub Pages) provide the ability to map a URL like `/foo` to `/foo.html` if it exists, without a redirect:
+Some servers or hosting platforms (for example Netlify, Vercel, GitHub Seiten) provide the ability to map a URL like `/foo` to `/foo.html` if it exists, without a redirect:
 
-- Netlify and GitHub Pages support this by default.
+- Netlify and GitHub Seiten support this by default.
 - Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-If this feature is available to you, you can then also enable VitePress' own [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
+If this feature is verfügbar to you, you can then also enable VitePress' own [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
 
 - Inbound links between pages are generated without the `.html` extension.
 - If current path ends with `.html`, the router will perform a client-side redirect to the extension-less path.
@@ -153,7 +153,7 @@ If, however, you cannot configure your server with such support, you will have t
 
 ## Route Rewrites
 
-You can customize the mapping between the source directory structure and the generated pages. It's useful when you have a complex project structure. For example, let's say you have a monorepo with multiple packages, and would like to place documentations along with the source files like this:
+Du kannst customize the mapping between the source directory structure and the generated pages. It's useful when you have a complex project structure. Zum Beispiel, let's say you have a monorepo with multiple packages, and would like to place documentations along with the source files like this:
 
 ```
 .
@@ -177,7 +177,7 @@ packages/pkg-b/src/index.md  -->  /pkg-b/index.html
 packages/pkg-b/src/bar.md    -->  /pkg-b/bar.html
 ```
 
-You can achieve this by configuring the [`rewrites`](../reference/site-config#rewrites) option like this:
+Du kannst achieve this by configuring the [`rewrites`](../reference/site-config#rewrites) option like this:
 
 ```ts [.vitepress/config.js]
 export default {
@@ -190,7 +190,7 @@ export default {
 }
 ```
 
-The `rewrites` option also supports dynamic route parameters. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
+The `rewrites` option also unterstützt dynamic route parameters. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
 
 ```ts
 export default {
@@ -200,9 +200,9 @@ export default {
 }
 ```
 
-The rewrite paths are compiled using the `path-to-regexp` package - consult [its documentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
+The rewrite paths are compiled Verwendung the `path-to-regexp` package - consult [its documentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
 
-`rewrites` can also be a function that receives the original path and returns the new path:
+`rewrites` can also be a function that receives the original path and gibt zurück the new path:
 
 ```ts
 export default {
@@ -214,7 +214,7 @@ export default {
 
 ::: warning Relative Links with Rewrites
 
-When rewrites are enabled, **relative links should be based on the rewritten paths**. For example, in order to create a relative link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
+When rewrites are enabled, **relative links should be based on the rewritten paths**. Zum Beispiel, in order to erstellen a relative link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
 
 ```md
 [Link to PKG B](../pkg-b/pkg-b-code)
@@ -223,7 +223,7 @@ When rewrites are enabled, **relative links should be based on the rewritten pat
 
 ## Dynamische Routen
 
-You can generate many pages using a single Markdown file and dynamic data. For example, you can create a `packages/[pkg].md` file that generates a corresponding page for every package in a project. Here, the `[pkg]` segment is a route **parameter** that differentiates each page from the others.
+Du kannst generate many pages Verwendung a single Markdown file and dynamic Daten. Zum Beispiel, you can erstellen a `packages/[pkg].md` file that generates a corresponding page for every package in a project. Here, the `[pkg]` segment is a route **parameter** that differentiates each page from the others.
 
 ### Pfad-Loader-Datei
 
@@ -236,7 +236,7 @@ Since VitePress is a static site generator, the possible page paths must be dete
    └─ [pkg].paths.js   # route paths loader
 ```
 
-The paths loader should provide an object with a `paths` method as its default export. The `paths` method should return an array of objects with a `params` property. Each of these objects will generate a corresponding page.
+The paths loader should provide an object with a `paths` method as its default export. The `paths` method should zurückgeben an array of objects with a `params` property. Each of these objects will generate a corresponding page.
 
 Given the following `paths` array:
 
@@ -263,7 +263,7 @@ The generated HTML pages will be:
 
 ### Type-safe loader with `defineRoutes`
 
-If you are using TypeScript, you can wrap the loader with `defineRoutes` from `vitepress` to get type hints for route hooks such as `paths`, `watch`, and `transformPageData`:
+Wenn du are Verwendung TypeScript, you can wrap the loader with `defineRoutes` from `vitepress` to get type hints for route hooks such as `paths`, `watch`, and `transformPageData`:
 
 ```ts
 // packages/[pkg].paths.ts
@@ -289,7 +289,7 @@ export default defineRoutes({
 
 A dynamic route can contain multiple params:
 
-**File Structure**
+**Datei Structure**
 
 ```
 .
@@ -311,7 +311,7 @@ export default {
 }
 ```
 
-**Output**
+**Ausgabe**
 
 ```
 .
@@ -324,7 +324,7 @@ export default {
 
 ### Pfade dynamisch erzeugen
 
-The paths loader module is run in Node.js and only executed during build time. You can dynamically generate the paths array using any data, either local or remote.
+The paths loader module is run in Node.js and only executed during build time. Du kannst dynamically generate the paths array Verwendung any Daten, either local or remote.
 
 Generating paths from local files:
 
@@ -342,7 +342,7 @@ export default {
 }
 ```
 
-Generating paths from remote data:
+Generating paths from remote Daten:
 
 ```js
 export default {
@@ -361,9 +361,9 @@ export default {
 }
 ```
 
-### Watching Template and Data Files
+### Watching Template and Data Dateien
 
-When generating page content from templates or external data sources, you can use the watch option to automatically rebuild pages when those files change during development:
+When generating page content from Vorlagen or external Daten sources, you can use the watch option to automatisch rebuild pages when those files change during development:
 
 ```js
 // posts/[slug].paths.js
@@ -394,7 +394,7 @@ export default {
 }
 ```
 
-The `watch` option works the same way as in [data loaders](./data-loading#data-from-local-files):
+The `watch` option works the same way as in [Daten loaders](./Daten-loading#Daten-from-local-files):
 
 - Accepts [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
 - Patterns are relative to the `.paths.js` file itself
@@ -403,14 +403,14 @@ The `watch` option works the same way as in [data loaders](./data-loading#data-f
 
 ### Auf Parameter in Seiten zugreifen
 
-You can use the params to pass additional data to each page. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
+Du kannst use the params to pass additional Daten to each page. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
 
 ```md
 - package name: {{ $params.pkg }}
 - version: {{ $params.version }}
 ```
 
-You can also access the current page's params via the [`useData`](../reference/runtime-api#usedata) runtime API. This is available in both Markdown files and Vue components:
+Du kannst also access the current page's params via the [`useData`](../reference/runtime-api#usedata) runtime API. Dies ist verfügbar in both Markdown files and Vue Komponenten:
 
 ```vue
 <script setup>
@@ -425,9 +425,9 @@ console.log(params.value)
 
 ### Rohinhalt rendern
 
-Params passed to the page will be serialized in the client JavaScript payload, so you should avoid passing heavy data in params, for example raw Markdown or HTML content fetched from a remote CMS.
+Params passed to the page will be serialized in the client JavaScript payload, so you should avoid passing heavy Daten in params, for example raw Markdown or HTML content fetched from a remote CMS.
 
-Instead, you can pass such content to each page using the `content` property on each path object:
+Instead, you can pass such content to each page Verwendung the `content` property on each path object:
 
 ```js
 export default {

From 55ead12c3fbd50842475ba409092eb991a3d11cf Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:44 +0200
Subject: [PATCH 057/199] docs(de): translate remaining guide text

---
 docs/de/guide/sitemap-generation.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/sitemap-generation.md b/docs/de/guide/sitemap-generation.md
index 5bef11fa7..47846642e 100644
--- a/docs/de/guide/sitemap-generation.md
+++ b/docs/de/guide/sitemap-generation.md
@@ -18,7 +18,7 @@ To have `<lastmod>` tags in your `sitemap.xml`, you can enable the [`lastUpdated
 
 ## Optionen
 
-Sitemap support is powered by the [`sitemap`](https://www.npmjs.com/package/sitemap) module. You can pass any options supported by it to the `sitemap` option in your config file. These will be passed directly to the `SitemapStream` constructor. Refer to the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for more details. Example:
+Sitemap support is powered by the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it to the `sitemap` option in your config file. These will be passed directly to the `SitemapStream` constructor. Refer to the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for more details. Beispiel:
 
 ```ts
 export default {
@@ -29,7 +29,7 @@ export default {
 }
 ```
 
-If you're using `base` in your config, you should append it to the `hostname` option:
+Wenn du're Verwendung `base` in your config, you should append it to the `hostname` option:
 
 ```ts
 export default {
@@ -42,7 +42,7 @@ export default {
 
 ## `transformItems` Hook
 
-You can use the `sitemap.transformItems` hook to modify the sitemap items before they are written to the `sitemap.xml` file. This hook is called with an array of sitemap items and expects an array of sitemap items to be returned. Example:
+Du kannst use the `sitemap.transformItems` hook to modify the sitemap items before they are written to the `sitemap.xml` file. This hook is genannt with an array of sitemap items and expects an array of sitemap items to be returned. Beispiel:
 
 ```ts
 export default {

From 0004b270687e5e306527290768fca9890ab6f34f Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:46 +0200
Subject: [PATCH 058/199] docs(de): translate remaining guide text

---
 docs/de/guide/ssr-compat.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
index 879a56092..33f0e6c4d 100644
--- a/docs/de/guide/ssr-compat.md
+++ b/docs/de/guide/ssr-compat.md
@@ -1,17 +1,17 @@
 ---
 outline: deep
-description: your VitePress theme components and custom code are compatible with server-side rendering.
+description: your VitePress theme Komponenten and custom code are compatible with server-side rendering.
 ---
 
 # SSR-Kompatibilität
 
-VitePress pre-renders the app in Node.js during the production build, using Vue's Server-Side Rendering (SSR) capabilities. This means all custom code in theme components are subject to SSR Compatibility.
+VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all custom code in theme Komponenten are subject to SSR-Kompatibilität.
 
-The [SSR section in official Vue docs](https://vuejs.org/guide/scaling-up/ssr.html) provides more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is to only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue components.
+The [SSR section in official Vue docs](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is to only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue Komponenten.
 
 ## `<ClientOnly>`
 
-If you are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the built-in `<ClientOnly>` component:
+Wenn du are Verwendung or demoing Komponenten that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the built-in `<ClientOnly>` Komponente:
 
 ```md
 <ClientOnly>
@@ -21,7 +21,7 @@ If you are using or demoing components that are not SSR-friendly (for example, c
 
 ## Libraries that Access Browser API on Import
 
-Some components or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need to dynamically import them.
+Some Komponenten or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need to dynamically import them.
 
 ### Importing in Mounted Hook
 
@@ -39,7 +39,7 @@ onMounted(() => {
 
 ### Conditional Import
 
-You can also conditionally import a dependency using the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
+Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
 
 ```js
 if (!import.meta.env.SSR) {
@@ -64,7 +64,7 @@ export default {
 }
 ```
 
-If you're using TypeScript:
+Wenn du're Verwendung TypeScript:
 ```ts [.vitepress/theme/index.ts]
 import type { Theme } from 'vitepress'
 
@@ -81,7 +81,7 @@ export default {
 
 ### `defineClientComponent`
 
-VitePress provides a convenience helper for importing Vue components that access browser APIs on import.
+VitePress stellt bereit a convenience helper for importing Vue Komponenten that access browser APIs on import.
 
 ```vue
 <script setup>
@@ -97,7 +97,7 @@ const ClientComp = defineClientComponent(() => {
 </template>
 ```
 
-You can also pass props/children/slots to the target component:
+Du kannst also pass props/children/slots to the target Komponente:
 
 ```vue
 <script setup>
@@ -132,4 +132,4 @@ const ClientComp = defineClientComponent(
 </template>
 ```
 
-The target component will only be imported in the mounted hook of the wrapper component.
+The target Komponente will only be imported in the mounted hook of the wrapper Komponente.

From dd1f3c621e62b096f3676c0ea906827f70c36f98 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:48 +0200
Subject: [PATCH 059/199] docs(de): translate remaining guide text

---
 docs/de/guide/using-vue.md | 62 +++++++++++++++++++-------------------
 1 file changed, 31 insertions(+), 31 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index ef3f57085..12a3ff77a 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -1,22 +1,22 @@
 ---
-description: Vue components and dynamic templating features directly inside Markdown files in VitePress.
+description: Vue Komponenten and dynamic templating features directly inside Markdown files in VitePress.
 ---
 
 # Vue in Markdown verwenden
 
-In VitePress, each Markdown file is compiled into HTML and then processed as a [Vue Single-File Component](https://vuejs.org/guide/scaling-up/sfc.html). This means you can use any Vue features inside the Markdown, including dynamic templating, using Vue components, or arbitrary in-page Vue component logic by adding a `<script>` tag.
+In VitePress, each Markdown file is compiled into HTML and then processed as a [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
 
-It's worth noting that VitePress leverages Vue's compiler to automatically detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. In short, you only pay for the dynamic parts on any given page.
+It's worth noting that VitePress leverages Vue's compiler to automatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. In short, you only pay for the dynamic parts on any given page.
 
-::: tip SSR Compatibility
-All Vue usage needs to be SSR-compatible. See [SSR Compatibility](./ssr-compat) for details and common workarounds.
+::: tip SSR-Kompatibilität
+All Vue usage needs to be SSR-compatible. See [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
 :::
 
 ## Templating
 
 ### Interpolation
 
-Each Markdown file is first compiled into HTML and then passed on as a Vue component to the Vite process pipeline. This means you can use Vue-style interpolation in text:
+Each Markdown file is first compiled into HTML and then passed on as a Vue Komponente to the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
 
 **Input**
 
@@ -24,7 +24,7 @@ Each Markdown file is first compiled into HTML and then passed on as a Vue compo
 {{ 1 + 1 }}
 ```
 
-**Output**
+**Ausgabe**
 
 <div class="language-text"><pre><code>{{ 1 + 1 }}</code></pre></div>
 
@@ -38,13 +38,13 @@ Directives also work (note that by design, raw HTML is also valid in Markdown):
 <span v-for="i in 3">{{ i }}</span>
 ```
 
-**Output**
+**Ausgabe**
 
 <div class="language-text"><pre><code><span v-for="i in 3">{{ i }} </span></code></pre></div>
 
 ## `<script>` and `<style>`
 
-Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<template>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
+Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
 
 ```html
 ---
@@ -72,10 +72,10 @@ The count is: {{ count }}
 ```
 
 ::: warning Avoid `<style scoped>` in Markdown
-When used in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
+When verwendet in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
 :::
 
-You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which provides access to current page's metadata:
+You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access to current page's metadata:
 
 **Input**
 
@@ -89,7 +89,7 @@ const { page } = useData()
 <pre>{{ page }}</pre>
 ```
 
-**Output**
+**Ausgabe**
 
 ```json
 {
@@ -102,11 +102,11 @@ const { page } = useData()
 
 ## Using Components
 
-You can import and use Vue components directly in Markdown files.
+Du kannst import and use Vue Komponenten directly in Markdown files.
 
 ### Importing in Markdown
 
-If a component is only used by a few pages, it's recommended to explicitly import them where they are used. This allows them to be properly code-split and only loaded when the relevant pages are shown:
+If a Komponente is only verwendet by a few pages, it's recommended to explicitly import them where they are verwendet. Dies ermöglicht them to be properly code-split and only geladen when the relevant pages are shown:
 
 ```md
 <script setup>
@@ -126,17 +126,17 @@ This is a .md using a custom component
 
 ### Registering Components Globally
 
-If a component is going to be used on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Default Theme](./extending-default-theme#registering-global-components) for an example.
+If a Komponente is going to be verwendet on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
 
 ::: warning IMPORTANT
-Make sure a custom component's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
+Stelle sicher a custom Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
 :::
 
 ### Using Components In Headers <ComponentInHeader />
 
-You can use Vue components in the headers, but note the difference between the following syntaxes:
+Du kannst use Vue Komponenten in the headers, but note the difference between the following syntaxes:
 
-| Markdown                                                | Output HTML                               | Parsed Header |
+| Markdown                                                | Ausgabe HTML                               | Parsed Header |
 | ------------------------------------------------------- | ----------------------------------------- | ------------- |
 | <pre v-pre><code> # text &lt;Tag/&gt; </code></pre>     | `<h1>text <Tag/></h1>`                    | `text`        |
 | <pre v-pre><code> # text \`&lt;Tag/&gt;\` </code></pre> | `<h1>text <code>&lt;Tag/&gt;</code></h1>` | `text <Tag/>` |
@@ -144,13 +144,13 @@ You can use Vue components in the headers, but note the difference between the f
 The HTML wrapped by `<code>` will be displayed as-is; only the HTML that is **not** wrapped will be parsed by Vue.
 
 ::: tip
-The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and used for both the sidebar and document title).
+The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and verwendet for both the sidebar and document title).
 :::
 
 
 ## Escaping
 
-You can escape Vue interpolations by wrapping them in a `<span>` or other elements with the `v-pre` directive:
+Du kannst escape Vue interpolations by wrapping them in a `<span>` or other elements with the `v-pre` directive:
 
 **Input**
 
@@ -158,7 +158,7 @@ You can escape Vue interpolations by wrapping them in a `<span>` or other elemen
 This <span v-pre>{{ will be displayed as-is }}</span>
 ```
 
-**Output**
+**Ausgabe**
 
 <div class="escape-demo">
   <p>This <span v-pre>{{ will be displayed as-is }}</span></p>
@@ -172,7 +172,7 @@ Alternatively, you can wrap the entire paragraph in a `v-pre` custom container:
 :::
 ```
 
-**Output**
+**Ausgabe**
 
 <div class="escape-demo">
 
@@ -184,7 +184,7 @@ Alternatively, you can wrap the entire paragraph in a `v-pre` custom container:
 
 ## Unescape in Code Blocks
 
-By default, all fenced code blocks are automatically wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
+Standardmäßig, all fenced code blocks are automatisch wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
 
 **Input**
 
@@ -194,13 +194,13 @@ Hello {{ 1 + 1 }}
 ```
 ````
 
-**Output**
+**Ausgabe**
 
 ```js-vue
 Hello {{ 1 + 1 }}
 ```
 
-Note that this might prevent certain tokens from being syntax highlighted properly.
+Beachte, dass this might prevent certain tokens from being syntax highlighted properly.
 
 ## Using CSS Pre-processors
 
@@ -217,7 +217,7 @@ npm install -D less
 npm install -D stylus
 ```
 
-Then you can use the following in Markdown and theme components:
+Then you can use the following in Markdown and theme Komponenten:
 
 ```vue
 <style lang="sass">
@@ -228,12 +228,12 @@ Then you can use the following in Markdown and theme components:
 
 ## Using Teleports
 
-VitePress currently has SSG support for teleports to body only. For other targets, you can wrap them inside the built-in `<ClientOnly>` component or inject the teleport markup into the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
+VitePress currently has SSG support for teleports to body only. For other targets, you can wrap them inside the built-in `<ClientOnly>` Komponente or inject the teleport markup into the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
 
 <ModalDemo />
 
 ::: details
-<<< @/components/ModalDemo.vue
+<<< @/Komponenten/ModalDemo.vue
 :::
 
 ```md
@@ -247,8 +247,8 @@ VitePress currently has SSG support for teleports to body only. For other target
 ```
 
 <script setup>
-import ModalDemo from '../../components/ModalDemo.vue'
-import ComponentInHeader from '../../components/ComponentInHeader.vue'
+import ModalDemo from '../../Komponenten/ModalDemo.vue'
+import ComponentInHeader from '../../Komponenten/ComponentInHeader.vue'
 </script>
 
 <style>
@@ -264,7 +264,7 @@ import ComponentInHeader from '../../components/ComponentInHeader.vue'
 
 <!-- Based on https://github.com/vuejs/language-tools/pull/4321 -->
 
-Vue provides IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, to enable it for `.md` files, you need to make some adjustments to the configuration files.
+Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, to enable it for `.md` files, you need to make some adjustments to the configuration files.
 
 
 1. Add `.md` pattern to the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:

From b136edb558875deca227f85dc0c6bf546e3b8645 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:54 +0200
Subject: [PATCH 060/199] docs(de): translate reference text

---
 docs/de/reference/cli.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/reference/cli.md b/docs/de/reference/cli.md
index 2c221d3fe..cc1e24d24 100644
--- a/docs/de/reference/cli.md
+++ b/docs/de/reference/cli.md
@@ -6,7 +6,7 @@ description: of VitePress CLI commands including dev, build, preview, and init.
 
 ## `vitepress dev`
 
-Start VitePress dev server using designated directory as root. Defaults to current directory. The `dev` command can also be omitted when running in current directory.
+Start VitePress dev Server using designated directory as root. Defaults to current directory. The `dev` command can also be omitted when running in current directory.
 
 ### Verwendung
 
@@ -22,16 +22,16 @@ vitepress dev [root]
 
 | Option          | Description                                                       |
 | --------------- | ----------------------------------------------------------------- |
-| `--open [path]` | Open browser on startup (`boolean \| string`)                     |
+| `--open [path]` | Open Browser on startup (`boolean \| string`)                     |
 | `--port <port>` | Specify port (`number`)                                           |
-| `--base <path>` | Public base path (default: `/`) (`string`)                        |
-| `--cors`        | Enable CORS                                                       |
+| `--base <path>` | Public base path (Standard: `/`) (`string`)                        |
+| `--cors`        | Aktivieren CORS                                                       |
 | `--strictPort`  | Exit if specified port is already in use (`boolean`)              |
 | `--force`       | Force the optimizer to ignore the cache and re-bundle (`boolean`) |
 
 ## `vitepress build`
 
-Build the VitePress site for production.
+Build the VitePress site for Produktion.
 
 ### Verwendung
 
@@ -43,16 +43,16 @@ vitepress build [root]
 
 | Option                         | Description                                                                                                         |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
-| `--mpa` (experimental)         | Build in [MPA mode](../guide/mpa-mode) without client-side hydration (`boolean`)                                    |
-| `--base <path>`                | Public base path (default: `/`) (`string`)                                                                          |
+| `--mpa` (experimental)         | Build in [MPA mode](../guide/mpa-mode) without Client-side hydration (`boolean`)                                    |
+| `--base <path>`                | Public base path (Standard: `/`) (`string`)                                                                          |
 | `--assetsBase <url>`           | URL prefix the generated assets are served from, e.g. a CDN (`string`)                                              |
-| `--target <target>`            | Transpile target (default: `"modules"`) (`string`)                                                                  |
-| `--outDir <dir>`               | Output directory relative to **cwd** (default: `<root>/.vitepress/dist`) (`string`)                                 |
-| `--assetsInlineLimit <number>` | Static asset base64 inline threshold in bytes (default: `4096`) (`number`)                                          |
+| `--target <target>`            | Transpile target (Standard: `"modules"`) (`string`)                                                                  |
+| `--outDir <dir>`               | Output directory relative to **cwd** (Standard: `<root>/.vitepress/dist`) (`string`)                                 |
+| `--assetsInlineLimit <number>` | Static asset base64 inline threshold in bytes (Standard: `4096`) (`number`)                                          |
 
 ## `vitepress preview`
 
-Locally preview the production build.
+Locally preview the Produktion build.
 
 ### Verwendung
 
@@ -64,7 +64,7 @@ vitepress preview [root]
 
 | Option          | Description                                |
 | --------------- | ------------------------------------------ |
-| `--base <path>` | Public base path (default: `/`) (`string`) |
+| `--base <path>` | Public base path (Standard: `/`) (`string`) |
 | `--assetsBase <url>` | URL prefix the generated assets are served from, e.g. a CDN (`string`) |
 | `--port <port>` | Specify port (`number`)                    |
 

From 0ff85a824bd2d021b135af2f83797aad5fdc0dd2 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:55 +0200
Subject: [PATCH 061/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-badge.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/reference/default-theme-badge.md b/docs/de/reference/default-theme-badge.md
index d1468a43f..82ec55219 100644
--- a/docs/de/reference/default-theme-badge.md
+++ b/docs/de/reference/default-theme-badge.md
@@ -4,11 +4,11 @@ description: Use the Badge component to add status labels to headers in VitePres
 
 # Badge
 
-The badge lets you add status to your headers. For example, it could be useful to specify the section's type, or supported version.
+The badge lets you add status to your headers. Zum Beispiel, it could be useful to specify the section's type, or supported version.
 
 ## Verwendung
 
-You may use the `Badge` component which is globally available.
+Du kannst use the `Badge` component which is globally verfügbar.
 
 ```html
 ### Title <Badge type="info" text="default" />
@@ -19,12 +19,12 @@ You may use the `Badge` component which is globally available.
 
 Code above renders like:
 
-### Title <Badge type="info" text="default" />
+### Title <Badge type="info" text="Standard" />
 ### Title <Badge type="tip" text="^1.9.0" />
 ### Title <Badge type="warning" text="beta" />
 ### Title <Badge type="danger" text="deprecated" />
 
-## Custom Children
+## Eigenes Children
 
 `<Badge>` accept `children`, which will be displayed in the badge.
 
@@ -36,7 +36,7 @@ Code above renders like:
 
 ## Anpassen Type Color
 
-You can customize the style of badges by overriding css variables. The following are the default values:
+Du kannst customize the style of badges by overriding css variables. The following are the Standard values:
 
 ```css
 :root {

From 835b030d0b7ea530a56a7b94a1b9d55ed6e82144 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:46:58 +0200
Subject: [PATCH 062/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-carbon-ads.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/reference/default-theme-carbon-ads.md b/docs/de/reference/default-theme-carbon-ads.md
index e12f6b12e..4d3a618b8 100644
--- a/docs/de/reference/default-theme-carbon-ads.md
+++ b/docs/de/reference/default-theme-carbon-ads.md
@@ -1,5 +1,5 @@
 ---
-description: Integrate Carbon Ads into your VitePress site using the default theme's built-in support.
+description: Integrate Carbon Ads into your VitePress site using the Standard theme's built-in support.
 ---
 
 # Carbon Ads
@@ -26,4 +26,4 @@ The `format` option supports `classic`, `responsive`, and `cover`.
 `//cdn.carbonads.com/carbon.js?serve=${code}&placement=${placement}&format=${format}`
 ```
 
-To learn more about Carbon Ads configuration, please visit [Carbon Ads website](https://www.carbonads.net/).
+To learn more about Carbon Ads Konfiguration, please visit [Carbon Ads website](https://www.carbonads.net/).

From cc2297bcf3768fba5095618db739120a859e2803 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:00 +0200
Subject: [PATCH 063/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-config.md | 60 +++++++++++------------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
index 28e09d79b..c58497527 100644
--- a/docs/de/reference/default-theme-config.md
+++ b/docs/de/reference/default-theme-config.md
@@ -1,10 +1,10 @@
 ---
-description: Reference of all configuration options available for the VitePress default theme.
+description: Reference of all Konfiguration options verfügbar for the VitePress Standard theme.
 ---
 
 # Konfiguration des Standard-Themes
 
-Theme config lets you customize your theme. You can define theme config via the `themeConfig` option in the config file:
+Theme config lets you customize your theme. Du kannst define theme config via the `themeConfig` option in the config file:
 
 ```ts
 export default {
@@ -21,15 +21,15 @@ export default {
 }
 ```
 
-**The options documented on this page only apply to the default theme.** Different themes expect different theme config. When using a custom theme, the theme config object will be passed to the theme so the theme can define conditional behavior based on it.
+**The options documented on this page only apply to the Standard theme.** Different themes expect different theme config. When using a custom theme, the theme config object will be passed to the theme so the theme can define conditional behavior based on it.
 
 ## i18nRouting
 
 - Type: `boolean | ((data: VitePressData<DefaultTheme.Config>, route: Route, targetLocale: string) => string)`
 
-Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. You can disable this behavior by setting `themeConfig.i18nRouting` to `false`.
+Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. Du kannst disable this behavior by setting `themeConfig.i18nRouting` to `falsch`.
 
-Set `themeConfig.i18nRouting` to a function to customize the locale link. The function receives the current VitePress data, the current route, and the target locale key, and returns the target link.
+Set `themeConfig.i18nRouting` to a function to customize the locale link. The function receives the current VitePress data, the current route, and the target locale key, and gibt zurück the target link.
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -70,9 +70,9 @@ type ThemeableImage =
 
 ## siteTitle
 
-- Type: `string | false`
+- Type: `string | falsch`
 
-You can customize this item to replace the default site title (`title` in app config) in nav. When set to `false`, title in nav will be disabled. Useful when you have `logo` that already contains the site title text.
+Du kannst customize this item to replace the Standard site title (`title` in app config) in nav. When set to `falsch`, title in nav will be deaktiviert. Useful when you have `logo` that already contains the site title text.
 
 ```ts
 export default {
@@ -86,7 +86,7 @@ export default {
 
 - Type: `NavItem`
 
-The configuration for the nav menu item. More details in [Default Theme: Nav](./default-theme-nav#navigation-links).
+The Konfiguration for the nav menu item. More details in [Standard-Theme: Nav](./Standard-theme-nav#navigation-links).
 
 ```ts
 export default {
@@ -132,9 +132,9 @@ interface NavItemWithChildren {
 
 ## sidebar
 
-- Type: `Sidebar`
+- Type: `Seitenleiste`
 
-The configuration for the sidebar menu item. More details in [Default Theme: Sidebar](./default-theme-sidebar).
+The Konfiguration for the sidebar menu item. More details in [Standard-Theme: Seitenleiste](./Standard-theme-sidebar).
 
 ```ts
 export default {
@@ -203,22 +203,22 @@ export type SidebarItem = {
 ## aside
 
 - Type: `boolean | 'left'`
-- Default: `true`
+- Default: `wahr`
 - Can be overridden per page via [frontmatter](./frontmatter-config#aside)
 
-Setting this value to `false` prevents rendering of aside container.\
-Setting this value to `true` renders the aside to the right.\
+Setting this value to `falsch` prevents rendering of aside container.\
+Setting this value to `wahr` renders the aside to the right.\
 Setting this value to `left` renders the aside to the left.\
 In right-to-left layouts, both sides are mirrored.
 
-If you want to disable it for all viewports, you should use `outline: false` instead.
+Wenn du want to disable it for all viewports, you should use `outline: falsch` instead.
 
 ## outline
 
-- Type: `Outline | Outline['level'] | false`
+- Type: `Outline | Outline['level'] | falsch`
 - Level can be overridden per page via [frontmatter](./frontmatter-config#outline)
 
-Setting this value to `false` prevents rendering of outline container. Refer this interface for more details:
+Setting this value to `falsch` prevents rendering of outline container. Refer this interface for more details:
 
 ```ts
 interface Outline {
@@ -245,7 +245,7 @@ interface Outline {
 
 - Type: `SocialLink[]`
 
-You may define this option to show your social account links with icons in nav.
+Du kannst define this option to show your social account links with icons in nav.
 
 ```ts
 export default {
@@ -286,7 +286,7 @@ interface SocialLink {
 - Type: `Fußzeile`
 - Can be overridden per page via [frontmatter](./frontmatter-config#footer)
 
-Fußzeile configuration. You can add a message or copyright text on the footer, however, it will only be displayed when the page doesn't contain a sidebar. This is due to design concerns.
+Fußzeile Konfiguration. Du kannst add a message or copyright text on the footer, however, it will only be displayed when the page doesn't contain a sidebar. Dies is due to design concerns.
 
 ```ts
 export default {
@@ -311,7 +311,7 @@ export interface Fußzeile {
 - Type: `EditLink`
 - Can be overridden per page via [frontmatter](./frontmatter-config#editlink)
 
-Bearbeitungslink lets you display a link to edit the page on Git management services such as GitHub, or GitLab. See [Default Theme: Bearbeitungslink](./default-theme-edit-link) for more details.
+Bearbeitungslink lets you display a link to edit the page on Git management services such as GitHub, or GitLab. See [Standard-Theme: Bearbeitungslink](./Standard-theme-edit-link) for more details.
 
 ```ts
 export default {
@@ -370,7 +370,7 @@ export interface LastUpdatedOptions {
 
 - Type: `AlgoliaSearch`
 
-An option to support searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Learn more in [Default Theme: Search](./default-theme-search)
+An option to support searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Learn more in [Standard-Theme: Suche](./Standard-theme-search)
 
 ```ts
 export interface AlgoliaSearchOptions extends DocSearchProps {
@@ -406,13 +406,13 @@ export interface CarbonAdsOptions {
 }
 ```
 
-Learn more in [Default Theme: Carbon Ads](./default-theme-carbon-ads)
+Learn more in [Standard-Theme: Carbon Ads](./Standard-theme-carbon-ads)
 
 ## docFooter
 
 - Type: `DocFooter`
 
-Can be used to customize text appearing above previous and next links. Helpful if not writing docs in English. Also can be used to disable prev/next links globally. If you want to selectively enable/disable prev/next links, you can use [frontmatter](./default-theme-prev-next-links).
+Can be used to customize text appearing above previous and next links. Helpful if not writing docs in English. Also can be used to disable prev/next links globally. Wenn du want to selectively enable/disable prev/next links, you can use [frontmatter](./Standard-theme-prev-next-links).
 
 ```ts
 export default {
@@ -437,7 +437,7 @@ export interface DocFooter {
 - Type: `string`
 - Default: `Appearance`
 
-Can be used to customize the dark mode switch label. This label is only displayed in the mobile view.
+Can be used to customize the dark mode switch label. Dies label is only displayed in the mobile view.
 
 ## lightModeSwitchTitle
 
@@ -458,21 +458,21 @@ Can be used to customize the dark mode switch title that appears on hovering.
 - Type: `string`
 - Default: `Menu`
 
-Can be used to customize the sidebar menu label. This label is only displayed in the mobile view.
+Can be used to customize the sidebar menu label. Dies label is only displayed in the mobile view.
 
 ## returnToTopLabel
 
 - Type: `string`
 - Default: `Return to top`
 
-Can be used to customize the label of the return to top button. This label is only displayed in the mobile view.
+Can be used to customize the label of the zurückgeben to top button. Dies label is only displayed in the mobile view.
 
 ## langMenuLabel
 
 - Type: `string`
 - Default: `Change language`
 
-Can be used to customize the aria-label of the language toggle button in navbar. This is only used if you're using [i18n](../guide/i18n).
+Can be used to customize the aria-label of the language toggle button in navbar. Dies is only used if you're using [i18n](../guide/i18n).
 
 ## navMenuLabel
 
@@ -500,21 +500,21 @@ Can be used to customize the aria-label of the `⋯` menu button in the navbar.
 - Type: `string`
 - Default: `Skip to content`
 
-Can be used to customize the label of the skip to content link. This link is shown when the user is navigating the site using a keyboard.
+Can be used to customize the label of the skip to content link. Dies link is shown when the user is navigating the site using a keyboard.
 
 ## externalLinkIcon
 
 - Type: `boolean`
-- Default: `false`
+- Default: `falsch`
 
 Whether to show an external link icon next to external links in markdown.
 
 ## gradedContainers
 
 - Type: `boolean`
-- Default: `false`
+- Default: `falsch`
 
-Whether to color [custom containers](../guide/markdown#custom-containers), [GitHub-flavored alerts](../guide/markdown#github-flavored-alerts), and badges on a graded severity scale — danger red, warning orange, caution yellow. By default, colors match GitHub's alerts, where caution shares danger's red and warning is yellow.
+Whether to color [custom containers](../guide/markdown#custom-containers), [GitHub-flavored alerts](../guide/markdown#github-flavored-alerts), and badges on a graded severity scale — danger red, warning orange, caution yellow. By Standard, colors match GitHub's alerts, where caution shares danger's red and warning is yellow.
 
 ## `useLayout` <Badge type="info" text="composable" />
 

From aeb5bd3f6c715e362a36c0e152799ef3f128f3b5 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:03 +0200
Subject: [PATCH 064/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-edit-link.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/default-theme-edit-link.md b/docs/de/reference/default-theme-edit-link.md
index 0c12bfc18..5013cf30c 100644
--- a/docs/de/reference/default-theme-edit-link.md
+++ b/docs/de/reference/default-theme-edit-link.md
@@ -20,7 +20,7 @@ export default {
 
 The `pattern` option defines the URL structure for the link, and `:path` is going to be replaced with the page path.
 
-You can also put a pure function that accepts [`PageData`](./runtime-api#usedata) as the argument and returns the URL string.
+Du kannst also put a pure function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the URL string.
 
 ```js
 export default {
@@ -38,9 +38,9 @@ export default {
 }
 ```
 
-It should not have side-effects nor access anything outside of its scope since it will be serialized and executed in the browser.
+It should not have side-effects nor access anything outside of its scope since it will be serialized and executed in the Browser.
 
-By default, this will add the link text "Edit this page" at the bottom of the doc page. You may customize this text by defining the `text` option.
+By Standard, this will add the link text "Edit this page" at the bottom of the doc page. Du kannst customize this text by defining the `text` option.
 
 ```js
 export default {
@@ -55,7 +55,7 @@ export default {
 
 ## Frontmatter Config
 
-This can be disabled per-page using the `editLink` option on frontmatter:
+Dies can be deaktiviert per-page using the `editLink` option on frontmatter:
 
 ```yaml
 ---

From d6c62e26cbc1172f7544015bdf5162a2649d6071 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:05 +0200
Subject: [PATCH 065/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-footer.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/reference/default-theme-footer.md b/docs/de/reference/default-theme-footer.md
index 7070e220e..58384746e 100644
--- a/docs/de/reference/default-theme-footer.md
+++ b/docs/de/reference/default-theme-footer.md
@@ -1,5 +1,5 @@
 ---
-description: Configure the global footer displayed at the bottom of VitePress pages.
+description: Konfigurieren the global footer displayed at the bottom of VitePress pages.
 ---
 
 # Fußzeile
@@ -27,7 +27,7 @@ export interface Fußzeile {
 }
 ```
 
-The above configuration also supports HTML strings. So, for example, if you want to configure footer text to have some links, you can adjust the configuration as follows:
+The above Konfiguration also supports HTML strings. So, for example, if you want to configure footer text to have some links, you can adjust the Konfiguration as follows:
 
 ```ts
 export default {
@@ -41,14 +41,14 @@ export default {
 ```
 
 ::: warning
-Only inline elements can be used in `message` and `copyright` as they are rendered inside a `<p>` element. If you want to add block elements, consider using [`layout-bottom`](../guide/extending-default-theme#layout-slots) slot instead.
+Only inline elements can be used in `message` and `copyright` as they are rendered inside a `<p>` element. Wenn du want to add block elements, consider using [`layout-bottom`](../guide/extending-Standard-theme#layout-slots) slot instead.
 :::
 
-Note that footer will not be displayed when the [SideBar](./default-theme-sidebar) is visible.
+Hinweis that footer will not be displayed when the [SideBar](./Standard-theme-sidebar) is visible.
 
 ## Frontmatter Config
 
-This can be disabled per-page using the `footer` option on frontmatter:
+Dies can be deaktiviert per-page using the `footer` option on frontmatter:
 
 ```yaml
 ---

From c5422616b67bf5fa8d113e9ff0c8f3a8865ecde1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:08 +0200
Subject: [PATCH 066/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-home-page.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/reference/default-theme-home-page.md b/docs/de/reference/default-theme-home-page.md
index a1a27b964..e5ef6c9ea 100644
--- a/docs/de/reference/default-theme-home-page.md
+++ b/docs/de/reference/default-theme-home-page.md
@@ -1,10 +1,10 @@
 ---
-description: Configure the VitePress default theme home page layout with hero sections, features, and custom content.
+description: Konfigurieren the VitePress Standard theme home page layout with hero sections, features, and custom content.
 ---
 
 # Startseite
 
-VitePress default theme provides a homepage layout, which you can also see used on [the homepage of this site](../). You may use it on any of your pages by specifying `layout: home` in the [frontmatter](./frontmatter-config).
+VitePress Standard theme provides a homepage layout, which you can also see used on [the homepage of this site](../). Du kannst use it on any of your pages by specifying `layout: home` in the [frontmatter](./frontmatter-config).
 
 ```yaml
 ---
@@ -12,7 +12,7 @@ layout: home
 ---
 ```
 
-However, this option alone wouldn't do much. You can add several different pre templated "sections" to the homepage by setting additional other options such as `hero` and `features`.
+However, this option alone wouldn't do much. Du kannst add several different pre templated "sections" to the homepage by setting additional other options such as `hero` and `features`.
 
 ## Hero Section
 
@@ -105,7 +105,7 @@ Also you may customize it further by combining `--vp-home-hero-name-background`
 
 In Features section, you can list any number of features you would like to show right after the Hero section. To configure it, pass `features` option to the frontmatter.
 
-You can provide an icon for each feature, which can be an emoji or any type of image. When the configured icon is an image (svg, png, jpeg...), you must provide the icon with the proper width and height; you can also provide the description, its intrinsic size as well as its variants for dark and light theme when required.
+Du kannst provide an icon for each feature, which can be an emoji or any type of image. When the configured icon is an image (svg, png, jpeg...), you must provide the icon with the proper width and height; you can also provide the description, its intrinsic size as well as its variants for dark and light theme when erforderlich.
 
 ```yaml
 ---
@@ -171,9 +171,9 @@ type FeatureIcon =
     }
 ```
 
-## Markdown Content
+## Markdown Inhalt
 
-You can add additional content to your site's homepage just by adding Markdown below the `---` frontmatter divider.
+Du kannst add additional content to your site's homepage just by adding Markdown below the `---` frontmatter divider.
 
 ````md
 ---
@@ -195,5 +195,5 @@ npx vitepress init
 ````
 
 ::: info
-VitePress didn't always auto-style the extra content of the `layout: home` page. To revert to older behavior, you can add `markdownStyles: false` to the frontmatter.
+VitePress didn't always auto-style the extra content of the `layout: home` page. To revert to older behavior, you can add `markdownStyles: falsch` to the frontmatter.
 :::

From 41bb8602ea05878a38f1b68ae86cf493d3a6a28b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:10 +0200
Subject: [PATCH 067/199] docs(de): translate reference text

---
 docs/de/reference/default-theme-last-updated.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-last-updated.md b/docs/de/reference/default-theme-last-updated.md
index e2d2d6356..2a3538846 100644
--- a/docs/de/reference/default-theme-last-updated.md
+++ b/docs/de/reference/default-theme-last-updated.md
@@ -22,7 +22,7 @@ To fix this in **GitHub Actions**, use the following in your workflow:
 
 Other CI/CD platforms have similar settings.
 
-If such options aren't available, you can prepend the `docs:build` command in your `package.json` with a manual fetch:
+If such options aren't verfügbar, you can prepend the `docs:build` command in your `package.json` with a manual fetch:
 
 ```json
 "docs:build": "git fetch --unshallow && vitepress build docs"
@@ -39,7 +39,7 @@ export default {
 
 ## Frontmatter Config
 
-This can be disabled per-page using the `lastUpdated` option on frontmatter:
+Dies can be deaktiviert per-page using the `lastUpdated` option on frontmatter:
 
 ```yaml
 ---
@@ -47,4 +47,4 @@ lastUpdated: false
 ---
 ```
 
-Also refer [Default Theme: Letzte Aktualisierung](./default-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly disabled at site or page level.
+Also refer [Standard-Theme: Letzte Aktualisierung](./Standard-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly deaktiviert at site or page level.

From a8ef2d29a04f5c50fcb56f2896f4a73ffcebe1ab Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:16 +0200
Subject: [PATCH 068/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-layout.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/reference/default-theme-layout.md b/docs/de/reference/default-theme-layout.md
index d15e4330c..a6321d1f2 100644
--- a/docs/de/reference/default-theme-layout.md
+++ b/docs/de/reference/default-theme-layout.md
@@ -4,7 +4,7 @@ description: Choose between doc, page, and home layouts in the VitePress default
 
 # Layout
 
-You may choose the page layout by setting `layout` option to the page [frontmatter](./frontmatter-config). There are 3 layout options, `doc`, `page`, and `home`. If nothing is specified, then the page is treated as `doc` page.
+Du kannst choose the page layout by setting `layout` option to the page [frontmatter](./frontmatter-config). There are 3 layout options, `doc`, `page`, and `home`. If nothing is specified, then the page is treated as `doc` page.
 
 ```yaml
 ---
@@ -18,32 +18,32 @@ Option `doc` is the default layout and it styles the whole Markdown content into
 
 Almost all generic elements such as `p`, or `h2` get special styling. Therefore, keep in mind that if you add any custom HTML inside a Markdown content, those will get affected by those styles as well.
 
-It also provides documentation specific features listed below. These features are only enabled in this layout.
+It also stellt bereit documentation specific features listed below. These features are only aktiviert in this layout.
 
 - Bearbeitungslink
-- Prev Next Link
+- Prev Weiter Link
 - Outline
 - [Carbon Ads](./default-theme-carbon-ads)
 
-## Page Layout
+## Seite Layout
 
 Option `page` is treated as "blank page". The Markdown will still be parsed, and all of the [Markdown Extensions](../guide/markdown) work as same as `doc` layout, but it wouldn't get any default stylings.
 
 The page layout will let you style everything by you without VitePress theme affecting the markup. This is useful when you want to create your own custom page.
 
-Note that even in this layout, sidebar will still show up if the page has a matching sidebar config.
+Beachte, dass even in this layout, sidebar will still show up if the page has a matching sidebar config.
 
 ## Home Layout
 
-Option `home` will generate templated "Homepage". In this layout, you can set extra options such as `hero` and `features` to customize the content further. Please visit [Default Theme: Startseite](./default-theme-home-page) for more details.
+Option `home` will generate templated "Homepage". In this layout, you can set extra options such as `hero` and `features` to customize the content further. Please visit [Standard-Theme: Startseite](./default-theme-home-page) for more details.
 
 ## No Layout
 
-If you don't want any layout, you can pass `layout: false` through frontmatter. This option is helpful if you want a fully-customizable landing page (without any sidebar, navbar, or footer by default).
+Wenn du don't want any layout, you can pass `layout: false` through frontmatter. This option is helpful if you want a fully-customizable landing page (without any sidebar, navbar, or footer by default).
 
-## Custom Layout
+## Eigenes Layout
 
-You can also use a custom layout:
+Du kannst also use a custom layout:
 
 ```md
 ---
@@ -51,7 +51,7 @@ layout: foo
 ---
 ```
 
-This will look for a component named `foo` registered in context. For example, you can register your component globally in `.vitepress/theme/index.ts`:
+This will look for a component named `foo` registered in context. Zum Beispiel, you can register your component globally in `.vitepress/theme/index.ts`:
 
 ```ts
 import DefaultTheme from 'vitepress/theme'

From a0015d368b9b95426c045241c874d3aa1b09cb26 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:18 +0200
Subject: [PATCH 069/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-nav.md | 28 +++++++++++++-------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/docs/de/reference/default-theme-nav.md b/docs/de/reference/default-theme-nav.md
index 02caac415..3b9c98c80 100644
--- a/docs/de/reference/default-theme-nav.md
+++ b/docs/de/reference/default-theme-nav.md
@@ -1,5 +1,5 @@
 ---
-description: Configure the navigation bar in the VitePress default theme including site title, logo, and menu links.
+description: Konfigurieren the navigation bar in the VitePress default theme including site title, logo, and menu links.
 ---
 
 # Nav
@@ -8,7 +8,7 @@ The Nav is the navigation bar displayed on top of the page. It contains the site
 
 ## Site Title and Logo
 
-By default, nav shows the title of the site referencing [`config.title`](./site-config#title) value. If you would like to change what's displayed on nav, you may define custom text in `themeConfig.siteTitle` option.
+Standardmäßig, nav shows the title of the site referencing [`config.title`](./site-config#title) value. Wenn du would like to change what's displayed on nav, you may define custom text in `themeConfig.siteTitle` option.
 
 ```js
 export default {
@@ -18,7 +18,7 @@ export default {
 }
 ```
 
-If you have a logo for your site, you can display it by passing in the path to the image. You should place the logo within `public` directly, and define the absolute path to it.
+Wenn du have a logo for your site, you can display it by passing in the path to the image. Du solltest place the logo within `public` directly, and define the absolute path to it.
 
 ```js
 export default {
@@ -39,11 +39,11 @@ export default {
 }
 ```
 
-You can also pass an object as logo if you want to add `alt` attribute or customize it based on dark/light mode. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
+Du kannst also pass an object as logo if you want to add `alt` attribute or customize it based on dark/light mode. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
 
 ## Navigation Links
 
-You may define `themeConfig.nav` option to add links to your nav.
+Du kannst define `themeConfig.nav` option to add links to your nav.
 
 ```js
 export default {
@@ -59,7 +59,7 @@ export default {
 
 The `text` is the actual text displayed in nav, and the `link` is the link that will be navigated to when the text is clicked. For the link, set path to the actual file without `.md` prefix, and always start with `/`.
 
-The `link` can also be a function that accepts [`PageData`](./runtime-api#usedata) as the argument and returns the path.
+The `link` can also be a function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the path.
 
 Nav links can also be dropdown menus. To do this, set `items` key on link option.
 
@@ -81,9 +81,9 @@ export default {
 }
 ```
 
-Note that dropdown menu title (`Dropdown Menu` in the above example) can not have `link` property since it becomes a button to open dropdown dialog.
+Beachte, dass dropdown menu title (`Dropdown Menu` in the above example) can not have `link` property since it becomes a button to open dropdown dialog.
 
-You may further add "sections" to the dropdown menu items as well by passing in more nested items.
+Du kannst further add "sections" to the dropdown menu items as well by passing in more nested items.
 
 ```js
 export default {
@@ -120,7 +120,7 @@ export default {
 }
 ```
 
-### Customize link's "active" state
+### Anpassen link's "active" state
 
 Nav menu items will be highlighted when the current page is under the matching path. if you would like to customize the path to be matched, define `activeMatch` property and regex as a string value.
 
@@ -144,9 +144,9 @@ export default {
 `activeMatch` is expected to be a regex string, but you must define it as a string. We can't use actual RegExp object here because it isn't serializable during the build time.
 :::
 
-### Customize link's "target" and "rel" attributes
+### Anpassen link's "target" and "rel" attributes
 
-By default, VitePress automatically determines `target` and `rel` attributes based on whether the link is an external link. But if you want, you can customize them too.
+Standardmäßig, VitePress automatisch determines `target` and `rel` attributes based on whether the link is an external link. But if you want, you can customize them too.
 
 ```js
 export default {
@@ -167,9 +167,9 @@ export default {
 
 Refer [`socialLinks`](./default-theme-config#sociallinks).
 
-## Custom Components
+## Eigenes Komponenten
 
-You can include custom components in the navigation bar by using the `component` option. The `component` key should be the Vue component name, and must be registered globally using [Theme.enhanceApp](../guide/custom-theme#theme-interface).
+Du kannst include custom components in the navigation bar by using the `component` option. The `component` key should be the Vue component name, and must be registered globally using [Theme.enhanceApp](../guide/custom-theme#theme-interface).
 
 ```js [.vitepress/config.js]
 export default {
@@ -218,4 +218,4 @@ Your component will be rendered in the navigation bar. VitePress will provide th
 - `screenMenu`: an optional boolean indicating whether the component is inside mobile navigation menu
 - `menu`: an optional boolean indicating whether the component is inside a dropdown panel — for example, the `⋯` menu that nav items collapse into when they don't fit the bar. In both these contexts, render a flat list instead of a floating flyout, which would end up nested inside the panel
 
-You can check an example in the e2e tests [here](https://github.com/vuejs/vitepress/tree/main/__tests__/e2e/.vitepress).
+Du kannst check an example in the e2e tests [here](https://github.com/vuejs/vitepress/tree/main/__tests__/e2e/.vitepress).

From e0d8ffb8d8fb266c876c5a93a4889237b4e415f2 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:21 +0200
Subject: [PATCH 070/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-prev-next-links.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/default-theme-prev-next-links.md b/docs/de/reference/default-theme-prev-next-links.md
index e57360b46..38221be48 100644
--- a/docs/de/reference/default-theme-prev-next-links.md
+++ b/docs/de/reference/default-theme-prev-next-links.md
@@ -1,10 +1,10 @@
 ---
-description: Customize the previous and next page links displayed at the bottom of doc pages in VitePress.
+description: Anpassen the previous and next page links displayed at the bottom of doc pages in VitePress.
 ---
 
-# Prev Next Links
+# Prev Weiter Links
 
-You can customize the text and link for the previous and next pages (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
+Du kannst customize the text and link for the previous and next pages (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
 
 ## prev
 
@@ -12,7 +12,7 @@ You can customize the text and link for the previous and next pages (shown at do
 
 - Details:
 
-  Specifies the text/link to show on the link to the previous page. If you don't set this in frontmatter, the text/link will be inferred from the sidebar config.
+  Specifies the text/link to show on the link to the previous page. Wenn du don't set this in frontmatter, the text/link will be inferred from the sidebar config.
 
 - Beispiele:
 

From 5278b5c484f63104ba0be52f8d120998a64c2dc0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:23 +0200
Subject: [PATCH 071/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-search.md | 30 +++++++++++------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/docs/de/reference/default-theme-search.md b/docs/de/reference/default-theme-search.md
index 0c81da715..1285a813c 100644
--- a/docs/de/reference/default-theme-search.md
+++ b/docs/de/reference/default-theme-search.md
@@ -7,7 +7,7 @@ description: Set up local or Algolia-powered search for your VitePress site.
 
 ## Local Suche
 
-VitePress supports fuzzy full-text search using an in-browser index thanks to [minisearch](https://github.com/lucaong/minisearch/). To enable this feature, simply set the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
+VitePress unterstützt fuzzy full-text search using an in-browser index thanks to [minisearch](https://github.com/lucaong/minisearch/). To enable this feature, simply set the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -35,7 +35,7 @@ Alternatively, you can use [Algolia DocSearch](#algolia-search) or some communit
 
 ### i18n {#local-search-i18n}
 
-You can use a config like this to use multilingual search:
+Du kannst use a config like this to use multilingual search:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -78,7 +78,7 @@ export default defineConfig({
 
 ### miniSearch options
 
-You can configure MiniSearch like this:
+Du kannst configure MiniSearch like this:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -110,15 +110,15 @@ export default defineConfig({
 })
 ```
 
-Learn more in [MiniSearch docs](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
+Mehr erfahren in [MiniSearch docs](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
 
 ::: info Document IDs
 Suche document IDs (as seen by `searchOptions.filter`, `boostDocument`, and in the raw index) are site-relative paths like `/guide/page.html#section` — they do not include [`base`](../reference/site-config#base). The theme resolves them against the base when rendering results.
 :::
 
-### Custom content renderer
+### Eigenes content renderer
 
-You can customize the function used to render the markdown content before indexing it:
+Du kannst customize the function used to render the markdown content before indexing it:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -146,7 +146,7 @@ This function will be stripped from client-side site data, so you can use Node.j
 
 #### Beispiel: Excluding pages from search
 
-You can exclude pages from search by adding `search: false` to the frontmatter of the page. Alternatively:
+Du kannst exclude pages from search by adding `search: false` to the frontmatter of the page. Alternatively:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -196,7 +196,7 @@ export default defineConfig({
 
 ## Algolia Suche
 
-VitePress supports searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Refer to their getting started guide. In your `.vitepress/config.ts` you'll need to provide at least the following to make it work:
+VitePress unterstützt searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Refer to their getting started guide. In your `.vitepress/config.ts` you'll need to provide at least the following to make it work:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -217,7 +217,7 @@ export default defineConfig({
 
 ### i18n {#algolia-search-i18n}
 
-You can use a config like this to use multilingual search:
+Du kannst use a config like this to use multilingual search:
 
 <details>
 <summary>View full example</summary>
@@ -230,7 +230,7 @@ Refer [official Algolia docs](https://docsearch.algolia.com/docs/api#translation
 
 ### Algolia Ask AI Support {#ask-ai}
 
-If you would like to include **Ask AI**, pass the `askAi` option (or any of the partial fields) inside `options`:
+Wenn du would like to include **Ask AI**, pass the `askAi` option (or any of the partial fields) inside `options`:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -260,12 +260,12 @@ export default defineConfig({
 ```
 
 ::: warning Note
-If you want to default to keyword search and do not want to use Ask AI, omit the `askAi` property.
+Wenn du want to default to keyword search and do not want to use Ask AI, omit the `askAi` property.
 :::
 
 ### Ask AI Side Panel {#ask-ai-side-panel}
 
-DocSearch v4.5+ supports an optional **Ask AI side panel**. When enabled, it can be opened with **Ctrl/Cmd+I** by default. The [Sidepanel API Reference](https://docsearch.algolia.com/docs/sidepanel/api-reference) contains the full list of options.
+DocSearch v4.5+ unterstützt an optional **Ask AI side panel**. When aktiviert, it can be opened with **Ctrl/Cmd+I** by default. The [Sidepanel API Reference](https://docsearch.algolia.com/docs/sidepanel/api-reference) contains the full list of options.
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -302,7 +302,7 @@ questions. Algolia's standalone Ask AI examples also mention
 VitePress side panel mode and does not make the integrated keyword-search
 modal display suggested questions on first open.
 
-If you need to disable the keyboard shortcut, use the `keyboardShortcuts` option at the sidepanel root level:
+Wenn du need to disable the keyboard shortcut, use the `keyboardShortcuts` option at the sidepanel root level:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -331,7 +331,7 @@ export default defineConfig({
 
 #### Mode (auto / sidePanel / hybrid / modal) {#ask-ai-mode}
 
-You can optionally control how VitePress integrates keyword search and Ask AI:
+Du kannst optionally control how VitePress integrates keyword search and Ask AI:
 
 - `mode: 'auto'` (default): infer `hybrid` when keyword search is configured, otherwise `sidePanel` when Ask AI side panel is configured.
 - `mode: 'sidePanel'`: force side panel only (hides the keyword search button).
@@ -340,7 +340,7 @@ You can optionally control how VitePress integrates keyword search and Ask AI:
 
 #### Ask AI only (no keyword search) {#ask-ai-only}
 
-If you want to use **Ask AI side panel only**, you can omit top-level keyword search config and provide credentials under `askAi`:
+Wenn du want to use **Ask AI side panel only**, you can omit top-level keyword search config and provide credentials under `askAi`:
 
 ```ts
 import { defineConfig } from 'vitepress'

From 39d6d4113c49f99fc9d76d1ef8d6369ad58a0643 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:26 +0200
Subject: [PATCH 072/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-sidebar.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/de/reference/default-theme-sidebar.md b/docs/de/reference/default-theme-sidebar.md
index 52bccc783..c974c4b20 100644
--- a/docs/de/reference/default-theme-sidebar.md
+++ b/docs/de/reference/default-theme-sidebar.md
@@ -1,10 +1,10 @@
 ---
-description: Configure the sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
+description: Konfigurieren the sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
 ---
 
 # Seitenleiste
 
-The sidebar is the main navigation block for your documentation. You can configure the sidebar menu in [`themeConfig.sidebar`](./default-theme-config#sidebar).
+The sidebar is the main navigation block for your documentation. Du kannst configure the sidebar menu in [`themeConfig.sidebar`](./default-theme-config#sidebar).
 
 ```js
 export default {
@@ -52,7 +52,7 @@ export default {
 }
 ```
 
-Each `link` should specify the path to the actual file starting with `/`. If you add trailing slash to the end of link, it will show `index.md` of the corresponding directory.
+Each `link` should specify the path to the actual file starting with `/`. Wenn du add trailing slash to the end of link, it will show `index.md` of the corresponding directory.
 
 ```js
 export default {
@@ -70,7 +70,7 @@ export default {
 }
 ```
 
-You may further nest the sidebar items up to 6 level deep counting up from the root level. Note that deeper than 6 level of nested items gets ignored and will not be displayed on the sidebar.
+Du kannst further nest the sidebar items up to 6 level deep counting up from the root level. Beachte, dass deeper than 6 level of nested items gets ignored and will not be displayed on the sidebar.
 
 ```js
 export default {
@@ -99,7 +99,7 @@ export default {
 
 ## Multiple Sidebars
 
-You may show different sidebar depending on the page path. For example, as shown on this site, you might want to create a separate sections of content in your documentation like "Guide" page and "Config" page.
+Du kannst show different sidebar depending on the page path. Zum Beispiel, as shown on this site, you might want to create a separate sections of content in your documentation like "Guide" page and "Config" page.
 
 To do so, first organize your pages into directories for each desired section:
 
@@ -169,7 +169,7 @@ export default {
 }
 ```
 
-All sections are "open" by default. If you would like them to be "closed" on initial page load, set `collapsed` option to `true`.
+All sections are "open" by default. Wenn du would like them to be "closed" on initial page load, set `collapsed` option to `true`.
 
 ```js
 export default {
@@ -187,13 +187,13 @@ export default {
 
 ## Path Prefix
 
-When your documentation structure has deep directories or groups located under the same subdirectory, you can use the `base` option to automatically prepend a path prefix to all nested `items` inside that group. This avoids repeating the same path prefix for every `link`.
+When your documentation structure has deep directories or groups located under the same subdirectory, you can use the `base` option to automatisch prepend a path prefix to all nested `items` inside that group. This avoids repeating the same path prefix for every `link`.
 
 The `base` option is supported in both multiple sidebar configurations and nested sidebar groups.
 
 ### In Multiple Sidebars
 
-You can define `base` at the root of a sidebar section configuration:
+Du kannst define `base` at the root of a sidebar section configuration:
 
 ```js {5}
 export default {
@@ -215,7 +215,7 @@ export default {
 
 ### In Nested Groups
 
-You can also use `base` inside nested sidebar groups. It will apply to the immediate children of that group:
+Du kannst also use `base` inside nested sidebar groups. It will apply to the immediate children of that group:
 
 ```js{6,13}
 export default {

From 4d1525af750885ef38c578756623eaf8791ad090 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:29 +0200
Subject: [PATCH 073/199] docs(de): complete German translation

---
 docs/de/reference/default-theme-team-page.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/reference/default-theme-team-page.md b/docs/de/reference/default-theme-team-page.md
index 99bed39cd..8deadf4de 100644
--- a/docs/de/reference/default-theme-team-page.md
+++ b/docs/de/reference/default-theme-team-page.md
@@ -29,11 +29,11 @@ const members = [
 
 # Teamseite
 
-If you would like to introduce your team, you may use Team components to construct the Teamseite. There are two ways of using these components. One is to embed it in doc page, and another is to create a full Teamseite.
+Wenn du would like to introduce your team, you may use Team components to construct the Teamseite. There are two ways of using these components. One is to embed it in doc page, and another is to create a full Teamseite.
 
 ## Show team members in a page
 
-You may use `<VPTeamMembers>` component exposed from `vitepress/theme` to display a list of team members on any page.
+Du kannst use `<VPTeamMembers>` component exposed from `vitepress/theme` to display a list of team members on any page.
 
 ```html
 <script setup>
@@ -64,11 +64,11 @@ The above will display a team member in card looking element. It should display
 
 <VPTeamMembers size="small" :members />
 
-`<VPTeamMembers>` component comes in 2 different sizes, `small` and `medium`. While it boils down to your preference, usually `small` size should fit better when used in doc page. Also, you may add more properties to each member such as adding "description" or "sponsor" button. Learn more about it in [`<VPTeamMembers>`](#vpteammembers).
+`<VPTeamMembers>` component comes in 2 different sizes, `small` and `medium`. While it boils down to your preference, usually `small` size should fit better when used in doc page. Also, you may add more properties to each member such as adding "description" or "sponsor" button. Mehr erfahren about it in [`<VPTeamMembers>`](#vpteammembers).
 
 Embedding team members in doc page is good for small size team where having dedicated full team page might be too much, or introducing partial members as a reference to documentation context.
 
-If you have large number of members, or simply would like to have more space to show team members, consider [creating a full team page](#create-a-full-team-page).
+Wenn du have large number of members, or simply would like to have more space to show team members, consider [creating a full team page](#create-a-full-team-page).
 
 ## Create a full Teamseite
 
@@ -123,7 +123,7 @@ When creating a full team page, remember to wrap all components with `<VPTeamPag
 
 ### Add sections to divide team members
 
-You may add "sections" to the team page. For example, you may have different types of team members such as Core Team Members and Community Partners. You can divide these members into sections to better explain the roles of each group.
+Du kannst add "sections" to the team page. Zum Beispiel, you may have different types of team members such as Core Team Members and Community Partners. Du kannst divide these members into sections to better explain the roles of each group.
 
 To do so, add `<VPTeamPageSection>` component to the `team.md` file we created previously.
 
@@ -244,7 +244,7 @@ Adds "title" section of the page. Best use at the very beginning under `<VPTeamP
 
 ## `<VPTeamPageSection>`
 
-Creates a "section" with in team page. It accepts `#title`, `#lead`, and `#members` slot. You may add as many sections as you like inside `<VPTeamPage>`.
+Creates a "section" with in team page. It accepts `#title`, `#lead`, and `#members` slot. Du kannst add as many sections as you like inside `<VPTeamPage>`.
 
 ```html
 <VPTeamPage>

From 742e70195d8f8a95841c8b69e989bd63b5c14ceb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:31 +0200
Subject: [PATCH 074/199] docs(de): complete German translation

---
 docs/de/reference/frontmatter-config.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/frontmatter-config.md b/docs/de/reference/frontmatter-config.md
index 1fb437338..1d16fd76c 100644
--- a/docs/de/reference/frontmatter-config.md
+++ b/docs/de/reference/frontmatter-config.md
@@ -1,6 +1,6 @@
 ---
 outline: deep
-description: Reference of all available frontmatter configuration options for VitePress Markdown pages.
+description: Reference of all verfügbar frontmatter configuration options for VitePress Markdown pages.
 ---
 
 # Frontmatter-Konfiguration
@@ -16,7 +16,7 @@ editLink: true
 ---
 ```
 
-You can access frontmatter data via the `$frontmatter` global in Vue expressions:
+Du kannst access frontmatter data via the `$frontmatter` global in Vue expressions:
 
 ```md
 {{ $frontmatter.title }}
@@ -107,7 +107,7 @@ The following frontmatter options are only applicable when using the default the
 Determines the layout of the page.
 
 - `doc` - It applies default documentation styles to the markdown content.
-- `home` - Special layout for "Startseite". You may add extra options such as `hero` and `features` to rapidly create beautiful landing page.
+- `home` - Special layout for "Startseite". Du kannst add extra options such as `hero` and `features` to rapidly create beautiful landing page.
 - `page` - Behave similar to `doc` but it applies no styles to the content. Useful when you want to create a fully custom page.
 
 ```yaml

From cfc6da39209d1c5d6127606adaf287326125a1bc Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:33 +0200
Subject: [PATCH 075/199] docs(de): complete German translation

---
 docs/de/reference/runtime-api.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/reference/runtime-api.md b/docs/de/reference/runtime-api.md
index aaab22aac..22321dcc4 100644
--- a/docs/de/reference/runtime-api.md
+++ b/docs/de/reference/runtime-api.md
@@ -6,13 +6,13 @@ description: Reference of VitePress runtime APIs including composables, helper f
 
 VitePress offers several built-in APIs to let you access app data. VitePress also comes with a few built-in components that can be used globally.
 
-The helper methods are globally importable from `vitepress` and are typically used in custom theme Vue components. However, they are also usable inside `.md` pages because markdown files are compiled into Vue [Single-File Components](https://vuejs.org/guide/scaling-up/sfc.html).
+The helper methods are globally importable from `vitepress` and are typically used in custom theme Vue components. However, they are also usable inside `.md` pages because markdown files are compiled into Vue [Single-Datei Komponenten](https://vuejs.org/guide/scaling-up/sfc.html).
 
 Methods that start with `use*` indicates that it is a [Vue 3 Composition API](https://vuejs.org/guide/introduction.html#composition-api) function ("Composable") that can only be used inside `setup()` or `<script setup>`.
 
 ## `useData` <Badge type="info" text="composable" />
 
-Returns page-specific data. The returned object has the following type:
+Gibt zurück page-specific data. The returned object has the following type:
 
 ```ts
 interface VitePressData<T = any> {
@@ -62,7 +62,7 @@ interface PageData {
 }
 ```
 
-`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) is enabled. Without that option, it remains an empty array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
+`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) is aktiviert. Without that option, it remains an empty array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
 
 **Beispiel:**
 
@@ -80,7 +80,7 @@ const { theme } = useData()
 
 ## `useRoute` <Badge type="info" text="composable" />
 
-Returns the current route object with the following type:
+Gibt zurück the current route object with the following type:
 
 ```ts
 interface Route {
@@ -92,7 +92,7 @@ interface Route {
 
 ## `useRouter` <Badge type="info" text="composable" />
 
-Returns the VitePress router instance so you can programmatically navigate to another page.
+Gibt zurück the VitePress router instance so you can programmatically navigate to another page.
 
 ```ts
 interface Router {
@@ -134,13 +134,13 @@ router.onBeforeRouteChange = (to) => {
 }
 ```
 
-For custom themes, the same router is available from [`enhanceApp`](../guide/custom-theme#theme-interface).
+For custom themes, the same router is verfügbar from [`enhanceApp`](../guide/custom-theme#theme-interface).
 
 ## `useIcon` <Badge type="info" text="composable" />
 
 - **Type**: `(icon: MaybeRefOrGetter<string | { svg: string } | undefined>, el?: MaybeRefOrGetter<HTMLElement | null>) => ComputedRef<string | undefined>`
 
-Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Takes a fully qualified `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) and returns the class to put on the element — `vpi-<collection>-<name>`.
+Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Takes a fully qualified `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) and gibt zurück the class to put on the element — `vpi-<collection>-<name>`.
 
 During SSR the name is registered on the page's [`SSGContext`](./site-config#postrender), so the build emits the icon's styles into the generated stylesheet; in dev, icons are served on demand by the dev server from the locally installed collections. No icon is ever fetched from an external service.
 
@@ -174,9 +174,9 @@ Icons rendered only on the client (e.g. inside `<ClientOnly />`) can't be collec
 
 Prepends the configured [`base`](./site-config#base) to a given URL path. Also see [Base URL](../guide/asset-handling#base-url).
 
-## `<Content />` <Badge type="info" text="component" />
+## `<Inhalt />` <Badge type="info" text="component" />
 
-The `<Content />` component displays the rendered markdown contents. Useful [when creating your own theme](../guide/custom-theme).
+The `<Inhalt />` component displays the rendered markdown contents. Useful [when creating your own theme](../guide/custom-theme).
 
 ```vue
 <template>
@@ -191,7 +191,7 @@ The `<ClientOnly />` component renders its slot only at client side.
 
 Because VitePress applications are server-rendered in Node.js when generating static builds, any Vue usage must conform to the universal code requirements. In short, make sure to only access Browser / DOM APIs in beforeMount or mounted hooks.
 
-If you are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the `ClientOnly` component.
+Wenn du are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the `ClientOnly` component.
 
 ```vue-html
 <ClientOnly>

From 50cca2cc351b147d4da5774af7bfb991080d5ee6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:36 +0200
Subject: [PATCH 076/199] docs(de): complete German translation

---
 docs/de/reference/site-config.md | 58 ++++++++++++++++----------------
 1 file changed, 29 insertions(+), 29 deletions(-)

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
index 6eddae7a2..b7abecf5b 100644
--- a/docs/de/reference/site-config.md
+++ b/docs/de/reference/site-config.md
@@ -5,7 +5,7 @@ description: Complete reference of VitePress site configuration options includin
 
 # Site-Konfiguration
 
-Site config is where you can define the global settings of the site. App config options define settings that apply to every VitePress site, regardless of what theme it is using. For example, the base directory or the title of the site.
+Site config is where you can define the global settings of the site. App config options define settings that apply to every VitePress site, regardless of what theme it is using. Zum Beispiel, the base directory or the title of the site.
 
 ## Übersicht
 
@@ -27,7 +27,7 @@ export default {
 
 ::: details Dynamic (Async) Config
 
-If you need to dynamically generate the config, you can also default export a function. For example:
+Wenn du need to dynamically generate the config, you can also default export a function. Zum Beispiel:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -54,7 +54,7 @@ export default async () => {
 }
 ```
 
-You can also use top-level `await`. For example:
+Du kannst also use top-level `await`. Zum Beispiel:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -83,7 +83,7 @@ export default defineConfig({
 
 ### Config Intellisense
 
-Using the `defineConfig` helper will provide TypeScript-powered intellisense for config options. Assuming your IDE supports it, this should work in both JavaScript and TypeScript.
+Using the `defineConfig` helper will provide TypeScript-powered intellisense for config options. Assuming your IDE unterstützt it, this should work in both JavaScript and TypeScript.
 
 ```js
 import { defineConfig } from 'vitepress'
@@ -95,7 +95,7 @@ export default defineConfig({
 
 ### Typed Theme Config
 
-By default, `defineConfig` helper expects the theme config type from default theme:
+Standardmäßig, `defineConfig` helper expects the theme config type from default theme:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -107,7 +107,7 @@ export default defineConfig({
 })
 ```
 
-If you use a custom theme and want type checks for the theme config, you'll need to use `defineConfigWithTheme` instead, and pass the config type for your custom theme via a generic argument:
+Wenn du use a custom theme and want type checks for the theme config, you'll need to use `defineConfigWithTheme` instead, and pass the config type for your custom theme via a generic argument:
 
 ```ts
 import { defineConfigWithTheme } from 'vitepress'
@@ -124,23 +124,23 @@ export default defineConfigWithTheme<ThemeConfig>({
 
 - **Vite**
 
-  You can configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. No need to create a separate Vite config file.
+  Du kannst configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. No need to create a separate Vite config file.
 
 - **Vue**
 
-  VitePress already includes the official Vue plugin for Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). You can configure its options using the [vue](#vue) option in your VitePress config.
+  VitePress already includes the official Vue plugin for Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). Du kannst configure its options using the [vue](#vue) option in your VitePress config.
 
 - **Markdown**
 
-  You can configure the underlying [Markdown-It](https://github.com/markdown-it/markdown-it) instance using the [markdown](#markdown) option in your VitePress config.
+  Du kannst configure the underlying [Markdown-It](https://github.com/markdown-it/markdown-it) instance using the [markdown](#markdown) option in your VitePress config.
 
-### Page-Level Overrides
+### Seite-Level Overrides
 
 Some settings can be overridden for specific pages using frontmatter.
 
 See [Frontmatter-Konfiguration](./frontmatter-config) for details.
 
-### Directory-Level Overrides
+### Verzeichnis-Level Overrides
 
 Some config settings can be overridden at the directory level, allowing all pages in that directory to share settings without needing to repeat them in the frontmatter of each page.
 
@@ -148,9 +148,9 @@ This is achieved by adding a file called `config.ts` (or `.js`, `.mjs`, or `.mts
 
 Nested directories inherit settings from their parent directory, with configuration overrides being merged accordingly.
 
-The `defineAdditionalConfig` helper can be used to get TypeScript-powered intellisense for the available options, though as with `defineConfig` its use is optional.
+The `defineAdditionalConfig` helper can be used to get TypeScript-powered intellisense for the verfügbar options, though as with `defineConfig` its use is optional.
 
-For example, for a site with multiple languages we might want a different `description` for each language. We could add `es/config.ts` with the following content:
+Zum Beispiel, for a site with multiple languages we might want a different `description` for each language. We could add `es/config.ts` with the following content:
 
 ```ts
 import { defineAdditionalConfig } from 'vitepress'
@@ -174,7 +174,7 @@ Alternatively, when using the built-in i18n features, the settings for a locale
 
 Title for the site. When using the default theme, this will be displayed in the nav bar.
 
-It will also be used as the default suffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. For example with the following config and page content:
+It will also be used as the default suffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. Zum Beispiel with the following config and page content:
 
 ```ts
 export default {
@@ -193,7 +193,7 @@ The title of the page will be `Hello | My Awesome Site`.
 - Type: `string | boolean`
 - Can be overridden per page via [frontmatter](./frontmatter-config#titletemplate) or at the [directory level](#directory-level-overrides)
 
-Allows customizing each page's title suffix or the entire title. For example:
+Allows customizing each page's title suffix or the entire title. Zum Beispiel:
 
 ```ts
 export default {
@@ -206,7 +206,7 @@ export default {
 # Hello
 ```
 
-The title of the page will be `Hello | Custom Suffix`.
+The title of the page will be `Hello | Eigenes Suffix`.
 
 To completely customize how the title should be rendered, you can use the `:title` symbol in `titleTemplate`:
 
@@ -216,7 +216,7 @@ export default {
 }
 ```
 
-Here `:title` will be replaced with the text inferred from the page's first `<h1>` header. The title of the previous example page will be `Hello - Custom Suffix`.
+Here `:title` will be replaced with the text inferred from the page's first `<h1>` header. The title of the previous example page will be `Hello - Eigenes Suffix`.
 
 The option can be set to `false` to disable title suffixes.
 
@@ -386,11 +386,11 @@ export default {
 - Type: `string`
 - Default: `/`
 
-The base URL the site will be deployed at. You will need to set this if you plan to deploy your site under a sub path, for example, GitHub pages. If you plan to deploy your site to `https://foo.github.io/bar/`, then you should set base to `'/bar/'`. It should always start and end with a slash.
+The base URL the site will be deployed at. You will need to set this if you plan to deploy your site under a sub path, for example, GitHub pages. Wenn du plan to deploy your site to `https://foo.github.io/bar/`, then you should set base to `'/bar/'`. It should always start and end with a slash.
 
 The one exception is `'./'`, which produces a [relocatable build](../guide/deploy#relocatable-builds-relative-base): pages reference everything relative to their own location, so the same output works from any sub path (IPFS gateways, archives) without rebuilding and stays browsable when opened directly from the file system.
 
-The base is automatically prepended to all the URLs that start with / in other options, so you only need to specify it once.
+The base is automatisch prepended to all the URLs that start with / in other options, so you only need to specify it once.
 
 ```ts
 export default {
@@ -434,7 +434,7 @@ export default {
 - Type: `string`
 - Default: `.`
 
-The directory where your markdown pages are stored, relative to project root. Also see [Root and Source Directory](../guide/routing#root-and-source-directory).
+The directory where your markdown pages are stored, relative to project root. Also see [Root and Quelle Verzeichnis](../guide/routing#root-and-source-directory).
 
 ```ts
 export default {
@@ -508,7 +508,7 @@ Only production builds are affected. `vitepress preview` serves a root-absolute
 - Type: `number`
 - Default: `undefined`
 
-Spreads the generated assets over this many subdirectories of [`assetsDir`](#assetsdir), `assets/0/` through `assets/N-1/`, instead of one flat directory. Use it when the host caps the number of files per directory; Netlify, for example, allows 54,000. Each page emits two JavaScript files, so a site with 60,000 pages needs at least three shards, plus some headroom because files are distributed by a hash of their name.
+Spreads the generated assets over this many subdirectories of [`assetsDir`](#assetsdir), `assets/0/` through `assets/N-1/`, instead of one flat directory. Use it when the host caps the number of files per directory; Netlify, for example, ermöglicht 54,000. Each page emits two JavaScript files, so a site with 60,000 pages needs at least three shards, plus some headroom because files are distributed by a hash of their name.
 
 ```ts
 export default {
@@ -539,7 +539,7 @@ export default {
 - Type: `string`
 - Default: `./.vitepress/cache`
 
-The directory for cache files, relative to [project root](../guide/routing#root-and-source-directory). See also: [cacheDir](https://vite.dev/config/shared-options.html#cachedir).
+The directory for cache files, relative to [project root](../guide/routing#root-and-source-directory). Siehe auch: [cacheDir](https://vite.dev/config/shared-options.html#cachedir).
 
 ```ts
 export default {
@@ -614,7 +614,7 @@ This option injects an inline script that restores users settings from local sto
 
 Whether to get the last updated timestamp for each page using Git. The timestamp will be included in each page's page data, accessible via [`useData`](./runtime-api#usedata).
 
-When using the default theme, enabling this option will display each page's last updated time. You can customize the text via [`themeConfig.lastUpdated.text`](./default-theme-config#lastupdated) option.
+When using the default theme, enabling this option will display each page's last updated time. Du kannst customize the text via [`themeConfig.lastUpdated.text`](./default-theme-config#lastupdated) option.
 
 ## Customization
 
@@ -622,7 +622,7 @@ When using the default theme, enabling this option will display each page's last
 
 - Type: `MarkdownOption`
 
-Configure Markdown parser options. VitePress uses [Markdown-it](https://github.com/markdown-it/markdown-it) as the parser, and [Shiki](https://github.com/shikijs/shiki) to highlight language syntax. Inside this option, you may pass various Markdown related options to fit your needs.
+Konfigurieren Markdown parser options. VitePress uses [Markdown-it](https://github.com/markdown-it/markdown-it) as the parser, and [Shiki](https://github.com/shikijs/shiki) to highlight language syntax. Inside this option, you may pass various Markdown related options to fit your needs.
 
 ```js
 export default {
@@ -630,9 +630,9 @@ export default {
 }
 ```
 
-Check the [type declaration and jsdocs](https://github.com/vuejs/vitepress/blob/main/src/node/markdown/markdown.ts) for all the options available.
+Check the [type declaration and jsdocs](https://github.com/vuejs/vitepress/blob/main/src/node/markdown/markdown.ts) for all the options verfügbar.
 
-Set `markdown.headers` to `true` or pass [`@mdit-vue/plugin-headers`](https://github.com/mdit-vue/mdit-vue/tree/main/packages/plugin-headers) options to collect headings into [`useData().page.headers`](./runtime-api#usedata). This option is disabled by default.
+Set `markdown.headers` to `true` or pass [`@mdit-vue/plugin-headers`](https://github.com/mdit-vue/mdit-vue/tree/main/packages/plugin-headers) options to collect headings into [`useData().page.headers`](./runtime-api#usedata). This option is deaktiviert by default.
 
 ### vite
 
@@ -712,7 +712,7 @@ interface SSGContext {
 
 - Type: `(context: TransformContext) => Awaitable<HeadConfig[]>`
 
-`transformHead` is a build hook to add extra tags to the `<head>` of each page. It allows you to add head entries that cannot be statically added to your VitePress config. You only need to return extra entries, they will be merged automatically with the existing ones.
+`transformHead` is a build hook to add extra tags to the `<head>` of each page. It ermöglicht you to add head entries that cannot be statically added to your VitePress config. You only need to zurückgeben extra entries, they will be merged automatisch with the existing ones.
 
 ::: warning
 Don't mutate anything inside the `context`.
@@ -798,10 +798,10 @@ export default {
 
 - Type: `(pageData: PageData, context: TransformPageContext) => Awaitable<Partial<PageData> | { [key: string]: any } | void>`
 
-`transformPageData` is a hook to transform the `pageData` of each page. You can directly mutate `pageData` or return changed values which will be merged into the page data.
+`transformPageData` is a hook to transform the `pageData` of each page. Du kannst directly mutate `pageData` or zurückgeben changed values which will be merged into the page data.
 
 ::: warning
-Don't mutate anything inside the `context` and be careful that this might impact the performance of dev server, especially if you have some network requests or heavy computations (like generating images) in the hook. You can check for `process.env.NODE_ENV === 'production'` for conditional logic.
+Don't mutate anything inside the `context` and be careful that this might impact the performance of dev server, especially if you have some network requests or heavy computations (like generating images) in the hook. Du kannst check for `process.env.NODE_ENV === 'production'` for conditional logic.
 :::
 
 ```ts

From 261bc5bf2a9e2bd0835fb89fa0f7fd0c27dd75c7 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:47:38 +0200
Subject: [PATCH 077/199] docs(de): complete German translation

---
 docs/de/config.ts | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/config.ts b/docs/de/config.ts
index 299606a21..767a8c066 100644
--- a/docs/de/config.ts
+++ b/docs/de/config.ts
@@ -85,7 +85,7 @@ export default defineAdditionalConfig({
 })
 
 function nav(): DefaultTheme.NavItem[] {
-  return [
+  zurückgeben [
     {
       text: 'Guide',
       link: 'de/guide/what-is-vitepress',
@@ -117,7 +117,7 @@ function nav(): DefaultTheme.NavItem[] {
 }
 
 function sidebarGuide(): DefaultTheme.SidebarItem[] {
-  return [
+  zurückgeben [
     {
       text: 'Einführung',
       collapsed: false,
@@ -166,7 +166,7 @@ function sidebarGuide(): DefaultTheme.SidebarItem[] {
 }
 
 function sidebarReference(): DefaultTheme.SidebarItem[] {
-  return [
+  zurückgeben [
     {
       text: 'Referenz',
       base: 'de/reference/',
@@ -183,7 +183,7 @@ function sidebarReference(): DefaultTheme.SidebarItem[] {
             { text: 'Navigation', link: 'nav' },
             { text: 'Seitenleiste', link: 'sidebar' },
             { text: 'Startseite', link: 'home-page' },
-            { text: 'Footer', link: 'footer' },
+            { text: 'Fußzeile', link: 'footer' },
             { text: 'Layout', link: 'layout' },
             { text: 'Badge', link: 'badge' },
             { text: 'Team-Seite', link: 'team-page' },
@@ -200,7 +200,7 @@ function sidebarReference(): DefaultTheme.SidebarItem[] {
 }
 
 function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
-  return {
+  zurückgeben {
     translations: {
       button: {
         buttonText: 'Suche',

From 9dfd68a8614c490dd7dcdc1bda2e71880460d58b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:50:01 +0200
Subject: [PATCH 078/199] =?UTF-8?q?docs(de):=20vollst=C3=A4ndige=20=C3=9Cb?=
 =?UTF-8?q?ersetzung=20fortsetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/frontmatter.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
index be1e481d2..2639652f8 100644
--- a/docs/de/guide/frontmatter.md
+++ b/docs/de/guide/frontmatter.md
@@ -1,53 +1,53 @@
 ---
-description: Erfahre how to use YAML frontmatter in VitePress Markdown files to control page-level metadata and behavior.
+description: Erfahre, wie du YAML-Frontmatter in VitePress-Markdown-Dateien verwendest, um Metadaten und Verhalten einzelner Seiten zu steuern.
 ---
 
 # Frontmatter
 
 ## Verwendung
 
-VitePress unterstützt YAML frontmatter in all Markdown files, parsing them mit [gray-matter](https://github.com/jonschlinkert/gray-matter). The frontmatter must be at the top of the Markdown file (bevor any elements including `<script>` tags), and must take the form of valid YAML set zwischen triple-dashed lines. Beispiel:
+VitePress unterstützt YAML frontmatter in allen Markdown-Dateien und verarbeitet sie mit [gray-matter](https://github.com/jonschlinkert/gray-matter). Das Frontmatter muss am Anfang der Markdown-Datei stehen (vor allen Elementen einschließlich `<script>`-Tags) und aus gültigem YAML zwischen drei Bindestrichzeilen bestehen. Beispiel:
 
 ```md
 ---
-title: Docs with VitePress
+title: Dokumentation mit VitePress
 editLink: true
 ---
 ```
 
-Many site or default theme config options have corresponding options in frontmatter. Du kannst use frontmatter to override specific behavior for the current page only. For details, see [Frontmatter Config Referenz](../reference/frontmatter-config).
+Viele Optionen der Website- oder Standard-Theme-Konfiguration besitzen entsprechende Optionen im Frontmatter. Du kannst Frontmatter verwenden, um bestimmtes Verhalten nur für die aktuelle Seite zu überschreiben. Einzelheiten findest du in [Frontmatter Config Referenz](../reference/frontmatter-config).
 
-Du kannst also define custom frontmatter data of your own, to be verwendet in dynamic Vue expressions on the page.
+Du kannst außerdem eigene Frontmatter-Daten definieren und sie in dynamischen Vue-Ausdrücken auf der Seite verwenden.
 
-## Accessing Frontmatter Data
+## Zugriff auf Frontmatter-Daten
 
-Frontmatter data can be accessed via the special `$frontmatter` global variable:
+Auf Frontmatter-Daten kannst du über die spezielle globale Variable `$frontmatter` zugreifen:
 
-Here's an example of how you could use it in your Markdown file:
+Hier ist ein Beispiel dafür, wie du sie in deiner Markdown-Datei verwenden kannst:
 
 ```md
 ---
-title: Docs with VitePress
+title: Dokumentation mit VitePress
 editLink: true
 ---
 
 # {{ $frontmatter.title }}
 
-Guide content
+Inhalt der Anleitung
 ```
 
-Property accesses like `{{ $frontmatter.title }}` are resolved while the Markdown is rendered, so the value also ends up in the local search index, in [content loader](./data-loading#createcontentloader) output, in heading anchors - the heading above gets `id="docs-mit-vitepress"` - and in link targets written ohne spaces around the expression, like `[text]({{$frontmatter.link}})`. Other expressions are evaluated by Vue at runtime as usual, and wrapping an expression in [`v-pre`](./Verwendung-vue#escaping) shows it literally.
+Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [content loader](./data-loading#createcontentloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
 
-Du kannst also access current page's frontmatter data in `<script setup>` mit the [`useData()`](../reference/runtime-api#usedata) helper.
+Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#usedata) -Helper zugreifen.
 
-## Alternative Frontmatter Formats
+## Alternative Frontmatter-Formate
 
-VitePress also unterstützt JSON frontmatter syntax, starting and ending in curly braces:
+VitePress unterstützt auch die JSON-Frontmatter-Syntax, die mit geschweiften Klammern beginnt und endet:
 
 ```json
 ---
 {
-  "title": "Blogging Like a Hacker",
+  "title": "Bloggen wie ein Hacker",
   "editLink": true
 }
 ---

From 43b8ae57bebedb9c8edd13cc7a39d12b2f241136 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:50:04 +0200
Subject: [PATCH 079/199] =?UTF-8?q?docs(de):=20vollst=C3=A4ndige=20=C3=9Cb?=
 =?UTF-8?q?ersetzung=20fortsetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/getting-started.md | 70 ++++++++++++++++----------------
 1 file changed, 35 insertions(+), 35 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index d42f83d2c..be8c74626 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -1,23 +1,23 @@
 ---
-description: Get up and running mit VitePress. Erfahre how to install, scaffold, and start developing your documentation site.
+description: Starte mit VitePress. Erfahre, wie du deine Dokumentations-Website installierst, einrichtest und mit der Entwicklung beginnst.
 ---
 
 # Erste Schritte
 
 ## Online ausprobieren
 
-Du kannst try VitePress directly in your browser on [StackBlitz](https://vitepress.new).
+Du kannst VitePress direkt im Browser auf [StackBlitz](https://vitepress.new).
 
 ## Installation
 
 ### Voraussetzungen
 
-- [Node.js](https://nodejs.org/) version 22 or higher.
-- Terminal for accessing VitePress via its command line interface (CLI).
-- Text Editor mit [Markdown](https://en.wikipedia.org/wiki/Markdown) syntax Unterstützung.
-  - [VSCode](https://code.visualstudio.com/) is recommended, along mit the [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar).
+- [Node.js](https://nodejs.org/) Version 22 oder höher.
+- Ein Terminal, um über die Kommandozeilenschnittstelle (CLI) auf VitePress zuzugreifen.
+- Ein Texteditor mit [Markdown](https://en.wikipedia.org/wiki/Markdown) Syntax-Unterstützung.
+  - [VSCode](https://code.visualstudio.com/) wird zusammen mit der [official Vue extension](https://marketplace.visualstudio.com/items?itemName=Vue.volar).
 
-VitePress can be verwendet on its own, or be installed in an existing project. In both cases, you can install it mit:
+VitePress kann eigenständig verwendet oder in einem bestehenden Projekt installiert werden. In beiden Fällen kannst du es mit folgendem Befehl installieren:
 
 ::: code-group
 
@@ -43,15 +43,15 @@ $ deno add -D vitepress@next
 
 :::
 
-::: tip NOTE
+::: tip Hinweis
 
-VitePress is an ESM-only package. Don't use `require()` to import it, and make sure your nearest `package.json` contains `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Refer to [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) for more details. Also, innerhalb async CJS contexts, you can use `await import('vitepress')` instead.
+VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` instead.
 
 :::
 
 ### Einrichtungsassistent
 
-VitePress ships mit a command line setup wizard that will help you scaffold a basic project. After installation, start the wizard by running:
+VitePress enthält einen Einrichtungsassistenten für die Kommandozeile, der dir beim Erstellen eines grundlegenden Projekts hilft. Starte den Assistenten nach der Installation mit:
 
 ::: code-group
 
@@ -73,19 +73,19 @@ $ bun vitepress init
 
 :::
 
-You will be greeted mit a few simple questions:
+Der Assistent stellt dir einige einfache Fragen:
 
 <<< @/snippets/init.ansi
 
-::: tip Vue as Peer Dependency
-Wenn du intend to perform customization that verwendet Vue components or APIs, you should also explicitly install `vue` as a dependency.
+::: tip Vue als Peer-Abhängigkeit
+Wenn du Anpassungen vornehmen möchtest, die Vue-Komponenten oder APIs verwenden, solltest du `vue` zusätzlich ausdrücklich als Abhängigkeit installieren.
 :::
 
 ## Dateistruktur
 
-Wenn du are building a standalone VitePress site, you can scaffold the site in your current directory (`./`). However, if you are installing VitePress in an existing project alongside other source code, it is recommended to scaffold the site in a nested directory (e.g. `./docs`) so that it is separate von the rest of the project.
+Wenn du eine eigenständige VitePress-Website erstellst, kannst du sie im aktuellen Verzeichnis (`./`). Wenn du VitePress jedoch zusammen mit anderem Quellcode in einem bestehenden Projekt installierst, empfiehlt es sich, die Website in einem Unterverzeichnis (e.g. `./docs`) damit sie vom restlichen Projekt getrennt ist.
 
-Assuming you chose to scaffold the VitePress project in `./docs`, the generated file structure should look like this:
+Angenommen, du hast das VitePress-Projekt in `./docs`, Die erzeugte Dateistruktur sollte dann so aussehen:
 
 ```
 .
@@ -98,41 +98,41 @@ Assuming you chose to scaffold the VitePress project in `./docs`, the generated
 └─ package.json
 ```
 
-The `docs` directory is considered the **project root** of the VitePress site. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionale Anpassungen des Themes reserviert.
 
 ::: tip
-Standardmäßig, VitePress stores its dev server cache in `.vitepress/cache`, and the production build output in `.vitepress/dist`. If Verwendung Git, you should add them to your `.gitignore` file. These locations can also be [konfiguriert](../reference/site-config#outdir).
+Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can also be [konfiguriert](../reference/site-config#outdir).
 :::
 
 ### Die Konfigurationsdatei
 
-The config file (`.vitepress/config.js`) ermöglicht you to customize various aspects of your VitePress site, mit the most basic options being the title and description of the site:
+Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic options being the title and description of the site:
 
 ```js [.vitepress/config.js]
 export default {
-  // site-level options
+  // Optionen auf Website-Ebene
   title: 'VitePress',
   description: 'Just playing around.',
 
   themeConfig: {
-    // theme-level options
+    // Optionen auf Theme-Ebene
   }
 }
 ```
 
-Du kannst also configure the behavior of the theme via the `themeConfig` option. Consult the [Config Referenz](../reference/site-config) for full details on all config options.
+Du kannst das Verhalten des Themes außerdem über die `themeConfig` option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on all config options.
 
 ### Quelldateien
 
-Markdown files außerhalb the `.vitepress` directory are considered **source files**.
+Markdown-Dateien außerhalb des Verzeichnisses `.vitepress` gelten als **Quelldateien**.
 
-VitePress verwendet **file-based routing**: each `.md` file is compiled in a corresponding `.html` file mit the same path. Zum Beispiel, `index.md` will be compiled in `index.html`, and can be visited at the root path `/` of the resulting VitePress site.
+VitePress verwendet **file-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
 
-VitePress also stellt bereit the ability to generate clean URLs, rewrite paths, and dynamically generate pages. These will be covered in the [Routing Anleitung](./routing).
+VitePress bietet außerdem die Möglichkeit, saubere URLs zu erzeugen, Pfade umzuschreiben und Seiten dynamisch zu generieren. Diese Funktionen werden in der [Routing Anleitung](./routing).
 
 ## Loslegen
 
-The tool should have also injected the following npm scripts to your `package.json` if you allowed it to do so während the setup process:
+Wenn du dies während der Einrichtung zugelassen hast, sollte das Tool außerdem die folgenden npm-Skripte in deine `package.json` if you allowed it to do so während the setup process:
 
 ```json [package.json]
 {
@@ -146,7 +146,7 @@ The tool should have also injected the following npm scripts to your `package.js
 }
 ```
 
-The `docs:dev` script will start a local dev server mit instant hot updates. Run it mit the following command:
+Das Skript `docs:dev` startet einen lokalen Entwicklungsserver mit sofortigen Hot-Updates. Starte ihn mit folgendem Befehl:
 
 ::: code-group
 
@@ -168,7 +168,7 @@ $ bun run docs:dev
 
 :::
 
-Instead of npm scripts, you can also invoke VitePress directly mit:
+Statt npm-Skripte zu verwenden, kannst du VitePress auch direkt aufrufen:
 
 ::: code-group
 
@@ -190,18 +190,18 @@ $ bun vitepress dev docs
 
 :::
 
-More command line usage is documented in the [CLI Referenz](../reference/cli).
+Weitere Informationen zur Verwendung der Kommandozeile findest du in der [CLI Referenz](../reference/cli).
 
-The dev server should be running at `http://localhost:5173`. Visit the URL in your browser to see your new site in action!
+The dev server should be running at `http://localhost:5173`. Öffne die URL in deinem Browser, um deine neue Website zu sehen.
 
-## What's Weiter?
+## Wie geht es weiter?
 
-- To better understand how markdown files are mapped to generated HTML, proceed to the [Routing Anleitung](./routing).
+- Um besser zu verstehen, wie Markdown-Dateien auf erzeugtes HTML abgebildet werden, fahre mit der [Routing Anleitung](./routing).
 
-- To discover more about what you can do on the page, such as writing markdown content or Verwendung Vue Components, refer to the "Schreiben" section of the guide. A great place to start would be to learn about [Markdown Extensions](./markdown).
+- Um mehr darüber zu erfahren, was du auf einer Seite tun kannst, etwa Markdown-Inhalte schreiben oder Vue-Komponenten verwenden, lies den Abschnitt „Schreiben“ der Anleitung. Ein guter Ausgangspunkt sind die [Markdown Extensions](./markdown).
 
-- To explore the features provided by the default documentation theme, check out the [Standard-Theme Config Referenz](../reference/default-theme-config).
+- Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-theme-config).
 
-- Wenn du want to further customize the appearance of your site, explore how to either [Extend the Standard-Theme](./extending-default-theme) or [Build a Eigenes Theme](./custom-theme).
+- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
 
-- Once your documentation site takes shape, make sure to read the [Bereitstellung Anleitung](./deploy).
+- Sobald deine Dokumentations-Website Gestalt annimmt, solltest du die [Bereitstellung Anleitung](./deploy).

From 82245d812941983fa79bb7a3ea7fa496cfbdfa86 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:50:41 +0200
Subject: [PATCH 080/199] =?UTF-8?q?docs(de):=20vollst=C3=A4ndige=20=C3=9Cb?=
 =?UTF-8?q?ersetzung=20fortsetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/custom-theme.md | 114 +++++++++++++++++-----------------
 1 file changed, 57 insertions(+), 57 deletions(-)

diff --git a/docs/de/guide/custom-theme.md b/docs/de/guide/custom-theme.md
index 21cf4e264..8cfd75803 100644
--- a/docs/de/guide/custom-theme.md
+++ b/docs/de/guide/custom-theme.md
@@ -1,67 +1,67 @@
 ---
-description: Create and use a custom theme in VitePress to fully control the look and feel of your site.
+description: Erstelle und verwende ein eigenes Theme in VitePress, um das Erscheinungsbild und Verhalten deiner Website vollständig zu steuern.
 ---
 
-# Using a Custom Theme
+# Ein eigenes Theme verwenden
 
-## Theme Resolving
+## Theme-Auflösung
 
-You can enable a custom theme by creating a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (the "theme entry file"):
+Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (die „Theme-Einstiegsdatei“):
 
 ```
 .
-├─ docs                # project root
+├─ docs                # Projektstammverzeichnis
 │  ├─ .vitepress
 │  │  ├─ theme
-│  │  │  └─ index.js   # theme entry
-│  │  └─ config.js     # config file
+│  │  │  └─ index.js   # Theme-Einstiegsdatei
+│  │  └─ config.js     # Konfigurationsdatei
 │  └─ index.md
 └─ package.json
 ```
 
-VitePress will always use the custom theme instead of the default theme when it detects presence of a theme entry file. You can, however, [extend the default theme](./extending-default-theme) to perform advanced customizations on top of it.
+VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend the default theme](./extending-default-theme) to perform advanced customizations on top of it.
 
-## Theme Interface
+## Theme-Schnittstelle
 
-A VitePress custom theme is defined as an object with the following interface:
+Ein eigenes VitePress-Theme wird als Objekt mit der folgenden Schnittstelle definiert:
 
 ```ts
 interface Theme {
   /**
-   * Root layout component for every page
+   * Stamm-Layout-Komponente für jede Seite
    * @required
    */
   Layout: Component
   /**
-   * Enhance Vue app instance
+   * Vue-App-Instanz erweitern
    * @optional
    */
   enhanceApp?: (ctx: EnhanceAppContext) => Awaitable<void>
   /**
-   * Runs inside the root component's `setup()`
+   * Wird innerhalb von `setup()` der Stammkomponente ausgeführt
    * @optional
    */
   setup?: () => void
   /**
-   * Extend another theme, calling its `enhanceApp` and `setup` before ours
+   * Ein anderes Theme erweitern und dessen `enhanceApp` und `setup` vor unserem aufrufen
    * @optional
    */
   extends?: Theme
 }
 
 interface EnhanceAppContext {
-  app: App // Vue app instance
-  router: Router // VitePress router instance
-  siteData: Ref<SiteData> // Site-level metadata
+  app: App // Vue-App-Instanz
+  router: Router // VitePress-Router-Instanz
+  siteData: Ref<SiteData> // Metadaten auf Website-Ebene
 }
 ```
 
-The theme entry file should export the theme as its default export:
+Die Theme-Einstiegsdatei sollte das Theme als Standardexport exportieren:
 
 ```js [.vitepress/theme/index.js]
 
-// You can directly import Vue files in the theme entry
-// VitePress is pre-configured with @vitejs/plugin-vue.
+// Vue-Dateien können direkt in der Theme-Einstiegsdatei importiert werden
+// VitePress ist bereits mit @vitejs/plugin-vue vorkonfiguriert.
 import Layout from './Layout.vue'
 
 export default {
@@ -73,27 +73,27 @@ export default {
 }
 ```
 
-The `enhanceApp` hook allows you to access the [Vue app instance](https://vuejs.org/api/application.html) and other runtime data, which can be used to [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
+Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
 
-The `router` value is the same VitePress router instance returned by [`useRouter()`](../reference/runtime-api#userouter). To listen for route changes, assign handlers on the router:
+Der Wert `router` ist dieselbe VitePress-Router-Instanz, die von [`useRouter()`](../reference/runtime-api#userouter). Um auf Routenänderungen zu reagieren, weist du dem Router Handler zu:
 
 ```ts [.vitepress/theme/index.ts]
 export default {
   enhanceApp({ router }) {
     router.onBeforeRouteChange = (to) => {
-      console.log('navigating to', to)
+      console.log('navigiere zu', to)
     }
 
     router.onAfterRouteChange = (to) => {
-      console.log('navigated to', to)
+      console.log('weitergeleitet zu', to)
     }
   }
 }
 ```
 
-Return `false` from `onBeforeRouteChange` or `onBeforePageLoad` to cancel navigation.
+Gib von `onBeforeRouteChange` or `onBeforePageLoad` `false` zurück, um die Navigation abzubrechen.
 
-The `setup` hook runs inside the root component's `setup()`, so Composition API calls (`onMounted`, `watch`, composables, ...) work there without wrapping the layout component:
+Der `setup`-Hook wird innerhalb von `setup()` der Stammkomponente ausgeführt. Deshalb funktionieren Aufrufe der Composition API (`onMounted`, `watch`, composables, ...) dort ohne dass du die Layout-Komponente umschließen musst:
 
 ```ts [.vitepress/theme/index.ts]
 import { watch } from 'vue'
@@ -111,26 +111,26 @@ export default {
 }
 ```
 
-With `extends`, each theme's `setup` runs base-first, like `enhanceApp`. It also runs during SSR/SSG rendering, so keep browser-only work inside `onMounted`.
+Mit `extends` wird das `setup` jedes Themes wie bei `enhanceApp` von der Basis ausgehend ausgeführt. Es läuft außerdem während des SSR-/SSG-Renderings. Browser-spezifische Arbeit sollte daher innerhalb von `onMounted` bleiben.
 
-The default export is the only contract for a custom theme, and only the `Layout` property is required. So technically, a VitePress theme can be as simple as a single Vue component.
+Der Standardexport ist der einzige Vertrag für ein eigenes Theme, und nur die Eigenschaft `Layout` ist erforderlich. Technisch kann ein VitePress-Theme daher aus nur einer einzigen Vue-Komponente bestehen.
 
-Inside your layout component, it works just like a normal Vite + Vue 3 application. Do note the theme also needs to be [SSR-compatible](./ssr-compat).
+Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Beachte, dass das Theme außerdem [SSR-compatible](./ssr-compat).
 
-## Building a Layout
+## Ein Layout erstellen
 
-The most basic layout component needs to contain a [`<Content />`](../reference/runtime-api#content) component:
+Die einfachste Layout-Komponente muss eine [`<Content />`](../reference/runtime-api#content) -Komponente enthalten:
 
 ```vue [.vitepress/theme/Layout.vue]
 <template>
-  <h1>Custom Layout!</h1>
+  <h1>Eigenes Layout!</h1>
 
-  <!-- this is where markdown content will be rendered -->
+  <!-- Hier wird der Markdown-Inhalt gerendert -->
   <Content />
 </template>
 ```
 
-The above layout simply renders every page's markdown as HTML. The first improvement we can add is to handle 404 errors:
+Das obige Layout rendert den Markdown-Inhalt jeder Seite einfach als HTML. Als erste Verbesserung können wir die Behandlung von 404-Fehlern hinzufügen:
 
 ```vue{1-4,9-12}
 <script setup>
@@ -139,10 +139,10 @@ const { page } = useData()
 </script>
 
 <template>
-  <h1>Custom Layout!</h1>
+  <h1>Eigenes Layout!</h1>
 
   <div v-if="page.isNotFound">
-    Custom 404 page!
+    Eigene 404-Seite!
   </div>
   <Content v-else />
 </template>
@@ -165,19 +165,19 @@ const { page, frontmatter } = useData()
 </script>
 
 <template>
-  <h1>Custom Layout!</h1>
+  <h1>Eigenes Layout!</h1>
 
   <div v-if="page.isNotFound">
-    Custom 404 page!
+    Eigene 404-Seite!
   </div>
   <div v-if="frontmatter.layout === 'home'">
-    Custom home page!
+    Eigene Startseite!
   </div>
   <Content v-else />
 </template>
 ```
 
-You can, of course, split the layout into more components:
+Natürlich kannst du das Layout auch auf mehrere Komponenten aufteilen:
 
 ```vue{3-5,12-15}
 <script setup>
@@ -190,7 +190,7 @@ const { page, frontmatter } = useData()
 </script>
 
 <template>
-  <h1>Custom Layout!</h1>
+  <h1>Eigenes Layout!</h1>
 
   <NotFound v-if="page.isNotFound" />
   <Home v-if="frontmatter.layout === 'home'" />
@@ -198,27 +198,27 @@ const { page, frontmatter } = useData()
 </template>
 ```
 
-Consult the [Runtime API Reference](../reference/runtime-api) for everything available in theme components. In addition, you can leverage [Build-Time Data Loading](./data-loading) to generate data-driven layout - for example, a page that lists all blog posts in the current project.
+In der [Runtime API Reference](../reference/runtime-api) findest du alles, was in Theme-Komponenten verfügbar ist. Zusätzlich kannst du [Build-Time Data Loading](./data-loading) nutzen, um datenbasierte Layouts zu erzeugen – beispielsweise eine Seite, die alle Blogbeiträge des aktuellen Projekts auflistet.
 
-## Distributing a Custom Theme
+## Ein eigenes Theme verteilen
 
-The easiest way to distribute a custom theme is by providing it as a [template repository on GitHub](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository).
+Am einfachsten verteilst du ein eigenes Theme, indem du es als [template repository on GitHub](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-template-repository).
 
-If you wish to distribute the theme as an npm package, follow these steps:
+Wenn du das Theme als npm-Paket verteilen möchtest, gehe folgendermaßen vor:
 
-1. Export the theme object as the default export in your package entry.
+1. Exportiere das Theme-Objekt als Standardexport des Paketeintrags.
 
-2. If applicable, export your theme config type definition as `ThemeConfig`.
+2. Falls zutreffend, exportiere die Typdefinition deiner Theme-Konfiguration als `ThemeConfig`.
 
-3. If your theme requires adjusting the VitePress config, export that config under a package sub-path (e.g. `my-theme/config`) so the user can extend it.
+3. Wenn dein Theme Anpassungen an der VitePress-Konfiguration erfordert, exportiere diese Konfiguration unter einem Paket-Unterpfad (e.g. `my-theme/config`) damit Benutzer sie erweitern können.
 
-4. Document the theme config options (both via config file and frontmatter).
+4. Dokumentiere die Optionen der Theme-Konfiguration sowohl über die Konfigurationsdatei als auch über Frontmatter.
 
-5. Provide clear instructions on how to consume your theme (see below).
+5. Stelle klare Anweisungen zur Verwendung deines Themes bereit (siehe unten).
 
-## Consuming a Custom Theme
+## Ein eigenes Theme verwenden
 
-To consume an external theme, import and re-export it from the custom theme entry:
+Um ein externes Theme zu verwenden, importiere und exportiere es aus der Theme-Einstiegsdatei erneut:
 
 ```js [.vitepress/theme/index.js]
 import Theme from 'awesome-vitepress-theme'
@@ -226,7 +226,7 @@ import Theme from 'awesome-vitepress-theme'
 export default Theme
 ```
 
-If the theme needs to be extended:
+Wenn das Theme erweitert werden muss:
 
 ```js [.vitepress/theme/index.js]
 import Theme from 'awesome-vitepress-theme'
@@ -239,18 +239,18 @@ export default {
 }
 ```
 
-If the theme requires special VitePress config, you will need to also extend it in your own config:
+Wenn das Theme eine spezielle VitePress-Konfiguration benötigt, musst du sie auch in deiner eigenen Konfiguration erweitern:
 
 ```ts [.vitepress/config.ts]
 import baseConfig from 'awesome-vitepress-theme/config'
 
 export default {
-  // extend theme base config (if needed)
+  // Basis-Konfiguration des Themes erweitern (falls erforderlich)
   extends: baseConfig
 }
 ```
 
-Finally, if the theme provides types for its theme config:
+Wenn das Theme schließlich Typen für seine Theme-Konfiguration bereitstellt:
 
 ```ts [.vitepress/config.ts]
 import baseConfig from 'awesome-vitepress-theme/config'
@@ -260,7 +260,7 @@ import type { ThemeConfig } from 'awesome-vitepress-theme'
 export default defineConfig<ThemeConfig>({
   extends: baseConfig,
   themeConfig: {
-    // Type is `ThemeConfig`
+    // Typ ist `ThemeConfig`
   }
 })
 ```

From c5a08f34a7fa2a60aca2460c64e56bcb6b738f57 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:50:44 +0200
Subject: [PATCH 081/199] =?UTF-8?q?docs(de):=20vollst=C3=A4ndige=20=C3=9Cb?=
 =?UTF-8?q?ersetzung=20fortsetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/data-loading.md | 114 +++++++++++++++++-----------------
 1 file changed, 57 insertions(+), 57 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index 0b81fd98b..32aa63fb6 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -1,16 +1,16 @@
 ---
-description: Load arbitrary data at build time Verwendung VitePress data loaders and import it von pages or components.
+description: Lade beliebige Daten zur Build-Zeit mit VitePress Data Loadern und importiere sie in Seiten oder Komponenten.
 ---
 
-# Build-Time Daten laden
+# Daten zur Build-Zeit laden
 
-VitePress stellt bereit a feature genannt **data loaders** that ermöglicht you to load arbitrary data and import it von pages or components. The data loading is executed **only at build time**: the resulting data will be serialized as JSON in the final JavaScript bundle.
+VitePress stellt eine Funktion namens **Data Loader** bereit, mit der du beliebige Daten laden und in Seiten oder Komponenten importieren kannst. Das Laden der Daten wird **nur zur Build-Zeit** ausgeführt: Die resultierenden Daten werden als JSON im endgültigen JavaScript-Bundle serialisiert.
 
-Data loaders can be verwendet to fetch remote data, or generate metadata based on local files. Zum Beispiel, you can use data loaders to parse all your local API pages and automatisch generate an index of all API entries.
+Data Loader können verwendet werden, um entfernte Daten abzurufen oder Metadaten auf Grundlage lokaler Dateien zu erzeugen. Zum Beispiel kannst du damit deine lokalen API-Seiten analysieren und automatisch einen Index aller API-Einträge erzeugen.
 
-## Basic Verwendung
+## Grundlegende Verwendung
 
-A data loader file must end mit either `.data.js` or `.data.ts`. The file should provide a default export of an object mit the `load()` method:
+Eine Data-Loader-Datei muss mit `.data.js` or `.data.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
 
 ```js [example.data.js]
 export default {
@@ -22,9 +22,9 @@ export default {
 }
 ```
 
-The loader module is evaluated only in Node.js, so you can import Node APIs and npm dependencies as needed.
+Das Loader-Modul wird nur in Node.js ausgewertet. Du kannst daher nach Bedarf Node-APIs und npm-Abhängigkeiten importieren.
 
-Du kannst then import data von this file in `.md` pages and `.vue` components Verwendung the `data` named export:
+Du kannst anschließend Daten aus dieser Datei in `.md`-Seiten und `.vue`-Komponenten mit dem `data` named export:
 
 ```vue
 <script setup>
@@ -34,7 +34,7 @@ import { data } from './example.data.js'
 <pre>{{ data }}</pre>
 ```
 
-Output:
+Ausgabe:
 
 ```json
 {
@@ -42,26 +42,26 @@ Output:
 }
 ```
 
-You'll notice the data loader itself does not export the `data`. It is VitePress calling the `load()` method behind the scenes and implicitly exposing the result via the `data` named export.
+Du wirst feststellen, dass der Data Loader selbst `data` nicht exportiert. Stattdessen ruft VitePress im Hintergrund die Methode `load()` auf und stellt das Ergebnis implizit über den benannten Export `data` bereit.
 
-This works even if the loader is async:
+Das funktioniert auch, wenn der Loader asynchron ist:
 
 ```js
 export default {
   async load() {
-    // fetch remote data
+    // entfernte Daten abrufen
     return (await fetch('...')).json()
   }
 }
 ```
 
-## Data von Local Dateien
+## Daten aus lokalen Dateien
 
-Wenn du need to generate data based on local files, you should use the `watch` option in the data loader so that changes made to these files can trigger hot updates.
+Wenn du Daten auf Grundlage lokaler Dateien erzeugen musst, solltest du die `watch` Option im Data Loader verwenden, damit Änderungen an diesen Dateien Hot-Updates auslösen können.
 
-The `watch` option is also convenient in that you can use [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match multiple files. The patterns can be relative to the loader file itself, and the `load()` function will receive the matched files as absolute paths.
+Die Option `watch` ist außerdem praktisch, weil du [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) verwenden kannst, um mehrere Dateien zu finden. Die Muster können relativ zur Loader-Datei angegeben werden, und die Funktion `load()` erhält die gefundenen Dateien als absolute Pfade.
 
-The following example shows loading CSV files and transforming them in JSON Verwendung [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Because this file only executes at build time, you will not be shipping the CSV parser to the client!
+Das folgende Beispiel zeigt, wie CSV-Dateien geladen und mit [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Da diese Datei nur zur Build-Zeit ausgeführt wird, wird der CSV-Parser nicht an den Client ausgeliefert!
 
 ```js
 import fs from 'node:fs'
@@ -70,9 +70,9 @@ import { parse } from 'csv-parse/sync'
 export default {
   watch: ['./data/*.csv'],
   load(watchedFiles) {
-    // watchedFiles will be an array of absolute paths of the matched files.
-    // generate an array of blog post metadata that can be used to render
-    // a list in the theme layout
+    // watchedFiles ist ein Array mit den absoluten Pfaden der gefundenen Dateien.
+    // Erzeuge ein Array mit Metadaten von Blogbeiträgen, das zum Rendern
+    // einer Liste im Theme-Layout verwendet werden kann
     return watchedFiles.map((file) => {
       return parse(fs.readFileSync(file, 'utf-8'), {
         columns: true,
@@ -85,7 +85,7 @@ export default {
 
 ## `createContentLoader`
 
-When building a content focused site, we often need to create an "archive" or "index" page: a page where we list all verfügbar entries in our content collection, for example blog posts or API pages. We **can** implement this directly mit the data loader API, but since this is such a common use case, VitePress also stellt bereit a `createContentLoader` helper to simplify this:
+Beim Erstellen einer inhaltsorientierten Website müssen wir häufig eine „Archiv“- oder „Index“-Seite erstellen: eine Seite, auf der wir alle verfügbaren Einträge unserer Inhaltssammlung auflisten, beispielsweise Blogbeiträge oder API-Seiten. Wir **können** dies direkt mit der Data-Loader-API umsetzen. Da dies jedoch ein sehr häufiger Anwendungsfall ist, stellt VitePress den Helper `createContentLoader` bereit, der dies vereinfacht:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
@@ -93,29 +93,29 @@ import { createContentLoader } from 'vitepress'
 export default createContentLoader('posts/*.md', /* options */)
 ```
 
-The helper takes a glob pattern relative to the [source directory](./routing#source-directory), and gibt zurück a `{ watch, load }` data loader object that can be verwendet as the default export in a data loader file. It also implements caching based on file modified timestamps to improve dev performance.
+Der Helper akzeptiert ein Glob-Muster relativ zum [source directory](./routing#source-directory), und gibt ein `{ watch, load }`-Data-Loader-Objekt zurück, das als Standardexport in einer Data-Loader-Datei verwendet werden kann. Außerdem wird ein Cache auf Grundlage der Änderungszeitpunkte von Dateien verwendet, um die Leistung während der Entwicklung zu verbessern.
 
-Hinweis the loader only works mit Markdown files - matched non-Markdown files will be skipped.
+Hinweis: Der Loader funktioniert nur mit Markdown-Dateien – gefundene Dateien ohne Markdown-Endung werden übersprungen.
 
-The loaded data will be an array mit the type of `ContentData[]`:
+Die geladenen Daten sind ein Array vom Typ `ContentData[]`:
 
 ```ts
 interface ContentData {
-  // mapped URL for the page. e.g. /posts/hello.html (does not include base)
-  // manually iterate or use custom `transform` to normalize the paths
+  // Zugeordnete URL der Seite, z. B. /posts/hello.html (enthält base nicht)
+  // Pfade manuell durchlaufen oder mit `transform` normalisieren
   url: string
-  // frontmatter data of the page
+  // Frontmatter-Daten der Seite
   frontmatter: Record<string, any>
 
-  // the following are only present if relevant options are enabled
-  // we will discuss them below
+  // Die folgenden Eigenschaften sind nur vorhanden, wenn die entsprechenden Optionen aktiviert sind
+  // Wir besprechen sie weiter unten
   src: string | undefined
   html: string | undefined
   excerpt: string | undefined
 }
 ```
 
-Standardmäßig, only `url` and `frontmatter` are provided. This is because the loaded data will be inlined as JSON in the client bundle, so we need to be cautious about its size. Here's an example Verwendung the data to build a minimal blog index page:
+Standardmäßig werden nur `url` und `frontmatter` bereitgestellt. Da die geladenen Daten als JSON in das Client-Bundle eingebettet werden, müssen wir auf ihre Größe achten. Hier ist ein Beispiel dafür, wie du die Daten für eine minimale Blog-Indexseite verwendest:
 
 ```vue
 <script setup>
@@ -123,11 +123,11 @@ import { data as posts } from './posts.data.js'
 </script>
 
 <template>
-  <h1>All Blog Posts</h1>
+  <h1>Alle Blogbeiträge</h1>
   <ul>
     <li v-for="post of posts">
       <a :href="post.url">{{ post.frontmatter.title }}</a>
-      <span>by {{ post.frontmatter.author }}</span>
+      <span>von {{ post.frontmatter.author }}</span>
     </li>
   </ul>
 </template>
@@ -135,66 +135,66 @@ import { data as posts } from './posts.data.js'
 
 ### Optionen
 
-The default data may not suit all needs - you can opt-in to transform the data Verwendung options:
+Die Standarddaten sind möglicherweise nicht für alle Anwendungsfälle geeignet. Du kannst die Daten mithilfe von Optionen transformieren:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
 
 export default createContentLoader('posts/*.md', {
-  includeSrc: true, // include raw markdown source?
-  render: true,     // include rendered full page HTML?
-  excerpt: true,    // include excerpt?
+  includeSrc: true, // Rohquelle des Markdown einschließen?
+  render: true,     // Gerendertes vollständiges HTML der Seite einschließen?
+  excerpt: true,    // Auszug einschließen?
   transform(rawData) {
-    // map, sort, or filter the raw data as you wish.
-    // the final result is what will be shipped to the client.
+    // Rohdaten nach Bedarf abbilden, sortieren oder filtern.
+    // Das Endergebnis wird an den Client ausgeliefert.
     return rawData.sort((a, b) => {
       return +new Date(b.frontmatter.date) - +new Date(a.frontmatter.date)
     }).map((page) => {
-      page.src     // raw markdown source
-      page.html    // rendered full page HTML
-      page.excerpt // rendered excerpt HTML (content above first `---`)
+      page.src     // Rohquelle des Markdown
+      page.html    // Gerendertes vollständiges HTML der Seite
+      page.excerpt // Gerendertes HTML des Auszugs (Inhalt vor dem ersten `---`)
       return {/* ... */}
     })
   }
 })
 ```
 
-Check out how it is verwendet in the [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
+Sieh dir an, wie dies im [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
 
-The `createContentLoader` API can also be verwendet innerhalb [build hooks](../reference/site-config#build-hooks):
+Die `createContentLoader`-API kann auch innerhalb von [build hooks](../reference/site-config#build-hooks):
 
 ```js [.vitepress/config.js]
 export default {
   async buildEnd() {
     const posts = await createContentLoader('posts/*.md').load()
-    // generate files based on posts metadata, e.g. RSS feed
+    // Dateien anhand der Beitragsmetadaten erzeugen, z. B. einen RSS-Feed
   }
 }
 ```
 
-**Types**
+**Typen**
 
 ```ts
 interface ContentOptions<T = ContentData[]> {
   /**
-   * Include src?
+   * src einschließen?
    * @default false
    */
   includeSrc?: boolean
 
   /**
-   * Render src to HTML and include in data?
+   * src in HTML rendern und in die Daten aufnehmen?
    * @default false
    */
   render?: boolean
 
   /**
-   * If `boolean`, whether to parse and include excerpt? (rendered as HTML)
+   * Wenn `boolean`: ob ein Auszug verarbeitet und aufgenommen werden soll (als HTML gerendert).
    *
-   * If `function`, control how the excerpt is extracted from the content.
+   * Wenn `function`: steuert, wie der Auszug aus dem Inhalt extrahiert wird.
    *
-   * If `string`, define a custom separator to be used for extracting the
-   * excerpt. Default separator is `---` if `excerpt` is `true`.
+   * Wenn `string`: definiert ein benutzerdefiniertes Trennzeichen zum Extrahieren des
+   * excerpt. Das Standardtrennzeichen ist `---` if `excerpt` is `true`.
    *
    * @see https://github.com/jonschlinkert/gray-matter#optionsexcerpt
    * @see https://github.com/jonschlinkert/gray-matter#optionsexcerpt_separator
@@ -207,29 +207,29 @@ interface ContentOptions<T = ContentData[]> {
     | string
 
   /**
-   * Transform the data. Note the data will be inlined as JSON in the client
-   * bundle if imported from components or markdown files.
+   * Daten transformieren. Beachte, dass die Daten als JSON im Client-Bundle eingebettet werden, wenn sie aus Komponenten oder Markdown-Dateien
+   * importiert werden.
    */
   transform?: (data: ContentData[]) => T | Promise<T>
 }
 ```
 
-## Typed Data Loaders
+## Typisierte Data Loader
 
-When Verwendung TypeScript, you can type your loader and `data` export like so:
+Bei Verwendung von TypeScript kannst du deinen Loader und den `data`-Export wie folgt typisieren:
 
 ```ts
 import { defineLoader } from 'vitepress'
 
 export interface Data {
-  // data type
+  // Datentyp
 }
 
 declare const data: Data
 export { data }
 
 export default defineLoader({
-  // type checked loader options
+  // Typgeprüfte Loader-Optionen
   watch: ['...'],
   async load(): Promise<Data> {
     // ...
@@ -239,7 +239,7 @@ export default defineLoader({
 
 ## Konfiguration
 
-To get the Konfiguration information innerhalb a loader, you can use some code like this:
+Um innerhalb eines Loaders auf die Konfigurationsinformationen zuzugreifen, kannst du beispielsweise folgenden Code verwenden:
 
 ```ts
 import type { SiteConfig } from 'vitepress'

From 2a1ff4b832d1ac8f1c22189e3e1f9989d3152e04 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:51:23 +0200
Subject: [PATCH 082/199] =?UTF-8?q?docs(de):=20Deployment-Anleitung=20voll?=
 =?UTF-8?q?st=C3=A4ndig=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/deploy.md | 152 ++++++++++++++++++++--------------------
 1 file changed, 76 insertions(+), 76 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index d72b523e2..5f7d1b7cf 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -1,15 +1,15 @@
 ---
 outline: deep
-description: Deploy your VitePress site to popular platforms like Netlify, Vercel, GitHub Seiten, and more.
+description: Stelle deine VitePress-Website auf beliebten Plattformen wie Netlify, Vercel, GitHub Pages und weiteren Plattformen bereit.
 ---
 
-# Deploy Your VitePress Site
+# Deine VitePress-Website bereitstellen
 
-The following guides are based on some shared assumptions:
+Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
-- The VitePress site is innerhalb the `docs` directory of your project.
-- You are Verwendung the default build output directory (`.vitepress/dist`).
-- VitePress is installed as a local dependency in your project, and you have set up the following scripts in your `package.json`:
+- Die VitePress-Website befindet sich im Verzeichnis `docs` deines Projekts.
+- Du verwendest das standardmäßige Build-Ausgabeverzeichnis (`.vitepress/dist`).
+- VitePress ist als lokale Abhängigkeit in deinem Projekt installiert, und du hast die folgenden Skripte in deiner `package.json`:
 
   ```json [package.json]
   {
@@ -20,23 +20,23 @@ The following guides are based on some shared assumptions:
   }
   ```
 
-## Build and Test Locally
+## Lokal erstellen und testen
 
-1. Run this command to build the docs:
+1. Führe diesen Befehl aus, um die Dokumentation zu erstellen:
 
    ```sh
    $ npm run docs:build
    ```
 
-2. Once built, preview it locally by running:
+2. Nach dem Erstellen kannst du die Website lokal mit folgendem Befehl anzeigen:
 
    ```sh
    $ npm run docs:preview
    ```
 
-   The `preview` command will boot up a local static web server that will serve the output directory `.vitepress/dist` at `http://localhost:4173`. Du kannst use this to make sure everything looks good bevor pushing to production.
+   Der Befehl `preview` startet einen lokalen statischen Webserver, der das Ausgabeverzeichnis `.vitepress/dist` unter `http://localhost:4173` bereitstellt. Du kannst damit überprüfen, ob alles korrekt aussieht, bevor du die Website in die Produktion überträgst.
 
-3. Du kannst configure the port of the server by passing `--port` as an argument.
+3. Du kannst den Port des Servers ändern, indem du `--port` als Argument übergibst.
 
    ```json
    {
@@ -46,17 +46,17 @@ The following guides are based on some shared assumptions:
    }
    ```
 
-   Now the `docs:preview` method will launch the server at `http://localhost:8080`.
+   Das Skript `docs:preview` startet den Server nun unter `http://localhost:8080`.
 
-## Setting a Public Base Path
+## Einen öffentlichen Basispfad festlegen
 
-Standardmäßig, we assume the site is going to be deployed at the root path of a domain (`/`). If your site is going to be served at a sub-path, e.g. `https://mywebsite.com/blog/`, then you need to set the [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
+Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
 
-**Beispiel:** Wenn du're Verwendung Github (or GitLab) Seiten and deploying to `user.github.io/repo/`, then set your `base` to `/repo/`.
+**Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, then set your `base` to `/repo/`.
 
-## Relocatable Builds (Relative Base) {#relocatable-builds-relative-base}
+## Verschiebbare Builds (relativer Basispfad) {#relocatable-builds-relative-base}
 
-When the final URL of the site isn't known at build time — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled in an app — set `base` to `'./'`:
+Wenn die endgültige URL der Website zur Build-Zeit noch nicht bekannt ist — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled in an app — set `base` to `'./'`:
 
 ```ts
 export default {
@@ -64,33 +64,33 @@ export default {
 }
 ```
 
-Every page then references assets and other pages relative to its own location, and the client runtime recovers the real mount point when the page loads. The same build works von **any** sub path ohne rebuilding — including several at once — mit routing, search and prefetching fully functional.
+Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Derselbe Build funktioniert von **jedem** Unterpfad aus ohne erneuten Build – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
 
-Opening the generated HTML files straight von the file system (`file://`) also works as a styled, fully navigable static site. Browsers block JavaScript modules over `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
+Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) also works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
 
-A few things to know:
+Einige Dinge solltest du beachten:
 
-- Keep [`cleanUrls`](../reference/site-config#cleanurls) off (the default): portable output needs links that end in `.html`, since there is no server to rewrite pretty URLs.
-- `404.html` is generated for the root depth. Hosts that serve it as a fallback for arbitrarily deep URLs will render it ohne styles (there is no correct relative prefix for an unknown depth).
-- [`head`](../reference/site-config#head) entries are emitted verbatim, as always — avoid root-absolute paths like `/favicon.ico` there and prefer absolute URLs or `transformHead`.
-- Raw HTML `<a>` tags in Markdown keep their `href` as written — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
-- Links erstellt by [`createContentLoader`](./data-loading#createcontentloader) content stay site-absolute (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
-- Serve pages at their canonical URLs: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
-- The dev server always serves at `/`; the relative behavior applies to the production build.
+- Lasse [`cleanUrls`](../reference/site-config#cleanurls) deaktiviert (Standardeinstellung): Für portable Ausgaben müssen Links mit `.html` enden, da kein Server vorhanden ist, der saubere URLs umschreibt.
+- `404.html` wird für die Stammebene erzeugt. Hosts, die sie als Fallback für beliebig tiefe URLs ausliefern, rendern sie ohne Styles (there is no correct relative prefix for an unknown depth).
+- [`head`](../reference/site-config#head) Einträge werden wie immer unverändert ausgegeben – vermeide dort absolute Pfade wie `/favicon.ico` there and prefer absolute URLs or `transformHead`.
+- Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
+- Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
+- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
+- Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktions-Build.
 
-## HTTP Cache Headers
+## HTTP-Cache-Header
 
-Wenn du have control over the HTTP headers on your production server, you can configure `cache-control` headers to achieve better performance on repeated visits.
+Wenn du Kontrolle über die HTTP-Header deines Produktionsservers hast, kannst du `cache-control`-Header konfigurieren, um bei wiederholten Besuchen eine bessere Leistung zu erzielen.
 
-The production build verwendet hashed file names for static assets (JavaScript, CSS and other imported assets not in `public`). Wenn du inspect the production preview Verwendung your browser devtools' network tab, you will see files like `app.4f283b18.js`.
+Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and other imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see files like `app.4f283b18.js`.
 
-This `4f283b18` hash is generated von the content of this file. The same hashed URL is guaranteed to serve the same file content - if the contents change, the URLs change too. Das bedeutet you can safely use the strongest cache headers for these files. All such files will be placed under `assets/` in the output directory, so you can configure the following header for them:
+Dieser Hash `4f283b18` wird aus dem Inhalt dieser Datei erzeugt. Dieselbe gehashte URL liefert garantiert denselben Dateiinhalt – wenn sich der Inhalt ändert, ändern sich auch die URLs. Das bedeutet, dass du für diese Dateien bedenkenlos die stärksten Cache-Header verwenden kannst. Alle solchen Dateien werden im Ausgabeverzeichnis unter `assets/` abgelegt. Dafür kannst du den folgenden Header konfigurieren:
 
 ```
 Cache-Control: max-age=31536000,immutable
 ```
 
-::: details Beispiel Netlify `_headers` file
+::: details Beispiel für die Netlify-Datei `_headers`
 
 ```
 /assets/*
@@ -98,13 +98,13 @@ Cache-Control: max-age=31536000,immutable
   cache-control: immutable
 ```
 
-Hinweis: the `_headers` file should be placed in the [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - so that it is copied verbatim to the output directory.
+Hinweis: Die Datei `_headers` sollte im [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - liegen, damit sie unverändert in das Ausgabeverzeichnis kopiert wird.
 
-[Netlify custom headers documentation](https://docs.netlify.com/routing/headers/)
+[Netlify-Dokumentation zu benutzerdefinierten Headern](https://docs.netlify.com/routing/headers/)
 
 :::
 
-::: details Beispiel Vercel config in `vercel.json`
+::: details Beispiel für die Vercel-Konfiguration in `vercel.json`
 
 ```json
 {
@@ -122,58 +122,58 @@ Hinweis: the `_headers` file should be placed in the [public directory](./asset-
 }
 ```
 
-Hinweis: the `vercel.json` file should be placed at the root of your **repository**.
+Hinweis: Die Datei `vercel.json` sollte im Stammverzeichnis deines **Repositorys** liegen.
 
-[Vercel documentation on headers config](https://vercel.com/docs/concepts/projects/project-Konfiguration#headers)
+[Vercel-Dokumentation zur Header-Konfiguration](https://vercel.com/docs/concepts/projects/project-Konfiguration#headers)
 
 :::
 
-## Platform Guides
+## Anleitungen für Plattformen
 
-### Netlify / Vercel / Cloudflare Seiten / AWS Amplify / Render {#generic}
+### Netlify / Vercel / Cloudflare Pages / AWS Amplify / Render {#generic}
 
-Set up a new project and change these settings Verwendung your dashboard:
+Richte ein neues Projekt ein und ändere diese Einstellungen über dein Dashboard:
 
-- **Build Command:** `npm run docs:build`
-- **Output Verzeichnis:** `docs/.vitepress/dist`
-- **Node Version:** `20` (or above)
+- **Build-Befehl:** `npm run docs:build`
+- **Ausgabeverzeichnis:** `docs/.vitepress/dist`
+- **Node-Version:** `20` (or above)
 
 ::: warning
-Don't enable options like _Auto Minify_ for HTML code. It will remove comments von output which have meaning to Vue. You may see hydration mismatch errors if they get removed.
+Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommentare aus der Ausgabe entfernt, die für Vue Bedeutung haben. Wenn sie entfernt werden, können Hydration-Mismatch-Fehler auftreten.
 :::
 
-### GitHub Seiten
+### GitHub Pages
 
-1. Erstellen a file named `deploy.yml` innerhalb `.github/workflows` directory of your project mit some content like this:
+1. Erstelle eine Datei namens `deploy.yml` im Verzeichnis `.github/workflows` deines Projekts, beispielsweise mit folgendem Inhalt:
 
    ```yaml [.github/workflows/deploy.yml]
-   # Sample workflow for building and deploying a VitePress site to GitHub Pages
+   # Beispiel-Workflow zum Erstellen und Bereitstellen einer VitePress-Website auf GitHub Pages
    #
-   name: Deploy VitePress site to Pages
+   name: VitePress-Website auf Pages bereitstellen
 
    on:
-     # Runs on pushes targeting the `main` branch. Change this to `master` if you're
-     # using the `master` branch as the default branch.
+     # Wird bei Pushes auf den `main`-Branch ausgeführt. Ändere dies zu `master`, wenn du
+     # den `master`-Branch als Standard-Branch verwendest.
      push:
        branches: [main]
 
-     # Allows you to run this workflow manually from the Actions tab
+     # Ermöglicht das manuelle Ausführen dieses Workflows über den Actions-Tab
      workflow_dispatch:
 
-   # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
+   # Legt die Berechtigungen des GITHUB_TOKEN für die Bereitstellung auf GitHub Pages fest
    permissions:
      contents: read
      pages: write
      id-token: write
 
-   # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
-   # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
+   # Erlaubt nur eine gleichzeitige Bereitstellung und überspringt zwischenzeitlich eingereihtes Ausführungen.
+   # Laufende Ausführungen dürfen jedoch NICHT abgebrochen werden, damit diese Produktionsbereitstellungen abgeschlossen werden können.
    concurrency:
      group: pages
      cancel-in-progress: false
 
    jobs:
-     # Build job
+     # Build-Aufgabe
      build:
        runs-on: ubuntu-latest
        steps:
@@ -208,33 +208,33 @@ Don't enable options like _Auto Minify_ for HTML code. It will remove comments v
            with:
              path: docs/.vitepress/dist
 
-     # Deployment job
+     # Bereitstellungsaufgabe
      deploy:
        environment:
          name: github-pages
          url: ${{ steps.deployment.outputs.page_url }}
        needs: build
        runs-on: ubuntu-latest
-       name: Deploy
+       name: Bereitstellen
        steps:
-         - name: Deploy to GitHub Pages
+         - name: Bereitstellen to GitHub Pages
            id: deployment
            uses: actions/deploy-pages@v4
    ```
 
    ::: warning
-   Stelle sicher the `base` option in your VitePress is properly konfiguriert. See [Setting a Public Base Path](#setting-a-public-base-path) for more details.
+   Stelle sicher, dass die Option `base` in deiner VitePress-Konfiguration korrekt konfiguriert ist. Weitere Informationen findest du unter [Einen öffentlichen Basispfad festlegen](#setting-a-public-base-path).
    :::
 
-2. In your repository's settings under "Seiten" menu item, select "GitHub Actions" in "Build and deployment > Source".
+2. Wähle in den Repository-Einstellungen unter „Pages“ bei „Build and deployment > Source“ die Option „GitHub Actions“ aus.
 
-3. Push your changes to the `main` branch and wait for the GitHub Actions workflow to complete. Du solltest see your site deployed to `https://<username>.github.io/[repository]/` or `https://<custom-domain>/` depending on your settings. Your site will automatisch be deployed on every push to the `main` branch.
+3. Übertrage deine Änderungen auf den `main`-Branch und warte, bis der GitHub-Actions-Workflow abgeschlossen ist. Deine Website sollte anschließend unter `https://<username>.github.io/[repository]/` oder `https://<custom-domain>/` bereitstehen, abhängig von deinen Einstellungen. Deine Website wird bei jedem Push auf den `main`-Branch automatisch bereitgestellt.
 
-### GitLab Seiten
+### GitLab Pages
 
-1. Set `outDir` in VitePress config to `../public`. Konfigurieren `base` option to `'/<repository>/'` if you want to deploy to `https://<username>.gitlab.io/<repository>/`. You don't need `base` if you're deploying to custom domain, user or group pages, or have "Verwenden unique domain" setting enabled in GitLab.
+1. Setze `outDir` in der VitePress-Konfiguration auf `../public`. Konfiguriere die Option `base` auf `'/<repository>/'` wenn du unter `https://<username>.gitlab.io/<repository>/`. Du benötigst `base` nicht, wenn du eine benutzerdefinierte Domain, Benutzer- oder Gruppenseiten verwendest oder die Einstellung „Eindeutige Domain verwenden“ in GitLab aktiviert hast.
 
-2. Erstellen a file named `.gitlab-ci.yml` in the root of your project mit the content below. This will build and deploy your site whenever you make changes to your content:
+2. Erstelle eine Datei namens `.gitlab-ci.yml` im Stammverzeichnis deines Projekts mit folgendem Inhalt. Dadurch wird deine Website bei jeder Änderung am Inhalt erstellt und bereitgestellt:
 
    ```yaml [.gitlab-ci.yml]
    image: node:24
@@ -253,13 +253,13 @@ Don't enable options like _Auto Minify_ for HTML code. It will remove comments v
        - main
    ```
 
-<!-- keep headings sorted alphabetically, leave nginx at the end -->
+<!-- Überschriften alphabetisch sortiert halten, nginx am Ende lassen -->
 
 ### Azure
 
-1. Follow the [official documentation](https://docs.microsoft.com/en-us/azure/static-web-apps/build-Konfiguration).
+1. Folge der [offiziellen Dokumentation](https://docs.microsoft.com/en-us/azure/static-web-apps/build-Konfiguration).
 
-2. Set these values in your Konfiguration file (and remove the ones you don't require, like `api_location`):
+2. Setze diese Werte in deiner Konfigurationsdatei (und entferne nicht benötigte Werte wie `api_location`):
 
    - **`app_location`**: `/`
    - **`output_location`**: `docs/.vitepress/dist`
@@ -271,7 +271,7 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
 
 ### Firebase
 
-1. Erstellen `firebase.json` and `.firebaserc` at the root of your project:
+1. Erstelle `firebase.json` und `.firebaserc` im Stammverzeichnis deines Projekts:
 
    `firebase.json`:
 
@@ -294,7 +294,7 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
    }
    ```
 
-2. After running `npm run docs:build`, run this command to deploy:
+2. Nach `npm run docs:build` führe diesen Befehl aus, um die Website bereitzustellen:
 
    ```sh
    firebase deploy
@@ -302,9 +302,9 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
 
 ### Heroku
 
-1. Follow documentation and guide given in [`heroku-buildpack-static`](https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static).
+1. Folge der Dokumentation und Anleitung für [`heroku-buildpack-static`](https://elements.heroku.com/buildpacks/heroku/heroku-buildpack-static).
 
-2. Erstellen a file genannt `static.json` in the root of your project mit the below content:
+2. Erstelle eine Datei namens `static.json` im Stammverzeichnis deines Projekts mit folgendem Inhalt:
 
    ```json [static.json]
    {
@@ -314,7 +314,7 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
 
 ### Hostinger
 
-Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). While configuring build settings, choose VitePress as the framework and adjust the root directory to `./docs`.
+Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). Wähle bei der Build-Konfiguration VitePress als Framework und setze das Stammverzeichnis auf `./docs`.
 
 ### Lizard
 
@@ -328,7 +328,7 @@ lizard add --service web
 lizard up --service web --port 80
 ```
 
-Leave build and start command overrides unset to use automatic detection. For GitHub deployments or other layouts, see the [Lizard VitePress guide](https://lizard.build/docs/framework-guides/vitepress).
+Lasse Überschreibungen für Build- und Startbefehle leer, damit die automatische Erkennung verwendet wird. Für GitHub-Bereitstellungen oder andere Strukturen siehe die [Lizard VitePress guide](https://lizard.build/docs/framework-guides/vitepress).
 
 ### Stormkit
 
@@ -336,7 +336,7 @@ Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) b
 
 ### Surge
 
-After running `npm run docs:build`, run this command to deploy to [Surge](https://surge.sh):
+Nach `npm run docs:build` führe diesen Befehl aus, um die Website auf [Surge](https://surge.sh):
 
 ```sh
 npx surge docs/.vitepress/dist
@@ -344,7 +344,7 @@ npx surge docs/.vitepress/dist
 
 ### harvis
 
-After running `npm run docs:build`, run this command to deploy to [harvis](https://harvis.dev):
+Nach `npm run docs:build` führe diesen Befehl aus, um die Website auf [harvis](https://harvis.dev):
 
 ```sh
 npx harvis docs/.vitepress/dist
@@ -352,7 +352,7 @@ npx harvis docs/.vitepress/dist
 
 ### nginx
 
-Here is a example of an nginx server block Konfiguration. This setup includes gzip compression for common text-based assets, rules for serving your VitePress site's static files mit proper caching headers as well as handling `cleanUrls: wahr`.
+Hier ist ein Beispiel für die Konfiguration eines nginx-Serverblocks. Diese Konfiguration enthält Gzip-Komprimierung für gängige textbasierte Assets, Regeln zum Ausliefern der statischen Dateien deiner VitePress-Website mit geeigneten Cache-Headern sowie die Behandlung von `cleanUrls: true`.
 
 ```nginx
 map $uri $cache_control {

From c68e111dea1d1c882f6299235d5084a9d4d65576 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:51:29 +0200
Subject: [PATCH 083/199] docs(de): deutsche UI-Bezeichnungen korrigieren

---
 docs/de/config.ts | 50 +++++++++++++++++++++++------------------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/docs/de/config.ts b/docs/de/config.ts
index 767a8c066..e9226e8b0 100644
--- a/docs/de/config.ts
+++ b/docs/de/config.ts
@@ -28,7 +28,7 @@ export default defineAdditionalConfig({
   head: [
     [
       'link',
-      // for the vazirmatn font-face defined in .vitepress/theme/styles.css
+      // für die in .vitepress/theme/styles.css definierte Vazirmatn-Schrift
       { rel: 'preconnect', href: 'https://cdn.jsdelivr.net', crossorigin: '' }
     ]
   ],
@@ -39,23 +39,23 @@ export default defineAdditionalConfig({
     search: { options: searchOptions() },
 
     sidebar: {
-      '/de/guide/': { base: '/de/guide/', items: sidebarGuide() },
+      '/de/guide/': { base: '/de/guide/', items: sidebarAnleitung() },
       '/de/reference/': { base: '/de/reference/', items: sidebarReference() }
     },
 
     editLink: {
       pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
-      text: 'Bearbeite diese Seite auf GitHub'
+      text: 'Diese Seite auf GitHub bearbeiten'
     },
 
     footer: {
-      message: 'Freigegeben unter MIT License',
+      message: 'Veröffentlicht unter der MIT-Lizenz',
       copyright: 'Copyright © 2019-heute Evan You'
     },
 
     docFooter: {
-      prev: 'Vorheriger',
-      next: 'Nächster'
+      prev: 'Zurück',
+      next: 'Weiter'
     },
 
     outline: {
@@ -63,7 +63,7 @@ export default defineAdditionalConfig({
     },
 
     lastUpdated: {
-      text: 'Zuletzt geupdated'
+      text: 'Zuletzt aktualisiert'
     },
 
     notFound: {
@@ -75,7 +75,7 @@ export default defineAdditionalConfig({
     },
 
     langMenuLabel: 'Sprache ändern',
-    returnToTopLabel: 'Zurück nach oben',
+    returnToTopLabel: 'Nach oben',
     sidebarMenuLabel: 'Seitenleiste',
     darkModeSwitchLabel: 'Dunkelmodus',
     lightModeSwitchTitle: 'Zum Hellmodus wechseln',
@@ -87,7 +87,7 @@ export default defineAdditionalConfig({
 function nav(): DefaultTheme.NavItem[] {
   zurückgeben [
     {
-      text: 'Guide',
+      text: 'Anleitung',
       link: 'de/guide/what-is-vitepress',
       activeMatch: '/guide/'
     },
@@ -116,7 +116,7 @@ function nav(): DefaultTheme.NavItem[] {
   ]
 }
 
-function sidebarGuide(): DefaultTheme.SidebarItem[] {
+function sidebarAnleitung(): DefaultTheme.SidebarItem[] {
   zurückgeben [
     {
       text: 'Einführung',
@@ -125,7 +125,7 @@ function sidebarGuide(): DefaultTheme.SidebarItem[] {
         { text: 'Was ist VitePress?', link: 'what-is-vitepress' },
         { text: 'Erste Schritte', link: 'getting-started' },
         { text: 'Routing', link: 'routing' },
-        { text: 'Deployment', link: 'deploy' }
+        { text: 'Bereitstellung', link: 'deploy' }
       ]
     },
     {
@@ -145,16 +145,16 @@ function sidebarGuide(): DefaultTheme.SidebarItem[] {
       items: [
         { text: 'Ein eigenes Theme nutzen', link: 'custom-theme' },
         {
-          text: 'Standart-Theme erweitern',
+          text: 'Standard-Theme erweitern',
           link: 'extending-default-theme'
         },
-        { text: 'Datenladen', link: 'data-loading' },
+        { text: 'Daten laden', link: 'data-loading' },
         { text: 'SSR-Kompatibilität', link: 'ssr-compat' },
         { text: 'Mit einem CMS verbinden', link: 'cms' }
       ]
     },
     {
-      text: 'Experimental',
+      text: 'Experimentell',
       collapsed: false,
       items: [
         { text: 'MPA-Modus', link: 'mpa-mode' },
@@ -176,7 +176,7 @@ function sidebarReference(): DefaultTheme.SidebarItem[] {
         { text: 'Runtime-API', link: 'runtime-api' },
         { text: 'CLI', link: 'cli' },
         {
-          text: 'Standart-Theme',
+          text: 'Standard-Theme',
           base: 'de/reference/default-theme-',
           items: [
             { text: 'Übersicht', link: 'config' },
@@ -189,7 +189,7 @@ function sidebarReference(): DefaultTheme.SidebarItem[] {
             { text: 'Team-Seite', link: 'team-page' },
             { text: 'Vorher / Nachher Links', link: 'prev-next-links' },
             { text: 'Link bearbeiten', link: 'edit-link' },
-            { text: 'Zuletzt geupdated Zeitstempel', link: 'last-updated' },
+            { text: 'Zuletzt aktualisiert Zeitstempel', link: 'last-updated' },
             { text: 'Suche', link: 'search' },
             { text: 'Carbon Ads', link: 'carbon-ads' }
           ]
@@ -239,7 +239,7 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
           closeText: 'Schließen',
           backToSearchText: 'Zurück zur Suche',
           closeKeyAriaLabel: 'Escape-Taste',
-          poweredByText: 'Angetrieben von'
+          poweredByText: 'Bereitgestellt von'
         },
         errorScreen: {
           titleText: 'Ergebnisse konnten nicht abgerufen werden.',
@@ -272,12 +272,12 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
           disclaimerText:
             'Die Antworten werden von einer KI generiert und können ungenau sein. Bitte überprüfen Sie diese.',
           relatedSourcesText: 'Verwandte Quellen',
-          thinkingText: 'Denken...',
+          thinkingText: 'Nachdenken...',
           copyButtonText: 'Kopieren',
           copyButtonCopiedText: 'Kopiert!',
           copyButtonTitle: 'Kopieren',
           likeButtonTitle: 'Hilfreich',
-          dislikeButtonTitle: 'Nicht Hilfreich',
+          dislikeButtonTitle: 'Nicht hilfreich',
           thanksForFeedbackText: 'Danke für Ihr Feedback!',
           preToolCallText: 'Suchen...',
           duringToolCallText: 'Suchen...',
@@ -305,7 +305,7 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
               viewConversationHistoryText: 'Gesprächsverlauf'
             },
             promptForm: {
-              promptPlaceholderText: 'Frage eine Frage',
+              promptPlaceholderText: 'Eine Frage stellen',
               promptAnsweringText: 'Antwort generieren...',
               promptAskAnotherQuestionText: 'Frage eine weitere Frage',
               promptDisclaimerText:
@@ -317,17 +317,17 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
             conversationScreen: {
               preToolCallText: 'Suchen...',
               searchingText: 'Suchen...',
-              toolCallResultText: 'Siche nach',
+              toolCallResultText: 'Suche nach',
               conversationDisclaimer:
                 'Die Antworten werden von einer KI generiert und können ungenau sein. Bitte überprüfen Sie diese.',
               reasoningText: 'Nachdenken...',
-              thinkingText: 'Denken...',
-              relatedSourcesText: 'Ähnliche Quellen',
+              thinkingText: 'Nachdenken...',
+              relatedSourcesText: 'Verwandte Quellen',
               stoppedStreamingText: 'Du hast diese Antwort angehalten',
               copyButtonText: 'Kopieren',
               copyButtonCopiedText: 'Kopiert!',
               likeButtonTitle: 'Hilfreich',
-              dislikeButtonTitle: 'Nicht Hilfreich',
+              dislikeButtonTitle: 'Nicht hilfreich',
               thanksForFeedbackText: 'Danke für dein Feedback!',
               errorTitleText: 'Konversationsfehler'
             },
@@ -337,7 +337,7 @@ function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
                 'Ich werde Ihre Dokumentation durchsuchen, um schnell Einrichtungsanleitungen, Details zu Funktionen und Tipps zur Fehlerbehebung zu finden.'
             },
             logo: {
-              poweredByText: 'Angetrieben von'
+              poweredByText: 'Bereitgestellt von'
             }
           }
         }

From d8f09fa3e1fd73b42473be6ca6285071fdb9e145 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:52:35 +0200
Subject: [PATCH 084/199] =?UTF-8?q?docs(de):=20Guide=20vollst=C3=A4ndig=20?=
 =?UTF-8?q?ins=20Deutsche=20=C3=BCbertragen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/what-is-vitepress.md | 50 +++++++++++++++---------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index 662611786..6f2689278 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -1,59 +1,59 @@
 ---
-description: a static site generator designed for building fast, content-centric websites powered by Vite and Vue.
+description: Ein statischer Website-Generator zum Erstellen schneller, inhaltsorientierter Websites auf Basis von Vite und Vue.
 ---
 
 # Was ist VitePress?
 
-VitePress is a [Static Site Generator](https://en.wikipedia.org/wiki/Static_site_generator) (SSG) designed for building fast, content-centric websites. In a nutshell, VitePress takes your source content written in [Markdown](https://en.wikipedia.org/wiki/Markdown), applies a theme to it, and generates static HTML pages that can be easily deployed anywhere.
+VitePress ist ein [statischer Website-Generator](https://en.wikipedia.org/wiki/Static_site_generator) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
 
 ::: tip {no-title}
-Just want to try it out? Skip to the [Quickstart](./getting-started).
+Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./getting-started).
 :::
 
 ## Anwendungsfälle
 
-- **Documentation**
+- **Dokumentation**
 
-  VitePress ships with a default theme designed for technical documentation. It powers this page you are reading right now, along with the documentation for [Vite](https://vite.dev/), [Rollup](https://rollupjs.org/), [Pinia](https://pinia.vuejs.org/), [VueUse](https://vueuse.org/), [Vitest](https://vitest.dev/), [D3](https://d3js.org/), [UnoCSS](https://unocss.dev/), [Iconify](https://iconify.design/) and [many more](https://github.com/search?q=/%22vitepress%22:+/+path:/(?:package%7Cdeno)%5C.jsonc?$/+NOT+is:fork+NOT+is:archived&type=code).
+  VitePress enthält ein Stundard-Theme für technische Dokumentation. Es wird für diese Seite und unter underem für die Dokumentation von [Vite](https://vite.dev/), [Rollup](https://rollupjs.org/), [Pinia](https://pinia.vuejs.org/), [VueUse](https://vueuse.org/), [Vitest](https://vitest.dev/), [D3](https://d3js.org/), [UnoCSS](https://unocss.dev/), [Iconify](https://iconify.design/) und [many more](https://github.com/search?q=/%22vitepress%22:+/+path:/(?:package%7Cdeno)%5C.jsonc?$/+NOT+is:fork+NOT+is:archived&type=code).
 
-  The [official Vue.js documentation](https://vuejs.org/) is also based on VitePress, but uses a custom theme shared between multiple translations.
+  Die [offizielle Vue.js-Dokumentation](https://vuejs.org/) basiert ebenfalls auf VitePress, verwendet jedoch ein eigenes Theme, das von mehreren Übersetzungen gemeinsam genutzt wird.
 
-- **Blogs, Portfolios, and Marketing Sites**
+- **Blogs, Portfolios und Marketing-Websites**
 
-  VitePress supports [fully customized themes](./custom-theme), with the developer experience of a standard Vite + Vue application. Being built on Vite also means you can directly leverage Vite plugins from its rich ecosystem. In addition, VitePress provides flexible APIs to [load data](./data-loading) (local or remote) and [dynamically generate routes](./routing#dynamic-routes). You can use it to build almost anything as long as the data can be determined at build time.
+  VitePress supports [fully customized themes](./custom-theme), with the developer experience of a stundard Vite + Vue application. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [load data](./data-loading) (local or remote) und [dynamically generate routes](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
 
-  The official [Vue.js blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
+  Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
 
 ## Entwicklererfahrung
 
-VitePress aims to provide a great Developer Experience (DX) when working with Markdown content.
+VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mit Markdown-Inhalten bieten.
 
-- **[Vite-Powered:](https://vite.dev/)** instant server start, with edits always instantly reflected (<100ms) without page reload.
+- **[Vite-Powered:](https://vite.dev/)** sofortiger Serverstart, wobei Änderungen ohne Neuladen der Seite unmittelbar (<100 ms) sichtbar werden.
 
-- **[Built-in Markdown Extensions:](./markdown)** Frontmatter, tables, syntax highlighting... you name it. Specifically, VitePress provides many advanced features for working with code blocks, making it ideal for highly technical documentation.
+- **[Built-in Markdown Extensions:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
 
-- **[Vue-Enhanced Markdown:](./using-vue)** each Markdown page is also a Vue [Single-File Component](https://vuejs.org/guide/scaling-up/sfc.html), thanks to Vue template's 100% syntax compatibility with HTML. You can embed interactivity in your static content using Vue templating features or imported Vue components.
+- **[Vue-Enhanced Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks to Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
 
-## Performance
+## Leistung
 
-Unlike many traditional SSGs where each navigation results in a full page reload, a website generated by VitePress serves static HTML on the initial visit, but becomes a [Single Page Application](https://en.wikipedia.org/wiki/Single-page_application) (SPA) for subsequent navigation within the site. This model, in our opinion, provides an optimal balance for performance:
+Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollständiges Neuladen der Seite auslöst, liefert eine mit VitePress erzeugte Website beim ersten Besuch statisches HTML aus und wird bei weiterer Navigation innerhalb der Website zu einer [Single-Page-Anwendung](https://en.wikipedia.org/wiki/Single-page_application) (SPA) Dieses Modell bietet unserer Ansicht nach ein ausgewogenes Verhältnis zwischen Leistung und Benutzerfreundlichkeit:
 
-- **Fast Initial Load**
+- **Schnelles erstes Laden**
 
-  The initial visit to any page will be served the static, pre-rendered HTML for fast loading speed and optimal SEO. The page then loads a JavaScript bundle that turns the page into a Vue SPA ("hydration"). Contrary to common assumptions of SPA hydration being slow, this process is actually extremely fast thanks to Vue 3's raw performance and compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
+  The initial visit to any page will be served the static, pre-rendered HTML for fast loading speed und optimal SEO. The page then loads a JavaScript bundle that turns the page into a Vue SPA ("hydration"). Contrary to common assumptions of SPA hydration being slow, this process is actually extremely fast thanks to Vue 3's raw performance und compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
 
-- **Fast Post-load Navigation**
+- **Schnelle Navigation nach dem Laden**
 
-  More importantly, the SPA model leads to better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched and dynamically updated. VitePress also automatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
+  More importantly, the SPA model leads to better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched und dynamically updated. VitePress also automatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
 
-- **Interactivity Without Penalty**
+- **Interaktivität ohne Nachteile**
 
-  To be able to hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue component and compiled into JavaScript. This may sound inefficient, but the Vue compiler is smart enough to separate the static and dynamic parts, minimizing both the hydration cost and payload size. For the initial page load, the static parts are automatically eliminated from the JavaScript payload and skipped during hydration.
+  To be able to hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue component und compiled into JavaScript. This may sound inefficient, but the Vue compiler is smart enough to separate the static und dynamic parts, minimizing both the hydration cost und payload size. For the initial page load, the static parts are automatically eliminated from the JavaScript payload und skipped during hydration.
 
-## What About VuePress?
+## Und was ist mit VuePress?
 
-VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 and webpack. With Vue 3 and Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, and a more flexible customization API.
+VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible customization API.
 
-The API difference between VitePress and VuePress 1 mostly lies in theming and customization. If you are using VuePress 1 with the default theme, it should be relatively straightforward to migrate to VitePress.
+The API difference between VitePress und VuePress 1 mostly lies in theming und customization. If you are using VuePress 1 with the default theme, it should be relatively straightforward to migrate to VitePress.
 
-Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided to focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, and VuePress 2 has been handed over to the VuePress community team for further development and maintenance.
+Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided to focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, und VuePress 2 has been hunded over to the VuePress community team for further development und maintenance.

From 672b9b5ff51ec0b63b2beb97c773076610ec2c8d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:52:38 +0200
Subject: [PATCH 085/199] =?UTF-8?q?docs(de):=20Guide=20vollst=C3=A4ndig=20?=
 =?UTF-8?q?ins=20Deutsche=20=C3=BCbertragen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/routing.md | 150 +++++++++++++++++++--------------------
 1 file changed, 75 insertions(+), 75 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index b8e175a74..8503e5303 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -1,13 +1,13 @@
 ---
 outline: deep
-description: Understand VitePress file-based routing, dynamic routes, clean URLs, and path rewrites.
+description: Verstehe das dateibasierte Routing, dynamische Routen, saubere URLs und Pfadumschreibungen von VitePress.
 ---
 
 # Routing
 
 ## Dateibasierte Routen
 
-VitePress uses file-based routing, which means the generated HTML pages are mapped from the directory structure of the source Markdown files. Zum Beispiel, given the following directory structure:
+VitePress verwendet dateibasiertes Routing. Das bedeutet, dass die erzeugten HTML-Seiten aus der Verzeichnisstruktur der Markdown-Quelldateien abgeleitet werden. Zum Beispiel bei folgender Verzeichnisstruktur:
 
 ```
 .
@@ -18,12 +18,12 @@ VitePress uses file-based routing, which means the generated HTML pages are mapp
 └─ prologue.md
 ```
 
-The generated HTML pages will be:
+Die erzeugten HTML-Seiten sind:
 
 ```
-index.md                  -->  /index.html (accessible as /)
+index.md                  -->  /index.html (erreichbar unter /)
 prologue.md               -->  /prologue.html
-guide/index.md            -->  /guide/index.html (accessible as /guide/)
+guide/index.md            -->  /guide/index.html (erreichbar unter /guide/)
 guide/getting-started.md  -->  /guide/getting-started.html
 ```
 
@@ -31,18 +31,18 @@ The resulting HTML can be hosted on any web server that can serve static files.
 
 ## Stamm- und Quellverzeichnis
 
-There are two important concepts in the file structure of a VitePress project: the **project root** and the **source directory**.
+In der Dateistruktur eines VitePress-Projekts gibt es zwei wichtige Konzepte: das **Projektstammverzeichnis** und das **Quellverzeichnis**.
 
 ### Projektverzeichnis
 
-Projekt root is where VitePress will try to look for the `.vitepress` special directory. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+Das Projektstammverzeichnis ist der Ort, an dem VitePress nach dem speziellen Verzeichnis `.vitepress` sucht. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
 
-Wenn du run `vitepress dev` or `vitepress build` from the command line, VitePress will use the current working directory as project root. To specify a sub-directory as root, you will need to pass the relative path to the command. Zum Beispiel, if your VitePress project is located in `./docs`, you should run `vitepress dev docs`:
+Wenn du `vitepress dev` oder `vitepress build` über die Kommandozeile ausführst, verwendet VitePress das aktuelle Arbeitsverzeichnis als Projektstammverzeichnis. Um ein Unterverzeichnis als Stammverzeichnis festzulegen, musst du den relativen Pfad an den Befehl übergeben. Wenn dein VitePress-Projekt beispielsweise in `./docs` liegt, solltest du `vitepress dev docs` ausführen:
 
 ```
 .
-├─ docs                    # project root
-│  ├─ .vitepress           # config dir
+├─ docs                    # Projektstammverzeichnis
+│  ├─ .vitepress           # Konfigurationsverzeichnis
 │  ├─ getting-started.md
 │  └─ index.md
 └─ ...
@@ -52,22 +52,22 @@ Wenn du run `vitepress dev` or `vitepress build` from the command line, VitePres
 vitepress dev docs
 ```
 
-Dies ist going to result in the following source-to-HTML mapping:
+Dies führt zu folgender Zuordnung von Quelle zu HTML:
 
 ```
-docs/index.md            -->  /index.html (accessible as /)
+docs/index.md            -->  /index.html (erreichbar unter /)
 docs/getting-started.md  -->  /getting-started.html
 ```
 
 ### Quellverzeichnis
 
-Quelle directory is where your Markdown source files live. Standardmäßig, it is the same as the project root. However, you can configure it via the [`srcDir`](../reference/site-config#srcdir) config option.
+Das Quellverzeichnis ist der Ort, an dem deine Markdown-Quelldateien liegen. Standardmäßig entspricht es dem Projektstammverzeichnis. Du kannst es jedoch über die [`srcDir`](../reference/site-config#srcdir) Konfigurationsoption festlegen.
 
-The `srcDir` option is resolved relative to project root. Zum Beispiel, with `srcDir: 'src'`, your file structure will look like this:
+Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `srcDir: 'src'`, your file structure will look like this:
 
 ```
-.                          # project root
-├─ .vitepress              # config dir
+.                          # Projektstammverzeichnis
+├─ .vitepress              # Konfigurationsverzeichnis
 └─ src                     # source dir
    ├─ getting-started.md
    └─ index.md
@@ -76,29 +76,29 @@ The `srcDir` option is resolved relative to project root. Zum Beispiel, with `sr
 The resulting source-to-HTML mapping:
 
 ```
-src/index.md            -->  /index.html (accessible as /)
+src/index.md            -->  /index.html (erreichbar unter /)
 src/getting-started.md  -->  /getting-started.html
 ```
 
 ## Zwischen Seiten verlinken
 
-Du kannst use both absolute and relative paths when linking between pages. Beachte, dass although both `.md` and `.html` extensions will work, the best practice is to omit file extensions so that VitePress can generate the final URLs based on your config.
+Du kannst sowohl absolute als auch relative Pfade verwenden, um zwischen Seiten zu verlinken. Beachte, dass sowohl die Endungen `.md` als auch `.html` funktionieren, es jedoch empfohlen wird, Dateiendungen wegzulassen, damit VitePress die endgültigen URLs anhand deiner Konfiguration erzeugen kann.
 
 ```md
-<!-- Do -->
-[Getting Started](./getting-started)
-[Getting Started](../guide/getting-started)
+<!-- Richtig -->
+[Erste Schritte](./getting-started)
+[Erste Schritte](../guide/getting-started)
 
-<!-- Don't -->
-[Getting Started](./getting-started.md)
-[Getting Started](./getting-started.html)
+<!-- Nicht empfohlen -->
+[Erste Schritte](./getting-started.md)
+[Erste Schritte](./getting-started.html)
 ```
 
-Mehr erfahren about linking to assets such images in [Asset Handling](./asset-handling).
+Mehr über das Verlinken von Assets wie Bildern erfährst du unter [Asset-Verwaltung](./asset-handling).
 
 ### Auf Nicht-VitePress-Seiten verlinken
 
-Wenn du want to link to a page in your site that is not generated by VitePress, you'll either need to use the full URL (opens in a new tab) or explicitly specify the target:
+Wenn du auf eine Seite deiner Website verlinken möchtest, die nicht von VitePress erzeugt wird, musst du entweder die vollständige URL verwenden (öffnet einen neuen Tab) oder das Ziel ausdrücklich angeben:
 
 **Input**
 
@@ -110,11 +110,11 @@ Wenn du want to link to a page in your site that is not generated by VitePress,
 
 [Link to pure.html](/pure.html){target="_self"}
 
-::: tip Note
+::: tip Hinweis
 
-In Markdown links, the `base` is automatisch prepended to the URL. Das bedeutet that if you want to link to a page outside of your base, you'd need something like `../../pure.html` in the link (resolved relative to the current page by the browser).
+Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` in the link (resolved relative to the current page by the browser).
 
-Alternatively, you can directly use the anchor tag syntax:
+Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 
 ```md
 <a href="/pure.html" target="_self">Link to pure.html</a>
@@ -122,25 +122,25 @@ Alternatively, you can directly use the anchor tag syntax:
 
 :::
 
-## Generating Clean URLs
+## Saubere URLs erzeugen
 
 ::: warning Server Support Required
-To serve clean URLs with VitePress, server-side support is erforderlich.
+Um saubere URLs mit VitePress bereitzustellen, ist Unterstützung auf Serverseite erforderlich.
 :::
 
-Standardmäßig, VitePress resolves inbound links to URLs ending with `.html`. However, some users may prefer "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
+Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` enden. Manche Benutzer bevorzugen jedoch "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
 
-Some servers or hosting platforms (for example Netlify, Vercel, GitHub Seiten) provide the ability to map a URL like `/foo` to `/foo.html` if it exists, without a redirect:
+Einige Server oder Hosting-Plattformen (beispielsweise Netlify, Vercel und GitHub Pages) können eine URL wie `/foo` ohne Weiterleitung auf `/foo.html` abbilden, wenn diese Datei existiert:
 
 - Netlify and GitHub Seiten support this by default.
 - Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-If this feature is verfügbar to you, you can then also enable VitePress' own [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
+Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
 
 - Inbound links between pages are generated without the `.html` extension.
 - If current path ends with `.html`, the router will perform a client-side redirect to the extension-less path.
 
-If, however, you cannot configure your server with such support, you will have to manually resort to the following directory structure:
+Wenn du deinen Server jedoch nicht entsprechend konfigurieren kannst, musst du stattdessen manuell die folgende Verzeichnisstruktur verwenden:
 
 ```
 .
@@ -151,9 +151,9 @@ If, however, you cannot configure your server with such support, you will have t
 └─ index.md
 ```
 
-## Route Rewrites
+## Routen umschreiben
 
-Du kannst customize the mapping between the source directory structure and the generated pages. It's useful when you have a complex project structure. Zum Beispiel, let's say you have a monorepo with multiple packages, and would like to place documentations along with the source files like this:
+Du kannst die Zuordnung zwischen der Quellverzeichnisstruktur und den erzeugten Seiten anpassen. Das ist bei komplexen Projektstrukturen hilfreich. Angenommen, du hast beispielsweise ein Monorepo mit mehreren Paketen und möchtest die Dokumentation zusammen mit den Quelldateien wie folgt ablegen:
 
 ```
 .
@@ -168,7 +168,7 @@ Du kannst customize the mapping between the source directory structure and the g
          └─ index.md
 ```
 
-And you want the VitePress pages to be generated like this:
+Und du möchtest, dass die VitePress-Seiten so erzeugt werden:
 
 ```
 packages/pkg-a/src/index.md  -->  /pkg-a/index.html
@@ -177,7 +177,7 @@ packages/pkg-b/src/index.md  -->  /pkg-b/index.html
 packages/pkg-b/src/bar.md    -->  /pkg-b/bar.html
 ```
 
-Du kannst achieve this by configuring the [`rewrites`](../reference/site-config#rewrites) option like this:
+Du kannst dies durch Konfiguration der the [`rewrites`](../reference/site-config#rewrites) option like this:
 
 ```ts [.vitepress/config.js]
 export default {
@@ -190,7 +190,7 @@ export default {
 }
 ```
 
-The `rewrites` option also unterstützt dynamic route parameters. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
+Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
 
 ```ts
 export default {
@@ -200,9 +200,9 @@ export default {
 }
 ```
 
-The rewrite paths are compiled Verwendung the `path-to-regexp` package - consult [its documentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
+Die Rewrite-Pfade werden mit dem Paket `path-to-regexp` kompiliert – weitere Informationen findest du in [dessen Dokumentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
 
-`rewrites` can also be a function that receives the original path and gibt zurück the new path:
+`rewrites` can also be a function that receives the original path und gibt den neuen Pfad zurück:
 
 ```ts
 export default {
@@ -212,9 +212,9 @@ export default {
 }
 ```
 
-::: warning Relative Links with Rewrites
+::: warning Relative Links bei Rewrites
 
-When rewrites are enabled, **relative links should be based on the rewritten paths**. Zum Beispiel, in order to erstellen a relative link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
+Wenn Rewrites aktiviert sind, sollten **relative Links auf den umgeschriebenen Pfaden basieren**. Um beispielsweise einen relativen Link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
 
 ```md
 [Link to PKG B](../pkg-b/pkg-b-code)
@@ -223,20 +223,20 @@ When rewrites are enabled, **relative links should be based on the rewritten pat
 
 ## Dynamische Routen
 
-Du kannst generate many pages Verwendung a single Markdown file and dynamic Daten. Zum Beispiel, you can erstellen a `packages/[pkg].md` file that generates a corresponding page for every package in a project. Here, the `[pkg]` segment is a route **parameter** that differentiates each page from the others.
+Du kannst mit einer einzigen Markdown-Datei und dynamischen Daten viele Seiten erzeugen. Zum Beispiel kannst du eine `packages/[pkg].md` file that generates a corresponding page for every package in a project. Hier ist das Segment `[pkg]` ein Routen-**Parameter**, der die einzelnen Seiten voneinander unterscheidet.
 
 ### Pfad-Loader-Datei
 
-Since VitePress is a static site generator, the possible page paths must be determined at build time. Therefore, a dynamic route page **must** be accompanied by a **paths loader file**. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
+Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
 
 ```
 .
 └─ packages
-   ├─ [pkg].md         # route template
-   └─ [pkg].paths.js   # route paths loader
+   ├─ [pkg].md         # Routenvorlage
+   └─ [pkg].paths.js   # Loader für Routenpfade
 ```
 
-The paths loader should provide an object with a `paths` method as its default export. The `paths` method should zurückgeben an array of objects with a `params` property. Each of these objects will generate a corresponding page.
+Der Paths Loader sollte ein Objekt mit einer Methode `paths` als Standardexport bereitstellen. Die Methode `paths` sollte ein Array von Objekten mit einer Eigenschaft `params` zurückgeben. Jedes dieser Objekte erzeugt eine entsprechende Seite.
 
 Given the following `paths` array:
 
@@ -252,7 +252,7 @@ export default {
 }
 ```
 
-The generated HTML pages will be:
+Die erzeugten HTML-Seiten sind:
 
 ```
 .
@@ -261,9 +261,9 @@ The generated HTML pages will be:
    └─ bar.html
 ```
 
-### Type-safe loader with `defineRoutes`
+### Typsicherer Loader mit `defineRoutes`
 
-Wenn du are Verwendung TypeScript, you can wrap the loader with `defineRoutes` from `vitepress` to get type hints for route hooks such as `paths`, `watch`, and `transformPageData`:
+Wenn du TypeScript verwendest, kannst du den Loader mit `defineRoutes` aus `vitepress` umschließen, um Typ-Hinweise für Routen-Hooks wie `paths`, `watch` und `transformPageData` zu erhalten:
 
 ```ts
 // packages/[pkg].paths.ts
@@ -283,13 +283,13 @@ export default defineRoutes({
 })
 ```
 
-`defineRoutes` is optional, but recommended when authoring `.paths.ts` files.
+`defineRoutes` ist optional, wird beim Erstellen von `.paths.ts`-Dateien aber empfohlen.
 
 ### Mehrere Parameter
 
-A dynamic route can contain multiple params:
+Eine dynamische Route kann mehrere Parameter enthalten:
 
-**Datei Structure**
+**Dateistruktur**
 
 ```
 .
@@ -324,9 +324,9 @@ export default {
 
 ### Pfade dynamisch erzeugen
 
-The paths loader module is run in Node.js and only executed during build time. Du kannst dynamically generate the paths array Verwendung any Daten, either local or remote.
+Das Paths-Loader-Modul läuft in Node.js und wird nur zur Build-Zeit ausgeführt. Du kannst das `paths`-Array mit beliebigen lokalen oder entfernten Daten dynamisch erzeugen.
 
-Generating paths from local files:
+Pfade aus lokalen Dateien erzeugen:
 
 ```js
 import fs from 'node:fs'
@@ -342,7 +342,7 @@ export default {
 }
 ```
 
-Generating paths from remote Daten:
+Pfade aus entfernten Daten erzeugen:
 
 ```js
 export default {
@@ -361,9 +361,9 @@ export default {
 }
 ```
 
-### Watching Template and Data Dateien
+### Vorlagen- und Datendateien überwachen
 
-When generating page content from Vorlagen or external Daten sources, you can use the watch option to automatisch rebuild pages when those files change during development:
+Wenn Seiteninhalte aus Vorlagen oder externen Datenquellen erzeugt werden, kannst du die Option `watch` verwenden, um Seiten während der Entwicklung automatisch neu zu erzeugen, wenn sich diese Dateien ändern:
 
 ```js
 // posts/[slug].paths.js
@@ -371,15 +371,15 @@ import fs from 'node:fs'
 import { renderTemplate } from './templates/renderer.js'
 
 export default {
-  // Watch for changes to template files and data sources
+  // Änderungen an Vorlagendateien und Datenquellen überwachen
   watch: [
-    './templates/**/*.njk',     // Template files
-    '../data/**/*.json'         // Data files
+    './templates/**/*.njk',     // Vorlagendateien
+    '../data/**/*.json'         // Datendateien
   ],
 
   paths(watchedFiles) {
-    // watchedFiles will be an array of absolute paths of the matched files
-    // Read data files to generate routes
+    // watchedFiles ist ein Array mit den absoluten Pfaden der gefundenen Dateien
+    // Datendateien lesen, um Routen zu erzeugen
     const dataFiles = watchedFiles.filter(file => file.endsWith('.json'))
 
     return dataFiles.map(file => {
@@ -394,23 +394,23 @@ export default {
 }
 ```
 
-The `watch` option works the same way as in [Daten loaders](./Daten-loading#Daten-from-local-files):
+Die Option `watch` funktioniert genauso wie bei [Data Loadern](./Daten-loading#Daten-from-local-files):
 
-- Accepts [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
-- Patterns are relative to the `.paths.js` file itself
-- Changes to watched files trigger page regeneration and HMR during development
-- In production builds, all pages are generated once regardless of watch configuration
+- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
+- Muster sind relativ zur `.paths.js`-Datei selbst
+- Änderungen an überwachten Dateien lösen während der Entwicklung eine Seitengenerierung und HMR aus
+- In Produktions-Builds werden alle Seiten unabhängig von der `watch`-Konfiguration einmal erzeugt
 
 ### Auf Parameter in Seiten zugreifen
 
-Du kannst use the params to pass additional Daten to each page. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
+Du kannst die Parameter verwenden, um jeder Seite zusätzliche Daten zu übergeben. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
 
 ```md
 - package name: {{ $params.pkg }}
 - version: {{ $params.version }}
 ```
 
-Du kannst also access the current page's params via the [`useData`](../reference/runtime-api#usedata) runtime API. Dies ist verfügbar in both Markdown files and Vue Komponenten:
+Du kannst außerdem über die [`useData`](../reference/runtime-api#usedata) Runtime API auf die Parameter der aktuellen Seite zugreifen. Dies ist sowohl in Markdown-Dateien als auch in Vue-Komponenten verfügbar:
 
 ```vue
 <script setup>
@@ -425,9 +425,9 @@ console.log(params.value)
 
 ### Rohinhalt rendern
 
-Params passed to the page will be serialized in the client JavaScript payload, so you should avoid passing heavy Daten in params, for example raw Markdown or HTML content fetched from a remote CMS.
+An die Seite übergebene Parameter werden in der JavaScript-Nutzlast des Clients serialisiert. Daher solltest du vermeiden, große Datenmengen als Parameter zu übergeben, beispielsweise rohes Markdown oder HTML aus einem entfernten CMS.
 
-Instead, you can pass such content to each page Verwendung the `content` property on each path object:
+Stattdessen kannst du solche Inhalte jeder Seite über die Eigenschaft `content` des jeweiligen Pfadobjekts übergeben: `content` property on each path object:
 
 ```js
 export default {
@@ -444,7 +444,7 @@ export default {
 }
 ```
 
-Then, use the following special syntax to render the content as part of the Markdown file itself:
+Verwende anschließend die folgende spezielle Syntax, um den Inhalt als Teil der Markdown-Datei selbst zu rendern:
 
 ```md
 <!-- @content -->

From 4607213b5a90dbccd27300753322312bae0e030d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:52:44 +0200
Subject: [PATCH 086/199] fix: deutsche Dokumentation syntaktisch korrigieren

---
 docs/de/guide/asset-handling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/guide/asset-handling.md b/docs/de/guide/asset-handling.md
index 36da2d87c..8f2c4d17d 100644
--- a/docs/de/guide/asset-handling.md
+++ b/docs/de/guide/asset-handling.md
@@ -48,7 +48,7 @@ Nur dynamisch erzeugte Pfade benötigen besondere Behandlung – beispielsweise
 
 \`\`\`vue
 <script setup>
-import { withBase, useData } von 'vitepress'
+import { withBase, useData } from 'vitepress'
 
 const { theme } = useData()
 </script>

From db781c201584d5f485d58b8acab42fe274f0ee90 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:52:47 +0200
Subject: [PATCH 087/199] fix: deutsche Dokumentation syntaktisch korrigieren

---
 docs/de/config.ts | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/config.ts b/docs/de/config.ts
index e9226e8b0..f3a201ee0 100644
--- a/docs/de/config.ts
+++ b/docs/de/config.ts
@@ -85,7 +85,7 @@ export default defineAdditionalConfig({
 })
 
 function nav(): DefaultTheme.NavItem[] {
-  zurückgeben [
+  return [
     {
       text: 'Anleitung',
       link: 'de/guide/what-is-vitepress',
@@ -117,7 +117,7 @@ function nav(): DefaultTheme.NavItem[] {
 }
 
 function sidebarAnleitung(): DefaultTheme.SidebarItem[] {
-  zurückgeben [
+  return [
     {
       text: 'Einführung',
       collapsed: false,
@@ -166,7 +166,7 @@ function sidebarAnleitung(): DefaultTheme.SidebarItem[] {
 }
 
 function sidebarReference(): DefaultTheme.SidebarItem[] {
-  zurückgeben [
+  return [
     {
       text: 'Referenz',
       base: 'de/reference/',
@@ -200,7 +200,7 @@ function sidebarReference(): DefaultTheme.SidebarItem[] {
 }
 
 function searchOptions(): Partial<DefaultTheme.AlgoliaSearchOptions> {
-  zurückgeben {
+  return {
     translations: {
       button: {
         buttonText: 'Suche',

From 7b21da51349dff7ffc6b0abfaeef94f295a5ef6b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:55:06 +0200
Subject: [PATCH 088/199] docs(de): translate cms.md

---
 docs/de/guide/cms.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/guide/cms.md b/docs/de/guide/cms.md
index b627c2d08..a9f7bce71 100644
--- a/docs/de/guide/cms.md
+++ b/docs/de/guide/cms.md
@@ -1,17 +1,17 @@
 ---
 outline: deep
-description: Connect VitePress to a headless CMS Verwendung dynamic routes and data loaders.
+description: Verbinde VitePress mit einem Headless-CMS mithilfe dynamischer Routen und Datenlader.
 ---
 
 # Mit einem CMS verbinden
 
-## General Workflow
+## Allgemeiner Ablauf
 
-Connecting VitePress to a CMS will largely revolve around [Dynamisch Routes](./routing#dynamic-routes). Stelle sicher to understand how it works bevor proceeding.
+Die Verbindung von VitePress mit einem CMS dreht sich hauptsächlich um [dynamische Routen](./routing#dynamische-routen). Stelle sicher, dass du verstanden hast, wie sie funktionieren, bevor du fortfährst.
 
-Since each CMS will work differently, here we can only provide a generic workflow that you will need to adapt to your specific scenario.
+Da jedes CMS anders funktioniert, können wir hier nur einen allgemeinen Ablauf beschreiben, den du an dein konkretes Szenario anpassen musst.
 
-1. If your CMS requires authentication, create an `.env` file to store your API tokens and load it so:
+1. Wenn dein CMS eine Authentifizierung erfordert, erstelle eine `.env`-Datei zum Speichern deiner API-Tokens und lade sie:
 
     ```js
     // posts/[id].paths.js
@@ -20,15 +20,15 @@ Since each CMS will work differently, here we can only provide a generic workflo
     const env = loadEnv('', process.cwd())
     ```
 
-2. Fetch the necessary data von the CMS and format it in proper paths data:
+2. Rufe die benötigten Daten aus dem CMS ab und formatiere sie als gültige Pfaddaten:
 
     ```js
     export default {
       async paths() {
-        // use respective CMS client library if needed
+        // Verwende bei Bedarf die Client-Bibliothek des jeweiligen CMS.
         const data = await (await fetch('https://my-cms-api', {
           headers: {
-            // token if necessary
+            // Token, falls erforderlich.
           }
         })).json()
 
@@ -42,16 +42,16 @@ Since each CMS will work differently, here we can only provide a generic workflo
     }
     ```
 
-3. Render the content in the page:
+3. Rendere den Inhalt auf der Seite:
 
     ```md
     # {{ $params.title }}
 
-    - by {{ $params.author }} on {{ $params.date }}
+    - von {{ $params.author }} am {{ $params.date }}
 
     <!-- @content -->
     ```
 
-## Integration Guides
+## Integrationsanleitungen
 
-Wenn du have written a guide on integrating VitePress mit a specific CMS, please use the "Edit this page" link below to submit it here!
+Wenn du eine Anleitung zur Integration von VitePress in ein bestimmtes CMS geschrieben hast, verwende bitte den Link „Diese Seite bearbeiten“ unten auf der Seite, um sie hier einzureichen.

From 13c8003a63e27c8b9d9c4fdd861534b20bd1e47e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:55:08 +0200
Subject: [PATCH 089/199] docs(de): translate migration-from-vitepress-0.md

---
 docs/de/guide/migration-from-vitepress-0.md | 28 ++++++++++-----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/docs/de/guide/migration-from-vitepress-0.md b/docs/de/guide/migration-from-vitepress-0.md
index 86a747f9c..c3aac1b80 100644
--- a/docs/de/guide/migration-from-vitepress-0.md
+++ b/docs/de/guide/migration-from-vitepress-0.md
@@ -1,23 +1,23 @@
 # Migration von VitePress 0.x
 
-Wenn du're coming von VitePress 0.x version, there're several breaking changes due to new features and enhancement. Please follow this guide to see how to migrate your app over to the latest VitePress.
+Wenn du von einer VitePress-0.x-Version kommst, gibt es aufgrund neuer Funktionen und Verbesserungen mehrere Änderungen, die nicht abwärtskompatibel sind. Befolge diese Anleitung, um deine Anwendung auf die aktuelle VitePress-Version zu migrieren.
 
-## App Config
+## App-Konfiguration
 
-- The internationalization feature is not yet implemented.
+- Die Internationalisierungsfunktion ist noch nicht implementiert.
 
-## Theme Config
+## Theme-Konfiguration
 
-- `sidebar` option has changed its structure.
-  - `children` key is now named `items`.
-  - Top level item may not contain `link` at the moment. We're planning to bring it back.
-- `repo`, `repoLabel`, `docsDir`, `docsBranch`, `editLinks`, `editLinkText` are removed in favor of more flexible api.
-  - For adding GitHub link with icon to the nav, use [Social Links](../reference/default-theme-nav#navigation-links) feature.
-  - For adding "Edit this page" feature, use [Bearbeitungslink](../reference/default-theme-edit-link) feature.
-- `lastUpdated` option is now split into `config.lastUpdated` and `themeConfig.lastUpdated.text`.
-- `carbonAds.carbon` is changed to `carbonAds.code`.
+- Die Option `sidebar` hat ihre Struktur geändert.
+  - Der Schlüssel `children` heißt jetzt `items`.
+  - Ein Element der obersten Ebene darf derzeit kein `link` enthalten. Es ist geplant, dies wieder zu ermöglichen.
+- `repo`, `repoLabel`, `docsDir`, `docsBranch`, `editLinks` und `editLinkText` wurden zugunsten einer flexibleren API entfernt.
+  - Um einen GitHub-Link mit Symbol zur Navigation hinzuzufügen, verwende die Funktion [Social Links](../reference/default-theme-nav#navigationslinks).
+  - Um die Funktion „Diese Seite bearbeiten“ hinzuzufügen, verwende die Funktion [Bearbeitungslink](../reference/default-theme-edit-link).
+- Die Option `lastUpdated` ist jetzt in `config.lastUpdated` und `themeConfig.lastUpdated.text` aufgeteilt.
+- `carbonAds.carbon` wurde in `carbonAds.code` geändert.
 
 ## Frontmatter-Konfiguration
 
-- `home: true` option has changed to `layout: home`. Also, many Homepage related settings have been modified to provide additional features. See [Home Seite guide](../reference/default-theme-home-page) for details.
-- `footer` option is moved to [`themeConfig.footer`](../reference/default-theme-config#footer).
+- Die Option `home: true` wurde in `layout: home` geändert. Außerdem wurden viele Einstellungen der Startseite angepasst, um zusätzliche Funktionen bereitzustellen. Weitere Informationen findest du in der [Anleitung zur Startseite](../reference/default-theme-home-page).
+- Die Option `footer` wurde nach [`themeConfig.footer`](../reference/default-theme-config#footer) verschoben.

From 2a53d7af2a3acb331da93f28eee2889188123c4f Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:08 +0200
Subject: [PATCH 090/199] docs(de): translate remaining guide prose

---
 docs/de/guide/migration-from-vuepress.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/guide/migration-from-vuepress.md b/docs/de/guide/migration-from-vuepress.md
index da390deed..b38e074ce 100644
--- a/docs/de/guide/migration-from-vuepress.md
+++ b/docs/de/guide/migration-from-vuepress.md
@@ -4,13 +4,13 @@
 
 ### Seitenleiste
 
-The sidebar is no longer automatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
+The sidebar is no longer auzumatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) zu dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
 
 ## Markdown
 
 ### Bilder
 
-Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatisch when you use static image.
+Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config auzumatisch when you use static image.
 
 Hence, now you can render images without `img` tag.
 
@@ -23,8 +23,8 @@ Hence, now you can render images without `img` tag.
 For dynamic images you still need `withBase` as shown in [Base URL guide](./asset-handling#base-url).
 :::
 
-Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex to find and replace it with `![$2]($1)` to replace all the images with `![](...)` syntax.
+Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex zu find and replace it with `![$2]($1)` zu replace all the images with `![](...)` syntax.
 
 ---
 
-more to follow...
+more zu follow...

From 7505ad385fbd232333a2d87da618007f5a85ae48 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:10 +0200
Subject: [PATCH 091/199] docs(de): translate remaining guide prose

---
 docs/de/guide/mpa-mode.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/guide/mpa-mode.md b/docs/de/guide/mpa-mode.md
index 4f11b5ccd..255baed9a 100644
--- a/docs/de/guide/mpa-mode.md
+++ b/docs/de/guide/mpa-mode.md
@@ -6,15 +6,15 @@ description: MPA (Multi-Seite Application) mode in VitePress for zero-JavaScript
 
 MPA (Multi-Seite Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
 
-In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit tools.
+In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit zuols.
 
-However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
+However, due zu the absence of SPA navigation, cross-page links will lead zu full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
 
-Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need to use the special `<script client>` tag:
+Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need zu use the special `<script client>` tag:
 
 ```html
 <script client>
-document.querySelector('h1').addEventListener('click', () => {
+document.querySeleczur('h1').addEventListener('click', () => {
   console.log('client side JavaScript!')
 })
 </script>
@@ -22,6 +22,6 @@ document.querySelector('h1').addEventListener('click', () => {
 # Hello
 ```
 
-`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled together, while client script for a specific page will be split for that page only.
+`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled zugether, while client script for a specific page will be split for that page only.
 
 Beachte, dass `<script client>` is **not evaluated as Vue Komponente code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be verwendet if your site requires absolutely minimal client-side interactivity.

From 28e03ce45ce6bf06fd7fa9c1eab46fc0f8861e94 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:13 +0200
Subject: [PATCH 092/199] docs(de): translate remaining guide prose

---
 docs/de/guide/routing.md | 50 ++++++++++++++++++++--------------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 8503e5303..05d57cfce 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -27,7 +27,7 @@ guide/index.md            -->  /guide/index.html (erreichbar unter /guide/)
 guide/getting-started.md  -->  /guide/getting-started.html
 ```
 
-The resulting HTML can be hosted on any web server that can serve static files.
+Das erzeugte HTML kann auf jedem Webserver bereitgestellt werden, der statische Dateien ausliefern kann.
 
 ## Stamm- und Quellverzeichnis
 
@@ -35,7 +35,7 @@ In der Dateistruktur eines VitePress-Projekts gibt es zwei wichtige Konzepte: da
 
 ### Projektverzeichnis
 
-Das Projektstammverzeichnis ist der Ort, an dem VitePress nach dem speziellen Verzeichnis `.vitepress` sucht. The `.vitepress` directory is a reserved location for VitePress' config file, dev server cache, build output, and optional theme customization code.
+Das Projektstammverzeichnis ist der Ort, an dem VitePress nach dem speziellen Verzeichnis `.vitepress` sucht. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionalen Theme-Anpassungscode reserviert.
 
 Wenn du `vitepress dev` oder `vitepress build` über die Kommandozeile ausführst, verwendet VitePress das aktuelle Arbeitsverzeichnis als Projektstammverzeichnis. Um ein Unterverzeichnis als Stammverzeichnis festzulegen, musst du den relativen Pfad an den Befehl übergeben. Wenn dein VitePress-Projekt beispielsweise in `./docs` liegt, solltest du `vitepress dev docs` ausführen:
 
@@ -63,17 +63,17 @@ docs/getting-started.md  -->  /getting-started.html
 
 Das Quellverzeichnis ist der Ort, an dem deine Markdown-Quelldateien liegen. Standardmäßig entspricht es dem Projektstammverzeichnis. Du kannst es jedoch über die [`srcDir`](../reference/site-config#srcdir) Konfigurationsoption festlegen.
 
-Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `srcDir: 'src'`, your file structure will look like this:
+Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `srcDir: 'src'`, deine Dateistruktur sieht dann so aus:
 
 ```
 .                          # Projektstammverzeichnis
 ├─ .vitepress              # Konfigurationsverzeichnis
-└─ src                     # source dir
+└─ src                     # Quellverzeichnis
    ├─ getting-started.md
    └─ index.md
 ```
 
-The resulting source-to-HTML mapping:
+Die resultierende Zuordnung von Quelle zu HTML:
 
 ```
 src/index.md            -->  /index.html (erreichbar unter /)
@@ -103,42 +103,42 @@ Wenn du auf eine Seite deiner Website verlinken möchtest, die nicht von VitePre
 **Input**
 
 ```md
-[Link to pure.html](/pure.html){target="_self"}
+[Link zu pure.html](/pure.html){target="_self"}
 ```
 
 **Ausgabe**
 
-[Link to pure.html](/pure.html){target="_self"}
+[Link zu pure.html](/pure.html){target="_self"}
 
 ::: tip Hinweis
 
-Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` in the link (resolved relative to the current page by the browser).
+Bei Markdown-Links wird `base` auzumatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` im Link (resolved relative zu the current page by the browser).
 
 Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 
 ```md
-<a href="/pure.html" target="_self">Link to pure.html</a>
+<a href="/pure.html" target="_self">Link zu pure.html</a>
 ```
 
 :::
 
 ## Saubere URLs erzeugen
 
-::: warning Server Support Required
+::: warning Serverunterstützung erforderlich
 Um saubere URLs mit VitePress bereitzustellen, ist Unterstützung auf Serverseite erforderlich.
 :::
 
-Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` enden. Manche Benutzer bevorzugen jedoch "Clean URLs" without the `.html` extension - for example, `example.com/path` instead of `example.com/path.html`.
+Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` enden. Manche Benutzer bevorzugen jedoch "Saubere URLs" ohne die Erweiterung `.html` – beispielsweise `example.com/path` statt `example.com/path.html`.
 
 Einige Server oder Hosting-Plattformen (beispielsweise Netlify, Vercel und GitHub Pages) können eine URL wie `/foo` ohne Weiterleitung auf `/foo.html` abbilden, wenn diese Datei existiert:
 
 - Netlify and GitHub Seiten support this by default.
-- Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
+- Bei Vercel muss the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
+Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) Konfigurationsoption so setzen, dass:
 
-- Inbound links between pages are generated without the `.html` extension.
-- If current path ends with `.html`, the router will perform a client-side redirect to the extension-less path.
+- Links zwischen Seiten ohne die Erweiterung `.html` erzeugt werden.
+- Wenn der aktuelle Pfad mit `.html` endet, führt der Router eine clientseitige Weiterleitung zum Pfad ohne Erweiterung durch.
 
 Wenn du deinen Server jedoch nicht entsprechend konfigurieren kannst, musst du stattdessen manuell die folgende Verzeichnisstruktur verwenden:
 
@@ -190,7 +190,7 @@ export default {
 }
 ```
 
-Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose to list all the paths if you have many packages. Given that they all have the same file structure, you can simplify the config like this:
+Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose zu list all the paths if you have many packages. Da alle dieselbe Dateistruktur haben, kannst du die Konfiguration so vereinfachen:
 
 ```ts
 export default {
@@ -200,9 +200,9 @@ export default {
 }
 ```
 
-Die Rewrite-Pfade werden mit dem Paket `path-to-regexp` kompiliert – weitere Informationen findest du in [dessen Dokumentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) for more advanced syntax.
+Die Rewrite-Pfade werden mit dem Paket `path-zu-regexp` kompiliert – weitere Informationen findest du in [dessen Dokumentation](https://github.com/pillarjs/path-zu-regexp/tree/6.x#parameters) für eine fortgeschrittenere Syntax.
 
-`rewrites` can also be a function that receives the original path und gibt den neuen Pfad zurück:
+`rewrites` kann auch eine Funktion sein, die den ursprünglichen Pfad erhält und gibt den neuen Pfad zurück:
 
 ```ts
 export default {
@@ -214,10 +214,10 @@ export default {
 
 ::: warning Relative Links bei Rewrites
 
-Wenn Rewrites aktiviert sind, sollten **relative Links auf den umgeschriebenen Pfaden basieren**. Um beispielsweise einen relativen Link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
+Wenn Rewrites aktiviert sind, sollten **relative Links auf den umgeschriebenen Pfaden basieren**. Um beispielsweise einen relativen Link from `packages/pkg-a/src/pkg-a-code.md` zu `packages/pkg-b/src/pkg-b-code.md`, solltest du verwenden:
 
 ```md
-[Link to PKG B](../pkg-b/pkg-b-code)
+[Link zu PKG B](../pkg-b/pkg-b-code)
 ```
 :::
 
@@ -227,7 +227,7 @@ Du kannst mit einer einzigen Markdown-Datei und dynamischen Daten viele Seiten e
 
 ### Pfad-Loader-Datei
 
-Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
+Da VitePress ein statischer Website-Generazur ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, benötigen wir `packages/[pkg].paths.js` (`.ts` is also supported):
 
 ```
 .
@@ -238,7 +238,7 @@ Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seiten
 
 Der Paths Loader sollte ein Objekt mit einer Methode `paths` als Standardexport bereitstellen. Die Methode `paths` sollte ein Array von Objekten mit einer Eigenschaft `params` zurückgeben. Jedes dieser Objekte erzeugt eine entsprechende Seite.
 
-Given the following `paths` array:
+Bei folgendem `paths`-Array:
 
 ```js
 // packages/[pkg].paths.js
@@ -363,7 +363,7 @@ export default {
 
 ### Vorlagen- und Datendateien überwachen
 
-Wenn Seiteninhalte aus Vorlagen oder externen Datenquellen erzeugt werden, kannst du die Option `watch` verwenden, um Seiten während der Entwicklung automatisch neu zu erzeugen, wenn sich diese Dateien ändern:
+Wenn Seiteninhalte aus Vorlagen oder externen Datenquellen erzeugt werden, kannst du die Option `watch` verwenden, um Seiten während der Entwicklung auzumatisch neu zu erzeugen, wenn sich diese Dateien ändern:
 
 ```js
 // posts/[slug].paths.js
@@ -387,7 +387,7 @@ export default {
 
       return {
         params: { slug: data.slug },
-        content: renderTemplate(data)  // Use template to generate content
+        content: renderTemplate(data)  // Use template zu generate content
       }
     })
   }
@@ -396,7 +396,7 @@ export default {
 
 Die Option `watch` funktioniert genauso wie bei [Data Loadern](./Daten-loading#Daten-from-local-files):
 
-- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
+- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) zu match files
 - Muster sind relativ zur `.paths.js`-Datei selbst
 - Änderungen an überwachten Dateien lösen während der Entwicklung eine Seitengenerierung und HMR aus
 - In Produktions-Builds werden alle Seiten unabhängig von der `watch`-Konfiguration einmal erzeugt

From 00284774a149c76cfbf5c6a25834fbdbb5c86ddc Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:16 +0200
Subject: [PATCH 093/199] docs(de): translate remaining guide prose

---
 docs/de/guide/sitemap-generation.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/sitemap-generation.md b/docs/de/guide/sitemap-generation.md
index 47846642e..0f58df3c5 100644
--- a/docs/de/guide/sitemap-generation.md
+++ b/docs/de/guide/sitemap-generation.md
@@ -1,10 +1,10 @@
 ---
-description: a sitemap.xml file for your VitePress site to improve search engine discoverability.
+description: a sitemap.xml file for your VitePress site zu improve search engine discoverability.
 ---
 
 # Sitemap-Generierung
 
-VitePress comes with out-of-the-box support for generating a `sitemap.xml` file for your site. To enable it, add the following to your `.vitepress/config.js`:
+VitePress unterstützt standardmäßig die Erzeugung von a `sitemap.xml` file for your site. To enable it, add the following zu your `.vitepress/config.js`:
 
 ```ts
 export default {
@@ -14,11 +14,11 @@ export default {
 }
 ```
 
-To have `<lastmod>` tags in your `sitemap.xml`, you can enable the [`lastUpdated`](../reference/default-theme-last-updated) option.
+Damit `<lastmod>` tags in your `sitemap.xml`, you can enable the [`lastUpdated`](../reference/default-theme-last-updated) option.
 
 ## Optionen
 
-Sitemap support is powered by the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it to the `sitemap` option in your config file. These will be passed directly to the `SitemapStream` constructor. Refer to the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for more details. Beispiel:
+Sitemap wird unterstützt durch the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it zu the `sitemap` option in deiner Konfiguration file. These will be passed directly zu the `SitemapStream` construczur. Refer zu the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for weitere Details. Beispiel:
 
 ```ts
 export default {
@@ -29,7 +29,7 @@ export default {
 }
 ```
 
-Wenn du're Verwendung `base` in your config, you should append it to the `hostname` option:
+Wenn du're Verwendung `base` in deiner Konfiguration, you should append it zu the `hostname` option:
 
 ```ts
 export default {
@@ -42,7 +42,7 @@ export default {
 
 ## `transformItems` Hook
 
-Du kannst use the `sitemap.transformItems` hook to modify the sitemap items before they are written to the `sitemap.xml` file. This hook is genannt with an array of sitemap items and expects an array of sitemap items to be returned. Beispiel:
+Du kannst use the `sitemap.transformItems` hook zu modify the sitemap items before they are written zu the `sitemap.xml` file. This hook is genannt with an array of sitemap items and expects an array of sitemap items zu be returned. Beispiel:
 
 ```ts
 export default {

From c5c493762f3fa4f826da2a99f32266922e76ec5c Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:18 +0200
Subject: [PATCH 094/199] docs(de): translate remaining guide prose

---
 docs/de/guide/ssr-compat.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
index 33f0e6c4d..ca33f9bd1 100644
--- a/docs/de/guide/ssr-compat.md
+++ b/docs/de/guide/ssr-compat.md
@@ -1,17 +1,17 @@
 ---
 outline: deep
-description: your VitePress theme Komponenten and custom code are compatible with server-side rendering.
+description: your VitePress theme Komponenten and cuszum code are compatible with server-side rendering.
 ---
 
 # SSR-Kompatibilität
 
-VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all custom code in theme Komponenten are subject to SSR-Kompatibilität.
+VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all cuszum code in theme Komponenten are subject zu SSR-Kompatibilität.
 
-The [SSR section in official Vue docs](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is to only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue Komponenten.
+Der [SSR-Abschnitt in der offiziellen Vue-Dokumentation](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is zu only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue Komponenten.
 
 ## `<ClientOnly>`
 
-Wenn du are Verwendung or demoing Komponenten that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the built-in `<ClientOnly>` Komponente:
+Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for example, contain cuszum directives), kannst du sie in die integrierte `<ClientOnly>` Komponente:
 
 ```md
 <ClientOnly>
@@ -19,11 +19,11 @@ Wenn du are Verwendung or demoing Komponenten that are not SSR-friendly (for exa
 </ClientOnly>
 ```
 
-## Libraries that Access Browser API on Import
+## Bibliotheken, die beim Import auf Browser-APIs zugreifen
 
-Some Komponenten or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need to dynamically import them.
+Some Komponenten or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need zu dynamically import them.
 
-### Importing in Mounted Hook
+### Import in einem Mounted-Hook
 
 ```vue
 <script setup>
@@ -37,9 +37,9 @@ onMounted(() => {
 </script>
 ```
 
-### Conditional Import
+### Bedingter Import
 
-Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
+Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` Flags (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
 
 ```js
 if (!import.meta.env.SSR) {
@@ -49,7 +49,7 @@ if (!import.meta.env.SSR) {
 }
 ```
 
-Since [`Theme.enhanceApp`](./custom-theme#theme-interface) can be async, you can conditionally import and register Vue plugins that access browser APIs on import:
+Da [`Theme.enhanceApp`](./cuszum-theme#theme-interface) asynchron sein kann, kannst du Vue-Plugins bedingt importieren und registrieren that access browser APIs on import:
 
 ```js [.vitepress/theme/index.js]
 /** @type {import('vitepress').Theme} */
@@ -88,7 +88,7 @@ VitePress stellt bereit a convenience helper for importing Vue Komponenten that
 import { defineClientComponent } from 'vitepress'
 
 const ClientComp = defineClientComponent(() => {
-  return import('component-that-access-window-on-import')
+  return import('Komponente-that-access-window-on-import')
 })
 </script>
 
@@ -97,7 +97,7 @@ const ClientComp = defineClientComponent(() => {
 </template>
 ```
 
-Du kannst also pass props/children/slots to the target Komponente:
+Du kannst also pass props/children/slots zu the target Komponente:
 
 ```vue
 <script setup>
@@ -106,9 +106,9 @@ import { defineClientComponent } from 'vitepress'
 
 const clientCompRef = ref(null)
 const ClientComp = defineClientComponent(
-  () => import('component-that-access-window-on-import'),
+  () => import('Komponente-that-access-window-on-import'),
 
-  // args are passed to h() - https://vuejs.org/api/render-function.html#h
+  // args are passed zu h() - https://vuejs.org/api/render-function.html#h
   [
     {
       ref: clientCompRef
@@ -120,7 +120,7 @@ const ClientComp = defineClientComponent(
     }
   ],
 
-  // callback after the component is loaded, can be async
+  // callback after the Komponente is loaded, asynchron sein kann
   () => {
     console.log(clientCompRef.value)
   }

From 64c995d4ee948af2b848c843da6a513c0cf9613d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:20 +0200
Subject: [PATCH 095/199] docs(de): translate remaining guide prose

---
 docs/de/guide/using-vue.md | 76 +++++++++++++++++++-------------------
 1 file changed, 38 insertions(+), 38 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index 12a3ff77a..e0df0bbfe 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -4,19 +4,19 @@ description: Vue Komponenten and dynamic templating features directly inside Mar
 
 # Vue in Markdown verwenden
 
-In VitePress, each Markdown file is compiled into HTML and then processed as a [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
+In VitePress, each Markdown file is compiled inzu HTML and then processed as a [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
 
-It's worth noting that VitePress leverages Vue's compiler to automatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. In short, you only pay for the dynamic parts on any given page.
+Beachte, dass VitePress leverages Vue's compiler zu auzumatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized inzu single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. Kurz gesagt betrifft der zusätzliche Aufwand nur die dynamischen Teile einer jeweiligen Seite.
 
 ::: tip SSR-Kompatibilität
-All Vue usage needs to be SSR-compatible. See [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
+All Vue usage needs zu be SSR-compatible. Siehe [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
 :::
 
 ## Templating
 
 ### Interpolation
 
-Each Markdown file is first compiled into HTML and then passed on as a Vue Komponente to the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
+Each Markdown file is first compiled inzu HTML and then passed on as a Vue Komponente zu the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
 
 **Input**
 
@@ -30,7 +30,7 @@ Each Markdown file is first compiled into HTML and then passed on as a Vue Kompo
 
 ### Directives
 
-Directives also work (note that by design, raw HTML is also valid in Markdown):
+Direktiven funktionieren ebenfalls (note that by design, raw HTML is also valid in Markdown):
 
 **Input**
 
@@ -44,7 +44,7 @@ Directives also work (note that by design, raw HTML is also valid in Markdown):
 
 ## `<script>` and `<style>`
 
-Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
+Elemente `<script>` und `<style>` auf der obersten Ebene von Markdown-Dateien funktionieren genauso wie in Vue-SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Beachte außerdem, dass alle Tags **nach** dem Frontmatter stehen müssen:
 
 ```html
 ---
@@ -61,21 +61,21 @@ const count = ref(0)
 
 The count is: {{ count }}
 
-<button :class="$style.button" @click="count++">Increment</button>
+<butzun :class="$style.butzun" @click="count++">Increment</butzun>
 
 <style module>
-.button {
+.butzun {
   color: red;
   font-weight: bold;
 }
 </style>
 ```
 
-::: warning Avoid `<style scoped>` in Markdown
-When verwendet in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
+::: warning Vermeide `<style scoped>` in Markdown
+When verwendet in Markdown, `<style scoped>` requires adding special attributes zu every element on the current page, which will significantly bloat the page size. `<style module>` ist vorzuziehen, wenn eine lokal begrenzte Gestaltung auf einer Seite benötigt wird.
 :::
 
-You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access to current page's metadata:
+You also have access zu VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access zu current page's metadata:
 
 **Input**
 
@@ -100,39 +100,39 @@ const { page } = useData()
 }
 ```
 
-## Using Components
+## Komponenten verwenden
 
 Du kannst import and use Vue Komponenten directly in Markdown files.
 
 ### Importing in Markdown
 
-If a Komponente is only verwendet by a few pages, it's recommended to explicitly import them where they are verwendet. Dies ermöglicht them to be properly code-split and only geladen when the relevant pages are shown:
+If a Komponente is only verwendet by a few pages, it's recommended zu explicitly import them where they are verwendet. Dies ermöglicht them zu be properly code-split and only geladen when the relevant pages are shown:
 
 ```md
 <script setup>
-import CustomComponent from '../components/CustomComponent.vue'
+import CuszumComponent from '../Komponentes/CuszumComponent.vue'
 </script>
 
 # Docs
 
-This is a .md using a custom component
+This is a .md using a cuszum Komponente
 
-<CustomComponent />
+<CuszumComponent />
 
 ## More docs
 
 ...
 ```
 
-### Registering Components Globally
+### Komponenten global registrieren
 
-If a Komponente is going to be verwendet on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
+If a Komponente is going zu be verwendet on most of the pages, they can be registered globally by cuszumizing the Vue app instance. Siehe relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
 
-::: warning IMPORTANT
-Stelle sicher a custom Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
+::: warning WICHTIG
+Stelle sicher a cuszum Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead zu hydration mismatch because `<p>` does not allow block elements zu be placed inside it.
 :::
 
-### Using Components In Headers <ComponentInHeader />
+### Komponenten verwenden In Headers <ComponentInHeader />
 
 Du kannst use Vue Komponenten in the headers, but note the difference between the following syntaxes:
 
@@ -144,11 +144,11 @@ Du kannst use Vue Komponenten in the headers, but note the difference between th
 The HTML wrapped by `<code>` will be displayed as-is; only the HTML that is **not** wrapped will be parsed by Vue.
 
 ::: tip
-The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and verwendet for both the sidebar and document title).
+Das Ausgabe-HTML wird von [Markdown-it](https://github.com/Markdown-it/Markdown-it), während die analysierten Überschriften von VitePress (and verwendet for both the sidebar and document title).
 :::
 
 
-## Escaping
+## Maskierung
 
 Du kannst escape Vue interpolations by wrapping them in a `<span>` or other elements with the `v-pre` directive:
 
@@ -164,7 +164,7 @@ This <span v-pre>{{ will be displayed as-is }}</span>
   <p>This <span v-pre>{{ will be displayed as-is }}</span></p>
 </div>
 
-Alternatively, you can wrap the entire paragraph in a `v-pre` custom container:
+Alternativ kannst du den gesamten Absatz in a `v-pre` cuszum container:
 
 ```md
 ::: v-pre
@@ -182,9 +182,9 @@ Alternatively, you can wrap the entire paragraph in a `v-pre` custom container:
 
 </div>
 
-## Unescape in Code Blocks
+## Maskierung in Codeblöcken aufheben
 
-Standardmäßig, all fenced code blocks are automatisch wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
+Standardmäßig, all fenced code blocks are auzumatisch wrapped with `v-pre`, umschlossen, sodass darin keine Vue-Syntax verarbeitet wird. Um Vue-artige Interpolation innerhalb von Codeblöcken zu aktivieren, kannst du an die Sprache das `-vue` suffix, e.g. `js-vue`:
 
 **Input**
 
@@ -200,11 +200,11 @@ Hello {{ 1 + 1 }}
 Hello {{ 1 + 1 }}
 ```
 
-Beachte, dass this might prevent certain tokens from being syntax highlighted properly.
+Beachte, dass this might prevent certain zukens from being syntax highlighted properly.
 
-## Using CSS Pre-processors
+## CSS-Präprozessoren verwenden
 
-VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need to install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
+VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need zu install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
 
 ```
 # .scss and .sass
@@ -217,7 +217,7 @@ npm install -D less
 npm install -D stylus
 ```
 
-Then you can use the following in Markdown and theme Komponenten:
+Danach kannst du Folgendes verwenden in Markdown and theme Komponenten:
 
 ```vue
 <style lang="sass">
@@ -226,9 +226,9 @@ Then you can use the following in Markdown and theme Komponenten:
 </style>
 ```
 
-## Using Teleports
+## Teleports verwenden
 
-VitePress currently has SSG support for teleports to body only. For other targets, you can wrap them inside the built-in `<ClientOnly>` Komponente or inject the teleport markup into the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
+VitePress currently has SSG support for teleports zu body only. For other targets, kannst du sie in die integrierte `<ClientOnly>` Komponente or inject the teleport markup inzu the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
 
 <ModalDemo />
 
@@ -238,7 +238,7 @@ VitePress currently has SSG support for teleports to body only. For other target
 
 ```md
 <ClientOnly>
-  <Teleport to="#modal">
+  <Teleport zu="#modal">
     <div>
       // ...
     </div>
@@ -260,14 +260,14 @@ import ComponentInHeader from '../../Komponenten/ComponentInHeader.vue'
 </style>
 
 
-## VS Code IntelliSense Support
+## VS-Code-IntelliSense-Unterstützung
 
-<!-- Based on https://github.com/vuejs/language-tools/pull/4321 -->
+<!-- Based on https://github.com/vuejs/language-zuols/pull/4321 -->
 
-Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, to enable it for `.md` files, you need to make some adjustments to the configuration files.
+Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, zu enable it for `.md` files, you need zu make some adjustments zu the configuration files.
 
 
-1. Add `.md` pattern to the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:
+1. Add `.md` pattern zu the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:
 
 ::: code-group
 ```json [tsconfig.json]
@@ -284,7 +284,7 @@ Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS
 ```
 :::
 
-2. Add `markdown` to the `vue.server.includeLanguages` option in the VS Code setting:
+2. Add `markdown` zu the `vue.server.includeLanguages` option in the VS Code setting:
 
 ::: code-group
 ```json [.vscode/settings.json]

From 4f374a6bf2611f8f59da1e55d10ad5641a1e801d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:23 +0200
Subject: [PATCH 096/199] docs(de): translate remaining guide prose

---
 docs/de/guide/what-is-vitepress.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index 6f2689278..b5991c249 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -1,10 +1,10 @@
 ---
-description: Ein statischer Website-Generator zum Erstellen schneller, inhaltsorientierter Websites auf Basis von Vite und Vue.
+description: Ein statischer Website-Generazur zum Erstellen schneller, inhaltsorientierter Websites auf Basis von Vite und Vue.
 ---
 
 # Was ist VitePress?
 
-VitePress ist ein [statischer Website-Generator](https://en.wikipedia.org/wiki/Static_site_generator) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
+VitePress ist ein [statischer Website-Generazur](https://en.wikipedia.org/wiki/Static_site_generazur) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
 
 ::: tip {no-title}
 Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./getting-started).
@@ -20,7 +20,7 @@ Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./gettin
 
 - **Blogs, Portfolios und Marketing-Websites**
 
-  VitePress supports [fully customized themes](./custom-theme), with the developer experience of a stundard Vite + Vue application. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [load data](./data-loading) (local or remote) und [dynamically generate routes](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
+  VitePress supports [fully cuszumized themes](./cuszum-theme), with the developer experience of a stundard Vite + Vue application. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [load data](./data-loading) (local or remote) und [dynamically generate routes](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
 
   Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
 
@@ -32,7 +32,7 @@ VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mi
 
 - **[Built-in Markdown Extensions:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
 
-- **[Vue-Enhanced Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks to Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
+- **[Vue-Enhanced Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks zu Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
 
 ## Leistung
 
@@ -40,20 +40,20 @@ Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollst
 
 - **Schnelles erstes Laden**
 
-  The initial visit to any page will be served the static, pre-rendered HTML for fast loading speed und optimal SEO. The page then loads a JavaScript bundle that turns the page into a Vue SPA ("hydration"). Contrary to common assumptions of SPA hydration being slow, this process is actually extremely fast thanks to Vue 3's raw performance und compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
+  The initial visit zu any page will be served the static, pre-rendered HTML for fast loading speed und optimal SEO. The page then loads a JavaScript bundle that turns the page inzu a Vue SPA ("hydration"). Contrary zu common assumptions of SPA hydration being slow, this process is actually extremely fast thanks zu Vue 3's raw performance und compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
 
 - **Schnelle Navigation nach dem Laden**
 
-  More importantly, the SPA model leads to better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched und dynamically updated. VitePress also automatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
+  More importantly, the SPA model leads zu better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched und dynamically updated. VitePress also auzumatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
 
 - **Interaktivität ohne Nachteile**
 
-  To be able to hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue component und compiled into JavaScript. This may sound inefficient, but the Vue compiler is smart enough to separate the static und dynamic parts, minimizing both the hydration cost und payload size. For the initial page load, the static parts are automatically eliminated from the JavaScript payload und skipped during hydration.
+  To be able zu hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue Komponente und compiled inzu JavaScript. This may sound inefficient, but the Vue compiler is smart enough zu separate the static und dynamic parts, minimizing both the hydration cost und payload size. For the initial page load, the static parts are auzumatically eliminated from the JavaScript payload und skipped during hydration.
 
 ## Und was ist mit VuePress?
 
-VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible customization API.
+VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible cuszumization API.
 
-The API difference between VitePress und VuePress 1 mostly lies in theming und customization. If you are using VuePress 1 with the default theme, it should be relatively straightforward to migrate to VitePress.
+The API difference between VitePress und VuePress 1 mostly lies in theming und cuszumization. If you are using VuePress 1 with the default theme, it should be relatively straightforward zu migrate zu VitePress.
 
-Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided to focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, und VuePress 2 has been hunded over to the VuePress community team for further development und maintenance.
+Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided zu focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, und VuePress 2 has been hunded over zu the VuePress community team for further development und maintenance.

From 8b9f3a4c74f0daa90e2292431ec8742e6ceb1e07 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:56 +0200
Subject: [PATCH 097/199] docs(de): translate guide prose safely

---
 docs/de/guide/migration-from-vuepress.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/guide/migration-from-vuepress.md b/docs/de/guide/migration-from-vuepress.md
index b38e074ce..da390deed 100644
--- a/docs/de/guide/migration-from-vuepress.md
+++ b/docs/de/guide/migration-from-vuepress.md
@@ -4,13 +4,13 @@
 
 ### Seitenleiste
 
-The sidebar is no longer auzumatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) zu dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
+The sidebar is no longer automatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
 
 ## Markdown
 
 ### Bilder
 
-Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config auzumatisch when you use static image.
+Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatisch when you use static image.
 
 Hence, now you can render images without `img` tag.
 
@@ -23,8 +23,8 @@ Hence, now you can render images without `img` tag.
 For dynamic images you still need `withBase` as shown in [Base URL guide](./asset-handling#base-url).
 :::
 
-Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex zu find and replace it with `![$2]($1)` zu replace all the images with `![](...)` syntax.
+Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex to find and replace it with `![$2]($1)` to replace all the images with `![](...)` syntax.
 
 ---
 
-more zu follow...
+more to follow...

From aa8865ccf54699c7a22c02056e5ae5e11e9ca103 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:56:59 +0200
Subject: [PATCH 098/199] docs(de): translate guide prose safely

---
 docs/de/guide/mpa-mode.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/guide/mpa-mode.md b/docs/de/guide/mpa-mode.md
index 255baed9a..4f11b5ccd 100644
--- a/docs/de/guide/mpa-mode.md
+++ b/docs/de/guide/mpa-mode.md
@@ -6,15 +6,15 @@ description: MPA (Multi-Seite Application) mode in VitePress for zero-JavaScript
 
 MPA (Multi-Seite Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
 
-In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit zuols.
+In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit tools.
 
-However, due zu the absence of SPA navigation, cross-page links will lead zu full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
+However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
 
-Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need zu use the special `<script client>` tag:
+Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need to use the special `<script client>` tag:
 
 ```html
 <script client>
-document.querySeleczur('h1').addEventListener('click', () => {
+document.querySelector('h1').addEventListener('click', () => {
   console.log('client side JavaScript!')
 })
 </script>
@@ -22,6 +22,6 @@ document.querySeleczur('h1').addEventListener('click', () => {
 # Hello
 ```
 
-`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled zugether, while client script for a specific page will be split for that page only.
+`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled together, while client script for a specific page will be split for that page only.
 
 Beachte, dass `<script client>` is **not evaluated as Vue Komponente code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be verwendet if your site requires absolutely minimal client-side interactivity.

From 75f4d4ec82e663c29bf5f3c6729f5b1745909721 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:02 +0200
Subject: [PATCH 099/199] docs(de): translate guide prose safely

---
 docs/de/guide/routing.md | 32 ++++++++++++++++----------------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 05d57cfce..2f1f4f22e 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -68,7 +68,7 @@ Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `sr
 ```
 .                          # Projektstammverzeichnis
 ├─ .vitepress              # Konfigurationsverzeichnis
-└─ src                     # Quellverzeichnis
+└─ src                     # source dir
    ├─ getting-started.md
    └─ index.md
 ```
@@ -103,21 +103,21 @@ Wenn du auf eine Seite deiner Website verlinken möchtest, die nicht von VitePre
 **Input**
 
 ```md
-[Link zu pure.html](/pure.html){target="_self"}
+[Link to pure.html](/pure.html){target="_self"}
 ```
 
 **Ausgabe**
 
-[Link zu pure.html](/pure.html){target="_self"}
+[Link to pure.html](/pure.html){target="_self"}
 
 ::: tip Hinweis
 
-Bei Markdown-Links wird `base` auzumatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` im Link (resolved relative zu the current page by the browser).
+Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` in the link (resolved relative to the current page by the browser).
 
 Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 
 ```md
-<a href="/pure.html" target="_self">Link zu pure.html</a>
+<a href="/pure.html" target="_self">Link to pure.html</a>
 ```
 
 :::
@@ -133,11 +133,11 @@ Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` en
 Einige Server oder Hosting-Plattformen (beispielsweise Netlify, Vercel und GitHub Pages) können eine URL wie `/foo` ohne Weiterleitung auf `/foo.html` abbilden, wenn diese Datei existiert:
 
 - Netlify and GitHub Seiten support this by default.
-- Bei Vercel muss the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
+- Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) Konfigurationsoption so setzen, dass:
+Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
 
-- Links zwischen Seiten ohne die Erweiterung `.html` erzeugt werden.
+- Links zwischen Seiten werden ohne die Erweiterung `.html` erzeugt.
 - Wenn der aktuelle Pfad mit `.html` endet, führt der Router eine clientseitige Weiterleitung zum Pfad ohne Erweiterung durch.
 
 Wenn du deinen Server jedoch nicht entsprechend konfigurieren kannst, musst du stattdessen manuell die folgende Verzeichnisstruktur verwenden:
@@ -190,7 +190,7 @@ export default {
 }
 ```
 
-Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose zu list all the paths if you have many packages. Da alle dieselbe Dateistruktur haben, kannst du die Konfiguration so vereinfachen:
+Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose to list all the paths if you have many packages. Da alle dieselbe Dateistruktur haben, kannst du die Konfiguration so vereinfachen:
 
 ```ts
 export default {
@@ -200,7 +200,7 @@ export default {
 }
 ```
 
-Die Rewrite-Pfade werden mit dem Paket `path-zu-regexp` kompiliert – weitere Informationen findest du in [dessen Dokumentation](https://github.com/pillarjs/path-zu-regexp/tree/6.x#parameters) für eine fortgeschrittenere Syntax.
+Die Rewrite-Pfade werden mit dem Paket `path-to-regexp` kompiliert – weitere Informationen findest du in [dessen Dokumentation](https://github.com/pillarjs/path-to-regexp/tree/6.x#parameters) für eine fortgeschrittenere Syntax.
 
 `rewrites` kann auch eine Funktion sein, die den ursprünglichen Pfad erhält und gibt den neuen Pfad zurück:
 
@@ -214,10 +214,10 @@ export default {
 
 ::: warning Relative Links bei Rewrites
 
-Wenn Rewrites aktiviert sind, sollten **relative Links auf den umgeschriebenen Pfaden basieren**. Um beispielsweise einen relativen Link from `packages/pkg-a/src/pkg-a-code.md` zu `packages/pkg-b/src/pkg-b-code.md`, solltest du verwenden:
+Wenn Rewrites aktiviert sind, sollten **relative Links auf den umgeschriebenen Pfaden basieren**. Um beispielsweise einen relativen Link from `packages/pkg-a/src/pkg-a-code.md` to `packages/pkg-b/src/pkg-b-code.md`, you should use:
 
 ```md
-[Link zu PKG B](../pkg-b/pkg-b-code)
+[Link to PKG B](../pkg-b/pkg-b-code)
 ```
 :::
 
@@ -227,7 +227,7 @@ Du kannst mit einer einzigen Markdown-Datei und dynamischen Daten viele Seiten e
 
 ### Pfad-Loader-Datei
 
-Da VitePress ein statischer Website-Generazur ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, benötigen wir `packages/[pkg].paths.js` (`.ts` is also supported):
+Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
 
 ```
 .
@@ -363,7 +363,7 @@ export default {
 
 ### Vorlagen- und Datendateien überwachen
 
-Wenn Seiteninhalte aus Vorlagen oder externen Datenquellen erzeugt werden, kannst du die Option `watch` verwenden, um Seiten während der Entwicklung auzumatisch neu zu erzeugen, wenn sich diese Dateien ändern:
+Wenn Seiteninhalte aus Vorlagen oder externen Datenquellen erzeugt werden, kannst du die Option `watch` verwenden, um Seiten während der Entwicklung automatisch neu zu erzeugen, wenn sich diese Dateien ändern:
 
 ```js
 // posts/[slug].paths.js
@@ -387,7 +387,7 @@ export default {
 
       return {
         params: { slug: data.slug },
-        content: renderTemplate(data)  // Use template zu generate content
+        content: renderTemplate(data)  // Use template to generate content
       }
     })
   }
@@ -396,7 +396,7 @@ export default {
 
 Die Option `watch` funktioniert genauso wie bei [Data Loadern](./Daten-loading#Daten-from-local-files):
 
-- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) zu match files
+- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
 - Muster sind relativ zur `.paths.js`-Datei selbst
 - Änderungen an überwachten Dateien lösen während der Entwicklung eine Seitengenerierung und HMR aus
 - In Produktions-Builds werden alle Seiten unabhängig von der `watch`-Konfiguration einmal erzeugt

From 7769b83f2394038e550053990ef4d941a6512ac7 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:05 +0200
Subject: [PATCH 100/199] docs(de): translate guide prose safely

---
 docs/de/guide/sitemap-generation.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/sitemap-generation.md b/docs/de/guide/sitemap-generation.md
index 0f58df3c5..8c2a73871 100644
--- a/docs/de/guide/sitemap-generation.md
+++ b/docs/de/guide/sitemap-generation.md
@@ -1,10 +1,10 @@
 ---
-description: a sitemap.xml file for your VitePress site zu improve search engine discoverability.
+description: a sitemap.xml file for your VitePress site to improve search engine discoverability.
 ---
 
 # Sitemap-Generierung
 
-VitePress unterstützt standardmäßig die Erzeugung von a `sitemap.xml` file for your site. To enable it, add the following zu your `.vitepress/config.js`:
+VitePress unterstützt standardmäßig die Erzeugung einer `sitemap.xml`-Datei für deine Website. Um dies zu aktivieren, füge Folgendes zu deiner `.vitepress/config.js` hinzu:
 
 ```ts
 export default {
@@ -14,11 +14,11 @@ export default {
 }
 ```
 
-Damit `<lastmod>` tags in your `sitemap.xml`, you can enable the [`lastUpdated`](../reference/default-theme-last-updated) option.
+Damit deine `sitemap.xml`-Datei `<lastmod>`-Tags enthält, kannst du die [`lastUpdated`](../reference/default-theme-last-updated) option.
 
 ## Optionen
 
-Sitemap wird unterstützt durch the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it zu the `sitemap` option in deiner Konfiguration file. These will be passed directly zu the `SitemapStream` construczur. Refer zu the [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) for weitere Details. Beispiel:
+Sitemap wird unterstützt durch the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it to the `sitemap` option in your config file. Diese werden direkt an the `SitemapStream` constructor. Siehe die [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) für weitere Details. Beispiel:
 
 ```ts
 export default {
@@ -29,7 +29,7 @@ export default {
 }
 ```
 
-Wenn du're Verwendung `base` in deiner Konfiguration, you should append it zu the `hostname` option:
+Wenn du're Verwendung `base` in your config, you should append it to the `hostname` option:
 
 ```ts
 export default {
@@ -42,7 +42,7 @@ export default {
 
 ## `transformItems` Hook
 
-Du kannst use the `sitemap.transformItems` hook zu modify the sitemap items before they are written zu the `sitemap.xml` file. This hook is genannt with an array of sitemap items and expects an array of sitemap items zu be returned. Beispiel:
+Du kannst use the `sitemap.transformItems` Hook verwenden, um die Sitemap-Einträge vor dem Schreiben in die `sitemap.xml` file. This hook is genannt with an array of sitemap items und erwartet, dass ein Array von Sitemap-Einträgen zurückgegeben wird. Beispiel:
 
 ```ts
 export default {

From 7e6279edde43d71546698d90e0ed081d293b51bc Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:07 +0200
Subject: [PATCH 101/199] docs(de): translate guide prose safely

---
 docs/de/guide/ssr-compat.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
index ca33f9bd1..0c59df503 100644
--- a/docs/de/guide/ssr-compat.md
+++ b/docs/de/guide/ssr-compat.md
@@ -1,17 +1,17 @@
 ---
 outline: deep
-description: your VitePress theme Komponenten and cuszum code are compatible with server-side rendering.
+description: your VitePress theme Komponenten and custom code are compatible with server-side rendering.
 ---
 
 # SSR-Kompatibilität
 
-VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all cuszum code in theme Komponenten are subject zu SSR-Kompatibilität.
+VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all custom code in theme Komponenten are subject to SSR-Kompatibilität.
 
-Der [SSR-Abschnitt in der offiziellen Vue-Dokumentation](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is zu only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue Komponenten.
+Der [SSR-Abschnitt in der offiziellen Vue-Dokumentation](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. Als Faustregel gilt, dass Browser-/DOM-APIs nur in `beforeMount` or `mounted` hooks of Vue Komponenten.
 
 ## `<ClientOnly>`
 
-Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for example, contain cuszum directives), kannst du sie in die integrierte `<ClientOnly>` Komponente:
+Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for example, contain custom directives), kannst du sie in die integrierte `<ClientOnly>` Komponente:
 
 ```md
 <ClientOnly>
@@ -21,7 +21,7 @@ Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for
 
 ## Bibliotheken, die beim Import auf Browser-APIs zugreifen
 
-Some Komponenten or libraries access browser APIs **on import**. To use code that assumes a browser environment on import, you need zu dynamically import them.
+Some Komponenten or libraries access browser APIs **on import**. Um Code zu verwenden, der beim Import eine Browserumgebung voraussetzt, musst du ihn dynamisch importieren.
 
 ### Import in einem Mounted-Hook
 
@@ -39,7 +39,7 @@ onMounted(() => {
 
 ### Bedingter Import
 
-Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` Flags (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
+Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
 
 ```js
 if (!import.meta.env.SSR) {
@@ -49,7 +49,7 @@ if (!import.meta.env.SSR) {
 }
 ```
 
-Da [`Theme.enhanceApp`](./cuszum-theme#theme-interface) asynchron sein kann, kannst du Vue-Plugins bedingt importieren und registrieren that access browser APIs on import:
+Da [`Theme.enhanceApp`](./custom-theme#theme-interface) asynchron sein kann, kannst du Vue-Plugins bedingt importieren und registrieren that access browser APIs on import:
 
 ```js [.vitepress/theme/index.js]
 /** @type {import('vitepress').Theme} */
@@ -88,7 +88,7 @@ VitePress stellt bereit a convenience helper for importing Vue Komponenten that
 import { defineClientComponent } from 'vitepress'
 
 const ClientComp = defineClientComponent(() => {
-  return import('Komponente-that-access-window-on-import')
+  return import('component-that-access-window-on-import')
 })
 </script>
 
@@ -97,7 +97,7 @@ const ClientComp = defineClientComponent(() => {
 </template>
 ```
 
-Du kannst also pass props/children/slots zu the target Komponente:
+Du kannst also pass props/children/slots to the target Komponente:
 
 ```vue
 <script setup>
@@ -106,9 +106,9 @@ import { defineClientComponent } from 'vitepress'
 
 const clientCompRef = ref(null)
 const ClientComp = defineClientComponent(
-  () => import('Komponente-that-access-window-on-import'),
+  () => import('component-that-access-window-on-import'),
 
-  // args are passed zu h() - https://vuejs.org/api/render-function.html#h
+  // args are passed to h() - https://vuejs.org/api/render-function.html#h
   [
     {
       ref: clientCompRef
@@ -120,7 +120,7 @@ const ClientComp = defineClientComponent(
     }
   ],
 
-  // callback after the Komponente is loaded, asynchron sein kann
+  // callback after the component is loaded, can be async
   () => {
     console.log(clientCompRef.value)
   }

From e990fd3fb47bdc678f1145049c1e3730b57e3ba9 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:10 +0200
Subject: [PATCH 102/199] docs(de): translate guide prose safely

---
 docs/de/guide/using-vue.md | 58 +++++++++++++++++++-------------------
 1 file changed, 29 insertions(+), 29 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index e0df0bbfe..736bdb981 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -4,19 +4,19 @@ description: Vue Komponenten and dynamic templating features directly inside Mar
 
 # Vue in Markdown verwenden
 
-In VitePress, each Markdown file is compiled inzu HTML and then processed as a [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
+In VitePress wird jede Markdown-Datei in HTML kompiliert und anschließend als [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
 
-Beachte, dass VitePress leverages Vue's compiler zu auzumatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized inzu single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. Kurz gesagt betrifft der zusätzliche Aufwand nur die dynamischen Teile einer jeweiligen Seite.
+Beachte, dass VitePress leverages Vue's compiler to automatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. Kurz gesagt betrifft der zusätzliche Aufwand nur die dynamischen Teile einer jeweiligen Seite.
 
 ::: tip SSR-Kompatibilität
-All Vue usage needs zu be SSR-compatible. Siehe [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
+Jede Verwendung von Vue muss SSR-kompatibel sein. See [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
 :::
 
 ## Templating
 
 ### Interpolation
 
-Each Markdown file is first compiled inzu HTML and then passed on as a Vue Komponente zu the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
+Each Markdown file is first compiled into HTML and then passed on as a Vue Komponente to the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
 
 **Input**
 
@@ -44,7 +44,7 @@ Direktiven funktionieren ebenfalls (note that by design, raw HTML is also valid
 
 ## `<script>` and `<style>`
 
-Elemente `<script>` und `<style>` auf der obersten Ebene von Markdown-Dateien funktionieren genauso wie in Vue-SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Beachte außerdem, dass alle Tags **nach** dem Frontmatter stehen müssen:
+Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
 
 ```html
 ---
@@ -61,21 +61,21 @@ const count = ref(0)
 
 The count is: {{ count }}
 
-<butzun :class="$style.butzun" @click="count++">Increment</butzun>
+<button :class="$style.button" @click="count++">Increment</button>
 
 <style module>
-.butzun {
+.button {
   color: red;
   font-weight: bold;
 }
 </style>
 ```
 
-::: warning Vermeide `<style scoped>` in Markdown
-When verwendet in Markdown, `<style scoped>` requires adding special attributes zu every element on the current page, which will significantly bloat the page size. `<style module>` ist vorzuziehen, wenn eine lokal begrenzte Gestaltung auf einer Seite benötigt wird.
+::: warning Avoid `<style scoped>` in Markdown
+When verwendet in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
 :::
 
-You also have access zu VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access zu current page's metadata:
+You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access to current page's metadata:
 
 **Input**
 
@@ -106,18 +106,18 @@ Du kannst import and use Vue Komponenten directly in Markdown files.
 
 ### Importing in Markdown
 
-If a Komponente is only verwendet by a few pages, it's recommended zu explicitly import them where they are verwendet. Dies ermöglicht them zu be properly code-split and only geladen when the relevant pages are shown:
+If a Komponente is only verwendet by a few pages, it's recommended to explicitly import them where they are verwendet. Dies ermöglicht them to be properly code-split and only geladen when the relevant pages are shown:
 
 ```md
 <script setup>
-import CuszumComponent from '../Komponentes/CuszumComponent.vue'
+import CustomComponent from '../components/CustomComponent.vue'
 </script>
 
 # Docs
 
-This is a .md using a cuszum Komponente
+This is a .md using a custom component
 
-<CuszumComponent />
+<CustomComponent />
 
 ## More docs
 
@@ -126,10 +126,10 @@ This is a .md using a cuszum Komponente
 
 ### Komponenten global registrieren
 
-If a Komponente is going zu be verwendet on most of the pages, they can be registered globally by cuszumizing the Vue app instance. Siehe relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
+If a Komponente is going to be verwendet on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
 
-::: warning WICHTIG
-Stelle sicher a cuszum Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead zu hydration mismatch because `<p>` does not allow block elements zu be placed inside it.
+::: warning IMPORTANT
+Stelle sicher a custom Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
 :::
 
 ### Komponenten verwenden In Headers <ComponentInHeader />
@@ -144,7 +144,7 @@ Du kannst use Vue Komponenten in the headers, but note the difference between th
 The HTML wrapped by `<code>` will be displayed as-is; only the HTML that is **not** wrapped will be parsed by Vue.
 
 ::: tip
-Das Ausgabe-HTML wird von [Markdown-it](https://github.com/Markdown-it/Markdown-it), während die analysierten Überschriften von VitePress (and verwendet for both the sidebar and document title).
+The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and verwendet for both the sidebar and document title).
 :::
 
 
@@ -164,7 +164,7 @@ This <span v-pre>{{ will be displayed as-is }}</span>
   <p>This <span v-pre>{{ will be displayed as-is }}</span></p>
 </div>
 
-Alternativ kannst du den gesamten Absatz in a `v-pre` cuszum container:
+Alternativ kannst du den gesamten Absatz in a `v-pre` custom container:
 
 ```md
 ::: v-pre
@@ -184,7 +184,7 @@ Alternativ kannst du den gesamten Absatz in a `v-pre` cuszum container:
 
 ## Maskierung in Codeblöcken aufheben
 
-Standardmäßig, all fenced code blocks are auzumatisch wrapped with `v-pre`, umschlossen, sodass darin keine Vue-Syntax verarbeitet wird. Um Vue-artige Interpolation innerhalb von Codeblöcken zu aktivieren, kannst du an die Sprache das `-vue` suffix, e.g. `js-vue`:
+Standardmäßig, all fenced code blocks are automatisch wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
 
 **Input**
 
@@ -200,11 +200,11 @@ Hello {{ 1 + 1 }}
 Hello {{ 1 + 1 }}
 ```
 
-Beachte, dass this might prevent certain zukens from being syntax highlighted properly.
+Beachte, dass this might prevent certain tokens from being syntax highlighted properly.
 
 ## CSS-Präprozessoren verwenden
 
-VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need zu install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
+VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need to install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
 
 ```
 # .scss and .sass
@@ -217,7 +217,7 @@ npm install -D less
 npm install -D stylus
 ```
 
-Danach kannst du Folgendes verwenden in Markdown and theme Komponenten:
+Then you can use the following in Markdown and theme Komponenten:
 
 ```vue
 <style lang="sass">
@@ -228,7 +228,7 @@ Danach kannst du Folgendes verwenden in Markdown and theme Komponenten:
 
 ## Teleports verwenden
 
-VitePress currently has SSG support for teleports zu body only. For other targets, kannst du sie in die integrierte `<ClientOnly>` Komponente or inject the teleport markup inzu the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
+VitePress currently has SSG support for teleports to body only. For other targets, kannst du sie in die integrierte `<ClientOnly>` Komponente or inject the teleport markup into the correct location in your final page HTML through [`postRender` hook](../reference/site-config#postrender).
 
 <ModalDemo />
 
@@ -238,7 +238,7 @@ VitePress currently has SSG support for teleports zu body only. For other target
 
 ```md
 <ClientOnly>
-  <Teleport zu="#modal">
+  <Teleport to="#modal">
     <div>
       // ...
     </div>
@@ -262,12 +262,12 @@ import ComponentInHeader from '../../Komponenten/ComponentInHeader.vue'
 
 ## VS-Code-IntelliSense-Unterstützung
 
-<!-- Based on https://github.com/vuejs/language-zuols/pull/4321 -->
+<!-- Based on https://github.com/vuejs/language-tools/pull/4321 -->
 
-Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, zu enable it for `.md` files, you need zu make some adjustments zu the configuration files.
+Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS Code plugin](https://marketplace.visualstudio.com/items?itemName=Vue.volar). However, to enable it for `.md` files, you need to make some adjustments to the configuration files.
 
 
-1. Add `.md` pattern zu the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:
+1. Add `.md` pattern to the `include` and `vueCompilerOptions.vitePressExtensions` options in the tsconfig/jsconfig file:
 
 ::: code-group
 ```json [tsconfig.json]
@@ -284,7 +284,7 @@ Vue stellt bereit IntelliSense support out of the box via the [Vue - Official VS
 ```
 :::
 
-2. Add `markdown` zu the `vue.server.includeLanguages` option in the VS Code setting:
+2. Add `markdown` to the `vue.server.includeLanguages` option in the VS Code setting:
 
 ::: code-group
 ```json [.vscode/settings.json]

From 6e1734df696d323cfa6030af48deb502b1198bc5 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:41 +0200
Subject: [PATCH 103/199] docs(de): translate reference prose

---
 docs/de/reference/cli.md | 46 ++++++++++++++++++++--------------------
 1 file changed, 23 insertions(+), 23 deletions(-)

diff --git a/docs/de/reference/cli.md b/docs/de/reference/cli.md
index cc1e24d24..a2ab098ea 100644
--- a/docs/de/reference/cli.md
+++ b/docs/de/reference/cli.md
@@ -1,12 +1,12 @@
 ---
-description: of VitePress CLI commands including dev, build, preview, and init.
+description: Referenz der VitePress-CLI-Befehle einschließlich dev, build, preview und init.
 ---
 
 # Kommandozeilenschnittstelle
 
 ## `vitepress dev`
 
-Start VitePress dev Server using designated directory as root. Defaults to current directory. The `dev` command can also be omitted when running in current directory.
+Starte den VitePress-Entwicklungsserver mit dem angegebenen Verzeichnis als Stammverzeichnis. Standardmäßig wird das aktuelle Verzeichnis verwendet. Der Befehl `dev` kann beim Ausführen im aktuellen Verzeichnis weggelassen werden.
 
 ### Verwendung
 
@@ -20,18 +20,18 @@ vitepress dev [root]
 
 ### Optionen
 
-| Option          | Description                                                       |
+| Option          | Beschreibung                                                       |
 | --------------- | ----------------------------------------------------------------- |
-| `--open [path]` | Open Browser on startup (`boolean \| string`)                     |
-| `--port <port>` | Specify port (`number`)                                           |
-| `--base <path>` | Public base path (Standard: `/`) (`string`)                        |
-| `--cors`        | Aktivieren CORS                                                       |
-| `--strictPort`  | Exit if specified port is already in use (`boolean`)              |
-| `--force`       | Force the optimizer to ignore the cache and re-bundle (`boolean`) |
+| `--open [path]` | Browser beim Start öffnen (`boolean \| string`)                     |
+| `--port <port>` | Port festlegen (`number`)                                           |
+| `--base <path>` | Öffentlicher Basispfad (Standard: `/`) (`string`)                        |
+| `--cors`        | CORS aktivieren                                                       |
+| `--strictPort`  | Beenden, wenn der angegebene Port bereits verwendet wird (`boolean`)              |
+| `--force`       | Optimierer zwingen, den Cache zu ignorieren und erneut zu bündeln (`boolean`) |
 
 ## `vitepress build`
 
-Build the VitePress site for Produktion.
+VitePress-Website für die Produktion erstellen.
 
 ### Verwendung
 
@@ -41,18 +41,18 @@ vitepress build [root]
 
 ### Optionen
 
-| Option                         | Description                                                                                                         |
+| Option                         | Beschreibung                                                                                                         |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
-| `--mpa` (experimental)         | Build in [MPA mode](../guide/mpa-mode) without Client-side hydration (`boolean`)                                    |
-| `--base <path>`                | Public base path (Standard: `/`) (`string`)                                                                          |
-| `--assetsBase <url>`           | URL prefix the generated assets are served from, e.g. a CDN (`string`)                                              |
-| `--target <target>`            | Transpile target (Standard: `"modules"`) (`string`)                                                                  |
-| `--outDir <dir>`               | Output directory relative to **cwd** (Standard: `<root>/.vitepress/dist`) (`string`)                                 |
-| `--assetsInlineLimit <number>` | Static asset base64 inline threshold in bytes (Standard: `4096`) (`number`)                                          |
+| `--mpa` (experimental)         | Im [MPA-Modus erstellen](../guide/mpa-mode) ohne clientseitige Hydration (`boolean`)                                    |
+| `--base <path>`                | Öffentlicher Basispfad (Standard: `/`) (`string`)                                                                          |
+| `--assetsBase <url>`           | URL-Präfix, von dem die erzeugten Assets ausgeliefert werden, z. B. ein CDN (`string`)                                              |
+| `--target <target>`            | Transpilierungsziel (Standard: `"modules"`) (`string`)                                                                  |
+| `--outDir <dir>`               | Ausgabeverzeichnis relativ zu **cwd** (Standard: `<root>/.vitepress/dist`) (`string`)                                 |
+| `--assetsInlineLimit <number>` | Grenzwert für das Base64-Einbetten statischer Assets in Byte (Standard: `4096`) (`number`)                                          |
 
 ## `vitepress preview`
 
-Locally preview the Produktion build.
+Produktions-Build lokal in der Vorschau anzeigen.
 
 ### Verwendung
 
@@ -62,15 +62,15 @@ vitepress preview [root]
 
 ### Optionen
 
-| Option          | Description                                |
+| Option          | Beschreibung                                |
 | --------------- | ------------------------------------------ |
-| `--base <path>` | Public base path (Standard: `/`) (`string`) |
-| `--assetsBase <url>` | URL prefix the generated assets are served from, e.g. a CDN (`string`) |
-| `--port <port>` | Specify port (`number`)                    |
+| `--base <path>` | Öffentlicher Basispfad (Standard: `/`) (`string`) |
+| `--assetsBase <url>` | URL-Präfix, von dem die erzeugten Assets ausgeliefert werden, z. B. ein CDN (`string`) |
+| `--port <port>` | Port festlegen (`number`)                    |
 
 ## `vitepress init`
 
-Start the [Setup Wizard](../guide/getting-started#setup-wizard) in current directory.
+Starte den [Einrichtungsassistenten](../guide/getting-started#setup-wizard) in current directory.
 
 ### Verwendung
 

From 1f7f5e2856ddb200351ad30c36e11eddb3047398 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:43 +0200
Subject: [PATCH 104/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-badge.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/reference/default-theme-badge.md b/docs/de/reference/default-theme-badge.md
index 82ec55219..98288fa00 100644
--- a/docs/de/reference/default-theme-badge.md
+++ b/docs/de/reference/default-theme-badge.md
@@ -1,14 +1,14 @@
 ---
-description: Use the Badge component to add status labels to headers in VitePress documentation.
+description: Verwende die Badge-Komponente, um Statusbezeichnungen zu Überschriften in der VitePress-Dokumentation hinzuzufügen.
 ---
 
 # Badge
 
-The badge lets you add status to your headers. Zum Beispiel, it could be useful to specify the section's type, or supported version.
+Mit dem Badge kannst du deinen Überschriften einen Status hinzufügen. Zum Beispiel kann damit der Typ eines Abschnitts oder die unterstützte Version angegeben werden.
 
 ## Verwendung
 
-Du kannst use the `Badge` component which is globally verfügbar.
+Du kannst die global verfügbare `Badge`-Komponente verwenden.
 
 ```html
 ### Title <Badge type="info" text="default" />
@@ -17,7 +17,7 @@ Du kannst use the `Badge` component which is globally verfügbar.
 ### Title <Badge type="danger" text="deprecated" />
 ```
 
-Code above renders like:
+Der obige Code wird folgendermaßen dargestellt:
 
 ### Title <Badge type="info" text="Standard" />
 ### Title <Badge type="tip" text="^1.9.0" />
@@ -26,7 +26,7 @@ Code above renders like:
 
 ## Eigenes Children
 
-`<Badge>` accept `children`, which will be displayed in the badge.
+`<Badge>` akzeptiert `children`, die im Badge angezeigt werden.
 
 ```html
 ### Title <Badge type="info">custom element</Badge>
@@ -34,9 +34,9 @@ Code above renders like:
 
 ### Title <Badge type="info">custom element</Badge>
 
-## Anpassen Type Color
+## Farbe und Typ anpassen
 
-Du kannst customize the style of badges by overriding css variables. The following are the Standard values:
+Du kannst das Erscheinungsbild der Badges durch Überschreiben der CSS-Variablen anpassen. Die folgenden Werte sind die Standardwerte:
 
 ```css
 :root {
@@ -72,7 +72,7 @@ Du kannst customize the style of badges by overriding css variables. The followi
 
 ## `<Badge>`
 
-`<Badge>` component accepts following props:
+Die Komponente `<Badge>` akzeptiert die folgenden Props:
 
 ```ts
 interface Props {

From 0e0b6583a31d9c4fa7fb7c34ef8265931d4822b2 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:45 +0200
Subject: [PATCH 105/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-carbon-ads.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-carbon-ads.md b/docs/de/reference/default-theme-carbon-ads.md
index 4d3a618b8..97c5e5fa9 100644
--- a/docs/de/reference/default-theme-carbon-ads.md
+++ b/docs/de/reference/default-theme-carbon-ads.md
@@ -1,10 +1,10 @@
 ---
-description: Integrate Carbon Ads into your VitePress site using the Standard theme's built-in support.
+description: Integriere Carbon Ads mithilfe der integrierten Unterstützung des Standard-Themes in deine VitePress-Website.
 ---
 
 # Carbon Ads
 
-VitePress has built in native support for [Carbon Ads](https://www.carbonads.net/). By defining the Carbon Ads credentials in config, VitePress will display ads on the page.
+VitePress has built in native support for [Carbon Ads](https://www.carbonads.net/). Wenn du die Carbon-Ads-Zugangsdaten in der Konfiguration definierst, zeigt VitePress Anzeigen auf der Seite an.
 
 ```js
 export default {
@@ -18,7 +18,7 @@ export default {
 }
 ```
 
-These values are used to call carbon CDN script as shown below.
+Diese Werte werden verwendet, um das Carbon-CDN-Skript wie unten gezeigt aufzurufen.
 
 The `format` option supports `classic`, `responsive`, and `cover`.
 

From e1dfabb198935c027913fa7d473f51c486adc547 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:48 +0200
Subject: [PATCH 106/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-edit-link.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/reference/default-theme-edit-link.md b/docs/de/reference/default-theme-edit-link.md
index 5013cf30c..40131aefa 100644
--- a/docs/de/reference/default-theme-edit-link.md
+++ b/docs/de/reference/default-theme-edit-link.md
@@ -1,12 +1,12 @@
 ---
-description: Display an edit link on doc pages to let users suggest changes on GitHub or GitLab.
+description: Zeige auf Dokumentationsseiten einen Bearbeitungslink an, über den Nutzer Änderungen auf GitHub oder GitLab vorschlagen können.
 ---
 
 # Bearbeitungslink
 
-## Site-Level Config
+## Websiteweite Konfiguration
 
-Bearbeitungslink lets you display a link to edit the page on Git management services such as GitHub, or GitLab. To enable it, add `themeConfig.editLink` options to your config.
+Mit dem Bearbeitungslink kannst du einen Link zum Bearbeiten der Seite bei Git-Verwaltungsdiensten wie GitHub oder GitLab anzeigen. Füge zum Aktivieren die Optionen von `themeConfig.editLink` zu deiner Konfiguration hinzu.
 
 ```js
 export default {
@@ -18,7 +18,7 @@ export default {
 }
 ```
 
-The `pattern` option defines the URL structure for the link, and `:path` is going to be replaced with the page path.
+Die Option `pattern` definiert die URL-Struktur des Links. `:path` wird durch den Seitenpfad ersetzt.
 
 Du kannst also put a pure function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the URL string.
 
@@ -38,9 +38,9 @@ export default {
 }
 ```
 
-It should not have side-effects nor access anything outside of its scope since it will be serialized and executed in the Browser.
+Die Funktion sollte keine Seiteneffekte haben und nicht auf Dinge außerhalb ihres Gültigkeitsbereichs zugreifen, da sie serialisiert und im Browser ausgeführt wird.
 
-By Standard, this will add the link text "Edit this page" at the bottom of the doc page. Du kannst customize this text by defining the `text` option.
+Standardmäßig wird am unteren Rand der Dokumentationsseite der Linktext „Diese Seite bearbeiten“ hinzugefügt. Du kannst diesen Text über die Option `text` anpassen.
 
 ```js
 export default {
@@ -53,9 +53,9 @@ export default {
 }
 ```
 
-## Frontmatter Config
+## Frontmatter-Konfiguration
 
-Dies can be deaktiviert per-page using the `editLink` option on frontmatter:
+Dies kann pro Seite über die Option `editLink` im Frontmatter deaktiviert werden:
 
 ```yaml
 ---

From 2d752f73c5df395cdf035b6f17af835e719c04b1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:51 +0200
Subject: [PATCH 107/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-footer.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/reference/default-theme-footer.md b/docs/de/reference/default-theme-footer.md
index 58384746e..2c0e95021 100644
--- a/docs/de/reference/default-theme-footer.md
+++ b/docs/de/reference/default-theme-footer.md
@@ -1,10 +1,10 @@
 ---
-description: Konfigurieren the global footer displayed at the bottom of VitePress pages.
+description: Konfiguriere die globale Fußzeile, die am unteren Rand von VitePress-Seiten angezeigt wird.
 ---
 
 # Fußzeile
 
-VitePress will display global footer at the bottom of the page when `themeConfig.footer` is present.
+VitePress zeigt eine globale Fußzeile am unteren Rand der Seite an, wenn `themeConfig.footer` vorhanden ist.
 
 ```ts
 export default {
@@ -27,7 +27,7 @@ export interface Fußzeile {
 }
 ```
 
-The above Konfiguration also supports HTML strings. So, for example, if you want to configure footer text to have some links, you can adjust the Konfiguration as follows:
+Die obige Konfiguration unterstützt außerdem HTML-Zeichenketten. Wenn du beispielsweise Links in der Fußzeile anzeigen möchtest, kannst du die Konfiguration wie folgt anpassen:
 
 ```ts
 export default {
@@ -41,12 +41,12 @@ export default {
 ```
 
 ::: warning
-Only inline elements can be used in `message` and `copyright` as they are rendered inside a `<p>` element. Wenn du want to add block elements, consider using [`layout-bottom`](../guide/extending-Standard-theme#layout-slots) slot instead.
+In `message` und `copyright` können nur Inline-Elemente verwendet werden, da sie innerhalb eines `<p>`-Elements gerendert werden. Wenn du want to add block elements, consider using [`layout-bottom`](../guide/extending-Standard-theme#layout-slots) slot instead.
 :::
 
 Hinweis that footer will not be displayed when the [SideBar](./Standard-theme-sidebar) is visible.
 
-## Frontmatter Config
+## Frontmatter-Konfiguration
 
 Dies can be deaktiviert per-page using the `footer` option on frontmatter:
 

From 12cbab32e2b63f8dec84ada802b29afea863bf2d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:53 +0200
Subject: [PATCH 108/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-home-page.md | 26 ++++++++++----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/de/reference/default-theme-home-page.md b/docs/de/reference/default-theme-home-page.md
index e5ef6c9ea..914af76ac 100644
--- a/docs/de/reference/default-theme-home-page.md
+++ b/docs/de/reference/default-theme-home-page.md
@@ -1,5 +1,5 @@
 ---
-description: Konfigurieren the VitePress Standard theme home page layout with hero sections, features, and custom content.
+description: Konfiguriere das Startseitenlayout des VitePress-Standard-Themes mit Hero-Bereichen, Features und eigenen Inhalten.
 ---
 
 # Startseite
@@ -12,11 +12,11 @@ layout: home
 ---
 ```
 
-However, this option alone wouldn't do much. Du kannst add several different pre templated "sections" to the homepage by setting additional other options such as `hero` and `features`.
+Diese Option allein bewirkt jedoch noch nicht viel. Du kannst der Startseite verschiedene vorgefertigte „Bereiche“ hinzufügen, indem du zusätzliche Optionen wie `hero` und `features` setzt.
 
-## Hero Section
+## Hero-Bereich
 
-The Hero section comes at the top of the homepage. Here's how you can configure the Hero section.
+Der Hero-Bereich befindet sich oben auf der Startseite. So kannst du ihn konfigurieren.
 
 ```yaml
 ---
@@ -82,9 +82,9 @@ interface HeroAction {
 }
 ```
 
-### Customizing the name color
+### Farbe des Namens anpassen
 
-VitePress uses the brand color (`--vp-c-brand-1`) for the `name`. However, you may customize this color by overriding `--vp-home-hero-name-color` variable.
+VitePress verwendet für `name` die Markenfarbe (`--vp-c-brand-1`). Du kannst diese Farbe jedoch durch Überschreiben der Variable `--vp-home-hero-name-color` anpassen.
 
 ```css
 :root {
@@ -92,7 +92,7 @@ VitePress uses the brand color (`--vp-c-brand-1`) for the `name`. However, you m
 }
 ```
 
-Also you may customize it further by combining `--vp-home-hero-name-background` to give the `name` gradient color.
+Du kannst es außerdem weiter anpassen, indem du `--vp-home-hero-name-background` to give the `name` gradient color.
 
 ```css
 :root {
@@ -101,11 +101,11 @@ Also you may customize it further by combining `--vp-home-hero-name-background`
 }
 ```
 
-## Features Section
+## Feature-Bereich
 
-In Features section, you can list any number of features you would like to show right after the Hero section. To configure it, pass `features` option to the frontmatter.
+Im Feature-Bereich kannst du beliebig viele Features auflisten, die direkt nach dem Hero-Bereich angezeigt werden sollen. Übergebe dazu die Option `features` im Frontmatter.
 
-Du kannst provide an icon for each feature, which can be an emoji or any type of image. When the configured icon is an image (svg, png, jpeg...), you must provide the icon with the proper width and height; you can also provide the description, its intrinsic size as well as its variants for dark and light theme when erforderlich.
+Du kannst für jedes Feature ein Symbol angeben, which can be an emoji or any type of image. When the configured icon is an image (svg, png, jpeg...), you must provide the icon with the proper width and height; you can also provide the description, its intrinsic size as well as its variants for dark and light theme wenn erforderlich.
 
 ```yaml
 ---
@@ -171,9 +171,9 @@ type FeatureIcon =
     }
 ```
 
-## Markdown Inhalt
+## Markdown-Inhalt
 
-Du kannst add additional content to your site's homepage just by adding Markdown below the `---` frontmatter divider.
+Du kannst zusätzliche Inhalte zur Startseite deiner Website hinzufügen, indem du einfach unterhalb der `---`-Frontmatter-Trennlinie Markdown hinzufügst.
 
 ````md
 ---
@@ -195,5 +195,5 @@ npx vitepress init
 ````
 
 ::: info
-VitePress didn't always auto-style the extra content of the `layout: home` page. To revert to older behavior, you can add `markdownStyles: falsch` to the frontmatter.
+VitePress hat zusätzliche Inhalte einer Seite mit `layout: home` nicht immer automatisch gestaltet. Um das frühere Verhalten wiederherzustellen, kannst du `markdownStyles: false` im Frontmatter setzen.
 :::

From a4aaf8ad40afb606663cadd1253715284e732768 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:57:56 +0200
Subject: [PATCH 109/199] docs(de): translate reference prose

---
 docs/de/reference/default-theme-last-updated.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/reference/default-theme-last-updated.md b/docs/de/reference/default-theme-last-updated.md
index 2a3538846..a57e1ae55 100644
--- a/docs/de/reference/default-theme-last-updated.md
+++ b/docs/de/reference/default-theme-last-updated.md
@@ -1,13 +1,13 @@
 ---
-description: Show the last updated timestamp on VitePress pages based on Git commit history.
+description: Zeige den Zeitpunkt der letzten Aktualisierung von VitePress-Seiten anhand der Git-Commit-Historie an.
 ---
 
 # Letzte Aktualisierung
 
-The update time of the last content will be displayed in the lower right corner of the page. To enable it, add `lastUpdated` options to your config.
+Der Aktualisierungszeitpunkt des letzten Inhalts wird unten rechts auf der Seite angezeigt. Füge zum Aktivieren die Option `lastUpdated` zu deiner Konfiguration hinzu.
 
 ::: info
-VitePress displays the "last updated" time using the timestamp of the most recent Git commit for each file. To enable this, the Markdown file must be committed to Git.
+VitePress zeigt den Zeitpunkt der letzten Aktualisierung anhand des Zeitstempels des neuesten Git-Commits für jede Datei an. Dafür muss die Markdown-Datei in Git committed sein.
 
 Internally, VitePress runs `git log -1 --pretty="%ai"` on each file to retrieve its timestamp. If all pages show the same update time, it's likely due to shallow cloning (common in CI environments), which limits Git history.
 
@@ -20,16 +20,16 @@ To fix this in **GitHub Actions**, use the following in your workflow:
     fetch-depth: 0
 ```
 
-Other CI/CD platforms have similar settings.
+Andere CI/CD-Plattformen verfügen über ähnliche Einstellungen.
 
-If such options aren't verfügbar, you can prepend the `docs:build` command in your `package.json` with a manual fetch:
+Wenn solche Optionen nicht verfügbar sind, kannst du dem Befehl `docs:build` in deiner `package.json` einen manuellen Abruf voranstellen:
 
 ```json
 "docs:build": "git fetch --unshallow && vitepress build docs"
 ```
 :::
 
-## Site-Level Config
+## Websiteweite Konfiguration
 
 ```js
 export default {
@@ -37,7 +37,7 @@ export default {
 }
 ```
 
-## Frontmatter Config
+## Frontmatter-Konfiguration
 
 Dies can be deaktiviert per-page using the `lastUpdated` option on frontmatter:
 
@@ -47,4 +47,4 @@ lastUpdated: false
 ---
 ```
 
-Also refer [Standard-Theme: Letzte Aktualisierung](./Standard-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly deaktiviert at site or page level.
+Weitere Informationen findest du unter [Standard-Theme: Letzte Aktualisierung](./Standard-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly deaktiviert at site or page level.

From e083db3c47ca659c9e7d69e3afa91a72b5bef9f0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:38 +0200
Subject: [PATCH 111/199] docs(de): translate remaining reference prose

---
 docs/de/reference/default-theme-nav.md | 42 +++++++++++++-------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/docs/de/reference/default-theme-nav.md b/docs/de/reference/default-theme-nav.md
index 3b9c98c80..8e4e94a6e 100644
--- a/docs/de/reference/default-theme-nav.md
+++ b/docs/de/reference/default-theme-nav.md
@@ -1,14 +1,14 @@
 ---
-description: Konfigurieren the navigation bar in the VitePress default theme including site title, logo, and menu links.
+description: Konfiguriere die navigation bar in the VitePress default theme including site title, logo, and menu links.
 ---
 
 # Nav
 
-The Nav is the navigation bar displayed on top of the page. It contains the site title, global menu links, etc.
+Die Navigation ist die oben auf der Seite angezeigte Navigationsleiste. Sie enthält den Seitentitel, globale Menülinks usw.
 
 ## Site Title and Logo
 
-Standardmäßig, nav shows the title of the site referencing [`config.title`](./site-config#title) value. Wenn du would like to change what's displayed on nav, you may define custom text in `themeConfig.siteTitle` option.
+Standardmäßig, nav shows the title of the site referencing [`config.title`](./site-config#title) value. Wenn du die Anzeige in der Navigation ändern möchtest, kannst du einen eigenen Text in `themeConfig.siteTitle` option.
 
 ```js
 export default {
@@ -18,7 +18,7 @@ export default {
 }
 ```
 
-Wenn du have a logo for your site, you can display it by passing in the path to the image. Du solltest place the logo within `public` directly, and define the absolute path to it.
+Wenn du ein Logo für deine Website hast, kannst du es über den Bildpfad anzeigen. Du solltest das Logo direkt in `public` ablegen und den absoluten Pfad dazu angeben.
 
 ```js
 export default {
@@ -28,7 +28,7 @@ export default {
 }
 ```
 
-When adding a logo, it gets displayed along with the site title. If your logo is all you need and if you would like to hide the site title text, set `false` to the `siteTitle` option.
+Beim Hinzufügen eines Logos wird es zusammen mit dem Seitentitel angezeigt. If your logo is all you need and if you would like to hide the site title text, set `false` to the `siteTitle` option.
 
 ```js
 export default {
@@ -39,11 +39,11 @@ export default {
 }
 ```
 
-Du kannst also pass an object as logo if you want to add `alt` attribute or customize it based on dark/light mode. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
+Du kannst als Logo auch ein Objekt übergeben, wenn du ein `alt`-Attribut hinzufügen oder es abhängig vom Hell-/Dunkelmodus anpassen möchtest. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
 
 ## Navigation Links
 
-Du kannst define `themeConfig.nav` option to add links to your nav.
+Du kannst die Option `themeConfig.nav` definieren, um Links zur Navigation hinzuzufügen.
 
 ```js
 export default {
@@ -57,11 +57,11 @@ export default {
 }
 ```
 
-The `text` is the actual text displayed in nav, and the `link` is the link that will be navigated to when the text is clicked. For the link, set path to the actual file without `.md` prefix, and always start with `/`.
+`text` ist der tatsächlich angezeigte Text in der Navigation, und `link` ist das Ziel, das beim Anklicken des Textes geöffnet wird. Setze beim Link den Pfad zur tatsächlichen Datei ohne `.md` und beginne immer mit `/`.
 
 The `link` can also be a function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the path.
 
-Nav links can also be dropdown menus. To do this, set `items` key on link option.
+Navigationslinks können auch Dropdown-Menüs sein. Setze dazu den Schlüssel `items` in der Link-Option.
 
 ```js
 export default {
@@ -81,9 +81,9 @@ export default {
 }
 ```
 
-Beachte, dass dropdown menu title (`Dropdown Menu` in the above example) can not have `link` property since it becomes a button to open dropdown dialog.
+Beachte, dass der Titel des Dropdown-Menüs (`Dropdown Menu` in the above example) keine Eigenschaft `link` besitzen kann, da er zu einer Schaltfläche zum Öffnen des Dropdowns wird.
 
-Du kannst further add "sections" to the dropdown menu items as well by passing in more nested items.
+Du kannst den Dropdown-Menüeinträgen außerdem weitere „Abschnitte“ hinzufügen by passing in more nested items.
 
 ```js
 export default {
@@ -120,9 +120,9 @@ export default {
 }
 ```
 
-### Anpassen link's "active" state
+### Status des Links "active" state
 
-Nav menu items will be highlighted when the current page is under the matching path. if you would like to customize the path to be matched, define `activeMatch` property and regex as a string value.
+Navigationseinträge werden hervorgehoben, wenn sich die aktuelle Seite unter dem passenden Pfad befindet. Wenn du den abzugleichenden Pfad anpassen möchtest, definiere die Eigenschaft `activeMatch` als Zeichenkette mit einem regulären Ausdruck.
 
 ```js
 export default {
@@ -144,9 +144,9 @@ export default {
 `activeMatch` is expected to be a regex string, but you must define it as a string. We can't use actual RegExp object here because it isn't serializable during the build time.
 :::
 
-### Anpassen link's "target" and "rel" attributes
+### Status des Links "target" and "rel" attributes
 
-Standardmäßig, VitePress automatisch determines `target` and `rel` attributes based on whether the link is an external link. But if you want, you can customize them too.
+Standardmäßig bestimmt VitePress automatisch `target` and `rel` attributes abhängig davon, ob der Link extern ist. But if you want, you can customize them too.
 
 ```js
 export default {
@@ -167,9 +167,9 @@ export default {
 
 Refer [`socialLinks`](./default-theme-config#sociallinks).
 
-## Eigenes Komponenten
+## Eigene Komponenten
 
-Du kannst include custom components in the navigation bar by using the `component` option. The `component` key should be the Vue component name, and must be registered globally using [Theme.enhanceApp](../guide/custom-theme#theme-interface).
+Du kannst eigene Komponenten mithilfe der Option `component` in die Navigationsleiste aufnehmen. by using the `component` option. The `component` key should be the Vue component name, and must be registered globally using [Theme.enhanceApp](../guide/custom-theme#theme-interface).
 
 ```js [.vitepress/config.js]
 export default {
@@ -195,7 +195,7 @@ export default {
 }
 ```
 
-Then, you need to register the component globally:
+Anschließend musst du die Komponente global registrieren:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -213,9 +213,9 @@ export default {
 }
 ```
 
-Your component will be rendered in the navigation bar. VitePress will provide the following additional props to the component:
+Deine Komponente wird in der Navigationsleiste gerendert. VitePress will provide the following additional props to the component:
 
-- `screenMenu`: an optional boolean indicating whether the component is inside mobile navigation menu
-- `menu`: an optional boolean indicating whether the component is inside a dropdown panel — for example, the `⋯` menu that nav items collapse into when they don't fit the bar. In both these contexts, render a flat list instead of a floating flyout, which would end up nested inside the panel
+- `screenMenu`: ein optionaler Boolean, der angibt, ob sich die Komponente im mobilen Navigationsmenü befindet
+- `menu`: ein optionaler Boolean, der angibt, ob sich die Komponente in einem Dropdown-Bereich befindet — for example, the `⋯` menu that nav items collapse into when they don't fit the bar. In both these contexts, render a flat list instead of a floating flyout, which would end up nested inside the panel
 
 Du kannst check an example in the e2e tests [here](https://github.com/vuejs/vitepress/tree/main/__tests__/e2e/.vitepress).

From 23dfb23fcb42a2c9bcfb266004893a6357bb3d3e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:40 +0200
Subject: [PATCH 112/199] docs(de): translate remaining reference prose

---
 docs/de/reference/default-theme-prev-next-links.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-prev-next-links.md b/docs/de/reference/default-theme-prev-next-links.md
index 38221be48..56f846a7c 100644
--- a/docs/de/reference/default-theme-prev-next-links.md
+++ b/docs/de/reference/default-theme-prev-next-links.md
@@ -1,10 +1,10 @@
 ---
-description: Anpassen the previous and next page links displayed at the bottom of doc pages in VitePress.
+description: Passe die am unteren Rand von Dokumentationsseiten in VitePress angezeigten Links zur vorherigen und nächsten Seite an.
 ---
 
 # Prev Weiter Links
 
-Du kannst customize the text and link for the previous and next pages (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
+Du kannst Text und Link für die vorherige und nächste Seite anpassen (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
 
 ## prev
 
@@ -44,4 +44,4 @@ Du kannst customize the text and link for the previous and next pages (shown at
 
 ## next
 
-Same as `prev` but for the next page.
+Wie `prev`, aber für die nächste Seite.

From 464410772c65286896bfa2e3feb51b13e067cafb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:43 +0200
Subject: [PATCH 113/199] docs(de): translate remaining reference prose

---
 docs/de/reference/default-theme-search.md | 54 +++++++++++------------
 1 file changed, 27 insertions(+), 27 deletions(-)

diff --git a/docs/de/reference/default-theme-search.md b/docs/de/reference/default-theme-search.md
index 1285a813c..d6b5fe39d 100644
--- a/docs/de/reference/default-theme-search.md
+++ b/docs/de/reference/default-theme-search.md
@@ -1,13 +1,13 @@
 ---
 outline: deep
-description: Set up local or Algolia-powered search for your VitePress site.
+description: Richte eine lokale oder von Algolia bereitgestellte Suche für deine VitePress-Website ein.
 ---
 
 # Suche
 
-## Local Suche
+## Lokale Suche
 
-VitePress unterstützt fuzzy full-text search using an in-browser index thanks to [minisearch](https://github.com/lucaong/minisearch/). To enable this feature, simply set the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
+VitePress unterstützt eine unscharfe Volltextsuche mithilfe eines Index im Browser dank [minisearch](https://github.com/lucaong/minisearch/). Um diese Funktion zu aktivieren, setze einfach the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -21,7 +21,7 @@ export default defineConfig({
 })
 ```
 
-Beispiel result:
+Beispielergebnis:
 
 ![screenshot of the search modal](/search.png)
 
@@ -35,7 +35,7 @@ Alternatively, you can use [Algolia DocSearch](#algolia-search) or some communit
 
 ### i18n {#local-search-i18n}
 
-Du kannst use a config like this to use multilingual search:
+Du kannst eine Konfiguration wie diese verwenden, um eine mehrsprachige Suche einzurichten:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -76,9 +76,9 @@ export default defineConfig({
 })
 ```
 
-### miniSearch options
+### MiniSearch-Optionen
 
-Du kannst configure MiniSearch like this:
+Du kannst MiniSearch folgendermaßen konfigurieren:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -110,15 +110,15 @@ export default defineConfig({
 })
 ```
 
-Mehr erfahren in [MiniSearch docs](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
+Weitere Informationen findest du in der [MiniSearch-Dokumentation](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
 
 ::: info Document IDs
-Suche document IDs (as seen by `searchOptions.filter`, `boostDocument`, and in the raw index) are site-relative paths like `/guide/page.html#section` — they do not include [`base`](../reference/site-config#base). The theme resolves them against the base when rendering results.
+Die Dokument-IDs der Suche (wie sie von `searchOptions.filter`, `boostDocument`, and in the raw index) are site-relative paths like `/guide/page.html#section` — they enthalten nicht [`base`](../reference/site-config#base). Das Theme löst sie beim Rendern der Ergebnisse gegen `base` auf.
 :::
 
-### Eigenes content renderer
+### Eigenen Inhalts-Renderer
 
-Du kannst customize the function used to render the markdown content before indexing it:
+Du kannst die Funktion anpassen, mit der der Markdown-Inhalt vor der Indizierung gerendert wird:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -142,11 +142,11 @@ export default defineConfig({
 })
 ```
 
-This function will be stripped from client-side site data, so you can use Node.js APIs in it.
+Diese Funktion wird aus den clientseitigen Websitedaten entfernt, sodass du darin Node.js-APIs verwenden kannst.
 
 #### Beispiel: Excluding pages from search
 
-Du kannst exclude pages from search by adding `search: false` to the frontmatter of the page. Alternatively:
+Du kannst Seiten aus der Suche ausschließen by adding `search: false` to the frontmatter of the page. Alternativ:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -169,7 +169,7 @@ export default defineConfig({
 ```
 
 ::: warning Note
-In case a custom `_render` function is provided, you need to handle the `search: false` frontmatter yourself. Also, the `env` object won't be completely populated before `md.renderAsync` is called, so any checks on optional `env` properties like `frontmatter` should be done after that.
+Wenn eine eigene `_render`-Funktion bereitgestellt wird, musst du das Frontmatter `search: false` selbst behandeln. Also, das `env`-Objekt ist vor dem Aufruf von `md.renderAsync` is called, so any checks on optional `env` properties like `frontmatter` should be done after that.
 :::
 
 #### Beispiel: Transforming content - adding anchors
@@ -194,9 +194,9 @@ export default defineConfig({
 })
 ```
 
-## Algolia Suche
+## Algolia-Suche
 
-VitePress unterstützt searching your docs site using [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Refer to their getting started guide. In your `.vitepress/config.ts` you'll need to provide at least the following to make it work:
+VitePress unterstützt die Suche in deiner Dokumentation mit [Algolia DocSearch](https://docsearch.algolia.com/docs/what-is-docsearch). Siehe die entsprechende Einstiegsanleitung. In your `.vitepress/config.ts` you'll need to provide at least the following to make it work:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -217,20 +217,20 @@ export default defineConfig({
 
 ### i18n {#algolia-search-i18n}
 
-Du kannst use a config like this to use multilingual search:
+Du kannst eine Konfiguration wie diese verwenden, um eine mehrsprachige Suche einzurichten:
 
 <details>
-<summary>View full example</summary>
+<summary>Vollständiges Beispiel anzeigen</summary>
 
 <<< @/snippets/algolia-i18n.ts
 
 </details>
 
-Refer [official Algolia docs](https://docsearch.algolia.com/docs/api#translations) to learn more about them. To quickly get started, you can also copy the translations used by this site from [our GitHub repo](https://github.com/search?q=repo:vuejs/vitepress+%22function+searchOptions%22&type=code).
+Refer [official Algolia docs](https://docsearch.algolia.com/docs/api#translations) to learn more about them. Für einen schnellen Einstieg kannst du auch the translations used by this site from [our GitHub repo](https://github.com/search?q=repo:vuejs/vitepress+%22function+searchOptions%22&type=code).
 
 ### Algolia Ask AI Support {#ask-ai}
 
-Wenn du would like to include **Ask AI**, pass the `askAi` option (or any of the partial fields) inside `options`:
+Wenn du **Ask AI** einbinden möchtest, pass the `askAi` option (or any of the partial fields) inside `options`:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -260,12 +260,12 @@ export default defineConfig({
 ```
 
 ::: warning Note
-Wenn du want to default to keyword search and do not want to use Ask AI, omit the `askAi` property.
+Wenn du standardmäßig die Stichwortsuche verwenden und Ask AI nicht nutzen möchtest, lasse the `askAi` property.
 :::
 
 ### Ask AI Side Panel {#ask-ai-side-panel}
 
-DocSearch v4.5+ unterstützt an optional **Ask AI side panel**. When aktiviert, it can be opened with **Ctrl/Cmd+I** by default. The [Sidepanel API Reference](https://docsearch.algolia.com/docs/sidepanel/api-reference) contains the full list of options.
+DocSearch v4.5+ unterstützt an optional **Ask-AI-Seitenleiste**. Wenn sie aktiviert ist, kann sie with **Ctrl/Cmd+I** by default. The [Sidepanel API Reference](https://docsearch.algolia.com/docs/sidepanel/api-reference) contains the full list of options.
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -302,7 +302,7 @@ questions. Algolia's standalone Ask AI examples also mention
 VitePress side panel mode and does not make the integrated keyword-search
 modal display suggested questions on first open.
 
-Wenn du need to disable the keyboard shortcut, use the `keyboardShortcuts` option at the sidepanel root level:
+Wenn du die Tastenkombination deaktivieren möchtest, verwende the `keyboardShortcuts` option at the sidepanel root level:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -331,16 +331,16 @@ export default defineConfig({
 
 #### Mode (auto / sidePanel / hybrid / modal) {#ask-ai-mode}
 
-Du kannst optionally control how VitePress integrates keyword search and Ask AI:
+Du kannst optional festlegen, wie VitePress Stichwortsuche und Ask AI integriert:
 
-- `mode: 'auto'` (default): infer `hybrid` when keyword search is configured, otherwise `sidePanel` when Ask AI side panel is configured.
+- `mode: 'auto'` (default): infer `hybrid` when keyword search is configured, otherwise `sidePanel` when Ask-AI-Seitenleiste is configured.
 - `mode: 'sidePanel'`: force side panel only (hides the keyword search button).
-- `mode: 'hybrid'`: enable keyword search modal + Ask AI side panel (requires keyword search configuration).
+- `mode: 'hybrid'`: enable keyword search modal + Ask-AI-Seitenleiste (requires keyword search configuration).
 - `mode: 'modal'`: keep Ask AI inside the DocSearch modal (even if you configured the side panel).
 
 #### Ask AI only (no keyword search) {#ask-ai-only}
 
-Wenn du want to use **Ask AI side panel only**, you can omit top-level keyword search config and provide credentials under `askAi`:
+Wenn du want to use **Ask-AI-Seitenleiste only**, you can omit top-level keyword search config and provide credentials under `askAi`:
 
 ```ts
 import { defineConfig } from 'vitepress'

From c0552456f5866c94abc6571bcabb4f788b0cd8e7 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:48 +0200
Subject: [PATCH 114/199] docs(de): translate remaining reference prose

---
 docs/de/reference/default-theme-sidebar.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-sidebar.md b/docs/de/reference/default-theme-sidebar.md
index c974c4b20..c51399021 100644
--- a/docs/de/reference/default-theme-sidebar.md
+++ b/docs/de/reference/default-theme-sidebar.md
@@ -1,10 +1,10 @@
 ---
-description: Konfigurieren the sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
+description: Konfiguriere die sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
 ---
 
 # Seitenleiste
 
-The sidebar is the main navigation block for your documentation. Du kannst configure the sidebar menu in [`themeConfig.sidebar`](./default-theme-config#sidebar).
+Die Seitenleiste ist der zentrale Navigationsbereich deiner Dokumentation. Du kannst das Seitenleistenmenü konfigurieren in [`themeConfig.sidebar`](./default-theme-config#sidebar).
 
 ```js
 export default {
@@ -25,7 +25,7 @@ export default {
 
 ## The Basics
 
-The simplest form of the sidebar menu is passing in a single array of links. The first level item defines the "section" for the sidebar. It should contain `text`, which is the title of the section, and `items` which are the actual navigation links.
+Die einfachste Form des Seitenleistenmenüs besteht aus einem einzelnen Array von Links. Das Element der ersten Ebene definiert den „Abschnitt“ der Seitenleiste. It should contain `text`, which is the title of the section, and `items` which are the actual navigation links.
 
 ```js
 export default {

From c4c111885994fb7aaac1a0d7a1a188d06df47e69 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:54 +0200
Subject: [PATCH 116/199] docs(de): translate remaining reference prose

---
 docs/de/reference/frontmatter-config.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/reference/frontmatter-config.md b/docs/de/reference/frontmatter-config.md
index 1d16fd76c..6a3589e8a 100644
--- a/docs/de/reference/frontmatter-config.md
+++ b/docs/de/reference/frontmatter-config.md
@@ -97,14 +97,14 @@ dir: rtl
 
 ## Standard-Theme Only
 
-The following frontmatter options are only applicable when using the default theme.
+Die folgenden Frontmatter-Optionen are only applicable when using the default theme.
 
 ### layout
 
 - Type: `doc | home | page`
 - Default: `doc`
 
-Determines the layout of the page.
+Legt das Layout der Seite fest.
 
 - `doc` - It applies default documentation styles to the markdown content.
 - `home` - Special layout for "Startseite". Du kannst add extra options such as `hero` and `features` to rapidly create beautiful landing page.
@@ -129,7 +129,7 @@ Defines items to display in features section when `layout` is set to `home`. Mor
 - Type: `boolean`
 - Default: `true`
 
-Whether to display [navbar](./default-theme-nav).
+Ob [navbar](./default-theme-nav).
 
 ```yaml
 ---
@@ -142,7 +142,7 @@ navbar: false
 - Type: `boolean`
 - Default: `true`
 
-Whether to display [sidebar](./default-theme-sidebar).
+Ob [sidebar](./default-theme-sidebar).
 
 ```yaml
 ---
@@ -172,7 +172,7 @@ aside: false
 - Type: `number | [number, number] | 'deep' | false`
 - Default: `2`
 
-The levels of header in the outline to display for the page. It's same as [config.themeConfig.outline.level](./default-theme-config#outline), and it overrides the value set in site-level config.
+Die Überschriftenebenen, die in der Seitenübersicht für die Seite angezeigt werden. It's same as [config.themeConfig.outline.level](./default-theme-config#outline), and it overrides the value set in site-level config.
 
 ```yaml
 ---
@@ -185,7 +185,7 @@ outline: [2, 4]
 - Type: `boolean | Date`
 - Default: `true`
 
-Whether to display [last updated](./default-theme-last-updated) text in the footer of the current page. If a datetime is specified, it will be displayed instead of the last git modified timestamp.
+Ob [last updated](./default-theme-last-updated) text in the footer of the current page. If a datetime is specified, it will be displayed instead of the last git modified timestamp.
 
 ```yaml
 ---
@@ -198,7 +198,7 @@ lastUpdated: false
 - Type: `boolean`
 - Default: `true`
 
-Whether to display [edit link](./default-theme-edit-link) in the footer of the current page.
+Ob [edit link](./default-theme-edit-link) in the footer of the current page.
 
 ```yaml
 ---
@@ -211,7 +211,7 @@ editLink: false
 - Type: `boolean`
 - Default: `true`
 
-Whether to display [footer](./default-theme-footer).
+Ob [footer](./default-theme-footer).
 
 ```yaml
 ---
@@ -223,7 +223,7 @@ footer: false
 
 - Type: `string`
 
-Add extra class name to a specific page.
+Füge einer bestimmten Seite einen zusätzlichen Klassennamen hinzu.
 
 ```yaml
 ---
@@ -231,7 +231,7 @@ pageClass: custom-page-class
 ---
 ```
 
-Then you can customize styles of this specific page in `.vitepress/theme/custom.css` file:
+Anschließend kannst du die Stile of this specific page in `.vitepress/theme/custom.css` file:
 
 ```css
 .custom-page-class {

From c786ffcf44fb42ecf1421ec61d7dfa1c4974ebcd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:56 +0200
Subject: [PATCH 117/199] docs(de): translate remaining reference prose

---
 docs/de/reference/runtime-api.md | 40 ++++++++++++++++----------------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/docs/de/reference/runtime-api.md b/docs/de/reference/runtime-api.md
index 22321dcc4..e10646e8a 100644
--- a/docs/de/reference/runtime-api.md
+++ b/docs/de/reference/runtime-api.md
@@ -1,18 +1,18 @@
 ---
-description: Reference of VitePress runtime APIs including composables, helper functions, and built-in components.
+description: Referenz der VitePress-Runtime-APIs einschließlich Composables, Hilfsfunktionen und integrierter Komponenten.
 ---
 
 # Runtime API
 
-VitePress offers several built-in APIs to let you access app data. VitePress also comes with a few built-in components that can be used globally.
+VitePress bietet mehrere integrierte APIs für den Zugriff auf Anwendungsdaten. VitePress also comes with a few built-in components that can be used globally.
 
-The helper methods are globally importable from `vitepress` and are typically used in custom theme Vue components. However, they are also usable inside `.md` pages because markdown files are compiled into Vue [Single-Datei Komponenten](https://vuejs.org/guide/scaling-up/sfc.html).
+Die Hilfsmethoden können global importiert werden from `vitepress` and are typically used in custom theme Vue components. Sie können jedoch auch innerhalb von `.md`-Seiten verwendet werden because markdown files are compiled into Vue [Single-Datei Komponenten](https://vuejs.org/guide/scaling-up/sfc.html).
 
-Methods that start with `use*` indicates that it is a [Vue 3 Composition API](https://vuejs.org/guide/introduction.html#composition-api) function ("Composable") that can only be used inside `setup()` or `<script setup>`.
+Methoden, die mit `use*` beginnen, sind that it is a [Vue 3 Composition API](https://vuejs.org/guide/introduction.html#composition-api) function ("Composable") that can only be used inside `setup()` or `<script setup>`.
 
 ## `useData` <Badge type="info" text="composable" />
 
-Gibt zurück page-specific data. The returned object has the following type:
+Gibt seitenspezifische Daten zurück. The returned object has the following type:
 
 ```ts
 interface VitePressData<T = any> {
@@ -62,7 +62,7 @@ interface PageData {
 }
 ```
 
-`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) is aktiviert. Without that option, it remains an empty array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
+`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) ist aktiviert. Ohne diese Option bleibt es ein leeres Array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
 
 **Beispiel:**
 
@@ -80,7 +80,7 @@ const { theme } = useData()
 
 ## `useRoute` <Badge type="info" text="composable" />
 
-Gibt zurück the current route object with the following type:
+Gibt das aktuelle Routenobjekt zurück with the following type:
 
 ```ts
 interface Route {
@@ -92,7 +92,7 @@ interface Route {
 
 ## `useRouter` <Badge type="info" text="composable" />
 
-Gibt zurück the VitePress router instance so you can programmatically navigate to another page.
+Gibt die VitePress-Routerinstanz zurück, mit der du programmgesteuert zu einer anderen Seite navigieren kannst.
 
 ```ts
 interface Router {
@@ -134,15 +134,15 @@ router.onBeforeRouteChange = (to) => {
 }
 ```
 
-For custom themes, the same router is verfügbar from [`enhanceApp`](../guide/custom-theme#theme-interface).
+Bei eigenen Themes ist derselbe Router über [`enhanceApp`](../guide/custom-theme#theme-interface).
 
 ## `useIcon` <Badge type="info" text="composable" />
 
 - **Type**: `(icon: MaybeRefOrGetter<string | { svg: string } | undefined>, el?: MaybeRefOrGetter<HTMLElement | null>) => ComputedRef<string | undefined>`
 
-Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Takes a fully qualified `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) and gibt zurück the class to put on the element — `vpi-<collection>-<name>`.
+Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Erwartet eine vollständig qualifizierte `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) und gibt die Klasse zurück, die auf dem Element gesetzt werden soll — `vpi-<collection>-<name>`.
 
-During SSR the name is registered on the page's [`SSGContext`](./site-config#postrender), so the build emits the icon's styles into the generated stylesheet; in dev, icons are served on demand by the dev server from the locally installed collections. No icon is ever fetched from an external service.
+Während SSR wird der Name im [`SSGContext`](./site-config#postrender), so the build emits the icon's styles into the generated stylesheet; in dev, icons are served on demand by the dev server from the locally installed collections. No icon is ever fetched from an external service.
 
 ```vue
 <script setup>
@@ -158,25 +158,25 @@ const iconClass = useIcon('lucide:rocket', el)
 </template>
 ```
 
-Pass the template ref of the element carrying the class so dev mode can resolve the icon on it. The element needs the mask rules the default theme ships; in a custom theme without them, dev applies an inline equivalent and the generated stylesheet includes zero-specificity base rules for production.
+Übergebe die Template-Referenz of the element carrying the class so dev mode can resolve the icon on it. Das Element benötigt the mask rules the default theme ships; in a custom theme without them, dev applies an inline equivalent and the generated stylesheet includes zero-specificity base rules for production.
 
-When using the default theme, the `VPIcon` component from `vitepress/theme` wraps this composable (and also accepts a raw `{ svg }` string):
+Bei Verwendung des Standard-Themes, the `VPIcon` component from `vitepress/theme` wraps this composable (and also accepts a raw `{ svg }` string):
 
 ```vue-html
 <VPIcon icon="lucide:rocket" />
 ```
 
-Icons rendered only on the client (e.g. inside `<ClientOnly />`) can't be collected during the build — list them in [`icons.include`](./site-config#icons) instead.
+Symbole, die nur auf dem Client gerendert werden (e.g. inside `<ClientOnly />`) can't be collected during the build — list them in [`icons.include`](./site-config#icons) instead.
 
 ## `withBase` <Badge type="info" text="helper" />
 
 - **Type**: `(path: string) => string`
 
-Prepends the configured [`base`](./site-config#base) to a given URL path. Also see [Base URL](../guide/asset-handling#base-url).
+Stellt das konfigurierte [`base`](./site-config#base) einem angegebenen URL-Pfad voran. Also see [Base URL](../guide/asset-handling#base-url).
 
 ## `<Inhalt />` <Badge type="info" text="component" />
 
-The `<Inhalt />` component displays the rendered markdown contents. Useful [when creating your own theme](../guide/custom-theme).
+The `<Inhalt />` component displays the rendered markdown contents. Nützlich [beim Erstellen eines eigenen Themes](../guide/custom-theme).
 
 ```vue
 <template>
@@ -187,9 +187,9 @@ The `<Inhalt />` component displays the rendered markdown contents. Useful [when
 
 ## `<ClientOnly />` <Badge type="info" text="component" />
 
-The `<ClientOnly />` component renders its slot only at client side.
+Die Komponente `<ClientOnly />` rendert ihren Slot nur auf der Clientseite.
 
-Because VitePress applications are server-rendered in Node.js when generating static builds, any Vue usage must conform to the universal code requirements. In short, make sure to only access Browser / DOM APIs in beforeMount or mounted hooks.
+Da VitePress-Anwendungen beim Erzeugen statischer Builds in Node.js serverseitig gerendert werden, any Vue usage must conform to the universal code requirements. In short, make sure to only access Browser / DOM APIs in beforeMount or mounted hooks.
 
 Wenn du are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the `ClientOnly` component.
 
@@ -203,7 +203,7 @@ Wenn du are using or demoing components that are not SSR-friendly (for example,
 
 ## `$frontmatter` <Badge type="info" text="template global" />
 
-Directly access current page's [frontmatter](../guide/frontmatter) data in Vue expressions.
+Greife direkt auf die [frontmatter](../guide/frontmatter) data in Vue expressions.
 
 ```md
 ---
@@ -215,7 +215,7 @@ title: Hello
 
 ## `$params` <Badge type="info" text="template global" />
 
-Directly access current page's [dynamic route params](../guide/routing#dynamic-routes) in Vue expressions.
+Greife direkt auf die [dynamic route params](../guide/routing#dynamic-routes) in Vue expressions.
 
 ```md
 - package name: {{ $params.pkg }}

From a9644fdf6c1b7e400f519f30e2ed83f13b596626 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:58:59 +0200
Subject: [PATCH 118/199] docs(de): translate remaining reference prose

---
 docs/de/reference/site-config.md | 62 ++++++++++++++++----------------
 1 file changed, 31 insertions(+), 31 deletions(-)

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
index b7abecf5b..85c018cf3 100644
--- a/docs/de/reference/site-config.md
+++ b/docs/de/reference/site-config.md
@@ -1,19 +1,19 @@
 ---
 outline: deep
-description: Complete reference of VitePress site configuration options including app-level settings, theming, and build options.
+description: Vollständige Referenz der VitePress-Website-Konfigurationsoptionen einschließlich Einstellungen auf Anwendungsebene, Theme-Konfiguration und Build-Optionen.
 ---
 
 # Site-Konfiguration
 
-Site config is where you can define the global settings of the site. App config options define settings that apply to every VitePress site, regardless of what theme it is using. Zum Beispiel, the base directory or the title of the site.
+In der Website-Konfiguration definierst du die globalen Einstellungen der Website. Konfigurationsoptionen auf Anwendungsebene gelten für jede VitePress-Website, unabhängig vom verwendeten Theme. Zum Beispiel, the base directory or the title of the site.
 
 ## Übersicht
 
-### Config Resolution
+### Auflösung der Konfiguration
 
-The config file is always resolved from `<root>/.vitepress/config.[ext]`, where `<root>` is your VitePress [project root](../guide/routing#root-and-source-directory), and `[ext]` is one of the supported file extensions. TypeScript is supported out of the box. Supported extensions include `.js`, `.ts`, `.mjs`, and `.mts`.
+Die Konfigurationsdatei wird immer aus `<root>/.vitepress/config.[ext]`, wobei `<root>` dein VitePress [project root](../guide/routing#root-and-source-directory), and `[ext]` is one of the supported file extensions. TypeScript is supported out of the box. Supported extensions include `.js`, `.ts`, `.mjs`, and `.mts`.
 
-It is recommended to use ES modules syntax in config files. The config file should default export an object:
+Es wird empfohlen, in Konfigurationsdateien die ES-Modul-Syntax zu verwenden. The config file should default export an object:
 
 ```ts
 export default {
@@ -27,7 +27,7 @@ export default {
 
 ::: details Dynamic (Async) Config
 
-Wenn du need to dynamically generate the config, you can also default export a function. Zum Beispiel:
+Wenn du die Konfiguration dynamisch erzeugen musst, you can also default export a function. Zum Beispiel:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -54,7 +54,7 @@ export default async () => {
 }
 ```
 
-Du kannst also use top-level `await`. Zum Beispiel:
+Du kannst auch `await` auf oberster Ebene verwenden. Zum Beispiel:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -81,9 +81,9 @@ export default defineConfig({
 
 :::
 
-### Config Intellisense
+### Konfigurations-IntelliSense
 
-Using the `defineConfig` helper will provide TypeScript-powered intellisense for config options. Assuming your IDE unterstützt it, this should work in both JavaScript and TypeScript.
+Die Verwendung des Helpers `defineConfig` stellt TypeScript-basierte IntelliSense für Konfigurationsoptionen bereit. Sofern deine IDE dies unterstützt, this should work in both JavaScript and TypeScript.
 
 ```js
 import { defineConfig } from 'vitepress'
@@ -93,9 +93,9 @@ export default defineConfig({
 })
 ```
 
-### Typed Theme Config
+### Typisierte Theme-Konfiguration
 
-Standardmäßig, `defineConfig` helper expects the theme config type from default theme:
+Standardmäßig erwartet der Helper `defineConfig` the theme config type from default theme:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -107,7 +107,7 @@ export default defineConfig({
 })
 ```
 
-Wenn du use a custom theme and want type checks for the theme config, you'll need to use `defineConfigWithTheme` instead, and pass the config type for your custom theme via a generic argument:
+Wenn du ein eigenes Theme verwendest und Typprüfungen for the theme config, musst du stattdessen `defineConfigWithTheme` verwenden, and pass the config type for your custom theme via a generic argument:
 
 ```ts
 import { defineConfigWithTheme } from 'vitepress'
@@ -124,33 +124,33 @@ export default defineConfigWithTheme<ThemeConfig>({
 
 - **Vite**
 
-  Du kannst configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. No need to create a separate Vite config file.
+  Du kannst configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. Eine separate Vite-Konfigurationsdatei ist nicht erforderlich.
 
 - **Vue**
 
-  VitePress already includes the official Vue plugin for Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). Du kannst configure its options using the [vue](#vue) option in your VitePress config.
+  VitePress enthält bereits das offizielle Vue-Plugin für Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). Du kannst dessen Optionen konfigurieren using the [vue](#vue) option in your VitePress config.
 
 - **Markdown**
 
   Du kannst configure the underlying [Markdown-It](https://github.com/markdown-it/markdown-it) instance using the [markdown](#markdown) option in your VitePress config.
 
-### Seite-Level Overrides
+### Überschreibungen auf Seitenebene
 
-Some settings can be overridden for specific pages using frontmatter.
+Einige Einstellungen können für bestimmte Seiten über das Frontmatter überschrieben werden.
 
 See [Frontmatter-Konfiguration](./frontmatter-config) for details.
 
-### Verzeichnis-Level Overrides
+### Überschreibungen auf Verzeichnisebene
 
-Some config settings can be overridden at the directory level, allowing all pages in that directory to share settings without needing to repeat them in the frontmatter of each page.
+Einige Konfigurationseinstellungen können auf Verzeichnisebene überschrieben werden, allowing all pages in that directory to share settings without needing to repeat them in the frontmatter of each page.
 
-This is achieved by adding a file called `config.ts` (or `.js`, `.mjs`, or `.mts`) in the relevant directory. This file should export a config object using `export default`, similar to the main config file.
+Dies wird erreicht, indem eine Datei namens `config.ts` (or `.js`, `.mjs`, or `.mts`) in the relevant directory. This file should export a config object using `export default`, similar to the main config file.
 
-Nested directories inherit settings from their parent directory, with configuration overrides being merged accordingly.
+Verschachtelte Verzeichnisse übernehmen Einstellungen ihres übergeordneten Verzeichnisses, with configuration overrides being merged accordingly.
 
-The `defineAdditionalConfig` helper can be used to get TypeScript-powered intellisense for the verfügbar options, though as with `defineConfig` its use is optional.
+Der Helper `defineAdditionalConfig` kann verwendet werden to get TypeScript-powered intellisense for the verfügbar options, though as with `defineConfig` its use is optional.
 
-Zum Beispiel, for a site with multiple languages we might want a different `description` for each language. We could add `es/config.ts` with the following content:
+Zum Beispiel können wir bei einer Website mit mehreren Sprachen we might want a different `description` for each language. We could add `es/config.ts` with the following content:
 
 ```ts
 import { defineAdditionalConfig } from 'vitepress'
@@ -160,11 +160,11 @@ export default defineAdditionalConfig({
 })
 ```
 
-This `description` would then be used for all pages in the `es` directory.
+Diese `description` wird anschließend für alle Seiten in the `es` directory.
 
-Alternatively, when using the built-in i18n features, the settings for a locale directory can be overridden via the `locales` setting in the main configuration file. See [Internationalization](../guide/i18n) for details.
+Alternativ können bei Verwendung der integrierten i18n-Funktionen, the settings for a locale directory can be overridden via the `locales` setting in the main configuration file. See [Internationalization](../guide/i18n) for details.
 
-## Site Metadata
+## Website-Metadaten
 
 ### title
 
@@ -172,9 +172,9 @@ Alternatively, when using the built-in i18n features, the settings for a locale
 - Default: `VitePress`
 - Can be overridden per page via [frontmatter](./frontmatter-config#title) or at the [directory level](#directory-level-overrides)
 
-Title for the site. When using the default theme, this will be displayed in the nav bar.
+Title for the site. Bei Verwendung des Standard-Themes, this will be displayed in the nav bar.
 
-It will also be used as the default suffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. Zum Beispiel with the following config and page content:
+Er wird außerdem als Standardsuffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. Zum Beispiel with the following config and page content:
 
 ```ts
 export default {
@@ -186,7 +186,7 @@ export default {
 # Hello
 ```
 
-The title of the page will be `Hello | My Awesome Site`.
+Der Titel der Seite lautet `Hello | My Awesome Site`.
 
 ### titleTemplate
 
@@ -206,7 +206,7 @@ export default {
 # Hello
 ```
 
-The title of the page will be `Hello | Eigenes Suffix`.
+Der Titel der Seite lautet `Hello | Eigenes Suffix`.
 
 To completely customize how the title should be rendered, you can use the `:title` symbol in `titleTemplate`:
 
@@ -524,7 +524,7 @@ Shared chunks stay in `assets/chunks/`. A file's shard depends only on its name,
 
 Optionen for the generated icon styles. The build collects every iconify icon rendered during SSR. Names are fully qualified as `collection:name`, resolved against the `@iconify-json/*` packages declared in your project's dependencies.
 
-Icons rendered only on the client — inside `<ClientOnly>`, or after hydration — are invisible to SSR collection. List them in `include` to force them into the stylesheet:
+Symbole, die nur auf dem Client gerendert werden — inside `<ClientOnly>`, or after hydration — are invisible to SSR collection. List them in `include` to force them into the stylesheet:
 
 ```ts
 export default {
@@ -614,7 +614,7 @@ This option injects an inline script that restores users settings from local sto
 
 Whether to get the last updated timestamp for each page using Git. The timestamp will be included in each page's page data, accessible via [`useData`](./runtime-api#usedata).
 
-When using the default theme, enabling this option will display each page's last updated time. Du kannst customize the text via [`themeConfig.lastUpdated.text`](./default-theme-config#lastupdated) option.
+Bei Verwendung des Standard-Themes, enabling this option will display each page's last updated time. Du kannst customize the text via [`themeConfig.lastUpdated.text`](./default-theme-config#lastupdated) option.
 
 ## Customization
 

From b5111b0babadb80e1b420cac412f23bff41245d6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:17 +0200
Subject: [PATCH 119/199] docs(de): translate guide prose

---
 docs/de/guide/custom-theme.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/de/guide/custom-theme.md b/docs/de/guide/custom-theme.md
index 8cfd75803..1db0cbd8a 100644
--- a/docs/de/guide/custom-theme.md
+++ b/docs/de/guide/custom-theme.md
@@ -6,7 +6,7 @@ description: Erstelle und verwende ein eigenes Theme in VitePress, um das Ersche
 
 ## Theme-Auflösung
 
-Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (die „Theme-Einstiegsdatei“):
+Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/Theme/index.js` or `.vitepress/Theme/index.ts` Datei (die „Theme-Einstiegsdatei“):
 
 ```
 .
@@ -19,7 +19,7 @@ Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` o
 └─ package.json
 ```
 
-VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend the default theme](./extending-default-theme) to perform advanced customizations on top of it.
+VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend the Standard-Theme](./extending-default-Theme) to perform advanced eigeneizations on top of it.
 
 ## Theme-Schnittstelle
 
@@ -73,7 +73,7 @@ export default {
 }
 ```
 
-Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
+Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global Komponentes](./extending-default-Theme.md#registering-global-Komponentes), integrate mit Vue libraries, etc.
 
 Der Wert `router` ist dieselbe VitePress-Router-Instanz, die von [`useRouter()`](../reference/runtime-api#userouter). Um auf Routenänderungen zu reagieren, weist du dem Router Handler zu:
 
@@ -115,11 +115,11 @@ Mit `extends` wird das `setup` jedes Themes wie bei `enhanceApp` von der Basis a
 
 Der Standardexport ist der einzige Vertrag für ein eigenes Theme, und nur die Eigenschaft `Layout` ist erforderlich. Technisch kann ein VitePress-Theme daher aus nur einer einzigen Vue-Komponente bestehen.
 
-Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Beachte, dass das Theme außerdem [SSR-compatible](./ssr-compat).
+Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Bjedete, dass das Theme außerdem [SSR-compatible](./ssr-compat).
 
 ## Ein Layout erstellen
 
-Die einfachste Layout-Komponente muss eine [`<Content />`](../reference/runtime-api#content) -Komponente enthalten:
+Die einfachste Layout-Komponente muss eine [`<Content />`](../reference/runtime-api#Inhalt) -Komponente enthalten:
 
 ```vue [.vitepress/theme/Layout.vue]
 <template>
@@ -148,7 +148,7 @@ const { page } = useData()
 </template>
 ```
 
-The [`useData()`](../reference/runtime-api#usedata) helper provides us with all the runtime data we need to conditionally render different layouts. One of the other data we can access is the current page's frontmatter. We can leverage this to allow the end user to control the layout in each page. For example, the user can indicate the page should use a special home page layout with:
+The [`useData()`](../reference/runtime-api#useDaten) helper provides us mit alle the runtime Daten we need to conditionally render different layouts. One of the andere Daten we can access is the current Seite's frontmatter. We can leverage this to allow the end user to control the layout in jede Seite. Zum Beispiel, the user can indicate the Seite should use a special home Seite layout mit:
 
 ```md
 ---
@@ -156,7 +156,7 @@ layout: home
 ---
 ```
 
-And we can adjust our theme to handle this:
+And we can adjust our Theme to handle this:
 
 ```vue{3,12-14}
 <script setup>
@@ -198,7 +198,7 @@ const { page, frontmatter } = useData()
 </template>
 ```
 
-In der [Runtime API Reference](../reference/runtime-api) findest du alles, was in Theme-Komponenten verfügbar ist. Zusätzlich kannst du [Build-Time Data Loading](./data-loading) nutzen, um datenbasierte Layouts zu erzeugen – beispielsweise eine Seite, die alle Blogbeiträge des aktuellen Projekts auflistet.
+In der [Runtime API Referenz](../reference/runtime-api) findest du alles, was in Theme-Komponenten verfügbar ist. Zusätzlich kannst du [Build-Time Data Loading](./Daten-loading) nutzen, um datenbasierte Layouts zu erzeugen – beispielsweise eine Seite, die alle Blogbeiträge des aktuellen Projekts auflistet.
 
 ## Ein eigenes Theme verteilen
 
@@ -210,7 +210,7 @@ Wenn du das Theme als npm-Paket verteilen möchtest, gehe folgendermaßen vor:
 
 2. Falls zutreffend, exportiere die Typdefinition deiner Theme-Konfiguration als `ThemeConfig`.
 
-3. Wenn dein Theme Anpassungen an der VitePress-Konfiguration erfordert, exportiere diese Konfiguration unter einem Paket-Unterpfad (e.g. `my-theme/config`) damit Benutzer sie erweitern können.
+3. Wenn dein Theme Anpassungen an der VitePress-Konfiguration erfordert, exportiere diese Konfiguration unter einem Paket-Unterpfad (e.g. `my-Theme/config`) damit Benutzer sie erweitern können.
 
 4. Dokumentiere die Optionen der Theme-Konfiguration sowohl über die Konfigurationsdatei als auch über Frontmatter.
 

From a4b59e0cc7868c26eb8361ee0b88bf0011a775c6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:19 +0200
Subject: [PATCH 120/199] docs(de): translate guide prose

---
 docs/de/guide/data-loading.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index 32aa63fb6..f21e4c56b 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -10,7 +10,7 @@ Data Loader können verwendet werden, um entfernte Daten abzurufen oder Metadate
 
 ## Grundlegende Verwendung
 
-Eine Data-Loader-Datei muss mit `.data.js` or `.data.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
+Eine Data-Loader-Datei muss mit `.Daten.js` or `.Daten.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
 
 ```js [example.data.js]
 export default {
@@ -24,7 +24,7 @@ export default {
 
 Das Loader-Modul wird nur in Node.js ausgewertet. Du kannst daher nach Bedarf Node-APIs und npm-Abhängigkeiten importieren.
 
-Du kannst anschließend Daten aus dieser Datei in `.md`-Seiten und `.vue`-Komponenten mit dem `data` named export:
+Du kannst anschließend Daten aus dieser Datei in `.md`-Seiten und `.vue`-Komponenten mit dem `Daten` named export:
 
 ```vue
 <script setup>
@@ -42,7 +42,7 @@ Ausgabe:
 }
 ```
 
-Du wirst feststellen, dass der Data Loader selbst `data` nicht exportiert. Stattdessen ruft VitePress im Hintergrund die Methode `load()` auf und stellt das Ergebnis implizit über den benannten Export `data` bereit.
+Du wirst feststellen, dass der Data Loader selbst `Daten` nicht exportiert. Stattdessen ruft VitePress im Hintergrund die Methode `load()` auf und stellt das Ergebnis implizit über den benannten Export `Daten` bereit.
 
 Das funktioniert auch, wenn der Loader asynchron ist:
 
@@ -85,7 +85,7 @@ export default {
 
 ## `createContentLoader`
 
-Beim Erstellen einer inhaltsorientierten Website müssen wir häufig eine „Archiv“- oder „Index“-Seite erstellen: eine Seite, auf der wir alle verfügbaren Einträge unserer Inhaltssammlung auflisten, beispielsweise Blogbeiträge oder API-Seiten. Wir **können** dies direkt mit der Data-Loader-API umsetzen. Da dies jedoch ein sehr häufiger Anwendungsfall ist, stellt VitePress den Helper `createContentLoader` bereit, der dies vereinfacht:
+Beim Erstellen einer inhaltsorientierten Website müssen wir häufig eine „Archiv“- oder „Index“-Seite erstellen: eine Seite, auf der wir alle verfügbaren Einträge unserer Inhaltssammlung auflisten, beispielsweise Blogbeiträge oder API-Seiten. Wir **können** dies direkt mit der Data-Loader-API umsetzen. Da dies jedoch ein sehr häufiger Anwendungsfalle ist, stellt VitePress den Helper `createContentLoader` bereit, der dies vereinfacht:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
@@ -159,7 +159,7 @@ export default createContentLoader('posts/*.md', {
 })
 ```
 
-Sieh dir an, wie dies im [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
+Sieh dir an, wie dies im [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/Theme/posts.Daten.ts).
 
 Die `createContentLoader`-API kann auch innerhalb von [build hooks](../reference/site-config#build-hooks):
 
@@ -216,7 +216,7 @@ interface ContentOptions<T = ContentData[]> {
 
 ## Typisierte Data Loader
 
-Bei Verwendung von TypeScript kannst du deinen Loader und den `data`-Export wie folgt typisieren:
+Bei Verwendung von TypeScript kannst du deinen Loader und den `Daten`-Export wie folgt typisieren:
 
 ```ts
 import { defineLoader } from 'vitepress'

From b2e56fc85a3537ebdfe13a72321eb5649898db65 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:22 +0200
Subject: [PATCH 121/199] docs(de): translate guide prose

---
 docs/de/guide/deploy.md | 86 ++++++++++++++++++++---------------------
 1 file changed, 43 insertions(+), 43 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index 5f7d1b7cf..b2c6b8476 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -50,9 +50,9 @@ Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
 ## Einen öffentlichen Basispfad festlegen
 
-Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
+Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) Option to `'/blog/'` in the VitePress config.
 
-**Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, then set your `base` to `/repo/`.
+**Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, dann set your `base` to `/repo/`.
 
 ## Verschiebbare Builds (relativer Basispfad) {#relocatable-builds-relative-base}
 
@@ -66,23 +66,23 @@ export default {
 
 Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Derselbe Build funktioniert von **jedem** Unterpfad aus ohne erneuten Build – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
 
-Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) also works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
+Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`Datei://`) außerdem works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `Datei://`, so there is no hydration there — interactive features like search stay inactive, while alle pre-rendered Inhalt and links keep working.
 
-Einige Dinge solltest du beachten:
+Einige Dinge solltest du bjedeten:
 
 - Lasse [`cleanUrls`](../reference/site-config#cleanurls) deaktiviert (Standardeinstellung): Für portable Ausgaben müssen Links mit `.html` enden, da kein Server vorhanden ist, der saubere URLs umschreibt.
 - `404.html` wird für die Stammebene erzeugt. Hosts, die sie als Fallback für beliebig tiefe URLs ausliefern, rendern sie ohne Styles (there is no correct relative prefix for an unknown depth).
 - [`head`](../reference/site-config#head) Einträge werden wie immer unverändert ausgegeben – vermeide dort absolute Pfade wie `/favicon.ico` there and prefer absolute URLs or `transformHead`.
 - Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
-- Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
-- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
+- Von [`createContentLoader`](./Daten-loading#createInhaltloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in andere Seites, so no single relative prefix is correct) — they resolve nur for a root mount.
+- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on Seite URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually alle static hosts canonicalize this way bereits.
 - Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktions-Build.
 
 ## HTTP-Cache-Header
 
 Wenn du Kontrolle über die HTTP-Header deines Produktionsservers hast, kannst du `cache-control`-Header konfigurieren, um bei wiederholten Besuchen eine bessere Leistung zu erzielen.
 
-Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and other imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see files like `app.4f283b18.js`.
+Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and andere imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see Dateis like `app.4f283b18.js`.
 
 Dieser Hash `4f283b18` wird aus dem Inhalt dieser Datei erzeugt. Dieselbe gehashte URL liefert garantiert denselben Dateiinhalt – wenn sich der Inhalt ändert, ändern sich auch die URLs. Das bedeutet, dass du für diese Dateien bedenkenlos die stärksten Cache-Header verwenden kannst. Alle solchen Dateien werden im Ausgabeverzeichnis unter `assets/` abgelegt. Dafür kannst du den folgenden Header konfigurieren:
 
@@ -138,7 +138,7 @@ Richte ein neues Projekt ein und ändere diese Einstellungen über dein Dashboar
 - **Ausgabeverzeichnis:** `docs/.vitepress/dist`
 - **Node-Version:** `20` (or above)
 
-::: warning
+::: Warnung
 Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommentare aus der Ausgabe entfernt, die für Vue Bedeutung haben. Wenn sie entfernt werden, können Hydration-Mismatch-Fehler auftreten.
 :::
 
@@ -162,14 +162,14 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 
    # Legt die Berechtigungen des GITHUB_TOKEN für die Bereitstellung auf GitHub Pages fest
    permissions:
-     contents: read
-     pages: write
+     Inhalts: read
+     Seites: write
      id-token: write
 
    # Erlaubt nur eine gleichzeitige Bereitstellung und überspringt zwischenzeitlich eingereihtes Ausführungen.
    # Laufende Ausführungen dürfen jedoch NICHT abgebrochen werden, damit diese Produktionsbereitstellungen abgeschlossen werden können.
    concurrency:
-     group: pages
+     group: Seites
      cancel-in-progress: false
 
    jobs:
@@ -179,56 +179,56 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
        steps:
          - name: Checkout
            uses: actions/checkout@v5
-           with:
-             fetch-depth: 0 # Not needed if lastUpdated is not enabled
-         # - uses: pnpm/action-setup@v4 # Uncomment this block if you're using pnpm
-         #   with:
-         #     version: 9 # Not needed if you've set "packageManager" in package.json
-         # - uses: oven-sh/setup-bun@v1 # Uncomment this if you're using Bun
+           mit:
+             fetch-depth: 0 # Not needed wenn lastUpdated is not enabled
+         # - uses: pnpm/action-setup@v4 # Uncomment this block wenn you're mithilfe von pnpm
+         #   mit:
+         #     version: 9 # Not needed wenn you've set "packageManager" in package.json
+         # - uses: oven-sh/setup-bun@v1 # Uncomment this wenn you're mithilfe von Bun
          - name: Setup Node
            uses: actions/setup-node@v6
-           with:
+           mit:
              node-version: 24
              cache: npm # or pnpm / yarn
          - name: Cache VitePress
            uses: actions/cache@v4
-           with:
-             path: docs/.vitepress/cache
+           mit:
+             Pfad: docs/.vitepress/cache
              key: ${{ runner.os }}-vitepress-${{ hashFiles('docs/**', 'package-lock.json', 'pnpm-lock.yaml', 'yarn.lock', 'bun.lockb') }}
              restore-keys: |
                ${{ runner.os }}-vitepress-
          - name: Setup Pages
-           uses: actions/configure-pages@v4
-         - name: Install dependencies
-           run: npm ci # or pnpm install / yarn install / bun install
-         - name: Build with VitePress
+           uses: actions/configure-Seites@v4
+         - name: Installe dependencies
+           run: npm ci # or pnpm installe / yarn installe / bun install
+         - name: Build mit VitePress
            run: npm run docs:build # or pnpm docs:build / yarn docs:build / bun run docs:build
          - name: Upload artifact
-           uses: actions/upload-pages-artifact@v3
-           with:
-             path: docs/.vitepress/dist
+           uses: actions/upload-Seites-artifact@v3
+           mit:
+             Pfad: docs/.vitepress/dist
 
      # Bereitstellungsaufgabe
      deploy:
        environment:
-         name: github-pages
-         url: ${{ steps.deployment.outputs.page_url }}
+         name: github-Seites
+         url: ${{ steps.deployment.Ausgabes.Seite_url }}
        needs: build
        runs-on: ubuntu-latest
        name: Bereitstellen
        steps:
          - name: Bereitstellen to GitHub Pages
            id: deployment
-           uses: actions/deploy-pages@v4
+           uses: actions/deploy-Seites@v4
    ```
 
-   ::: warning
-   Stelle sicher, dass die Option `base` in deiner VitePress-Konfiguration korrekt konfiguriert ist. Weitere Informationen findest du unter [Einen öffentlichen Basispfad festlegen](#setting-a-public-base-path).
+   ::: Warnung
+   Stelle sicher, dass die Option `base` in deiner VitePress-Konfiguration korrekt konfiguriert ist. Weitere Informationen findest du unter [Einen öffentlichen Basispfad festlegen](#Einstellung-a-public-base-Pfad).
    :::
 
 2. Wähle in den Repository-Einstellungen unter „Pages“ bei „Build and deployment > Source“ die Option „GitHub Actions“ aus.
 
-3. Übertrage deine Änderungen auf den `main`-Branch und warte, bis der GitHub-Actions-Workflow abgeschlossen ist. Deine Website sollte anschließend unter `https://<username>.github.io/[repository]/` oder `https://<custom-domain>/` bereitstehen, abhängig von deinen Einstellungen. Deine Website wird bei jedem Push auf den `main`-Branch automatisch bereitgestellt.
+3. Übertrage deine Änderungen auf den `main`-Branch und warte, bis der GitHub-Actions-Workflow abgeschlossen ist. Deine Website sollte anschließend unter `https://<username>.github.io/[repository]/` oder `https://<eigene-domain>/` bereitstehen, abhängig von deinen Einstellungen. Deine Website wird bei jedem Push auf den `main`-Branch automatisch bereitgestellt.
 
 ### GitLab Pages
 
@@ -238,18 +238,18 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 
    ```yaml [.gitlab-ci.yml]
    image: node:24
-   pages:
+   Seites:
      cache:
-       paths:
+       Pfads:
          - node_modules/
      script:
-       # - apk add git # Uncomment this if you're using small docker images like alpine and have lastUpdated enabled
+       # - apk add git # Uncomment this wenn you're mithilfe von smalle docker images like alpine and have lastUpdated enabled
        - npm install
        - npm run docs:build
      artifacts:
-       paths:
+       Pfads:
          - public
-     only:
+     nur:
        - main
    ```
 
@@ -262,12 +262,12 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 2. Setze diese Werte in deiner Konfigurationsdatei (und entferne nicht benötigte Werte wie `api_location`):
 
    - **`app_location`**: `/`
-   - **`output_location`**: `docs/.vitepress/dist`
+   - **`Ausgabe_location`**: `docs/.vitepress/dist`
    - **`app_build_command`**: `npm run docs:build`
 
 ### CloudRay
 
-Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by following these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
+Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by folgende these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
 
 ### Firebase
 
@@ -314,13 +314,13 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
 
 ### Hostinger
 
-Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). Wähle bei der Build-Konfiguration VitePress als Framework und setze das Stammverzeichnis auf `./docs`.
+Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by folgende these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). Wähle bei der Build-Konfiguration VitePress als Framework und setze das Stammverzeichnis auf `./docs`.
 
 ### Lizard
 
 [Lizard (lizard.build)](https://lizard.build) builds VitePress sites von source and serves the generated HTML. For the layout verwendet in this guide, it detects `docs:build` and serves `docs/.vitepress/dist` on port `80`.
 
-Install the [Lizard CLI](https://lizard.build/docs/cli) and sign in mit `lizard login`. To deploy a local source directory, run these commands von the project root containing `package.json`:
+Installe the [Lizard CLI](https://lizard.build/docs/cli) and sign in mit `lizard login`. To deploy a local source directory, run these commands von the project root containing `package.json`:
 
 ```sh
 lizard init --name vitepress-docs
@@ -332,7 +332,7 @@ Lasse Überschreibungen für Build- und Startbefehle leer, damit die automatisch
 
 ### Stormkit
 
-Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
+Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) by folgende these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
 
 ### Surge
 

From 5ec11dfc72a12d227d956cd4e3a4dc5cbdbbbb7e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:26 +0200
Subject: [PATCH 122/199] docs(de): translate guide prose

---
 docs/de/guide/extending-default-theme.md | 76 ++++++++++++------------
 1 file changed, 38 insertions(+), 38 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index 01bdf63e8..38ef6f0d8 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -1,27 +1,27 @@
 ---
 outline: deep
-description: Anpassen and extend the VitePress default theme mit custom CSS, components, layouts, and slots.
+description: Anpassen and extend the VitePress Standard-Theme mit eigene CSS, Komponentes, layouts, and slots.
 ---
 
 # Standard-Theme erweitern
 
-VitePress' default theme is optimized for documentation, and can be customized. Consult the [Standard-Theme Config Übersicht](../reference/default-theme-config) for a comprehensive list of options.
+VitePress' Standard-Theme is optimized for documentation, and can be eigeneized. Consult the [Standard-Theme Config Übersicht](../reference/default-Theme-config) for a comprehensive list of Options.
 
-However, there are a number of cases where Konfiguration alone won't be enough. Zum Beispiel:
+However, there are a number of cases wo Konfiguration alone won't be enough. Zum Beispiel:
 
 1. You need to tweak the CSS styling;
-2. You need to modify the Vue app instance, for example to register global components;
-3. You need to inject custom content in the theme via layout slots.
+2. You need to modify the Vue app instance, zum Beispiel to register global Komponentes;
+3. You need to inject eigene Inhalt in the Theme über layout slots.
 
-These advanced customizations will require Verwendung a custom theme that "extends" the default theme.
+These advanced eigeneizations will require Verwendung a eigene Theme dass "extends" the Standard-Theme.
 
-::: tip
-Before proceeding, make sure to first read [Using a Eigenes Theme](./custom-theme) to understand how custom themes work.
+::: Tipp
+Before proceeding, make sure to first read [Using a Eigenes Theme](./eigene-Theme) to understand how eigene Themes work.
 :::
 
 ## Anpassen CSS
 
-The default theme CSS is customizable by overriding root level CSS variables:
+The Standard-Theme CSS is eigeneizable by overriding root level CSS variables:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -38,11 +38,11 @@ export default DefaultTheme
 }
 ```
 
-See [default theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css) that can be overridden.
+Siehe [Standard-Theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/Theme-default/styles/vars.css) dass can be overridden.
 
 ### Navbar
 
-The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching component internals:
+The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching Komponente internals:
 
 ```css
 :root {
@@ -72,19 +72,19 @@ Zum Beispiel, a frosted-glass navbar:
 }
 ```
 
-The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color by default, and where the two bars meet they share a single blurred surface, so the glass stays continuous across them.
+The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color standardmäßig, and wo the two bars meet they share a single blurred surface, so the glass stays continuous across them.
 
-::: warning
-`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. When Verwendung a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
+::: Warnung
+`backdrop-filter` has a measurable scroll performance cost, insbesondere on large or high-DPI screens. Wenn Verwendung a translucent bar, außerdem check text contrast over your Seite Inhalt. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
 :::
 
-When the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar instead of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
+Wenn the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar stattdessen of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-Theme-config#extramenulabel).
 
 ## Using Different Fonts
 
-VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build output. The font is also auto preloaded in production. However, this may not be desirable if you want to use a different main font.
+VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build Ausgabe. The font is außerdem auto preloaded in production. However, this may not be desirable wenn you want to use a different main font.
 
-To avoid including Inter in the build output, import the theme von `vitepress/theme-ohne-fonts` instead:
+To avoid including Inter in the build Ausgabe, import the Theme von `vitepress/Theme-ohne-fonts` stattdessen:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme-without-fonts'
@@ -101,11 +101,11 @@ export default DefaultTheme
 }
 ```
 
-::: warning
-Wenn du are Verwendung optional components like the [Team Seite](../reference/default-theme-team-page) components, make sure to also import them von `vitepress/theme-ohne-fonts`!
+::: Warnung
+Wenn du are Verwendung Optional Komponentes like the [Team Seite](../reference/default-Theme-team-Seite) Komponentes, make sure to außerdem import them von `vitepress/Theme-ohne-fonts`!
 :::
 
-If your font is a local file referenced via `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` mit hashed filename. To preload this file, use the [transformHead](../reference/site-config#transformhead) build hook:
+Wenn your font is a local Datei referenced über `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` mit hashed Dateiname. To preload this Datei, use the [transformHead](../reference/site-config#transformhead) build hook:
 
 ```js [.vitepress/config.js]
 export default {
@@ -159,11 +159,11 @@ export default {
 } satisfies Theme
 ```
 
-Since we are Verwendung Vite, you can also leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of components.
+Since we are Verwendung Vite, du kannst außerdem leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of Komponentes.
 
 ## Layout Slots
 
-The default theme's `<Layout/>` component has a few slots that can be verwendet to inject content at certain locations of the page. Here's an example of injecting a component in the bevor outline:
+The Standard-Theme's `<Layout/>` Komponente has a few slots dass can be verwendet to inject Inhalt at certain locations of the Seite. Here's an Beispiel of injecting a Komponente in the bevor outline:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -210,9 +210,9 @@ export default {
 }
 ```
 
-Full list of slots verfügbar in the default theme layout:
+Full list of slots verfügbar in the Standard-Theme layout:
 
-- When `layout: 'doc'` (default) is enabled via frontmatter:
+- Wenn `layout: 'doc'` (default) is enabled über frontmatter:
   - `doc-top`
   - `doc-bottom`
   - `doc-footer-bevor`
@@ -226,7 +226,7 @@ Full list of slots verfügbar in the default theme layout:
   - `aside-outline-nach`
   - `aside-ads-bevor`
   - `aside-ads-nach`
-- When `layout: 'home'` is enabled via frontmatter:
+- Wenn `layout: 'home'` is enabled über frontmatter:
   - `home-hero-bevor`
   - `home-hero-info-bevor`
   - `home-hero-info`
@@ -237,30 +237,30 @@ Full list of slots verfügbar in the default theme layout:
   - `home-hero-nach`
   - `home-features-bevor`
   - `home-features-nach`
-- When `layout: 'page'` is enabled via frontmatter:
-  - `page-top`
-  - `page-bottom`
-- On not found (404) page:
+- Wenn `layout: 'Seite'` is enabled über frontmatter:
+  - `Seite-top`
+  - `Seite-bottom`
+- On not found (404) Seite:
   - `not-found`
 - Always:
   - `layout-top`
   - `layout-bottom`
   - `nav-bar-title-bevor`
   - `nav-bar-title-nach`
-  - `nav-bar-content-bevor`
-  - `nav-bar-content-nach`
-  - `nav-screen-content-bevor`
-  - `nav-screen-content-nach`
+  - `nav-bar-Inhalt-bevor`
+  - `nav-bar-Inhalt-nach`
+  - `nav-screen-Inhalt-bevor`
+  - `nav-screen-Inhalt-nach`
 
 ## Using View Transitions API
 
 ### On Appearance Toggle
 
-Du kannst extend the default theme to provide a custom transition when the color mode is toggled. An example:
+Du kannst extend the Standard-Theme to provide a eigene transition wenn the color mode is toggled. An Beispiel:
 
-<<< @/components/AppearanceToggleTransition.vue [.vitepress/theme/Layout.vue]
+<<< @/Komponentes/AppearanceToggleTransition.vue [.vitepress/Theme/Layout.vue]
 
-Result (**warning!**: flashing colors, sudden movements, bright lights):
+Result (**Warnung!**: flashing colors, sudden movements, bright lights):
 
 <details>
 <summary>Demo</summary>
@@ -277,7 +277,7 @@ Coming soon.
 
 ## Overriding Internal Components
 
-Du kannst use Vite's [aliases](https://vite.dev/config/shared-options.html#resolve-alias) to replace default theme components mit your custom ones:
+Du kannst use Vite's [aliases](https://vite.dev/config/shared-Options.html#resolve-alias) to replace Standard-Theme Komponentes mit your eigene ones:
 
 ```ts
 import { fileURLToPath, URL } from 'node:url'
@@ -299,4 +299,4 @@ export default defineConfig({
 })
 ```
 
-To know the exact name of the component refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/theme-default/components). Since the components are internal, there is a slight chance their name is updated zwischen minor releases.
+To know the exact name of the Komponente refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/Theme-default/Komponentes). Since the Komponentes are internal, there is a slight chance their name is updated zwischen minor releases.

From 986a4b3b8f963502067d2d1d75b77dda6abd9092 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:29 +0200
Subject: [PATCH 123/199] docs(de): translate guide prose

---
 docs/de/guide/frontmatter.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
index 2639652f8..e06092460 100644
--- a/docs/de/guide/frontmatter.md
+++ b/docs/de/guide/frontmatter.md
@@ -36,9 +36,9 @@ editLink: true
 Inhalt der Anleitung
 ```
 
-Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [content loader](./data-loading#createcontentloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
+Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [Inhalt loader](./Daten-loading#createInhaltloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
 
-Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#usedata) -Helper zugreifen.
+Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#useDaten) -Helper zugreifen.
 
 ## Alternative Frontmatter-Formate
 

From 950614f9b322ec8dbe4898aad0eaa548bb0e3f3b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:32 +0200
Subject: [PATCH 124/199] docs(de): translate guide prose

---
 docs/de/guide/getting-started.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index be8c74626..6589972d3 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -43,9 +43,9 @@ $ deno add -D vitepress@next
 
 :::
 
-::: tip Hinweis
+::: Tipp Hinweis
 
-VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change the file extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` instead.
+VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change the Datei extension of your relevant Dateis like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-nur) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` stattdessen.
 
 :::
 
@@ -77,7 +77,7 @@ Der Assistent stellt dir einige einfache Fragen:
 
 <<< @/snippets/init.ansi
 
-::: tip Vue als Peer-Abhängigkeit
+::: Tipp Vue als Peer-Abhängigkeit
 Wenn du Anpassungen vornehmen möchtest, die Vue-Komponenten oder APIs verwenden, solltest du `vue` zusätzlich ausdrücklich als Abhängigkeit installieren.
 :::
 
@@ -98,15 +98,15 @@ Angenommen, du hast das VitePress-Projekt in `./docs`, Die erzeugte Dateistruktu
 └─ package.json
 ```
 
-Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionale Anpassungen des Themes reserviert.
+Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und Optionale Anpassungen des Themes reserviert.
 
-::: tip
-Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can also be [konfiguriert](../reference/site-config#outdir).
+::: Tipp
+Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can außerdem be [konfiguriert](../reference/site-config#outdir).
 :::
 
 ### Die Konfigurationsdatei
 
-Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic options being the title and description of the site:
+Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic Options being the title and description of the site:
 
 ```js [.vitepress/config.js]
 export default {
@@ -120,19 +120,19 @@ export default {
 }
 ```
 
-Du kannst das Verhalten des Themes außerdem über die `themeConfig` option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on all config options.
+Du kannst das Verhalten des Themes außerdem über die `ThemeConfig` Option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on alle config Options.
 
 ### Quelldateien
 
 Markdown-Dateien außerhalb des Verzeichnisses `.vitepress` gelten als **Quelldateien**.
 
-VitePress verwendet **file-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
+VitePress verwendet **Datei-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
 
 VitePress bietet außerdem die Möglichkeit, saubere URLs zu erzeugen, Pfade umzuschreiben und Seiten dynamisch zu generieren. Diese Funktionen werden in der [Routing Anleitung](./routing).
 
 ## Loslegen
 
-Wenn du dies während der Einrichtung zugelassen hast, sollte das Tool außerdem die folgenden npm-Skripte in deine `package.json` if you allowed it to do so während the setup process:
+Wenn du dies während der Einrichtung zugelassen hast, sollte das Tool außerdem die folgenden npm-Skripte in deine `package.json` wenn you allowed it to do so während the setup process:
 
 ```json [package.json]
 {
@@ -200,8 +200,8 @@ The dev server should be running at `http://localhost:5173`. Öffne die URL in d
 
 - Um mehr darüber zu erfahren, was du auf einer Seite tun kannst, etwa Markdown-Inhalte schreiben oder Vue-Komponenten verwenden, lies den Abschnitt „Schreiben“ der Anleitung. Ein guter Ausgangspunkt sind die [Markdown Extensions](./markdown).
 
-- Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-theme-config).
+- Um die Funktionen des Standard-DokumentationsThemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-Theme-config).
 
-- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
+- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-Theme) oder [ein eigenes Theme erstellst](./eigene-Theme).
 
 - Sobald deine Dokumentations-Website Gestalt annimmt, solltest du die [Bereitstellung Anleitung](./deploy).

From 9671bb4686675d604f0ff05dd0e5bb801f437e9a Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:34 +0200
Subject: [PATCH 125/199] docs(de): translate guide prose

---
 docs/de/guide/i18n.md | 28 ++++++++++++++--------------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/docs/de/guide/i18n.md b/docs/de/guide/i18n.md
index 1ad6db3af..557d70840 100644
--- a/docs/de/guide/i18n.md
+++ b/docs/de/guide/i18n.md
@@ -1,5 +1,5 @@
 ---
-description: Set up internationalization (i18n) in VitePress to Unterstützung multiple languages for your site.
+description: Set up internationalization (i18n) in VitePress to Unterstützung mulTipple languages for your site.
 ---
 
 # Internationalisierung
@@ -15,7 +15,7 @@ docs/
 ├─ foo.md
 ```
 
-Then in `docs/.vitepress/config.ts`:
+Dann in `docs/.vitepress/config.ts`:
 
 ```ts [docs/.vitepress/config.ts]
 import { defineConfig } from 'vitepress'
@@ -39,7 +39,7 @@ export default defineConfig({
 })
 ```
 
-The following properties can be overridden for each locale (including root):
+The folgende properties can be overridden for jede locale (including root):
 
 ```ts
 interface LocaleSpecificConfig<ThemeConfig = any> {
@@ -53,13 +53,13 @@ interface LocaleSpecificConfig<ThemeConfig = any> {
 }
 ```
 
-Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-theme.d.ts) interface for details on customizing the placeholder texts of the default theme. Don't override `themeConfig.algolia` or `themeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-theme-search#algolia-search-i18n) for Verwendung multilingual search.
+Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-Theme.d.ts) interface for details on eigeneizing the placeholder texts of the Standard-Theme. Don't override `ThemeConfig.algolia` or `ThemeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-Theme-search#algolia-search-i18n) for Verwendung multilingual search.
 
-**Pro tip:** Config file can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a Konfiguration file per locale and then merge and export them von `index.ts`.
+**Pro Tipp:** Config Datei can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a Konfiguration Datei per locale and dann merge and export them von `index.ts`.
 
 ## Per-locale Markdown Strings
 
-Strings baked in pages by the markdown renderer - the default titles of [custom containers](./markdown#custom-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale mit the `markdown` key of a locale entry:
+Strings baked in Seites by the markdown renderer - the default titles of [eigene containers](./markdown#eigene-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale mit the `markdown` key of a locale entry:
 
 ```ts [docs/.vitepress/config.ts]
 import { defineConfig } from 'vitepress'
@@ -86,11 +86,11 @@ export default defineConfig({
 })
 ```
 
-Values fall back to the root-level `markdown` options when a locale leaves them unset. Locale entries can only override the titles of containers registered at the root level - registering new containers per locale is not supported. Also note that since the markdown renderer is erstellt once for the whole site, these can only be declared in the main config file, not in additional configs.
+Values falle back to the root-level `markdown` Options wenn a locale leaves them unset. Locale entries can nur override the titles of containers registered at the root level - registering new containers per locale is not supported. Also Hinweis dass since the markdown renderer is erstellt once for the whole site, these can nur be declared in the main config Datei, not in additional configs.
 
-## Separate directory for each locale
+## Separate directory for jede locale
 
-The following is a perfectly fine structure:
+The folgende is a perfectly fine structure:
 
 ```
 docs/
@@ -102,7 +102,7 @@ docs/
    ├─ foo.md
 ```
 
-However, VitePress won't redirect `/` to `/en/` by default. You'll need to configure your server for that. Zum Beispiel, on Netlify, you can add a `docs/public/_redirects` file like this:
+However, VitePress won't redirect `/` to `/en/` standardmäßig. You'll need to configure your server for that. Zum Beispiel, on Netlify, du kannst add a `docs/public/_redirects` Datei like this:
 
 ```
 /*  /es/:splat  302  Language=es
@@ -110,7 +110,7 @@ However, VitePress won't redirect `/` to `/en/` by default. You'll need to confi
 /*  /en/:splat  302
 ```
 
-**Pro tip:** If Verwendung the above approach, you can use `nf_lang` cookie to persist user's language choice:
+**Pro Tipp:** Wenn Verwendung the above approach, du kannst use `nf_lang` cookie to persist user's language choice:
 
 ```ts [docs/.vitepress/theme/index.ts]
 import DefaultTheme from 'vitepress/theme'
@@ -143,7 +143,7 @@ watchEffect(() => {
 
 ## RTL Support
 
-For right-to-left languages, set `dir: 'rtl'` in the config. The default theme is laid out mit [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_values), so the layout, the navigation and directional icons follow the dokumentieren direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
+For right-to-left languages, set `dir: 'rtl'` in the config. The Standard-Theme is laid out mit [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_Werts), so the layout, the navigation and directional icons follow the dokumentieren direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
 
 ```ts [docs/.vitepress/config.ts]
 export default {
@@ -152,9 +152,9 @@ export default {
 }
 ```
 
-For a multilingual site, set `dir` per locale in `locales`. It can also be overridden for a single page mit the [`dir`](../reference/frontmatter-config#dir) frontmatter option. Code blocks always stay left-to-right.
+For a multilingual site, set `dir` per locale in `locales`. It can außerdem be overridden for a single Seite mit the [`dir`](../reference/frontmatter-config#dir) frontmatter Option. Code blocks immer stay left-to-right.
 
-When adding your own styles, prefer logical properties such as `margin-inline-start` over `margin-left`, and mirror your own directional icons in right-to-left layouts:
+Wenn adding your own styles, prefer logical properties wie `margin-inline-start` over `margin-left`, and mirror your own directional icons in right-to-left layouts:
 
 ```css
 [dir='rtl'] .my-arrow-icon {

From a4a09f573b62acda3732169b72039b24ba5ab30b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 11:59:59 +0200
Subject: [PATCH 126/199] docs(de): translate guide prose safely

---
 docs/de/guide/custom-theme.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/de/guide/custom-theme.md b/docs/de/guide/custom-theme.md
index 1db0cbd8a..3367b8f0e 100644
--- a/docs/de/guide/custom-theme.md
+++ b/docs/de/guide/custom-theme.md
@@ -6,7 +6,7 @@ description: Erstelle und verwende ein eigenes Theme in VitePress, um das Ersche
 
 ## Theme-Auflösung
 
-Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/Theme/index.js` or `.vitepress/Theme/index.ts` Datei (die „Theme-Einstiegsdatei“):
+Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (die „Theme-Einstiegsdatei“):
 
 ```
 .
@@ -19,7 +19,7 @@ Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/Theme/index.js` o
 └─ package.json
 ```
 
-VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend the Standard-Theme](./extending-default-Theme) to perform advanced eigeneizations on top of it.
+VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend das Standard-Theme](./extending-default-theme) to perform advanced customizations on top of it.
 
 ## Theme-Schnittstelle
 
@@ -73,7 +73,7 @@ export default {
 }
 ```
 
-Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global Komponentes](./extending-default-Theme.md#registering-global-Komponentes), integrate mit Vue libraries, etc.
+Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
 
 Der Wert `router` ist dieselbe VitePress-Router-Instanz, die von [`useRouter()`](../reference/runtime-api#userouter). Um auf Routenänderungen zu reagieren, weist du dem Router Handler zu:
 
@@ -115,11 +115,11 @@ Mit `extends` wird das `setup` jedes Themes wie bei `enhanceApp` von der Basis a
 
 Der Standardexport ist der einzige Vertrag für ein eigenes Theme, und nur die Eigenschaft `Layout` ist erforderlich. Technisch kann ein VitePress-Theme daher aus nur einer einzigen Vue-Komponente bestehen.
 
-Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Bjedete, dass das Theme außerdem [SSR-compatible](./ssr-compat).
+Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Beachte, dass das Theme außerdem [SSR-compatible](./ssr-compat).
 
 ## Ein Layout erstellen
 
-Die einfachste Layout-Komponente muss eine [`<Content />`](../reference/runtime-api#Inhalt) -Komponente enthalten:
+Die einfachste Layout-Komponente muss eine [`<Content />`](../reference/runtime-api#content) -Komponente enthalten:
 
 ```vue [.vitepress/theme/Layout.vue]
 <template>
@@ -148,7 +148,7 @@ const { page } = useData()
 </template>
 ```
 
-The [`useData()`](../reference/runtime-api#useDaten) helper provides us mit alle the runtime Daten we need to conditionally render different layouts. One of the andere Daten we can access is the current Seite's frontmatter. We can leverage this to allow the end user to control the layout in jede Seite. Zum Beispiel, the user can indicate the Seite should use a special home Seite layout mit:
+The [`useData()`](../reference/runtime-api#usedata) helper provides us with all the runtime data we need to conditionally render different layouts. One of the other data we can access is die aktuelle Seite's frontmatter. We can leverage this to allow the end user to control the layout in each page. Zum Beispiel, the user can indicate die Seite should use a special home Seitenlayout with:
 
 ```md
 ---
@@ -156,7 +156,7 @@ layout: home
 ---
 ```
 
-And we can adjust our Theme to handle this:
+And we can adjust our theme to handle this:
 
 ```vue{3,12-14}
 <script setup>
@@ -198,7 +198,7 @@ const { page, frontmatter } = useData()
 </template>
 ```
 
-In der [Runtime API Referenz](../reference/runtime-api) findest du alles, was in Theme-Komponenten verfügbar ist. Zusätzlich kannst du [Build-Time Data Loading](./Daten-loading) nutzen, um datenbasierte Layouts zu erzeugen – beispielsweise eine Seite, die alle Blogbeiträge des aktuellen Projekts auflistet.
+In der [Runtime API Referenz](../reference/runtime-api) findest du alles, was in Theme-Komponenten verfügbar ist. Zusätzlich kannst du [Build-Time Data Loading](./data-loading) nutzen, um datenbasierte Layouts zu erzeugen – beispielsweise eine Seite, die alle Blogbeiträge des aktuellen Projekts auflistet.
 
 ## Ein eigenes Theme verteilen
 
@@ -210,7 +210,7 @@ Wenn du das Theme als npm-Paket verteilen möchtest, gehe folgendermaßen vor:
 
 2. Falls zutreffend, exportiere die Typdefinition deiner Theme-Konfiguration als `ThemeConfig`.
 
-3. Wenn dein Theme Anpassungen an der VitePress-Konfiguration erfordert, exportiere diese Konfiguration unter einem Paket-Unterpfad (e.g. `my-Theme/config`) damit Benutzer sie erweitern können.
+3. Wenn dein Theme Anpassungen an der VitePress-Konfiguration erfordert, exportiere diese Konfiguration unter einem Paket-Unterpfad (e.g. `my-theme/config`) damit Benutzer sie erweitern können.
 
 4. Dokumentiere die Optionen der Theme-Konfiguration sowohl über die Konfigurationsdatei als auch über Frontmatter.
 

From 4de4bdfdb6e034676e358ded828e092d86db7cc5 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:02 +0200
Subject: [PATCH 127/199] docs(de): translate guide prose safely

---
 docs/de/guide/data-loading.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index f21e4c56b..71a5842ee 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -10,7 +10,7 @@ Data Loader können verwendet werden, um entfernte Daten abzurufen oder Metadate
 
 ## Grundlegende Verwendung
 
-Eine Data-Loader-Datei muss mit `.Daten.js` or `.Daten.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
+Eine Data-Loader-Datei muss mit `.data.js` or `.data.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
 
 ```js [example.data.js]
 export default {
@@ -24,7 +24,7 @@ export default {
 
 Das Loader-Modul wird nur in Node.js ausgewertet. Du kannst daher nach Bedarf Node-APIs und npm-Abhängigkeiten importieren.
 
-Du kannst anschließend Daten aus dieser Datei in `.md`-Seiten und `.vue`-Komponenten mit dem `Daten` named export:
+Du kannst anschließend Daten aus dieser Datei in `.md`-Seiten und `.vue`-Komponenten mit dem `data` named export:
 
 ```vue
 <script setup>
@@ -42,7 +42,7 @@ Ausgabe:
 }
 ```
 
-Du wirst feststellen, dass der Data Loader selbst `Daten` nicht exportiert. Stattdessen ruft VitePress im Hintergrund die Methode `load()` auf und stellt das Ergebnis implizit über den benannten Export `Daten` bereit.
+Du wirst feststellen, dass der Data Loader selbst `data` nicht exportiert. Stattdessen ruft VitePress im Hintergrund die Methode `load()` auf und stellt das Ergebnis implizit über den benannten Export `data` bereit.
 
 Das funktioniert auch, wenn der Loader asynchron ist:
 
@@ -85,7 +85,7 @@ export default {
 
 ## `createContentLoader`
 
-Beim Erstellen einer inhaltsorientierten Website müssen wir häufig eine „Archiv“- oder „Index“-Seite erstellen: eine Seite, auf der wir alle verfügbaren Einträge unserer Inhaltssammlung auflisten, beispielsweise Blogbeiträge oder API-Seiten. Wir **können** dies direkt mit der Data-Loader-API umsetzen. Da dies jedoch ein sehr häufiger Anwendungsfalle ist, stellt VitePress den Helper `createContentLoader` bereit, der dies vereinfacht:
+Beim Erstellen einer inhaltsorientierten Website müssen wir häufig eine „Archiv“- oder „Index“-Seite erstellen: eine Seite, auf der wir alle verfügbaren Einträge unserer Inhaltssammlung auflisten, beispielsweise Blogbeiträge oder API-Seiten. Wir **können** dies direkt mit der Data-Loader-API umsetzen. Da dies jedoch ein sehr häufiger Anwendungsfall ist, stellt VitePress den Helper `createContentLoader` bereit, der dies vereinfacht:
 
 ```js [posts.data.js]
 import { createContentLoader } from 'vitepress'
@@ -93,7 +93,7 @@ import { createContentLoader } from 'vitepress'
 export default createContentLoader('posts/*.md', /* options */)
 ```
 
-Der Helper akzeptiert ein Glob-Muster relativ zum [source directory](./routing#source-directory), und gibt ein `{ watch, load }`-Data-Loader-Objekt zurück, das als Standardexport in einer Data-Loader-Datei verwendet werden kann. Außerdem wird ein Cache auf Grundlage der Änderungszeitpunkte von Dateien verwendet, um die Leistung während der Entwicklung zu verbessern.
+Der Helper akzeptiert ein Glob-Muster relativ zum [Quellverzeichnis](./routing#source-directory), und gibt ein `{ watch, load }`-Data-Loader-Objekt zurück, das als Standardexport in einer Data-Loader-Datei verwendet werden kann. Außerdem wird ein Cache auf Grundlage der Änderungszeitpunkte von Dateien verwendet, um die Leistung während der Entwicklung zu verbessern.
 
 Hinweis: Der Loader funktioniert nur mit Markdown-Dateien – gefundene Dateien ohne Markdown-Endung werden übersprungen.
 
@@ -159,7 +159,7 @@ export default createContentLoader('posts/*.md', {
 })
 ```
 
-Sieh dir an, wie dies im [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/Theme/posts.Daten.ts).
+Sieh dir an, wie dies im [Vue.js blog](https://github.com/vuejs/blog/blob/main/.vitepress/theme/posts.data.ts).
 
 Die `createContentLoader`-API kann auch innerhalb von [build hooks](../reference/site-config#build-hooks):
 
@@ -216,7 +216,7 @@ interface ContentOptions<T = ContentData[]> {
 
 ## Typisierte Data Loader
 
-Bei Verwendung von TypeScript kannst du deinen Loader und den `Daten`-Export wie folgt typisieren:
+Bei Verwendung von TypeScript kannst du deinen Loader und den `data`-Export wie folgt typisieren:
 
 ```ts
 import { defineLoader } from 'vitepress'

From 5030abc85e3a379501273e6e3d153e4001d195f8 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:06 +0200
Subject: [PATCH 128/199] docs(de): translate guide prose safely

---
 docs/de/guide/deploy.md | 82 ++++++++++++++++++++---------------------
 1 file changed, 41 insertions(+), 41 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index b2c6b8476..18623d610 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -50,7 +50,7 @@ Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
 ## Einen öffentlichen Basispfad festlegen
 
-Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) Option to `'/blog/'` in the VitePress config.
+Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
 
 **Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, dann set your `base` to `/repo/`.
 
@@ -66,23 +66,23 @@ export default {
 
 Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Derselbe Build funktioniert von **jedem** Unterpfad aus ohne erneuten Build – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
 
-Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`Datei://`) außerdem works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `Datei://`, so there is no hydration there — interactive features like search stay inactive, while alle pre-rendered Inhalt and links keep working.
+Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) also works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
 
-Einige Dinge solltest du bjedeten:
+Einige Dinge solltest du beachten:
 
 - Lasse [`cleanUrls`](../reference/site-config#cleanurls) deaktiviert (Standardeinstellung): Für portable Ausgaben müssen Links mit `.html` enden, da kein Server vorhanden ist, der saubere URLs umschreibt.
 - `404.html` wird für die Stammebene erzeugt. Hosts, die sie als Fallback für beliebig tiefe URLs ausliefern, rendern sie ohne Styles (there is no correct relative prefix for an unknown depth).
 - [`head`](../reference/site-config#head) Einträge werden wie immer unverändert ausgegeben – vermeide dort absolute Pfade wie `/favicon.ico` there and prefer absolute URLs or `transformHead`.
 - Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
-- Von [`createContentLoader`](./Daten-loading#createInhaltloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in andere Seites, so no single relative prefix is correct) — they resolve nur for a root mount.
-- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on Seite URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually alle static hosts canonicalize this way bereits.
+- Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
+- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
 - Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktions-Build.
 
 ## HTTP-Cache-Header
 
 Wenn du Kontrolle über die HTTP-Header deines Produktionsservers hast, kannst du `cache-control`-Header konfigurieren, um bei wiederholten Besuchen eine bessere Leistung zu erzielen.
 
-Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and andere imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see Dateis like `app.4f283b18.js`.
+Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and other imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see files like `app.4f283b18.js`.
 
 Dieser Hash `4f283b18` wird aus dem Inhalt dieser Datei erzeugt. Dieselbe gehashte URL liefert garantiert denselben Dateiinhalt – wenn sich der Inhalt ändert, ändern sich auch die URLs. Das bedeutet, dass du für diese Dateien bedenkenlos die stärksten Cache-Header verwenden kannst. Alle solchen Dateien werden im Ausgabeverzeichnis unter `assets/` abgelegt. Dafür kannst du den folgenden Header konfigurieren:
 
@@ -98,7 +98,7 @@ Cache-Control: max-age=31536000,immutable
   cache-control: immutable
 ```
 
-Hinweis: Die Datei `_headers` sollte im [public directory](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - liegen, damit sie unverändert in das Ausgabeverzeichnis kopiert wird.
+Hinweis: Die Datei `_headers` sollte im [Public-Verzeichnis](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - liegen, damit sie unverändert in das Ausgabeverzeichnis kopiert wird.
 
 [Netlify-Dokumentation zu benutzerdefinierten Headern](https://docs.netlify.com/routing/headers/)
 
@@ -138,7 +138,7 @@ Richte ein neues Projekt ein und ändere diese Einstellungen über dein Dashboar
 - **Ausgabeverzeichnis:** `docs/.vitepress/dist`
 - **Node-Version:** `20` (or above)
 
-::: Warnung
+::: warning
 Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommentare aus der Ausgabe entfernt, die für Vue Bedeutung haben. Wenn sie entfernt werden, können Hydration-Mismatch-Fehler auftreten.
 :::
 
@@ -162,14 +162,14 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 
    # Legt die Berechtigungen des GITHUB_TOKEN für die Bereitstellung auf GitHub Pages fest
    permissions:
-     Inhalts: read
-     Seites: write
+     contents: read
+     pages: write
      id-token: write
 
    # Erlaubt nur eine gleichzeitige Bereitstellung und überspringt zwischenzeitlich eingereihtes Ausführungen.
    # Laufende Ausführungen dürfen jedoch NICHT abgebrochen werden, damit diese Produktionsbereitstellungen abgeschlossen werden können.
    concurrency:
-     group: Seites
+     group: pages
      cancel-in-progress: false
 
    jobs:
@@ -179,56 +179,56 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
        steps:
          - name: Checkout
            uses: actions/checkout@v5
-           mit:
+           with:
              fetch-depth: 0 # Not needed wenn lastUpdated is not enabled
-         # - uses: pnpm/action-setup@v4 # Uncomment this block wenn you're mithilfe von pnpm
-         #   mit:
+         # - uses: pnpm/action-setup@v4 # Uncomment this block wenn you're using pnpm
+         #   with:
          #     version: 9 # Not needed wenn you've set "packageManager" in package.json
-         # - uses: oven-sh/setup-bun@v1 # Uncomment this wenn you're mithilfe von Bun
+         # - uses: oven-sh/setup-bun@v1 # Uncomment this wenn you're using Bun
          - name: Setup Node
            uses: actions/setup-node@v6
-           mit:
+           with:
              node-version: 24
              cache: npm # or pnpm / yarn
          - name: Cache VitePress
            uses: actions/cache@v4
-           mit:
-             Pfad: docs/.vitepress/cache
+           with:
+             path: docs/.vitepress/cache
              key: ${{ runner.os }}-vitepress-${{ hashFiles('docs/**', 'package-lock.json', 'pnpm-lock.yaml', 'yarn.lock', 'bun.lockb') }}
              restore-keys: |
                ${{ runner.os }}-vitepress-
          - name: Setup Pages
-           uses: actions/configure-Seites@v4
-         - name: Installe dependencies
-           run: npm ci # or pnpm installe / yarn installe / bun install
-         - name: Build mit VitePress
+           uses: actions/configure-pages@v4
+         - name: Install dependencies
+           run: npm ci # or pnpm install / yarn install / bun install
+         - name: Build with VitePress
            run: npm run docs:build # or pnpm docs:build / yarn docs:build / bun run docs:build
          - name: Upload artifact
-           uses: actions/upload-Seites-artifact@v3
-           mit:
-             Pfad: docs/.vitepress/dist
+           uses: actions/upload-pages-artifact@v3
+           with:
+             path: docs/.vitepress/dist
 
      # Bereitstellungsaufgabe
      deploy:
        environment:
-         name: github-Seites
-         url: ${{ steps.deployment.Ausgabes.Seite_url }}
+         name: github-pages
+         url: ${{ steps.deployment.outputs.page_url }}
        needs: build
        runs-on: ubuntu-latest
        name: Bereitstellen
        steps:
          - name: Bereitstellen to GitHub Pages
            id: deployment
-           uses: actions/deploy-Seites@v4
+           uses: actions/deploy-pages@v4
    ```
 
-   ::: Warnung
-   Stelle sicher, dass die Option `base` in deiner VitePress-Konfiguration korrekt konfiguriert ist. Weitere Informationen findest du unter [Einen öffentlichen Basispfad festlegen](#Einstellung-a-public-base-Pfad).
+   ::: warning
+   Stelle sicher, dass die Option `base` in deiner VitePress-Konfiguration korrekt konfiguriert ist. Weitere Informationen findest du unter [Einen öffentlichen Basispfad festlegen](#setting-a-public-base-path).
    :::
 
 2. Wähle in den Repository-Einstellungen unter „Pages“ bei „Build and deployment > Source“ die Option „GitHub Actions“ aus.
 
-3. Übertrage deine Änderungen auf den `main`-Branch und warte, bis der GitHub-Actions-Workflow abgeschlossen ist. Deine Website sollte anschließend unter `https://<username>.github.io/[repository]/` oder `https://<eigene-domain>/` bereitstehen, abhängig von deinen Einstellungen. Deine Website wird bei jedem Push auf den `main`-Branch automatisch bereitgestellt.
+3. Übertrage deine Änderungen auf den `main`-Branch und warte, bis der GitHub-Actions-Workflow abgeschlossen ist. Deine Website sollte anschließend unter `https://<username>.github.io/[repository]/` oder `https://<custom-domain>/` bereitstehen, abhängig von deinen Einstellungen. Deine Website wird bei jedem Push auf den `main`-Branch automatisch bereitgestellt.
 
 ### GitLab Pages
 
@@ -238,18 +238,18 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 
    ```yaml [.gitlab-ci.yml]
    image: node:24
-   Seites:
+   pages:
      cache:
-       Pfads:
+       paths:
          - node_modules/
      script:
-       # - apk add git # Uncomment this wenn you're mithilfe von smalle docker images like alpine and have lastUpdated enabled
+       # - apk add git # Uncomment this wenn you're using small docker images like alpine and have lastUpdated enabled
        - npm install
        - npm run docs:build
      artifacts:
-       Pfads:
+       paths:
          - public
-     nur:
+     only:
        - main
    ```
 
@@ -262,12 +262,12 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
 2. Setze diese Werte in deiner Konfigurationsdatei (und entferne nicht benötigte Werte wie `api_location`):
 
    - **`app_location`**: `/`
-   - **`Ausgabe_location`**: `docs/.vitepress/dist`
+   - **`output_location`**: `docs/.vitepress/dist`
    - **`app_build_command`**: `npm run docs:build`
 
 ### CloudRay
 
-Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by folgende these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
+Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by following these [instructions](https://cloudray.io/articles/how-to-deploy-vitepress-site).
 
 ### Firebase
 
@@ -314,13 +314,13 @@ Du kannst deploy your VitePress project mit [CloudRay](https://cloudray.io/) by
 
 ### Hostinger
 
-Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by folgende these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). Wähle bei der Build-Konfiguration VitePress als Framework und setze das Stammverzeichnis auf `./docs`.
+Du kannst deploy your VitePress project mit [Hostinger](https://www.hostinger.com/web-apps-hosting) by following these [instructions](https://www.hostinger.com/Unterstützung/how-to-deploy-a-nodejs-website-in-hostinger/). Wähle bei der Build-Konfiguration VitePress als Framework und setze das Stammverzeichnis auf `./docs`.
 
 ### Lizard
 
 [Lizard (lizard.build)](https://lizard.build) builds VitePress sites von source and serves the generated HTML. For the layout verwendet in this guide, it detects `docs:build` and serves `docs/.vitepress/dist` on port `80`.
 
-Installe the [Lizard CLI](https://lizard.build/docs/cli) and sign in mit `lizard login`. To deploy a local source directory, run these commands von the project root containing `package.json`:
+Install the [Lizard CLI](https://lizard.build/docs/cli) and sign in mit `lizard login`. To deploy a local Quellverzeichnis, run these commands von the Projektstammverzeichnis containing `package.json`:
 
 ```sh
 lizard init --name vitepress-docs
@@ -332,7 +332,7 @@ Lasse Überschreibungen für Build- und Startbefehle leer, damit die automatisch
 
 ### Stormkit
 
-Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) by folgende these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
+Du kannst deploy your VitePress project to [Stormkit](https://www.stormkit.io) by following these [instructions](https://stormkit.io/blog/how-to-deploy-vitepress).
 
 ### Surge
 

From 403749e02f428f999e9a385b192f301a8052c921 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:08 +0200
Subject: [PATCH 129/199] docs(de): translate guide prose safely

---
 docs/de/guide/extending-default-theme.md | 76 ++++++++++++------------
 1 file changed, 38 insertions(+), 38 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index 38ef6f0d8..074f1f0a2 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -1,27 +1,27 @@
 ---
 outline: deep
-description: Anpassen and extend the VitePress Standard-Theme mit eigene CSS, Komponentes, layouts, and slots.
+description: Anpassen and extend the VitePress Standard-Theme mit custom CSS, components, layouts, and slots.
 ---
 
 # Standard-Theme erweitern
 
-VitePress' Standard-Theme is optimized for documentation, and can be eigeneized. Consult the [Standard-Theme Config Übersicht](../reference/default-Theme-config) for a comprehensive list of Options.
+VitePress' Standard-Theme is optimized for documentation, and can be customized. Consult the [Standard-Theme Config Übersicht](../reference/default-theme-config) for a comprehensive list of options.
 
-However, there are a number of cases wo Konfiguration alone won't be enough. Zum Beispiel:
+However, there are a number of cases where Konfiguration alone won't be enough. Zum Beispiel:
 
 1. You need to tweak the CSS styling;
-2. You need to modify the Vue app instance, zum Beispiel to register global Komponentes;
-3. You need to inject eigene Inhalt in the Theme über layout slots.
+2. You need to modify the Vue app instance, zum Beispiel to register global components;
+3. You need to inject custom content in the theme via layout slots.
 
-These advanced eigeneizations will require Verwendung a eigene Theme dass "extends" the Standard-Theme.
+These advanced customizations will require Verwendung a eigenes Theme that "extends" das Standard-Theme.
 
-::: Tipp
-Before proceeding, make sure to first read [Using a Eigenes Theme](./eigene-Theme) to understand how eigene Themes work.
+::: tip
+Before proceeding, make sure to first read [Using a Eigenes Theme](./custom-theme) to understand how eigenes Themes work.
 :::
 
 ## Anpassen CSS
 
-The Standard-Theme CSS is eigeneizable by overriding root level CSS variables:
+The Standard-Theme CSS is customizable by overriding root level CSS variables:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -38,11 +38,11 @@ export default DefaultTheme
 }
 ```
 
-Siehe [Standard-Theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/Theme-default/styles/vars.css) dass can be overridden.
+Siehe [Standard-Theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css) that can be overridden.
 
 ### Navbar
 
-The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching Komponente internals:
+The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching component internals:
 
 ```css
 :root {
@@ -72,19 +72,19 @@ Zum Beispiel, a frosted-glass navbar:
 }
 ```
 
-The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color standardmäßig, and wo the two bars meet they share a single blurred surface, so the glass stays continuous across them.
+The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color standardmäßig, and where the two bars meet they share a single blurred surface, so the glass stays continuous across them.
 
-::: Warnung
-`backdrop-filter` has a measurable scroll performance cost, insbesondere on large or high-DPI screens. Wenn Verwendung a translucent bar, außerdem check text contrast over your Seite Inhalt. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
+::: warning
+`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. Wenn Verwendung a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
 :::
 
-Wenn the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar stattdessen of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-Theme-config#extramenulabel).
+Wenn the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar instead of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
 
 ## Using Different Fonts
 
-VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the build Ausgabe. The font is außerdem auto preloaded in production. However, this may not be desirable wenn you want to use a different main font.
+VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the Build-Ausgabe. The font is also auto preloaded in production. However, this may not be desirable wenn you want to use a different main font.
 
-To avoid including Inter in the build Ausgabe, import the Theme von `vitepress/Theme-ohne-fonts` stattdessen:
+To avoid including Inter in the Build-Ausgabe, import the theme von `vitepress/theme-ohne-fonts` instead:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme-without-fonts'
@@ -101,11 +101,11 @@ export default DefaultTheme
 }
 ```
 
-::: Warnung
-Wenn du are Verwendung Optional Komponentes like the [Team Seite](../reference/default-Theme-team-Seite) Komponentes, make sure to außerdem import them von `vitepress/Theme-ohne-fonts`!
+::: warning
+Wenn du are Verwendung optional components like the [Team Seite](../reference/default-theme-team-page) components, make sure to also import them von `vitepress/theme-ohne-fonts`!
 :::
 
-Wenn your font is a local Datei referenced über `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` mit hashed Dateiname. To preload this Datei, use the [transformHead](../reference/site-config#transformhead) build hook:
+Wenn your font is a local file referenced via `@font-face`, it will be processed as an asset and included under `.vitepress/dist/assets` mit hashed filename. To preload this file, use the [transformHead](../reference/site-config#transformhead) build hook:
 
 ```js [.vitepress/config.js]
 export default {
@@ -159,11 +159,11 @@ export default {
 } satisfies Theme
 ```
 
-Since we are Verwendung Vite, du kannst außerdem leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of Komponentes.
+Since we are Verwendung Vite, du kannst außerdem leverage Vite's [glob import feature](https://vite.dev/guide/features.html#glob-import) to auto register a directory of components.
 
 ## Layout Slots
 
-The Standard-Theme's `<Layout/>` Komponente has a few slots dass can be verwendet to inject Inhalt at certain locations of the Seite. Here's an Beispiel of injecting a Komponente in the bevor outline:
+The Standard-Theme's `<Layout/>` component has a few slots that can be verwendet to inject content at certain locations of die Seite. Here's an example of injecting a component in the bevor outline:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -210,9 +210,9 @@ export default {
 }
 ```
 
-Full list of slots verfügbar in the Standard-Theme layout:
+Full list of slots verfügbar in das Standard-Theme layout:
 
-- Wenn `layout: 'doc'` (default) is enabled über frontmatter:
+- Wenn `layout: 'doc'` (default) is enabled via frontmatter:
   - `doc-top`
   - `doc-bottom`
   - `doc-footer-bevor`
@@ -226,7 +226,7 @@ Full list of slots verfügbar in the Standard-Theme layout:
   - `aside-outline-nach`
   - `aside-ads-bevor`
   - `aside-ads-nach`
-- Wenn `layout: 'home'` is enabled über frontmatter:
+- Wenn `layout: 'home'` is enabled via frontmatter:
   - `home-hero-bevor`
   - `home-hero-info-bevor`
   - `home-hero-info`
@@ -237,30 +237,30 @@ Full list of slots verfügbar in the Standard-Theme layout:
   - `home-hero-nach`
   - `home-features-bevor`
   - `home-features-nach`
-- Wenn `layout: 'Seite'` is enabled über frontmatter:
-  - `Seite-top`
-  - `Seite-bottom`
-- On not found (404) Seite:
+- Wenn `layout: 'page'` is enabled via frontmatter:
+  - `page-top`
+  - `page-bottom`
+- On not found (404) page:
   - `not-found`
 - Always:
   - `layout-top`
   - `layout-bottom`
   - `nav-bar-title-bevor`
   - `nav-bar-title-nach`
-  - `nav-bar-Inhalt-bevor`
-  - `nav-bar-Inhalt-nach`
-  - `nav-screen-Inhalt-bevor`
-  - `nav-screen-Inhalt-nach`
+  - `nav-bar-content-bevor`
+  - `nav-bar-content-nach`
+  - `nav-screen-content-bevor`
+  - `nav-screen-content-nach`
 
 ## Using View Transitions API
 
 ### On Appearance Toggle
 
-Du kannst extend the Standard-Theme to provide a eigene transition wenn the color mode is toggled. An Beispiel:
+Du kannst extend das Standard-Theme to provide a custom transition wenn the color mode is toggled. An example:
 
-<<< @/Komponentes/AppearanceToggleTransition.vue [.vitepress/Theme/Layout.vue]
+<<< @/components/AppearanceToggleTransition.vue [.vitepress/theme/Layout.vue]
 
-Result (**Warnung!**: flashing colors, sudden movements, bright lights):
+Result (**warning!**: flashing colors, sudden movements, bright lights):
 
 <details>
 <summary>Demo</summary>
@@ -277,7 +277,7 @@ Coming soon.
 
 ## Overriding Internal Components
 
-Du kannst use Vite's [aliases](https://vite.dev/config/shared-Options.html#resolve-alias) to replace Standard-Theme Komponentes mit your eigene ones:
+Du kannst use Vite's [aliases](https://vite.dev/config/shared-options.html#resolve-alias) to replace Standard-Theme components mit your custom ones:
 
 ```ts
 import { fileURLToPath, URL } from 'node:url'
@@ -299,4 +299,4 @@ export default defineConfig({
 })
 ```
 
-To know the exact name of the Komponente refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/Theme-default/Komponentes). Since the Komponentes are internal, there is a slight chance their name is updated zwischen minor releases.
+To know the exact name of the component refer [our source code](https://github.com/vuejs/vitepress/tree/main/src/client/theme-default/components). Since the components are internal, there is a slight chance their name is updated zwischen minor releases.

From 687d094c86744c56e6a0e359b96192b517d197cf Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:11 +0200
Subject: [PATCH 130/199] docs(de): translate guide prose safely

---
 docs/de/guide/frontmatter.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
index e06092460..2639652f8 100644
--- a/docs/de/guide/frontmatter.md
+++ b/docs/de/guide/frontmatter.md
@@ -36,9 +36,9 @@ editLink: true
 Inhalt der Anleitung
 ```
 
-Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [Inhalt loader](./Daten-loading#createInhaltloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
+Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [content loader](./data-loading#createcontentloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
 
-Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#useDaten) -Helper zugreifen.
+Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#usedata) -Helper zugreifen.
 
 ## Alternative Frontmatter-Formate
 

From ea7bf13068d50fe8b997acf8969cd1db1c594ff4 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:14 +0200
Subject: [PATCH 131/199] docs(de): translate guide prose safely

---
 docs/de/guide/getting-started.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index 6589972d3..ff3481883 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -43,9 +43,9 @@ $ deno add -D vitepress@next
 
 :::
 
-::: Tipp Hinweis
+::: tip Hinweis
 
-VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change the Datei extension of your relevant Dateis like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-nur) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` stattdessen.
+VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change die Datei extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` instead.
 
 :::
 
@@ -77,7 +77,7 @@ Der Assistent stellt dir einige einfache Fragen:
 
 <<< @/snippets/init.ansi
 
-::: Tipp Vue als Peer-Abhängigkeit
+::: tip Vue als Peer-Abhängigkeit
 Wenn du Anpassungen vornehmen möchtest, die Vue-Komponenten oder APIs verwenden, solltest du `vue` zusätzlich ausdrücklich als Abhängigkeit installieren.
 :::
 
@@ -98,15 +98,15 @@ Angenommen, du hast das VitePress-Projekt in `./docs`, Die erzeugte Dateistruktu
 └─ package.json
 ```
 
-Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und Optionale Anpassungen des Themes reserviert.
+Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionale Anpassungen des Themes reserviert.
 
-::: Tipp
-Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can außerdem be [konfiguriert](../reference/site-config#outdir).
+::: tip
+Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can also be [konfiguriert](../reference/site-config#outdir).
 :::
 
 ### Die Konfigurationsdatei
 
-Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic Options being the title and description of the site:
+Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic options being the title and description of the site:
 
 ```js [.vitepress/config.js]
 export default {
@@ -120,13 +120,13 @@ export default {
 }
 ```
 
-Du kannst das Verhalten des Themes außerdem über die `ThemeConfig` Option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on alle config Options.
+Du kannst das Verhalten des Themes außerdem über die `themeConfig` option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on all config options.
 
 ### Quelldateien
 
 Markdown-Dateien außerhalb des Verzeichnisses `.vitepress` gelten als **Quelldateien**.
 
-VitePress verwendet **Datei-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
+VitePress verwendet **file-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
 
 VitePress bietet außerdem die Möglichkeit, saubere URLs zu erzeugen, Pfade umzuschreiben und Seiten dynamisch zu generieren. Diese Funktionen werden in der [Routing Anleitung](./routing).
 
@@ -200,8 +200,8 @@ The dev server should be running at `http://localhost:5173`. Öffne die URL in d
 
 - Um mehr darüber zu erfahren, was du auf einer Seite tun kannst, etwa Markdown-Inhalte schreiben oder Vue-Komponenten verwenden, lies den Abschnitt „Schreiben“ der Anleitung. Ein guter Ausgangspunkt sind die [Markdown Extensions](./markdown).
 
-- Um die Funktionen des Standard-DokumentationsThemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-Theme-config).
+- Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-theme-config).
 
-- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-Theme) oder [ein eigenes Theme erstellst](./eigene-Theme).
+- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
 
 - Sobald deine Dokumentations-Website Gestalt annimmt, solltest du die [Bereitstellung Anleitung](./deploy).

From cd5f002b4f7997474a71daee61d57d89ec1010eb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:00:41 +0200
Subject: [PATCH 132/199] docs(de): complete standard theme config translation

---
 docs/de/reference/default-theme-config.md | 70 +++++++++++------------
 1 file changed, 35 insertions(+), 35 deletions(-)

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
index c58497527..8e8fa38a3 100644
--- a/docs/de/reference/default-theme-config.md
+++ b/docs/de/reference/default-theme-config.md
@@ -1,10 +1,10 @@
 ---
-description: Reference of all Konfiguration options verfügbar for the VitePress Standard theme.
+description: Referenz aller für das VitePress-Standard-Theme verfügbaren Konfigurationsoptionen.
 ---
 
 # Konfiguration des Standard-Themes
 
-Theme config lets you customize your theme. Du kannst define theme config via the `themeConfig` option in the config file:
+Mit der Theme-Konfiguration kannst du dein Theme anpassen. Du kannst sie über die Option `themeConfig` in der Konfigurationsdatei definieren:
 
 ```ts
 export default {
@@ -21,15 +21,15 @@ export default {
 }
 ```
 
-**The options documented on this page only apply to the Standard theme.** Different themes expect different theme config. When using a custom theme, the theme config object will be passed to the theme so the theme can define conditional behavior based on it.
+**Die auf dieser Seite dokumentierten Optionen gelten nur für das Standard-Theme.** Andere Themes erwarten eine andere Theme-Konfiguration. Bei Verwendung eines eigenen Themes wird das Theme-Konfigurationsobjekt an das Theme übergeben, damit es davon abhängiges Verhalten definieren kann.
 
 ## i18nRouting
 
 - Type: `boolean | ((data: VitePressData<DefaultTheme.Config>, route: Route, targetLocale: string) => string)`
 
-Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. Du kannst disable this behavior by setting `themeConfig.i18nRouting` to `falsch`.
+Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. Du kannst disable this behavior by setting `themeConfig.i18nRouting` to `false`.
 
-Set `themeConfig.i18nRouting` to a function to customize the locale link. The function receives the current VitePress data, the current route, and the target locale key, and gibt zurück the target link.
+Setze `themeConfig.i18nRouting` auf eine Funktion, um den Sprachlink anzupassen. Die Funktion erhält die aktuellen VitePress-Daten, die aktuelle Route und den Schlüssel der Zielsprache und gibt den Ziellink zurück.
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -51,7 +51,7 @@ export default defineConfig({
 
 - Type: `ThemeableImage`
 
-Logo file to display in nav bar, right before the site title. Accepts a path string, or an object to set a different logo for light/dark mode.
+Logo-Datei, die in der Navigationsleiste direkt vor dem Seitentitel angezeigt wird. Akzeptiert eine Pfadzeichenkette oder ein Objekt, um unterschiedliche Logos für den Hell-/Dunkelmodus festzulegen.
 
 ```ts
 export default {
@@ -70,9 +70,9 @@ type ThemeableImage =
 
 ## siteTitle
 
-- Type: `string | falsch`
+- Type: `string | false`
 
-Du kannst customize this item to replace the Standard site title (`title` in app config) in nav. When set to `falsch`, title in nav will be deaktiviert. Useful when you have `logo` that already contains the site title text.
+Du kannst dieses Element anpassen, um den Standard-Seitentitel (`title` in der App-Konfiguration) in der Navigation zu ersetzen. Bei `false` wird der Titel in der Navigation deaktiviert. Dies ist nützlich, wenn dein `logo` den Seitentitel bereits enthält.
 
 ```ts
 export default {
@@ -86,7 +86,7 @@ export default {
 
 - Type: `NavItem`
 
-The Konfiguration for the nav menu item. More details in [Standard-Theme: Nav](./Standard-theme-nav#navigation-links).
+Die Konfiguration für einen Navigationseintrag. Weitere Details findest du unter [Standard-Theme: Navigation](./Standard-theme-nav#navigation-links).
 
 ```ts
 export default {
@@ -132,9 +132,9 @@ interface NavItemWithChildren {
 
 ## sidebar
 
-- Type: `Seitenleiste`
+- Type: `Sidebar`
 
-The Konfiguration for the sidebar menu item. More details in [Standard-Theme: Seitenleiste](./Standard-theme-sidebar).
+Die Konfiguration für einen Seitenleisteneintrag. Weitere Details findest du unter [Standard-Theme: Seitenleiste](./Standard-theme-sidebar).
 
 ```ts
 export default {
@@ -203,22 +203,22 @@ export type SidebarItem = {
 ## aside
 
 - Type: `boolean | 'left'`
-- Default: `wahr`
+- Default: `true`
 - Can be overridden per page via [frontmatter](./frontmatter-config#aside)
 
-Setting this value to `falsch` prevents rendering of aside container.\
-Setting this value to `wahr` renders the aside to the right.\
-Setting this value to `left` renders the aside to the left.\
-In right-to-left layouts, both sides are mirrored.
+Setting this value to `false` prevents rendering of aside container.\
+Setting this value to `true` renders the aside to the right.\
+Wenn dieser Wert auf `left` gesetzt wird, wird der Aside-Container links gerendert.\
+In Rechts-nach-Links-Layouts werden beide Seiten gespiegelt.
 
-Wenn du want to disable it for all viewports, you should use `outline: falsch` instead.
+Wenn du es für alle Ansichtsgrößen deaktivieren möchtest, solltest du stattdessen `outline: false` verwenden.
 
 ## outline
 
-- Type: `Outline | Outline['level'] | falsch`
-- Level can be overridden per page via [frontmatter](./frontmatter-config#outline)
+- Type: `Outline | Outline['level'] | false`
+- Die Ebene kann pro Seite über das [Frontmatter] überschrieben werden.(./frontmatter-config#outline)
 
-Setting this value to `falsch` prevents rendering of outline container. Refer this interface for more details:
+Wenn dieser Wert auf `false` gesetzt wird, wird der Outline-Container nicht gerendert. Weitere Details findest du in diesem Interface:
 
 ```ts
 interface Outline {
@@ -245,7 +245,7 @@ interface Outline {
 
 - Type: `SocialLink[]`
 
-Du kannst define this option to show your social account links with icons in nav.
+Du kannst diese Option definieren, um Links zu deinen sozialen Konten mit Symbolen in der Navigation anzuzeigen.
 
 ```ts
 export default {
@@ -286,7 +286,7 @@ interface SocialLink {
 - Type: `Fußzeile`
 - Can be overridden per page via [frontmatter](./frontmatter-config#footer)
 
-Fußzeile Konfiguration. Du kannst add a message or copyright text on the footer, however, it will only be displayed when the page doesn't contain a sidebar. Dies is due to design concerns.
+Konfiguration der Fußzeile. Du kannst eine Nachricht oder einen Copyright-Text in der Fußzeile hinzufügen. Er wird jedoch nur angezeigt, wenn die Seite keine Seitenleiste enthält. Dies ist eine bewusste Designentscheidung.
 
 ```ts
 export default {
@@ -300,7 +300,7 @@ export default {
 ```
 
 ```ts
-export interface Fußzeile {
+export interface Footer {
   message?: string
   copyright?: string
 }
@@ -335,7 +335,7 @@ export interface EditLink {
 
 - Type: `LastUpdatedOptions`
 
-Allows customization for the last updated text and date format.
+Ermöglicht die Anpassung des Textes und Datumsformats für die letzte Aktualisierung.
 
 ```ts
 export default {
@@ -378,7 +378,7 @@ export interface AlgoliaSearchOptions extends DocSearchProps {
 }
 ```
 
-View full options [here](https://github.com/vuejs/vitepress/blob/main/types/docsearch.d.ts).
+Eine vollständige Liste der Optionen findest du [hier](https://github.com/vuejs/vitepress/blob/main/types/docsearch.d.ts).
 
 ## carbonAds {#carbon-ads}
 
@@ -406,13 +406,13 @@ export interface CarbonAdsOptions {
 }
 ```
 
-Learn more in [Standard-Theme: Carbon Ads](./Standard-theme-carbon-ads)
+Weitere Informationen findest du unter [Standard-Theme: Carbon Ads](./Standard-theme-carbon-ads)
 
 ## docFooter
 
 - Type: `DocFooter`
 
-Can be used to customize text appearing above previous and next links. Helpful if not writing docs in English. Also can be used to disable prev/next links globally. Wenn du want to selectively enable/disable prev/next links, you can use [frontmatter](./Standard-theme-prev-next-links).
+Kann verwendet werden, um den Text über den Links zur vorherigen und nächsten Seite anzupassen. Dies ist hilfreich, wenn die Dokumentation nicht auf Englisch verfasst ist. Außerdem können die Links global deaktiviert werden. Wenn du die Links gezielt aktivieren oder deaktivieren möchtest, kannst du [frontmatter](./Standard-theme-prev-next-links).
 
 ```ts
 export default {
@@ -437,42 +437,42 @@ export interface DocFooter {
 - Type: `string`
 - Default: `Appearance`
 
-Can be used to customize the dark mode switch label. Dies label is only displayed in the mobile view.
+Kann verwendet werden, um die Beschriftung des Dunkelmodus-Schalters anzupassen. Diese Beschriftung wird nur in der mobilen Ansicht angezeigt.
 
 ## lightModeSwitchTitle
 
 - Type: `string`
 - Default: `Switch to light theme`
 
-Can be used to customize the light mode switch title that appears on hovering.
+Kann verwendet werden, um den Titel des Hellmodus-Schalters anzupassen, der beim Darüberfahren angezeigt wird.
 
 ## darkModeSwitchTitle
 
 - Type: `string`
 - Default: `Switch to dark theme`
 
-Can be used to customize the dark mode switch title that appears on hovering.
+Kann verwendet werden, um den Titel des Dunkelmodus-Schalters anzupassen, der beim Darüberfahren angezeigt wird.
 
 ## sidebarMenuLabel
 
 - Type: `string`
 - Default: `Menu`
 
-Can be used to customize the sidebar menu label. Dies label is only displayed in the mobile view.
+Kann verwendet werden, um die Beschriftung des Seitenleistenmenüs anzupassen. Diese Beschriftung wird nur in der mobilen Ansicht angezeigt.
 
 ## returnToTopLabel
 
 - Type: `string`
 - Default: `Return to top`
 
-Can be used to customize the label of the zurückgeben to top button. Dies label is only displayed in the mobile view.
+Kann verwendet werden, um die Beschriftung der Schaltfläche zum Zurückkehren nach oben anzupassen. Diese Beschriftung wird nur in der mobilen Ansicht angezeigt.
 
 ## langMenuLabel
 
 - Type: `string`
 - Default: `Change language`
 
-Can be used to customize the aria-label of the language toggle button in navbar. Dies is only used if you're using [i18n](../guide/i18n).
+Kann verwendet werden, um das aria-label der Sprachumschalt-Schaltfläche in der Navigationsleiste anzupassen. Dies wird nur bei Verwendung von [i18n] genutzt.(../guide/i18n).
 
 ## navMenuLabel
 
@@ -505,14 +505,14 @@ Can be used to customize the label of the skip to content link. Dies link is sho
 ## externalLinkIcon
 
 - Type: `boolean`
-- Default: `falsch`
+- Default: `false`
 
 Whether to show an external link icon next to external links in markdown.
 
 ## gradedContainers
 
 - Type: `boolean`
-- Default: `falsch`
+- Default: `false`
 
 Whether to color [custom containers](../guide/markdown#custom-containers), [GitHub-flavored alerts](../guide/markdown#github-flavored-alerts), and badges on a graded severity scale — danger red, warning orange, caution yellow. By Standard, colors match GitHub's alerts, where caution shares danger's red and warning is yellow.
 

From 03e5800b207f6bedadb9e8f7575b3b7e8463d97c Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:01:02 +0200
Subject: [PATCH 133/199] docs(de): finish German guide translation

---
 docs/de/guide/i18n.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/i18n.md b/docs/de/guide/i18n.md
index 557d70840..1e58dff46 100644
--- a/docs/de/guide/i18n.md
+++ b/docs/de/guide/i18n.md
@@ -1,10 +1,10 @@
 ---
-description: Set up internationalization (i18n) in VitePress to Unterstützung mulTipple languages for your site.
+description: Richte Internationalisierung (i18n) in VitePress ein, um mehrere Sprachen für deine Website zu unterstützen.
 ---
 
 # Internationalisierung
 
-To use the built-in i18n features, one needs to create a directory structure as follows:
+Um die integrierten i18n-Funktionen zu verwenden, musst du eine Verzeichnisstruktur wie folgt erstellen:
 
 ```
 docs/
@@ -55,11 +55,11 @@ interface LocaleSpecificConfig<ThemeConfig = any> {
 
 Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-Theme.d.ts) interface for details on eigeneizing the placeholder texts of the Standard-Theme. Don't override `ThemeConfig.algolia` or `ThemeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-Theme-search#algolia-search-i18n) for Verwendung multilingual search.
 
-**Pro Tipp:** Config Datei can be stored at `docs/.vitepress/config/index.ts` too. It might help you organize stuff by creating a Konfiguration Datei per locale and dann merge and export them von `index.ts`.
+**Pro Tipp:** Die Konfigurationsdatei kann auch unter `docs/.vitepress/config/index.ts` gespeichert werden. Das kann bei der Organisation helfen, indem du eine Konfigurationsdatei pro Sprache erstellst und sie anschließend in `index.ts` zusammenführst und exportierst.
 
-## Per-locale Markdown Strings
+## Markdown-Zeichenketten pro Sprache
 
-Strings baked in Seites by the markdown renderer - the default titles of [eigene containers](./markdown#eigene-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - can be overridden per locale mit the `markdown` key of a locale entry:
+Vom Markdown-Renderer in Seiten eingebettete Zeichenketten - the default titles of [eigene containers](./markdown#eigene-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - können pro Sprache über den Schlüssel `markdown` eines Spracheintrags überschrieben werden:
 
 ```ts [docs/.vitepress/config.ts]
 import { defineConfig } from 'vitepress'
@@ -86,9 +86,9 @@ export default defineConfig({
 })
 ```
 
-Values falle back to the root-level `markdown` Options wenn a locale leaves them unset. Locale entries can nur override the titles of containers registered at the root level - registering new containers per locale is not supported. Also Hinweis dass since the markdown renderer is erstellt once for the whole site, these can nur be declared in the main config Datei, not in additional configs.
+Werte fallen auf die `markdown`-Optionen der obersten Ebene zurück, wenn eine Sprache sie nicht festlegt. Spracheinträge können nur die Titel von Containern überschreiben, die auf oberster Ebene registriert wurden. Das Registrieren neuer Container pro Sprache wird nicht unterstützt. Beachte außerdem, dass der Markdown-Renderer einmal für die gesamte Website erstellt wird. Diese Optionen können daher nur in der Hauptkonfigurationsdatei, nicht in zusätzlichen Konfigurationen, festgelegt werden.
 
-## Separate directory for jede locale
+## Separates Verzeichnis für jede Sprache
 
 The folgende is a perfectly fine structure:
 
@@ -102,7 +102,7 @@ docs/
    ├─ foo.md
 ```
 
-However, VitePress won't redirect `/` to `/en/` standardmäßig. You'll need to configure your server for that. Zum Beispiel, on Netlify, du kannst add a `docs/public/_redirects` Datei like this:
+VitePress leitet `/` jedoch standardmäßig nicht nach `/en/` weiter. Dafür musst du deinen Server entsprechend konfigurieren. Bei Netlify kannst du beispielsweise eine Datei `docs/public/_redirects` wie diese hinzufügen:
 
 ```
 /*  /es/:splat  302  Language=es
@@ -110,7 +110,7 @@ However, VitePress won't redirect `/` to `/en/` standardmäßig. You'll need to
 /*  /en/:splat  302
 ```
 
-**Pro Tipp:** Wenn Verwendung the above approach, du kannst use `nf_lang` cookie to persist user's language choice:
+**Pro Tipp:** Wenn du den obigen Ansatz verwendest, kannst du das Cookie `nf_lang` verwenden, um die Sprachauswahl des Benutzers zu speichern:
 
 ```ts [docs/.vitepress/theme/index.ts]
 import DefaultTheme from 'vitepress/theme'
@@ -141,7 +141,7 @@ watchEffect(() => {
 </template>
 ```
 
-## RTL Support
+## RTL-Unterstützung
 
 For right-to-left languages, set `dir: 'rtl'` in the config. The Standard-Theme is laid out mit [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_Werts), so the layout, the navigation and directional icons follow the dokumentieren direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
 

From 1d46e5f39747f5f8b636a5f0bd54886d4a8bbb91 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:01:04 +0200
Subject: [PATCH 134/199] docs(de): finish German guide translation

---
 docs/de/guide/what-is-vitepress.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index b5991c249..97f592668 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -20,7 +20,7 @@ Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./gettin
 
 - **Blogs, Portfolios und Marketing-Websites**
 
-  VitePress supports [fully cuszumized themes](./cuszum-theme), with the developer experience of a stundard Vite + Vue application. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [load data](./data-loading) (local or remote) und [dynamically generate routes](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
+  VitePress supports [fully cuszumized themes](./cuszum-theme), mit der Entwicklererfahrung einer normalen Vite- und Vue-Anwendung. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [Daten laden](./data-loading) (lokal oder entfernt) und [dynamische Routen erzeugen](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
 
   Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
 
@@ -30,9 +30,9 @@ VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mi
 
 - **[Vite-Powered:](https://vite.dev/)** sofortiger Serverstart, wobei Änderungen ohne Neuladen der Seite unmittelbar (<100 ms) sichtbar werden.
 
-- **[Built-in Markdown Extensions:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
+- **[Integrierte Markdown-Erweiterungen:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
 
-- **[Vue-Enhanced Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks zu Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
+- **[Vue-erweitertes Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks zu Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
 
 ## Leistung
 
@@ -44,7 +44,7 @@ Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollst
 
 - **Schnelle Navigation nach dem Laden**
 
-  More importantly, the SPA model leads zu better user experience **after** the initial load. Subsequent navigation within the site will no longer cause a full page reload. Instead, the incoming page's content will be fetched und dynamically updated. VitePress also auzumatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
+  More importantly, the SPA model leads zu better user experience **after** the initial load. Bei der weiteren Navigation innerhalb der Website wird die Seite nicht mehr vollständig neu geladen. Stattdessen wird der Inhalt der Zielseite abgerufen und dynamisch aktualisiert. VitePress also auzumatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
 
 - **Interaktivität ohne Nachteile**
 
@@ -52,7 +52,7 @@ Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollst
 
 ## Und was ist mit VuePress?
 
-VitePress is the spiritual successor of VuePress 1. The original VuePress 1 was based on Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible cuszumization API.
+VitePress ist der Nachfolger von VuePress 1. Das ursprüngliche VuePress 1 basierte auf Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible cuszumization API.
 
 The API difference between VitePress und VuePress 1 mostly lies in theming und cuszumization. If you are using VuePress 1 with the default theme, it should be relatively straightforward zu migrate zu VitePress.
 

From 1065b9bbe89780ef1974df3a20c3ee12cb1ed4f6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:01:35 +0200
Subject: [PATCH 135/199] docs(de): fix code examples in Markdown guide

---
 docs/de/guide/markdown.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/guide/markdown.md b/docs/de/guide/markdown.md
index 36e10117e..3ec5c9f51 100644
--- a/docs/de/guide/markdown.md
+++ b/docs/de/guide/markdown.md
@@ -513,8 +513,8 @@ export default {
 
 ```js{4}
 export default {
-  Daten () {
-    zurückgeben {
+  data () {
+    return {
       msg: 'Highlighted!'
     }
   }
@@ -549,8 +549,8 @@ export default { // Highlighted
 
 ```js{1,4,6-8}
 export default { // Highlighted
-  Daten () {
-    zurückgeben {
+  data () {
+    return {
       msg: `Highlighted!
       This line isn't highlighted,
       but this and the next 2 are.`,
@@ -581,8 +581,8 @@ export default {
 
 ```js
 export default {
-  Daten() {
-    zurückgeben {
+  data() {
+    return {
       msg: 'Highlighted!' // [!code highlight]
     }
   }
@@ -613,8 +613,8 @@ export default {
 
 ```js
 export default {
-  Daten() {
-    zurückgeben {
+  data() {
+    return {
       msg: 'Focused!' // [!code focus]
     }
   }
@@ -644,8 +644,8 @@ export default {
 
 ```js
 export default {
-  Daten () {
-    zurückgeben {
+  data () {
+    return {
       msg: 'Removed' // [!code --]
       msg: 'Added' // [!code ++]
     }
@@ -676,8 +676,8 @@ export default {
 
 ```js
 export default {
-  Daten() {
-    zurückgeben {
+  data() {
+    return {
       msg: 'Error', // [!code error]
       msg: 'Warnung' // [!code warning]
     }

From 41460f20f8fe1e8686c54f59a1d50b6db2593bbd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:04:50 +0200
Subject: [PATCH 136/199] docs(de): remove remaining Denglish

---
 docs/de/guide/migration-from-vuepress.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/migration-from-vuepress.md b/docs/de/guide/migration-from-vuepress.md
index da390deed..732554154 100644
--- a/docs/de/guide/migration-from-vuepress.md
+++ b/docs/de/guide/migration-from-vuepress.md
@@ -4,15 +4,15 @@
 
 ### Seitenleiste
 
-The sidebar is no longer automatisch populated from frontmatter. Du kannst [read the frontmatter yourself](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225) to dynamically populate the sidebar. [Additional utilities for this](https://github.com/vuejs/vitepress/issues/96) may be provided in the future.
+Die Seitenleiste wird nicht mehr automatisch aus dem Frontmatter erzeugt. Du kannst [das Frontmatter selbst auslesen](https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225), um die Seitenleiste dynamisch zu erzeugen. [Zusätzliche Hilfsfunktionen dafür](https://github.com/vuejs/vitepress/issues/96) könnten in Zukunft bereitgestellt werden.
 
 ## Markdown
 
 ### Bilder
 
-Unlike VuePress, VitePress handles [`base`](./asset-handling#base-url) of your config automatisch when you use static image.
+Anders als VuePress verarbeitet VitePress [`base`](./asset-handling#base-url) aus deiner Konfiguration bei der Verwendung statischer Bilder automatisch.
 
-Hence, now you can render images without `img` tag.
+Daher kannst du Bilder jetzt ohne ein `img`-Tag rendern.
 
 ```diff
 - <img :src="$withBase('/foo.png')" alt="foo">
@@ -20,11 +20,11 @@ Hence, now you can render images without `img` tag.
 ```
 
 ::: warning
-For dynamic images you still need `withBase` as shown in [Base URL guide](./asset-handling#base-url).
+Für dynamische Bilder benötigst du weiterhin `withBase`, wie in der [Anleitung zur Basis-URL](./asset-handling#base-url) gezeigt.
 :::
 
-Use `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>` regex to find and replace it with `![$2]($1)` to replace all the images with `![](...)` syntax.
+Verwende den regulären Ausdruck `<img.*withBase\('(.*)'\).*alt="([^"]*)".*>`, um die entsprechenden Stellen zu finden und durch `![$2]($1)` zu ersetzen. So werden alle Bilder in die `![](...)`-Syntax umgewandelt.
 
 ---
 
-more to follow...
+Weitere Inhalte folgen...

From 096a764be2f617cd62b6c56b2ef8a4481dcee39f Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:04:52 +0200
Subject: [PATCH 137/199] docs(de): remove remaining Denglish

---
 docs/de/guide/mpa-mode.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/guide/mpa-mode.md b/docs/de/guide/mpa-mode.md
index 4f11b5ccd..b061b5ef5 100644
--- a/docs/de/guide/mpa-mode.md
+++ b/docs/de/guide/mpa-mode.md
@@ -1,16 +1,16 @@
 ---
-description: MPA (Multi-Seite Application) mode in VitePress for zero-JavaScript pages with better initial performance.
+description: MPA-Modus (Multi-Page Application) in VitePress für Seiten ohne JavaScript mit besserer anfänglicher Performance.
 ---
 
 # MPA-Modus <Badge type="warning" text="experimental" />
 
-MPA (Multi-Seite Application) mode can be enabled via the command line via `vitepress build --mpa`, or via config through the `mpa: true` option.
+Der MPA-Modus (Multi-Page Application) kann über die Kommandozeile mit `vitepress build --mpa` oder über die Konfiguration mit der Option `mpa: true` aktiviert werden.
 
-In MPA mode, all pages are rendered without any JavaScript included by default. As a result, the production site will likely have a better initial visit performance score from audit tools.
+Im MPA-Modus werden standardmäßig alle Seiten ohne eingebundenes JavaScript gerendert. Dadurch erreicht die Produktionswebsite bei der ersten Ansicht wahrscheinlich bessere Performance-Werte in Prüfwerkzeugen.
 
-However, due to the absence of SPA navigation, cross-page links will lead to full page reloads. Post-laden navigations in MPA mode will not feel as instant as in SPA mode.
+Da die SPA-Navigation fehlt, führen Links zwischen Seiten jedoch zu vollständigen Seitenneuladungen. Navigationen nach dem Laden fühlen sich im MPA-Modus daher nicht so unmittelbar an wie im SPA-Modus.
 
-Also note that no-JS-by-default means you are essentially Verwendung Vue purely as a server-side templating language. No event handlers will be attached in the browser, so there will be no interactivity. To laden client-side JavaScript, you will need to use the special `<script client>` tag:
+Beachte außerdem, dass „standardmäßig kein JavaScript“ bedeutet, dass Vue im Wesentlichen nur als serverseitige Template-Sprache verwendet wird. Im Browser werden keine Event-Handler registriert, sodass keine Interaktivität vorhanden ist. Um clientseitiges JavaScript zu laden, musst du das spezielle `<script client>`-Tag verwenden:
 
 ```html
 <script client>
@@ -22,6 +22,6 @@ document.querySelector('h1').addEventListener('click', () => {
 # Hello
 ```
 
-`<script client>` is a VitePress-only feature, not a Vue feature. It works in both `.md` and `.vue` files, but only in MPA mode. Client scripts in all theme Komponenten will be bundled together, while client script for a specific page will be split for that page only.
+`<script client>` ist eine reine VitePress-Funktion und keine Vue-Funktion. Sie funktioniert sowohl in `.md`- als auch in `.vue`-Dateien, aber nur im MPA-Modus. Client-Skripte aller Theme-Komponenten werden gemeinsam gebündelt, während das Client-Skript einer bestimmten Seite nur für diese Seite aufgeteilt wird.
 
-Beachte, dass `<script client>` is **not evaluated as Vue Komponente code**: it's processed as a plain JavaScript module. For this reason, MPA mode should only be verwendet if your site requires absolutely minimal client-side interactivity.
+Beachte, dass `<script client>` **nicht als Vue-Komponentencode ausgewertet wird**: Es wird als gewöhnliches JavaScript-Modul verarbeitet. Deshalb solltest du den MPA-Modus nur verwenden, wenn deine Website unbedingt minimale clientseitige Interaktivität benötigt.

From ac41f6e637f9a46c6b34b0faf78859e1d4f2fdcc Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:04:55 +0200
Subject: [PATCH 138/199] docs(de): remove remaining Denglish

---
 docs/de/guide/sitemap-generation.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/sitemap-generation.md b/docs/de/guide/sitemap-generation.md
index 8c2a73871..b38a4395b 100644
--- a/docs/de/guide/sitemap-generation.md
+++ b/docs/de/guide/sitemap-generation.md
@@ -1,5 +1,5 @@
 ---
-description: a sitemap.xml file for your VitePress site to improve search engine discoverability.
+description: Eine sitemap.xml-Datei für deine VitePress-Website zur besseren Auffindbarkeit durch Suchmaschinen.
 ---
 
 # Sitemap-Generierung
@@ -14,11 +14,11 @@ export default {
 }
 ```
 
-Damit deine `sitemap.xml`-Datei `<lastmod>`-Tags enthält, kannst du die [`lastUpdated`](../reference/default-theme-last-updated) option.
+Damit deine `sitemap.xml`-Datei `<lastmod>`-Tags enthält, kannst du die Option [`lastUpdated`](../reference/default-theme-last-updated) aktivieren.
 
 ## Optionen
 
-Sitemap wird unterstützt durch the [`sitemap`](https://www.npmjs.com/package/sitemap) module. Du kannst pass any options supported by it to the `sitemap` option in your config file. Diese werden direkt an the `SitemapStream` constructor. Siehe die [`sitemap` documentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) für weitere Details. Beispiel:
+Die Sitemap wird durch das [`sitemap`](https://www.npmjs.com/package/sitemap)-Modul unterstützt. Du kannst alle von ihm unterstützten Optionen an die `sitemap`-Option deiner Konfigurationsdatei übergeben. Diese werden direkt an den `SitemapStream`-Konstruktor übergeben. Siehe die [`sitemap`-Dokumentation](https://www.npmjs.com/package/sitemap#options-you-can-pass) für weitere Details. Beispiel:
 
 ```ts
 export default {
@@ -29,7 +29,7 @@ export default {
 }
 ```
 
-Wenn du're Verwendung `base` in your config, you should append it to the `hostname` option:
+Wenn du `base` in deiner Konfiguration verwendest, solltest du den Wert an die Option `hostname` anhängen:
 
 ```ts
 export default {
@@ -42,14 +42,14 @@ export default {
 
 ## `transformItems` Hook
 
-Du kannst use the `sitemap.transformItems` Hook verwenden, um die Sitemap-Einträge vor dem Schreiben in die `sitemap.xml` file. This hook is genannt with an array of sitemap items und erwartet, dass ein Array von Sitemap-Einträgen zurückgegeben wird. Beispiel:
+Du kannst den `sitemap.transformItems`-Hook verwenden, um die Sitemap-Einträge vor dem Schreiben in die Datei `sitemap.xml` zu verändern. Dieser Hook wird mit einem Array von Sitemap-Einträgen aufgerufen und erwartet, dass ein Array von Sitemap-Einträgen zurückgegeben wird. Beispiel:
 
 ```ts
 export default {
   sitemap: {
     hostname: 'https://example.com',
     transformItems: (items) => {
-      // add new items or modify/filter existing items
+      // Neue Einträge hinzufügen oder vorhandene Einträge ändern/filtern
       items.push({
         url: '/extra-page',
         changefreq: 'monthly',

From dc739e818435e86a3ac2c7a7626ac7ce74e50c74 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:04:57 +0200
Subject: [PATCH 139/199] docs(de): remove remaining Denglish

---
 docs/de/guide/ssr-compat.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
index 0c59df503..224ac883f 100644
--- a/docs/de/guide/ssr-compat.md
+++ b/docs/de/guide/ssr-compat.md
@@ -1,17 +1,17 @@
 ---
 outline: deep
-description: your VitePress theme Komponenten and custom code are compatible with server-side rendering.
+description: Sicherstellen, dass deine VitePress-Theme-Komponenten und dein eigener Code mit serverseitigem Rendering kompatibel sind.
 ---
 
 # SSR-Kompatibilität
 
-VitePress pre-renders the app in Node.js during the production build, Verwendung Vue's Server-Side Rendering (SSR) capabilities. Das bedeutet all custom code in theme Komponenten are subject to SSR-Kompatibilität.
+VitePress rendert die Anwendung während des Produktions-Builds in Node.js vor und verwendet dabei die Server-Side-Rendering-Funktionen (SSR) von Vue. Das bedeutet, dass eigener Code in Theme-Komponenten SSR-kompatibel sein muss.
 
-Der [SSR-Abschnitt in der offiziellen Vue-Dokumentation](https://vuejs.org/guide/scaling-up/ssr.html) stellt bereit more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. Als Faustregel gilt, dass Browser-/DOM-APIs nur in `beforeMount` or `mounted` hooks of Vue Komponenten.
+Der [SSR-Abschnitt in der offiziellen Vue-Dokumentation](https://vuejs.org/guide/scaling-up/ssr.html) bietet weitere Informationen zu SSR, zum Verhältnis zwischen SSR und SSG sowie zu wichtigen Hinweisen für SSR-kompatiblen Code. Als Faustregel gilt, dass Browser-/DOM-APIs nur in `beforeMount`- oder `mounted`-Hooks von Vue-Komponenten verwendet werden sollten.
 
 ## `<ClientOnly>`
 
-Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for example, contain custom directives), kannst du sie in die integrierte `<ClientOnly>` Komponente:
+Wenn du nicht SSR-kompatible Komponenten verwendest oder demonstrierst (beispielsweise solche mit eigenen Direktiven), kannst du sie in die integrierte `<ClientOnly>`-Komponente einschließen:
 
 ```md
 <ClientOnly>
@@ -21,7 +21,7 @@ Wenn du are Verwendung or demoing Komponenten die nicht SSR-kompatibel sind (for
 
 ## Bibliotheken, die beim Import auf Browser-APIs zugreifen
 
-Some Komponenten or libraries access browser APIs **on import**. Um Code zu verwenden, der beim Import eine Browserumgebung voraussetzt, musst du ihn dynamisch importieren.
+Einige Komponenten oder Bibliotheken greifen **beim Import** auf Browser-APIs zu. Um Code zu verwenden, der beim Import eine Browserumgebung voraussetzt, musst du ihn dynamisch importieren.
 
 ### Import in einem Mounted-Hook
 
@@ -39,7 +39,7 @@ onMounted(() => {
 
 ### Bedingter Import
 
-Du kannst also conditionally import a dependency Verwendung the `import.meta.env.SSR` flag (part of [Vite env variables](https://vite.dev/guide/env-and-mode.html#env-variables)):
+Du kannst eine Abhängigkeit auch bedingt mithilfe des Flags `import.meta.env.SSR` importieren, das zu den [Vite-Umgebungsvariablen](https://vite.dev/guide/env-and-mode.html#env-variables) gehört:
 
 ```js
 if (!import.meta.env.SSR) {
@@ -49,7 +49,7 @@ if (!import.meta.env.SSR) {
 }
 ```
 
-Da [`Theme.enhanceApp`](./custom-theme#theme-interface) asynchron sein kann, kannst du Vue-Plugins bedingt importieren und registrieren that access browser APIs on import:
+Da [`Theme.enhanceApp`](./custom-theme#theme-interface) asynchron sein kann, kannst du Vue-Plugins, die beim Import auf Browser-APIs zugreifen, bedingt importieren und registrieren:
 
 ```js [.vitepress/theme/index.js]
 /** @type {import('vitepress').Theme} */
@@ -81,7 +81,7 @@ export default {
 
 ### `defineClientComponent`
 
-VitePress stellt bereit a convenience helper for importing Vue Komponenten that access browser APIs on import.
+VitePress stellt einen praktischen Helper zum Importieren von Vue-Komponenten bereit, die beim Import auf Browser-APIs zugreifen.
 
 ```vue
 <script setup>
@@ -97,7 +97,7 @@ const ClientComp = defineClientComponent(() => {
 </template>
 ```
 
-Du kannst also pass props/children/slots to the target Komponente:
+Du kannst der Zielkomponente auch Props, Children und Slots übergeben:
 
 ```vue
 <script setup>
@@ -132,4 +132,4 @@ const ClientComp = defineClientComponent(
 </template>
 ```
 
-The target Komponente will only be imported in the mounted hook of the wrapper Komponente.
+Die Zielkomponente wird erst im `mounted`-Hook der Wrapper-Komponente importiert.

From b2c007ec61bc3ff8397ed7ce856ffc0b6b27168c Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:05:00 +0200
Subject: [PATCH 140/199] docs(de): remove remaining Denglish

---
 docs/de/reference/default-theme-team-page.md | 40 ++++++++++----------
 1 file changed, 20 insertions(+), 20 deletions(-)

diff --git a/docs/de/reference/default-theme-team-page.md b/docs/de/reference/default-theme-team-page.md
index 8deadf4de..9de6c114d 100644
--- a/docs/de/reference/default-theme-team-page.md
+++ b/docs/de/reference/default-theme-team-page.md
@@ -1,5 +1,5 @@
 ---
-description: Create team pages with member profiles using VitePress built-in team components.
+description: Erstelle Teamseiten mit Mitgliederprofilen mithilfe der integrierten Team-Komponenten von VitePress.
 ---
 
 <script setup>
@@ -29,11 +29,11 @@ const members = [
 
 # Teamseite
 
-Wenn du would like to introduce your team, you may use Team components to construct the Teamseite. There are two ways of using these components. One is to embed it in doc page, and another is to create a full Teamseite.
+Wenn du dein Team vorstellen möchtest, kannst du Team-Komponenten verwenden, um eine Teamseite zu erstellen. Es gibt zwei Möglichkeiten: Du kannst sie in eine Dokumentationsseite einbetten oder eine vollständige Teamseite erstellen.
 
-## Show team members in a page
+## Teammitglieder auf einer Seite anzeigen
 
-Du kannst use `<VPTeamMembers>` component exposed from `vitepress/theme` to display a list of team members on any page.
+Du kannst die von `vitepress/theme` bereitgestellte Komponente `<VPTeamMembers>` verwenden, um auf jeder Seite eine Liste von Teammitgliedern anzuzeigen.
 
 ```html
 <script setup>
@@ -55,26 +55,26 @@ const members = [
 
 # Our Team
 
-Say hello to our awesome team.
+Lerne unser großartiges Team kennen.
 
 <VPTeamMembers size="small" :members />
 ```
 
-The above will display a team member in card looking element. It should display something similar to below.
+Der obige Code zeigt ein Teammitglied in einem kartenähnlichen Element an. Das Ergebnis sollte ungefähr wie folgt aussehen.
 
 <VPTeamMembers size="small" :members />
 
-`<VPTeamMembers>` component comes in 2 different sizes, `small` and `medium`. While it boils down to your preference, usually `small` size should fit better when used in doc page. Also, you may add more properties to each member such as adding "description" or "sponsor" button. Mehr erfahren about it in [`<VPTeamMembers>`](#vpteammembers).
+Die Komponente `<VPTeamMembers>` gibt es in zwei Größen: `small` und `medium`. Welche du verwendest, hängt von deinen Anforderungen ab; auf Dokumentationsseiten passt `small` normalerweise besser. Du kannst jedem Mitglied außerdem weitere Eigenschaften wie eine `description` oder eine `sponsor`-Schaltfläche hinzufügen. Weitere Informationen findest du unter [`<VPTeamMembers>`](#vpteammembers).
 
-Embedding team members in doc page is good for small size team where having dedicated full team page might be too much, or introducing partial members as a reference to documentation context.
+Das Einbetten von Teammitgliedern in eine Dokumentationsseite eignet sich für kleine Teams oder wenn nur einzelne Mitglieder im Zusammenhang mit der Dokumentation vorgestellt werden sollen.
 
-Wenn du have large number of members, or simply would like to have more space to show team members, consider [creating a full team page](#create-a-full-team-page).
+Wenn du viele Mitglieder hast oder einfach mehr Platz für ihre Darstellung benötigst, kannst du [eine vollständige Teamseite erstellen](#create-a-full-team-page).
 
 ## Create a full Teamseite
 
-Instead of adding team members to doc page, you may also create a full Teamseite, similar to how you can create a custom [Startseite](./default-theme-home-page).
+Statt Teammitglieder in eine Dokumentationsseite einzubetten, kannst du auch eine vollständige Teamseite erstellen, ähnlich wie bei einer eigenen [Startseite](./default-theme-home-page).
 
-To create a team page, first, create a new md file. The file name doesn't matter, but here lets call it `team.md`. In this file, set frontmatter option `layout: page`, and then you may compose your page structure using `TeamPage` components.
+Erstelle zunächst eine neue Markdown-Datei. Der Dateiname spielt keine Rolle; hier nennen wir sie `team.md`. Setze darin die Frontmatter-Option `layout: page` und baue anschließend die Seitenstruktur mit `TeamPage`-Komponenten auf.
 
 ```html
 ---
@@ -115,17 +115,17 @@ const members = [
 </VPTeamPage>
 ```
 
-When creating a full team page, remember to wrap all components with `<VPTeamPage>` component. This component will ensure all nested team related components get the proper layout structure like spacings.
+Bei einer vollständigen Teamseite musst du alle Komponenten mit der Komponente `<VPTeamPage>` umschließen. Sie sorgt dafür, dass alle verschachtelten Team-Komponenten die passende Layout-Struktur und Abstände erhalten.
 
-`<VPPageTitle>` component adds the page title section. The title being `<h1>` heading. Use `#title` and `#lead` slot to document about your team.
+Die Komponente `<VPPageTitle>` fügt den Seitentitelbereich hinzu. Der Titel ist eine `<h1>`-Überschrift. Verwende die Slots `#title` und `#lead`, um dein Team vorzustellen.
 
-`<VPMembers>` works as same as when used in a doc page. It will display list of members.
+`<VPMembers>` funktioniert genauso wie auf einer Dokumentationsseite und zeigt eine Liste von Mitgliedern an.
 
-### Add sections to divide team members
+### Abschnitte zur Aufteilung der Teammitglieder hinzufügen
 
-Du kannst add "sections" to the team page. Zum Beispiel, you may have different types of team members such as Core Team Members and Community Partners. Du kannst divide these members into sections to better explain the roles of each group.
+Du kannst der Teamseite „Abschnitte“ hinzufügen. Zum Beispiel kannst du verschiedene Arten von Teammitgliedern wie Kernteammitglieder und Community-Partner haben. Mit Abschnitten kannst du die Rollen der einzelnen Gruppen besser erläutern.
 
-To do so, add `<VPTeamPageSection>` component to the `team.md` file we created previously.
+Füge dazu die Komponente `<VPTeamPageSection>` in die zuvor erstellte Datei `team.md` ein.
 
 ```html
 ---
@@ -159,13 +159,13 @@ const partners = [...]
 </VPTeamPage>
 ```
 
-The `<VPTeamPageSection>` component can have `#title` and `#lead` slot similar to `VPTeamPageTitle` component, and also `#members` slot for displaying team members.
+Die Komponente `<VPTeamPageSection>` kann wie `VPTeamPageTitle` die Slots `#title` und `#lead` sowie zusätzlich den Slot `#members` zur Anzeige von Teammitgliedern enthalten.
 
-Remember to put in `<VPTeamMembers>` component within `#members` slot.
+Denke daran, die Komponente `<VPTeamMembers>` innerhalb des Slots `#members` einzufügen.
 
 ## `<VPTeamMembers>`
 
-The `<VPTeamMembers>` component displays a given list of members.
+Die Komponente `<VPTeamMembers>` zeigt eine übergebene Liste von Mitgliedern an.
 
 ```html
 <VPTeamMembers

From a6a752b9d81ae3f0c723e630a279f8e5afd6d435 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:05:02 +0200
Subject: [PATCH 141/199] docs(de): remove remaining Denglish

---
 docs/de/guide/routing.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 2f1f4f22e..643d5125c 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -68,7 +68,7 @@ Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `sr
 ```
 .                          # Projektstammverzeichnis
 ├─ .vitepress              # Konfigurationsverzeichnis
-└─ src                     # source dir
+└─ src                     # Quellverzeichnis
    ├─ getting-started.md
    └─ index.md
 ```
@@ -112,7 +112,7 @@ Wenn du auf eine Seite deiner Website verlinken möchtest, die nicht von VitePre
 
 ::: tip Hinweis
 
-Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` in the link (resolved relative to the current page by the browser).
+Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf eine Seite außerhalb deines Basispfads verlinken möchtest, benötigst du daher beispielsweise `../../pure.html` im Link (vom Browser relativ zur aktuellen Seite aufgelöst).
 
 Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 
@@ -132,10 +132,10 @@ Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` en
 
 Einige Server oder Hosting-Plattformen (beispielsweise Netlify, Vercel und GitHub Pages) können eine URL wie `/foo` ohne Weiterleitung auf `/foo.html` abbilden, wenn diese Datei existiert:
 
-- Netlify and GitHub Seiten support this by default.
-- Vercel requires enabling the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
+- Netlify und GitHub Pages unterstützen dies standardmäßig.
+- Vercel erfordert die Aktivierung von the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) config option so that:
+Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) Konfigurationsoption so that:
 
 - Links zwischen Seiten werden ohne die Erweiterung `.html` erzeugt.
 - Wenn der aktuelle Pfad mit `.html` endet, führt der Router eine clientseitige Weiterleitung zum Pfad ohne Erweiterung durch.
@@ -177,7 +177,7 @@ packages/pkg-b/src/index.md  -->  /pkg-b/index.html
 packages/pkg-b/src/bar.md    -->  /pkg-b/bar.html
 ```
 
-Du kannst dies durch Konfiguration der the [`rewrites`](../reference/site-config#rewrites) option like this:
+Du kannst dies durch Konfiguration der [`rewrites`](../reference/site-config#rewrites) option like this:
 
 ```ts [.vitepress/config.js]
 export default {
@@ -190,7 +190,7 @@ export default {
 }
 ```
 
-Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. In the above example, it would be verbose to list all the paths if you have many packages. Da alle dieselbe Dateistruktur haben, kannst du die Konfiguration so vereinfachen:
+Die Option `rewrites` unterstützt außerdem dynamische Routenparameter. Im obigen Beispiel wäre es bei vielen Paketen aufwendig, alle Pfade aufzulisten. Da alle dieselbe Dateistruktur haben, kannst du die Konfiguration so vereinfachen:
 
 ```ts
 export default {
@@ -227,7 +227,7 @@ Du kannst mit einer einzigen Markdown-Datei und dynamischen Daten viele Seiten e
 
 ### Pfad-Loader-Datei
 
-Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. For `packages/[pkg].md`, we will need `packages/[pkg].paths.js` (`.ts` is also supported):
+Da VitePress ein statischer Website-Generator ist, müssen die möglichen Seitenpfade zur Build-Zeit feststehen. Daher **muss** eine dynamische Routenseite von einer **Paths-Loader-Datei** begleitet werden. Für `packages/[pkg].md` benötigen wir `packages/[pkg].paths.js` (`.ts` wird ebenfalls unterstützt):
 
 ```
 .
@@ -396,14 +396,14 @@ export default {
 
 Die Option `watch` funktioniert genauso wie bei [Data Loadern](./Daten-loading#Daten-from-local-files):
 
-- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) to match files
+- Akzeptiert [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax), um Dateien zu finden
 - Muster sind relativ zur `.paths.js`-Datei selbst
 - Änderungen an überwachten Dateien lösen während der Entwicklung eine Seitengenerierung und HMR aus
 - In Produktions-Builds werden alle Seiten unabhängig von der `watch`-Konfiguration einmal erzeugt
 
 ### Auf Parameter in Seiten zugreifen
 
-Du kannst die Parameter verwenden, um jeder Seite zusätzliche Daten zu übergeben. The Markdown route file can access the current page params in Vue expressions via the `$params` global property:
+Du kannst die Parameter verwenden, um jeder Seite zusätzliche Daten zu übergeben. Die Markdown-Routendatei kann über die globale Eigenschaft `$params` in Vue-Ausdrücken auf die Parameter der aktuellen Seite zugreifen:
 
 ```md
 - package name: {{ $params.pkg }}
@@ -427,7 +427,7 @@ console.log(params.value)
 
 An die Seite übergebene Parameter werden in der JavaScript-Nutzlast des Clients serialisiert. Daher solltest du vermeiden, große Datenmengen als Parameter zu übergeben, beispielsweise rohes Markdown oder HTML aus einem entfernten CMS.
 
-Stattdessen kannst du solche Inhalte jeder Seite über die Eigenschaft `content` des jeweiligen Pfadobjekts übergeben: `content` property on each path object:
+Stattdessen kannst du solche Inhalte über die Eigenschaft `content` des jeweiligen Pfadobjekts an jede Seite übergeben:
 
 ```js
 export default {

From b742d62098de38d5999b7164dfb56f10f64009d6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:05:45 +0200
Subject: [PATCH 142/199] docs(de): finish German reference translation

---
 docs/de/reference/frontmatter-config.md | 50 ++++++++++++-------------
 1 file changed, 25 insertions(+), 25 deletions(-)

diff --git a/docs/de/reference/frontmatter-config.md b/docs/de/reference/frontmatter-config.md
index 6a3589e8a..134f79e2f 100644
--- a/docs/de/reference/frontmatter-config.md
+++ b/docs/de/reference/frontmatter-config.md
@@ -1,11 +1,11 @@
 ---
 outline: deep
-description: Reference of all verfügbar frontmatter configuration options for VitePress Markdown pages.
+description: Referenz aller verfügbaren Frontmatter-Konfigurationsoptionen für VitePress-Markdown-Seiten.
 ---
 
 # Frontmatter-Konfiguration
 
-Frontmatter enables page based configuration. In every markdown file, you can use frontmatter config to override site-level or theme-level config options. Also, there are config options which you can only define in frontmatter.
+Frontmatter ermöglicht die Konfiguration einzelner Seiten. In jeder Markdown-Datei kannst du Frontmatter verwenden, um Konfigurationsoptionen auf Website- oder Theme-Ebene zu überschreiben. Außerdem gibt es Optionen, die nur im Frontmatter definiert werden können.
 
 Beispiel usage:
 
@@ -16,7 +16,7 @@ editLink: true
 ---
 ```
 
-Du kannst access frontmatter data via the `$frontmatter` global in Vue expressions:
+Du kannst über das globale `$frontmatter` in Vue-Ausdrücken auf Frontmatter-Daten zugreifen:
 
 ```md
 {{ $frontmatter.title }}
@@ -26,7 +26,7 @@ Du kannst access frontmatter data via the `$frontmatter` global in Vue expressio
 
 - Type: `string`
 
-Title for the page. It's same as [config.title](./site-config#title), and it overrides the site-level config.
+Titel der Seite. Entspricht [config.title](./site-config#title) und überschreibt die Konfiguration auf Websiteebene.
 
 ```yaml
 ---
@@ -38,7 +38,7 @@ title: VitePress
 
 - Type: `string | boolean`
 
-The suffix for the title. It's same as [config.titleTemplate](./site-config#titletemplate), and it overrides the site-level config.
+Suffix für den Titel. Entspricht [config.titleTemplate](./site-config#titletemplate) und überschreibt die Konfiguration auf Websiteebene.
 
 ```yaml
 ---
@@ -51,7 +51,7 @@ titleTemplate: Vite & Vue powered static site generator
 
 - Type: `string`
 
-Description for the page. It's same as [config.description](./site-config#description), and it overrides the site-level config.
+Beschreibung der Seite. Entspricht [config.description](./site-config#description) und überschreibt die Konfiguration auf Websiteebene.
 
 ```yaml
 ---
@@ -63,7 +63,7 @@ description: VitePress
 
 - Type: `HeadConfig[]`
 
-Specify extra head tags to be injected for the current page. They are [merged](./site-config#head) with the head tags injected by site-level config.
+Gibt zusätzliche Head-Tags an, die für die aktuelle Seite eingefügt werden. Sie werden mit den über die Konfiguration auf Websiteebene eingefügten Head-Tags [zusammengeführt](./site-config#head).
 
 ```yaml
 ---
@@ -87,7 +87,7 @@ type HeadConfig =
 
 - Type: `'ltr' | 'rtl' | 'auto'`
 
-Overrides the [text direction](./site-config#dir) of the site for the current page.
+Überschreibt die [Schreibrichtung](./site-config#dir) der Website für die aktuelle Seite.
 
 ```yaml
 ---
@@ -97,7 +97,7 @@ dir: rtl
 
 ## Standard-Theme Only
 
-Die folgenden Frontmatter-Optionen are only applicable when using the default theme.
+Die folgenden Frontmatter-Optionen gelten nur bei Verwendung des Standard-Themes.
 
 ### layout
 
@@ -106,9 +106,9 @@ Die folgenden Frontmatter-Optionen are only applicable when using the default th
 
 Legt das Layout der Seite fest.
 
-- `doc` - It applies default documentation styles to the markdown content.
-- `home` - Special layout for "Startseite". Du kannst add extra options such as `hero` and `features` to rapidly create beautiful landing page.
-- `page` - Behave similar to `doc` but it applies no styles to the content. Useful when you want to create a fully custom page.
+- `doc` - Wendet die standardmäßigen Dokumentationsstile auf den Markdown-Inhalt an.
+- `home` - Spezielles Layout für die „Startseite“. Du kannst zusätzliche Optionen wie `hero` und `features` hinzufügen, um schnell ansprechende Startseiten zu erstellen.
+- `page` - Verhält sich ähnlich wie `doc`, wendet jedoch keine Stile auf den Inhalt an. Nützlich, wenn du eine vollständig eigene Seite erstellen möchtest.
 
 ```yaml
 ---
@@ -118,11 +118,11 @@ layout: doc
 
 ### hero <Badge type="info" text="home page only" />
 
-Defines contents of home hero section when `layout` is set to `home`. More details in [Standard-Theme: Startseite](./default-theme-home-page).
+Definiert den Inhalt des Hero-Bereichs der Startseite, wenn `layout` auf `home` gesetzt ist. Weitere Details findest du unter [Standard-Theme: Startseite](./default-theme-home-page).
 
 ### features <Badge type="info" text="home page only" />
 
-Defines items to display in features section when `layout` is set to `home`. More details in [Standard-Theme: Startseite](./default-theme-home-page).
+Definiert die im Feature-Bereich anzuzeigenden Elemente, wenn `layout` auf `home` gesetzt ist. Weitere Details findest du unter [Standard-Theme: Startseite](./default-theme-home-page).
 
 ### navbar
 
@@ -155,11 +155,11 @@ sidebar: false
 - Type: `boolean | 'left'`
 - Default: `true`
 
-Defines the location of the aside component in the `doc` layout.
+Definiert die Position der Aside-Komponente im `doc`-Layout.
 
-Setting this value to `false` prevents rendering of aside container.\
-Setting this value to `true` renders the aside to the right.\
-Setting this value to `'left'` renders the aside to the left.
+Bei `false` wird der Aside-Container nicht gerendert.\
+Bei `true` wird der Aside-Container rechts gerendert.\
+Bei `'left'` wird der Aside-Container links gerendert.
 
 ```yaml
 ---
@@ -172,7 +172,7 @@ aside: false
 - Type: `number | [number, number] | 'deep' | false`
 - Default: `2`
 
-Die Überschriftenebenen, die in der Seitenübersicht für die Seite angezeigt werden. It's same as [config.themeConfig.outline.level](./default-theme-config#outline), and it overrides the value set in site-level config.
+Die Überschriftenebenen, die in der Seitenübersicht für die Seite angezeigt werden. Entspricht [config.themeConfig.outline.level](./default-theme-config#outline) und überschreibt den Wert der Konfiguration auf Websiteebene.
 
 ```yaml
 ---
@@ -185,7 +185,7 @@ outline: [2, 4]
 - Type: `boolean | Date`
 - Default: `true`
 
-Ob [last updated](./default-theme-last-updated) text in the footer of the current page. If a datetime is specified, it will be displayed instead of the last git modified timestamp.
+Ob der Text für die [letzte Aktualisierung](./default-theme-last-updated) in der Fußzeile der aktuellen Seite angezeigt wird. Wenn ein Zeitpunkt angegeben ist, wird dieser anstelle des letzten Änderungszeitpunkts aus Git angezeigt.
 
 ```yaml
 ---
@@ -198,7 +198,7 @@ lastUpdated: false
 - Type: `boolean`
 - Default: `true`
 
-Ob [edit link](./default-theme-edit-link) in the footer of the current page.
+Ob ein [Bearbeitungslink](./default-theme-edit-link) in der Fußzeile der aktuellen Seite angezeigt wird.
 
 ```yaml
 ---
@@ -211,7 +211,7 @@ editLink: false
 - Type: `boolean`
 - Default: `true`
 
-Ob [footer](./default-theme-footer).
+Ob die [Fußzeile](./default-theme-footer) angezeigt wird.
 
 ```yaml
 ---
@@ -231,7 +231,7 @@ pageClass: custom-page-class
 ---
 ```
 
-Anschließend kannst du die Stile of this specific page in `.vitepress/theme/custom.css` file:
+Anschließend kannst du die Stile dieser bestimmten Seite in der Datei `.vitepress/theme/custom.css` anpassen:
 
 ```css
 .custom-page-class {
@@ -243,8 +243,8 @@ Anschließend kannst du die Stile of this specific page in `.vitepress/theme/cus
 
 - Type: `boolean`
 
-The default theme relies on checks like `frontmatter.layout === 'home'` to determine if the current page is the home page.\
-This is useful when you want to force show the home page elements in a custom layout.
+Das Standard-Theme verwendet Prüfungen wie `frontmatter.layout === 'home'`, um festzustellen, ob die aktuelle Seite die Startseite ist.\
+Dies ist nützlich, wenn du die Startseitenelemente in einem eigenen Layout erzwingen möchtest.
 
 ```yaml
 ---

From 116f978c3b462f60c7f292a6a9b53c04486cab06 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:05:48 +0200
Subject: [PATCH 143/199] docs(de): finish German reference translation

---
 docs/de/reference/runtime-api.md | 36 ++++++++++++++++----------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/docs/de/reference/runtime-api.md b/docs/de/reference/runtime-api.md
index e10646e8a..813a253a0 100644
--- a/docs/de/reference/runtime-api.md
+++ b/docs/de/reference/runtime-api.md
@@ -4,15 +4,15 @@ description: Referenz der VitePress-Runtime-APIs einschließlich Composables, Hi
 
 # Runtime API
 
-VitePress bietet mehrere integrierte APIs für den Zugriff auf Anwendungsdaten. VitePress also comes with a few built-in components that can be used globally.
+VitePress bietet außerdem einige integrierte Komponenten, die global verwendet werden können.
 
-Die Hilfsmethoden können global importiert werden from `vitepress` and are typically used in custom theme Vue components. Sie können jedoch auch innerhalb von `.md`-Seiten verwendet werden because markdown files are compiled into Vue [Single-Datei Komponenten](https://vuejs.org/guide/scaling-up/sfc.html).
+Die Hilfsmethoden können global aus `vitepress` importiert werden und werden normalerweise in Vue-Komponenten eigener Themes verwendet. Sie können jedoch auch innerhalb von `.md`-Seiten verwendet werden, da Markdown-Dateien in Vue-[Single-File-Komponenten](https://vuejs.org/guide/scaling-up/sfc.html) kompiliert werden.
 
-Methoden, die mit `use*` beginnen, sind that it is a [Vue 3 Composition API](https://vuejs.org/guide/introduction.html#composition-api) function ("Composable") that can only be used inside `setup()` or `<script setup>`.
+Methoden, die mit `use*` beginnen, sind [Vue-3-Composition-API](https://vuejs.org/guide/introduction.html#composition-api)-Funktionen („Composables“), die nur innerhalb von `setup()` oder `<script setup>` verwendet werden können.
 
 ## `useData` <Badge type="info" text="composable" />
 
-Gibt seitenspezifische Daten zurück. The returned object has the following type:
+Gibt seitenspezifische Daten zurück. Das zurückgegebene Objekt hat folgenden Typ:
 
 ```ts
 interface VitePressData<T = any> {
@@ -62,7 +62,7 @@ interface PageData {
 }
 ```
 
-`page.headers` is populated only when [`markdown.headers`](./site-config#markdown) ist aktiviert. Ohne diese Option bleibt es ein leeres Array. The default theme outline reads rendered headings from the page content, so it can still appear when `page.headers` is empty.
+`page.headers` wird nur gefüllt, wenn [`markdown.headers`](./site-config#markdown) aktiviert ist. Ohne diese Option bleibt es ein leeres Array. Die Seitenübersicht des Standard-Themes liest gerenderte Überschriften aus dem Seiteninhalt, sodass sie auch bei leerem `page.headers` angezeigt werden kann.
 
 **Beispiel:**
 
@@ -80,7 +80,7 @@ const { theme } = useData()
 
 ## `useRoute` <Badge type="info" text="composable" />
 
-Gibt das aktuelle Routenobjekt zurück with the following type:
+Gibt das aktuelle Routenobjekt mit folgendem Typ zurück:
 
 ```ts
 interface Route {
@@ -124,7 +124,7 @@ interface Router {
 }
 ```
 
-Assign route-change handlers on the router instance:
+Weise der Routerinstanz Handler für Routenänderungen zu:
 
 ```ts
 const router = useRouter()
@@ -140,9 +140,9 @@ Bei eigenen Themes ist derselbe Router über [`enhanceApp`](../guide/custom-them
 
 - **Type**: `(icon: MaybeRefOrGetter<string | { svg: string } | undefined>, el?: MaybeRefOrGetter<HTMLElement | null>) => ComputedRef<string | undefined>`
 
-Renders an [iconify](https://iconify.design/) icon through VitePress's icon pipeline. Erwartet eine vollständig qualifizierte `collection:name` (resolved against the `@iconify-json/*` packages in your project's dependencies) und gibt die Klasse zurück, die auf dem Element gesetzt werden soll — `vpi-<collection>-<name>`.
+Rendert ein [Iconify](https://iconify.design/)-Symbol über die Icon-Pipeline von VitePress. Erwartet eine vollständig qualifizierte `collection:name` (aufgelöst anhand der `@iconify-json/*`-Pakete in den Abhängigkeiten deines Projekts) und gibt die Klasse zurück, die auf dem Element gesetzt werden soll — `vpi-<collection>-<name>`.
 
-Während SSR wird der Name im [`SSGContext`](./site-config#postrender), so the build emits the icon's styles into the generated stylesheet; in dev, icons are served on demand by the dev server from the locally installed collections. No icon is ever fetched from an external service.
+Während SSR wird der Name im [`SSGContext`](./site-config#postrender) registriert, sodass der Build die Symbolstile in das erzeugte Stylesheet schreibt. Im Entwicklungsmodus liefert der Entwicklungsserver Symbole bei Bedarf aus den lokal installierten Sammlungen. Kein Symbol wird jemals von einem externen Dienst geladen.
 
 ```vue
 <script setup>
@@ -158,25 +158,25 @@ const iconClass = useIcon('lucide:rocket', el)
 </template>
 ```
 
-Übergebe die Template-Referenz of the element carrying the class so dev mode can resolve the icon on it. Das Element benötigt the mask rules the default theme ships; in a custom theme without them, dev applies an inline equivalent and the generated stylesheet includes zero-specificity base rules for production.
+Übergebe die Template-Referenz des Elements, das die Klasse trägt, damit der Entwicklungsmodus das Symbol darauf auflösen kann. Das Element benötigt die Maskenregeln des Standard-Themes; bei einem eigenen Theme ohne diese Regeln verwendet der Entwicklungsmodus ein entsprechendes Inline-Äquivalent und das erzeugte Stylesheet enthält für die Produktion Basisregeln ohne Spezifität.
 
-Bei Verwendung des Standard-Themes, the `VPIcon` component from `vitepress/theme` wraps this composable (and also accepts a raw `{ svg }` string):
+Bei Verwendung des Standard-Themes kapselt die Komponente `VPIcon` aus `vitepress/theme` dieses Composable (und akzeptiert auch eine rohe `{ svg }`-Zeichenkette):
 
 ```vue-html
 <VPIcon icon="lucide:rocket" />
 ```
 
-Symbole, die nur auf dem Client gerendert werden (e.g. inside `<ClientOnly />`) can't be collected during the build — list them in [`icons.include`](./site-config#icons) instead.
+Symbole, die nur auf dem Client gerendert werden (z. B. innerhalb von `<ClientOnly />`), können während des Builds nicht erfasst werden. Liste sie stattdessen unter [`icons.include`](./site-config#icons) auf.
 
 ## `withBase` <Badge type="info" text="helper" />
 
 - **Type**: `(path: string) => string`
 
-Stellt das konfigurierte [`base`](./site-config#base) einem angegebenen URL-Pfad voran. Also see [Base URL](../guide/asset-handling#base-url).
+Stellt das konfigurierte [`base`](./site-config#base) einem angegebenen URL-Pfad voran. Siehe auch [Basis-URL](../guide/asset-handling#base-url).
 
 ## `<Inhalt />` <Badge type="info" text="component" />
 
-The `<Inhalt />` component displays the rendered markdown contents. Nützlich [beim Erstellen eines eigenen Themes](../guide/custom-theme).
+Die Komponente `<Content />` zeigt den gerenderten Markdown-Inhalt an. Nützlich [beim Erstellen eines eigenen Themes](../guide/custom-theme).
 
 ```vue
 <template>
@@ -189,9 +189,9 @@ The `<Inhalt />` component displays the rendered markdown contents. Nützlich [b
 
 Die Komponente `<ClientOnly />` rendert ihren Slot nur auf der Clientseite.
 
-Da VitePress-Anwendungen beim Erzeugen statischer Builds in Node.js serverseitig gerendert werden, any Vue usage must conform to the universal code requirements. In short, make sure to only access Browser / DOM APIs in beforeMount or mounted hooks.
+Da VitePress-Anwendungen beim Erzeugen statischer Builds in Node.js serverseitig gerendert werden, muss jede Vue-Verwendung den Anforderungen an universellen Code entsprechen. Kurz gesagt: Greife nur in `beforeMount`- oder `mounted`-Hooks auf Browser-/DOM-APIs zu.
 
-Wenn du are using or demoing components that are not SSR-friendly (for example, contain custom directives), you can wrap them inside the `ClientOnly` component.
+Wenn du nicht SSR-kompatible Komponenten verwendest oder demonstrierst (beispielsweise solche mit eigenen Direktiven), kannst du sie in die `ClientOnly`-Komponente einschließen.
 
 ```vue-html
 <ClientOnly>
@@ -203,7 +203,7 @@ Wenn du are using or demoing components that are not SSR-friendly (for example,
 
 ## `$frontmatter` <Badge type="info" text="template global" />
 
-Greife direkt auf die [frontmatter](../guide/frontmatter) data in Vue expressions.
+Greife direkt auf die [Frontmatter](../guide/frontmatter)-Daten in Vue-Ausdrücken zu.
 
 ```md
 ---
@@ -215,7 +215,7 @@ title: Hello
 
 ## `$params` <Badge type="info" text="template global" />
 
-Greife direkt auf die [dynamic route params](../guide/routing#dynamic-routes) in Vue expressions.
+Greife direkt auf die [Parameter dynamischer Routen](../guide/routing#dynamic-routes) in Vue-Ausdrücken zu.
 
 ```md
 - package name: {{ $params.pkg }}

From f66d36cdf9110879b18b28586781de998305f6a9 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:05:50 +0200
Subject: [PATCH 144/199] docs(de): finish German reference translation

---
 docs/de/reference/site-config.md | 60 ++++++++++++++++----------------
 1 file changed, 30 insertions(+), 30 deletions(-)

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
index 85c018cf3..52fe22a98 100644
--- a/docs/de/reference/site-config.md
+++ b/docs/de/reference/site-config.md
@@ -5,15 +5,15 @@ description: Vollständige Referenz der VitePress-Website-Konfigurationsoptionen
 
 # Site-Konfiguration
 
-In der Website-Konfiguration definierst du die globalen Einstellungen der Website. Konfigurationsoptionen auf Anwendungsebene gelten für jede VitePress-Website, unabhängig vom verwendeten Theme. Zum Beispiel, the base directory or the title of the site.
+In der Website-Konfiguration definierst du die globalen Einstellungen der Website. Konfigurationsoptionen auf Anwendungsebene gelten für jede VitePress-Website, unabhängig vom verwendeten Theme. Zum Beispiel das Basisverzeichnis oder den Titel der Website.
 
 ## Übersicht
 
 ### Auflösung der Konfiguration
 
-Die Konfigurationsdatei wird immer aus `<root>/.vitepress/config.[ext]`, wobei `<root>` dein VitePress [project root](../guide/routing#root-and-source-directory), and `[ext]` is one of the supported file extensions. TypeScript is supported out of the box. Supported extensions include `.js`, `.ts`, `.mjs`, and `.mts`.
+Die Konfigurationsdatei wird immer aus `<root>/.vitepress/config.[ext]`, wobei `<root>` dein VitePress-[Projektstammverzeichnis](../guide/routing#root-and-source-directory) ist und `[ext]` eine der unterstützten Dateierweiterungen bezeichnet. TypeScript wird standardmäßig unterstützt. Unterstützte Erweiterungen sind `.js`, `.ts`, `.mjs` und `.mts`.
 
-Es wird empfohlen, in Konfigurationsdateien die ES-Modul-Syntax zu verwenden. The config file should default export an object:
+Es wird empfohlen, in Konfigurationsdateien die ES-Modul-Syntax zu verwenden. Die Konfigurationsdatei sollte standardmäßig ein Objekt exportieren:
 
 ```ts
 export default {
@@ -25,9 +25,9 @@ export default {
 }
 ```
 
-::: details Dynamic (Async) Config
+::: details Dynamische (asynchrone) Konfiguration
 
-Wenn du die Konfiguration dynamisch erzeugen musst, you can also default export a function. Zum Beispiel:
+Wenn du die Konfiguration dynamisch erzeugen musst, kannst du auch standardmäßig eine Funktion exportieren. Zum Beispiel:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -83,7 +83,7 @@ export default defineConfig({
 
 ### Konfigurations-IntelliSense
 
-Die Verwendung des Helpers `defineConfig` stellt TypeScript-basierte IntelliSense für Konfigurationsoptionen bereit. Sofern deine IDE dies unterstützt, this should work in both JavaScript and TypeScript.
+Die Verwendung des Helpers `defineConfig` stellt TypeScript-basierte IntelliSense für Konfigurationsoptionen bereit. Sofern deine IDE dies unterstützt, sollte dies sowohl in JavaScript als auch in TypeScript funktionieren.
 
 ```js
 import { defineConfig } from 'vitepress'
@@ -95,7 +95,7 @@ export default defineConfig({
 
 ### Typisierte Theme-Konfiguration
 
-Standardmäßig erwartet der Helper `defineConfig` the theme config type from default theme:
+Standardmäßig erwartet der Helper `defineConfig` den Theme-Konfigurationstyp des Standard-Themes:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -107,7 +107,7 @@ export default defineConfig({
 })
 ```
 
-Wenn du ein eigenes Theme verwendest und Typprüfungen for the theme config, musst du stattdessen `defineConfigWithTheme` verwenden, and pass the config type for your custom theme via a generic argument:
+Wenn du ein eigenes Theme verwendest und Typprüfungen für dessen Theme-Konfiguration möchtest, musst du stattdessen `defineConfigWithTheme` verwenden und den Konfigurationstyp deines eigenen Themes als generisches Argument übergeben:
 
 ```ts
 import { defineConfigWithTheme } from 'vitepress'
@@ -124,33 +124,33 @@ export default defineConfigWithTheme<ThemeConfig>({
 
 - **Vite**
 
-  Du kannst configure the underlying Vite instance using the [vite](#vite) option in your VitePress config. Eine separate Vite-Konfigurationsdatei ist nicht erforderlich.
+  Du kannst die zugrunde liegende Vite-Instanz über die Option [vite](#vite) in deiner VitePress-Konfiguration konfigurieren. Eine separate Vite-Konfigurationsdatei ist nicht erforderlich.
 
 - **Vue**
 
-  VitePress enthält bereits das offizielle Vue-Plugin für Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). Du kannst dessen Optionen konfigurieren using the [vue](#vue) option in your VitePress config.
+  VitePress enthält bereits das offizielle Vue-Plugin für Vite ([@vitejs/plugin-vue](https://github.com/vitejs/vite-plugin-vue)). Du kannst dessen Optionen über die Option [vue](#vue) in deiner VitePress-Konfiguration konfigurieren.
 
 - **Markdown**
 
-  Du kannst configure the underlying [Markdown-It](https://github.com/markdown-it/markdown-it) instance using the [markdown](#markdown) option in your VitePress config.
+  Du kannst die zugrunde liegende [Markdown-It](https://github.com/markdown-it/markdown-it)-Instanz über die Option [markdown](#markdown) in deiner VitePress-Konfiguration konfigurieren.
 
 ### Überschreibungen auf Seitenebene
 
 Einige Einstellungen können für bestimmte Seiten über das Frontmatter überschrieben werden.
 
-See [Frontmatter-Konfiguration](./frontmatter-config) for details.
+Weitere Informationen findest du unter [Frontmatter-Konfiguration](./frontmatter-config).
 
 ### Überschreibungen auf Verzeichnisebene
 
-Einige Konfigurationseinstellungen können auf Verzeichnisebene überschrieben werden, allowing all pages in that directory to share settings without needing to repeat them in the frontmatter of each page.
+Einige Konfigurationseinstellungen können auf Verzeichnisebene überschrieben werden, sodass alle Seiten in diesem Verzeichnis dieselben Einstellungen verwenden können, ohne sie im Frontmatter jeder Seite wiederholen zu müssen.
 
-Dies wird erreicht, indem eine Datei namens `config.ts` (or `.js`, `.mjs`, or `.mts`) in the relevant directory. This file should export a config object using `export default`, similar to the main config file.
+Dies wird erreicht, indem im entsprechenden Verzeichnis eine Datei namens `config.ts` (oder `.js`, `.mjs` bzw. `.mts`) angelegt wird. Diese Datei sollte wie die Hauptkonfigurationsdatei ein Konfigurationsobjekt über `export default` exportieren.
 
-Verschachtelte Verzeichnisse übernehmen Einstellungen ihres übergeordneten Verzeichnisses, with configuration overrides being merged accordingly.
+Verschachtelte Verzeichnisse übernehmen die Einstellungen ihres übergeordneten Verzeichnisses; Überschreibungen werden entsprechend zusammengeführt.
 
-Der Helper `defineAdditionalConfig` kann verwendet werden to get TypeScript-powered intellisense for the verfügbar options, though as with `defineConfig` its use is optional.
+Der Helper `defineAdditionalConfig` kann verwendet werden, um TypeScript-basierte IntelliSense für die verfügbaren Optionen zu erhalten. Wie bei `defineConfig` ist seine Verwendung optional.
 
-Zum Beispiel können wir bei einer Website mit mehreren Sprachen we might want a different `description` for each language. We could add `es/config.ts` with the following content:
+Bei einer Website mit mehreren Sprachen möchten wir beispielsweise für jede Sprache eine andere `description` verwenden. Dazu können wir `es/config.ts` mit folgendem Inhalt anlegen:
 
 ```ts
 import { defineAdditionalConfig } from 'vitepress'
@@ -160,9 +160,9 @@ export default defineAdditionalConfig({
 })
 ```
 
-Diese `description` wird anschließend für alle Seiten in the `es` directory.
+Diese `description` wird anschließend für alle Seiten im Verzeichnis `es` verwendet.
 
-Alternativ können bei Verwendung der integrierten i18n-Funktionen, the settings for a locale directory can be overridden via the `locales` setting in the main configuration file. See [Internationalization](../guide/i18n) for details.
+Alternativ können die Einstellungen eines Sprachverzeichnisses bei Verwendung der integrierten i18n-Funktionen über die `locales`-Einstellung in der Hauptkonfigurationsdatei überschrieben werden. Weitere Informationen findest du unter [Internationalisierung](../guide/i18n).
 
 ## Website-Metadaten
 
@@ -170,11 +170,11 @@ Alternativ können bei Verwendung der integrierten i18n-Funktionen, the settings
 
 - Type: `string`
 - Default: `VitePress`
-- Can be overridden per page via [frontmatter](./frontmatter-config#title) or at the [directory level](#directory-level-overrides)
+- Kann pro Seite über das [Frontmatter](./frontmatter-config#title) oder auf [Verzeichnisebene](#directory-level-overrides) überschrieben werden
 
-Title for the site. Bei Verwendung des Standard-Themes, this will be displayed in the nav bar.
+Titel der Website. Bei Verwendung des Standard-Themes wird er in der Navigationsleiste angezeigt.
 
-Er wird außerdem als Standardsuffix for all individual page titles, unless [`titleTemplate`](#titletemplate) is defined. An individual page's final title will be the text content of its first `<h1>` header, combined with the global `title` as the suffix. Zum Beispiel with the following config and page content:
+Er wird außerdem als Standardsuffix für alle einzelnen Seitentitel verwendet, sofern [`titleTemplate`](#titletemplate) nicht definiert ist. Der endgültige Titel einer einzelnen Seite besteht aus dem Text ihrer ersten `<h1>`-Überschrift und dem globalen `title` als Suffix. Zum Beispiel bei folgender Konfiguration und folgendem Seiteninhalt:
 
 ```ts
 export default {
@@ -191,9 +191,9 @@ Der Titel der Seite lautet `Hello | My Awesome Site`.
 ### titleTemplate
 
 - Type: `string | boolean`
-- Can be overridden per page via [frontmatter](./frontmatter-config#titletemplate) or at the [directory level](#directory-level-overrides)
+- Kann pro Seite über das [Frontmatter](./frontmatter-config#titletemplate) oder auf [Verzeichnisebene](#directory-level-overrides) überschrieben werden
 
-Allows customizing each page's title suffix or the entire title. Zum Beispiel:
+Ermöglicht die Anpassung des Titelsuffixes jeder Seite oder des gesamten Titels. Zum Beispiel:
 
 ```ts
 export default {
@@ -208,7 +208,7 @@ export default {
 
 Der Titel der Seite lautet `Hello | Eigenes Suffix`.
 
-To completely customize how the title should be rendered, you can use the `:title` symbol in `titleTemplate`:
+Um die Darstellung des Titels vollständig anzupassen, kannst du das Symbol `:title` in `titleTemplate` verwenden:
 
 ```ts
 export default {
@@ -216,17 +216,17 @@ export default {
 }
 ```
 
-Here `:title` will be replaced with the text inferred from the page's first `<h1>` header. The title of the previous example page will be `Hello - Eigenes Suffix`.
+Hier wird `:title` durch den aus der ersten `<h1>`-Überschrift der Seite ermittelten Text ersetzt. Der Titel der vorherigen Beispielseite lautet `Hello - Eigenes Suffix`.
 
-The option can be set to `false` to disable title suffixes.
+Die Option kann auf `false` gesetzt werden, um Titelsuffixe zu deaktivieren.
 
 ### description
 
 - Type: `string`
-- Default: `A VitePress site`
+- Standard: `Eine VitePress-Website`
 - Can be overridden per page via [frontmatter](./frontmatter-config#description) or at the [directory level](#directory-level-overrides)
 
-Description for the site. This will render as a `<meta>` tag in the page HTML.
+Beschreibung der Website. Sie wird als `<meta>`-Tag im HTML der Seite ausgegeben.
 
 ```ts
 export default {
@@ -240,7 +240,7 @@ export default {
 - Default: `[]`
 - Can be appended per page via [frontmatter](./frontmatter-config#head) or at the [directory level](#directory-level-overrides)
 
-Additional elements to render in the `<head>` tag in the page HTML. The user-added tags are rendered before the closing `head` tag, after VitePress tags.
+Zusätzliche Elemente, die im `<head>`-Tag des Seiten-HTML gerendert werden. Vom Benutzer hinzugefügte Tags werden nach den VitePress-Tags und vor dem schließenden `head`-Tag gerendert.
 
 ```ts
 type HeadConfig =

From 33bc3d9d1293084a85eaa44e9605349d812b38c2 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:06 +0200
Subject: [PATCH 145/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20verbessern?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/custom-theme.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/custom-theme.md b/docs/de/guide/custom-theme.md
index 3367b8f0e..dd4e0bf20 100644
--- a/docs/de/guide/custom-theme.md
+++ b/docs/de/guide/custom-theme.md
@@ -6,7 +6,7 @@ description: Erstelle und verwende ein eigenes Theme in VitePress, um das Ersche
 
 ## Theme-Auflösung
 
-Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` or `.vitepress/theme/index.ts` file (die „Theme-Einstiegsdatei“):
+Du kannst ein eigenes Theme aktivieren, indem du eine Datei `.vitepress/theme/index.js` oder `.vitepress/theme/index.ts` (die „Theme-Einstiegsdatei“) erstellst:
 
 ```
 .
@@ -19,7 +19,7 @@ Du kannst ein eigenes Theme aktivieren, indem du a `.vitepress/theme/index.js` o
 └─ package.json
 ```
 
-VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [extend das Standard-Theme](./extending-default-theme) to perform advanced customizations on top of it.
+VitePress verwendet immer das eigene Theme anstelle des Standard-Themes, sobald es eine Theme-Einstiegsdatei erkennt. Du kannst jedoch [das Standard-Theme erweitern](./extending-default-theme), um darauf aufbauend fortgeschrittene Anpassungen vorzunehmen.
 
 ## Theme-Schnittstelle
 
@@ -73,7 +73,7 @@ export default {
 }
 ```
 
-Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue app instance](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [register global components](./extending-default-theme.md#registering-global-components), integrate with Vue libraries, etc.
+Der `enhanceApp`-Hook ermöglicht den Zugriff auf die [Vue-App-Instanz](https://vuejs.org/api/application.html) und andere Laufzeitdaten. Damit kannst du beispielsweise [globale Komponenten registrieren](./extending-default-theme.md#registering-global-components), Vue-Bibliotheken integrieren usw.
 
 Der Wert `router` ist dieselbe VitePress-Router-Instanz, die von [`useRouter()`](../reference/runtime-api#userouter). Um auf Routenänderungen zu reagieren, weist du dem Router Handler zu:
 
@@ -115,7 +115,7 @@ Mit `extends` wird das `setup` jedes Themes wie bei `enhanceApp` von der Basis a
 
 Der Standardexport ist der einzige Vertrag für ein eigenes Theme, und nur die Eigenschaft `Layout` ist erforderlich. Technisch kann ein VitePress-Theme daher aus nur einer einzigen Vue-Komponente bestehen.
 
-Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Beachte, dass das Theme außerdem [SSR-compatible](./ssr-compat).
+Innerhalb deiner Layout-Komponente funktioniert alles wie in einer normalen Vite- + Vue-3-Anwendung. Beachte, dass das Theme außerdem [mit SSR kompatibel](./ssr-compat) sein muss.
 
 ## Ein Layout erstellen
 
@@ -148,7 +148,7 @@ const { page } = useData()
 </template>
 ```
 
-The [`useData()`](../reference/runtime-api#usedata) helper provides us with all the runtime data we need to conditionally render different layouts. One of the other data we can access is die aktuelle Seite's frontmatter. We can leverage this to allow the end user to control the layout in each page. Zum Beispiel, the user can indicate die Seite should use a special home Seitenlayout with:
+Der [`useData()`](../reference/runtime-api#usedata)-Helper stellt uns alle Laufzeitdaten zur Verfügung, die wir benötigen, um verschiedene Layouts bedingt zu rendern. Zu den Daten, auf die wir zugreifen können, gehört das Frontmatter der aktuellen Seite. Damit können wir dem Endbenutzer ermöglichen, das Layout jeder Seite zu steuern. Zum Beispiel kann der Benutzer angeben, dass die Seite ein spezielles Startseitenlayout verwenden soll:
 
 ```md
 ---
@@ -156,7 +156,7 @@ layout: home
 ---
 ```
 
-And we can adjust our theme to handle this:
+Anschließend können wir unser Theme entsprechend anpassen:
 
 ```vue{3,12-14}
 <script setup>

From 914e6580cd5b3e23dda4ada79d1e09bab888f7e5 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:08 +0200
Subject: [PATCH 146/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20verbessern?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/deploy.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index 18623d610..6ff6e3cbe 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -50,13 +50,13 @@ Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
 ## Einen öffentlichen Basispfad festlegen
 
-Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`). Wenn deine Website unter einem Unterpfad bereitgestellt wird, e.g. `https://mywebsite.com/blog/`, musst du die Option [`base`](../reference/site-config#base) option to `'/blog/'` in the VitePress config.
+Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`) bereitgestellt wird. Wenn deine Website unter einem Unterpfad wie `https://mywebsite.com/blog/` bereitgestellt wird, musst du die Option [`base`](../reference/site-config#base) in der VitePress-Konfiguration auf `'/blog/'` setzen.
 
 **Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, dann set your `base` to `/repo/`.
 
 ## Verschiebbare Builds (relativer Basispfad) {#relocatable-builds-relative-base}
 
-Wenn die endgültige URL der Website zur Build-Zeit noch nicht bekannt ist — an IPFS gateway (`https://gateway/ipfs/<cid>/…`), the Wayback Machine, a shared folder, docs bundled in an app — set `base` to `'./'`:
+Wenn die endgültige URL der Website zur Build-Zeit noch nicht bekannt ist – etwa bei einem IPFS-Gateway (`https://gateway/ipfs/<cid>/…`), der Wayback Machine, einem freigegebenen Ordner oder in eine App eingebetteter Dokumentation –, setze `base` auf `'./'`:
 
 ```ts
 export default {
@@ -66,23 +66,23 @@ export default {
 
 Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Derselbe Build funktioniert von **jedem** Unterpfad aus ohne erneuten Build – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
 
-Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) also works as a styled, fully navigable static site. Browser blockieren JavaScript-Module über `file://`, so there is no hydration there — interactive features like search stay inactive, while all pre-rendered content and links keep working.
+Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) funktioniert ebenfalls als vollständig navigierbare statische Website mit Formatierung. Browser blockieren JavaScript-Module über `file://`, daher findet dort keine Hydration statt – interaktive Funktionen wie die Suche bleiben inaktiv, während alle vorgerenderten Inhalte und Links weiterhin funktionieren.
 
 Einige Dinge solltest du beachten:
 
 - Lasse [`cleanUrls`](../reference/site-config#cleanurls) deaktiviert (Standardeinstellung): Für portable Ausgaben müssen Links mit `.html` enden, da kein Server vorhanden ist, der saubere URLs umschreibt.
-- `404.html` wird für die Stammebene erzeugt. Hosts, die sie als Fallback für beliebig tiefe URLs ausliefern, rendern sie ohne Styles (there is no correct relative prefix for an unknown depth).
-- [`head`](../reference/site-config#head) Einträge werden wie immer unverändert ausgegeben – vermeide dort absolute Pfade wie `/favicon.ico` there and prefer absolute URLs or `transformHead`.
-- Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert — use Markdown link syntax for site-absolute links (embedded `<img>` sources go durch the asset pipeline and are handled).
-- Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (their HTML is embedded in other pages, so no single relative prefix is correct) — they resolve only for a root mount.
-- Stelle Seiten unter ihren kanonischen URLs bereit: the root as `/dir/` (not `/dir`), and no added trailing slashes on page URLs. The relative prefix is resolved against the URL the browser actually shows, and virtually all static hosts canonicalize this way already.
+- `404.html` wird für die Stammebene erzeugt. Hosts, die sie als Fallback für beliebig tiefe URLs ausliefern, rendern sie ohne Styles (für eine unbekannte Pfadtiefe gibt es keinen korrekten relativen Präfix).
+- [`head`](../reference/site-config#head)-Einträge werden wie immer unverändert ausgegeben – vermeide dort absolute Pfade wie `/favicon.ico` und bevorzuge absolute URLs oder `transformHead`.
+- Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert – verwende für absolute Links innerhalb der Website die Markdown-Linksyntax (eingebettete `<img>`-Quellen werden über die Asset-Pipeline verarbeitet).
+- Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (ihr HTML wird in andere Seiten eingebettet, daher gibt es keinen einheitlichen relativen Präfix) – sie funktionieren nur bei einer Bereitstellung am Stammverzeichnis.
+- Stelle Seiten unter ihren kanonischen URLs bereit: das Stammverzeichnis als `/dir/` (nicht `/dir`) und ohne zusätzliche abschließende Schrägstriche bei Seiten-URLs. Der relative Präfix wird anhand der URL aufgelöst, die der Browser tatsächlich anzeigt, und praktisch alle statischen Hoster verwenden bereits diese kanonische Form.
 - Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktions-Build.
 
 ## HTTP-Cache-Header
 
 Wenn du Kontrolle über die HTTP-Header deines Produktionsservers hast, kannst du `cache-control`-Header konfigurieren, um bei wiederholten Besuchen eine bessere Leistung zu erzielen.
 
-Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS and other imported assets not in `public`). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, you will see files like `app.4f283b18.js`.
+Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS und andere importierte Assets, die nicht in `public` liegen). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, siehst du Dateien wie `app.4f283b18.js`.
 
 Dieser Hash `4f283b18` wird aus dem Inhalt dieser Datei erzeugt. Dieselbe gehashte URL liefert garantiert denselben Dateiinhalt – wenn sich der Inhalt ändert, ändern sich auch die URLs. Das bedeutet, dass du für diese Dateien bedenkenlos die stärksten Cache-Header verwenden kannst. Alle solchen Dateien werden im Ausgabeverzeichnis unter `assets/` abgelegt. Dafür kannst du den folgenden Header konfigurieren:
 
@@ -98,7 +98,7 @@ Cache-Control: max-age=31536000,immutable
   cache-control: immutable
 ```
 
-Hinweis: Die Datei `_headers` sollte im [Public-Verzeichnis](./asset-handling#the-public-directory) - in our case, `docs/public/_headers` - liegen, damit sie unverändert in das Ausgabeverzeichnis kopiert wird.
+Hinweis: Die Datei `_headers` sollte im [Public-Verzeichnis](./asset-handling#the-public-directory) – in diesem Fall `docs/public/_headers` – liegen, damit sie unverändert in das Ausgabeverzeichnis kopiert wird.
 
 [Netlify-Dokumentation zu benutzerdefinierten Headern](https://docs.netlify.com/routing/headers/)
 
@@ -136,7 +136,7 @@ Richte ein neues Projekt ein und ändere diese Einstellungen über dein Dashboar
 
 - **Build-Befehl:** `npm run docs:build`
 - **Ausgabeverzeichnis:** `docs/.vitepress/dist`
-- **Node-Version:** `20` (or above)
+- **Node-Version:** `20` (oder höher)
 
 ::: warning
 Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommentare aus der Ausgabe entfernt, die für Vue Bedeutung haben. Wenn sie entfernt werden, können Hydration-Mismatch-Fehler auftreten.

From cc2c6ab519aeaeeba885a6842364bedc535becc1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:11 +0200
Subject: [PATCH 147/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20verbessern?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/extending-default-theme.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index 074f1f0a2..f23c272f7 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -1,22 +1,22 @@
 ---
 outline: deep
-description: Anpassen and extend the VitePress Standard-Theme mit custom CSS, components, layouts, and slots.
+description: Passe das VitePress-Standard-Theme mit benutzerdefiniertem CSS, Komponenten, Layouts und Slots an und erweitere es.
 ---
 
 # Standard-Theme erweitern
 
-VitePress' Standard-Theme is optimized for documentation, and can be customized. Consult the [Standard-Theme Config Übersicht](../reference/default-theme-config) for a comprehensive list of options.
+Das VitePress-Standard-Theme ist für Dokumentation optimiert und kann angepasst werden. Eine umfassende Liste der Optionen findest du in der [Übersicht zur Standard-Theme-Konfiguration](../reference/default-theme-config).
 
-However, there are a number of cases where Konfiguration alone won't be enough. Zum Beispiel:
+Es gibt jedoch einige Fälle, in denen die Konfiguration allein nicht ausreicht. Zum Beispiel:
 
-1. You need to tweak the CSS styling;
-2. You need to modify the Vue app instance, zum Beispiel to register global components;
-3. You need to inject custom content in the theme via layout slots.
+1. Du musst die CSS-Gestaltung anpassen;
+2. Du musst die Vue-App-Instanz ändern, zum Beispiel um globale Komponenten zu registrieren;
+3. Du musst über Layout-Slots benutzerdefinierte Inhalte in das Theme einfügen.
 
-These advanced customizations will require Verwendung a eigenes Theme that "extends" das Standard-Theme.
+Diese fortgeschrittenen Anpassungen erfordern ein eigenes Theme, das das Standard-Theme „erweitert“.
 
 ::: tip
-Before proceeding, make sure to first read [Using a Eigenes Theme](./custom-theme) to understand how eigenes Themes work.
+Bevor du fortfährst, lies zunächst [Ein eigenes Theme verwenden](./custom-theme), um zu verstehen, wie eigene Themes funktionieren.
 :::
 
 ## Anpassen CSS
@@ -80,9 +80,9 @@ The same treatment carries over to the local nav: `--vp-local-nav-bg-color` foll
 
 Wenn the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar instead of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).
 
-## Using Different Fonts
+## Andere Schriftarten verwenden
 
-VitePress verwendet [Inter](https://rsms.me/inter/) as the default font, and will include the fonts in the Build-Ausgabe. The font is also auto preloaded in production. However, this may not be desirable wenn you want to use a different main font.
+VitePress verwendet [Inter](https://rsms.me/inter/) als Standardschriftart und fügt die Schriftarten der Build-Ausgabe hinzu. Die Schriftart wird in der Produktion außerdem automatisch vorab geladen. Das ist möglicherweise nicht erwünscht, wenn du eine andere Hauptschriftart verwenden möchtest.
 
 To avoid including Inter in the Build-Ausgabe, import the theme von `vitepress/theme-ohne-fonts` instead:
 

From 240712feb3ab6ce29d9388535ef4c7549c5c7a78 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:40 +0200
Subject: [PATCH 148/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/frontmatter.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/frontmatter.md b/docs/de/guide/frontmatter.md
index 2639652f8..c22c43ebc 100644
--- a/docs/de/guide/frontmatter.md
+++ b/docs/de/guide/frontmatter.md
@@ -15,7 +15,7 @@ editLink: true
 ---
 ```
 
-Viele Optionen der Website- oder Standard-Theme-Konfiguration besitzen entsprechende Optionen im Frontmatter. Du kannst Frontmatter verwenden, um bestimmtes Verhalten nur für die aktuelle Seite zu überschreiben. Einzelheiten findest du in [Frontmatter Config Referenz](../reference/frontmatter-config).
+Viele Optionen der Website- oder Standard-Theme-Konfiguration besitzen entsprechende Optionen im Frontmatter. Du kannst Frontmatter verwenden, um bestimmtes Verhalten nur für die aktuelle Seite zu überschreiben. Einzelheiten findest du in [Referenz zur Frontmatter-Konfiguration](../reference/frontmatter-config).
 
 Du kannst außerdem eigene Frontmatter-Daten definieren und sie in dynamischen Vue-Ausdrücken auf der Seite verwenden.
 
@@ -36,9 +36,9 @@ editLink: true
 Inhalt der Anleitung
 ```
 
-Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in [content loader](./data-loading#createcontentloader) Ausgabe, in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
+Zugriffe auf Eigenschaften wie `{{ $frontmatter.title }}` werden beim Rendern von Markdown aufgelöst. Der Wert landet dadurch auch im lokalen Suchindex, in der Ausgabe des [Datenladers](./data-loading#createcontentloader), in Überschriftenankern – die obige Überschrift erhält `id="docs-mit-vitepress"` – und in Linkzielen, die ohne Leerzeichen um den Ausdruck geschrieben werden, etwa `[text]({{$frontmatter.link}})`. Andere Ausdrücke werden wie gewohnt zur Laufzeit von Vue ausgewertet. Wenn du einen Ausdruck in [`v-pre`](./Verwendung-vue#escaping) einschließt, wird er wörtlich angezeigt.
 
-Du kannst außerdem auf die Frontmatter-Daten der aktuellen Seite in `<script setup>` mit dem [`useData()`](../reference/runtime-api#usedata) -Helper zugreifen.
+Du kannst außerdem in `<script setup>` mit dem [`useData()`](../reference/runtime-api#usedata)-Helper auf die Frontmatter-Daten der aktuellen Seite zugreifen.
 
 ## Alternative Frontmatter-Formate
 

From 3034c7bb39f23f36bd02df0a43716391ee3aa950 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:42 +0200
Subject: [PATCH 149/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/getting-started.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index ff3481883..9280738f9 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -45,7 +45,7 @@ $ deno add -D vitepress@next
 
 ::: tip Hinweis
 
-VitePress ist ein reines ESM-Paket. Verwende `require()` zum Importieren nicht `package.json` enthält `"type": "module"`, or change die Datei extension of your relevant files like `.vitepress/config.js` to `.mjs`/`.mts`. Weitere Informationen findest du in der [Vite's troubleshooting guide](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only) In asynchronen CJS-Kontexten kannst du außerdem stattdessen `await import('vitepress')` instead.
+VitePress ist ein reines ESM-Paket. Verwende `require()` nicht zum Importieren, es sei denn, `package.json` enthält `"type": "module"`. Alternativ kannst du die Dateiendung relevanter Dateien wie `.vitepress/config.js` in `.mjs`/`.mts` ändern. Weitere Informationen findest du in der [Fehlerbehebung von Vite](http://vite.dev/guide/troubleshooting.html#this-package-is-esm-only). In asynchronen CJS-Kontexten kannst du stattdessen `await import('vitepress')` verwenden.
 
 :::
 
@@ -101,12 +101,12 @@ Angenommen, du hast das VitePress-Projekt in `./docs`, Die erzeugte Dateistruktu
 Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionale Anpassungen des Themes reserviert.
 
 ::: tip
-Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. These locations can also be [konfiguriert](../reference/site-config#outdir).
+Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. Diese Verzeichnisse können ebenfalls [konfiguriert](../reference/site-config#outdir).
 :::
 
 ### Die Konfigurationsdatei
 
-Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. various aspects of your VitePress site, mit the most basic options being the title and description of the site:
+Die Konfigurationsdatei (`.vitepress/config.js`) ermöglicht es dir, verschiedene Aspekte deiner VitePress-Website anzupassen. Zu den grundlegenden Optionen gehören der Titel und die Beschreibung der Website:
 
 ```js [.vitepress/config.js]
 export default {
@@ -120,19 +120,19 @@ export default {
 }
 ```
 
-Du kannst das Verhalten des Themes außerdem über die `themeConfig` option. Eine vollständige Übersicht findest du in der [Config Referenz](../reference/site-config) for full details on all config options.
+Du kannst das Verhalten des Themes außerdem über die Option `themeConfig` anpassen. Eine vollständige Übersicht über alle Konfigurationsoptionen findest du in der [Referenz zur Konfiguration](../reference/site-config).
 
 ### Quelldateien
 
 Markdown-Dateien außerhalb des Verzeichnisses `.vitepress` gelten als **Quelldateien**.
 
-VitePress verwendet **file-based routing**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` in `index.html`, und kann über den Stammpfad `/` of the resulting VitePress site.
+VitePress verwendet **dateibasierte Routen**: Jede `.md`-Datei wird in eine entsprechende `.html`-Datei mit demselben Pfad kompiliert. Beispielsweise wird `index.md` zu `index.html` und kann über den Stammpfad `/` der daraus erzeugten VitePress-Website aufgerufen werden.
 
 VitePress bietet außerdem die Möglichkeit, saubere URLs zu erzeugen, Pfade umzuschreiben und Seiten dynamisch zu generieren. Diese Funktionen werden in der [Routing Anleitung](./routing).
 
 ## Loslegen
 
-Wenn du dies während der Einrichtung zugelassen hast, sollte das Tool außerdem die folgenden npm-Skripte in deine `package.json` wenn you allowed it to do so während the setup process:
+Wenn du dies während der Einrichtung zugelassen hast, sollte das Tool außerdem die folgenden npm-Skripte in deine `package.json` einfügen:
 
 ```json [package.json]
 {
@@ -192,7 +192,7 @@ $ bun vitepress dev docs
 
 Weitere Informationen zur Verwendung der Kommandozeile findest du in der [CLI Referenz](../reference/cli).
 
-The dev server should be running at `http://localhost:5173`. Öffne die URL in deinem Browser, um deine neue Website zu sehen.
+Der Entwicklungsserver sollte unter `http://localhost:5173` laufen. Öffne die URL in deinem Browser, um deine neue Website zu sehen.
 
 ## Wie geht es weiter?
 
@@ -202,6 +202,6 @@ The dev server should be running at `http://localhost:5173`. Öffne die URL in d
 
 - Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-theme-config).
 
-- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Extend the Standard-Theme](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
+- Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Standard-Theme erweitern](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
 
 - Sobald deine Dokumentations-Website Gestalt annimmt, solltest du die [Bereitstellung Anleitung](./deploy).

From 0757fa80a1fa25a455ed8a4496814162d7149ed8 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:08:45 +0200
Subject: [PATCH 150/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/using-vue.md | 34 +++++++++++++++++-----------------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index 736bdb981..3d0bd7226 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -1,22 +1,22 @@
 ---
-description: Vue Komponenten and dynamic templating features directly inside Markdown files in VitePress.
+description: Verwende Vue-Komponenten und dynamische Vorlagen direkt in Markdown-Dateien von VitePress.
 ---
 
 # Vue in Markdown verwenden
 
-In VitePress wird jede Markdown-Datei in HTML kompiliert und anschließend als [Vue Single-Datei Component](https://vuejs.org/guide/scaling-up/sfc.html). Das bedeutet you can use any Vue features inside the Markdown, including dynamic templating, Verwendung Vue Komponenten, or arbitrary in-page Vue Komponente logic by adding a `<script>` tag.
+In VitePress wird jede Markdown-Datei in HTML kompiliert und anschließend als [Vue-Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html) behandelt. Das bedeutet, dass du beliebige Vue-Funktionen innerhalb von Markdown verwenden kannst, einschließlich dynamischer Vorlagen, Vue-Komponenten oder beliebiger Vue-Logik innerhalb der Seite, indem du ein `<script>`-Tag hinzufügst.
 
-Beachte, dass VitePress leverages Vue's compiler to automatisch detect and optimize the purely static parts of the Markdown content. Static contents are optimized into single placeholder nodes and eliminated from the page's JavaScript payload for initial visits. They are also skipped during client-side hydration. Kurz gesagt betrifft der zusätzliche Aufwand nur die dynamischen Teile einer jeweiligen Seite.
+Beachte, dass VitePress den Vue-Compiler verwendet, um die rein statischen Teile des Markdown-Inhalts automatisch zu erkennen und zu optimieren. Statische Inhalte werden zu einzelnen Platzhalterknoten optimiert und bei ersten Besuchen aus der JavaScript-Nutzlast der Seite entfernt. Sie werden auch während der clientseitigen Hydration übersprungen. Kurz gesagt betrifft der zusätzliche Aufwand nur die dynamischen Teile der jeweiligen Seite.
 
 ::: tip SSR-Kompatibilität
-Jede Verwendung von Vue muss SSR-kompatibel sein. See [SSR-Kompatibilität](./ssr-compat) for details and common workarounds.
+Jede Verwendung von Vue muss SSR-kompatibel sein. Einzelheiten und gängige Lösungen findest du unter [SSR-Kompatibilität](./ssr-compat).
 :::
 
 ## Templating
 
 ### Interpolation
 
-Each Markdown file is first compiled into HTML and then passed on as a Vue Komponente to the Vite process pipeline. Das bedeutet you can use Vue-style interpolation in text:
+Jede Markdown-Datei wird zunächst in HTML kompiliert und anschließend als Vue-Komponente an die Vite-Prozesspipeline übergeben. Das bedeutet, dass du Vue-Interpolation in Text verwenden kannst:
 
 **Input**
 
@@ -42,9 +42,9 @@ Direktiven funktionieren ebenfalls (note that by design, raw HTML is also valid
 
 <div class="language-text"><pre><code><span v-for="i in 3">{{ i }} </span></code></pre></div>
 
-## `<script>` and `<style>`
+## `<script>` und `<style>`
 
-Root-level `<script>` and `<style>` tags in Markdown files work just like they do in Vue SFCs, including `<script setup>`, `<style module>`, etc. The main difference here is that there is no `<Vorlage>` tag: all other root-level content is Markdown. Also note that all tags should be placed **after** the frontmatter:
+Auf oberster Ebene verwendete `<script>`- und `<style>`-Tags in Markdown-Dateien funktionieren genauso wie in Vue-SFCs, einschließlich `<script setup>`, `<style module>` usw. Der wichtigste Unterschied besteht darin, dass es kein `<Vorlage>`-Tag gibt: Alle anderen Inhalte auf oberster Ebene sind Markdown. Beachte außerdem, dass alle Tags **nach** dem Frontmatter stehen sollten:
 
 ```html
 ---
@@ -57,7 +57,7 @@ import { ref } from 'vue'
 const count = ref(0)
 </script>
 
-## Markdown Content
+## Markdown-Inhalt
 
 The count is: {{ count }}
 
@@ -72,7 +72,7 @@ The count is: {{ count }}
 ```
 
 ::: warning Avoid `<style scoped>` in Markdown
-When verwendet in Markdown, `<style scoped>` requires adding special attributes to every element on the current page, which will significantly bloat the page size. `<style module>` is preferred when locally-scoped styling is needed in a page.
+Bei Verwendung in Markdown erfordert `<style scoped>` das Hinzufügen spezieller Attribute zu jedem Element der aktuellen Seite, wodurch die Seitengröße erheblich zunimmt. `<style module>` wird bevorzugt, wenn eine lokal begrenzte Gestaltung auf einer Seite benötigt wird.
 :::
 
 You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access to current page's metadata:
@@ -102,11 +102,11 @@ const { page } = useData()
 
 ## Komponenten verwenden
 
-Du kannst import and use Vue Komponenten directly in Markdown files.
+Du kannst Vue-Komponenten direkt in Markdown-Dateien importieren und verwenden.
 
 ### Importing in Markdown
 
-If a Komponente is only verwendet by a few pages, it's recommended to explicitly import them where they are verwendet. Dies ermöglicht them to be properly code-split and only geladen when the relevant pages are shown:
+Wenn eine Komponente nur auf wenigen Seiten verwendet wird, empfiehlt es sich, sie dort explizit zu importieren, wo sie verwendet wird. Dadurch kann sie korrekt aufgeteilt und nur geladen werden, wenn die entsprechenden Seiten angezeigt werden:
 
 ```md
 <script setup>
@@ -115,33 +115,33 @@ import CustomComponent from '../components/CustomComponent.vue'
 
 # Docs
 
-This is a .md using a custom component
+Dies ist eine .md-Datei, die eine benutzerdefinierte Komponente verwendet
 
 <CustomComponent />
 
-## More docs
+## Weitere Dokumentation
 
 ...
 ```
 
 ### Komponenten global registrieren
 
-If a Komponente is going to be verwendet on most of the pages, they can be registered globally by customizing the Vue app instance. See relevant section in [Extending Standard-Theme](./extending-default-theme#registering-global-Komponenten) for an example.
+Wenn eine Komponente auf den meisten Seiten verwendet werden soll, kann sie durch Anpassen der Vue-App-Instanz global registriert werden. Siehe den entsprechenden Abschnitt unter [Standard-Theme erweitern](./extending-default-theme#registering-global-Komponenten) for an example.
 
 ::: warning IMPORTANT
-Stelle sicher a custom Komponente's name either contains a hyphen or is in PascalCase. Otherwise, it will be treated as an inline element and wrapped inside a `<p>` tag, which will lead to hydration mismatch because `<p>` does not allow block elements to be placed inside it.
+Stelle sicher, dass der Name einer benutzerdefinierten Komponente entweder einen Bindestrich enthält oder in PascalCase geschrieben ist. Andernfalls wird sie als Inline-Element behandelt und in ein `<p>`-Tag eingeschlossen, was zu einer Abweichung bei der Hydration führt, da `<p>` keine Block-Elemente enthalten darf.
 :::
 
 ### Komponenten verwenden In Headers <ComponentInHeader />
 
-Du kannst use Vue Komponenten in the headers, but note the difference between the following syntaxes:
+Du kannst Vue-Komponenten in Überschriften verwenden, beachte jedoch den Unterschied zwischen den folgenden Syntaxvarianten:
 
 | Markdown                                                | Ausgabe HTML                               | Parsed Header |
 | ------------------------------------------------------- | ----------------------------------------- | ------------- |
 | <pre v-pre><code> # text &lt;Tag/&gt; </code></pre>     | `<h1>text <Tag/></h1>`                    | `text`        |
 | <pre v-pre><code> # text \`&lt;Tag/&gt;\` </code></pre> | `<h1>text <code>&lt;Tag/&gt;</code></h1>` | `text <Tag/>` |
 
-The HTML wrapped by `<code>` will be displayed as-is; only the HTML that is **not** wrapped will be parsed by Vue.
+Das von `<code>` umschlossene HTML wird unverändert angezeigt; nur HTML, das **nicht** umschlossen ist, wird von Vue analysiert.
 
 ::: tip
 The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and verwendet for both the sidebar and document title).

From 524a8b56370101fe4dfcbca22ac0cbb0a4ce20eb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:11 +0200
Subject: [PATCH 151/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/i18n.md | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/de/guide/i18n.md b/docs/de/guide/i18n.md
index 1e58dff46..5b139c05f 100644
--- a/docs/de/guide/i18n.md
+++ b/docs/de/guide/i18n.md
@@ -21,7 +21,7 @@ Dann in `docs/.vitepress/config.ts`:
 import { defineConfig } from 'vitepress'
 
 export default defineConfig({
-  // shared properties and other top-level stuff...
+  // Gemeinsame Eigenschaften und andere Inhalte auf oberster Ebene...
 
   locales: {
     root: {
@@ -30,8 +30,8 @@ export default defineConfig({
     },
     fr: {
       label: 'French',
-      lang: 'fr', // optional, will be added  as `lang` attribute on `html` tag
-      link: '/fr/guide' // default /fr/ -- shows on navbar translations menu, can be external
+      lang: 'fr', // optional, wird als `lang`-Attribut zum `html`-Tag hinzugefügt
+      link: '/fr/guide' // Standardwert /fr/ – wird im Übersetzungsmenü der Navigationsleiste angezeigt, kann extern sein
 
       // other locale specific properties...
     }
@@ -39,7 +39,7 @@ export default defineConfig({
 })
 ```
 
-The folgende properties can be overridden for jede locale (including root):
+Die folgenden Eigenschaften können für jede Spracheinstellung (einschließlich der Standardsprache) überschrieben werden:
 
 ```ts
 interface LocaleSpecificConfig<ThemeConfig = any> {
@@ -48,18 +48,18 @@ interface LocaleSpecificConfig<ThemeConfig = any> {
   title?: string
   titleTemplate?: string | boolean
   description?: string
-  head?: HeadConfig[] // will be merged with existing head entries, duplicate meta tags are automatically removed
-  themeConfig?: ThemeConfig // will be shallow merged, common stuff can be put in top-level themeConfig entry
+  head?: HeadConfig[] // wird mit vorhandenen head-Einträgen zusammengeführt, doppelte Meta-Tags werden automatisch entfernt
+  themeConfig?: ThemeConfig // wird flach zusammengeführt, gemeinsame Einstellungen können im themeConfig-Eintrag auf oberster Ebene angegeben werden
 }
 ```
 
-Refer [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-Theme.d.ts) interface for details on eigeneizing the placeholder texts of the Standard-Theme. Don't override `ThemeConfig.algolia` or `ThemeConfig.carbonAds` at locale-level. Refer [Algolia docs](../reference/default-Theme-search#algolia-search-i18n) for Verwendung multilingual search.
+Einzelheiten zum Anpassen der Platzhaltertexte des Standard-Themes findest du in der Schnittstelle [`DefaultTheme.Config`](https://github.com/vuejs/vitepress/blob/main/types/default-Theme.d.ts). Überschreibe `ThemeConfig.algolia` oder `ThemeConfig.carbonAds` nicht auf Sprachebene. Informationen zur Verwendung der mehrsprachigen Suche findest du in der [Algolia-Dokumentation](../reference/default-Theme-search#algolia-search-i18n).
 
 **Pro Tipp:** Die Konfigurationsdatei kann auch unter `docs/.vitepress/config/index.ts` gespeichert werden. Das kann bei der Organisation helfen, indem du eine Konfigurationsdatei pro Sprache erstellst und sie anschließend in `index.ts` zusammenführst und exportierst.
 
 ## Markdown-Zeichenketten pro Sprache
 
-Vom Markdown-Renderer in Seiten eingebettete Zeichenketten - the default titles of [eigene containers](./markdown#eigene-containers) and [GitHub-flavored alerts](./markdown#github-flavored-alerts), and the strings of the code copy button - können pro Sprache über den Schlüssel `markdown` eines Spracheintrags überschrieben werden:
+Vom Markdown-Renderer in Seiten eingebettete Zeichenketten – die Standardtitel der [benutzerdefinierten Container](./markdown#eigene-containers) und [GitHub-ähnlichen Hinweise](./markdown#github-flavored-alerts) sowie die Texte der Schaltfläche zum Kopieren von Code – können pro Sprache über den Schlüssel `markdown` eines Spracheintrags überschrieben werden:
 
 ```ts [docs/.vitepress/config.ts]
 import { defineConfig } from 'vitepress'
@@ -74,7 +74,7 @@ export default defineConfig({
         container: {
           tipLabel: '提示',
           warningLabel: '警告'
-          // ...the other labels, and titles of `customContainers`
+          // ...die anderen Beschriftungen und Titel von `customContainers`
         },
         codeCopyButton: {
           tooltipText: '复制代码',
@@ -90,7 +90,7 @@ Werte fallen auf die `markdown`-Optionen der obersten Ebene zurück, wenn eine S
 
 ## Separates Verzeichnis für jede Sprache
 
-The folgende is a perfectly fine structure:
+Die folgende Struktur ist vollständig gültig:
 
 ```
 docs/
@@ -143,7 +143,7 @@ watchEffect(() => {
 
 ## RTL-Unterstützung
 
-For right-to-left languages, set `dir: 'rtl'` in the config. The Standard-Theme is laid out mit [CSS logical properties](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_Werts), so the layout, the navigation and directional icons follow the dokumentieren direction on their own. No PostCSS plugin is needed; an RTLCSS plugin left in place would flip the mirrored styles a second time, so remove it.
+Für Sprachen mit Schreibrichtung von rechts nach links setze `dir: 'rtl'` in der Konfiguration. Das Standard-Theme verwendet [logische CSS-Eigenschaften](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_logical_properties_and_Werts), sodass Layout, Navigation und Richtungssymbole der dokumentierten Schreibrichtung automatisch folgen. Ein PostCSS-Plugin ist nicht erforderlich; ein vorhandenes RTLCSS-Plugin würde die bereits gespiegelten Stile ein zweites Mal umkehren und sollte daher entfernt werden.
 
 ```ts [docs/.vitepress/config.ts]
 export default {
@@ -152,9 +152,9 @@ export default {
 }
 ```
 
-For a multilingual site, set `dir` per locale in `locales`. It can außerdem be overridden for a single Seite mit the [`dir`](../reference/frontmatter-config#dir) frontmatter Option. Code blocks immer stay left-to-right.
+Bei einer mehrsprachigen Website setze `dir` pro Sprache in `locales`. Es kann außerdem für eine einzelne Seite mit der Frontmatter-Option [`dir`](../reference/frontmatter-config#dir) überschrieben werden. Codeblöcke bleiben immer von links nach rechts.
 
-Wenn adding your own styles, prefer logical properties wie `margin-inline-start` over `margin-left`, and mirror your own directional icons in right-to-left layouts:
+Wenn du eigene Stile hinzufügst, bevorzuge logische Eigenschaften wie `margin-inline-start` gegenüber `margin-left` und spiegle deine eigenen Richtungssymbole in Layouts mit Schreibrichtung von rechts nach links:
 
 ```css
 [dir='rtl'] .my-arrow-icon {

From 14914e0c561d84b26da73c845da4c5d24eb36cce Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:13 +0200
Subject: [PATCH 152/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/what-is-vitepress.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index 97f592668..eb95db662 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -1,10 +1,10 @@
 ---
-description: Ein statischer Website-Generazur zum Erstellen schneller, inhaltsorientierter Websites auf Basis von Vite und Vue.
+description: Ein statischer Website-Generator zum Erstellen schneller, inhaltsorientierter Websites auf Basis von Vite und Vue.
 ---
 
 # Was ist VitePress?
 
-VitePress ist ein [statischer Website-Generazur](https://en.wikipedia.org/wiki/Static_site_generazur) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
+VitePress ist ein [statischer Website-Generator](https://en.wikipedia.org/wiki/Static_site_generazur) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
 
 ::: tip {no-title}
 Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./getting-started).
@@ -14,15 +14,15 @@ Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./gettin
 
 - **Dokumentation**
 
-  VitePress enthält ein Stundard-Theme für technische Dokumentation. Es wird für diese Seite und unter underem für die Dokumentation von [Vite](https://vite.dev/), [Rollup](https://rollupjs.org/), [Pinia](https://pinia.vuejs.org/), [VueUse](https://vueuse.org/), [Vitest](https://vitest.dev/), [D3](https://d3js.org/), [UnoCSS](https://unocss.dev/), [Iconify](https://iconify.design/) und [many more](https://github.com/search?q=/%22vitepress%22:+/+path:/(?:package%7Cdeno)%5C.jsonc?$/+NOT+is:fork+NOT+is:archived&type=code).
+  VitePress enthält ein Standard-Theme für technische Dokumentation. Es wird für diese Seite und unter anderem für die Dokumentation von [Vite](https://vite.dev/), [Rollup](https://rollupjs.org/), [Pinia](https://pinia.vuejs.org/), [VueUse](https://vueuse.org/), [Vitest](https://vitest.dev/), [D3](https://d3js.org/), [UnoCSS](https://unocss.dev/), [Iconify](https://iconify.design/) und [viele weitere](https://github.com/search?q=/%22vitepress%22:+/+path:/(?:package%7Cdeno)%5C.jsonc?$/+NOT+is:fork+NOT+is:archived&type=code).
 
   Die [offizielle Vue.js-Dokumentation](https://vuejs.org/) basiert ebenfalls auf VitePress, verwendet jedoch ein eigenes Theme, das von mehreren Übersetzungen gemeinsam genutzt wird.
 
 - **Blogs, Portfolios und Marketing-Websites**
 
-  VitePress supports [fully cuszumized themes](./cuszum-theme), mit der Entwicklererfahrung einer normalen Vite- und Vue-Anwendung. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [Daten laden](./data-loading) (lokal oder entfernt) und [dynamische Routen erzeugen](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
+  VitePress unterstützt [vollständig angepasste Themes](./custom-theme) mit der Entwicklererfahrung einer normalen Vite- und Vue-Anwendung. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [Daten laden](./data-loading) (lokal oder entfernt) und [dynamische Routen erzeugen](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
 
-  Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) is a simple blog that generates its index page based on local content.
+  Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) ist ein einfacher Blog, der seine Indexseite auf Grundlage lokaler Inhalte erzeugt.
 
 ## Entwicklererfahrung
 
@@ -32,7 +32,7 @@ VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mi
 
 - **[Integrierte Markdown-Erweiterungen:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
 
-- **[Vue-erweitertes Markdown:](./using-vue)** jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html), thanks zu Vue template's 100% syntax compatibility with HTML. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
+- **[Vue-erweitertes Markdown:](./using-vue)** Jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html). Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
 
 ## Leistung
 
@@ -40,20 +40,20 @@ Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollst
 
 - **Schnelles erstes Laden**
 
-  The initial visit zu any page will be served the static, pre-rendered HTML for fast loading speed und optimal SEO. The page then loads a JavaScript bundle that turns the page inzu a Vue SPA ("hydration"). Contrary zu common assumptions of SPA hydration being slow, this process is actually extremely fast thanks zu Vue 3's raw performance und compiler optimizations. On [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F), typical VitePress sites achieve near-perfect performance scores even on low-end mobile devices with a slow network.
+  Beim ersten Aufruf einer beliebigen Seite wird statisches, vorgerendertes HTML ausgeliefert, um schnelle Ladezeiten und optimale SEO zu ermöglichen. Anschließend lädt die Seite ein JavaScript-Bundle, das die Seite in eine Vue-SPA („Hydration“) umwandelt. Entgegen der verbreiteten Annahme, dass die Hydration von SPAs langsam sei, ist dieser Vorgang dank der hohen Leistung von Vue 3 und der Compiler-Optimierungen sehr schnell. Auf [PageSpeed Insights](https://pagespeed.web.dev/report?url=https%3A%2F%2Fvitepress.dev%2F) erreichen typische VitePress-Websites selbst auf leistungsschwachen Mobilgeräten mit langsamer Verbindung nahezu perfekte Leistungswerte.
 
 - **Schnelle Navigation nach dem Laden**
 
-  More importantly, the SPA model leads zu better user experience **after** the initial load. Bei der weiteren Navigation innerhalb der Website wird die Seite nicht mehr vollständig neu geladen. Stattdessen wird der Inhalt der Zielseite abgerufen und dynamisch aktualisiert. VitePress also auzumatically pre-fetches page chunks for links that are within viewport. In most cases, post-load navigation will feel instant.
+  Noch wichtiger ist, dass das SPA-Modell **nach** dem ersten Laden zu einer besseren Benutzererfahrung führt. Bei der weiteren Navigation innerhalb der Website wird die Seite nicht mehr vollständig neu geladen. Stattdessen wird der Inhalt der Zielseite abgerufen und dynamisch aktualisiert. VitePress lädt außerdem automatisch Seitenabschnitte für Links vor, die sich im sichtbaren Bereich befinden. In den meisten Fällen fühlt sich die Navigation nach dem Laden sofort an.
 
 - **Interaktivität ohne Nachteile**
 
-  To be able zu hydrate the dynamic Vue parts embedded inside static Markdown, each Markdown page is processed as a Vue Komponente und compiled inzu JavaScript. This may sound inefficient, but the Vue compiler is smart enough zu separate the static und dynamic parts, minimizing both the hydration cost und payload size. For the initial page load, the static parts are auzumatically eliminated from the JavaScript payload und skipped during hydration.
+  Damit die in statisches Markdown eingebetteten dynamischen Vue-Teile hydratisiert werden können, wird jede Markdown-Seite als Vue-Komponente verarbeitet und in JavaScript kompiliert. Das mag ineffizient klingen, aber der Vue-Compiler kann statische und dynamische Teile voneinander trennen und dadurch sowohl die Kosten der Hydration als auch die Größe der Nutzlast minimieren. Beim ersten Laden der Seite werden die statischen Teile automatisch aus der JavaScript-Nutzlast entfernt und während der Hydration übersprungen.
 
 ## Und was ist mit VuePress?
 
-VitePress ist der Nachfolger von VuePress 1. Das ursprüngliche VuePress 1 basierte auf Vue 2 und webpack. With Vue 3 und Vite under the hood, VitePress provides significantly better DX, better production performance, a more polished default theme, und a more flexible cuszumization API.
+VitePress ist der Nachfolger von VuePress 1. Das ursprüngliche VuePress 1 basierte auf Vue 2 und webpack. Mit Vue 3 und Vite im Hintergrund bietet VitePress eine deutlich bessere Entwicklererfahrung, bessere Leistung in der Produktion, ein ausgereifteres Standard-Theme und eine flexiblere API zur Anpassung.
 
-The API difference between VitePress und VuePress 1 mostly lies in theming und cuszumization. If you are using VuePress 1 with the default theme, it should be relatively straightforward zu migrate zu VitePress.
+Die API-Unterschiede zwischen VitePress und VuePress 1 liegen hauptsächlich beim Theming und bei der Anpassung. Wenn du VuePress 1 mit dem Standard-Theme verwendest, sollte die Migration zu VitePress relativ unkompliziert sein.
 
-Maintaining two SSGs in parallel isn't sustainable, so the Vue team has decided zu focus on VitePress as the main recommended SSG in the long run. Now VuePress 1 has been deprecated, und VuePress 2 has been hunded over zu the VuePress community team for further development und maintenance.
+Die parallele Pflege zweier SSGs ist langfristig nicht sinnvoll. Daher hat das Vue-Team beschlossen, sich langfristig auf VitePress als empfohlenes SSG zu konzentrieren. VuePress 1 ist inzwischen veraltet, und VuePress 2 wurde zur weiteren Entwicklung und Pflege an das VuePress-Community-Team übergeben.

From 8259056e151dcbed73cab80b11ae4484064c1325 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:16 +0200
Subject: [PATCH 153/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/cli.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/cli.md b/docs/de/reference/cli.md
index a2ab098ea..a12547801 100644
--- a/docs/de/reference/cli.md
+++ b/docs/de/reference/cli.md
@@ -11,10 +11,10 @@ Starte den VitePress-Entwicklungsserver mit dem angegebenen Verzeichnis als Stam
 ### Verwendung
 
 ```sh
-# start in current directory, omitting `dev`
+# Start im aktuellen Verzeichnis, wobei `dev` weggelassen wird
 vitepress
 
-# start in sub directory
+# Start in einem Unterverzeichnis
 vitepress dev [root]
 ```
 
@@ -43,7 +43,7 @@ vitepress build [root]
 
 | Option                         | Beschreibung                                                                                                         |
 | ------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
-| `--mpa` (experimental)         | Im [MPA-Modus erstellen](../guide/mpa-mode) ohne clientseitige Hydration (`boolean`)                                    |
+| `--mpa` (experimentell)         | Im [MPA-Modus erstellen](../guide/mpa-mode) ohne clientseitige Hydration (`boolean`)                                    |
 | `--base <path>`                | Öffentlicher Basispfad (Standard: `/`) (`string`)                                                                          |
 | `--assetsBase <url>`           | URL-Präfix, von dem die erzeugten Assets ausgeliefert werden, z. B. ein CDN (`string`)                                              |
 | `--target <target>`            | Transpilierungsziel (Standard: `"modules"`) (`string`)                                                                  |
@@ -70,7 +70,7 @@ vitepress preview [root]
 
 ## `vitepress init`
 
-Starte den [Einrichtungsassistenten](../guide/getting-started#setup-wizard) in current directory.
+Starte den [Einrichtungsassistenten](../guide/getting-started#setup-wizard) im aktuellen Verzeichnis.
 
 ### Verwendung
 

From f5902e4ecb7fe1a1cf5e8e6096075ac421083501 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:50 +0200
Subject: [PATCH 154/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-config.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
index 8e8fa38a3..66343c858 100644
--- a/docs/de/reference/default-theme-config.md
+++ b/docs/de/reference/default-theme-config.md
@@ -27,7 +27,7 @@ export default {
 
 - Type: `boolean | ((data: VitePressData<DefaultTheme.Config>, route: Route, targetLocale: string) => string)`
 
-Changing locale to say `zh` will change the URL from `/foo` (or `/en/foo/`) to `/zh/foo`. Du kannst disable this behavior by setting `themeConfig.i18nRouting` to `false`.
+Wenn du die Sprache beispielsweise auf `zh` änderst, ändert sich die URL von `/foo` (oder `/en/foo/`) zu `/zh/foo`. Du kannst dieses Verhalten deaktivieren, indem du `themeConfig.i18nRouting` auf `false` setzt.
 
 Setze `themeConfig.i18nRouting` auf eine Funktion, um den Sprachlink anzupassen. Die Funktion erhält die aktuellen VitePress-Daten, die aktuelle Route und den Schlüssel der Zielsprache und gibt den Ziellink zurück.
 
@@ -162,12 +162,12 @@ export interface SidebarMulti {
 
 export type SidebarItem = {
   /**
-   * The text label of the item.
+   * Die Textbeschriftung des Eintrags.
    */
   text?: string
 
   /**
-   * The link of the item.
+   * Der Link des Eintrags.
    */
   link?: string
 

From 9001d11ec10858300c78c4d5362ac2ebedd65711 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:52 +0200
Subject: [PATCH 155/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-edit-link.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/reference/default-theme-edit-link.md b/docs/de/reference/default-theme-edit-link.md
index 40131aefa..2e2b3edf9 100644
--- a/docs/de/reference/default-theme-edit-link.md
+++ b/docs/de/reference/default-theme-edit-link.md
@@ -20,7 +20,7 @@ export default {
 
 Die Option `pattern` definiert die URL-Struktur des Links. `:path` wird durch den Seitenpfad ersetzt.
 
-Du kannst also put a pure function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the URL string.
+Du kannst auch eine reine Funktion angeben, die [`PageData`](./runtime-api#usedata) als Argument akzeptiert und die URL als Zeichenkette zurückgibt.
 
 ```js
 export default {

From ae244c5f5f383c1bd48b03c89c573e55abe2ecf0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:55 +0200
Subject: [PATCH 156/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-footer.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-footer.md b/docs/de/reference/default-theme-footer.md
index 2c0e95021..d7c693ed3 100644
--- a/docs/de/reference/default-theme-footer.md
+++ b/docs/de/reference/default-theme-footer.md
@@ -41,14 +41,14 @@ export default {
 ```
 
 ::: warning
-In `message` und `copyright` können nur Inline-Elemente verwendet werden, da sie innerhalb eines `<p>`-Elements gerendert werden. Wenn du want to add block elements, consider using [`layout-bottom`](../guide/extending-Standard-theme#layout-slots) slot instead.
+In `message` und `copyright` können nur Inline-Elemente verwendet werden, da sie innerhalb eines `<p>`-Elements gerendert werden. Wenn du Block-Elemente hinzufügen möchtest, verwende stattdessen den Slot [`layout-bottom`](../guide/extending-Standard-theme#layout-slots).
 :::
 
-Hinweis that footer will not be displayed when the [SideBar](./Standard-theme-sidebar) is visible.
+Beachte, dass die Fußzeile nicht angezeigt wird, wenn die [Seitenleiste](./Standard-theme-sidebar) sichtbar ist.
 
 ## Frontmatter-Konfiguration
 
-Dies can be deaktiviert per-page using the `footer` option on frontmatter:
+Dies kann pro Seite über die `footer`-Option im Frontmatter deaktiviert werden:
 
 ```yaml
 ---

From 38ca52c2a2b872ad8e36dd51535ea11def063a01 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:57 +0200
Subject: [PATCH 157/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-home-page.md | 22 ++++++++++----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/de/reference/default-theme-home-page.md b/docs/de/reference/default-theme-home-page.md
index 914af76ac..e235ff065 100644
--- a/docs/de/reference/default-theme-home-page.md
+++ b/docs/de/reference/default-theme-home-page.md
@@ -4,7 +4,7 @@ description: Konfiguriere das Startseitenlayout des VitePress-Standard-Themes mi
 
 # Startseite
 
-VitePress Standard theme provides a homepage layout, which you can also see used on [the homepage of this site](../). Du kannst use it on any of your pages by specifying `layout: home` in the [frontmatter](./frontmatter-config).
+Das VitePress-Standard-Theme stellt ein Startseitenlayout bereit, das du auch auf [der Startseite dieser Website](../) sehen kannst. Du kannst es auf jeder deiner Seiten verwenden, indem du `layout: home` im [Frontmatter](./frontmatter-config) angibst.
 
 ```yaml
 ---
@@ -41,21 +41,21 @@ hero:
 
 ```ts
 interface Hero {
-  // The string shown top of `text`. Comes with brand color
-  // and expected to be short, such as product name.
+  // Die Zeichenkette, die oberhalb von `text` angezeigt wird. Verwendet die Markenfarbe
+  // Sie sollte kurz sein, beispielsweise der Produktname.
   name?: string
 
-  // The main text for the hero section. This will be defined
+  // Der Haupttext des Hero-Bereichs. Dieser wird definiert
   // as `h1` tag.
   text: string
 
-  // Tagline displayed below `text`.
+  // Unter `text` angezeigter Untertitel.
   tagline?: string
 
-  // The image is displayed next to the text and tagline area.
+  // Das Bild wird neben dem Text- und Untertitelbereich angezeigt.
   image?: ThemeableImage
 
-  // Action buttons to display in home hero section.
+  // Aktionsschaltflächen, die im Hero-Bereich der Startseite angezeigt werden.
   actions?: HeroAction[]
 }
 
@@ -65,16 +65,16 @@ type ThemeableImage =
   | { light: string; dark: string; alt?: string }
 
 interface HeroAction {
-  // Color theme of the button. Defaults to `brand`.
+  // Farbvariante der Schaltfläche. Standardmäßig `brand`.
   theme?: 'brand' | 'alt'
 
-  // Label of the button.
+  // Beschriftung der Schaltfläche.
   text: string
 
-  // Destination link of the button.
+  // Ziellink der Schaltfläche.
   link: string
 
-  // Link target attribute.
+  // Zielattribut des Links.
   target?: string
 
   // Link rel attribute.

From 7953386ea2b264ca7debc271fa0d424351d1b133 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:09:59 +0200
Subject: [PATCH 158/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-last-updated.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-last-updated.md b/docs/de/reference/default-theme-last-updated.md
index a57e1ae55..6b5ba460b 100644
--- a/docs/de/reference/default-theme-last-updated.md
+++ b/docs/de/reference/default-theme-last-updated.md
@@ -9,7 +9,7 @@ Der Aktualisierungszeitpunkt des letzten Inhalts wird unten rechts auf der Seite
 ::: info
 VitePress zeigt den Zeitpunkt der letzten Aktualisierung anhand des Zeitstempels des neuesten Git-Commits für jede Datei an. Dafür muss die Markdown-Datei in Git committed sein.
 
-Internally, VitePress runs `git log -1 --pretty="%ai"` on each file to retrieve its timestamp. If all pages show the same update time, it's likely due to shallow cloning (common in CI environments), which limits Git history.
+Intern führt VitePress für jede Datei `git log -1 --pretty="%ai"` aus, um den Zeitstempel abzurufen. Wenn alle Seiten dieselbe Aktualisierungszeit anzeigen, liegt dies wahrscheinlich an einem flachen Klonen (häufig in CI-Umgebungen), das den Git-Verlauf begrenzt.
 
 To fix this in **GitHub Actions**, use the following in your workflow:
 
@@ -39,7 +39,7 @@ export default {
 
 ## Frontmatter-Konfiguration
 
-Dies can be deaktiviert per-page using the `lastUpdated` option on frontmatter:
+Dies kann pro Seite über die `lastUpdated`-Option im Frontmatter deaktiviert werden:
 
 ```yaml
 ---
@@ -47,4 +47,4 @@ lastUpdated: false
 ---
 ```
 
-Weitere Informationen findest du unter [Standard-Theme: Letzte Aktualisierung](./Standard-theme-config#lastupdated) for more details. Any truthy value at theme-level will also enable the feature unless explicitly deaktiviert at site or page level.
+Weitere Informationen findest du unter [Standard-Theme: Letzte Aktualisierung](./Standard-theme-config#lastupdated). Jeder als wahr ausgewertete Wert auf Theme-Ebene aktiviert die Funktion ebenfalls, sofern sie nicht ausdrücklich auf Website- oder Seitenebene deaktiviert wird.

From 85c64f43f4a86f2f31cd6e6389def7fa945f6fca Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:01 +0200
Subject: [PATCH 159/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-layout.md | 24 +++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/docs/de/reference/default-theme-layout.md b/docs/de/reference/default-theme-layout.md
index a6321d1f2..66c38bd17 100644
--- a/docs/de/reference/default-theme-layout.md
+++ b/docs/de/reference/default-theme-layout.md
@@ -1,10 +1,10 @@
 ---
-description: Choose between doc, page, and home layouts in the VitePress default theme.
+description: Wähle zwischen den Layouts doc, page und home im VitePress-Standard-Theme.
 ---
 
 # Layout
 
-Du kannst choose the page layout by setting `layout` option to the page [frontmatter](./frontmatter-config). There are 3 layout options, `doc`, `page`, and `home`. If nothing is specified, then the page is treated as `doc` page.
+Du kannst das Seitenlayout auswählen, indem du die Option `layout` im [Frontmatter](./frontmatter-config) der Seite setzt. Es gibt drei Layoutoptionen: `doc`, `page` und `home`. Wenn nichts angegeben ist, wird die Seite als `doc`-Seite behandelt.
 
 ```yaml
 ---
@@ -14,11 +14,11 @@ layout: doc
 
 ## Doc Layout
 
-Option `doc` is the default layout and it styles the whole Markdown content into "documentation" look. It works by wrapping whole content within `vp-doc` css class, and applying styles to elements underneath it.
+Die Option `doc` ist das Standardlayout. Sie gestaltet den gesamten Markdown-Inhalt im Stil einer „Dokumentation“, indem der gesamte Inhalt in die CSS-Klasse `vp-doc` eingeschlossen und auf die darin enthaltenen Elemente entsprechende Stile angewendet werden.
 
-Almost all generic elements such as `p`, or `h2` get special styling. Therefore, keep in mind that if you add any custom HTML inside a Markdown content, those will get affected by those styles as well.
+Nahezu alle allgemeinen Elemente wie `p` oder `h2` erhalten eine spezielle Gestaltung. Beachte daher, dass auch benutzerdefiniertes HTML innerhalb eines Markdown-Inhalts von diesen Stilen betroffen ist.
 
-It also stellt bereit documentation specific features listed below. These features are only aktiviert in this layout.
+Außerdem stellt dieses Layout die unten aufgeführten dokumentationsspezifischen Funktionen bereit. Diese Funktionen sind nur in diesem Layout aktiviert.
 
 - Bearbeitungslink
 - Prev Weiter Link
@@ -27,23 +27,23 @@ It also stellt bereit documentation specific features listed below. These featur
 
 ## Seite Layout
 
-Option `page` is treated as "blank page". The Markdown will still be parsed, and all of the [Markdown Extensions](../guide/markdown) work as same as `doc` layout, but it wouldn't get any default stylings.
+Die Option `page` wird als „leere Seite“ behandelt. Das Markdown wird weiterhin analysiert und alle [Markdown-Erweiterungen](../guide/markdown) funktionieren wie beim `doc`-Layout, erhalten jedoch keine Standardgestaltung.
 
-The page layout will let you style everything by you without VitePress theme affecting the markup. This is useful when you want to create your own custom page.
+Mit dem Seitenlayout kannst du alles selbst gestalten, ohne dass das VitePress-Theme das Markup beeinflusst. Das ist nützlich, wenn du eine eigene Seite erstellen möchtest.
 
-Beachte, dass even in this layout, sidebar will still show up if the page has a matching sidebar config.
+Beachte, dass auch in diesem Layout die Seitenleiste angezeigt wird, wenn für die Seite eine passende Seitenleistenkonfiguration vorhanden ist.
 
 ## Home Layout
 
-Option `home` will generate templated "Homepage". In this layout, you can set extra options such as `hero` and `features` to customize the content further. Please visit [Standard-Theme: Startseite](./default-theme-home-page) for more details.
+Die Option `home` erzeugt eine vorgefertigte „Startseite“. In diesem Layout kannst du zusätzliche Optionen wie `hero` und `features` festlegen, um den Inhalt weiter anzupassen. Weitere Informationen findest du unter [Standard-Theme: Startseite](./default-theme-home-page).
 
 ## No Layout
 
-Wenn du don't want any layout, you can pass `layout: false` through frontmatter. This option is helpful if you want a fully-customizable landing page (without any sidebar, navbar, or footer by default).
+Wenn du kein Layout möchtest, kannst du über das Frontmatter `layout: false` angeben. Diese Option ist hilfreich, wenn du eine vollständig anpassbare Einstiegsseite ohne standardmäßige Seitenleiste, Navigationsleiste oder Fußzeile erstellen möchtest.
 
 ## Eigenes Layout
 
-Du kannst also use a custom layout:
+Du kannst auch ein eigenes Layout verwenden:
 
 ```md
 ---
@@ -51,7 +51,7 @@ layout: foo
 ---
 ```
 
-This will look for a component named `foo` registered in context. Zum Beispiel, you can register your component globally in `.vitepress/theme/index.ts`:
+Dadurch wird nach einer im Kontext registrierten Komponente namens `foo` gesucht. Zum Beispiel kannst du deine Komponente global in `.vitepress/theme/index.ts` registrieren:
 
 ```ts
 import DefaultTheme from 'vitepress/theme'

From 4fcc0c2e0c5147efc78c779dccdfd206f47021b8 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:03 +0200
Subject: [PATCH 160/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-nav.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/de/reference/default-theme-nav.md b/docs/de/reference/default-theme-nav.md
index 8e4e94a6e..70817a61f 100644
--- a/docs/de/reference/default-theme-nav.md
+++ b/docs/de/reference/default-theme-nav.md
@@ -1,14 +1,14 @@
 ---
-description: Konfiguriere die navigation bar in the VitePress default theme including site title, logo, and menu links.
+description: Konfiguriere die Navigationsleiste im VitePress-Standard-Theme einschließlich Seitentitel, Logo und Menülinks.
 ---
 
 # Nav
 
 Die Navigation ist die oben auf der Seite angezeigte Navigationsleiste. Sie enthält den Seitentitel, globale Menülinks usw.
 
-## Site Title and Logo
+## Seitentitel und Logo
 
-Standardmäßig, nav shows the title of the site referencing [`config.title`](./site-config#title) value. Wenn du die Anzeige in der Navigation ändern möchtest, kannst du einen eigenen Text in `themeConfig.siteTitle` option.
+Standardmäßig zeigt die Navigation den Titel der Website anhand des Werts [`config.title`](./site-config#title) an. Wenn du die Anzeige in der Navigation ändern möchtest, kannst du einen eigenen Text über die Option `themeConfig.siteTitle` festlegen.
 
 ```js
 export default {
@@ -28,7 +28,7 @@ export default {
 }
 ```
 
-Beim Hinzufügen eines Logos wird es zusammen mit dem Seitentitel angezeigt. If your logo is all you need and if you would like to hide the site title text, set `false` to the `siteTitle` option.
+Beim Hinzufügen eines Logos wird es zusammen mit dem Seitentitel angezeigt. Wenn du nur das Logo benötigst und den Seitentitel ausblenden möchtest, setze die Option `siteTitle` auf `false`.
 
 ```js
 export default {
@@ -39,7 +39,7 @@ export default {
 }
 ```
 
-Du kannst als Logo auch ein Objekt übergeben, wenn du ein `alt`-Attribut hinzufügen oder es abhängig vom Hell-/Dunkelmodus anpassen möchtest. Refer [`themeConfig.logo`](./default-theme-config#logo) for details.
+Du kannst als Logo auch ein Objekt übergeben, wenn du ein `alt`-Attribut hinzufügen oder es abhängig vom Hell-/Dunkelmodus anpassen möchtest. Einzelheiten findest du unter [`themeConfig.logo`](./default-theme-config#logo).
 
 ## Navigation Links
 
@@ -59,7 +59,7 @@ export default {
 
 `text` ist der tatsächlich angezeigte Text in der Navigation, und `link` ist das Ziel, das beim Anklicken des Textes geöffnet wird. Setze beim Link den Pfad zur tatsächlichen Datei ohne `.md` und beginne immer mit `/`.
 
-The `link` can also be a function that accepts [`PageData`](./runtime-api#usedata) as the argument and gibt zurück the path.
+Der `link` kann auch eine Funktion sein, die [`PageData`](./runtime-api#usedata) als Argument akzeptiert und den Pfad zurückgibt.
 
 Navigationslinks können auch Dropdown-Menüs sein. Setze dazu den Schlüssel `items` in der Link-Option.
 
@@ -81,9 +81,9 @@ export default {
 }
 ```
 
-Beachte, dass der Titel des Dropdown-Menüs (`Dropdown Menu` in the above example) keine Eigenschaft `link` besitzen kann, da er zu einer Schaltfläche zum Öffnen des Dropdowns wird.
+Beachte, dass der Titel des Dropdown-Menüs (`Dropdown Menu` im obigen Beispiel) keine Eigenschaft `link` besitzen kann, da er zu einer Schaltfläche zum Öffnen des Dropdowns wird.
 
-Du kannst den Dropdown-Menüeinträgen außerdem weitere „Abschnitte“ hinzufügen by passing in more nested items.
+Du kannst den Dropdown-Menüeinträgen außerdem weitere „Abschnitte“ hinzufügen, indem du weitere verschachtelte Einträge angibst.
 
 ```js
 export default {

From 6d5b1d239e04f70197e0a4b94ddce3fd97196126 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:05 +0200
Subject: [PATCH 161/199] =?UTF-8?q?docs(de):=20Referenzseiten=20vollst?=
 =?UTF-8?q?=C3=A4ndig=20eindeutschen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-prev-next-links.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/reference/default-theme-prev-next-links.md b/docs/de/reference/default-theme-prev-next-links.md
index 56f846a7c..9a0c30144 100644
--- a/docs/de/reference/default-theme-prev-next-links.md
+++ b/docs/de/reference/default-theme-prev-next-links.md
@@ -4,7 +4,7 @@ description: Passe die am unteren Rand von Dokumentationsseiten in VitePress ang
 
 # Prev Weiter Links
 
-Du kannst Text und Link für die vorherige und nächste Seite anpassen (shown at doc footer). This is helpful if you want a different text there than what you have on your sidebar. Additionally, you may find it useful to disable the footer or link to a page that is not included in your sidebar.
+Du kannst Text und Link für die vorherige und nächste Seite anpassen (sie werden am Ende der Dokumentationsseite angezeigt). Das ist hilfreich, wenn du dort einen anderen Text als in deiner Seitenleiste verwenden möchtest. Außerdem kann es nützlich sein, die Fußzeile zu deaktivieren oder auf eine Seite zu verlinken, die nicht in deiner Seitenleiste enthalten ist.
 
 ## prev
 
@@ -12,7 +12,7 @@ Du kannst Text und Link für die vorherige und nächste Seite anpassen (shown at
 
 - Details:
 
-  Specifies the text/link to show on the link to the previous page. Wenn du don't set this in frontmatter, the text/link will be inferred from the sidebar config.
+  Legt den Text/Link fest, der für den Link zur vorherigen Seite angezeigt wird. Wenn du dies im Frontmatter nicht festlegst, werden Text und Link aus der Seitenleistenkonfiguration abgeleitet.
 
 - Beispiele:
 

From ec59f40d3f7e8210ac9cbea30713ce29f1a09f61 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:27 +0200
Subject: [PATCH 162/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-search.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/reference/default-theme-search.md b/docs/de/reference/default-theme-search.md
index d6b5fe39d..d695a2c7b 100644
--- a/docs/de/reference/default-theme-search.md
+++ b/docs/de/reference/default-theme-search.md
@@ -7,7 +7,7 @@ description: Richte eine lokale oder von Algolia bereitgestellte Suche für dein
 
 ## Lokale Suche
 
-VitePress unterstützt eine unscharfe Volltextsuche mithilfe eines Index im Browser dank [minisearch](https://github.com/lucaong/minisearch/). Um diese Funktion zu aktivieren, setze einfach the `themeConfig.search.provider` option to `'local'` in your `.vitepress/config.ts` file:
+VitePress unterstützt eine unscharfe Volltextsuche mithilfe eines Index im Browser dank [minisearch](https://github.com/lucaong/minisearch/). Um diese Funktion zu aktivieren, setze einfach die Option `themeConfig.search.provider` in deiner Datei `.vitepress/config.ts` auf `'local'`:
 
 ```ts
 import { defineConfig } from 'vitepress'
@@ -25,7 +25,7 @@ Beispielergebnis:
 
 ![screenshot of the search modal](/search.png)
 
-Alternatively, you can use [Algolia DocSearch](#algolia-search) or some community plugins like:
+Alternativ kannst du [Algolia DocSearch](#algolia-search) oder Community-Plugins verwenden, zum Beispiel:
 
 - <https://npmx.dev/package/vitepress-plugin-pagefind>
 - <https://npmx.dev/package/vitepress-plugin-typesense>
@@ -33,7 +33,7 @@ Alternatively, you can use [Algolia DocSearch](#algolia-search) or some communit
 
 <!-- - <https://npmx.dev/package/@orama/plugin-vitepress> -- replace with zbsearch one when published -->
 
-### i18n {#local-search-i18n}
+### Internationalisierung {#local-search-i18n}
 
 Du kannst eine Konfiguration wie diese verwenden, um eine mehrsprachige Suche einzurichten:
 
@@ -113,7 +113,7 @@ export default defineConfig({
 Weitere Informationen findest du in der [MiniSearch-Dokumentation](https://lucaong.github.io/minisearch/classes/MiniSearch.MiniSearch.html).
 
 ::: info Document IDs
-Die Dokument-IDs der Suche (wie sie von `searchOptions.filter`, `boostDocument`, and in the raw index) are site-relative paths like `/guide/page.html#section` — they enthalten nicht [`base`](../reference/site-config#base). Das Theme löst sie beim Rendern der Ergebnisse gegen `base` auf.
+Die Dokument-IDs der Suche (wie sie von `searchOptions.filter`, `boostDocument` und im rohen Index verwendet werden) sind relative Pfade innerhalb der Website wie `/guide/page.html#section` – sie enthalten nicht [`base`](../reference/site-config#base). Das Theme löst sie beim Rendern der Ergebnisse gegen `base` auf.
 :::
 
 ### Eigenen Inhalts-Renderer
@@ -144,9 +144,9 @@ export default defineConfig({
 
 Diese Funktion wird aus den clientseitigen Websitedaten entfernt, sodass du darin Node.js-APIs verwenden kannst.
 
-#### Beispiel: Excluding pages from search
+#### Beispiel: Seiten aus der Suche ausschließen
 
-Du kannst Seiten aus der Suche ausschließen by adding `search: false` to the frontmatter of the page. Alternativ:
+Du kannst Seiten aus der Suche ausschließen, indem du `search: false` in das Frontmatter der Seite einfügst. Alternativ:
 
 ```ts
 import { defineConfig } from 'vitepress'

From 0f3ef3cfbb9bae570b176e0ae36c00714a0fe58d Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:29 +0200
Subject: [PATCH 163/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-sidebar.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/reference/default-theme-sidebar.md b/docs/de/reference/default-theme-sidebar.md
index c51399021..cafaa6058 100644
--- a/docs/de/reference/default-theme-sidebar.md
+++ b/docs/de/reference/default-theme-sidebar.md
@@ -1,5 +1,5 @@
 ---
-description: Konfiguriere die sidebar navigation in the VitePress default theme with groups, collapsible sections, and multiple sidebars.
+description: Konfiguriere die Seitenleistennavigation im VitePress-Standard-Theme mit Gruppen, einklappbaren Abschnitten und mehreren Seitenleisten.
 ---
 
 # Seitenleiste
@@ -23,9 +23,9 @@ export default {
 }
 ```
 
-## The Basics
+## Grundlagen
 
-Die einfachste Form des Seitenleistenmenüs besteht aus einem einzelnen Array von Links. Das Element der ersten Ebene definiert den „Abschnitt“ der Seitenleiste. It should contain `text`, which is the title of the section, and `items` which are the actual navigation links.
+Die einfachste Form des Seitenleistenmenüs besteht aus einem einzelnen Array von Links. Das Element der ersten Ebene definiert den „Abschnitt“ der Seitenleiste. Es sollte `text`, den Titel des Abschnitts, und `items`, die eigentlichen Navigationslinks, enthalten.
 
 ```js
 export default {
@@ -52,7 +52,7 @@ export default {
 }
 ```
 
-Each `link` should specify the path to the actual file starting with `/`. Wenn du add trailing slash to the end of link, it will show `index.md` of the corresponding directory.
+Jeder `link` sollte den Pfad zur tatsächlichen Datei angeben und mit `/` beginnen. Wenn du am Ende des Links einen abschließenden Schrägstrich hinzufügst, wird `index.md` des entsprechenden Verzeichnisses angezeigt.
 
 ```js
 export default {
@@ -70,7 +70,7 @@ export default {
 }
 ```
 
-Du kannst further nest the sidebar items up to 6 level deep counting up from the root level. Beachte, dass deeper than 6 level of nested items gets ignored and will not be displayed on the sidebar.
+Du kannst die Seitenleisteneinträge bis zu sechs Ebenen tief verschachteln, ausgehend von der obersten Ebene. Beachte, dass Verschachtelungen mit mehr als sechs Ebenen ignoriert und nicht in der Seitenleiste angezeigt werden.
 
 ```js
 export default {
@@ -99,9 +99,9 @@ export default {
 
 ## Multiple Sidebars
 
-Du kannst show different sidebar depending on the page path. Zum Beispiel, as shown on this site, you might want to create a separate sections of content in your documentation like "Guide" page and "Config" page.
+Du kannst abhängig vom Seitenpfad unterschiedliche Seitenleisten anzeigen. Zum Beispiel möchtest du in deiner Dokumentation möglicherweise separate Inhaltsbereiche wie eine „Anleitung“-Seite und eine „Konfiguration“-Seite erstellen.
 
-To do so, first organize your pages into directories for each desired section:
+Ordne dazu zunächst deine Seiten in Verzeichnissen für die gewünschten Abschnitte an:
 
 ```
 .

From aaa7a99eae1d00556ca4ee2c9c610d8dd6c7de61 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:31 +0200
Subject: [PATCH 164/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-carbon-ads.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-carbon-ads.md b/docs/de/reference/default-theme-carbon-ads.md
index 97c5e5fa9..f49aabd30 100644
--- a/docs/de/reference/default-theme-carbon-ads.md
+++ b/docs/de/reference/default-theme-carbon-ads.md
@@ -4,7 +4,7 @@ description: Integriere Carbon Ads mithilfe der integrierten Unterstützung des
 
 # Carbon Ads
 
-VitePress has built in native support for [Carbon Ads](https://www.carbonads.net/). Wenn du die Carbon-Ads-Zugangsdaten in der Konfiguration definierst, zeigt VitePress Anzeigen auf der Seite an.
+VitePress bietet integrierte Unterstützung für [Carbon Ads](https://www.carbonads.net/). Wenn du die Carbon-Ads-Zugangsdaten in der Konfiguration definierst, zeigt VitePress Anzeigen auf der Seite an.
 
 ```js
 export default {
@@ -20,10 +20,10 @@ export default {
 
 Diese Werte werden verwendet, um das Carbon-CDN-Skript wie unten gezeigt aufzurufen.
 
-The `format` option supports `classic`, `responsive`, and `cover`.
+Die Option `format` unterstützt `classic`, `responsive` und `cover`.
 
 ```js
 `//cdn.carbonads.com/carbon.js?serve=${code}&placement=${placement}&format=${format}`
 ```
 
-To learn more about Carbon Ads Konfiguration, please visit [Carbon Ads website](https://www.carbonads.net/).
+Weitere Informationen zur Konfiguration von Carbon Ads findest du auf der [Carbon-Ads-Website](https://www.carbonads.net/).

From a35260de4192f26db1e1770eca1b365d6294b1f9 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:34 +0200
Subject: [PATCH 165/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/frontmatter-config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/reference/frontmatter-config.md b/docs/de/reference/frontmatter-config.md
index 134f79e2f..df836737f 100644
--- a/docs/de/reference/frontmatter-config.md
+++ b/docs/de/reference/frontmatter-config.md
@@ -11,7 +11,7 @@ Beispiel usage:
 
 ```md
 ---
-title: Docs with VitePress
+title: Dokumentation mit VitePress
 editLink: true
 ---
 ```
@@ -43,7 +43,7 @@ Suffix für den Titel. Entspricht [config.titleTemplate](./site-config#titletemp
 ```yaml
 ---
 title: VitePress
-titleTemplate: Vite & Vue powered static site generator
+titleTemplate: Statischer Website-Generator auf Basis von Vite und Vue
 ---
 ```
 

From 0ba1a2e8fcf2410689a043b15de207dac9e28a62 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:10:37 +0200
Subject: [PATCH 166/199] =?UTF-8?q?docs(de):=20Denglische=20=C3=9Cbersetzu?=
 =?UTF-8?q?ngen=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/site-config.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
index 52fe22a98..8bcee2848 100644
--- a/docs/de/reference/site-config.md
+++ b/docs/de/reference/site-config.md
@@ -3,7 +3,7 @@ outline: deep
 description: Vollständige Referenz der VitePress-Website-Konfigurationsoptionen einschließlich Einstellungen auf Anwendungsebene, Theme-Konfiguration und Build-Optionen.
 ---
 
-# Site-Konfiguration
+# Website-Konfiguration
 
 In der Website-Konfiguration definierst du die globalen Einstellungen der Website. Konfigurationsoptionen auf Anwendungsebene gelten für jede VitePress-Website, unabhängig vom verwendeten Theme. Zum Beispiel das Basisverzeichnis oder den Titel der Website.
 
@@ -41,7 +41,7 @@ export default async () => {
     title: 'VitePress',
     description: 'Vite & Vue powered static site generator.',
 
-    // theme level config options
+    // Konfigurationsoptionen auf Theme-Ebene
     themeConfig: {
       sidebar: [
         ...posts.map((post) => ({
@@ -67,7 +67,7 @@ export default defineConfig({
   title: 'VitePress',
   description: 'Vite & Vue powered static site generator.',
 
-  // theme level config options
+  // Konfigurationsoptionen auf Theme-Ebene
   themeConfig: {
     sidebar: [
       ...posts.map((post) => ({
@@ -102,7 +102,7 @@ import { defineConfig } from 'vitepress'
 
 export default defineConfig({
   themeConfig: {
-    // Type is `DefaultTheme.Config`
+    // Typ ist `DefaultTheme.Config`
   }
 })
 ```

From c026ea46c4969b1487d5d78290f1776143378292 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:14 +0200
Subject: [PATCH 167/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/asset-handling.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/asset-handling.md b/docs/de/guide/asset-handling.md
index 8f2c4d17d..f067a883c 100644
--- a/docs/de/guide/asset-handling.md
+++ b/docs/de/guide/asset-handling.md
@@ -60,7 +60,7 @@ const { theme } = useData()
 
 ## Assets über ein CDN ausliefern
 
-Um generierte Assets – Skripte, Styles, Schriftarten und aus Markdown oder Komponenten importierte Bilder – von einer anderen Origin als den Seiten auszuliefern, setze [\`assetsBase\`](../reference/site-config#assetsbase):
+Um generierte Assets – Skripte, Styles, Schriftarten und aus Markdown oder Komponenten importierte Bilder – von einer anderen Herkunft als den Seiten auszuliefern, setze [\`assetsBase\`](../reference/site-config#assetsbase):
 
 \`\`\`ts
 export default {
@@ -69,7 +69,7 @@ export default {
 }
 \`\`\`
 
-Lade das Verzeichnis \`assets\` aus dem Build-Ausgabeverzeichnis auf das CDN hoch, sodass es unter \`https://cdn.example.com/assets/\` erreichbar ist, und stelle den restlichen Output wie gewohnt auf deiner Website bereit. Dateien in \`public\` werden relativ zu \`base\` referenziert und bleiben bei den Seiten.
+Lade das Verzeichnis \`assets\` aus dem Ausgabeverzeichnis auf das CDN hoch, sodass es unter \`https://cdn.example.com/assets/\` erreichbar ist, und stelle die übrige Ausgabe wie gewohnt auf deiner Website bereit. Dateien in \`public\` werden relativ zu \`base\` referenziert und bleiben bei den Seiten.
 
 Da der Wert häufig von der Umgebung abhängt, kann er auch über die Kommandozeile übergeben werden:
 

From c1d90127e60ea0c410b0f07c056515c8a282ac56 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:16 +0200
Subject: [PATCH 168/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/data-loading.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index 71a5842ee..edafa87cb 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -10,7 +10,7 @@ Data Loader können verwendet werden, um entfernte Daten abzurufen oder Metadate
 
 ## Grundlegende Verwendung
 
-Eine Data-Loader-Datei muss mit `.data.js` or `.data.ts`. enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()` method:
+Eine Data-Loader-Datei muss mit `.data.js` oder `.data.ts` enden. Die Datei sollte ein Objekt als Standardexport bereitstellen, das die `load()`-Methode enthält:
 
 ```js [example.data.js]
 export default {
@@ -57,9 +57,9 @@ export default {
 
 ## Daten aus lokalen Dateien
 
-Wenn du Daten auf Grundlage lokaler Dateien erzeugen musst, solltest du die `watch` Option im Data Loader verwenden, damit Änderungen an diesen Dateien Hot-Updates auslösen können.
+Wenn du Daten auf Grundlage lokaler Dateien erzeugen musst, solltest du die `watch` Option im Data Loader verwenden, damit Änderungen an diesen Dateien automatische Aktualisierungen während der Entwicklung auslösen können.
 
-Die Option `watch` ist außerdem praktisch, weil du [glob patterns](https://github.com/mrmlnc/fast-glob#pattern-syntax) verwenden kannst, um mehrere Dateien zu finden. Die Muster können relativ zur Loader-Datei angegeben werden, und die Funktion `load()` erhält die gefundenen Dateien als absolute Pfade.
+Die Option `watch` ist außerdem praktisch, weil du [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) verwenden kannst, um mehrere Dateien zu finden. Die Muster können relativ zur Loader-Datei angegeben werden, und die Funktion `load()` erhält die gefundenen Dateien als absolute Pfade.
 
 Das folgende Beispiel zeigt, wie CSV-Dateien geladen und mit [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Da diese Datei nur zur Build-Zeit ausgeführt wird, wird der CSV-Parser nicht an den Client ausgeliefert!
 

From ac9671c00efcbc1a5479b14997a68bc4cbcee249 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:18 +0200
Subject: [PATCH 169/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/deploy.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index 6ff6e3cbe..8147021ce 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -180,8 +180,8 @@ Aktiviere keine Optionen wie _Auto Minify_ für HTML-Code. Dadurch werden Kommen
          - name: Checkout
            uses: actions/checkout@v5
            with:
-             fetch-depth: 0 # Not needed wenn lastUpdated is not enabled
-         # - uses: pnpm/action-setup@v4 # Uncomment this block wenn you're using pnpm
+             fetch-depth: 0 # Nicht erforderlich, wenn lastUpdated nicht aktiviert ist
+         # - uses: pnpm/action-setup@v4 # Entferne die Kommentarzeichen bei Verwendung von pnpm
          #   with:
          #     version: 9 # Not needed wenn you've set "packageManager" in package.json
          # - uses: oven-sh/setup-bun@v1 # Uncomment this wenn you're using Bun

From c5fc62e73c818e51d4b2ac1d4a79050931103396 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:21 +0200
Subject: [PATCH 170/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/extending-default-theme.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index f23c272f7..a17ca047c 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -21,7 +21,7 @@ Bevor du fortfährst, lies zunächst [Ein eigenes Theme verwenden](./custom-them
 
 ## Anpassen CSS
 
-The Standard-Theme CSS is customizable by overriding root level CSS variables:
+Das CSS des Standard-Themes kann durch Überschreiben der CSS-Variablen auf Stammebene angepasst werden:
 
 ```js [.vitepress/theme/index.js]
 import DefaultTheme from 'vitepress/theme'
@@ -38,11 +38,11 @@ export default DefaultTheme
 }
 ```
 
-Siehe [Standard-Theme CSS variables](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css) that can be overridden.
+Siehe die [CSS-Variablen des Standard-Themes](https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css), die überschrieben werden können.
 
 ### Navbar
 
-The navbar draws a single background surface controlled by CSS variables, so its look can be changed ohne touching component internals:
+Die Navigationsleiste verwendet eine einzelne, über CSS-Variablen gesteuerte Hintergrundfläche. Ihr Erscheinungsbild kann daher geändert werden, ohne die Interna der Komponenten anzupassen:
 
 ```css
 :root {

From 58bc040d6933ae0d3a184bd26aa94d72f6f23a17 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:23 +0200
Subject: [PATCH 171/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/markdown.md | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/de/guide/markdown.md b/docs/de/guide/markdown.md
index 3ec5c9f51..d81bea30a 100644
--- a/docs/de/guide/markdown.md
+++ b/docs/de/guide/markdown.md
@@ -1,35 +1,35 @@
 ---
-description: VitePress built-in Markdown extensions including custom containers, code blocks with syntax highlighting, line highlighting, code groups, and more.
+description: In VitePress integrierte Markdown-Erweiterungen einschließlich benutzerdefinierter Container, Codeblöcke mit Syntaxhervorhebung, Zeilenhervorhebung, Codegruppen und weiterer Funktionen.
 outline: deep
 ---
 
 # Markdown-Erweiterungen
 
-VitePress comes with built in Markdown-Erweiterungen.
+VitePress enthält integrierte Markdown-Erweiterungen.
 
 ## Header Anchors
 
-Headers automatisch get anchor links applied. Rendering of anchors can be configured Verwendung the `markdown.anchor` option.
+Überschriften erhalten automatisch Ankerlinks. Die Darstellung der Anker kann über die Option `markdown.anchor` konfiguriert werden.
 
 ### Eigenes anchors
 
-To specify a custom anchor tag for a heading instead of Verwendung the auto-generated one, add a suffix to the heading:
+Um für eine Überschrift einen eigenen Anker statt des automatisch erzeugten Ankers festzulegen, füge der Überschrift ein Suffix hinzu:
 
 ```
 # Using custom anchors {#my-anchor}
 ```
 
-Dies ermöglicht you to link to the heading as `#my-anchor` instead of the default `#Verwendung-custom-anchors`.
+Dadurch kannst du auf die Überschrift über `#my-anchor` statt über den Standardanker `#Verwendung-custom-anchors` verlinken.
 
 ## Links
 
-Both internal and external links get special treatment.
+Interne und externe Links werden speziell behandelt.
 
 ### Internal Links
 
-Internal links are converted to router links for SPA navigation. Also, every `index.md` contained in each sub-directory will automatisch be converted to `index.html`, with corresponding URL `/`.
+Interne Links werden für die SPA-Navigation in Router-Links umgewandelt. Außerdem wird jedes `index.md` in einem Unterverzeichnis automatisch in `index.html` mit der entsprechenden URL `/` umgewandelt.
 
-Zum Beispiel, given the following directory structure:
+Zum Beispiel bei der folgenden Verzeichnisstruktur:
 
 ```
 .
@@ -44,7 +44,7 @@ Zum Beispiel, given the following directory structure:
    └─ four.md
 ```
 
-And providing you are in `foo/one.md`:
+Wenn du dich in `foo/one.md` befindest:
 
 ```md
 [Home](/) <!-- sends the user to the root index.md -->

From 2f03c464954a912c38b0b853f6e548c5896c0011 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:26 +0200
Subject: [PATCH 172/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/routing.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 643d5125c..2f9840f60 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -103,12 +103,12 @@ Wenn du auf eine Seite deiner Website verlinken möchtest, die nicht von VitePre
 **Input**
 
 ```md
-[Link to pure.html](/pure.html){target="_self"}
+[Link zu pure.html](/pure.html){target="_self"}
 ```
 
 **Ausgabe**
 
-[Link to pure.html](/pure.html){target="_self"}
+[Link zu pure.html](/pure.html){target="_self"}
 
 ::: tip Hinweis
 
@@ -117,7 +117,7 @@ Bei Markdown-Links wird `base` automatisch der URL vorangestellt. Wenn du auf ei
 Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 
 ```md
-<a href="/pure.html" target="_self">Link to pure.html</a>
+<a href="/pure.html" target="_self">Link zu pure.html</a>
 ```
 
 :::
@@ -128,14 +128,14 @@ Alternativ kannst du direkt die Anchor-Tag-Syntax verwenden:
 Um saubere URLs mit VitePress bereitzustellen, ist Unterstützung auf Serverseite erforderlich.
 :::
 
-Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` enden. Manche Benutzer bevorzugen jedoch "Saubere URLs" ohne die Erweiterung `.html` – beispielsweise `example.com/path` statt `example.com/path.html`.
+Standardmäßig löst VitePress eingehende Links in URLs auf, die mit `.html` enden. Manche Benutzer bevorzugen jedoch „saubere URLs“ ohne die Erweiterung `.html` – beispielsweise `example.com/path` statt `example.com/path.html`.
 
 Einige Server oder Hosting-Plattformen (beispielsweise Netlify, Vercel und GitHub Pages) können eine URL wie `/foo` ohne Weiterleitung auf `/foo.html` abbilden, wenn diese Datei existiert:
 
 - Netlify und GitHub Pages unterstützen dies standardmäßig.
-- Vercel erfordert die Aktivierung von the [`cleanUrls` option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
+- Vercel erfordert die Aktivierung der [`cleanUrls`-Option in `vercel.json`](https://vercel.com/docs/concepts/projects/project-configuration#cleanurls).
 
-Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls) Konfigurationsoption so that:
+Wenn diese Funktion verfügbar ist, kannst du auch VitePress' eigene [`cleanUrls`](../reference/site-config#cleanurls)-Konfigurationsoption so konfigurieren:
 
 - Links zwischen Seiten werden ohne die Erweiterung `.html` erzeugt.
 - Wenn der aktuelle Pfad mit `.html` endet, führt der Router eine clientseitige Weiterleitung zum Pfad ohne Erweiterung durch.
@@ -177,7 +177,7 @@ packages/pkg-b/src/index.md  -->  /pkg-b/index.html
 packages/pkg-b/src/bar.md    -->  /pkg-b/bar.html
 ```
 
-Du kannst dies durch Konfiguration der [`rewrites`](../reference/site-config#rewrites) option like this:
+Du kannst dies durch Konfiguration der [`rewrites`](../reference/site-config#rewrites)-Option wie folgt tun:
 
 ```ts [.vitepress/config.js]
 export default {

From ac203b971b17722843e3a2c2c0dc5c1a38c10fb6 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:28 +0200
Subject: [PATCH 173/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/ssr-compat.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/ssr-compat.md b/docs/de/guide/ssr-compat.md
index 224ac883f..f61bee241 100644
--- a/docs/de/guide/ssr-compat.md
+++ b/docs/de/guide/ssr-compat.md
@@ -108,7 +108,7 @@ const clientCompRef = ref(null)
 const ClientComp = defineClientComponent(
   () => import('component-that-access-window-on-import'),
 
-  // args are passed to h() - https://vuejs.org/api/render-function.html#h
+  // Argumente werden an h() übergeben – https://vuejs.org/api/render-function.html#h
   [
     {
       ref: clientCompRef
@@ -120,7 +120,7 @@ const ClientComp = defineClientComponent(
     }
   ],
 
-  // callback after the component is loaded, can be async
+  // Rückruffunktion nach dem Laden der Komponente, kann asynchron sein
   () => {
     console.log(clientCompRef.value)
   }

From f342c74b7a1a447afe675934dc455c88940a2d7b Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:30 +0200
Subject: [PATCH 174/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/using-vue.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index 3d0bd7226..c776c06b6 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -30,7 +30,7 @@ Jede Markdown-Datei wird zunächst in HTML kompiliert und anschließend als Vue-
 
 ### Directives
 
-Direktiven funktionieren ebenfalls (note that by design, raw HTML is also valid in Markdown):
+Direktiven funktionieren ebenfalls (beachte, dass rohes HTML absichtlich auch in Markdown gültig ist):
 
 **Input**
 
@@ -59,7 +59,7 @@ const count = ref(0)
 
 ## Markdown-Inhalt
 
-The count is: {{ count }}
+Die Anzahl beträgt: {{ count }}
 
 <button :class="$style.button" @click="count++">Increment</button>
 
@@ -75,7 +75,7 @@ The count is: {{ count }}
 Bei Verwendung in Markdown erfordert `<style scoped>` das Hinzufügen spezieller Attribute zu jedem Element der aktuellen Seite, wodurch die Seitengröße erheblich zunimmt. `<style module>` wird bevorzugt, wenn eine lokal begrenzte Gestaltung auf einer Seite benötigt wird.
 :::
 
-You also have access to VitePress' runtime APIs such as the [`useData` helper](../reference/runtime-api#usedata), which stellt bereit access to current page's metadata:
+Du hast außerdem Zugriff auf VitePress' Laufzeit-APIs wie den [`useData`-Helper](../reference/runtime-api#usedata), der Zugriff auf die Metadaten der aktuellen Seite bereitstellt:
 
 **Input**
 
@@ -94,7 +94,7 @@ const { page } = useData()
 ```json
 {
   "path": "/using-vue.html",
-  "title": "Using Vue in Markdown",
+  "title": "Vue in Markdown verwenden",
   "frontmatter": {},
   ...
 }
@@ -126,7 +126,7 @@ Dies ist eine .md-Datei, die eine benutzerdefinierte Komponente verwendet
 
 ### Komponenten global registrieren
 
-Wenn eine Komponente auf den meisten Seiten verwendet werden soll, kann sie durch Anpassen der Vue-App-Instanz global registriert werden. Siehe den entsprechenden Abschnitt unter [Standard-Theme erweitern](./extending-default-theme#registering-global-Komponenten) for an example.
+Wenn eine Komponente auf den meisten Seiten verwendet werden soll, kann sie durch Anpassen der Vue-App-Instanz global registriert werden. Siehe den entsprechenden Abschnitt unter [Standard-Theme erweitern](./extending-default-theme#registering-global-Komponenten) für ein Beispiel.
 
 ::: warning IMPORTANT
 Stelle sicher, dass der Name einer benutzerdefinierten Komponente entweder einen Bindestrich enthält oder in PascalCase geschrieben ist. Andernfalls wird sie als Inline-Element behandelt und in ein `<p>`-Tag eingeschlossen, was zu einer Abweichung bei der Hydration führt, da `<p>` keine Block-Elemente enthalten darf.
@@ -144,7 +144,7 @@ Du kannst Vue-Komponenten in Überschriften verwenden, beachte jedoch den Unters
 Das von `<code>` umschlossene HTML wird unverändert angezeigt; nur HTML, das **nicht** umschlossen ist, wird von Vue analysiert.
 
 ::: tip
-The output HTML is accomplished by [Markdown-it](https://github.com/Markdown-it/Markdown-it), while the parsed headers are handled by VitePress (and verwendet for both the sidebar and document title).
+Das Ausgabe-HTML wird von [Markdown-it](https://github.com/Markdown-it/Markdown-it) erzeugt, während die analysierten Überschriften von VitePress verarbeitet werden (und sowohl für die Seitenleiste als auch für den Dokumenttitel verwendet werden).
 :::
 
 

From 6b35b6296a0baa9976a2a4db9c887a39f25ce64f Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:32 +0200
Subject: [PATCH 175/199] docs(de): letzte Denglish-Reste bereinigen

---
 docs/de/guide/what-is-vitepress.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index eb95db662..34b4ed2a0 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -4,7 +4,7 @@ description: Ein statischer Website-Generator zum Erstellen schneller, inhaltsor
 
 # Was ist VitePress?
 
-VitePress ist ein [statischer Website-Generator](https://en.wikipedia.org/wiki/Static_site_generazur) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
+VitePress ist ein [statischer Website-Generator](https://en.wikipedia.org/wiki/Static_site_generator) (SSG) zum Erstellen schneller, inhaltsorientierter Websites. Kurz gesagt nimmt VitePress deine in [Markdown](https://en.wikipedia.org/wiki/Markdown), geschriebenen Inhalte, wendet ein Theme darauf an und erzeugt statische HTML-Seiten, die sich nahezu überall bereitstellen lassen.
 
 ::: tip {no-title}
 Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./getting-started).
@@ -32,7 +32,7 @@ VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mi
 
 - **[Integrierte Markdown-Erweiterungen:](./markdown)** Frontmatter, Tabellen, Syntaxhervorhebung und vieles mehr. VitePress bietet insbesondere zahlreiche fortgeschrittene Funktionen für die Arbeit mit Codeblöcken und eignet sich dadurch besonders für hochtechnische Dokumentation.
 
-- **[Vue-erweitertes Markdown:](./using-vue)** Jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html). Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten. Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
+- **[Vue-erweitertes Markdown:](./using-vue)** Jede Markdown-Seite ist dank der 100%igen Syntaxkompatibilität von Vue-Templates mit HTML auch eine Vue-[Single-File-Komponente](https://vuejs.org/guide/scaling-up/sfc.html). Du kannst mithilfe von Vue-Template-Funktionen oder importierten Vue-Komponenten Interaktivität in deine statischen Inhalte einbetten.
 
 ## Leistung
 

From 5694ef34b9c33e53df79bd7c67285ffbed79409e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:56 +0200
Subject: [PATCH 176/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-last-updated.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/reference/default-theme-last-updated.md b/docs/de/reference/default-theme-last-updated.md
index 6b5ba460b..e0b194363 100644
--- a/docs/de/reference/default-theme-last-updated.md
+++ b/docs/de/reference/default-theme-last-updated.md
@@ -11,7 +11,7 @@ VitePress zeigt den Zeitpunkt der letzten Aktualisierung anhand des Zeitstempels
 
 Intern führt VitePress für jede Datei `git log -1 --pretty="%ai"` aus, um den Zeitstempel abzurufen. Wenn alle Seiten dieselbe Aktualisierungszeit anzeigen, liegt dies wahrscheinlich an einem flachen Klonen (häufig in CI-Umgebungen), das den Git-Verlauf begrenzt.
 
-To fix this in **GitHub Actions**, use the following in your workflow:
+Um dies in **GitHub Actions** zu beheben, verwende Folgendes in deinem Workflow:
 
 ```yaml{4}
 - name: Checkout

From 6cbeaf84e0b8c7cd5414e04aa77207042dbdfaf9 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:11:58 +0200
Subject: [PATCH 177/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-badge.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/de/reference/default-theme-badge.md b/docs/de/reference/default-theme-badge.md
index 98288fa00..7633e4790 100644
--- a/docs/de/reference/default-theme-badge.md
+++ b/docs/de/reference/default-theme-badge.md
@@ -11,28 +11,28 @@ Mit dem Badge kannst du deinen Überschriften einen Status hinzufügen. Zum Beis
 Du kannst die global verfügbare `Badge`-Komponente verwenden.
 
 ```html
-### Title <Badge type="info" text="default" />
-### Title <Badge type="tip" text="^1.9.0" />
-### Title <Badge type="warning" text="beta" />
-### Title <Badge type="danger" text="deprecated" />
+### Titel <Badge type="info" text="default" />
+### Titel <Badge type="tip" text="^1.9.0" />
+### Titel <Badge type="warning" text="beta" />
+### Titel <Badge type="danger" text="deprecated" />
 ```
 
 Der obige Code wird folgendermaßen dargestellt:
 
-### Title <Badge type="info" text="Standard" />
-### Title <Badge type="tip" text="^1.9.0" />
-### Title <Badge type="warning" text="beta" />
-### Title <Badge type="danger" text="deprecated" />
+### Titel <Badge type="info" text="Standard" />
+### Titel <Badge type="tip" text="^1.9.0" />
+### Titel <Badge type="warning" text="beta" />
+### Titel <Badge type="danger" text="deprecated" />
 
 ## Eigenes Children
 
 `<Badge>` akzeptiert `children`, die im Badge angezeigt werden.
 
 ```html
-### Title <Badge type="info">custom element</Badge>
+### Titel <Badge type="info">benutzerdefiniertes Element</Badge>
 ```
 
-### Title <Badge type="info">custom element</Badge>
+### Titel <Badge type="info">benutzerdefiniertes Element</Badge>
 
 ## Farbe und Typ anpassen
 

From 153faa9dc35f240e4f4b4ea6b88c6d7fd4dc4d62 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:01 +0200
Subject: [PATCH 178/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
index 66343c858..013bc2df8 100644
--- a/docs/de/reference/default-theme-config.md
+++ b/docs/de/reference/default-theme-config.md
@@ -12,7 +12,7 @@ export default {
   title: 'VitePress',
   description: 'Vite & Vue powered static site generator.',
 
-  // Theme related configurations.
+  // Konfigurationsoptionen für das Theme.
   themeConfig: {
     logo: '/logo.svg',
     nav: [...],
@@ -92,7 +92,7 @@ Die Konfiguration für einen Navigationseintrag. Weitere Details findest du unte
 export default {
   themeConfig: {
     nav: [
-      { text: 'Guide', link: '/guide' },
+      { text: 'Anleitung', link: '/guide' },
       {
         text: 'Dropdown Menu',
         items: [

From 37f3dff941783f14e33212b34c64d3fda78c06b5 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:03 +0200
Subject: [PATCH 179/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-prev-next-links.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-prev-next-links.md b/docs/de/reference/default-theme-prev-next-links.md
index 9a0c30144..549f4c1b6 100644
--- a/docs/de/reference/default-theme-prev-next-links.md
+++ b/docs/de/reference/default-theme-prev-next-links.md
@@ -16,7 +16,7 @@ Du kannst Text und Link für die vorherige und nächste Seite anpassen (sie werd
 
 - Beispiele:
 
-  - To customize only the text:
+  - Nur den Text anpassen:
 
     ```yaml
     ---
@@ -24,7 +24,7 @@ Du kannst Text und Link für die vorherige und nächste Seite anpassen (sie werd
     ---
     ```
 
-  - To customize both text and link:
+  - Text und Link anpassen:
 
     ```yaml
     ---
@@ -34,7 +34,7 @@ Du kannst Text und Link für die vorherige und nächste Seite anpassen (sie werd
     ---
     ```
 
-  - To hide previous page:
+  - Vorherige Seite ausblenden:
 
     ```yaml
     ---

From fd7096671e51c35464cacc2ee8862919dac0c5e1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:05 +0200
Subject: [PATCH 180/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-search.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/default-theme-search.md b/docs/de/reference/default-theme-search.md
index d695a2c7b..f9b108ce6 100644
--- a/docs/de/reference/default-theme-search.md
+++ b/docs/de/reference/default-theme-search.md
@@ -23,7 +23,7 @@ export default defineConfig({
 
 Beispielergebnis:
 
-![screenshot of the search modal](/search.png)
+![Screenshot des Suchfensters](/search.png)
 
 Alternativ kannst du [Algolia DocSearch](#algolia-search) oder Community-Plugins verwenden, zum Beispiel:
 
@@ -31,7 +31,7 @@ Alternativ kannst du [Algolia DocSearch](#algolia-search) oder Community-Plugins
 - <https://npmx.dev/package/vitepress-plugin-typesense>
 - <https://npmx.dev/package/vitepress-plugin-cloudflare-ai-search>
 
-<!-- - <https://npmx.dev/package/@orama/plugin-vitepress> -- replace with zbsearch one when published -->
+<!-- - <https://npmx.dev/package/@orama/plugin-vitepress> -- durch zbsearch ersetzen, sobald veröffentlicht -->
 
 ### Internationalisierung {#local-search-i18n}
 
@@ -46,7 +46,7 @@ export default defineConfig({
       provider: 'local',
       options: {
         locales: {
-          zh: { // make this `root` if you want to translate the default locale
+          zh: { // auf `root` setzen, wenn die Standardsprache übersetzt werden soll
             translations: {
               button: {
                 buttonText: '搜索',

From 2c0e4a651d38f22b72e009cd708e4923963981de Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:07 +0200
Subject: [PATCH 181/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/default-theme-sidebar.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/reference/default-theme-sidebar.md b/docs/de/reference/default-theme-sidebar.md
index cafaa6058..b6d5b25a8 100644
--- a/docs/de/reference/default-theme-sidebar.md
+++ b/docs/de/reference/default-theme-sidebar.md
@@ -4,7 +4,7 @@ description: Konfiguriere die Seitenleistennavigation im VitePress-Standard-Them
 
 # Seitenleiste
 
-Die Seitenleiste ist der zentrale Navigationsbereich deiner Dokumentation. Du kannst das Seitenleistenmenü konfigurieren in [`themeConfig.sidebar`](./default-theme-config#sidebar).
+Die Seitenleiste ist der zentrale Navigationsbereich deiner Dokumentation. Du kannst das Seitenleistenmenü unter [`themeConfig.sidebar`](./default-theme-config#sidebar) konfigurieren.
 
 ```js
 export default {

From 5244b7ce3c2c7f6875c8c9459134f105c43bac55 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:10 +0200
Subject: [PATCH 182/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/runtime-api.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/runtime-api.md b/docs/de/reference/runtime-api.md
index 813a253a0..fd0681e92 100644
--- a/docs/de/reference/runtime-api.md
+++ b/docs/de/reference/runtime-api.md
@@ -17,19 +17,19 @@ Gibt seitenspezifische Daten zurück. Das zurückgegebene Objekt hat folgenden T
 ```ts
 interface VitePressData<T = any> {
   /**
-   * Site-level metadata
+   * Metadaten auf Websiteebene
    */
   site: Ref<SiteData<T>>
   /**
-   * themeConfig from .vitepress/config.js
+   * themeConfig aus .vitepress/config.js
    */
   theme: Ref<T>
   /**
-   * Page-level metadata
+   * Metadaten auf Seitenebene
    */
   page: Ref<PageData>
   /**
-   * Page frontmatter
+   * Frontmatter der Seite
    */
   frontmatter: Ref<PageData['frontmatter']>
   /**

From 4caef4d7a4c98ee75aa0668809ac2c9562300db1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:12:13 +0200
Subject: [PATCH 183/199] docs(de): Denglische Reste entfernen

---
 docs/de/reference/site-config.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/reference/site-config.md b/docs/de/reference/site-config.md
index 8bcee2848..30cd311a4 100644
--- a/docs/de/reference/site-config.md
+++ b/docs/de/reference/site-config.md
@@ -20,7 +20,7 @@ export default {
   // app level config options
   lang: 'en-US',
   title: 'VitePress',
-  description: 'Vite & Vue powered static site generator.',
+  description: 'Statischer Website-Generator auf Basis von Vite und Vue.',
   ...
 }
 ```
@@ -39,7 +39,7 @@ export default async () => {
     // app level config options
     lang: 'en-US',
     title: 'VitePress',
-    description: 'Vite & Vue powered static site generator.',
+    description: 'Statischer Website-Generator auf Basis von Vite und Vue.',
 
     // Konfigurationsoptionen auf Theme-Ebene
     themeConfig: {
@@ -65,7 +65,7 @@ export default defineConfig({
   // app level config options
   lang: 'en-US',
   title: 'VitePress',
-  description: 'Vite & Vue powered static site generator.',
+  description: 'Statischer Website-Generator auf Basis von Vite und Vue.',
 
   // Konfigurationsoptionen auf Theme-Ebene
   themeConfig: {

From 63642f2d48a9e080d5c15733c03c3d48bb5ed7c1 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:27 +0200
Subject: [PATCH 184/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/deploy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index 8147021ce..a0812b235 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -52,7 +52,7 @@ Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
 Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`) bereitgestellt wird. Wenn deine Website unter einem Unterpfad wie `https://mywebsite.com/blog/` bereitgestellt wird, musst du die Option [`base`](../reference/site-config#base) in der VitePress-Konfiguration auf `'/blog/'` setzen.
 
-**Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und unter `user.github.io/repo/`, dann set your `base` to `/repo/`.
+**Beispiel:** Wenn du GitHub- (oder GitLab-) Pages verwendest und deine Website unter `user.github.io/repo/` bereitstellst, setze `base` auf `/repo/`.
 
 ## Verschiebbare Builds (relativer Basispfad) {#relocatable-builds-relative-base}
 

From 84025661d4ff0997b6a8689149b9bede24d873e0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:30 +0200
Subject: [PATCH 185/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/extending-default-theme.md | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/docs/de/guide/extending-default-theme.md b/docs/de/guide/extending-default-theme.md
index a17ca047c..437fa21a9 100644
--- a/docs/de/guide/extending-default-theme.md
+++ b/docs/de/guide/extending-default-theme.md
@@ -46,18 +46,18 @@ Die Navigationsleiste verwendet eine einzelne, über CSS-Variablen gesteuerte Hi
 
 ```css
 :root {
-  /* bar height and background */
+  /* Höhe und Hintergrund der Leiste */
   --vp-nav-height: 4rem;
   --vp-nav-bg-color: var(--vp-c-bg);
 
-  /* background while on top of the home page (unscrolled);
-     set to var(--vp-nav-bg-color) to opt out of the transparent treatment */
+  /* Hintergrund am oberen Rand der Startseite (nicht gescrollt);
+     auf var(--vp-nav-bg-color) setzen, um die Transparenz zu deaktivieren */
   --vp-nav-home-bg-color: transparent;
 
-  /* filter applied to the content behind the bar */
+  /* Filter für den Inhalt hinter der Leiste */
   --vp-nav-backdrop-filter: none;
 
-  /* the bar's bottom rule and the mobile menu background */
+  /* untere Linie der Leiste und Hintergrund des mobilen Menüs */
   --vp-nav-divider-color: var(--vp-c-gutter);
   --vp-nav-screen-bg-color: var(--vp-c-bg);
 }
@@ -72,10 +72,10 @@ Zum Beispiel, a frosted-glass navbar:
 }
 ```
 
-The same treatment carries over to the local nav: `--vp-local-nav-bg-color` follows the navbar surface color standardmäßig, and where the two bars meet they share a single blurred surface, so the glass stays continuous across them.
+Dieselbe Gestaltung gilt auch für die lokale Navigation: `--vp-local-nav-bg-color` folgt standardmäßig der Oberflächenfarbe der Navigationsleiste. Wo die beiden Leisten zusammentreffen, teilen sie sich eine einzige verschwommene Fläche, sodass der Glaseffekt durchgehend bleibt.
 
 ::: warning
-`backdrop-filter` has a measurable scroll performance cost, especially on large or high-DPI screens. Wenn Verwendung a translucent bar, also check text contrast over your page content. Safari 17 and earlier don't apply variable-driven backdrop filters, so they show the translucent color ohne the blur.
+`backdrop-filter` kann die Scrollleistung messbar beeinträchtigen, insbesondere auf großen Bildschirmen oder Bildschirmen mit hoher Pixeldichte. Wenn du eine halbtransparente Leiste verwendest, prüfe daher den Kontrast des Textes gegenüber deinem Seiteninhalt. Safari 17 und ältere Versionen wenden variablenbasierte Hintergrundfilter nicht an und zeigen daher die halbtransparente Farbe ohne Unschärfe.
 :::
 
 Wenn the nav items don't fit the verfügbar width, they move in the `⋯` menu at the end of the navbar instead of being clipped, starting mit the social links, the appearance switch and the locale switcher, followed by the nav items right-to-left. Its button label can be localized mit [`extraMenuLabel`](../reference/default-theme-config#extramenulabel).

From aa38fda7f47e992a673cb369993451f96646b4ee Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:33 +0200
Subject: [PATCH 186/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/markdown.md | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/docs/de/guide/markdown.md b/docs/de/guide/markdown.md
index d81bea30a..d10317584 100644
--- a/docs/de/guide/markdown.md
+++ b/docs/de/guide/markdown.md
@@ -16,7 +16,7 @@ VitePress enthält integrierte Markdown-Erweiterungen.
 Um für eine Überschrift einen eigenen Anker statt des automatisch erzeugten Ankers festzulegen, füge der Überschrift ein Suffix hinzu:
 
 ```
-# Using custom anchors {#my-anchor}
+# Benutzerdefinierte Anker verwenden {#my-anchor}
 ```
 
 Dadurch kannst du auf die Überschrift über `#my-anchor` statt über den Standardanker `#Verwendung-custom-anchors` verlinken.
@@ -47,17 +47,17 @@ Zum Beispiel bei der folgenden Verzeichnisstruktur:
 Wenn du dich in `foo/one.md` befindest:
 
 ```md
-[Home](/) <!-- sends the user to the root index.md -->
-[foo](/foo/) <!-- sends the user to index.html of directory foo -->
-[foo heading](./#heading) <!-- anchors user to a heading in the foo index file -->
-[bar - three](../bar/three) <!-- you can omit extension -->
-[bar - three](../bar/three.md) <!-- you can append .md -->
-[bar - four](../bar/four.html) <!-- or you can append .html -->
+[Startseite](/) <!-- führt zur index.md im Stammverzeichnis -->
+[foo](/foo/) <!-- führt zur index.html des Verzeichnisses foo -->
+[foo heading](./#heading) <!-- verankert den Benutzer an einer Überschrift der foo-index-Datei -->
+[bar - drei](../bar/three) <!-- die Dateiendung kann weggelassen werden -->
+[bar - drei](../bar/three.md) <!-- .md kann angehängt werden -->
+[bar - vier](../bar/four.html) <!-- alternativ kann .html angehängt werden -->
 ```
 
 ### Seite Suffix
 
-Seiten and internal links get generated with the `.html` suffix by default.
+Seiten und interne Links werden standardmäßig mit dem Suffix `.html` erzeugt.
 
 ### External Links
 
@@ -68,7 +68,7 @@ Outbound links automatisch get `target="_blank" rel="noreferrer"`:
 
 ## Frontmatter
 
-[YAML frontmatter](https://jekyllrb.com/docs/front-matter/) is supported out of the box:
+[YAML-Frontmatter](https://jekyllrb.com/docs/front-matter/) wird standardmäßig unterstützt:
 
 ```yaml
 ---
@@ -77,20 +77,20 @@ lang: en-US
 ---
 ```
 
-This Daten will be verfügbar to the rest of the page, along with all custom and theming Komponenten.
+Diese Daten stehen dem restlichen Seiteninhalt sowie allen benutzerdefinierten und Theme-Komponenten zur Verfügung.
 
-For more details, see [Frontmatter](../reference/frontmatter-config).
+Weitere Informationen findest du unter [Frontmatter](../reference/frontmatter-config).
 
 ## GitHub-Style Tables
 
 **Input**
 
 ```md
-| Tables        |      Are      |  Cool |
+| Tabellen      |      Sind     |  Toll |
 | ------------- | :-----------: | ----: |
-| col 3 is      | right-aligned | $1600 |
-| col 2 is      |   centered    |   $12 |
-| zebra stripes |   are neat    |    $1 |
+| Spalte 3      | rechtsbündig  | $1600 |
+| Spalte 2      | zentriert     |   $12 |
+| Zebrastreifen |   sehen gut aus|    $1 |
 ```
 
 **Ausgabe**

From 3b5903963be21986c30cc6c5b244e641b1e7f6d8 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:38 +0200
Subject: [PATCH 187/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/using-vue.md | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/docs/de/guide/using-vue.md b/docs/de/guide/using-vue.md
index c776c06b6..779f781e5 100644
--- a/docs/de/guide/using-vue.md
+++ b/docs/de/guide/using-vue.md
@@ -150,25 +150,25 @@ Das Ausgabe-HTML wird von [Markdown-it](https://github.com/Markdown-it/Markdown-
 
 ## Maskierung
 
-Du kannst escape Vue interpolations by wrapping them in a `<span>` or other elements with the `v-pre` directive:
+Du kannst Vue-Interpolationen umgehen, indem du sie in ein `<span>` oder ein anderes Element mit der Direktive `v-pre` einschließt:
 
 **Input**
 
 ```md
-This <span v-pre>{{ will be displayed as-is }}</span>
+Dies <span v-pre>{{ wird unverändert angezeigt }}</span>
 ```
 
 **Ausgabe**
 
 <div class="escape-demo">
-  <p>This <span v-pre>{{ will be displayed as-is }}</span></p>
+  <p>Dies <span v-pre>{{ wird unverändert angezeigt }}</span></p>
 </div>
 
-Alternativ kannst du den gesamten Absatz in a `v-pre` custom container:
+Alternativ kannst du den gesamten Absatz in einen benutzerdefinierten `v-pre`-Container einschließen:
 
 ```md
 ::: v-pre
-{{ This will be displayed as-is }}
+{{ Dies wird unverändert angezeigt }}
 :::
 ```
 
@@ -177,14 +177,14 @@ Alternativ kannst du den gesamten Absatz in a `v-pre` custom container:
 <div class="escape-demo">
 
 ::: v-pre
-{{ This will be displayed as-is }}
+{{ Dies wird unverändert angezeigt }}
 :::
 
 </div>
 
 ## Maskierung in Codeblöcken aufheben
 
-Standardmäßig, all fenced code blocks are automatisch wrapped with `v-pre`, so no Vue syntax will be processed inside. To enable Vue-style interpolation inside fences, you can append the language with the `-vue` suffix, e.g. `js-vue`:
+Standardmäßig werden alle abgegrenzten Codeblöcke automatisch mit `v-pre` umschlossen, sodass darin keine Vue-Syntax verarbeitet wird. Um Vue-Interpolation innerhalb solcher Blöcke zu aktivieren, kannst du die Sprache mit dem Suffix `-vue` versehen, z. B. `js-vue`:
 
 **Input**
 
@@ -200,20 +200,20 @@ Hello {{ 1 + 1 }}
 Hello {{ 1 + 1 }}
 ```
 
-Beachte, dass this might prevent certain tokens from being syntax highlighted properly.
+Beachte, dass dies verhindern kann, dass bestimmte Token korrekt hervorgehoben werden.
 
 ## CSS-Präprozessoren verwenden
 
-VitePress has [built-in support](https://vite.dev/guide/features.html#css-pre-processors) for CSS pre-processors: `.scss`, `.sass`, `.less`, `.styl` and `.stylus` files. There is no need to install Vite-specific plugins for them, but the corresponding pre-processor itself must be installed:
+VitePress bietet [integrierte Unterstützung](https://vite.dev/guide/features.html#css-pre-processors) für CSS-Präprozessoren: Dateien mit `.scss`, `.sass`, `.less`, `.styl` und `.stylus`. Dafür müssen keine Vite-spezifischen Plugins installiert werden, aber der jeweilige Präprozessor selbst muss installiert sein:
 
 ```
-# .scss and .sass
+# .scss und .sass
 npm install -D sass
 
 # .less
 npm install -D less
 
-# .styl and .stylus
+# .styl und .stylus
 npm install -D stylus
 ```
 

From dfe686076a82812ae11a3dd00bc90699e1231ebd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:40 +0200
Subject: [PATCH 188/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-badge.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/reference/default-theme-badge.md b/docs/de/reference/default-theme-badge.md
index 7633e4790..7aece0453 100644
--- a/docs/de/reference/default-theme-badge.md
+++ b/docs/de/reference/default-theme-badge.md
@@ -76,7 +76,7 @@ Die Komponente `<Badge>` akzeptiert die folgenden Props:
 
 ```ts
 interface Props {
-  // When `<slot>` is passed, this value gets ignored.
+  // Wenn `<slot>` übergeben wird, wird dieser Wert ignoriert.
   text?: string
 
   // Defaults to `tip`. Matches markdown containers/alerts colors.

From e0072b4e14c5568e7056344ba6fce032f50c57fd Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:42 +0200
Subject: [PATCH 189/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-edit-link.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/reference/default-theme-edit-link.md b/docs/de/reference/default-theme-edit-link.md
index 2e2b3edf9..820f73aec 100644
--- a/docs/de/reference/default-theme-edit-link.md
+++ b/docs/de/reference/default-theme-edit-link.md
@@ -47,7 +47,7 @@ export default {
   themeConfig: {
     editLink: {
       pattern: 'https://github.com/vuejs/vitepress/edit/main/docs/:path',
-      text: 'Edit this page on GitHub'
+      text: 'Diese Seite auf GitHub bearbeiten'
     }
   }
 }

From 8fa17474e162cea399deba6accefda63c424188e Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:45 +0200
Subject: [PATCH 190/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-footer.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/de/reference/default-theme-footer.md b/docs/de/reference/default-theme-footer.md
index d7c693ed3..6dbe08159 100644
--- a/docs/de/reference/default-theme-footer.md
+++ b/docs/de/reference/default-theme-footer.md
@@ -10,7 +10,7 @@ VitePress zeigt eine globale Fußzeile am unteren Rand der Seite an, wenn `theme
 export default {
   themeConfig: {
     footer: {
-      message: 'Released under the MIT License.',
+      message: 'Veröffentlicht unter der MIT-Lizenz.',
       copyright: 'Copyright © 2019-present Evan You'
     }
   }
@@ -19,10 +19,10 @@ export default {
 
 ```ts
 export interface Fußzeile {
-  // The message shown right before copyright.
+  // Die Nachricht, die direkt vor dem Copyright angezeigt wird.
   message?: string
 
-  // The actual copyright text.
+  // Der eigentliche Copyright-Text.
   copyright?: string
 }
 ```
@@ -33,7 +33,7 @@ Die obige Konfiguration unterstützt außerdem HTML-Zeichenketten. Wenn du beisp
 export default {
   themeConfig: {
     footer: {
-      message: 'Released under the <a href="https://github.com/vuejs/vitepress/blob/main/LICENSE">MIT License</a>.',
+      message: 'Veröffentlicht unter der <a href="https://github.com/vuejs/vitepress/blob/main/LICENSE">MIT-Lizenz</a>.',
       copyright: 'Copyright © 2019-present <a href="https://github.com/yyx990803">Evan You</a>'
     }
   }

From 25cd7f853695a7241a4b2d6ae23d1298ed8f5c56 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:48 +0200
Subject: [PATCH 191/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-home-page.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/reference/default-theme-home-page.md b/docs/de/reference/default-theme-home-page.md
index e235ff065..442b6781a 100644
--- a/docs/de/reference/default-theme-home-page.md
+++ b/docs/de/reference/default-theme-home-page.md
@@ -24,17 +24,17 @@ layout: home
 
 hero:
   name: VitePress
-  text: Vite & Vue powered static site generator.
+  text: Statischer Website-Generator auf Basis von Vite und Vue.
   tagline: Lorem ipsum...
   image:
     src: /logo.png
     alt: VitePress
   actions:
     - theme: brand
-      text: Get Started
+      text: Erste Schritte
       link: /guide/what-is-vitepress
     - theme: alt
-      text: View on GitHub
+      text: Auf GitHub ansehen
       link: https://github.com/vuejs/vitepress
 ---
 ```
@@ -77,7 +77,7 @@ interface HeroAction {
   // Zielattribut des Links.
   target?: string
 
-  // Link rel attribute.
+  // Link-rel-Attribut.
   rel?: string
 }
 ```
@@ -181,7 +181,7 @@ layout: home
 
 hero:
   name: VitePress
-  text: Vite & Vue powered static site generator.
+  text: Statischer Website-Generator auf Basis von Vite und Vue.
 ---
 
 ## Getting Started

From 77952960bc4d00d9f3099a8e5648dac2e68b88f4 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:18:51 +0200
Subject: [PATCH 192/199] =?UTF-8?q?docs(de):=20letzte=20englische=20Textre?=
 =?UTF-8?q?ste=20=C3=BCbersetzen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/reference/default-theme-config.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/reference/default-theme-config.md b/docs/de/reference/default-theme-config.md
index 013bc2df8..8a4f2b1fb 100644
--- a/docs/de/reference/default-theme-config.md
+++ b/docs/de/reference/default-theme-config.md
@@ -10,7 +10,7 @@ Mit der Theme-Konfiguration kannst du dein Theme anpassen. Du kannst sie über d
 export default {
   lang: 'en-US',
   title: 'VitePress',
-  description: 'Vite & Vue powered static site generator.',
+  description: 'Statischer Website-Generator auf Basis von Vite und Vue.',
 
   // Konfigurationsoptionen für das Theme.
   themeConfig: {
@@ -94,11 +94,11 @@ export default {
     nav: [
       { text: 'Anleitung', link: '/guide' },
       {
-        text: 'Dropdown Menu',
+        text: 'Dropdown-Menü',
         items: [
-          { text: 'Item A', link: '/item-1' },
-          { text: 'Item B', link: '/item-2' },
-          { text: 'Item C', link: '/item-3' }
+          { text: 'Eintrag A', link: '/item-1' },
+          { text: 'Eintrag B', link: '/item-2' },
+          { text: 'Eintrag C', link: '/item-3' }
         ]
       }
     ]

From a4b23d441740242f20a8ca31a7e09c25feae0029 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:21 +0200
Subject: [PATCH 193/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/data-loading.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/de/guide/data-loading.md b/docs/de/guide/data-loading.md
index edafa87cb..34d48dfe3 100644
--- a/docs/de/guide/data-loading.md
+++ b/docs/de/guide/data-loading.md
@@ -1,10 +1,10 @@
 ---
-description: Lade beliebige Daten zur Build-Zeit mit VitePress Data Loadern und importiere sie in Seiten oder Komponenten.
+description: Lade beliebige Daten zur Erstellungszeit mit VitePress-Datenladern und importiere sie in Seiten oder Komponenten.
 ---
 
-# Daten zur Build-Zeit laden
+# Daten zur Erstellungszeit laden
 
-VitePress stellt eine Funktion namens **Data Loader** bereit, mit der du beliebige Daten laden und in Seiten oder Komponenten importieren kannst. Das Laden der Daten wird **nur zur Build-Zeit** ausgeführt: Die resultierenden Daten werden als JSON im endgültigen JavaScript-Bundle serialisiert.
+VitePress stellt eine Funktion namens **Datenlader** bereit, mit der du beliebige Daten laden und in Seiten oder Komponenten importieren kannst. Das Laden der Daten wird **nur zur Erstellungszeit** ausgeführt: Die resultierenden Daten werden als JSON im endgültigen JavaScript-Bundle serialisiert.
 
 Data Loader können verwendet werden, um entfernte Daten abzurufen oder Metadaten auf Grundlage lokaler Dateien zu erzeugen. Zum Beispiel kannst du damit deine lokalen API-Seiten analysieren und automatisch einen Index aller API-Einträge erzeugen.
 
@@ -57,11 +57,11 @@ export default {
 
 ## Daten aus lokalen Dateien
 
-Wenn du Daten auf Grundlage lokaler Dateien erzeugen musst, solltest du die `watch` Option im Data Loader verwenden, damit Änderungen an diesen Dateien automatische Aktualisierungen während der Entwicklung auslösen können.
+Wenn du Daten auf Grundlage lokaler Dateien erzeugen musst, solltest du die Option `watch` im Datenlader verwenden, damit Änderungen an diesen Dateien automatische Aktualisierungen während der Entwicklung auslösen können.
 
 Die Option `watch` ist außerdem praktisch, weil du [Glob-Muster](https://github.com/mrmlnc/fast-glob#pattern-syntax) verwenden kannst, um mehrere Dateien zu finden. Die Muster können relativ zur Loader-Datei angegeben werden, und die Funktion `load()` erhält die gefundenen Dateien als absolute Pfade.
 
-Das folgende Beispiel zeigt, wie CSV-Dateien geladen und mit [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/). Da diese Datei nur zur Build-Zeit ausgeführt wird, wird der CSV-Parser nicht an den Client ausgeliefert!
+Das folgende Beispiel zeigt, wie CSV-Dateien mit [csv-parse](https://github.com/adaltas/node-csv/tree/master/packages/csv-parse/) geladen werden. Da diese Datei nur zur Build-Zeit ausgeführt wird, wird der CSV-Parser nicht an den Client ausgeliefert!
 
 ```js
 import fs from 'node:fs'
@@ -93,7 +93,7 @@ import { createContentLoader } from 'vitepress'
 export default createContentLoader('posts/*.md', /* options */)
 ```
 
-Der Helper akzeptiert ein Glob-Muster relativ zum [Quellverzeichnis](./routing#source-directory), und gibt ein `{ watch, load }`-Data-Loader-Objekt zurück, das als Standardexport in einer Data-Loader-Datei verwendet werden kann. Außerdem wird ein Cache auf Grundlage der Änderungszeitpunkte von Dateien verwendet, um die Leistung während der Entwicklung zu verbessern.
+Der Helper akzeptiert ein Glob-Muster relativ zum [Quellverzeichnis](./routing#source-directory), und gibt ein `{ watch, load }`-Datenlader-Objekt zurück, das als Standardexport in einer Data-Loader-Datei verwendet werden kann. Außerdem wird ein Cache auf Grundlage der Änderungszeitpunkte von Dateien verwendet, um die Leistung während der Entwicklung zu verbessern.
 
 Hinweis: Der Loader funktioniert nur mit Markdown-Dateien – gefundene Dateien ohne Markdown-Endung werden übersprungen.
 

From 1aa06ac357fa3086f737a074394d2629148e9adb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:24 +0200
Subject: [PATCH 194/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/deploy.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/de/guide/deploy.md b/docs/de/guide/deploy.md
index a0812b235..9d5d3247c 100644
--- a/docs/de/guide/deploy.md
+++ b/docs/de/guide/deploy.md
@@ -8,7 +8,7 @@ description: Stelle deine VitePress-Website auf beliebten Plattformen wie Netlif
 Die folgenden Anleitungen basieren auf einigen gemeinsamen Voraussetzungen:
 
 - Die VitePress-Website befindet sich im Verzeichnis `docs` deines Projekts.
-- Du verwendest das standardmäßige Build-Ausgabeverzeichnis (`.vitepress/dist`).
+- Du verwendest das standardmäßige Ausgabeverzeichnis (`.vitepress/dist`).
 - VitePress ist als lokale Abhängigkeit in deinem Projekt installiert, und du hast die folgenden Skripte in deiner `package.json`:
 
   ```json [package.json]
@@ -56,7 +56,7 @@ Standardmäßig wird angenommen, dass die Website am Stammpfad einer Domain (`/`
 
 ## Verschiebbare Builds (relativer Basispfad) {#relocatable-builds-relative-base}
 
-Wenn die endgültige URL der Website zur Build-Zeit noch nicht bekannt ist – etwa bei einem IPFS-Gateway (`https://gateway/ipfs/<cid>/…`), der Wayback Machine, einem freigegebenen Ordner oder in eine App eingebetteter Dokumentation –, setze `base` auf `'./'`:
+Wenn die endgültige URL der Website zur Erstellungszeit noch nicht bekannt ist – etwa bei einem IPFS-Gateway (`https://gateway/ipfs/<cid>/…`), der Wayback Machine, einem freigegebenen Ordner oder in eine App eingebetteter Dokumentation –, setze `base` auf `'./'`:
 
 ```ts
 export default {
@@ -64,7 +64,7 @@ export default {
 }
 ```
 
-Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Derselbe Build funktioniert von **jedem** Unterpfad aus ohne erneuten Build – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
+Jede Seite referenziert Assets und andere Seiten dann relativ zu ihrem eigenen Speicherort. Die Client-Laufzeit ermittelt beim Laden der Seite den tatsächlichen Einhängepunkt. Dieselbe Ausgabe funktioniert von **jedem** Unterpfad aus ohne erneute Erstellung – auch von mehreren Pfaden gleichzeitig – während Routing, Suche und Prefetching vollständig funktionieren.
 
 Das direkte Öffnen der erzeugten HTML-Dateien über das Dateisystem (`file://`) funktioniert ebenfalls als vollständig navigierbare statische Website mit Formatierung. Browser blockieren JavaScript-Module über `file://`, daher findet dort keine Hydration statt – interaktive Funktionen wie die Suche bleiben inaktiv, während alle vorgerenderten Inhalte und Links weiterhin funktionieren.
 
@@ -76,13 +76,13 @@ Einige Dinge solltest du beachten:
 - Rohe HTML-`<a>`-Tags in Markdown behalten ihr `href` unverändert – verwende für absolute Links innerhalb der Website die Markdown-Linksyntax (eingebettete `<img>`-Quellen werden über die Asset-Pipeline verarbeitet).
 - Von [`createContentLoader`](./data-loading#createcontentloader) erzeugte Links bleiben absolut zur Website (ihr HTML wird in andere Seiten eingebettet, daher gibt es keinen einheitlichen relativen Präfix) – sie funktionieren nur bei einer Bereitstellung am Stammverzeichnis.
 - Stelle Seiten unter ihren kanonischen URLs bereit: das Stammverzeichnis als `/dir/` (nicht `/dir`) und ohne zusätzliche abschließende Schrägstriche bei Seiten-URLs. Der relative Präfix wird anhand der URL aufgelöst, die der Browser tatsächlich anzeigt, und praktisch alle statischen Hoster verwenden bereits diese kanonische Form.
-- Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktions-Build.
+- Der Entwicklungsserver stellt immer unter `/` bereit; das relative Verhalten gilt für den Produktionsausgabe.
 
 ## HTTP-Cache-Header
 
 Wenn du Kontrolle über die HTTP-Header deines Produktionsservers hast, kannst du `cache-control`-Header konfigurieren, um bei wiederholten Besuchen eine bessere Leistung zu erzielen.
 
-Der Produktions-Build verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS und andere importierte Assets, die nicht in `public` liegen). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, siehst du Dateien wie `app.4f283b18.js`.
+Der Produktionsausgabe verwendet gehashte Dateinamen für statische Assets (JavaScript, CSS und andere importierte Assets, die nicht in `public` liegen). Wenn du die Produktionsvorschau mit dem Netzwerk-Tab der Browser-Entwicklertools untersuchst, siehst du Dateien wie `app.4f283b18.js`.
 
 Dieser Hash `4f283b18` wird aus dem Inhalt dieser Datei erzeugt. Dieselbe gehashte URL liefert garantiert denselben Dateiinhalt – wenn sich der Inhalt ändert, ändern sich auch die URLs. Das bedeutet, dass du für diese Dateien bedenkenlos die stärksten Cache-Header verwenden kannst. Alle solchen Dateien werden im Ausgabeverzeichnis unter `assets/` abgelegt. Dafür kannst du den folgenden Header konfigurieren:
 

From 85162c0498e5d67448f7d52aba776c2dce3af396 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:26 +0200
Subject: [PATCH 195/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/what-is-vitepress.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/what-is-vitepress.md b/docs/de/guide/what-is-vitepress.md
index 34b4ed2a0..ee370da2d 100644
--- a/docs/de/guide/what-is-vitepress.md
+++ b/docs/de/guide/what-is-vitepress.md
@@ -20,7 +20,7 @@ Du möchtest es einfach ausprobieren? Springe direkt zum [Schnellstart](./gettin
 
 - **Blogs, Portfolios und Marketing-Websites**
 
-  VitePress unterstützt [vollständig angepasste Themes](./custom-theme) mit der Entwicklererfahrung einer normalen Vite- und Vue-Anwendung. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [Daten laden](./data-loading) (lokal oder entfernt) und [dynamische Routen erzeugen](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Build-Zeit bestimmt werden können.
+  VitePress unterstützt [vollständig angepasste Themes](./custom-theme) mit der Entwicklererfahrung einer normalen Vite- und Vue-Anwendung. Da Vite die Grundlage bildet, kannst du außerdem direkt auf Vite-Plugins aus dessen umfangreichem Ökosystem zurückgreifen. Zusätzlich bietet VitePress flexible APIs zum [Daten laden](./data-loading) (lokal oder entfernt) und [dynamische Routen erzeugen](./routing#dynamic-routes). Damit kannst du nahezu alles erstellen, solange die benötigten Daten zur Erstellungszeit bestimmt werden können.
 
   Der offizielle [Vue.js-Blog](https://blog.vuejs.org/) ist ein einfacher Blog, der seine Indexseite auf Grundlage lokaler Inhalte erzeugt.
 
@@ -36,7 +36,7 @@ VitePress möchte eine hervorragende Developer Experience (DX) bei der Arbeit mi
 
 ## Leistung
 
-Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollständiges Neuladen der Seite auslöst, liefert eine mit VitePress erzeugte Website beim ersten Besuch statisches HTML aus und wird bei weiterer Navigation innerhalb der Website zu einer [Single-Page-Anwendung](https://en.wikipedia.org/wiki/Single-page_application) (SPA) Dieses Modell bietet unserer Ansicht nach ein ausgewogenes Verhältnis zwischen Leistung und Benutzerfreundlichkeit:
+Anders als bei vielen herkömmlichen SSGs, bei denen jede Navigation ein vollständiges Neuladen der Seite auslöst, liefert eine mit VitePress erzeugte Website beim ersten Besuch statisches HTML aus und wird bei weiterer Navigation innerhalb der Website zu einer [Single-Page-Anwendung](https://en.wikipedia.org/wiki/Single-page_application) (SPA). Dieses Modell bietet unserer Ansicht nach ein ausgewogenes Verhältnis zwischen Leistung und Benutzerfreundlichkeit:
 
 - **Schnelles erstes Laden**
 

From 0365f8cb8acafd110d1af40c6b879177cc5e65c0 Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:28 +0200
Subject: [PATCH 196/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/routing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/de/guide/routing.md b/docs/de/guide/routing.md
index 2f9840f60..0a4f43fab 100644
--- a/docs/de/guide/routing.md
+++ b/docs/de/guide/routing.md
@@ -35,7 +35,7 @@ In der Dateistruktur eines VitePress-Projekts gibt es zwei wichtige Konzepte: da
 
 ### Projektverzeichnis
 
-Das Projektstammverzeichnis ist der Ort, an dem VitePress nach dem speziellen Verzeichnis `.vitepress` sucht. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionalen Theme-Anpassungscode reserviert.
+Das Projektstammverzeichnis ist der Ort, an dem VitePress nach dem speziellen Verzeichnis `.vitepress` sucht. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Ausgabedateien und optionalen Theme-Anpassungscode reserviert.
 
 Wenn du `vitepress dev` oder `vitepress build` über die Kommandozeile ausführst, verwendet VitePress das aktuelle Arbeitsverzeichnis als Projektstammverzeichnis. Um ein Unterverzeichnis als Stammverzeichnis festzulegen, musst du den relativen Pfad an den Befehl übergeben. Wenn dein VitePress-Projekt beispielsweise in `./docs` liegt, solltest du `vitepress dev docs` ausführen:
 
@@ -63,7 +63,7 @@ docs/getting-started.md  -->  /getting-started.html
 
 Das Quellverzeichnis ist der Ort, an dem deine Markdown-Quelldateien liegen. Standardmäßig entspricht es dem Projektstammverzeichnis. Du kannst es jedoch über die [`srcDir`](../reference/site-config#srcdir) Konfigurationsoption festlegen.
 
-Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `srcDir: 'src'`, deine Dateistruktur sieht dann so aus:
+Die Option `srcDir` wird relativ zum Projektstammverzeichnis aufgelöst. Mit `srcDir: 'src'` sieht deine Dateistruktur so aus:
 
 ```
 .                          # Projektstammverzeichnis

From d488cdf0dbe3f14388a4f8b73f796bcc0667adeb Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:31 +0200
Subject: [PATCH 197/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/getting-started.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/de/guide/getting-started.md b/docs/de/guide/getting-started.md
index 9280738f9..d7281fae3 100644
--- a/docs/de/guide/getting-started.md
+++ b/docs/de/guide/getting-started.md
@@ -101,7 +101,7 @@ Angenommen, du hast das VitePress-Projekt in `./docs`, Die erzeugte Dateistruktu
 Das Verzeichnis `docs` gilt als **Projektstammverzeichnis** der VitePress-Website. Das Verzeichnis `.vitepress` ist für die VitePress-Konfigurationsdatei, den Cache des Entwicklungsservers, die Build-Ausgabe und optionale Anpassungen des Themes reserviert.
 
 ::: tip
-Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktions-Build-Ausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. Diese Verzeichnisse können ebenfalls [konfiguriert](../reference/site-config#outdir).
+Standardmäßig speichert VitePress den Cache des Entwicklungsservers in `.vitepress/cache`, und die Produktionsausgabe in `.vitepress/dist`. Wenn du Git verwendest, solltest du diese Verzeichnisse in deine `.gitignore` aufnehmen. Diese Verzeichnisse können ebenfalls [konfiguriert](../reference/site-config#outdir).
 :::
 
 ### Die Konfigurationsdatei
@@ -190,7 +190,7 @@ $ bun vitepress dev docs
 
 :::
 
-Weitere Informationen zur Verwendung der Kommandozeile findest du in der [CLI Referenz](../reference/cli).
+Weitere Informationen zur Verwendung der Kommandozeile findest du in der [CLI-Referenz](../reference/cli).
 
 Der Entwicklungsserver sollte unter `http://localhost:5173` laufen. Öffne die URL in deinem Browser, um deine neue Website zu sehen.
 
@@ -200,7 +200,7 @@ Der Entwicklungsserver sollte unter `http://localhost:5173` laufen. Öffne die U
 
 - Um mehr darüber zu erfahren, was du auf einer Seite tun kannst, etwa Markdown-Inhalte schreiben oder Vue-Komponenten verwenden, lies den Abschnitt „Schreiben“ der Anleitung. Ein guter Ausgangspunkt sind die [Markdown Extensions](./markdown).
 
-- Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Standard-Theme Config Referenz](../reference/default-theme-config).
+- Um die Funktionen des Standard-Dokumentationsthemes kennenzulernen, sieh dir die [Referenz zur Standard-Theme-Konfiguration](../reference/default-theme-config).
 
 - Wenn du das Erscheinungsbild deiner Website weiter anpassen möchtest, erfahre, wie du entweder [Standard-Theme erweitern](./extending-default-theme) oder [ein eigenes Theme erstellst](./custom-theme).
 

From f89732b8a267b46f0e95fd1f5671d951c8a09b0a Mon Sep 17 00:00:00 2001
From: Intense <intensed01@gmail.com>
Date: Sun, 27 Sep 2026 12:19:34 +0200
Subject: [PATCH 198/199] =?UTF-8?q?docs(de):=20Denglische=20Begriffe=20abs?=
 =?UTF-8?q?chlie=C3=9Fend=20bereinigen?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/de/guide/migration-from-vitepress-0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/de/guide/migration-from-vitepress-0.md b/docs/de/guide/migration-from-vitepress-0.md
index c3aac1b80..ab262b03f 100644
--- a/docs/de/guide/migration-from-vitepress-0.md
+++ b/docs/de/guide/migration-from-vitepress-0.md
@@ -12,7 +12,7 @@ Wenn du von einer VitePress-0.x-Version kommst, gibt es aufgrund neuer Funktione
   - Der Schlüssel `children` heißt jetzt `items`.
   - Ein Element der obersten Ebene darf derzeit kein `link` enthalten. Es ist geplant, dies wieder zu ermöglichen.
 - `repo`, `repoLabel`, `docsDir`, `docsBranch`, `editLinks` und `editLinkText` wurden zugunsten einer flexibleren API entfernt.
-  - Um einen GitHub-Link mit Symbol zur Navigation hinzuzufügen, verwende die Funktion [Social Links](../reference/default-theme-nav#navigationslinks).
+  - Um einen GitHub-Link mit Symbol zur Navigation hinzuzufügen, verwende die Funktion [Soziale Links](../reference/default-theme-nav#navigationslinks).
   - Um die Funktion „Diese Seite bearbeiten“ hinzuzufügen, verwende die Funktion [Bearbeitungslink](../reference/default-theme-edit-link).
 - Die Option `lastUpdated` ist jetzt in `config.lastUpdated` und `themeConfig.lastUpdated.text` aufgeteilt.
 - `carbonAds.carbon` wurde in `carbonAds.code` geändert.