Is anyone handling their front end interface translations in an efficient way that doesn’t require constant developer resources?
I know that the JMS Translation Bundle is being used and it has a back-end admin interface for editing and creating translations that doesn’t require editing the YML files directly. However, this interface is not locked down behind a login system and is only recommended to be run in a development environment since it is writing directly to those files. So I get why this would not be a great idea to enable this. We are using platform.sh so we would have to enable Read/Write permissions on those translations folder and ignore them in git. That would mean we would need a way to pull down those translations locally to keep in sync.
I have left out an important part which is adding new translations to the TWIG templates. That would always remain a back-end developers job to edit that source code to apply new translations. What I am look for is adding new language translations so we have the front-end twig edits in English in place but when we bring on French or German we would want to create new translations only in the YML file.
I hope that makes sense. There are times where translations need to be modified and with the platform.sh set-up that would require a full environment rebuild for something pretty basic. If this is a true developer task then so be it but I’m investigating if there is another option.