 Hi everyone, welcome to our webinar between the Drupal Association and SmartLing. We're giving it a couple minutes as more attendees join in, so bear with us. There's a few features you can use if you'd like to talk to each other. The chat feature at the bottom of the Zoom window will allow you to chat with other attendees. There's also a Q&A feature if you want to ask any questions. This is going to be a little bit of an interactive presentation. So there will also be some polls popping up. So feel free to take a look at those as well. But as I said, we're going to give it a couple more minutes just to let more people jump in and join, and then we will go from there. Thanks for your patience. Yes, so if you'd like to ask questions about the event, you can do so either directly in the chat or you can use the Q&A button. Hi, Escar, welcome to the event. Good to have you with us. Feel free to introduce yourselves and talk a little bit about where you're coming from. If you're not one of our panelists, your microphone is muted by default, so please do use that chat if you're trying to reach us. And we'll get started again in just another minute or two here. Awesome. Great to have everybody with us. I'm really excited about this content. I think it's a topic that is near and dear to a lot of Drupal site owners. In fact, I was telling Andrew and Adrian earlier that Drupal.org is considering going multilingual sometime soon here. So I am actually not just a presenter. I'm also an attendee. OK, so any minute now, I think we're just going to go ahead and jump in. I'm sure folks will continue to join as we go. But let me kick it off with some introduction. So good morning, everyone. Welcome to the Drupal Association and Smartling webinar on five steps for translating your Drupal website with only one developer. I will be hosting today. My name is Tim Lennon. I'm the executive director of the Drupal Association. And I will shortly be returning to my original role as the director of engineering as we bring a new executive director on board. I'm joined by Adrian and Andrew who will introduce in a moment some quick housekeeping. All attendee microphones are muted by default. If you'd like to chat with us or ask questions, please use the chat function in Zoom. It's a button at the bottom of the window. You can also use the Q&A feature to ask specific questions, which we can then either answer live or answer for you in text. And then we're going to be doing a little bit of an interactive component to this webinar. So we'll go through some poll questions just to get a little bit of idea of where you are all at in your current journeys, looking at translation and your needs for Drupal. So in terms of what we're really talking about today, we want to touch on, I think, a very real situation for a lot of teams and a lot of site managers, which is that, you know, if you need to do a multilingual project, if you need to do translation on your site, your product team probably wants your developers working on features instead. So in this webinar, Smartling is going to talk about the ways that we can kind of minimize the development time that's needed to do robust multilingual translation. We have the VP of product, Andrew Sacks, and the director of brand strategy and communications, Adrian Cohn, who will talk about Smartling and Drupal in terms of a translation management system to reduce those number of people involved. So these this conversation should benefit users who are both on Drupal 8 or Drupal 7 and how to scale your translation in your global reach without having to improve headcount. So without further ado, I will hand it over to Adrian and Andrew. Amazing. Tim, thank you so much. And thanks to everybody who's joined. I'm seeing a lot of new names, Peter. Thank you so much for being here, Ryan, Scott, Marie. You guys are rock stars for for joining us today. Actually, Andrew and I are doing this entire webinar live from the St. James Hotel in London. We're super, super excited to be here. And I think we've got a really solid webinar for you guys today. I think our goal is that you walk away with a lot of ideas and thoughts about how you can manage your global content pipeline through Drupal and just some thoughts and strategies around how to do that at scale. So it should be great. And Andrew is our VP of product. So I'm really excited to have you here today. Yeah, and we'll show both the Drupal side as well as where all the translation actually takes place. And there's probably a there's a little bit of a challenges to understand how those pieces fit together. But we'll show how that works. Yeah, it's going to be really cool. And as Tim said, this is meant to be super, super interactive. So use that chat function. We're going to be watching it the entire time. And feel free to ask questions. We'll definitely have time at the end for Q&A. And you can also reach me on Twitter. My handle is Adrian K. Cone, as you can see over there on the slide. And you can also tweet it smartly. We'll be taking a look at that and answering your questions as we go. We are here in London because tomorrow we have our second annual Global Ready conference, which is right here in the St. James Hotel. We're super excited if there's anyone on today's webinar that happens to be in London. And you would like to come to the event. Well, first, definitely answer this poll question. If you're near London right now, let's see how people respond to this. But if you're here, we'd love to have you at the conference. So let's see how we do on this first poll. Awesome. It looks like most folks are in other places, but that's no big surprise. If we do happen to find anybody nearby, I think that would be great because that conference will be an awesome opportunity to expand further on the kinds of topics we'll be talking about today. Awesome. Yes, well, one of the things that we're also excited about, we definitely want to make this super interactive. And one of the ways that we're doing this is by offering an opportunity to win $100 lift credit, which I think is pretty sweet. It's really easy. We're doing a Drupal Webinar, yeah. Yeah, just for attending. The one you'd have to do, it's really, really easy, is post a photo of how you're watching the webinar. Use the hashtag, move the world with words, which you can see on my t-shirt, move the world with words. And you're going to be automatically entered to win $100 lift credit. We're going to announce who won the lift credit at the end of this webinar. So stay tuned. But this should be really, really simple. The other day, when we were actually doing a test run of this, I posted a photo from how we were doing the test run. And this is how it came out. If your photo looks like this, you use the hashtag, move the world with words on Twitter, or on Instagram, or on LinkedIn. We're going to find it. We really appreciate your sharing the content. And we're going to give away $100 lift credit. We did this last week at our Global Ready conference. Kelsey happened to post a photo of her dog, whose name is also the name of one of our translators in Germany. And she won a lift credit. And she was super excited. You can do that too. And just to be participatory, I'm going to take a photo really quick of how we are delivering this webinar. If you go to my Twitter handle right now, you will actually see how it looks from our end. And I think that this is really cool. Everyone on this call as a technologist is cool. Like five years ago, we couldn't be doing what we're doing. And I'm really excited that you guys are here. But enough of that, let's get into the topic of today's conversation. We want to start with a poll, just so that we have an idea of where you guys are at in your journey. First and foremost, what version of Drupal are you currently using? Or are you not using Drupal yet at all? Right now, we've got D7, D8, and Evaluating Drupal. Yeah. It's looking like we've got so far 50% to 60% Drupal 8, about 30% of folks on Drupal 7, and 10% in the Evaluator mode. That's gone 60, 30 in favor of Drupal 8 right now. Wow, that's pretty good. That's great. Yeah, that's awesome. A lot of people are pretty early adopters. People have made the change, which is awesome. Yeah, that's really good. Seeing folks who are already on the next platform is great, especially in a year from now when Drupal 9 comes out, those folks on Drupal 8 were already be ready to go since that upgrade path is really significantly easier than it used to be. That's fantastic. That's awesome. And Tim, can you remind me, what was the percentage of people on the call that are evaluating Drupal? It's about 10%. 10%. OK, great. So we've got a fair number of folks on the call who are at different stages in their lifecycle. I'm confident that all of the content will be valuable for you, whether you're using D7, D8, or whether you're considering jumping over to Drupal for your content management system. So thanks for answering that. We did want to also point you in the direction of some great resources and just some broad strokes knowledge. First, Smarling supports Drupal 7 and Drupal 8. We have two methodologies for supporting this product. The first is we have a prebuilt integration, which we're continuously updating as Drupal releases new versions of D7 and D8. So it's a pretty simple. Yeah, I've got to say it looks like we have a misspelling. It's TMGMT. Oh, it's TMGMT. Smarling has been supporting Drupal for our customers for a while now, as far as prebuilt integration with connectors and all the various plugins and content types and modules and things that people might be using for Drupal. And most of our customers now are using our connector based off of TMGMT. We only have probably a few left who are using our legacy connector, which is a more custom built system before TMGMT was really the way to do localization in Drupal. Yeah, we have a lot of resources online for it, and we're always happy to answer questions about it. So that's great. So we have this prebuilt integration, Andrew. But what about customers that have really complex setups and maybe they want a lighter weight, easier way, of translating a Drupal website? Yeah, so Smarling has a few different ways and just kind of a little bit of background on Smarling. We are a platform for managing content for translation. And we need to get, of course, everyone's content into the platform in order to translate it. So if someone has content in Drupal, then we want to make sure that content is in Drupal. If they're using other CMS or the marketing platform or something like that, we want to make sure that we get all of that content into Smarling for translation. And then, of course, put it back wherever it came from. We do have some other more lightweight or some other methods of actually translating content. We have a proxy based system, which we call our global delivery network, which is kind of a layer that sits on top of websites and delivers localized websites in real time. And also, we can just accept different XML file types or JSON or whatever type of resource files people might have in the platform, which is also an option even in Drupal. But most of our Drupal customers are probably using the interface. Yeah, well, that's great to hear. And all of this information, by the way, it's on our website, Smarling.com. And if you go to help.smartling.com and you're really interested in getting the technical details, you can learn all about the integration and all of the functionality that we're going to talk about today in our support center. So just a couple of resources. We're going to circulate this deck after the webinar. So if you want to go back and take a look, you'll be able to. And on top of that, we will be recording this webinar. We are recording this webinar. And we'll be making it available to all attendees and posting on the Drupal Association YouTube channel. Awesome. Thanks for that, Tim. So the five steps. We want to go over these five steps. And while doing so, we're going to show you a demo of the Smarling product. We're going to also tell a customer success story with that one customer we've been in amazing with Drupal and with Drupal for Smarling. And we want to just do this in a really interactive way again. So the first is, you really need to know why you're doing this. And that may sound a little bit silly. Like why are we translating? Well, obviously, you want to reach people. But we think there's a really important business case behind this, and we want to just explore that for a minute. But then there are four other ways that we think you can really manage translation at scale for your Drupal content. The first is, you have to find a way to automate the upload and download of your content to a translation management system. Where number two, you could easily manage the entire translation pipeline, right? Yeah, and the automation piece is really important. Most people are probably developers, I would guess, on the call. And you don't want to be passing files in and out. You don't want to be emailing files to somebody who can see the translate. And you don't have to worry about re-downloading them and putting them back in the Drupal, whatever that process might look like. So the automation piece, no developer should ever have to worry about the file being moved around, or have to download a file, or chase something back, and trying to get it back into the source platform. Totally. So we're going to spend a fair amount of time on that automate piece. We're going to actually pull up a Drupal instance and show you exactly what it looks like to submit and retrieve content. So that will be a really, really helpful part of this webinar. But you do have to translate a little bit. So we want to talk a little bit about the ways that you can efficiently manage translation at scale. And lastly, you also need to be able to report on all of this. You need to learn from your successes and from areas where you think you might be able to improve your translation process. So these are the five steps that we recommend Drupal users to take when managing translation at scale. So really quick, we want to get an idea for where you are in the translation life cycle. I know that Bob, you've said that you're new to multilingual and translations, but let's throw a poll up there. And let's take a look at where everyone else stands in terms of, are you translating? Is your company currently translating or not? Hey, Tim, can you throw the poll up there? Yeah, I would like to. I'm afraid the polling here has just frozen up on me real quick. So could you please perhaps put your answers in the chat while I try and sort this out? Thanks, everybody. Sorry about that. Let's do that. Why not a Y for your currently translating and an N if you're not translating? Let's see. All right, Richard says, no, Marie, you're translating. That's awesome. Currently translating, Maria, awesome, awesome. Bob, yes, you're new to this, which is great. Legal documents, Patrick, thank you. Great, great. All right, so it looks like we've got a pretty healthy mix between folks who are new to translation and some folks who are looking to get started, a couple of folks using machine translation. Machine translation is a big deal right now. Maybe we'll talk a little bit about that. John, if you're interested in learning more, if you put a Y in the chat right now, we can talk a little bit more about machine translation a little bit. But all that sounds great. Cool, all right, we'll do that. So let's move on. It's really important that companies translate. It's super, super important. And I'd like to just walk you through this really quickly. The research says that people are not going to buy products or services if the content is not delivered in their native language. And on the other side of that spectrum, consumers are six times more likely to buy your product if the product that you're serving, the content experience that you're delivering is delivered in their native language. And 56.2% of consumers said that the ability to obtain information in their own language is more important than price. Which means it tells me, Andrew, they're willing to pony up for content and products so long as it is in their language. So this is really important. The other trends that we've seen, and this is quite obvious, is that there are way more people online than there ever have been before. And that trend is not going to reverse. Right here, you can see that year over year, we're getting way, way, way, way, way more numbers of users on the internet. So the point of showing this is that there are gonna be a lot more folks who are buyers on the internet. And what we're seeing as well, this is sourced from CMO, is that people are spending a lot of time engaging with digital content. So the folks on this call who are building and developing Drupal websites, you're doing it for a good reason. Consumers are on your website property, and they are in business with all of your content. And boy, we're spending money on it, right? 2018. Yeah, I think when we look at our customers who are successfully translating and doing it at scale, I mean, they probably fit most of these categories, especially the top ones. And they've identified already why it is important to them. And they know that it's important that their business is critical to their business to have a localized website. And they would probably all fit in these categories, especially travel and fashion and beauty. Totally, totally. And Dan, thank you for your comment. Love to chat with you about that later. You're right, I'd love to see some other data. I'm sure there is other data out there that may be a little bit more compelling. But I think it is worth noting, like, pretty obvious. I mean, if you can't consume content, like if you can't read it, it's gonna be hard to make a decision. But I think what would also be interesting, Andrew, now that we've seen the breakdown of consumer spending by industry in 2018, what business vertical are you guys in? I think that poll may still be down. Unfortunately, it looks like the poll function is still down. Please do use the chat again. Just type on in. You've got higher ed for sure. It looks like, given Dan's question earlier, there's at least a couple higher ed folks. Manufacturing, pharma. Cool. Hey, John, just really quick so we understand. When you say higher ed, are you working for, oh, I see a lot of folks here. Are you guys in higher ed, are you working for like an online, like a MOOC, or is it that you're working for a university that loves to understand where you guys are? Government, great university over here, great traditional university, great, great, great. Awesome, awesome. Yeah, I'd be very curious to learn more about the types of universities that you guys are representing. Global citizens, global students now. So you definitely have to be attracting students around the world. So that would be interesting. Yeah, university content is probably like all over the place. And probably the admissions process and that type of thing would probably be the critical component. Although they probably transit tons of other internal content and write papers and things like that. Yeah, it'd be interesting. Very cool. Well, thanks for dropping in the comments, guys. We really helped, it helps us to know who we're speaking with during these webinars. So, okay, we want to attack today by sharing these five steps. But in order to set those up, we wanted to share a couple of things that we feel are challenges in the industry to just set the stage. So the first, and Andrew alluded to this, is that right now a lot of companies are using a very, very manual process to translate their content. Typically, this takes place in the form of currently manually downloading files and emailing them to translators and then merging it back with the code base when the translations are done. It just takes your time away from building new and better experiences, right? There's so many things that come when you start thinking about how you're going to pack a different content, send it out and get it back. And things like, do you have placeholders and do you have HTML tags in your content? And are you going to try to do a dip between new content and old content? And if you're paying for translation, how you pack it up may influence what you actually conduct paying for the translation, which also kind of goes to number three as well. So there's so many things that go into this manual component. And if you are doing it manually, then you don't have that process set up to really take care of a lot of those kind of complex elements. Totally. And if you're experiencing these problems, drop a note in the chat. So we just get an idea of where you guys are at. But the second challenge is that since a lot of companies are managing this without a platform, they have no visibility in through the translation process. So no dashboard on our translation is complete. No sort of insights into how long it's going to take for the translators to finish their job, things like that. The third problem is it's really tough to manage translation quality and cost. And we're going to dive into that a little bit further. And lastly, you don't have analytics. You don't have data to figure out how to optimize your process. And instead, you kind of like lick your finger and put it up to the wind and see which way the wind's blowing. And it's just not a very data-driven approach to managing things. And we're definitely working in a data-driven world. So really quickly, if that poll is working, I don't know if it is. Yeah, sorry. We're still trying to fix it in the background here. It's a built-in Zoom feature. And unfortunately, it's just frozen up. And I don't want to reconnect because we might lose the whole call. So, yeah. So for these challenges, folks, again, if you can please use the chat and talk about whether you have issues with the four categories that we saw above on the previous slide. Maybe we can show those again for folks to type that in. Definitely. So if you're really the main driver that we typically see in webinars with developers is that number one manual process. But yes, John, translation quality from Google totally got it there. Yeah, of course, if you haven't started, well, it's good for you to know that these are the problems because, boy, will they become really problematic quickly if you're not aware of them early on. Continue to drop in your thoughts as we go, but we want to keep moving. And I want to start by sharing a story about a customer of ours who has absolutely massive reach. They have over 100 million monthly active users and they're one of the top access websites in the United States. And it's remarkable the type of reach that they have. They have a massive global audience. They're supporting something like 40 or 50 languages. It's an application that everyone on this call and most people globally are using at least once or you're using a competitor of this product at least once per day. And they're selling media on their website to drive revenue. So that's just to say it's really important for this customer to be translating their content so that they can drive ad revenue not just from where they are home-based but also in the countries that they're operating in overseas. So really, really big properties. And I just want to share a little bit about their tech stack. They're using Drupal 8. They're also using GitHub for their iOS and Android content. So they've got a lot of different content types that they need to manage. And over time, they've been translating a lot of content so, so much content. In fact, this year they're on pace to translate about five million boards. So they're really, really ramping up all of their translations. And as you can see it's just growing year over year. So these guys had a big problem when they came to us. The problem was that it took them over four days to get their content from the point where they submitted it for translation to having it shipped to their own users. And what's worse, Andrew, is that they needed something like eight or nine developers to manage this process. Yeah, that's crazy. It's crazy. It's crazy. First of all, that four plus days, it may not seem like a lot, especially if you're on the call and your turnaround times are like four or eight or seven days, but four plus days is, I mean, you can't really be competitive in this particular industry that this customer's in if you're shipping content four days later. Just doesn't work. Would you release your app and wait four days for all the language to be done or your website, like it's out of control. And it's, and that's sort of been the thesis of SmartLine for so long is that we were really built as a software company having most of the people coming from software in the beginning in that we knew that we needed to build websites and apps and things and get things out quickly. And you just can't wait four days for content to be translated. Yeah, we've experienced that as well inside the Drupal Association. We do these coordinated press releases about the upcoming features of Drupal 8.7 or the upcoming release of Drupal 9. And we have volunteer translators who help us get the word out, but a lot of the time there's some lag time there and it just doesn't feel like you're giving your international customers that experience of being a first class citizen. So cool. We should talk. But in all seriousness, these are the ways that this customer was successful and we're gonna walk through each of these so we don't need to spend so much time on this slide, but these are the results. These are the results. They went from shipping content in more than four days to having a turnaround time of between one and two days and they went from having eight or more developers work on every single deployment to zero. To zero. I mean, that sounds good to me. That is impressive. So Andrew, I think that what we should do really quickly, they use a Drupal integration between Smartling and Drupal 8 and they use our repository connector for all of their iOS and Android streams. But I think we should show everybody how this works because this is really what you came here for. You wanna see how customers are submitting content from Drupal into Smartling, the translation management system. All of this is a demo account that we're using so we're gonna walk you through all of the different automation features and naturally, since we've logged into a bunch of different tabs here, we're gonna click through tabs to make it a little more efficient. Yeah, and the point about even that customer who's using GitHub as well as Drupal, they're probably in your organization, there's not just one source and content that you do have iOS apps and Android apps and if I have content, I work on Word documents and Excel files and you also have a content coming from Drupal, so you need a place to really centralize and manage that. So I'm just gonna do a quick, high level overview of Smartling and then go to Drupal and then show what that content looks like when it comes into Smartling. So the intention of Smartling is to be that area where all of your content comes in from, whether it is Drupal or someone is dropping a Word document in or an InDesign file or whatever it might be, all the content is centralized in Smartling and then you can track it and monitor costs and see when content is gonna be completed and then automatically should go back to wherever it came from and there's various levels of management that you may or may not need and the most sophisticated people probably need a lot of tools to manage translation and manage different vendors or internal people to help do review and probably the newer people probably just need things to make sure that the content is in a translational workflow, it's getting translated and it can go back out. So I'm just gonna jump quickly around here. So generally in Smartling when content comes into the platform, it goes in what we call a job and this is really a temporary bucket that helps manage content and if you're familiar with translation in Drupal, Drupal also has the concept of a job. So there's a Drupal job and there's also a Smartling job and in this case, we can see that this is just some test content that came in and we do give some details around it. We also give a cost and then when it's authorized, it goes into what we call a workflow and that content and this is again, there's as much management information as you want to have but you also don't have to kind of deal with that if you don't want to deal with it. And when we talk about connecting Drupal to a TMS or to Smartling, it's really passing files in and out. So it's when you push the button and Drupal is passing an XML file and you move or then whenever we translate the content, we're pushing another XML file back in Drupal. So it's really just file management at this point. So if you also, if you just look at a couple of other things, it's up, talk for a second about workflow and there's a lot of different ways that you can kind of manage workflow and I think there were some people who were talking about some manual processes and Google Translate. A lot of times the workflow will help influence the speed and quality as well as the cost for translation. If you were just using Google Translate, then maybe there might be some quality concerns but maybe you would have some people doing some editing on Google Translate and that will improve the quality and as well as keeps the cost pretty low or maybe you just want to have human translation all the way through. So there's all these different ways that you can kind of mix and match translation methods for your type of content. So Smartling again, we have tons of reports to do kind of the analysis and things that will help you understand how much savings you're getting by using the platform, if there's any problems, like maybe there's a misspelled word on your Drupal site or maybe there's, you have a button somewhere and the translation doesn't fit in that area and the translator's gonna say, hey, this content is not gonna fit this button, what should I do? So a lot of different management tools here. So let me jump over to Drupal quickly. So in Drupal here, and then this probably looks pretty familiar again, this is just a staging demo site. Here I have, I've just created a page, just a simple note, it just has a few words for translation in it. If I jump over to the translation tab and there is the sources section, I can submit the content for one or more language and again, this is really, this is TMGMT and it's interfaces. So smartly we use the standard Drupal kind of objects and interfaces but then we also insert some of our own kind of custom tools and information, I'll get to that in a second. So here we can see that smartly is really configured as the provider here and smartly you'll create a new job. In fact, you'll select a bunch of content in Drupal, you'll say I want to translate this content, you'll name the job, new content to translate, you'll say when you want it to be authorized and then you get it submitted into smartly for translation. So let me jump over to see what that looks like. All right, so here I submitted this job, this was webpage for the site has 12 words, which was the, I think the title as well as this just little heading here and I don't have a cost yet on it and it's basically in a workflow and we can see that it came in with a single file and in this case, TMGMT is creating a file for every source to target language, every English to German, English to French, English to Spanish, whatever that kind of configuration is it's going to create a file, an XML file and just submit it to smartly for translation. So on the smartly side, we really think having, being able to have all this visibility into both the file information, whatever metadata, whatever metadata might need to be submitted for description, maybe there's some reference information that should be submitted, all that information is really important, but one of the most important features is having context and in this case, you can see again, this is kind of a demo site, but the context is really how the webpage will look to the translator or the mobile app or the Word document and for smartly, that's a really critical component and when we built our integration to Drupal, context is a really kind of a first class citizen as far as the type of functionality that we build and we build that into really all of our different tools and we can see that this is representative of what the translator would actually see when they are translating. So just to chime in, like this is so, so important. In fact, our data shows that this improves translation quality by 30%. So like why wouldn't you want visual context if you know that it can improve your quality by 30%? Like it's like, it's a no-brainer and for you guys who are developers, you've probably experienced the pains of translating content without context because what you probably experience is you're sending, you're retrieving translations from whomever is translating your content right now, you go to merge it with your code base and the strings are breaking buttons or the experience just totally doesn't look right. This tool eliminates that problem. It completely eliminates that problem. Yeah, and then you can also see things like 158 characters left. So this was a title field and we know the headline and we know that it has a limit on how much content can be there. So we're telling the translator, you can't go over this limit and then we'll give them an error message if they go over that limit. But one thing I just wanted to point out quickly in thinking about how you're doing the development is the things that can impact how your site is built and what it looks like. And thinking about Drupal is one thing but also thinking about just maybe even other content that might be influencing Drupal or that might be pulled into Drupal or maybe somewhere else on your site, things like placeholders. Is it hello, Adrian, hello, Tim, hello, Marie and that's a placeholder, making sure that we are maintaining those placeholders. There's a number of consistency. Tags is a huge one. If there's a bold tag and you don't and the translator skips the bold tag then you now have a broken HTML structure and you don't want that. So there's a lot of different ways that you control kind of quality from a basic level in addition to spell check and number of consistency and spacing and all those things that are also built in. Yeah, this is super important and it actually really fits in well with the next theme that we typically go over which is that manage theme. You really wanna make sure that you are proactively and programmatically ensuring translation quality and that's exactly what these quality check tools do. We have about 30 of them in the platform right now and what I think it's so deeply valuable about this is that you or your localization manager or whomever is responsible for the target languages, they can go in here and they can fine tune the different quality checks so that it will interfere with the translator's workflow or not based on the quality check that is really important to you. Yeah, and the good thing like this takes care of that, those all the issues that come up when you do get bad code or bad spacing or line breaks that are messing up the content, all these things are handled automatically so that the developer or even the localization manager doesn't have to deal with it and that's kind of both the automation component and the management component that really you should be managing by exception. If there is a major problem then someone needs to kind of go and find that to figure out the major problem but all of these smaller details should be taken care of automatically. Totally. I think this kind of automated quality control in combination with what you see is what you get kind of preview of the translated material is actually really, really cool does that system integrate with sort of workflows and permissions and things like that for users in terms of controlling who's got translation access and things of that nature? Yeah, so on the smirking side we have a pretty robust system for managing users including things, let me see if I can go into one. There's a lot of different ways that you can control what people have access to. One is workflow. So users only have access to the content that is available to them in their workflow depending on your role. And then there's different levels of permissions as far as giving someone ability to authorize content or maybe control the quality checks. So really you can have that fine-grained control as to who might have access to different parts of the platform. That's awesome, very cool. And guys, we know it's a, there might be a little bit of background noise. We're sorry about that, but we wanna keep this super conversational and fun and upbeat, I know it might be a little distracting but hang in there. We've got a couple more cool things to share. Yeah, so if you can kind of understand how this is working now. So now we have, the content has come into the platform from Drupal. So someone did the submission process directly from Drupal. They've packaged up a set of content. They've said it's okay to translate out in the smart link platform and it's starting to make its way through a workflow. And again, that might be Google translate for someone. It may be just human translation. There may be a human and then maybe you have an internal employee who's gonna review a certain language. So really anyone can kind of participate in the process. That really depends on the type of quality you want. Maybe the oversight if you require internal people to participate as well as the cost and maybe speed. If you have five different steps and five different people participating in a workflow then of course that's gonna take longer than maybe just one step. So now the content is making its way through the workflow. You have visibility as to where it is, where this job is, how it is making its way through the workflow. If there's any hang up, if there's any issues, I don't think this one has no issues. You can really manage all of that directly in the platform. And from within Drupal, you always have access to the exact progress. So this is, again, it's a little bit confusing because Drupal and Smarling both use the word job but you have access to the content as the progress is in Smarling. And as that content is completed in Smarling then it's automatically pulled back into Drupal. And you can always have direct access both to the file in the Smarling dashboard as well as be able to just download the content anytime you want in Drupal. So if this had translations and we had actually completed this translation then you can download that content and put it back in Drupal kind of at any time. But again, the idea is that you don't really have to manage and worry about this as the content is completed in Smarling is automatically pulled back into Drupal. So that's kind of the long and short of how the content will go from Drupal to Smarling and then back again. Some of the things that we think about whenever people are working with us and working with Drupal is really the, when the complexity starts to happen is, of course Drupal is a CMS that anyone can customize to do whatever they want to and however they want to use it. And there's tons of modules and tons of different things that can be included in different components and different parts of the site. So people have of course extended and built a lot of customizations. And when we start to work with customers who are using Drupal, that's kind of the one of the first things we look at is like, and customers will ask, do you support this particular module? And we go and we look to see, well, is it supporting, does it support internationalization and localization natively? Does it have a place to store the translations? Can we actually get content out of it? So those are some of the things that we think about. The simplest, it's passing content back and forth. And then we try to rely on TMGMT as much as possible to kind of do the actual management of packaging up the content and then pulling it back in and putting it into another place. Awesome. So, I mean, what's so important here, again, is you can so easily plug SmartLing into Drupal and automate your translation pipeline. And there are a bunch of other features that you can use with SmartLing to automate various parts of the workflow that make it super easy to manage all of this at scale. So really exciting. I think we covered a fair number of these other tools like manage just a couple of points. When you're using a product like SmartLing, for example, you will have the ability to really take a look at all of your translation jobs and know where you are in the translation process. You'll be able to get an idea for what a translation job is going to cost before you click submit. And we also calculate all of your translation memory and everything like that before we give you the estimate and before the translator starts to work on it. Yeah, it's such an important piece, especially around like how much are you spending if you resubmit content? Are you saving money because you're reusing content that was already translated? As well as some of the communication problems around content, like is there a spelling issue? Is there a spacing issue? And we have a lot of different ways, Tim mentioned, are there ways to control roles and access and of course, if you have people in your organization that need to participate, we support them for every, anyone can participate. We also have like single sign on. So anyone kind of in an organization can easily sign into the platform for their organization as well as just communication with Slack via Slack, posting different issues and posting different things to Slack. So there's a lot of different ways that you can kind of manage and communicate around this. I know that Drupal has often used a lot in like advertising and marketing agencies to kind of really help their customers build out sites. And this is a great way to kind of including translation, including a package such as a smart link connector in probably a standard build that you might use for a bunch of customers is a really great way to kind of have the half easy button to get to the translation process. I think that would be a really good use case for all of our higher ed folks as well. There's often sub-departmental websites and things like that where you might want to delegate roles in just the same way that you described in a higher ed environment. Totally. So we do wanna make sure we have some time for questions. We wanna be respectful of your time. You know, we showed you the translation interface that we provide, the visual context component, super, super important. And what we also want you guys to think about is that software is super important, but the people behind translation are also really, really important. And we've actually had a language services division in our company since 2009. And we've got some unbelievable results from our work. And one of the most important things is that you actually know who the translator is. And that's important to us, because we want you guys to have a direct relationship with the translators that we work with who create your content in all the different languages. So to that end, we've got a completely innovative model where we actually just work with freelancers and you have a direct relationship with your translators, which is great because it helps you to get to market 50% faster than it would if you were to go through a traditional language services provider. And our team is killing it. Last year, nearly 100% of the content was delivered on time and 99%, almost 99% of the content was approved by the customer without making any changes to the content. So we're really excited about that. And we also saved our customers money because we've eliminated project management fees for those of you who are new to translation, watch out for project management fees, and we have no minimums. We have a one word minimum when submitting new translations, one word. If you're new to translation, be careful about that. You might have to submit like 10, like 50 or 100 words per language just to get a translator to look at it. So the costs really, really stack up. And our people are just amazing. If you wanna learn more about the translators to work with smartlink, go to smartlink.com slash translators. We just finished a trip around the world where we actually met all of these people like Daniel and Juana. They are unbelievable people. Yeah, it's such an important component. You probably saw from some of the demo earlier, maybe a little bit in the permissions areas that you can, like we have different roles for agencies and vendors and kind of anyone can participate in the process. If you have your own agency and your own vendor or your own friend who's doing translation, they can of course participate in the process. But one, and we are the software platform that enables that. But we, as agents, we've been offering language services and translation for a long time. And if I saw there were some people who were in marketing and then education and a few other things, then you want people who know about your product to know about your service. If you're gonna have people translate things, you want them to know about your terminology and to really care about your product, because that's how you really get good quality. And our language source, it takes a lot of time and care and to kind of pulling that in. Yeah, for sure. And I think we're particularly excited about this landing page slash translators because you actually will get to know the people who translate your content. It's so, so cool to learn more about these users. We're about to hop over to the questions and I just wanted to throw two reminders out there. First is start asking those questions in the Q and A section below so that way Tim can take a look at what sort of questions you have. You could put it in the Q and A section or I suppose you can also put it in the chat section. Yeah, either one's fine. And the other thing I wanted to remind you guys of is if you post a photo of how you're watching the webinar, you could, with the hashtag, move the world with words. That way we know you did it. You can win that $100 lift card. And right now I've got my photo right up there on Twitter and we're hanging on, we're waiting for some other folks to add stuff because it would be quite embarrassing if I was the one who won the $100 lift card. That would be cool. I want you, I want someone on this call to win that $100 gift card. And yes, Dan, we can absolutely set up a customized demo and we'll reach out to you after this call to get that rolling. But definitely send the photo out. We want you guys to walk away with a $100 gift card. Just a reminder, the way that our customer was successful is they, number one, they knew exactly why they were translating. They wanted to enable users around the world to access their product and they needed to sell ad space on their website. Number two, they used the Drupal integration. They used the Drupal integration. They use it, they're automating the process. They went from having eight developers to zero, four plus days to turning around content to one or two days. And they've got this unbelievable translation management platform that drives translation quality. It allows them to have visibility into the process and they can analyze every single thing that happens in the translation pipeline so that they can get even better over time. So that's what we've got for you today. Of course, we have a poll question and the poll may not work. If you want to learn more about smiling, do what Dan did. Just drop the question in the chat or say you'd like a demo. We'll make sure to follow up with you but we see that there are a few questions. So Tim, why don't you take it from that? Sounds good, yeah. We've definitely got a couple of questions come in and there were a few that came in up in the back scroll that I've jotted down as well. So one was you addressed this a little bit when talking about the platform itself and going through the demo process but can you just speak a little bit more broadly to how costs are managed and calculated for when you're doing translations of content? Yeah, so there's a few different ways and really it depends on the type of people who are doing the translation and the type of mix of translation you might be using. And there's different use cases for different types of type of translation providers like Google Translate or Microsoft Translator or something like that or DeepL or some of these other providers are a great way to kind of start on some pieces of content. And really we've seen, just to kind of go on that a little bit, we've seen I think like a maybe almost a third of our customers now are using machine translation in a meaningful way but they're often doing that with some sort of what's called post editing. So someone uses machine translation and then they edit it. But generally there's some sort of kind of a per word rate or an hourly rate or something that is negotiated. And then you can reuse content that has been translated. Smaring has a lot of intelligence. We built a lot of tools to kind of reuse as much as possible, which is really where people start to see cost savings. And we also have some additional tools to help in the source content creation process so that you can stop, if you change one word from the to an or something or add a dash that can impact what you may need to translate. So you can stop those problems upfront rather than having to deal with it and when you're paying for translation. That makes a lot of sense. And I can imagine a scenario again in higher ed or in pharma, which I think one of our attendees is in where you have sort of multi-site installation or at least many sites out in the wild for various brands. And I could totally see a situation where it's like, there's this one paragraph that's gonna be on all of them. Let's reuse that content rather than resubmitting for every site. And even if you think about your marketing website versus your maybe Android app or a help center or whatever, you probably want to reuse content across those different applications. For sure. Okay, a few more questions. Want to make sure we're cognizant of time. So one, the next one here is, does this, how well does the system work for content that is behind a login, behind a permissioned wall? Yeah, so if you're within Drupal, the TMGMT system, the smart link integration handles everything within the Drupal platform. So even context, it will send and push the context into smart link. So smart link isn't trying to go and get content behind a login. And as far as us, we can also push content to Drupal once it's completed from smart link. So a callback essentially. And we can handle a login in those cases. For getting content back into Drupal, there's always also a background task that will run in case something doesn't work. Gotcha. Yeah, logins are not a problem. Sounds good. And then a last question that we have right now, although if anyone wants to throw in one more, feel free to drop in chat or in the Q&A feature. This is a technical question really. So I'm not sure if we'll be able to answer it entirely on this call, but the question's from Patrick. It says, I've evaluated the D8 smart link suite from my organization with a lot of success so far. But the only issue I observed when the translated XML files downloaded, it doesn't populate the review form for approval. Any thoughts? So the review form in Drupal, if you're doing the, where it has the side by side, I believe is what Patrick was talking about. Honestly, I'm not sure off the top of my head. It sounds like we should probably touch base and investigate that a little bit more. Cool. So it sounds like something that Patrick, if you reach out to Andrew or Adrienne, we can touch base on that offline and try and get that taken care of for you. You saved your name. Yeah, we just took a screenshot actually. So Patrick, we've got it. We're gonna get to you as soon as this call is over to get more information. Okay. And then let's see. Yes. And he has just replied in chat. He'd love that. He has sample files for you to look at. So that's great. So I think that is all the questions we have. I'll keep an eye on it for the last minute here. But I wanna say a tremendous thank you to Andrew and Adrienne for joining us and to Smartling for their support for the Drupal Association and the Drupal community. They've been really great partners in working with people who work in the Drupal world to help enhance the multilingual capabilities that Drupal has built in and then make the actual management and translation process much easier. So we're really grateful to have them as partners and really grateful that they could join to give this information and to share it with all of you. So as we finish this call, as I said before, we will be sending out a recording to everyone who's attended or registered for this event. And then Adrienne and Andrew will also send out the deck so that you'll be able to reach out if you wanna learn more. Any final thoughts? Yeah, like we're here. We'll sit on the call for another two or three minutes that way if people have questions we're here to answer them. We wanna make your localization journey as easy as possible. If you don't have the question today, no problem. You can go to smartling.com and a little chat bot will actually pop up in the bottom right hand corner. And you can just throw your question in there and a live human being will get to your question on our website and we're gonna help you. We're gonna do everything that we can to help you be successful whether it's with smartling or with somebody else. We just wanna help, we wanna help developers make translation easier for your company, for your project, whatever it is that you're working on. So thank you all so, so much for joining us. We hope it was valuable to you and we would appreciate your feedback as well. And yeah, I think we'll just hang out for a minute to see if anyone else has any questions. Thank you, Maria. We really appreciate your being here and John, thank you so much. Especially the folks in higher ed who joined. We really appreciate it. Yeah, would love to learn more about what you are thinking about and how you're working with people in translation and higher ed that's something we'd like to know more about. Totally, yeah. Totally agree. So yeah, we'll hang out, feel free to drop off if you don't have questions, if you do or if you'd just like to share a little bit more about your use case so that Adrian and Andrew can learn a little bit more about what you're looking for. Feel free to drop that in while we hang out here for another couple minutes. But otherwise, thank you very much for attending, everybody. Thank you guys, thank you, Tim. Thank you for helping to organize this and for everybody who joined, really. It's so great to be part of a community. I think that it's, and I know some, before I actually moved to the brand team at Smarling, I represented customers at Smarling and I had a number of Drupal customers and every single person who I met with not only raved about using Drupal but they raved about the Drupal community and they always have like their buddies in the same city, I thought that was really cool. Yeah, I've been to DrupalCon. I probably haven't been in a couple years but I think other people from Smarling have gone but yeah, it's always a pretty good event. Yeah, maybe we'll see you folks there at DrupalCon. Well, Amsterdam is coming up in October but also Minneapolis next year in May so that would be pretty cool. Yeah, that'd be great, count me in. Yeah. Especially the Amsterdam. Absolutely. Let's see. And then just as a reminder for folks, we said earlier that if there was anyone in London that we wanted to help them go to the conference you're attending, it didn't seem like there were any people directly there but if you have folks on your teams, perhaps maybe they could reach out and something like that, get someone over to you. Totally, and if you are in London, we're just sitting in the lobby as you guys can see. So like you can actually like walk in right now and see what's going on. Conference starts tomorrow at 9. 9, so 9 GMT. But if you're not in London, then you can't walk in and say hello. If you invite us to where you are, maybe we'll come by and say hello to you in your home. Great. That is an option. Very well. So it looks like we are all set so I think we will wrap it up here. Thank you very much, everyone. I hope everyone has a wonderful Wednesday and a wonderful end to your week and we'll be out with those materials in the next several hours when recording finishes processing and all that kind of stuff. Thanks, everyone. Take care. Bye-bye. Thanks.