 Reinventing international development, so quick introduction, who dat, what they do, and with Form 1, we're a full digital service agency that crafts solutions for the world's most influential organizations. So what sets us apart from every other digital shop out there? We're not a one and done. We build client relationships with our customers. We're passionate, we're creative, but most of all we're strategic in who we choose, so we are very selective in our RFP process. We deal with nonprofits, associations, government organizations that are trying to make a difference in the world. Some of the clients that are, or our future clients are Farm to Census, Center for Global Development, Robert Wood Johnson, Bill Gates Foundation, Smithsonian, and the one I'm going to be talking about today, the Global Innovation Exchange for the USAID. So a little bit about me. I'm Chad Schellman, technical architect, Drupal Evangelist, author for Drupal 8 Theming of Twig, big proponent of utilizing Pattern Lab with Twig and Drupal 8 to generate Drupal 8 to make templates automatically. We did a presentation on that yesterday. If it didn't get a chance, make sure you check that out, some groundbreaking stuff with Drupal 8. Oh, and by the way, the obligatory, we're hiring, so if you're, it sounds like something you're interested in doing, make sure you stop by the four month booth, always looking for some crazy developers. All right, so what are we going to cover with reinventing international development? First of all, I'm going to start off not by telling you what we do, how we do it, everybody can do that. I'm actually going to start off by telling you a story and a very interesting client kickoff meeting that we had. Then I'll talk a little bit about and show you some examples of how we use creative design to kind of lead the direction, both strategically but also creatively, and how we use Pattern Lab to do that. I'm also going to talk about long form content. I don't know how many people realize this, but nobody reads your PDFs anymore, okay, and PDFs are dead. So I'm going to talk about how we handle that scenario. Search, search up makes everything in the web nowadays, I'm talking about a little bit about solar, but how we actually extended solar. Really impressively, I think at least to me, is we took a government agency website and went from design to completion in a hundred days, which I don't know if you ever had a government client or if there was any government clients in here. That's almost unheard of, especially with the bureaucracy nowadays. It all started with a seed. So what do you mean by that? This is a moronga seed. So in the deserts of South Africa, vegetation is obviously really scarce on how it grows, but actually there's a moronga tree that actually produces a seed. So what does this have to do with global innovation and what I had to talk about today? Well, for this kickoff meeting with Alexis Bonnell at USAID, it started with not getting in a room with her stakeholders, it actually started with getting on a plane, getting on a plane and flying to Boston, getting off a plane to Boston, driving to MIT, going to the D-Labs in MIT and actually looking at different inventions and innovations that were being developed not only by MIT, but all the smart students that were actually attending MIT, such things as washing machines connected to bicycles because there's no power for them or solar lanterns. But the one that was most interesting was this machine that looked like kind of a bingo ball tumbler. And what it was, it was to de-shell these very hard moronga seeds. And I don't know if you've ever even heard of a moronga seed, but these are used for medicinal purposes, which at the time I wasn't aware of. So I said, can you eat one? And they said, well, yes, you can eat them, they're actually used in some places for weight loss. So Alexis, the wild client she was, said, okay, everybody, grab a seed, we're all going to eat one. So we ate one and it was fine, chewed for a couple of minutes, and then probably about 20 seconds into it, it felt like somebody had taken my mouth and rinsed it out with an antiseptic. Continue to walk around probably for about 30 minutes after that, not being able to feel my face, my tongue. One story short, though, a lot of times we don't get a chance when we're building something to actually feel it, to touch it, smell it, use our other senses. We're always focused on the visual aspects of a website. Being able to actually have this opportunity was probably one of the most exciting actually aspects of it, because once I was able to actually feel it, touch it, smell it, when it came to actually sitting down and doing content strategy, when it came to doing design, it put everything in a lot better perspective than what we have done on a lot of projects. So what does that all look like? So really quickly, I'm going to talk about creative, pattern lab, long-form content, solar, and the 100 days that it took for us to build this website. So I'm going to make a part of the slide, so let's go ahead and exit out of here and go into what I call demo time. So this is the homepage of Global Innovation Exchange. We were actually able to start design on this before we even started looking at content strategy, content types, fields, UX, by utilizing something called pattern lab. Anybody here use pattern lab? A couple of people, okay? Pattern lab allows us to actually create atoms, molecules, organisms, templates, and those pages all within static HTML, CSS, SAS, that we can then turn around and utilize these actually to build out the web pages in Drupal. This is actually what kind of expedited us being able to kick off the project, so at the time that the development actually caught up, it took two weeks to actually theme the site in full, because we had already done the design work utilizing the pattern lab. The nice thing about pattern lab, if you haven't seen it, is it's responsive in nature, so you can already start testing for particular break points. You can see the color palette, the way that fonts look like, the way the different elements look like, and as you start to break this down from atoms to molecules, you start taking these, the most finite component of this and you start building upon it until you get to the point where you can actually say, okay, well, what's the homepage going to look like? This is not Drupal, it's actually a pattern lab, but you can actually see interaction, what card styles are going to look like, what staff picks, funding opportunities, so that when it came to the time of actually steaming it, we're actually able to actually put it back over into Drupal very easily. Next thing I want to talk about is search with solar. So people are used to Google search, people are used to database search, but when you start talking about 3,000 innovators, thousands of funders, resources, a piece of the content that people are looking at, because here's the challenge behind a website like this, is this is a community-based website with users, but funders are actually coming to like to say, okay, well, how many people are actually building a solar lantern? And believe it or not, prior to this site being built, there was over 350 people building pretty much the same solar lantern, okay? So now we actually have a place to crowdsource that information, be able to actually have funders and resources come in and actually take a look at innovations that are available, they can quickly do it at a glance to look at the different information that's being innovated on, the stages of it, the cost per unit, where it's being created, where it's sector and area that's supposed to be developed for, so the funders are able to actually get a really quick glance, and it's also giving the innovators a marketplace, so to speak, to be able to actually put their innovations and actually have people be able to find them. It also allowed for innovators to actually get together and talk to each other and possibly even partner up to say, you know, well, we're all, there's 10 of us building the same exact solar lantern, let's pool our resources and make one really kick-ass solar lantern, okay? So that site provided the ability to do that, but because there were so many innovations coming in, you know, they needed to be able to wait to provide a really nice search mechanism for this, so we implemented solar, and yes, anybody can go and implement solar, doesn't take a lot to create a solar index view, or to create facets to be able to filter information down based off of, you know, different fields and keywords, but where this actually really came in handy was for the actual innovators or users of this community that actually were logged in, because of actually what we were able to do with that is generate, you know, a custom dashboard utilizing the same concepts with solar, so not only were they being able to see, you know, organizations and money being funded and the amount of resources in there, but they were also, as an innovator, were able to actually take those solar indexes and make more like this functionality, so they're actually able to see what's my competition, what are other people around me that have maybe favored in my innovation also looking at, and so it would give us a ability to actually really extend upon solar's capabilities with something that's really not available out of the box with Drupal in a module, but actually writing, you know, custom code that actually talked to solar in the back end. Taking that, you know, one step further, we were actually able to build these dashboard pages utilizing that, but then it came to the point where they were saying, well, I have this really long PDF, and we were like, nobody's gonna read your PDF. You need to make your PDF of your innovation or the information you're trying to share with your innovation or the resource that you're trying to upload more interactive to the user, okay? So how many people here are familiar with long form content? Couple, okay? So since people, especially depending on where they're at, their main medium might actually might be a phone. People are used to scrolling on phones now, okay? So that's translated now over to browsers as well. People don't have a problem scrolling through long pieces of content as long as a content is interactive, as long as it's engaging, okay? So what we did is actually turn around and made long form content fun to look at, okay? And we did this inside a Drupal tour that could actually develop and build these pages by themselves without actually having a developer or a designer have to interact with them, okay? So you may have been asking, well, you know, is this just a basic page? How are these components being developed? What's the flexibility that they have? You know, and those are all great questions. What we ended up using is simply is paragraph bundle. Anybody familiar with paragraphs? Okay, so we're actually able to generate, you know, long form content pages utilizing different paragraph bundles which allowed us to create, you know, a long form image or an aside or a section break and let the client put the back in the client's hand to actually take a look at their PDF and actually build these pages dynamically utilizing this functionality. All this together though, actually, you know, it was able to speed up the process and so between pattern lab, between the long form content and the solar, we're able to make this really robust community-based website for innovators, for funders and for places for resources, you know, to be almost like a central marketplace. And we were able to do that really fast, 100 days. You know, I worked on a lot of projects that have been a technical architect, a front-end developer, a front-end manager, many different facets on many different projects and this was probably by far the fastest. Now I will say, this was a Drupal 8 project. This would have been done about 30% faster. But you know, we had built this prior to Drupal 8 being released, but if you're looking at getting ready to start a project, by all means, take a look at Drupal 8. That's all I had, real quick, fast, you know, skinny of what we did on that particular project, how we're able to turn that around 100 days. Are there any questions? No? All right, well, that was re-inventing international development. Again, Cheshire Summit 4 and 1, if you have any questions after this, feel free to stop by our booth. Thank you. You have a new Mac or an old Mac? Let's see, there's HDMI in here somewhere, isn't there? Yeah, at the end of that. That's there, so you can just go in there. All right, thanks for, I guess I'll stand here. Thanks for coming to this presentation. So I'm with Smartling, I'm a solutions architect, which is the post sales integrations person that really helps clients once Smartling's, you know, made the sale, helps the clients actually integrate with our technology. I'll be presenting with two guys from the Weather Company, who with the Drupal community knows much more at this point than Smartling, and so we're really happy to be able to do this with them, kind of use their power to get our name out there and kind of, you know, tout the success that we found together with our partnership. And I'll introduce them when we come to, when I hand that off to them, so. And the presentation that I want to present here is translating actually into other languages and localizing content, so localizing a little more, you know, if you have images and other media that isn't just pure translation, but actually you want, you know, those of the community that you're marketing to or presenting your content to, you might want to present different content, not even just translation. So translating and localizing content in Drupal, using the media current presentation framework. Let me get that. So for those who are interested in getting the presentation, I'll put this up at the end too, before DrupalCon, you know, downloading the presentation through the official DrupalCon site, you can go to this short URL and grab the presentation right now if interested. And you can look at that after we have some more slides at the end of this presentation that go into more details on the technical integration. So you might be interested in downloading that presentation, looking at those slides. And of course, coming by Smartling has a booth, 703, kind of on the far when you go in all the way to the right. So feel free to stop by and ask us any more questions that you don't get answered here. Okay, so let me tell you a little bit about Smartling. So we are a translation software company that simplifies the process of managing and delivering global content. That's a strictly marketing spiel there. So really what that means is our company, if your company is looking to go global very quickly, scale, but also not requiring a team of 20 to 30 people managing your translation process, that's where Smartling comes into play. So we, three main kind of points that I want you to take away about Smartling is what we provide is one. Visibility, so let me go through here. So here's our main product is we call it the global fluency platform. And so with this product, this comes with both the kind of technical backend for actually moving data around and getting that translated as well as being a platform for reporting, keeping track of your translations and content and actually having translators go in and do the translations themselves. Smartling alone doesn't employ translators, but we have relationships with translation agencies to do the translations, human actual real translations versus machine translation. And we also allow if your company like Weather who came to us and they already had a relationship with translation vendors, we onboard them into our system. So more agnostic, more flexible with those who are doing the actual translation, but we're that platform capturing content and allowing translators come to one place to do the translations. So the three pieces I want you to remember is one, visibility and control. There's other vendors out there that are in our field that kind of offer a product that's a black box. So they say, hey, you come to us, we're the one stop shop. Just don't worry about what's happening in between. Just give us content. It'll get translated and reviewed and we'll just deliver it back to you. You have no control, but that's great because you don't need to control. You have no input into the service, but we're gonna deliver this back to you on time and you're kind of stuck with what you got. So in our system, we automate a lot of the process of pulling content into the system, but you have visibility throughout the whole process. You can see as the content's moving through translation, you no longer have to reach out to smartling or your translation vendor to say, hey, you promised that this content would be done by a certain date. Where are you in that process? How much have you actually translated? In smartling, you're able to log in to our dashboard as a content owner and actually in one shot be able to see the translators going through translating content and if they have any questions or concerns, they can raise those issues right through the smartling interface and it kind of just simplifies it all into one place to get your reporting and status of the content. Two, improved productivity slash scaling your business. So one thing that weather is gonna talk a lot about here coming up is how they were already, to some extent, successfully localizing and translating their content, but they were running into a place where they didn't wanna hire more people to go do even more languages. It wasn't scaling very well for them. So smartling really allows you to have one person instead of 10 manage n number of languages. This one person, if you add 10 more languages on top of the 30 you already have, you don't have to hire another person. That person, after a few clicks, can go ahead and send the same content they have for French and German. They can have that content go out for Italian and have it started translating with an end date or two. At that point, all the pipes, to get the data back into, say in this case, Drupal or other content management systems, that work has already been done. So all it is really is working on our platform to request translations for new languages, and at that point they can sit back let the translations happen and it'll automatically deliver to the place that will deliver to the end user. And three, fast time to market. This kinda goes along with the first two, but this, we do also along with the quality and not being a black box, we do wanna make sure you get to market quickly. So we do wanna make sure that your content comes in as soon as it changes and updates. Your developers have created a new page in Drupal that comes automatically into smartling. It gets to translators, they start translating right away, and they deliver that back and it automatically comes back from your system. All of that, other than the human translations themselves, we've automated the rest of that process so quickly you can scale from, say, 10 languages to 40 at one time without having to add months onto your process to set everything up. Once the pipes are connected, you're all set to begin scaling to any number of languages you're looking to do or the volume of content. So let's talk, since this audience is a very targeted audience here for Drupal, one of our connectors, as we call them, is a module for Drupal. So we actually have a module for Drupal 7 and for Drupal 8 we're polishing the final touches for the Drupal 8 module. But what this really allows you to do is, and whether, again, we'll kinda go into detail on how this helped them, is going to Smartling allows the content creators and the developers to have some initial integration with Smartling to kind of connect the module up to the Smartling project in database of record. Once that's done, the content creators can go ahead, either node by node, page by page, or say, you know, they can send in bulk in couple clicks a whole bunch of content over to Smartling, select a few languages within the module in Drupal, and then go ahead and commit 100,000 source words for German, French, and Italian with a couple clicks, and that sends right over to Smartling. They don't have to worry about packaging that together, tracking in Excel spreadsheets. Our module keeps track of all the content that's submitted. And some of the teams, as you're going through, you don't wanna necessarily have to wait for French to be done to get German and Italian. If German's already done, then our system automatically goes out once it's 100% complete, pulls that right in, automatically creates the node for that language. And really, it makes it so, once you connect those dots, your content creators can just go into, keep to their standard process, but as they're updating content, our module is picking that up, resending it for translation. Only the new content from before is getting translated, so they don't have to redo any work. Then it automatically comes back to Drupal. And so we have this in Drupal, but we also have these in many other channels, including WordPress, Sitecore, Adobe Experience Manager, Git, Repositories, et cetera. We have many other channels, so if Drupal, like I was just talking with the weather guys, is really only one path of content needs to be translated. We also have the other channels to get their content translated and leveraging the same translations you've already done. And finally, from the smart link side, I just wanna say, kinda highlight, here's an animated GIF, it's probably hard to kinda see from back there, but a translator, when they come into smart link, is gonna, they don't need to log into Drupal, they don't need to log into WordPress to see the content. We actually capture, if they're Drupal module, the visual, how the page actually looks, and if it was rendered on a webpage. And as they're doing the translation, it actually dynamically puts it right into the interface. They can see, is this breaking the user interface? Is this, instead of going back and forth via email, once you're done translating, a developer looks at it and says, that's German word is 200% too long. That's an incredibly long word. I need that about half the length. The translators will see right here if it's breaking your user interface. Oh, this is an alert box. Okay, I only have this much room. And that kinda cuts out that back and forth. So that's a big benefit that you get with the smart link system. So, saying that, I will hand this over to Vashal, who's a senior engineer for web development at weather.com or the weather company, and he's gonna talk a little bit about weather's needs and why they chose smart link and the integration that we did. Good afternoon everybody. So, in 2014, we used to have our websites working on Java technology using and translations for international sites was done through Java's resource bundles. We didn't have any translation management system to connect and record all the translations for all the different languages sites that we supported. We used to have our mobile website and our desktop website as separate entities. So, just imagine two different applications just for the website, and then we had the iOS app, the Windows app, as well as Android app. All of these systems did not talk to each other in terms of translation. So, each system had their own set of translations for almost similar terms. So, like, weather terms like pressure, humidity, wind, you know, all of those were like separately translated to their own translation vendors. And we didn't have a single repository to have a tab on the quality of translation or having a translation memory that we could leverage for all these properties. So, in 2014, we started with the redesign of our internet, of our US site. So, this is a screenshot from one of the pages of our US site where everything is in English, obviously. And at that time, when we launched the US site, our international sites were still on the older platform with unmanageable translations, basically. So, last year, when we started working towards a solution of internationalizing the new framework using Drupal, so this website is currently working in Drupal 7, right? And Angular modules, so Angular JavaScript modules. So, each component on the page that you see is an Angular module by itself. And Drupal renders the module configuration and the module basically requests for all the translations and any resources or JavaScript or CSS by itself. So, when we were supposed to migrate this platform into the international sites, we were looking for vendors and we did a, we reached out a few vendors and did a scorecard on certain parameters that we had that needed to be fulfilled. So, the big ones were a single translation management system that we could use for different platforms. So, Smartling did that job for us, connecting the apps through the GitHub and the Drupal was done by our internal team in conjunction with Media Current to come up with a solution for the Drupal module that Drupal Smartling module that Dan talked about. So, using that framework, we were able to deliver like 38 or 39 sites within a period of three to four months. So, the US site took almost seven to eight months to build but all 38 sites after that were just like integration of Smartling Drupal module with our systems, with our Drupal system to roll out all those sites and it was pretty seamless. Once the solution was in place, without going through development cycle, the product manager or the localization manager could roll out any number of locales directly by doing some configuration changes within Smartling interface and Drupal interface that we have. So, little to no development work involved and they can roll out sites at will. So, basically these were the requirements for selecting Smartling. Let me go to the next slide. All right, so here comes the Drupal technical expertise that Patrick is gonna talk about, how those things were meshed together to come up with the solution. It's Patrick. Hello, my name is Patrick Birch. I work for Weather.com, the weather company of course and basically how this works is Smartling provides a wrapper around the entity API, so that's how it can get all of your nodes and taxonomy terms and everything translated into the system. But Weather.com doesn't really have that as its primary interface because we have the Angular mods. So, with the help of Smartling, they wrote an extra module to help translate our special Angular mods and those made it really easy to get everything localized to every other language. And yeah, the loose coupling. The loose coupling, yeah, basically how it helps is that we can produce an Angular mod with the PO files that have the strings to be translated and then whenever those are committed into the repo, that we can go to our test environment or staging and go ahead and submit them from there and once they get submitted and they start getting translated and they're complete and they get downloaded, then we can test and verify on a lower environment before they ever get pushed to production. And once it makes it to production, all you have to do is download the strings and it's done. And it makes it really easy to make sure that everything is very fail safe. And here's an example of the interface and I'm going to turn it back over to Vishal who actually uses this interface. All right, so this is the interface that Smartling and our CMS team built for basically the product development team, including the web development team and product managers, QA team, everybody involved with the product development basically. So this is an example of a screen where you can see there's a global forecast weekend module, so which is nothing but like global mobile module that basically serves the weekend forecast. So like Friday, Saturday, Sunday data that you could find that on our website. So this is an Angular module with certain labels and phrases that need to be translated. So each Angular module has a PO file which is basically a key value pair of message ID and message string, if you guys are not aware of what PO file is. So the message ID message string is basically written by the developers when they are building the module and we use a directive using the Drupal's PF translate. So we have an Angular directive that actually talks to the Drupal PF translate module or I don't know, what do you call Drupal? What is the locale module? Yes, locale's module. So each of those PO files will have a certain number of strings. So basically what it represents is this module is shown up here. When you click on it and select translate, you'll see the screen on the right side. So basically the first screen is the first page when you go to the submission screen where you actually have to translate into whatever languages you want to translate into and the next screen is the one where you actually select the locales. So let's say we have the forecast module only available on 10 of our 40 sites. So you go ahead and just select those 10 languages or locales and select and submit it. Once it's submitted, it goes into the workflow system and our localization manager, the product manager for localization, he actually reviews the request that comes from a developer and sees whether the request is valid for all those locales and then he'll approve or disapprove or send it back to the developer depending upon the requirements. So let's say if the developer by accident selected all 40 locales and that module is only going to be used for eight language sites. So there's no point translating it for all those 40 languages because each translation has a cost associated to it. So he can review that and just get those eight translated. Once the translation is done, we see the screen, this is the smart link. The submission screen. No, it's not the submission. I think this is the submission screen. Yeah, it's showing the progress of all these programs. Yeah, it's a progress screen basically. So it shows you for each locale for that module was the progress. So here we have captured a screenshot that actually has 100% on every different locale but you could have an example where the Spanish and French and German are all 100% but some other locale like Arabic or some other are like just 40%. So you could download the translations as they keep coming. Normally the turnaround time for a regular English or Latin character sites is one to two days for more complex Asian languages like Chinese, Korean, Arabic, specifically it takes up to three to four days but they have their SLAs defined for getting the translations unless there's a on a case-to-case basis you may have some unusual, but mostly it's like within three to four days you get all your translations back. So basically it's a pretty quick turnaround and the good thing is if you have a string that's already translated, you don't have to go back to the translation because the translation management system or the translation memory will actually get back the string for you. And let's say a feature rolled out for the apps and they had 10 different strings being translated. So the translation memory will have those 10 strings translated in different languages. So if for the website we go and build a similar module and the similar eight or 10 different strings you get that automatically without having to go through the translation. So that cuts down on a lot of cost that we had to be associated for getting it translated through the translation vendors that we could get very streamlined using the smartling module and TMS system. This is an example of the screen, basically similar screen to how we had for US, but you see the same Angular module using the PO file translations can serve all different kinds of languages. We have example of Spanish, we have example of Chinese, and the second one is actually right to left language side which is an Arabic side because they read right to left, not left to right as regular languages. So we were able to accomplish all of these using that solution. So any questions, comments? So we used to have different domains, subdomains like es.spaniel.wether.com or fr.wether.com. With the latest Google SEO best practices, what we found out that having a single domain and then having the locale as part, as a subpath is, yeah, like a subfolder like weather.com slash frfr or weather.com slash d-e-d-e actually ranks better with Google because then it thinks all these properties are from weather.com. And if you have subdomains, we have a lot of issues with cookie management and stuff because subdomain cookies might interfere with your base domain cookies and whatnot. And local storage has problems. So now with this, you don't have to worry about those issues as well as have a better SEO ranking with Google. So that's how we managed currently since last year. Currently, we do an accept language and the IP, both. And if you go to the, if you are in Germany and you go to weather.com, it will detect, if you have a browser that has an accept language as German, it will take you to the German site, weather.com slash d-e-d-e and also say that we detected you are in Germany with a German language browser. So we have redirected you to German site. If you really want to go back to the US, I click here and then they can opt out of that. But by default, only on the homepage we do that because we don't want users with deep link like the Today page or any of the forecast pages if they are already having a bookmarker coming from Google, we don't want them to be forcefully redirected to their language site. So they have an option to select it from the dropdown in the header. So another question back there. So right now, we're just working out the final, some final pieces to that to kind of polish that off and get that ready. That ETA and that I'm always careful being on the client services side and not allowed to give any dates or always get bit by those when that happens. But very soon, it's the final pieces to that. We're going to get that out the door extremely quickly. That's the highest priority right now for our Drupal developers is getting that out the door since there's so much hype. On the other side, of course, it's related to people adopting Drupal 8.2 and so I think, you know, once our clients that we have, which you have a few are starting to dip their toes into Drupal 8, that's incentive to get that finalizing out the door. So I know that wasn't an exact time for you, but very soon. Short answer is yes. We support, to some extent, a smartling attempts to be, you know, agnostic or it doesn't care about the actual source of that content. So get tax or P.O. is one example, but we support, you know, Android and strings files. We support XLIF, we support custom XML, support Java properties, et cetera. And you can find more on our website at docs.smartling.com if you're interested in seeing what different file types. But we know that Drupal, I think the common ones are get text, XLIF and XML is, and we support all those through the module. Yeah, kind of dependent on how that content is stored. Any other questions? Vishal, do you wanna talk a little bit about like the day in the life of a string and how you kind of, the steps a developer creates a new module or an update and kind of how that moves through the system? Sure. Just kind of simplify that. Yeah. So let's say a request for a new module or a future feature comes from the product team and it comes back to the developer. So they start working on that module basically based upon the design marks. Design marks may have some strings on them already. So when you are building the HTML or if a certain thing needs to be shown as a dynamic value coming from a JavaScript web service or whatnot, we identify that data is going to be a dynamic data. So we need to make sure that the system that actually provides us the data has the translations available for whatever languages we are going to support. If it's a static string that's going to be like a label on our web page, we externalize all those English labels into the PO file, create the PO file from the local Drupal instance as well when you're developing, you can go to the smart link module in your local Drupal instance and submit for translations. So you can do that from your local. Once your local instance actually pushes the content over to the translation management system and the localization manager approves that translation, it goes through to the smart link system where the translators receive the request for translating into various languages. So I think first smart link checks if the string is already translated. If not, then only it goes to the translation managers. So we get back the strings within two or three days. It just depends if it's like machine translated coming from the memory, it's instantaneous. Maybe the same day you'll receive it because the push and pull happens through a cron job. So Drupal has a cron job running where it pushes the content to smart link and receives smart link translated content automatically. So it just depends upon what's the time frame that you have the cron setup for. So on production, I think it's pretty frequent. Some of our test environments, it might not be so you can go and actually run those cron jobs through your run cron interface in Drupal. So once the translations are received, it's just available in whatever environment. So let's say your development is completed and it goes into QA, QA boxes can just go and download those translations. So currently we do a submit and download, but the submission is actually just like a trigger in that environment to fetch the translations because we made that decision concept decision because let's say a model's already there in production and you have a request to change that, something in that module and you are either changing the label or doing something else with one of the existing labels. So you don't want the production module to get affected directly by a change that you did in the development or QA environment. So we made a conscious decision of not automatically downloading it, though smart link did provide us that opportunity to use it because we didn't want to corrupt production with any development or QA changes. So whenever there's a change, you just go and submit for translation and it should be there in smart link, it comes back automatically. But yeah, we currently do it manually just to avoid any undue situations, yes. Currently we don't have anything that indicates that the translation is not available on the front end at least because the way the PO files work is you use the English fallback strings. So if you see that this thing is coming up in English, you know that this is still not translated unless something like certain words or phrases can be the same for like Spanish, like I'm not sure like wind, I think in German and English they both call wind. So it's really hard to say if it was actually translated. So you can go to the smart link interface, look for that PO module and see if the translation is already completed because it will show you 100% or 80% or whatever percentage. If it's 100% you 100% sure that everything has translated. Yeah, and I think to add on that too as far as it kind of depends on your workflow or process that you need and the business requirements, the simplest approach when automating the data into smart link is really conceptually say, you know in general I want this type of content, this module from now until forever for these five or six languages or these target languages. And from there smart link, that module can whenever you update that content the developer doesn't have to continuously submit that content. You've already said you want that module and our module or that for that module and our smart link module and Drupal will pick those changes up and resend to smart link and does a diff at that point. You don't have to understand what is the differences. We will only pull that one new string in but I guess short answer in the Drupal interface you won't necessarily know that one sentence that's gonna be that new string for translation but you can trust only your updates and changes will smart link send for translation. Did that answer your question? Any other questions? Well the only things that will get sent for translation are translatable strings that are wrapped in T-function. So it works pretty much just like everything else in Drupal like for nodes and taxonomy. It's like if it's- Unmetatags for example. Yeah, unmetatags. Anything that, only the thing that could get translated. Yeah, you can. So Kostya's actually, this is our actual, Drupal developers wrote the module. So Drupal. Yeah, so of course you can send pretty much anything for further information. For example, you know, we just resend in our interface when you take the fields. Right. That you want to do to play and then you just send. So you can configure that. Yeah. So when you get content back, like for nodes, for example, a genomicable pattern is like two types of ancient nodes, yeah, one when you like hold on, you know, into the other instance. And other when it's like a little translation. It will check if the content that is translated. So if we are talking about a little collection that also support little collections, it's like some other sort of. Yeah. Great. So what you're saying in a sense is that yes. Yeah, short answer. Yes. Thank you. Are there other questions? Okay, let's make a screen here. As you probably know, if you've been to other events, please go on to our event on the Drupal.com website and rate that you guys loved and enjoyed our presentation. Now, you get authentically rate and so here is that. And thanks for coming. Thank you. Oh. And Smartling has a booth, 703, please come by. We have charging dongles. If you need your phone to charge, we got what you need.