Skip to content

Feature request: make the website translatable (i18n), Basque translation available #85

Open

Description

@ederto1987

Hi CachyOS team,

I'm a Basque (eu) translator and I've recently been working on localizing CachyOS into Basque:

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.

Thanks for CachyOS!

Activity

  1. ufortstephen commented on Nov 10, 2026

    @ufortstephen

    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.

  2. ederto1987 commented on Nov 11, 2026

    @ederto1987
    Author
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions