I stopped managing translations manually (and...

Managing multilingual content has always felt… wrong to me. In most projects, it quickly turns into: duplicated fields (title_en, title_fr) messy i18n JSON files constant synchronization issues At some point, I started wondering: why is this even a developer problem? Rethinking the approach Instead of treating translations as something external (keys, files, etc.), I tried a different approach: What if multilingual support was part of the data model itself? So I built a small Airtable-like syste