lokalise-reference-architecture

# Lokalise Reference Architecture ## Overview A production-ready architecture for integrating Lokalise into web applications. Covers the end-to-end translation flow from source code through CI/CD and Lokalise to deployed translations, recommended project structure for i18n, file organization conventions, multi-app translation sharing, and the tradeoffs between OTA (over-the-air) and build-time translation loading. ## Prerequisites - Node.js 18+ with TypeScript - `@lokalise/node-api` SDK installed (`npm install @lokalise/node-api`) - An i18n framework selected (i18next, react-intl, vue-i18n, or equivalent) - Lokalise project created with at least one source language configured - Basic understanding of CI/CD pipelines (GitHub Actions, GitLab CI, or equivalent) ## Instructions ### Step 1: Architecture Diagram The translation lifecycle follows this flow: ``` ┌─────────────┐ ┌──────────┐ ┌─────────────┐ │ Source Code │────▶│ CI/CD │────▶│ Lokalise │ │ │ │ (upload) │ │ (TMS) │ │ en.json │ └──────────┘ │ │ │ t('key') │ │ ┌────────┐ │ └─────────────┘ │ │Transla-│ │ │ │ tors │ │ │ └────────┘ │ ┌─────────────┐ ┌──────────┐ │ │ │ Deploy │◀────│ CI/CD │◀────│ Download │ │ │ │ (build) │ │ │ │ CDN/Server │ └──────────┘ └───...