[Grollicus]

They seem to store all translated strings in a single jsonfield instead of using a separate column for each language.

That means there's a bit more overhead while loading (and you can't exclude unneeded language fields), but it allows dynamically changing languages during runtime without needing a migration.

[andrewingram]

With Django's ORM and PostgreSQL, it is possible to map specific keys of a JSONField to an annotation. But I don't know if the overhead of doing this would undo the gains from not sending data for every language in the query result.