 Morning, everyone. We are going to kick off our webcast now. I am really excited about this. I think we have a phenomenal story here, dare I say, one that has exciting tales of high sea adventures. Sorry, that was the best joke I could come up with. But the crux of the story today, we're gonna be talking about how Princess Cruises is using Lingotech and Drupal to really empower an application that allows for onboard interactions with their customers. And without further ado, I really want to get kicked off. Before we do that, I have just a couple of housekeeping items. If you're listening from your computer, select the mic and speaker audio option. Actually, I'm gonna say the majority of questions we'll go ahead and take via the Q&A system. Please remain muted if you are a panelist and you're participating until you're actually speaking that'll help keep down the external noise. I'd love for you to ask those questions in the chat window and I will pass those on to the panelists as we go along. And if at any time you wanna tweet something in this webcast, please do tweet with the handle at Drupal association and we'll make sure that that gets published back out. One more little announcement. We do have an upcoming DrupalCon. Just finished one and it's time to start planning the next one. In late September, we're gonna be going to Dublin and so I wanted to remind everybody of that. Also, we frequently throughout the year have global training days and I wanted to call out that the next global training day, I believe is September 9th and that will be the next big event that you can kind of get involved in with the Drupal community and the Drupal association. So without further ado, let's go ahead and jump into this. So we're gonna be talking through the Princess at Sea application and onboard surveys that you participated in. Our presenters today, we have Hilary Neith who's the project lead from Princess Cruises. Nate Craddock who's also a project lead at Princess Cruises. Sabu, oh, I apologize, I should have got the message. Yeah, I thought you had him. My apologies, Sabu. Good to go. And also, I'm from VP of marketing from you. So let's go ahead and kick this off. So just in short, could someone give us that high level view of what this project was about and what made it so successful? You want to go? Sabu? So Princess Sea is kind of a guest experience portal on board our ship. It's, we'll go into a little bit more detail, at least from, I guess, details on a high level, kind of a contradiction, but at least give a little insight into what it actually is through some screenshots and a little bit. But really it's a way for each of our individual vessels to have kind of their own web-based experience. It is a portal that allows our passengers and their guests to view their on-demand bill, view all the events that are happening on board to see menus and dining and venues and ship deck plans and all available on the ship via the wifi. Drupal runs on each one of our vessels right now. So we've got 17 different Drupals floating around the world. All maintained by the ship, as well as having content fed from a centralized shore side repository that both pushes content out to each one of the vessels, as well as brings content back in. You'll see some of that workflow later. We'll kind of go into one of the more interesting use cases we have with that content workflow that in particular deals with multiple languages and automatic translations and human translations and all this kind of stuff. Stuff that we couldn't have done without Drupal and without Link to Tech. I mean, that flow might make it even more visual and clear. Yeah. And it sounds very complex now. It might get better. Yeah. And in particular, we'll be talking about kind of the onboard evaluation survey that we use that's really kind of expanded what we can do with this platform onboard and the way that we can get feedback from our guests. This sounds really exciting. I'm excited to dig into this a bit more. So let's talk a little bit. How did you connect? How did Link to Tech get involved in this project? And Calvin, maybe a little bit about Link to Tech's kind of role in kicking this off. We cannot hear you, Calvin. Good morning. Thank you. Sorry about that. I appreciate the opportunity here to speak. Link to Tech and Princess Cruises have been working on the Princess at Sea's application for a couple of years now and we're excited to be a partner with them. And the new survey application as part of that is the newest project that these folks are doing. What's exciting is they've been able to use the same platform and having that sit on site at Drupal and use it for a variety of different functions and applications on each of their ships. And so I'll let Nate and Cebu and Hilary talk a little bit more, but it was really important for them to be able to service their multilingual clientele and have the customer service aspect be serviced onboard those ships. And so it naturally fit that they needed to have translation as part of the capabilities of their solution. And we had met, I think, at a bad camp several years ago and made the introduction and started working on some prototypes early on. And it's really that these guys' vision that made this come true. We're just the translation piece of that, but we're excited because it's such an interesting case study. And as you'll see as we start to go through some of the slides, how they've actually solved this problem, I think it's probably, if not the most unique solution, it's one of the most unique Drupal solutions out there. So I'll turn it back over to those folks and let them describe that. But we were excited to be a part of the project and certainly, the community aspect and being in some of the camps and cons has helped us be part of the community and make these kinds of connections. Excellent. So go to the next slide. Thanks, Kevin, for the introduction and relationship with Lingotech. It's been very, very valuable for our Princess Satsi team to work with Lingotech. It's been a great partnership and there's more to come in the future. Going to this one is our team from Drupalcon New Orleans from last week. So Hilary is part of the presentation, I think, where she's having some technical issues that she's not able to join. So should we move forward to the next slide? I apologize, dude, this slide's a little complicated. So I hope we get up so. So just a brief introduction to Princess. We were founded in 1965. We just had our 50th anniversary last year. It was a full year long thing. We had 18 cruise ships up until March. We retired one of them, so we have 17 currently and another in construction in Montalcone, Italy. So we'll be back up to 18 mid, or round in next year. We host over 1.7 million guests each year across all our fleet and all our vessels. And a lot of people know us from the Love Book, which is a very popular show. It ran for like a decade. We celebrated that as part of our 50th anniversary last year, actually. We have the cast out on one of the ships during the naming ceremony of Regal Princess. A lot of fun. And kind of ties in with the Love Boat a little bit. Our last deployment was actually on the namesake of the Love Boat, which is the Pacific Princess. So kind of give you an idea of the scale of what a ship is like. Kind of hard to get a picture of it, even seeing this photo. It looks big, but some kind of facts about the actual construction of these ships. If you could page forward a little bit. There's a bunch of little stuff here. So like a vessel like this takes about 3 million man hours to construct. It's built out of 37,000 tons of steel. Within it, it has about 2,500 miles of electrical cable, land cables, all the infrastructure to make, not only the regular plugs and all that stuff work, but all the IT equipment work. And to make it that clean look, it took about 95,000 gallons of paint to paint the entire ship. And there's a 14-tongue and anchor in the front. You can kind of see it in the front of the ship here right under the princess, regal princess name right there. It's a big kind of slot in the side. To give you some ideas about what our operation looks like from the entire fleet per month, we go through almost, you know, a little over 14 million slices of pizza. It's a lot of pizza, about a million and a half gallons of soda pop. One million cookies we serve on board. It's my favorite thing. It's kind of bad, very bad. 120,000 bananas, which I always find interesting when you compare the amount of bananas to cookies. It's, you know, and enough ice cream to fill an Olympic-sized pool. So, it's a lot of stuff, you know, we- That's some amazing religious stuff there. Yeah, oh yeah, yeah. I mean, that's to me one of the most fascinating things about this business is just, you know, in order to make someone's vacation happen, you know, what goes into that really in the background. So, presidency, like I said, it's Drupal-based application that lives on board the ship. So, there is a web server on the ship serving up Drupal. It's D7-based right now. We hook into a bunch of different backend systems as well as have our own content publishing. So, we show like all the events that are happening on board, which also includes allowing our guests to create their own personal events that they can share amongst their circle of friends on board. We include, I think there's, yeah, there we go, the access to their state room account, which ties into our property management system on board, a free messaging system so that guests can communicate with each other. And a very important part of this is the multilingual interface. We started out two years ago on Sapphire Princess when we first started operating in China and Japan. We offered simplified Chinese on one ship, rolled it out then in Japanese and Chinese on two other ships and have recently rolled all our languages out across the entire fleet. So, we currently have Spanish, Chinese, Japanese, and English. We'll be adding German in about a month and a half, adding traditional Chinese in August and then rolling about three or four other languages out next year. So, a couple of things to note here is one thing I would like to remind is the Drupal is running in each ship and the challenge that we have is providing the right information to the passenger at the right ship at the right time, which is a disconnected environment. It's not, the satellite connection is not very strong at times so Drupal has to independently work on board the ship as well as it should be smart enough to provide the information even in a disconnected state to the passenger. So, and the ships travel through time zones. One interesting factor that we had to solve is normally when you think about a server it stays at one place. Our server moves around the world and moves through time zones. So, it's an interesting problem that we had to solve those things. So, if we go back a couple of slides, actually missed. Yeah, so, and that's one other piece we kind of talked about briefly is that, you know, Drupal is on the ship, it drives not only our application on the mobile and on tablets and desktops, we also have web services available that our video on demand system uses. We drive kiosks for like the art gallery, directly and indirectly. We talk to some of the equipment on the bridge so that we know, you know, what the latitude, longitude of the ship is, all sorts of different data, as well as a future project which is driving the actual printed version of the ship's daily newsletter from the content that we have. So, all of this is a little fine as well. Oh, hi, Henry. Hey. Glad you could make it. Yep. I love it. Drupal is truly your great ones, publish everywhere hub for exactly what you're doing on the ships. And that too in a disconnected environment with the application of data. Irrespective, if you think about it, we provide information in multiple languages but we may not have translators on board for all the like six, seven languages that we'll be supplying. So, we had to have the corporate branded information to the passengers with the flexibility of changing schedules and changing events and everything to provide us a system that is flexible enough to give the passengers the right information. So, yeah, if we go to the next slide. Yeah, I think if you could once more. Well, yeah, go ahead, Henry. We can go through it all. So, the way we have it set up is each ship is running its own instance of Drupal as well as a shoreside version in California and the shoreside version is actually the system of record. So, it contains all the information that needs to be served out to the passengers but also the code base has to go out to each of the ships as well. So, that shoreside server replicates information to all the ships throughout the world over a satellite connection which is really limited bandwidth on our ship. And like I said, it serves both the passenger but also the business. So, it's feeding things like the kiosks, the flinage on board the ship pattern. So, it's really important that we maintain that connection between them. Do you mind if I ask real quick, is the content actually being produced at the ship level or is it being produced back home in California and then shipped out to the... It's actually both. So, yeah, we have some information is created from shoreside corporate and then other information is created by the different crew members on board. So, they're gonna be entering perhaps event data or event changes if they have to skip a port. So, things like that, the crew members need to be updating on board the ship. Excellent. I also love this representation of Drupal taking over the world. I'm just gonna say. We have been reusing this info for many presentations. People love it. We like it here. Yeah, I love it. I like seeing them floating around with Drupal Conf. Yeah. So, tell me a little bit about how this is empowering your customer engagement. So, yeah, I think it's a good transition into kind of where the thing we wanted to highlight today which is kind of, we talk about technology and we talk about Drupal and we talk about how we deploy content and all that stuff. But in the end, our customer and our guests on board, that's really the important thing. The technology is there to enable all of that kind of stuff to enable them to have a great vacation, to enable our crew members to provide the information to the customer at the right time so that they can make informed choices about what they wanna do in their leisure time and then also to provide that good guest experience on board. So, we think about all this stuff. There were some key things that we could improve, essentially. So, one of the key performance metrics that the ship has is the onboard evaluation survey. It's something that is sent out to every guest via email at the end of the voyage. It allows them to give pretty candid direct feedback on how the ship operations were, what they thought of different offerings we had on board, different ports, that kind of stuff. But we did have a challenge and that really is, was centered around kind of our role in Asia and that was because a lot of our guests are booking via charter companies. They're really, we didn't have direct access to them like we might have with somebody who's doing a direct booking with us here in North America. So, we had to rely on paper forms really and trying to get the guests to fill out this paper form while they were still on board or try to get it distributed through the charter company, et cetera. We didn't have email addresses to send the stuff out to and get them to fill it back in. So, you can imagine with this benefits to this, we get a lot of data, but there's big drawbacks with paper forms. You might want to move to the next slide. Yeah, and one of the challenges that we have with a paper form is that we're not just serving English language speakers as our customers, that it is a worldwide operation with bases of operation in different areas of the world. During the summer times, we may be in the Mediterranean focusing on a more European-centric passenger and different times of the year we will be operating in Alaska, which is mainly North American passengers. Other times we'll be focusing on having certain ships in Asia so we'll be really trying to give that guest experience to native Japanese or Chinese language speakers. So, we run into a challenge there with a paper form that's English-based with a crew that is mainly English-based trying to get passengers to give us that kind of feedback that we need in a meaningful manner, which we've done. And I think it is an enormous amount of effort because you can collect paper, but you do end up collecting a lot of paper. And since it is an analog thing, you not only have to collect that paper, you have to code it, you have to key it into the data warehouse, then you have in order to even do some meaningful analysis of that data. And one of the things we found, I think that's kind of like the life cycle of one of these, from a guest filling out our survey to it getting translated to it coming back to the office, to it getting keyed into our warehouse, to it going back to the ship was about three weeks. And it's a tremendous amount of time for to be able to pivot and make positive impact on the guest experience. We may have, there may be an issue that's happening on board that we wanna correct, but we may not know about it for almost a month and we may have repeated that same issue over and over and over again before we were able to correct it. So in a period where we are doing instant customer recovery and service, so Twitter and other mediums, our business, even though it's heavily dependent on customer service and meaningful experience for the passenger, we have lost our, or probably might have lost our chance to recover a customer with this entire process of taking three weeks to get information of the how the customer sentiment was while they are doing the cruise. So this has been a major business challenge to give a customer service that people expect these days. So that's where we have to create some, better creative solutions. That's what he makes the most of it. Yeah. And that's where we thought, well, we have this dynamic digital platform on board all the ships already. How can we leverage this? That has multilingual, that feeds all these different environments that has a connection, short side to Lingotech that we use mainly for human translations, but also has a powerful machine translation workflow. What can we do to leverage this? On the first step, it was creating an electronic version of this form that we could deliver, that didn't require emails, that didn't require paper, that allowed somebody to have more decent amount of time on board. So we looked at a lot of different community-driven modules for this. There's a ton of great stuff out there, unfortunately for us, for our particular use case. And what we needed to do with this form, we had to kind of build out something ourselves. That could allow us to allow our short side content managers to maintain their own question bank to publish that question bank with multiple different kinds of questions. Sounds very similar to web form or those kind of things, but unfortunately web form has some limitations around translation and that kind of stuff that just wasn't gonna quite work for us. But it's kind of key when you look at the slides. So we have some generic stuff that is like checkbox kind of options. Have you sailed with any of these brands before? We have the ability to do radio kind of check boxes that'd be able to rate from zero to 10, which is mimics what we do with our email-based Qualtrics survey system that also allows us to dynamically generate questions. So this particular one, how much did you and Joy visiting each destination? It's basically just the generic question that looks in the principle of C to see what the itinerary is and then allows us to say, okay, we know we are in Tokyo, Besson, Kobe, so let's collect the- Yeah, and the next step is also more personalized questions. Like, okay, you have taken the short excursions. What do you think about that short excursion? So it's highly dynamic how we are thinking about it. And personalized to the customer. So this is Calvin. So you guys are actually creating dynamic surveys based on the actual trip and content. And is that something you guys have to go in and customize or does that just happen automatically? It looks like it happens automatically, but- Yeah, so there is a little upfront work in defining that kind of a question, but yeah, once that question is defined, then yeah, then it just happens dynamically. As long as that question exists in that particular evaluation for that particular voyage, for that particular ship even, then it'll show up and automatically populate. Very neat. And we also have open text fields where they can share more information. So irrespective of having regular check boxes or radio buttons, we also have full feedback they can type in in their native language. So if we go to the next slide. Sure thing, we also have a couple of questions that are coming in. One of them was asking about the theme. Did you base it on an existing theme? It looks like it's being delivered over web. So is it a headless approach or is it a more traditional Drupal theme approach? So right now it is a traditional Drupal theme approach. We are moving in the headless route, which we don't have a huge, so we're doing APIs and headless for ourselves more than anything for our own sanity, but it's working perfectly fine the way it is. So we don't have like a huge rush or a need to drive out a headless Drupal implementation. But we do have services going out to other platforms. If you have seen the earlier slides, we talked about digital signages and video and demand systems, which actually get data from our APIs. Moreover, we also have some places where we use high build approach. So we use Drupal to render the shell and then the data inside gets rendered by a headless route and a front end rendering mechanism has been done. It also happens while we interact with other systems like our billing system on board, we don't process the data that's been provided but it's rendered on the front end from the APIs on those systems. So it's like a hybrid approach. We use Drupal rendering, we use front end headless approach too within the Drupal shell. And we are moving towards a headless route too. Yeah, I think these particular pages are all kind of an API driven form. The rest of the site uses views quite heavily. So we're a big fan of views, we're very happy when that's in D8 and all that kind of stuff. So you see here, this is like another, this is basically the Japanese version of that same form. These first couple slides are the first couple screens here you'll see are the Japanese side and the next couple are the simplified Chinese side. And this was a key feature for us was, it's easy, there's no translation involved when it's a 0-3-10 score, but it's these particular open text fields that were the important ones to us. So right now what we're looking at is that kind of one way outbound translation workflow where content is generated, shore side automatically uploaded into LingoTech. There's workflows in there for each language separate from Drupal. One of the things we really liked about the LingoTech implementation was, for us Drupal's multilingual stuff, it makes sense, you know, entity translation, string translation, well, it makes sense maybe being generous. It makes sense once you understand it, but it is so... It's a little bit of a minor, yeah. Yeah, yeah, so we wanted to turn this over completely to the business, so we really, that way we were from the get go looking at translation management systems and talking with LingoTech and their integration that they had already for Drupal, it made the most sense that we could allow people to translate content without ever having to actually learn the idiosyncrasies of Drupal's translation management side. So we want to take the translation out of Drupal and also we might have translators from all over the world who may not know how to access the system or may not even have access to Drupal, so we wanted to take that content outside of Drupal, push it to LingoTech and have a separate workflow within LingoTech and then once the workflow is completed, we'll bring the data back to our show set application and then get replicated to the ship. We have some more data and visuals of how it happens, but one thing before we move from this slide, this survey module that we have done, as Nate has mentioned, is a question bank. We had a custom create a question bank, the reason being reusability. So once the question is created, that can be used in a traditional survey like this or ad hoc surveys. So as I was saying, if the passenger has taken a specific shore excursion, we can do ad hoc surveys once they're back from the shore excursions out there. They had a dining experience and we can do ad hoc surveys. So it's a question bank which brings in data from different touch points in different ways and then brings it all together into one place. So the question can be reused in multiple ways. That's why we had to do something custom and we couldn't use anything that's available in the community. And that actually works pretty well now. And I think we should go forward to how the workflow happens overall between Princess at sea and Lingo Tech. And what do you mean? So this will probably require a lot of clicking. So I'm sorry, I apologize for all our animations we put in here. A little complicated. No worries, I'm learning it on the fly. It's all good. You can just do it while you're gone. Cool. So kind of like we had said, we just really want to make this kind of clear so it's clear how the data kind of all flows, whether it be data that's being driven automatically or is it something that a person is actually inputting. So it kind of starts with the two systems that we have here, shore side that are managing content, both are Princess at sea that lives internally and Lingo Tech, our shore side of bins will add content and in this case, specifically those questions into the question bank, which automatically goes out to Lingo Tech and there's a workflow around that where it gets translated then automatically comes back into our Princess at sea. And at that point, it then starts populating out to the ships over our satellite connection. So one of the unique things about the way we set it up was that questions and any content really can target specific ships or multiple ships. So in this case, ship A and ship B are getting the content distributed out to it. When the survey goes live, then our cruise guests can start entering in their data. So at this point, it's all one way out to the ships for that kind of global population usage. So they'll start entering all their data and all that stuff. And now this is where we now have to start doing the interesting stuff. It's easy for us to look at a numeric value when we roll this data up back shore side, which we do. All the survey questions come back shore side, go into our master repository here and so on. But it's this one that was the tricky part. We wanted to get feedback from our guests in their own voice because there may be specific things in there or little bits of things in there that we might pick up on and that will help us with service recovery and the experience recovery. So the guests will enter in their feedback into that form. I think there should be an animation on the guest on the next slide. All right. And then it all starts replicating back via the satellite to our shore side library. Now this is where we go from a human translation to a machine translation. So Linglitech automatically machine translates it, repopulates that content back into our shore side library. It then gets sent automatically into our data warehouse exactly like our Qualtrics system does. And one important note there, everything else in this flow is JSON based REST communication. The data warehouse in parentheses use XML because that's what Qualtrics uses and we wanted to just leverage what that was already doing. So I just note that because it's one of the neat things about services in Drupal is that it's very, very easy to switch from one format to the other, you know? You can have essentially both endpoints working at the same time and just about in the installation which is really powerful because it gives you a lot of legacy compatibility if you're dealing with systems of maybe older technologies at play. Yeah, absolutely, absolutely. So clicking further, you have a lot of clicks in there. So now we've got it machine translated into languages. Now the nice thing too is we've got it in Linglitech so to say there is something, something the machine may not get quite right but it's a comment that we want to really look at. We can go back in and a human can post translate it and then it'll update all these systems as well. So once it gets back shore side then it redistributes this machine translated content back into the ships, into the original questions. So the original language stays the same but we've got the entity translations for all the different stuff that particularly English that may be needed which then gives us a pretty interesting opportunity. It gets back to the ships and then I think if you go for one more, you know, that's the cool thing. So this process takes about 15 minutes, 30 minutes maybe max, it's all more dependent upon the latency and the speed of the connection more than the Linglitech translation or Drupal doing anything. So once it's back, so we went from three weeks now to 15 minutes of a machine translation of comments from the system. This is a dashboard that the ships customer service directors and people in that department can look at. This one's got every language enabled because it just will automatically translate everything to everything else but maintain the original language. But what we're really looking at is the English. You do see here it is a machine doing the translation so it's not always gonna get the translation perfect. It leverages either Microsoft or Google translate here but uses the same connection to Linglitech system as we had before. So there really was no new work needed other than creating a new project on the Linglitech side. I love it because what you've got is that instant feedback if something doesn't make sense they can just request actual manual translation and go through the process there. So you're getting the best of the both worlds you're getting the speed of machine and then a follow up with that manual to get the accuracy. That's really powerful. Yeah absolutely and that's really for us like the key thing is now we've gone down to 15 minutes. We have a dashboard on the server. It's getting into our data warehouse faster than ever. So it allows now if you go to the next slide just to kind of, it allows our customer service people on the ship to see this stuff if there is some kind of issue where we are have an opportunity to elevate the guest experience they can reach out to that particular guest directly immediately rather than waiting for a comment card and one of our international hosts or somebody to translate it and it just happens. And then you can immediately assuage the issue with a pina colada, which is what I'm seeing in this slide. Exactly, they have good information that they didn't have ever to serve as a customer and have a better experience for the customer a better location experience for the customer. And that's the key for Princess business too. So that the customers have the maximum cruise experience and the destination experience through Princess. And I think we frequently hear the statistic that it's at least five times or more even costly to acquire new customers instead of retaining our existing customers. So this system definitely helps us fix any issues and try and keep that customer expectation right where it should be. Excellent. Great story. So just to kind of wrap up, definitely dramatically reduce the survey time. I mean, you just can't compare three weeks to 30 minutes, gives us that opportunity for increased engagement. I mean, that to me is one of the key things. Like what all this technology stuff really should be doing is allowing more and more human interaction on board that wasn't possible before. And by that, we can personalize that the customer service experience for our guests. And it becomes very like transparent that their comments are being heard that the ship is acting on them that they're, we wanna provide the best vacation experience that they can have and the best value for their spend. You know, really. Absolutely. It's again, the customer experience that you come to expect in a show site environment, you know, a famous story of somebody getting a problem with their food order actually tweeted and the manager comes before the food arrived because they are tracking to Twitter and had a better customer service. You cannot imagine that in a ship environment somewhere, you know, somewhere on the sea. We're trying to provide that level of customer service that you come to expect on a shore in a ship cruise ship. That's what you're trying to do. That's all right. And, you know, kind of the final thing was like Sabud touched on earlier, it's giving us new opportunities and new ways of thinking about, you know, how we gather this kind of information. It's paper forms work, but they are kind of dry and boring and there's a lot of effort in order to get this out. And there's now, we now have a platform where we can do a lot more interesting things and interesting ways of getting feedback and acting on feedback and increasing our transparency to our guests too, you know. Well, one question that just came through was, you know, you have the content going back, getting translated, coming back to the ships. Does the ships have an opportunity to correct the translation there if you have someone on the ship who can basically provide a manual translation and pass it back? Or does that surely happen at shore side? Yeah, so we do allow our, the qualified translators on board, they do have access to Lingotech on the ship too, so they can go in correct translation. Because we do want to get it in there because there's a lot of stuff about a translation management system. I'm sure Calvin will talk a little bit about more, but you know, having that in the translation memory and a correct translation in there is key for the future. So when we are going to leverage that memory for other translated documents that a correct translation exists already and can be matched up with those strings. So the quality of translation gets refined as we go along and fix the translation because it goes back to the translation memory and then the translation gets better and better over a period of time. Excellent. Well, speaking of Calvin and kind of getting an overview of the systems there, good segue. Calvin, tell us a little bit more about how Lingotech plays into this and some of the services you offer. Yeah, I appreciate that. I thank you, Hilary and Nate and Sabu for the explanation and I have to give these folks kudos. This is an absolute killer way of implementing this and it's very creative. Not only do they have onboard folks that can do translations, they centralize all of their content. It gets reused, repurposed, pushed out. And as you can see, this is happening all near real time, which is just amazing. We're really happy to be a part of this. It's been a fun journey for us to see, they then push the limits and the bounds on this, not only from just Drupal, but just in how you push content in general around, to different services and servers and it's just really fun. But just to give you a really brief overview of Lingotech, we are the first cloud-based translation management system, as Nate mentioned, and translation management system really is a project management workflow tool that allows you to translate content from a variety of different sources, whether it's Drupal or Save and Word docs or a variety of different applications. We do support dozens of applications on top of Drupal, which helps in a lot of organizations because a lot of organizations will have different marketing automation tools or knowledge bases or Drupal as a website. We are very proud of the fact that we have a 96% customer retention rate. I think it goes to the fact that we do deal with really great folks like Princess Cruises and kind of their vision and helping them out and providing a solution as opposed to just being a provider. And one thing that they didn't mention is we do have a network of professional translators and we sometimes tap into that for folks like Princess Cruises and in some cases they have their own folks do the translations and the translation management system allows you to pick workflows based on the content type or where the content's coming from. So in some cases it might be machine translated and in some cases it might be human translated. It might be our translators, as Lingotek where it might be their translators as an in-country marketing manager or someone that's on staff. So the system's highly flexible in that regard. So it's fun to see them push the limits and the bounds on this. We do have an open API that allows you to connect to different systems. So if you have a state of something that needs to be translated that's not Drupal or something else, we can easily kind of hook into that. Just next slide. As you know, all of our customers are global organizations such as Princess Cruises and you can see they're supporting, I think six, seven and possibly up to 10 languages and you can go to the next slide. And all of these folks have a significant amount of content that needs to be translated. So the question is, next slide, how do you get these dozens of different content authors to help translate all of this content? And in this particular regard, these guys are really stretching the bounds on this because they literally have hundreds of people participating and contributing and looking at onboard folks, shore folks and whatnot. And all of that content is dynamic and is consistently changing, right? So how do you stay up to this? These guys are using a satellite to keep their data up to date on these different off-shore vessels and so that's pretty neat as well. And so next slide, they do need to have this content translated and kind of the old traditional translation method on the next slide and you can just hit go a couple of times and it just draws on here. The offline professional translation process just fails, right? You have to have an API driven system, you have to have a dev zone, you can't have manual blind obsolete wasteful, there's all this fragmented stuff. Having them have a central repository in their corporate offices allows them to distribute content globally across all of these different entities and ships and that makes it more cost efficient for them. You mentioned translation memories, we store all of the translations and if the translation comes up again, we don't have to retranslate it because we match it and we just show you the differences and go from there. So you go to the next slide, hit a couple of things. What happens is we enable continuous publishing of this and of course you have all these different content repositories across human resources, marketing, development, support and we have this API that can connect all of those pieces together into the translation network and the lingo tech and then when done push back to those folks. So next slide, just really quickly, Drupal and lingo tech, we're fully integrated into both D7 and 8. We saw that we have this enabled continuous translation of Drupal content. We can automate and run, trip this content into our TMS and you can see from any location across the globe and then it allows you to track and manage all of this content really easily. I just want to call out, I think it's great that you're already ahead of the curve with the D8 module, getting that out there quickly. It's awesome to see in our software vendors that help build out our ecosystem but they're kind of staying on top of that because especially since it's so API based and definitely has all this promise of even better web service capability built in, progressive decoupling and all the things that Dries has been talking about. Just love to see it, so thank you. Yeah, and we were, you know, I appreciate that, thank you very much. We were actually on release day one, we were out in fact, even some of the beta as we had a couple of clients that we were working with to get them on the D8 and the multilingual folks often ask because one of the main initiatives for Drupal 8 was multilingual and to make that a better experience. And D7, as everyone knows, has several modules that are dependencies that are outside of core that have to be installed and managed, all of that stuff in D8 has been moved into core as maintained as part of the core. We actually think it's better, it's made it easier for us to program and it makes more sense that it's often there. Gabor who's in charge of that from the D8 perspective has been a great leader on that and we appreciate him and all of the stuff that he's done to help drive that pieces of that. And so we're actually really excited about D8 because it does make our stuff work better and it's a little easier to manage and maintain it will be for the end users. I'm one of the things too I also like to point out, we deal with a lot of different content management systems and Drupal 7 and 8 are one of the best multi-lingual capable content management systems out there. Simply from the support I know people will say, well D7 has all these modules that are dependent on it even still it's a much better system than a lot of other systems. Just at a high level I think, if you're deciding to go with multi-lingual and looking for a content management system Drupals are very good, if not one of the best or better content management systems to be out there because of the fact that there's such a focus on that in the core and in the community itself. Just a few steps from our side, we feel really proud of this, launching your module on Drupal.org and you have one download and then you have two downloads and to get a couple of years into this have 52,000 downloads. We're really proud of the fact that we do have a lot of communities running this. We do offer a free version of this that has some limited functionality but people can certainly get it and try it. If you're running a multi-lingual site I would certainly install using our stuff because it automatically in D7 installs all of the dependencies. We do have some interesting ads where we do five EPA calls per second which we feel is quite a bit. We're starting to, as you start to get into that it starts to show the growth of that. We have over 60,000 users on our site on our translation management system and we support 20,000 translation memory vaults which is all of this previously translated content and that's the cost savings that people have when they can reuse those memories and all of that kind of stuff. Again, we're fully supported on eight and that was been from the initial release day. So super happy to be part of the Drupal.org and Drupal organization association and had a really good time at DrupalCon last week and it was fun to catch up with Princess Cruises and other folks and really happy about the webinar today so we appreciate it. I find, well, thank you so much. This has been, one, it's a powerful story. As you said, it's a case study that really highlights the best of Drupal. I don't think anyone in the Drupal community has any doubt that the number of sites that need this kind of translation, localization, web service based, central hub repository model, that's just gonna increase as there's more and more companies that are really pushing into these global markets and doing these amazing things and I wanna thank you all for your time and pulling this together and putting it out there. You know, we're getting pretty close to time here but I just wanna give a quick second if there are any questions that people wanna pop up in the Q and A, I'm happy to pass those along. I see one and actually I feel a little bit hesitant asking this one but it's about price tag. For a project this big, what sort of budget should you set aside or is that something you're willing to share? It's, well, it's a hard question even for us to answer, not for any other reason other than we are internally, we're an internal development team at Princess. So there was no, apart from Lingotech and that stuff, all the Drupal development, front end development, all that stuff took place internally. So even if I gave a number, it wouldn't really match. I don't think what an open market cost would be. In Moro, it's a product that we are building. It's not an application that we are building, it's an entire platform. So it's a lot more than building a Drupal website. So I wouldn't think of the number that we even come up with will even closely match building a website of Drupal. You can continue some improvements and really rolling out features continuously going, I'm assuming some sort of agile process where you're going through sprints and user stories and really focusing on the user. Yeah, yeah, that's fine. Yeah, and Hillary's much more involved in this than we are in some ways, but we released the ships right now once a week. We're gonna probably move to twice a week. Hopefully we can get to daily, that's where we wanna be. So it is continuous iteration. We started on the project almost four years ago from the Giga. We were involved from collecting all the business requirements, getting the user stories all together, doing the first iteration of wire frames through the design, through the creation of it, through actually going to the shipyard and doing the physical deployment of it. Cebu and I between the two of us have been probably on 16 ships doing the rollout and training of this. So we're very hands on and involved in the whole thing from end to end. So yeah, it's like Cebu said, it's hard to, it becomes a challenge to kind of put a project cost on that in a traditional sense. So because we were complaining about my hand with while developing again, if you were developing from the ships, like that or a satellite connection that actually works, but yeah. Yeah, definitely. It can be an adventure, hopefully that. So it's like a concept to completion. We actually do training onboard the ships too. So we go to the ship, deploy, train crew members. We have trained like 800, 900 crew members in big theater. So as a team, we do everything end to end from concept to not to delivering and getting feedback directly from customers. So that says that the range is kind of different or the way we work is kind of different from a traditional project team. Awesome, such a great story. Well, just one last quick reminder. Again, Drupal Khan Dublin, I hope you guys submit this to Drupal Khan Dublin. Surely you have a ship nearby that you could use to get there. Good idea. I like it. I would love to hear the story told again. And also a quick reminder about Global Training Days, which is the next opportunity to engage with the Drupal Association. Again, thank you everyone. This has been an excellent webcast. I'm sure there's gonna get a ton of usage out of it and it's telling such an amazing story. So thank you. Thank you everybody. Thank you for the opportunity. Thank you.