Add possibility to publish only selected translations
Jakub Pomykała
Hey Thomas Wilhelm , thanks for the idea! I like it, and I’m sure we’ll get that functionality in the future. Right now, there isn’t a straightforward way to achieve this. Every publication is atomic, meaning it’s either 'everything' or 'nothing.' This approach makes it simple to manage and easy to revert, while also allowing us to clearly track the current state of a publication.
Could you please let me know why you would like to have this feature? I’ve been thinking about how we could implement something like this, as a similar request has come up before. I believe both approaches might solve the problem, but they target different use cases (I won’t go into more details as I don’t want to make it suggestive 😉).
Here are two possible approaches I’ve been considering:
- We could add an option to directly ‘push’ updates for specific translation keys (and their translations) from the Translations tab to any hosting environment without performing a full publication. The next ‘full’ publication to that environment would overwrite those changes to keep everything in sync.
- The second option would be to allow direct modifications to keys and translations for a given resource in the Hosting tab. This would skip the step of changing the translation in the editor, allowing you to edit a single resource directly (or import it from the web editor). The downside here is that you might need to update multiple translation files, like the English translation in the _index file and the resource file with just English translations. However, this typically wouldn’t be an issue, as only one of those files is commonly used in the end.
Both ideas are intended for emergency situations where you need to update specific translations to fix a production issue, and for some reason, you can’t revert or perform a full publication.
At the time of writing this, I’m not sure how the Activity Log should reflect these actions. Ultimately, I want to keep it as simple and clear as possible to avoid confusing users.
An alternative solution is to use a custom hosting provider: https://simplelocalize.io/docs/translation-hosting/custom-hosting-providers/, which gives you full control over the published resources, but it’s not very user-friendly.