You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature request: make the website translatable (i18n), Basque translation available #85
Calamares (upstream, Transifex): Basque now at 100%
The website (cachyos.org) is currently English-only and its texts are hardcoded in the Astro components, so there's no way to contribute a translation without changes on your side.
Would you be open to making the website translatable? Astro has built-in i18n routing (e.g. /eu/, /fr/, /es/), and the wiki already handles several languages with Starlight, so a similar approach could work here. The main pages (home, about, download) are fairly short, so the translation effort per language would be small.
If you decide to add i18n support, I'd be happy to provide and maintain the Basque translation, and other translators from the wiki would probably contribute their languages too.
Hi @ederto1987 and CachyOS team! You've already translated the Welcome app, Kernel Manager, the package installer and Calamares into Basque, so the website is the last piece still English-only.
I can do the setup so translators only ever edit one JSON file per language and never touch the Astro components. I'm building localize.dev, which handles that part: it moves the hardcoded text out of the components into src/locales/en.json with readable keys, and the diff only touches the strings themselves. On main that's about 120 strings, including the FAQ and the edition descriptions on the download page.
The PR would:
add Astro i18n routing, English at / and other languages under /eu/, /es/ and so on, like the wiki
cover home, about and download, with no visible change to the English site
add a small language switcher
include a Basque draft for @ederto1987 to correct or replace
optionally add a CI check that flags new English text with no translation, so translators can see what changed after each update
Team member and sponsor names would stay as they are. Would you be open to it? I can start with just the download page if a smaller PR is easier to review.
Thanks a lot for the proposal, @ufortstephen! I fully support it: one JSON file per language without touching the Astro components is exactly what makes it easy for translators.
Of course, the decision is up to the CachyOS team. A few thoughts from the translator side:
- Starting with the download page sounds like a good way to keep the first PR small and easy to review.
- I'll review the Basque draft and correct or rewrite it so it matches the terminology I used for the Welcome app, Kernel Manager, the package installer and Calamares.
- The CI check for untranslated strings would be really helpful.
- If the team uses a translation platform (Weblate, Crowdin…), the `src/locales/*.json` files could be connected to it later, so translators who don't use Git can contribute too.
Just tag me when the PR is open and I'll take care of the Basque (`eu`) locale.
Eskerrik asko!
2026(e)ko azaroaren 10(a) (18:58), "Ufort Stephen" ***@***.*** ***@***.***?to=%22Ufort%20Stephen%22%20%3Cnotifications%40github.com%3E > idatzia:
Activity
ufortstephen commentedon Nov 10, 2026
Hi @ederto1987 and CachyOS team! You've already translated the Welcome app, Kernel Manager, the package installer and Calamares into Basque, so the website is the last piece still English-only.
I can do the setup so translators only ever edit one JSON file per language and never touch the Astro components. I'm building localize.dev, which handles that part: it moves the hardcoded text out of the components into
src/locales/en.jsonwith readable keys, and the diff only touches the strings themselves. Onmainthat's about 120 strings, including the FAQ and the edition descriptions on the download page.The PR would:
/and other languages under/eu/,/es/and so on, like the wikiTeam member and sponsor names would stay as they are. Would you be open to it? I can start with just the download page if a smaller PR is easier to review.
ederto1987 commentedon Nov 11, 2026