At prosalmontech, internationalization (i18n) is not an afterthought; it is an architectural cornerstone woven into our web services, mobile tools, and technical documentation. Yet, building an agile multilingual publication pipeline proved far more complex than anticipated.
In this article, I share the operational friction we faced with our initial Headless CMS (Contentful), the decisive pivot back to static Markdown/HTML, and our strategic roadmap for serving international students across Asia.
1. Why Multilingual Blogging Matters to an Indie Educator
For most solo developers, publishing in a single language offers the highest return on investment. For prosalmontech, however, the primary motivation stems directly from the Japanese language classroom.
My students originate from Nepal, Vietnam, Myanmar, China, Korea, Indonesia, and Thailand. To support their employment journeys, visa qualifications, and everyday life in Japan, I have engineered multilingual tools like JPQuiz and Konnichiwork. Documenting engineering decisions and educational methodologies in languages accessible both to global technologists and non-native Japanese learners is central to our mission.
2. The Contentful Experiment and the "English-First" Dilemma
When initially spinning up this blog, I adopted Contentful, a renowned headless CMS with robust REST/GraphQL APIs and built-in locale management.
However, practical day-to-day writing surfaced unexpected workflow roadblocks:
- Strict English-First Publishing Constraints: Under Contentful's default locale hierarchy, English served as the parent root. Even when draft articles were conceived and authored primarily in Japanese, the publishing engine would prevent releasing the Japanese version unless the English entry had been populated and synchronized.
- Interface Friction: Managing rich text fields, asset reference hierarchies, and per-locale metadata across dozens of clicks diluted the spontaneous momentum essential for rapid technical writing.
- API Rate Limits and Static Build Bottlenecks: As article counts multiplied across languages, static site generation triggered hundreds of external API calls, amplifying the risk of build timeouts on edge hosts.
3. Returning to Static Markdown: The Power of Simplicity
This experience reinforced an enduring engineering principle: relying on simple, Git-versioned plain files (Markdown and static HTML) offers vastly superior durability, velocity, and ownership over proprietary hosted CMS ecosystems.
Today, our articles reside as local files version-controlled directly within Git. Synchronizing translations between Japanese and English is accelerated through custom CLI pipelines and agentic tooling, eliminating graphical overhead while preserving complete autonomy over markup structure.
4. Expanding to Nepali and Southeast Asian Languages
Extending our content pipeline to non-Latin scripts such as Devanagari (Nepali) and Burmese presents exciting technical frontiers:
- Font Performance & Glyph Rendering: Complex conjunct consonants in Devanagari demand proper font subsetting and glyph rendering to maintain crisp typography without degrading Core Web Vitals.
- Nuanced Technical Translation: Literal machine translations frequently distort programming idioms. Prompt engineering must balance conceptual paraphrasing in the native tongue with standard English terminology in brackets.
- hreflang & Search Console Integrity: Enforcing precise canonical targets and reciprocal hreflang annotations ensures search engines accurately route international audiences without duplicate content penalties.
5. The Road Ahead
Authoring thoughtful technical analyses in Japanese, refining them into high-fidelity English editions, and localizing core insights into the native languages of our students form the distinctive engine of prosalmontech. We remain committed to breaking linguistic barriers through code and education.