Localization: first class citizen

[bumbus]

Hi, I am not sure if you have already tackled this topic: translations. The world has seen some CMSs in the past where the ability to translate things was just added later via plugins etc., which quite often resulted in clumsy development experience (e.g. interop with other addons etc.) and UX for the content authors. For sure there are others which integrate translatable content very well. I just wanted to wake your awareness on this topic, because I believe it will be useful feature.

Cheers

[leandrocp]

Hi @bumbus do you have some examples of good implementations to share? Thanks.

[sachamasry]

Hi @leandrocp ,

Even though this is an old issue, it's still open, so I thought I might chime in. I've been using the Apostrophe 3 CMS (apostrophecms.com), which is Vue-based (I believe), very flexible and open-source. It has excellent localisation built in, though it does use a module to provide the actual functionality, (localization). Once all the locales are defined in a configuration file, every content type which is authored in one language, will show as not having a translation into the other ones configured, and the user will be prompted to make the necessary translation, and subsequently every time further edits are made to the document. The project documentation is good, and their screenshots do a good job of illustrating the process: dynamic i10n.

For all developer-created modules, static localisation to strings used in the admin interface are made in JSON files, one per language.

I haven't used any others, so it's difficult to say if it's clumsy as the OP states, but it has worked well for my customer's simple needs. The project's CMS is used by Michelin, who reportedly use it on 400 of their various sites, so it stands to reason that they find it usable.

I can easily create a simple repository if you wanted to audition it yourself.

Hope that helps

[leandrocp]

It certainly helps! Thanks for sharing such detailed feedback, I'll look into that.