inlang

An ecosystem to globalize software (i18n, localize)

🕹️ Apps · 📄 Docs · 💙 Discord · 𝕏 Twitter

What is inlang?

Inlang is an ecosystem of interoperable lix apps to globalize software.

Every app in the inlang ecosystem shares the same review, automation, and collaboration layer, making cross-team collaboration possible. No syncing, hand-offs, or automation barriers.

Example apps

• Paraglide.js to have a fully translated, typesafe & fast app in minutes
• Sherlock to translate your app right in the editor
• Fink to translate your app in the browser & invite collaborators to help you
• Parrot see translations directly in Figma
• inlang CLI to lint your messsages with lint rules or machine translate them & have quality control in CI/CD
• build your own app / plugin / lint rule with the inlang SDK
• ...

Why inlang?

Globalizing software is a cross-team effort that involves ensuring compliance, adapting the design, handling different currencies, managing translations, writing different marketing copy, etc.

Existing point solutions such as apps to manage translations (Lokalise, Weglot, Smartling), apps to manage design copy (ditto, translator), or i18n libraries for developers (next-intl, i18next) don’t have interop between each other.

The lack of interop of existing solutions leads every app and team to have its own collaboration layer, review system, and automation capabilities. Cross-team collaboration and automation, which are required to globalize software, are difficult to impossible.

Contributing

There are many ways you can contribute to inlang! Here are a few options:

• Star this repo
• Create issues every time you feel something is missing or goes wrong
• Upvote issues with 👍 reaction so we know what the demand for a particular issue to prioritize it within the roadmap

If you would like to contribute to the development of the project, please refer to our Contributing guide.

All contributions are highly appreciated. 🙏