GitLab Digital Experience, 9 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab marketing site translation contributions

Description

How to contribute and edit translated content on the GitLab marketing website.

Working from this epic: https://gitlab.com/groups/gitlab-com/marketing/digital-experience/-/epics/250

Part 2: adding commits to a MR here - https://youtu.be/84z7P_s8R2s

A

Hello Lauren Barker here it is May 29, 2003 and I'm gonna, walk through a process to review and contribute edits to our translated content on the buyer. Experience repository and I will go ahead and share my screen, so we can get started here, we're going to start off on our nice epic here, where we've created issues for all the pieces of content that need to be reviewed by human translators, because it's all been machine translated and for the demonstration of this video we're going to work with the Japanese Enterprise page.

A

So if I go in here, looking at this issue, let's say: I'm the internal translator, I assign this you to myself and I know that Daniel has some labels set up, so let's do l10n assigned so this way we can see that it's assigned and for our iteration, let's go to buyer experience and we'll pick the iteration at which we're working on this issue, which is May 8th through the 21st.

A

um You know we'll give it a way to point one, and so now this issue is ready to be worked on. There are um four steps to each of these issues.

A

um It's a good idea to read over them because some may be different than others, but for this one, we'll we'll State what the goal is, which is to review the machine translation of our Japanese Enterprise page, we'll link to this page, which is live uh and then the four steps which is to review the live version and then open the content file that generates that live version make edits um as you see fit as the translator and then to verify your edits are live on production as intended, and if there are things that cannot be done through that content file, let's say: there's an image with English text in it to make a thread down here such as, uh and we can actually go ahead and do that um so I'm going to go ahead and open this Japanese Enterprise page come down here and oh cool, they Translate text bubbles.

A

Well, that's cool that just happened, but an example uh would have been last week. Hey, you know, take a screenshot of that sucker come down here, drag the the thing in here and say you know these speech. Bubbles are not translated and that will create um a thread that we can then address later. In this case it is translated. So that's just for demonstration purposes. So we've done the first step. We've reviewed the live page.

A

So now we're gonna go and make edits to the content file and uh we have linked direct link to all of the the files to be edited in each issue so and come in here and just let's say, open link, a new tab and what this is going to do.

A

It's going to take you to the yaml file, where this content is stored and it's a nice yaml file uh and let's say for the demonstration purchases here we want to change in the sub hero, this title to be something other than devsecops, so we're gonna smash that open in web IDE, Blue Button super cool button, and this will bring up that file in a web IDE, and we can see here in our Solutions hero, subtitle, devsec, Ops and I'm, going to say um demo text update and all caps now.

A

That would be not that, but you get the idea you go through. This whole file. Make all the edits that you want and we're going to click on this little button over here submit message, I'm going to say demo text update there we go and commit and push we want to commit to a new Branch. Yes, we do it'll, give you a branch name, that's good enough and then the big part, this little window is going to come up here.

A

There's going to be an orange button, it says, create Mr click on that button, and it's going to take you to this beautiful new merge request screen, and this is where all the magic happens and in this merge request uh screen we're gonna have a new template coming soon to you for language edits, but for the purpose of this video we'll just do the digital experience template because I know it's less and up here we're going to say what changed and why uh I mean not that.

A

But you get the idea and then come back here. The issue copy that issue URL go to the new merge request, say, closes just link that that issue right there assign that Mr to yourself super important. So that way, it doesn't get lost in the gitlab Eco sphere and labels.

A

Here, let's do L10 and we'll say in progress, because localization has been in progress and then we'll smash that blue merge request button, and this is going to create the branch it's going to start a pipeline which will enable us to view our changes in a review app and the coolest of all.

A

um We can go to our changes Tab and it will show you exactly what changed um in this Mr and we can see here is my edit that I made, um which is super cool, and we can see my commit. So let's say you want to do one pass through where you change. One phrase to something else say that in your commit, you want to do another pass where you change a different phrase to something else.

A

You do that in a commit, and you can just start to build on your review um through commits, so that creates this Mr and it's going and it's assigned how do I go back to this Mr. Well, we come back to see the issue here we can see. We have quite a few demo Mrs that are now linked to this issue, which makes it really easy to go and find all the Mrs. That's why we want to link them.

A

How do you find this issue? So you come up here to this top little toolbar the farthest one on the left. These will be all the issues that are assigned to you: Japanese Enterprise, human page, human translation. There's that issue this middle one right here, I go to a sign.

A

I can see all the Mrs that are assigned to myself super quick way to get to them, and so here's this one that we just did demo text, update, pipeline's still running I'm gonna go ahead and go to a previous Mr I mean Daniel did earlier, where the pipeline has run so I can show you that review app. It's the coolest uh pipelines run if I go to the changes you can see. Okay, here are the changes that have been made.

A

This content file directory is also with the URL will be so jajp Dash Enterprise slash cut off the yaml part, so you just copy that name right. There click on this, this button, The View app button, it's the coolest, and this takes you to a whole staging of the entire marketing site. But with your changes from that merge request- and let's say, I want to find what are where our changes are. I can just paste that path in there and know that yaml isn't going to go just replace with the Slash and.

A

Why did it work?

A

That's that JP there we go and jhap Enterprise ah I, don't know what happened there, but just manually type in it works, and now we can see here are my edits that I made and you can go and review them as they would be um if this Mr goes live, and so this is like a great QA check, not only for you as the the reviewer of the translation, but then also um these data structures.

A

You know if something's off period gets off somewhere like it's good, to have an engineer come in and review those as well uh what else? So this is good, um we'll come back here. So the the final step. Let's say this Mrs is good to go. It gets approved um by the reviewer, which uh will either be Daniel or your team, and then someone on digital experience it gets approved and then you know make sure it doesn't have the draft on it. Mark is ready, merge, I'm, not gonna, merge it. That would not be good.

A

I'm gonna actually go ahead and put the draft back on so that we know not to merge it, but that if you do have smash that merge button, then this pipeline runs gets merged into Maine and action. So the final step before you click this off. Well, actually that does that the third step verify your edits alive on production would mean waiting for that pipeline to pass going back to the live page and say: oh there's my edits, they're there and they're as intended.

A

So then you can click that one and then create issues for the threads that could not be edited in there such as this, and then you can just close that issue or um if there are threads that are unresolved, we'll create new issues um to work from that, but that, um for this first pass at building the localized marketing site um will be the efficient way for us to get to the first iteration and then from there.

A

uh We're gonna build more automated processes, um but, as you can see, we have quite a few issues for the team to work through and I'm, looking forward to seeing the translators, assign and starting to work through those and see those Mrs come through. All right see you later.