What if we I18n jsr.io

[AugustinMauroy]

Hi 👋,

I would like to propose adding internationalization (i18n) support to JSR.io to make it more accessible to developers worldwide. Here's a basic overview of how we could structure this:

Implementation Areas

1. Landing Page

   • Simple i18n key-value pairs in JSON
   • Easy to maintain and update UI text

2. Documentation

   • i18n JSON for UI elements
   • Translated markdown files for documentation content
   • Each language in its own directory (e.g., /docs/fr/, /docs/es/)

3. Packages/Registry UI

   • i18n JSON for UI elements only
   • Package content and metadata remain untranslated
   • Covers navigation, buttons, and interface text

Translation Management

• Use Crowdin with GitHub Actions to keep translations in sync
• Makes it easy for the community to contribute translations
• Automated workflow for syncing changes

This would help make JSR more accessible to developers worldwide and strengthen our community-first approach.

Thoughts? 🤔