Hi Lightdash Team 👋 I'd love to suggest adopting a web-based translation platform (like Crowdin or POEditor) for future localization, similar to Metabase's approach. I previously contributed Japanese translations to Metabase, and the web UI made it incredibly easy to fix strings without Git or code changes. Since Lightdash is currently English-only, lowering this barrier from the start lets the community drive localization seamlessly—without adding any management or PR overhead to your dev team. Would love to hear your thoughts! 🚀

Hey Yuichiro, thanks for this - and cool that you've contributed Japanese translations to Metabase! We have an open feature request tracking localization support here: https://github.com/lightdash/lightdash/issues/14109 I've added your suggestion about using a web-based translation platform (Crowdin, POEditor, etc.) to that issue. It's a great point about lowering the barrier so community contributors can jump in without needing Git or PRs. No timeline on this yet. We'll keep you posted as things progress, and we'd love to have contributors like you involved when the time comes 🙂

I've upvoted issue #14109 for you! This issue has been requested by 5 other users. I'll notify everyone here as soon as it's fixed.

This issue and #5026 seem to cover the same ground — app-wide i18n/localization. Would it make sense to consolidate them here and close #5026 as a duplicate? This issue has a more comprehensive requirements list and is more actively tracked.

Hey Yuichiro, good callout, those two do overlap. Issue #5206 is the one prioritized internally, and both issues are linked with all the Github context. I'll flag this for the team though to consider consolidating!

I've upvoted issue #5026 for you! This issue has been requested by 4 other users. I'll notify everyone here as soon as it's fixed.