We are deploying a forem instance in another language. Since the i18n issue will take sometime in such big and important project, we have two options (hacks?) to tackle it:
- Use a lambda function (or something else) on top of CloudFront and then regex keywords, phrases and so on. Since JS/CSS comes minified, it could be easy to avoid any wrong match (translating a css class, for instance)
- Regex the entire source code before each deploy in a simple bash script during CI/CD.
We do not need a perfect translation, just the main pages to help our users.
I think forking is not an option: it would create a huge merge every single time.
What do you say?