Blog Post Translation (Korean → English)
Process
- •
Read the specified MDX file (or ask which post to translate)
- •
Review the Korean version first
- •Run a quick quality check (frontmatter, structure, code blocks)
- •Flag any issues in the Korean version before translating
- •
Translate the post
- •Translate title, description, and body content to natural English
- •Keep all code blocks, frontmatter field names, and technical terms unchanged
- •Preserve MDX component usage and JSX syntax exactly
- •Maintain heading hierarchy and document structure
- •Adapt Korean-specific idioms to natural English equivalents
- •
Save the translated version
- •Create
content/blog/<slug>.en.mdxalongside the Korean version - •Update frontmatter: keep same date and tags, translate title and description
- •Create
- •
Post-translation review
- •Verify MDX syntax is valid
- •Check that code blocks and inline code are untouched
- •Ensure natural English tone (not machine-translated feel)
Translation Guidelines
- •Use active voice where possible
- •Keep sentences concise and clear
- •Technical terms should follow common English conventions
- •Don't translate brand names, library names, or API names
- •Preserve original formatting (bold, italic, links)
- •Code comments inside code blocks: translate to English