# Make contributing translations easier
**URL:** https://discourse.nodered.org/t/make-contributing-translations-easier/74368
**Category:** Feature Requests
**Created:** [29 January 2023 17:16 UTC](https://discourse.nodered.org/t/make-contributing-translations-easier/74368 "2023-01-29T17:16:26Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@samuelstroschein](https://discourse.nodered.org/u/samuelstroschein)
#### Post date: [29 January 2023 17:16 UTC](https://discourse.nodered.org/t/make-contributing-translations-easier/74368/1 "2023-01-29T17:16:26Z")
Hello everyone,
I stumbled upon multiple issues (#3802) and questions from the community on how to contribute translations, see Discourse discussion 5366.
The [inlang/inlang](https://github.com/inlang/inlang) project I maintain might be of use for Node-RED. It provides contributors and translators with a UI to manage translations in a repository and contribute via PRs. There is much more to the project like a CLI, CI/CD, ide extension, and more but the editor seems to be of particular use for node-red.
No workflows need to be changed, no accounts created, nothing. Just a simple config file in the repo is required. The result of adding a config file would be similar to [https://inlang.com/editor/github.com/inlang/example](https://inlang.com/editor/github.com/inlang/example).
Would it be beneficial if I create a PR with the config file? And generally, what could I built to make localization for devs easier?
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [30 March 2023 17:16 UTC](https://discourse.nodered.org/t/make-contributing-translations-easier/74368/2 "2023-03-30T17:16:26Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.