 All right, so welcome. This is the 19th of April. Alex and I are going to configure CrowdIn Enterprise for use by the Jenkins project. So let's share my screen. Okay, so I think what we want is jankins.crowdin.com. This I believe Alex is CrowdIn Enterprise. Am I correct? Yes, you're absolutely correct. This is the CrowdIn Enterprise instance for Jenkins. Okay, and so now we had previously platform labeler and some other simple things. What should I do first? What are my preferences? A good start would be to invite me. Okay, and how do I do that? Yeah, you are already on the console tab. Yeah, if you can use our management. Okay, and so now. All right, I didn't sign up on this instance. So let me open it myself really quick. Jenkins.crowdin.com. So each contributor would register themselves with CrowdIn.com, and then we would invite them to this workspace or to this. Oh, very good. Okay. Yeah, I just signed up really quick. And I think I should enable admin access for you short term so that you can make changes if necessary. Okay. Admin access is only for the instance itself. It doesn't give access to the actual projects. Ah, okay. All right, great. Yeah, if you want to give someone administrative access to all projects, you click on the manager's tab right above workflow templates on the left. Okay. And would need to add me there. Oh yeah, I'm already there because I'm an admin. Okay. Okay, so, but this is the concept of managers is distinct in that sense from the concept of user management. I can add a user who is not a manager. Yeah, for example, all right, if permission, if permission granularity is enabled, because you can you can configure CrowdIn in a way that not every administrator has necessarily full access to every project. Okay. And I don't know, is there is there any compelling reason why you would think we would ever need that level of granularity? Uh, I don't think so. Okay. It's just a level to fine tune permissions in case you would want to set that up. But the current set up would the current setup would equal the GitHub setup where special people have admin access on the JLCI organization who can manage repositories as well. Okay, got it. All right. Now, what are my next steps? Yeah, let me open it myself real quick. I just need to verify my email. Otherwise, I can't open the administrative view. All right. Yeah, we currently don't have any projects or setups on here because everything is on my instance. So we could start moving over the design library, for example, but basically, CrowdIn configuration is pretty much straightforward. Like, you don't need to do hundreds of steps preliminary to make sure people can access it, because like you see, I just signed up and have already access to things. Don't need to configure my account or something else or give it specific permission. So, yeah. So conceptually, I could move the platform labeler from where we had it before into this? Yeah. I mean, you can't set an export on the one instance and import on the other instance. That is not possible, but I could suspend it on my instance and reset a new project on this instance, for example. Ah, okay. So, but it's a suspend and reconfigure. It's not just a move kind of concept. Okay, so it's probably better for this if we create a new project here to do that rather than going through that suspend and restart. So do we want another plugin that we then add here as part of our setup? Oh, yeah, we could add the design library, for example. It has quite a few installation strings as well. Okay. Yeah. We could head to the workspace now. Okay. Yeah, and already tells you that we have no projects or groups yet, and we could create a new project. And the concept of a group in this, so this would be design library plugin and pre-fill. Yeah, that's the typical languages. Yeah, the group concept would be like group access, like similar on GitHub. So you have a few people you can put into one group and give this group access to a project rather than managing everyone individually. Okay. But considering there's only me at the moment, and you can just add myself straight away. Okay. So and I've selected several languages here. I just say create project at this point. Or is there more that I need to do? I need to delay workflow start. I remember. That would be fine. And to click on the crowd sourcing workflow step, not in-house translations. Okay. Because people actually can interact with it. Right. Very good. Okay. So choose crowd sourcing, delay workflow start. Yeah. And I chose 16 languages. That's probably not terrible. Remember the selection. So this would then remember my setting for crowd sourcing and delay workflow start. Yeah. Okay. For sake of making it easier, we can also delete unnecessary workflows we don't need or don't want. So that only crowd sourcing or something custom is available. I see. So for instance, the fact that we don't, we aren't likely to use in-house translation or in-house machine. We could remove those from the list of templates that are presented here. Yeah. Workflows are just another template. You can create your own workflows, for example, but crowd sourcing is basically either one we have used for the other projects on the other instance. Okay. So we're ready for me to press create project. Yeah. For sure. Okay. All right. Please upgrade your subscription plan to create more projects. Let me take a look real quick. Organization settings. We should be on the open source plan because that's just what it tells me. Oh. So am I on the wrong location? I need to be this. I thought we wanted crowd in enterprise, right? And I thought that was maybe I'm in the wrong place. Let me check. No, you are on the right place. Yeah. But I see, if you don't mind, I would share my screen real quick. Yes, please. I have, let's have it open. We need this monitor. Yeah, because this is the open source plan on the Jenkins instance. We are currently on the open source plan, but we are limited to 10 managers and 500,000 words. On my instance, I have unlimited managers and unlimited words. Oh, interesting. Okay. But we are actually both on the open source plan. Well, I have the open source plan Jenkins has open source. I don't know if there's any difference on it. Okay. I have because unlimited managers and unlimited words would be pretty much needed. Right. Right. We certainly, it's a big enough project that, okay, yes. So the other one that I had set up that's not in enterprise is a different location. So I think Jenkins. Well, yeah, I mean, this, this is already the right enterprise instance. And we have the typically layer out. Yeah. But it has weird restrictions that the, at my instance doesn't have, which is also an open source instance. Interesting. Okay. So maybe we need to ask for help from crowd in support. Okay. So I'm going to reply to them and see if, okay, now okay. So trying to configure our crowd in enterprise limited in 10 managers and 500 k words that we are limited to 10 managers and 500 k words on our instance, while his instance, our, and it was open source, right? Yeah, it was his instance. Yeah, you could name it because my instance is actually called open source plan and open source plan. And Jenkins one is just called open source has unlimited has unlimited managers, unlimited managers and unlimited words. Right. Yes. Because my basic projects plus the three demonstration projects are already more than one million words. So right. Which hints that Jenkins will probably far exceed 500,000 words. Yeah, by ease. Okay. All right. Is there something more we so do we need to just click the upgrade plan? I mean, if I click up, am I on the upgrade? Or is it going to ask us do you want to pay money to upgrade the plan? Jenkins, building upgrade plan. Yeah, upgrade your organization account. We do can't require that we we've then pay them monthly the monthly fee. Okay. Yeah, maybe some just some mistake or misclick on their end, because I'm not aware that there's an open that there are different types of open source plans. Because on the website, the open source plan is also advertised as unlimited managers and words. Right. Okay, it would be would be weird that I have a higher limit as a smaller project than Jenkins instance, for example. Right. Yeah. Well, so now okay, so I'm sending that question to them. Now I saw while we're while we're waiting for their response, it looked like there is some customization we could do like customizing our logo and and things like that. Yeah, for example, let me just close my instance real quick. Yeah, that's pretty, pretty simple organization at an icon in the description below. We have the scene and record if we ever want to point to something else. That's right on the system settings organization tab over view. Good. So so conceptually, we could have a crowd in dot crowd in dot Jenkins that I owe that points to this this location and then is is presented underneath the Jenkins that I owe custom domain name. Yeah. Nice. Okay. Basically, basically, go ahead and give it a typical Jenkins like icon banner. So people actually recognize this as our instance and accessing it. You want to do that or I was going to say let me do it because that way you can watch and you can tell me when I make a mistake. And we've still got the recording if you're okay with that. Yeah. Okay, so I'm going to stop your sharing and I'm going to share mine. Okay, so here it was. Let's see it was workspace. No, no, this is this is the overview of the instance of the organization. If you want to manage the organization, you click on your account icon, the M and the upper right corner and click on organization settings. There we go. Thank you. Very good. Okay, so now I want to upload a new logo, but in order to upload the logo, I need to go download the logo. So let's go to Jenkins artwork and we could choose. Let's see. I think, well, just a minute. I want to see which one I've used in the Dock SIG because maybe that's the one we know. We should just use the standard Jenkins logo. I agree. That's a nice, Jenkins needs you is a very nice thing, but let's just grab. Yeah, we should use the official icon here. Exactly. So now where there it is, this one. Okay. So if I save that image, okay, now wait a second. I want the SVG probably, don't I? Yeah, I think it works either, but it's a rather small icon. So right. Okay, so Jenkins.SVG, now if I try to upload the new logo. Oh, okay. And it wants a PNG. It doesn't. Okay. So I need a bigger picture. Okay, just a moment while I get a bigger picture. Okay, edit. Yes, I'm sure there's a better way to do this, but this will do for now. Yeah, possibly, but wasn't even aware that that's an extension access. Oh, I love this go full page. This thing is so nice. Yeah. Okay, good. So now let's try uploading a new logo with this one. All right. Now we need to. I need to zoom out a bit. Oh, and I bet there is a zoom out like that. Nope. Let's go a little further. See, this is where I need someone with your skills, Alex. All right. Got it. Can do the fine tuning at a later point. Right. So that gives us Jenkins. Yeah. All right. And then a cover image, I could use any one of several, let's see, we've got one on the Jenkins website, don't we? It's more of a banner than an image. So, but it could be something that is more wider than the current icons. Yeah. Well, and this one, I would typically do something with the Jenkins social media cover slide deck to create that. So 1500 by 500, I can do that later. Yeah. Okay. So we've done an organization setting now. Let's see if I got a response by any chance from crowd in. Don't see it yet. Not yet. Okay. So we continue. All right. So the organization setting is up to date. Are there other things we should configure while we wait for them to, I mean, is there a concept of a group that would matter in this case? I mean, you could create an example group of the design library, adding me and I'm possibly adding others in. Okay. So, and a group in this case would... No, you don't need to include group. Oh, just call it design library. Okay. Yeah, because... Now, how do I get rid of that? I already said it is a group. Right. That makes... Okay. So delete the group. Okay. So create a group, design library. Okay. Yeah. And if you just select the group, now you can click on the create button on the lower right corner. Oh, create. Here we go. Okay. And here it's... Now I would have to do a project inside the group. Right. And again, we expect that will fail because... All right. So we've got... If I do create project, it's going to say, yes, you're not allowed to create more projects. And that part, I really don't understand because it's like they've... There's something configured that's not allowing us to create projects at all. Yeah. I think there's just a misconfiguration on their end because even with the current plan, we could set up such a simple project, but for some reason, we are restricted or not allowed to. Okay. I don't recall that I had such an issue when I set up my instance. Okay. And so here it says, welcome aboard. And... Oh, well, maybe we can... Okay. Maybe we can start with a chat session with them. Okay. We're trying to configure our crowd and enterprise and can't create a project. It says we need to upgrade. There. So maybe this is the way to get the quickest answer. Yes. Oh, that's wonderful. Yeah. They are really quick responding to things. Yeah. I think this sounds fine. Well, and then it gives me hope that as quickly as they responded, we may still be able to make progress. That's great. Yeah. In the meantime, we could take care of the now obsolete templates, making sure every... Oh, very good idea. Okay. So new tab to the right. I don't want to risk losing that. So here we go. And now your suggestion was let's go remove... Oh, hey, that's great. Every tab. Excellent. Okay. There's the workflow templates option on the left. Workflow templates here. Okay. And we say... It's the one we want to use. And the other one, we can basically just delete because we likely never set up in-house translations. Right. Okay. And translation agency, we are unlikely to fund the translation agency. So... Okay. Good. Yeah. And if you click on the crowdsourcing one... Okay. Yeah. That's basically our current setup. That's breaking it down. We select the target language. People translated. Some approve, read it. And once approved, it's delivered. And so this is describing... This workflow diagram is describing the stages in the workflow. I'm not sure I understand the... This arc right here, the one that seems to go from pre-translation directly to proofreading. Yeah. That would be the case if we import a project which has already translated strings. I see. Okay. Where, for instance, a plugin may have already been translated by someone else, but it hasn't been through their approval process, the approval process in CrowdIn yet. Yeah. I see. Okay. Thank you. So by default, the default process would be that previously translated strings would be under another review before they had shipped or ignored again. Makes sense. Okay. So she's offering, try to recreate one again. So let's do... Did you send them a link to our instance or...? I did. I told her, I think I did anyway. No, I said it was for the Jenkins project, but she says, try it again. Now, how do I... I can't get there without... Let's just open new tab. Okay. New tab and Jenkins, whoops, Jenkins.crowdin.com. Okay. And here I can try closing it. Yeah. Okay. And now create project. And... Oh, no, wait a sec. I shouldn't do it there. I should do it here. Inside the design library, create... Inside the design library group, I create the design library project. And here I want... I'm going to limit it. I just want Chinese simplified, Chinese traditional, German and French. Oh, English as well. Yeah. The default languages are customizable as well. Okay. Oh, good. So if we have specific languages that we'd like to encourage, so let's say French and Deutsch. Okay. There we go. Like that. Yeah. That would be the Jenkins default sample we could ship as default translations. Right. Okay. And now I set delay workflow start and we're ready to press create project. Yes. Okay. Oh, and I should have done Brazilian Portuguese because we got it. And that didn't work out surprisingly well. Nice. Boom. Okay. And now what? Yeah. It's showing you a little tutorial because you are in your counter this instance that you can go through as new user or just dismiss because we likely already know how to set up this project, I hope. Okay. Yeah. Yeah. That is the design library. I have the design library. Let me design library. I think I have integrated with GitHub actions. Yeah. So we could reintegrate with GitHub actions here instead of reintegrating it with the GitHub tab. Okay. And how would we do that? So back to the integrations. So here it was. Whoops. Now did I know I made a mistake? Should I? Okay. So I'm in the design library group. View the project. Yeah. It's fine. You don't do the action integration and crawling at all. Oh, I see. I see. Okay. All right. All right. And now does the GitHub actions integration then use, does it submit the pull request as you, as me, as somebody else? It submits them as crowd and bought, but it does also configure rebel. Oh, good. Okay. So it submits them as a clearly distinguishable non-user. All right. Okay. Great. It's just using your personal access token from crowd and as authentication method. Okay. So what steps would I need to take then? You say that that's configured from GitHub. GitHub not from here? If you had on the, if you had to the design library tab on GitHub, we just need to sort out my personal access token from my instance with mine from the Jenkins instance. Just need to set one up real quick. Okay. So, so here we are at the design library plugin. Yeah. And if you click on settings and secrets, secrets right here. Okay. Yeah. Actions. Okay. It's called a bit below. Yeah. We have my crowd and personal token. This is the one I'm using for my instance. I see. It has access to the design library on my instance, which you can basically get rid of now because I would need to add a new token for the new instance. Okay. So you want me to click remove? That seems. Yeah. I'm just creating a new token in the meantime. Ah, okay. So you're okay if I click remove. So I'll click remove here. It's going to say, are you really sure you're okay that I remove that secret? Absolutely. Sure. Okay. All right. Very good. That's very bold. Okay. So it's been deleted. So Maven token and Maven username, and those are used for the continuous delivery, if I remember right. Yeah. Okay. Please don't delete them. No, no, no, no, no, no. All right. I've created a token and restricted it to the design library project. Just need to add a new one. Secrets actions. New repository secret. How did I name it in the workflow? It was crowd in, a crowd and personal token. Add secret. Yeah. And here we have a new token. Okay. Now we can close everything away. And if you re-open the workflow tab. Okay. So back here to the workflow tab or here to the crowd and not a crowd and not on GitHub. Oh, wait a sec. So open the workflow tab on crowd in. So right here workflow templates. No, no, no, the workspace tab, not workflow. Ah, got it. Okay. All right. So here I am in the workspace. If you, if we head to the design library. Okay. And open the project five languages, five minutes ago. This is what you added. I just pushed workflow trigger on GitHub to re-synchronize it. And it failed for some reason. Oh yeah, makes sense. If you're using crowd and enterprise, you actually need to tell the GitHub integration where the crowd enterprise instance is. Oh, right. Because it's Jenkins dot crowd in dot com. Right. Okay. Yeah. I just need to exchange that real quick from intellectual sites to crowd in because now we have my personal access token from Jenkins trying to access mine sense on intellectual sites and that obviously won't work. Right. Okay. Fix master crowd and Pat. And so this newly added crowd in personal token, that's the one that you just created for use with Jenkins dot crowd in dot com. Yeah. Jenkins dot crowd in dot com. Let me grab the project idea real quick. That is the number two. Let's update my hat. All right. Just gonna match this PR real quick. Yeah. Jenkins dot crowd in dot com. The project ID is the project with ID number two. That is fine. So the things that you're answering configuration on these are configurations on the GitHub side. Is that right? Yeah. Okay. So what you're doing over here on the GitHub side is you're configuring, configuring the actions here so that it will, oh yes, here's the crowd in action. If you head to the code tab, we can go over real quickly what I did in my conversation with myself. Oh, okay. The code tab here. Yeah. This is just my PR. I matched real quick and visited. So it is, oh, look at the PR. Okay. So let's look at the PR. Okay. This is the one I just created and put in real quick. If you click on the file, it's changed. Okay. Yeah, the commit. Yeah. This is basically what I did. I exchanged the intellectual sites instance with the official current instance and changed the project ID. Okay. And it will fill in the secrets dot GitHub token and secrets that crowd in personal token. So there's no credential actually stored in this file. Great. It's not different from authenticating with any other GitHub workflow. Like you don't have credentials in the CD workflow as well. It's everything done through the secrets tab. Just need to make sure that the name in the workflow file actually matches the name of the secret. Otherwise, it can't find it. Yes. So this is important. Crowd in personal token. Okay. The crowd and project ID is the ID of the project you have in the URL. So that was this number right here. The two on the very end. Okay. Yeah. And the project URL is like the URL. You can access this project. And that's that's the base URL top level. It's and so if we if we eventually get crowd in dot Jenkins dot IO, this could then be changed to that. Or does it will it need to stay the the non CNAME based? This is not something I tried out yet, but the GitHub action basically does use the GitHub command line interface. So assume it can follow CNAME records. Okay. All right. But yeah, as you can see in the workflow, we have pull request title, create pull request, pull request labels, we can basically set up how we want the action and action create PR want to look on GitHub. Oh, okay. So, so this file has it's a rather simple file. Here's the PR title. Here's the commit message. Okay. Got it. Yeah, there are lots of more options to customize it, but I am fine with the current layout. And the PRs it creates are under the I think crowd and enterprise or crowd and bot. So it makes it pretty easy to see that this is not created by a user human being. Right. Okay. And so we would see then in the closed pull requests on this, we might see some changes already. Yes. So here, new crowd in translations were committed 18, 18 days ago. Yeah, it would be something like this, the same kind of thing. Yeah, this is the GitHub action spot and the actual bot feature in your current translations. That's what we wanted to use for that. Okay. So go ahead. I think the workflow and no, this is CD. Yeah, crowd and action just built and synchronized with crowd in. If we had back to back to crowd in. Okay. So here we are. Yeah, the current action is still running, but if it is done, we should have the pre translated German files and other things available. I hope. Okay. So all right. Yeah, I'm going to finish the chat with them because I think that's done. And a big smile. I could take a look again. What our plan does say now Jenkins, crowd in.com organization settings. Okay. So organization settings was right over here. Yeah. And if you click on billing, it tells you the plan. Okay. Still are still limited 10 managers and 500,000 words, but we were able to create a project. So, so we've at least got a beginning working place. We'll still likely need to ask for their, their help to resolve at least this 500,000 word limit. Yeah. And ask them in a chat right away. Yes. Okay. So all right. So let's do that again. And where was my chat? It was support. Oh, yes. Good. Okay. Okay. Back. Start a conversation chat. Concerned that limits of current plan won't be enough for the Jenkins projects. We need more words. Okay. Yeah. I could also like ask if there's actually any different kind of open source and open source plan. Yeah. Because the 500,000 words are definitely far, far too less. I think of my projects over all I have over one million words. So, right. Well, and I could easily imagine, I don't know how they count words, but I could easily imagine exceeding 500,000 words in, in not very much time with Jenkins that there's, there are a lot of words. Yeah. Like every word is a word. I don't think I have any special counting for it. Oh, oh. So, so for instance, they may not be filtering source code out or no, no, no, but oh, okay. Yeah. It's just what to translate like the translation string as 10 words and get a plus 10 on the overall world count. Oh, okay. So she says open source licenses have some limits checking what she can do. So you may have been lucky that your limits are different than the current limits they set. We'll take it. I hope for the best. Good. Yeah. Like my instance has no limits at all. I can have unlimited words and unlimited managers. Right. I mean, of course, I think my instance has limits who just not visibly shown to me. Right. Yeah. Unlimited is mythology, right? Welcome to the world of cloud platforms where we can be presented myths. Yes. Yeah. Have some unlimited disk space right here. Exactly. Unlimited disk space until I have to pay the bill. Okay. So the design library, and again, this project, now it's, what's happening is it will read the, read the sources from the GitHub repository from here or rather from here and then present things that need additional, that need translation ready for someone from the crowd to the invited team, the invited people here to provide a translation. Yeah. Just enable the notification for translators about new strings, but at the moment, it doesn't import the project at all because the German translation does. So it's still empty, but I completed that a couple of weeks ago. So, but now I do see, I do see strings here. So it's as though it did successfully import the English. So I see on my screen, I see the click me, click me that I know is one of the strings. Yeah. The string step is the, is a mirror of the source strings. Okay. So broken them up, broken them down out of all files and then overview it. That is not actually what you're translating. Okay. And that's also not available to translators. That is just for project managers. Okay. Now, you have to click through every file. If Alex, if you had any experience using CrowdIn on a website managed as code like Jenkins.io is when I see screenshots here, I think, oh, wow, maybe should we consider, we have a Chinese translated Jenkins.io site currently. Could, could CrowdIn conceptually be used also to translate a site like Jenkins.io? Possibly, but I'm not sure what you mean with screenshots like well, so, so there are, I've got a project running right now with Sheikot Africa that's helping us find and correct images inside the Jenkins documentation that are showing things that are no longer accurate. So pictures that it no longer, the product no longer looks like that because Jenkins 2.344 has a much, much more attractive user interface now. So here's, here's one example file here, I think has a bad screenshot in it. Come on, come on. Nope, nope. I've, we've been working through them and we found, we found several examples. So maybe it's, let's, let's use this one. I think this would give us one where we just say it's not a terribly bad screenshot, but it's not, it's no longer, yeah, this one right here for instance, that is not quite correct. It may, there may be some change needed. And my thought was, ah, well, their tool has some ways of identifying screenshots that might help us if we wanted to, so long-term thing for consideration. It could, it could ASCII doc be fed to this, this system just as we're doing Java properties and HTML files. ASCII doc is dot a doc, no. Correct, right, dot a dot files. I think I have it right here on the web interface, language codes, yeah, dot a doc, call it call it enterprise. And it's okay if, if the answer is, I don't know, that's perfectly fine. It just, while, while we're here together realized, oh, maybe there are more places we could use this. Yeah, I know out of my mind that, that it supports a lot of different source languages, but either I don't find the list at the moment or a doc doesn't appear right here. Yeah, but that does also support lots of languages and different projects that are not necessarily Java or Java related. So it does work with them, but I don't have it at hand at the moment. No problem. Thank you. And now in terms of inviting additional people, can I invite by, oh, they have to have already registered with crowd in? Or can I, can I send, could I send an email invitation to this email address even though please provide me? Yeah, like I think so. Okay, but it, I suspect it wants to, I need to have already registered because here it says, yes, I could select you, but I can't select any, I can't send an arbitrary email. Okay. Yeah, I don't think that is possible, but there are lots of things like a magic link, for example, to look into the instance with us, could just put that in the email. Right. So if I copy this link and then said, hey, in fact, I'm going to do that actually, I'm going to send an invitation to a French speaker who's been willing to help. So if I send and compose to Damian. Okay. Okay. So I just said, I think it will be a while. Yeah, currently the instance is configured that people can sign up with GitHub with email or via magic link and lots of other sign up options. Okay. But oh, go ahead. Excuse me, Alex. Oh, go ahead. I'm just reading the methods. Five million, please leave us a review on G2. Absolutely. Okay. I'll do that review on G2 later so that good. Okay. All right. So word limit has been increased to five million and activated some more features. Okay. Good. Yeah, we are on five million words and 20 minutes. Oh, very nice. Okay. Excellent. I mean, the manager count is likely not an actual concern, so that would be more the word limit. Okay. Well, and if five million is not enough, we can always ask them later. So I'm going to go ahead and end this chat. You're okay with that? Yeah. Okay. I think for a basic instance that was fine. All right. So we've got, we've got the design library group created here and a design library project. And now you had indicated that this has not yet shown anything needing to be translated. Yeah, for some reason, I have re-triggered the workflow twice to make sure like since the data to crawl, but for some reason current doesn't pick it up or doesn't show it. I actually didn't open a translation file yet. Well, that's the workflow file I wanted to run. Yeah, but it does still display them as untranslated even if all gem messages are translated. So quite not sure why it doesn't work yet. Couldn't find any file to download. Okay. Yeah, the action basically does use the GitHub clouding command line interface to run the action, which did work fine in the past, but I didn't try to re-trigger it from the old instance to the new instance yet. So would it be useful at this point to have you guide me through doing this same sequence of configuration for the platform labeler to see if we get a different result there? Actually, I guess we've almost run out of time. So Alex, maybe it's maybe it's better. We just call call that we'll we'll can plan for this for another time. Are you available during Thursday's docs office hours to try again this week? Yes. My calendar says that is fine. All right. So shall we? Thanks very much. We're we're feels like we're making progress. We've got a group. We've got oops. Now why does this not show my project? Ah, okay. Now we've got a project. And so for instance, if I want to if I want to adjust the configuration of this target languages, it's that easy. I just click there and add a new target language like I want Italian. And it was that easy. Okay. Now now eventually, when when it starts detecting, we'll probably see that, hey, there's no Italian translation at all for design library. Yeah, no, I mean, it would display that there is a translation available, but it would display the green progress bar because it's completed. Oh, okay. So it has been translated already into Italian. Okay. No, the platform label I plug in did. Oh, right. No, I was talking to design library. Sorry, platform label. Yes, we completed it. Okay. Yeah, no, only German is available at the moment. Ah, good. Okay. I don't think why doesn't work. I don't know why it doesn't work at the one, but I will take a look at a later time. Right. Thank you very much for your time. Are you okay if I share this recording in case it helps? I can make it also unlisted or choose not to share it. What's your preference? I'm fine with sharing, though I don't know how much useful it will actually be because setting up the instance is likely less, likely less informative for Excel translators. Yeah, the recording is mostly for my benefit, truthfully. And I'm actually okay with that because it helps me go back and refer to it later, realize, oh, hey, that's okay. I did that wrong. I need to do this right, et cetera. All right. Alex, thank you very much. You are so kind in going through this. Thank you. Thank you. I'm looking forward to this. I will, I will talk to you then on Thursday. All the best. See you on Thursday.