We built Django-Garnett at Aristotle Metadata because we had a monolithic Django app and wanted to backport multilingual support for our clients in, without having to change references to fields in our templates and code in potentially thousands of places.
It allows clients to add and remove languages on-the-fly and means app developers only have to add a middleware and don’t have to change their Django ORM code very much at all.
We’re going to do a big engineering post on it, but in a huge code base, apart from the effort of building this library, and some UX design for the language switcher, it was a relatively painless process converting a monolingual app into a multilingual one.
It allows clients to add and remove languages on-the-fly and means app developers only have to add a middleware and don’t have to change their Django ORM code very much at all.
We’re going to do a big engineering post on it, but in a huge code base, apart from the effort of building this library, and some UX design for the language switcher, it was a relatively painless process converting a monolingual app into a multilingual one.
We have a fun demo site that shows it in action here: https://django-garnett.herokuapp.com/