Before you get into today's topic, read the previous articles in this series to see what you can achieve with Automated Workflows:
- Translate Content Immediately After Uploading with MT
- Fine-Tune Your UX Copy Before Translating It
- Prevent Translation of Unwanted Strings
- Apply Any Filters (with AI!✨)
- Delete Deprecated Keys Automatically
❓ Why automate showing keys? 🔗
When going through a migration or project rebranding, there may be a bunch of keys that contain obsolete words, such as the old name of your app or links, etc. They are still present on Localazy and visible to translators, so if you keep translating your project while migrating/rebranding it at the same time, your translators could end up focusing on translations that will later be changed. That's a waste of their time and your money.
One possible solution is to stop translating everything until all texts are adapted for the new version. This could slow down the process and put pressure on the product team.
The other option is to hide the keys containing specific keywords so they are invisible to translators. That's a simple solution, but you need to remember to show these keys again as soon as they are migrated/rebranded. Or, our Automated Workflows can do that for you!
⚙️ Setting up the workflow 🔗
1. Hide all the obsolete keys 🔗
Just navigate to your project on Localazy, go to the source language management, and filter out keys containing your specific keywords. Select them all and hide them.
2. Create and configure a new workflow 🔗
Navigate to Workflows in the console and select the project you want to automate. Now, create a new empty workflow. You can name it as you want; I chose Show migrated keys, so it's descriptive.
My new workflow is ready, but it's empty and paused. Let's edit it.
Be sure to enable the workflow, as they are disabled by default for security reasons. Also, select the desired action, which is to Show keys.
We want to trigger the event if the keys are updated, so out of the possible Trigger Events, we just need the Key or translation updated, nothing else. Also, since, by default, the Show key action is only applied to the source language, we can keep the Apply to all events checkbox ticked.
Filters can be helpful when you want to limit the workflow to a specific subset of keys. Read more about them here.
Save the workflow and verify that it's enabled and ready to roll. That's it. All is configured!
3. Upload content periodically while migrating/rebranding it 🔗
Whether you upload your files manually or via CLI, keep uploading them periodically as you change them to update the old names and links to new ones.
Whenever new updated keys appear, the workflow will be run, and keys that match the filter will be automatically shown if they were hidden before. It won't matter if you spend one day or one month reorganizing your project; you'll never need to think about the process again.
✅ Conclusion 🔗
In conclusion, automating the process of showing keys during migration or rebranding projects saves time and resources by letting translators focus on relevant translations. Utilizing Automated Workflows streamlines the process effortlessly, allowing developers to upload content as needed without manual key management. Ultimately, this approach ensures a smoother transition and optimizes translation efficiency.
