Background
According to Google Trends data from around February 2026,
it was confirmed that interest in PostHog is gradually increasing in South Korea.
Problem Identification
Despite advancements in AI agents and machine translation,
Korean developers still rely on Google Translate, DeepL,
and similar tools to consume English-language documentation.
As a result:
- Context is not accurately conveyed
- Product understanding is reduced
- Friction arises during the learning and adoption process
- PostHog’s developer-friendly / geeky tone is not properly conveyed
For Korean developers, there is still a significant language barrier.
This leads to lower acquisition and conversion rates.
Scope of Work
Translate 3 piece of Newsletter,
- https://newsletter.posthog.com/p/the-golden-rules-of-agent-first-product
- https://newsletter.posthog.com/p/an-engineers-guide-to-product-management
- https://newsletter.posthog.com/p/10x-job-posts-for-10x-engineers
Considerations for the Work
The following options need to be evaluated:
-
Expanding the content system (introducing i18n)
- Necessary in the long term
- Large scope of changes (affects existing structure)
- Hard to roll back, slows down experimentation
-
Minimal changes to the build system for multilingual support
- Reduces change scope
- Allows some level of scalability
- Requires compatibility checks with existing structure
-
Serving Korean pages as static content
- Simple implementation, fast to experiment
- May increase maintenance cost
Implementation Principle
Because Gatsby changes can affect every static page on posthog.com, this experiment should keep Gatsby changes as small and localized as possible. Prefer static MDX content and narrowly scoped page/SEO support over broad i18n, navigation, search, Strapi, Algolia, or build-pipeline changes unless the owners decide the experiment should expand.
SEO Considerations
Comply with Google’s Multilingual/Multi-regional Guidelines
https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites
cc. @jina-yoon
Background
According to Google Trends data from around February 2026,
it was confirmed that interest in PostHog is gradually increasing in South Korea.
Problem Identification
Despite advancements in AI agents and machine translation,
Korean developers still rely on Google Translate, DeepL,
and similar tools to consume English-language documentation.
As a result:
For Korean developers, there is still a significant language barrier.
This leads to lower acquisition and conversion rates.
Scope of Work
Translate 3 piece of Newsletter,
Considerations for the Work
The following options need to be evaluated:
Expanding the content system (introducing i18n)
Minimal changes to the build system for multilingual support
Serving Korean pages as static content
Implementation Principle
Because Gatsby changes can affect every static page on posthog.com, this experiment should keep Gatsby changes as small and localized as possible. Prefer static MDX content and narrowly scoped page/SEO support over broad i18n, navigation, search, Strapi, Algolia, or build-pipeline changes unless the owners decide the experiment should expand.
SEO Considerations
Comply with Google’s Multilingual/Multi-regional Guidelines
https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites
cc. @jina-yoon