Skip to content

Korean and English versions

Once the Korean version is out, you can make the post’s English version. blog-studio keeps Korean as the source and makes the English translation as a pair, putting each up on its language’s blog. If you don’t run an English blog, you can skip this step.

Call it in natural language.

make the English version of the post I just wrote too

Or “just translate it.” blog-localization reads the Korean source, makes the English version, and piles it up as a pair at _workspace/posts/new/en/{category}/{slug}.md.

The translation isn’t literal. It carries over into the English reader’s context while preserving the Korean version’s units of meaning. It doesn’t pad the length with literal translation; it rewrites the same message at an English pace.

2) The spot where the two point at each other

Section titled “2) The spot where the two point at each other”

The Korean and English versions are bound by frontmatter. The Korean version points at the English one with hreflang_en, and the English version points at the Korean one with hreflang_ko.

# Korean version
lang: "ko"
hreflang_en: "/posts/en/{category}/{slug}"
# English version
lang: "en"
hreflang_ko: "/posts/ko/{category}/{slug}"

This cross-reference is what lets a search engine recognize the two posts as different-language editions of the same post. If only one is made or a path drifts, the two posts end up apart. The path mapping is automatic, so a human doesn’t have to align it every time.

Normal screen: the English staging file path shows, and the Korean and English versions are paired under the same slug.

Terminal window
find _workspace/posts/new -iname "*{slug}*" -print

Two lines should come up. If only one shows, the translation hasn’t happened yet or the slug has drifted.

4) ko/en parity is checked once more before publishing

Section titled “4) ko/en parity is checked once more before publishing”

The pre-publish quality gate (quality-check) looks at ko/en parity. It confirms the core message matches, the H2 structure corresponds, the data matches, hreflang points at each other correctly, and the slugs are the same. It has to clear this check to move to publishing. So a human doesn’t have to align the two bodies line by line; the gate catches the spots that drifted.

Once the Korean and English versions are paired, go to publish, the spot for putting it up on Blogger.