Most interesting work this month came from a customer in Japan who wanted something I hadn't built called "Easy Japanese" (やさしい日本語), which is like a simplified version for non-native readers. Turned into supporting fully custom locales. Also been improving how the GH action picks up manual changes to target translations in commits, they now get ingested back for review, making things a bit more flexible.

On the side, https://infrabase.ai (AI infrastructure tools directory) had its best month yet, up ~40% visitors MoM. Interesting finding is still the GEO angle, visitors arriving from Claude/ChatGPT/Perplexity spend 2-6 minutes on the site. Been making comparison pages more "extractable" for AI answers with job-tagged tables and some have now held their Perplexity citations for weeks.

Good start of the month with user discussions and feedback.

Been pushing some new stuff on https://infrabase.ai as well, my AI infrastructure tools directory. Traffic growing steadily from comparison and alternatives pages. Interesting finding is that blog posts rank better but get fewer clicks now because AI Overviews, interactive comparison pages still earn clicks. ChatGPT has also started citing the site more as a source. Adding new content and polishing existing parts of it, added a page focusing on EU based services at https://infrabase.ai/european.

Also been spending some time on my old side project https://infrabase.ai, an directory of AI infra related tools. Redesigned the landscape page (https://infrabase.ai/landscape), going through product submissions and content, optimizing a bit for seo/geo.

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 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.

Comments URL: https://news.ycombinator.com/item?id=7953616

Points: 153

# Comments: 85