Pretty early in the journey your community will exist beyond a single project repository. Contributions will be spread across multiple repos. People will follow you on Twitter or join your Discord server (I created ours today, come join us!). Being hyper-focussed on a single project risks missing the forest for the trees. Success then brings its own challenges: there's a lot of activity, too much to guarantee... - Source: dev.to / over 1 year ago

But meanwhile I got to play around with Orbit. It is a community growth platform. It already fell in love with it as it gives you so much information about your community out of the box. - Source: dev.to / over 1 year ago

Not sure if it work for you, but take a look at Orbit - https://orbit.love/. Is this what you are looking for? - Source: Hacker News / over 1 year ago

Check out Orbit - we have connectors for lots of platforms, including Reddit. Our customers include Miro, Patreon, Stripe, and a whole bunch of others. Source: over 1 year ago

HACK: If you want to save all of your current slack messages, sign up for https://orbit.love, connect it to slack, and then grab the messages from the API. Not sure how much longer this will work, it takes time and they may catch on. I do like Orbit as a user, still a relatively new product. - Source: Hacker News / almost 2 years 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