Skip to content
Translation live preview
All projects

Translation

Translate 100+ project descriptions consistently instead of paying per-word machine translation fees.

Serving both English and Thai audiences meant translating a growing library of content, and per-call translation APIs got expensive fast.

Tech Domain · Book Dev|Published|Evidence: Live|Next.js, TypeScript

A public deployment is available to try.

Case Study

Before

The portfolio serves both English and Thai audiences, but manually translating 100+ project descriptions and blog posts was impractical. Machine translation APIs were expensive at scale.

After

Made bilingual content production sustainable at scale instead of translating post-by-post. The translation memory ensures consistent terminology, and batch processing enables translating entire content updates in one operation.

How it's solved

Built a translation utility that integrates with free translation APIs, supports batch processing for content files, and maintains a translation memory for consistent terminology across the portfolio.

Trade-offs

Machine-translated content still needs a human pass for nuance — it's a first draft, not a final translation.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev

Translation - Chaowalit Greepoke Portfolio