
Headings, links, code blocks, and frontmatter stay intact. Your documentation translated, your formatting preserved.
Markdown formatting is easy to write but fragile to translate. One extra space kills a heading. A translated link label breaks the URL. Code blocks get localized when they shouldn't. Front matter YAML gets corrupted. The result: broken docs that need hours of manual cleanup.
Headings, bold, italic, and list markers break when translators add or remove characters
Link labels get translated but URLs get corrupted or mangled in the process
Inline code and code blocks get translated when they should stay in English
YAML frontmatter (title, description, slug) gets corrupted or partially translated
---
title: Getting Started
description: Learn how to set up your project
---
# Getting Started
Welcome to **MyApp**! Follow these steps:
1. Install the package:
```bash
npm install myapp
```
2. Configure your `config.yml` file
3. Run `myapp init` to initialize
> Need help? Check our [FAQ](/faq) or
> [open an issue](https://github.com/myapp).---
title: はじめに
description: プロジェクトのセットアップ方法
---
# はじめに
**MyApp**へようこそ!以下の手順に従ってください:
1. パッケージをインストール:
```bash
npm install myapp
```
2. `config.yml`ファイルを設定
3. `myapp init`を実行して初期化
> ヘルプが必要ですか?[FAQ](/faq)または
> [Issueを作成](https://github.com/myapp)してください。Headings, bold, italic, lists, blockquotes, and tables are preserved. No broken formatting.
URLs stay untouched. Link labels are translated. Image alt text is localized. Reference links are handled.
Inline code and fenced code blocks are left in English. Only the surrounding prose is translated.
YAML frontmatter is parsed structurally. Title and description are translated. Slugs and dates stay unchanged.

No manual copy-paste. No string extraction. Just translated files.
Still stuck on a TMS contract? Let's talk about migrating.