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:
Intense
3 days ago