How Weet integrates localization into the GitLab pipeline with Lokalise

This post details how Weet integrated Lokalise with GitLab CI/CD to automate their localization workflow. Key technical contributions include: 1. Automating the extraction of text strings from the codebase into Lokalise upon each push to master. 2. Utilizing Lokalise's task features to assign translation work to the marketing team. 3. Creating merge requests from Lokalise for translated content, integrating it back into the development pipeline. 4. Implementing internal processes for managing localization data, including splitting it into multiple .json files based on component (emails, frontend, integration, server-side rendering, mobile), using a naming pattern for simplified key maintenance, and establishing rules for conflict resolution (developers only update labels in Lokalise, add/remove keys locally). This enables continuous localization within an hour for new releases.