Pantheon VS Lokalise

Pantheon.io — Drupal and WordPress hosting, automated DevOps, and scalable infrastructure. Free for developers and agencies. No custom domain. - Source: dev.to / 3 months ago

Creating an account at pantheon.io (its free) and setting up a base install of a drupal 10 site there, learning how you can use their git repo to work with your code base, and hosting the site there. (sandbox environments are free). Source: 11 months ago

I run a majority of my client work on pantheon.io - you can read a case study of a high traffic site I launched there, 9 years ago, that handled a homepage link from nytimes.com with zero problems https://pantheon.io/blog/tavern-green-gets-details-right-pro-website-alphex-pantheon. Source: 11 months ago

Regardless of which way you go,yYou can give it all a try for free by creating an account on Pantheon, which will let you spin up a free Drupal sandbox site, as well as a free WordPress sandbox site. Source: about 1 year ago

I had to do this for a job a few years ago. I created a sandbox version of the site on pantheon.io and removed all editing permissions. On additional discovery that they only needed the static content, I created a static site using SiteSucker (mac app store). They were able to put this folder on their local machine to access anytime. Source: 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: 11 months 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: over 1 year ago