Building https://localhero.ai, automated on-brand i18n translations that run in your CI pipeline. Right now I'm working on better .po/gettext support, based on feedback from an early customer. With gettext you usually keeps source strings in the actual source code. So I'm building a workflow where non-technical people (PMs, designers) can edit translations in the web UI and then easily generate a PR with both code changes and translation file updates. Trying to make translations work smooth for both automated CI pipelines and PMs/designers who don't live in Git, when translations are checked into the repo. Also going through my network, talking to devs and localization folks to understand what could be improved in their orgs for translations.

Nice! We use an internal workflow with translations by llms at Minut. This looks smoother, esp as everything is driven through the PR. Swapped out lokalize for cost reasons.

Edit: we’re Malmö-based, lmk if you want to chat.

Cool, I'll drop a dm on linkedin!

Building https://localhero.ai, automated on-brand i18n translations that run in your CI pipeline.

Right now I'm working on better .po/gettext support, based on feedback from an early customer. With gettext you usually keeps source strings in the actual source code. So I'm building a workflow where non-technical people (PMs, designers) can edit translations in the web UI and then easily generate a PR with both code changes and translation file updates. Trying to make translations work smooth for both automated CI pipelines and PMs/designers who don't live in Git, when translations are checked into the repo. Also going through my network, talking to devs and localization folks to understand what could be improved in their orgs for translations.

I'm building https://localhero.ai. Automated i18n translations that run in your CI pipeline.

I have worked as dev in many different constellations of the years, and seen many teams choose between bad options like delay feature launches for manual translations, ship incomplete translations and promise "we'll translate it later," or lately use ChatGPT/LLMs that lose consistency/context and require coordination.

Localhero starts from the premise that translations are part of CI. New strings get translated automatically in GitHub Actions, with glossaries and style guides so it sounds like your product and not generic AI output.

Goal is to help product teams ship localized features without all the coordination/delay.