Website Localization Strategy Discussion

Date: 28 Aug 2025 Participants: Experts, Development Team

---

Topic

Implementation options for website localization (content translation).

---

Discussion Points

1. Content Translation via Admin Panel

   • Two strategies for enabling English localization were discussed:

     Strategy 1 – Translation Service Integration

     • The system will provide an “English mode.”
     • Ukrainian content will be translated into English through an AI-based API.
     • The administrator will be able to review, edit, and publish the translated content.
     • Provides a controlled workflow where translations can be refined before publication.
     • Rominos7’s preferred option.

     Strategy 2 – On-the-Fly Translation Switch

     • Each admin modal or page will include a switch to activate English mode.
     • Activating the switch triggers automatic translation of the displayed fields.
     • The administrator can edit the translated fields directly and save them.
     • Offers real-time preview but may complicate editing workflows.

2. Data Storage Considerations

   • Discussion on saving translated content in a NoSQL database (e.g., MongoDB) @maxvonlancaster TBD.
   • This approach would allow flexible handling of multilingual content files and improve scalability.

---

Key Takeaways

• The expert recommends proceeding with Strategy 1 (translation service integration with admin review).
• MongoDB or another NoSQL database may be used to store translated content for better scalability and content management.

Date: 18 Sept 2025 Participants: Experts, Development Team, BA, designers

---

Topic

Architecture of Localization feature

---

Architecture Description