Data Studio Translations in Directus

Speaker 0: Carmen is so developer, educator, and direct translation station. Is translation station. Alright. Back to English. So here we've got a direct us project that I'm running for my blog.

And, yeah, just one blog post for now. We'll be filling it up with time. But I wanted to show you in the data studio the collections I've got. I've got some authors, I've got some languages, and I've got some posts. So, as you can see, my computer's default language is English.

Now, my Directus project is also running by default in English. But what if I wanna make it available in another language? What I can do is go over to the settings module and then the settings page itself, where amongst other settings, I'm gonna find the default language. I'm gonna open this up and show you just how many languages we have available here and not just languages, but languages specific to a region. So I'm going to scroll down being Chilean myself.

I'm going to set my language to Latin American Spanish. Gina's there too, but I wanna encompass all of this continent. Click on that and I'm going to save my changes. You can see now that a bunch of things have changed already. I'm in the setting in the modules instead of settings and so on and so forth.

What's really key to know here is the Directus project language has now changed. But what happens to the rest of our things? For example, in our data model or modelo de datos, we're gonna see that the names of our collections haven't changed. Or if we go to content or as it is now, we're gonna see that my blog post stays the same. Even the fields on the blog post themselves.

But that's to be expected because our project is now in Spanish, but the content itself and the data model are still in English because that's how it was when I created it. But what I want to focus on here is the language of the Directus project itself. Let's go back to our settings module real quick. You might be wondering where do the translations for these come from and how can I change or contribute to them? Now given that Directus is open source under the BSL license, we actually get these translations as open source contributions.

That's right. You can contribute your own translations to Directus. Next, I'm gonna show you how to do that. Over in the Directus documentation, under resources, community, and contribution translations, we're gonna find the instructions for how to contribute localizations to the Directus Data Studio. And this is done by a platform called Crowdin.

So over in Crowdin, we can see there's a bunch of translations that exist, which I love to see. Got Catalan, Dutch, Finnish, Estonian, and a whole bunch of other languages. So how can I contribute to a language, say, if I find a typo? First thing I need to do is log into Crowdin, which is via free account. Now that I'm logged in, I can go ahead and look for my language and start contributing to it.

For example, let's look for Spanish and specifically focus on that Spanish Latin America. Now on this page, I'm gonna click on translate all. This will give me a list of all of the strings or pieces of text that can be translated in Directus. Now here, under editing preset, I can see the string editor predefinido, but because this is in the current test we're currently editing, it should actually be editando predefinido. So what I'm gonna do is make that suggestion and save it.

But because there's already an approved translation, what I'm gonna do is notify a proofreader. Cool. So now my suggestion is made to improve this Latin American Spanish translation of Directus, but what happens next? So our team over at Directus is going to get a pull request from Croudon with the change that I've made. Now you might be thinking, well, why don't I just make the pull request if it's open source?

Bear in mind that crowding's automatic synchronization is going to overwrite any changes that don't correspond with crowding itself. So it's best to make those translations directly through crowding. Now, the last question is, when am I gonna get that new string? It'll be merged into Directus itself and will be available in the next release. So now we just gotta sit tight.

Alright. Well, there you have it. How to configure your Directus project in another language, which strings are translated directly, and how to contribute your own translations to the greater Directus ecosystem. I hope this was helpful. But there's more stops on this Translation Station journey we're going on.

We'll also be learning about translation strings, translating content in the data studio, and accessing translated content in your own application. So all aboard for the next station, and off we go. See you next time.