[Question]: Internationalization (i18n) roadmap? Willing to help add Chinese supportย #11
Description
Question or Feedback
Thank you for this awesome project! Iโm wondering if there is a plan for internationalization (i18n), and Iโd love to help add Chinese (zh-CN) support.
Context and motivation
- This project has helped me a lot in my day-to-day work and in my homelab. I was thinkingโif it had Chinese support, that would make it even better and help more people use it.
- I noticed thereโs a โLanguageโ section in the settings menu, which looks like a UI placeholder but doesnโt yet switch the app language or persist the choice.
- Iโm not very familiar with this projectโs tech stack, so my understanding of best practices here may be limited. Iโd rely on prior experience implementing i18n in other frameworks and will follow the maintainersโ guidance.
Questions
- Do you have an i18n roadmap or a preferred approach/library (e.g. svelte-i18n / typesafe-i18n / i18next)?
- For the first phase, would you prefer a cookie/localStorageโbased language selection (no URL prefix), and consider SEO-friendly URL prefixes (e.g. /zh/) later?
How I can help
- I can open a minimal PR to introduce the i18n framework, add a zh-CN dictionary scaffold, wire the existing settings menu โLanguageโ control to the global locale and persistence, and translate several key pages.
- Iโm happy to follow any maintainer preferences on library choice, directory structure, key naming, route strategy, etc., and progressively expand translations.
- I can also provide a short contributor guide for adding/reviewing translations to encourage community contributions.
Acceptance criteria (suggested)
- Users can switch between English and Chinese in settings, and the choice persists across refreshes.
- Home, navigation, settings, and at least 1โ2 core pages switch key UI strings correctly.
- No build errors or noticeable performance regressions.
References
- typesafe-i18n: https://github.com/ivanhofer/typesafe-i18n
If you already have a direction in mind (naming conventions, language codes, routing preferences, etc.), Iโd be glad to align with it. Thanks again!