Implement Multi-Language Support for Puzzle Content

[Mkalbani]

Description

Add internationalisation (i18n) support so that puzzle titles, descriptions, and hints can be served in multiple languages. As LogiQuest grows its player base globally, language should not be a barrier to participation. The system should allow admins to add translations for existing puzzles without duplicating the puzzle record or breaking existing sessions.

Acceptance Criteria

• A PuzzleTranslation entity stores puzzleId, locale, title, description, and translated hints
• GET /puzzles/:id accepts an Accept-Language header and returns content in the requested locale
• English (en) is the fallback locale when a translation is unavailable
• POST /puzzles/:id/translations (admin-only) adds or updates a translation for a given locale
• GET /puzzles/:id/translations (admin-only) returns all available locales for a puzzle
• Locale is validated against a supported list defined in config
• Session records store the locale that was active at start time for accurate replay
• Unit tests cover locale resolution, fallback to English, translation creation, and unsupported locale rejection

[Ebenezer199914]

i will love to work on this issue

[Okorie2000-code]

Hi Maintainer,

I'd like to work on this issue. I have experience with backend development and internationalization (i18n), and I can submit a clean PR within 48 hours.

[playmaker410]

Hi Maintainer,
I’d love to take this on. I have hands-on experience with Rust, Soroban, and TypeScript, and I’m confident I can deliver a solid solution within 24 hours.

[Primex-hub]

I would love to solve this issue

[sheyman546]

please i will love to work on this issue

[Justprotocol]

Hi Maintainer,

I would love to take on this issue and implement multi-language support (i18n) for the LogiQuest puzzle content. I have solid experience building localized backend systems and working with the tech stack here.

My Approach to Implementing This:

1. Database / Schema Configuration: I will set up the PuzzleTranslation entity to cleanly map puzzleId, locale, title, description, and translated hints without disrupting the existing schema.

2. Accept-Language Header Parsing: Update the GET /puzzles/:id endpoint to inspect the standard Accept-Language header, fallback gracefully to English (en) if a specific locale translation is missing or unsupported, and validate incoming locales against a configured whitelist.

3. Admin and Session Flow:

   • Implement POST /puzzles/:id/translations for secure admin-only updates.
   • Implement GET /puzzles/:id/translations for listing all available locales.
   • Bind the selected locale context cleanly to the active session state at start-time to ensure consistent, accurate replays.

4. Testing Coverage: Deliver comprehensive unit tests validating correct locale resolution, English fallbacks, successful translation creation, and strict rejection of unsupported locales.

I'm ready to begin immediately and can deliver a clean, fully-tested PR quickly!

[grantfox-oss]

🦊 GrantFox — @playmaker410 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #87)
2. Your PR will be reviewed by the MindFlowInteractive maintainers

Good luck! Track your progress on GrantFox.