Figma integration

Add ability to use translations from Localesy directly in Figma

CMS Strategy and Integrations

Treat this as a place to discuss how Localesy should work with popular CMS platforms. Things that will need to be considered: Establish ideal workflow with CMS platforms How should integration look like? Plugin/Embed/Extension?

Localesy API for translating and accessing platform data

CLI for Developers

Publish `@localesy/cli` package to enhance developers' workflow for translating their app content. CLI could be also used for CI/CD pipelines where you could skip git repository integration entirely, provided you have your Localesy access key

Support more git providers

We currently support only Github, but it's only one of many platforms that serve as git providers. Add support for at least: Bitbucket Gitlab Azure Repos We can add more to that list based on demand from Localesy community

Advanced Access Control

Add support for more granular access control: Add roles like "Owner", "Translator", "Developer" with configurable access scopes Implement role guards across the platform to prevent unauthorised access

Preview before creating Pull Request

Display a preview of changes that will land in a Pull Request to ensure we're shipping right changes. Add ability to select which changes should land the created PR Add ability to preview raw output with applied formatting and sorting

Basic Organizations support

Add support for basic organizations support: Ability to invite users to organizations by sending an e-mail Ability to remove users when you're an owner Roles and more advanced access control is something we are planning to support in the near future

Fill Missing Translations with one click

Add ability to fill all missing translations: Manually - from Project view, by clicking on "Fill all missing translations" button On Base Translation change - when user edits base translation they should be prompted with "Want to translate all languages based on your changes?" On Pull from Github - same as above, whenever base translation gets updated we want to ask user if they want to translate all other languages based on new content This feature also creates new problems like: What if I only want to update a few selected changes? What if I only want to update values in a few selected languages? We thought about two potential solutions, that don't exclude each other: Display Diff Engine whenever user decides to auto-translate based on updated base translation entries Allow locking selected translation entries, so they never get updated, even when base translation changes and user wants to auto-generate the rest It is likely that both solutions will be available at some point

Basic Translation Entries management

Manage selected entries

Add ability to manage selected entries: Allow translating selected entries Allow removing selected entries Allow deselecting & deselect on save

Generate entire languages with one click

Add ability to generate a completely new language based on selected translation. Display modal asking for base and target language Inform about estimated tokens usage Generate translation entries in the target language Update tokens usage based on real usage

Support for enormous Translations

Add support for creating and editing huge translations (~15-25k translation entries per language)

Support for creating Github Pull Requests

Pull changes from Github

Diff Engine for resolving conflicts