Thank you. Some of the comments were pretty helpful, they helped me improve performance by lazy loading a lot of the content, so it works a lot better now. I have seen the "critical HN comments" before on some other show HNs so I know what you're talking about though. Hope me being an inspiration helps fuel you to do a 24 hour type challenge as well! Maybe that could be a good idea to build a directory of people... - Source: Hacker News / over 1 year ago

I'm pretty sure, you'll find companies like this one which provide a nice GUI for helping with l10n or this one which offers translation services or this page that offers to convert between different formats, one of which probably has a nice GUI tool. Found them by 20 secs of googling. Source: about 1 year ago

Localise has no problem reading the json files or export to json, we recently started using it in collaboration with external translators. Source: about 1 year ago

Actually I don't have "my" app. But in our app we use https://lokalise.com/ to localize it even to Norwegian. Our team is not the most expensive company in the world btw. And we don't have 1B+ users all over the world. Source: about 1 year ago

Internationalization (i18n) pain for a documentation project is a process problem, not a feature gap. Documentation frameworks are not meant to translate your developer docs for you into the language of your choice. Some frameworks might offer i18n support, like the Crowdin support in Docusauraus v2. With Jekyll, you have to pick a theme like this one. I doubt if the reST or adoc frameworks would differ much from... - Source: dev.to / over 1 year ago

I've been thinking about building a micro saas very similar to this after having so many issues coordinating the localization of several products I manage. The only robust options in the market are incredibly expensive (for example https://lokalise.com/). Source: almost 2 years ago