Personal website planning: How can meaning and chronology stay accurate when presenting experience across languages?

When you maintain a personal website in more than one language, the first thing that tends to drift is chronology. A project listed as running from March 2020 to January 2021 in one version might get summarized as "about a year" or "nearly two years" in another, depending on how the writer rounds. These small differences accumulate, and a reader comparing versions—or a future you updating one version but forgetting the other—ends up with conflicting timelines. A practical way to reduce this is to keep a single dated record of your experience, separate from the website text itself, and treat each language page as a rendering of that record rather than an independent document. When you update one, you check the record first, then propagate the change.

Meaning drift is a related but distinct problem. Job titles, role descriptions, and skill labels rarely map one-to-one between languages. A title that carries a specific seniority implication in one language might sound either more or less senior when translated directly, and sometimes the closest equivalent in the other language refers to a different kind of role entirely. There is no universal fix for this, but you can note your choices as you make them. If you decide to use a broader term in one language because the exact equivalent would confuse readers, write that decision down next to the entry in your source record. That way, when you revisit the site months later, you can see whether the choice still makes sense or whether it has started to misrepresent the actual scope of what you did.

A third issue is that updates happen unevenly. You might add a new project to the English version because that is the language you are currently working in, and forget to add it to the other version until much later. By then the chronology in the second version has a gap that looks like inactivity. One approach that helps is to treat your source record as the place where new entries go first, before any language version is updated. The record holds the facts: what happened, when, and in what order. Each language page then gets updated from the record on its own schedule, but because the record is complete, neither version silently loses an event. You can also keep a short note in the record marking which language versions have been updated and which have not, so the gap is visible rather than hidden.

None of these steps guarantee that every reader will perceive your experience identically across languages, and that may not even be a realistic goal. What they do is give you a way to notice when the versions have diverged in fact rather than just in tone, and to correct the factual divergences without having to rebuild everything from memory. The source record does not need to be elaborate—a simple dated list with notes on translation choices is enough to start. The key habit is checking it before you edit any single language page, rather than editing one page and hoping the others still match.