MDX EN to ZH Post
Workflow
- •Read the source file from
content/posts/en/<slug>.mdxorcontent/posts/en/<slug>.md. - •Write the translated file to
content/posts/zh/<slug>.mdxorcontent/posts/zh/<slug>.mdusing the same slug. - •Translate natural-language content to Chinese:
- •Frontmatter text fields such as
title,type,project,summary - •Headings, paragraphs, list items, table text, blockquotes, callouts
- •Preserve non-language structure exactly:
- •Keep frontmatter keys and ordering stable
- •Keep
dateand file paths unchanged - •Keep code fences and inline code unchanged
- •Keep URLs and local asset paths unchanged
- •Keep MDX/JSX tags and attributes valid
Output Rules
- •Keep the target filename equal to the source slug.
- •Keep frontmatter keys present:
title,type,project,date,summary. - •Keep markdown heading depth and code-block count aligned with source.
- •Keep local links such as
/posts/...,/portfolio/...,/videos/...,/audio/...unchanged unless the source itself is broken.
Validation
Run:
bash
python skills/public/mdx-en-to-zh-post/scripts/verify_translation.py \ --source content/posts/en/<slug>.mdx \ --target content/posts/zh/<slug>.mdx
Fix any reported errors before finishing.
Style Guide
Use references/translation-style.md for tone and wording constraints.