vitepress-bilingual-page

To add a bilingual VitePress page, create markdown files with proper frontmatter for titles and asides, configure clean URLs, and wire the path into the navigation. Verify the build to ensure correct i18n routing.

VitePress i18n path conventions separate translated content into distinct directory structures, while standalone legal pages like privacy policies use specific file layouts outside the standard guide bilinguals to maintain URL cleanliness.

The best way to wire a privacy policy into VitePress navigation is to add the page path to the operations nav configuration, then run a build verification to confirm the routing and clean URL setup function correctly.

Yes, you can use frontmatter to enforce titles and asides for VitePress i18n pages. This approach ensures both EN and PT-BR translated content displays correctly without modifying the core site configuration.

A new VitePress bilingual page might not show in navigation if the file placement violates i18n path conventions or the operations nav configuration lacks the correct clean URL path, requiring a build verification to troubleshoot.

No, this VitePress bilingual approach does not require external dependencies. It leverages built-in frontmatter configuration, native clean URL settings, and standard directory layouts to manage EN and PT-BR translations.