i18n-editor is a tool for editing translation resources in JSON format.
Managing translation resources centrally can be a complicated task. Even something as simple as correcting a word in one language and updating it across all the others can take a lot of time.
That can turn a task that should be quick into a much longer one.
Because of that, I started trying public and paid tools. None fully met my needs, except BabelEdit. I used it during its free trial.
When the trial ended, I thought: “I can create and build a system with BabelEdit’s basic features.”
That spark got me started. I immediately began building a website with Angular. Within a few hours, I had a functional foundation for editing resources.
The visual interface, though, had 0% CSS—it looked like a site from the 2000s 😅.
After using i18n-editor heavily at work for a few days, I made several adjustments and improvements. Most importantly, my productivity improved considerably.
I no longer had to split my screen into ten side-by-side VS Code tabs to view and edit each JSON file (even an ultrawide monitor felt too small).
With i18n-editor, I could do the same work in a single window that took up half—or less—of the screen 😻.
Seeing how useful the tool was, I decided to share it with my circle of colleagues. I received constructive feedback, and later the first contributor joined, adding support for loading Excel files.
I’m writing this first post to share the beginning of this story and invite anyone interested to use and contribute to i18n-editor.
Thanks for reading 👋. Let me know your thoughts, questions, or suggestions in the comments 👇.