Back to writing

Building in Public

I’m Keeping the English Version Small for Now

A language switcher is easy. Maintaining two useful versions of a small website takes more thought.

Lingfeng · 265 words · 2 mins

While picking a template for my personal site, I casually added one more requirement: Chinese and English.

Chinese will be the main language. I just want someone visiting the English version to understand who I am, what I work on, and what I’ve built. It sounded simple until I started comparing themes.

A lot of them have a language switcher. You click EN, the navigation changes, and the job looks done. But what happens when a visitor opens a Chinese article? Does the button take them to a matching English article, or dump them on the English homepage? And what if no translation exists?

I don’t want a button that promises more than the site actually provides.

For the first version, I’ll translate only the homepage, About page, a few projects, and selected articles. Everything else can stay in Chinese until there’s a good reason to translate it.

I’ll keep the URLs predictable: /blog/ for Chinese and /en/blog/ for English. When two posts have the same content, they’ll be linked as translations; if there’s no English version, the site should say so. Basic language metadata and hreflang need to be correct too.

I’m also not aiming for word-for-word translation. A casual Chinese sentence about “tinkering with a tool” shouldn’t become awkward English just because the words line up. AI can help draft a translation, but names, facts, links, and tone still need a human check.

Comments, automatic translation, and a full CMS can wait. I want a site I can publish today and still maintain a year from now—not another complicated system to look after.

↑