Moved every string into a content tree
Moved every user‑facing string out of Python into a content tree of
874 files across three languages, after finding dead translations
nobody could see were dead and a check silently grading a third of
the achievements.
August 2026

Situation. Every user‑facing string in the generator — every
achievement, every review, every section heading, every summary, in
three languages — lived inside Python source. That makes editing a
sentence a code change, makes reviewing a translation a diff against
source, and makes it impossible to tell at a glance whether a
language is complete. It also hides the failure mode that matters: a
translation can be present, wrong, and unreachable at the same time.

Task. The strings had to move out of code into a content tree that
can be counted, compared across languages, and checked without
running the renderer.

Action. The result is 874 files under a content directory, organised
by kind and then by language: achievements, reviews, summaries,
titles, companies, regions, categories, services, profiles,
references and cover‑letter fragments. Tab‑separated files where the
unit is a line with an identifier, individual files where the unit
is a paragraph. The loader reads them at build time and the database
is assembled from them, so the tree is the source and the database
is derived. Two findings came directly out of being able to count.
Some translated strings no longer had any English counterpart — dead
entries that nothing rendered and nobody could have noticed while
they were embedded in code, because an unreferenced dictionary key
looks exactly like a referenced one. And a content check that was
supposed to grade every achievement was reading only the subset it
could resolve, grading thirty‑seven of ninety‑three and reporting
success. Making the corpus a directory made both of these visible as
a mismatch in file counts.

Result. The prose is now editable without touching code and
comparable across languages by counting. The cost is that adding a
language is now unambiguous rather than gradual — the tree makes an
incomplete language obvious, which is the point, but it also means
partial translations cannot be shipped quietly while they are being
finished.

Categories:
1Backend Engineering	/categories/backend/	software.engineer.company	70
1Data Governance	/categories/data-governance/	software.engineer.company	70
1Migrations & Modernization	/categories/migration/	software.engineer.company	70
1Python	/categories/python/	software.engineer.company	70
1Internationalization	/categories/i18n/	software.engineer.company	70
1Documentation	/categories/documentation/	software.engineer.company	70

Services:
1Backend & API Development	/services/backend-development/	software.engineer.company	70
1Internationalization & Localization	/services/i18n-localization/	software.engineer.company	70
1Database Migration & Modernization	/services/database-migration/	software.engineer.company	70
1Data Governance & Quality	/services/data-governance/	software.engineer.company	70

hThis page on the web	URL:https://software.engineer.company/portfolio/moved-every-string-into-a-content-tree/	software.engineer.company	70
