 All right everyone just let's get started First of all, thank you very much for for coming and welcome to the first session of the Drupal showcase track What we What we wanted to do today is to present About this case that we built last year for Lush Japan And we're very excited. I was just telling Greg the track chair We got very excited when we got approved to talk about the session I hope you guys are very excited to to be here today. I think the Drupal that the keynote was awesome And I really uh, just a quick question or just quick poll. Who is the first time Drupal com or All right, cool. And who is um evaluating Drupal or Trying to start starting Drupal now or Okay, good. All right guys. So, um, we're gonna do a little bit of a both of us talking here So I'm gonna mix a bit Um And we probably will finish not Like it's gonna be quite fast. I think so you're gonna have enough lots of time for us to discuss and have some questions about the this case So uh today the story it's more like a segue story So if you just If you just google around you're gonna see that there is a lush story lush uk story about using Drupal ready So we're not gonna talk too much about that because it was the first story But the focus like I said is talking about the lush japan adoption of Drupal on their commerce platform Excuse me and um I think this story is really how Four interesting elements Got together how we mix them together and make it work not not only us here But all the agencies involved and lush itself and the first one is a global retail organization lush Let me do this Second one is uh putting a e-commerce digital strategy. So that's another challenge here Drupal using Drupal for that And the last challenge is japan. Is there anyone from japan here? Okay, good so, uh I'm gonna talk a little bit about that and you guys can help me out the case or confirm what I'm gonna say um So before we we continue A little bit of an introduction about myself Philip Rubin. I'm head of operations for cint in Asia pacific I've been working with Drupal for the past six almost seven years now I'm brazilian. Maybe we got that by with the accent. Um I lived here in west for a few years as well before moving to australia Now i'm in sydney so i'm traveling around and you may meet me or find me in tokyo or shunhai every other month as well so i'm a bit flying over all the time and uh And I think I just saw in the keynote and that remind me of my own story. So I'm one of the lucky people Or or proud I guess that had Drupal changing in my life. I think I remember About seven years ago when my boss called me on a sunday. Say look, there's a there's a there's a customer in us They want to use Drupal I was like, use what? And uh, you know what they need someone there in new jersey next week Can you go there you speak english? enough Well, we're kind of well to go there. Let's let's let's tackle that. We need someone there on site. Can you all right? Let's do it. I never come back to brazil. I met my wife at a baby in us Had a family. Uh, so Drupal changed my life. So since them I never did anything else different than Drupal Very happy to to be part of this community as well So I was was good to see Drupal like Drupal Dries Keynote and and remember my story too. So I hope you guys also We'll have some similar stories Um and have a right Okay, thank you, Philippe Uh, hi everybody. Good morning Uh, I'm ever right Uh, I'm a chinese a part of uh, cnt china t cnt Yeah Uh, my english name ever right Just translate from my chinese name Yong doi Yong means ever and the doi means right So just translate my from my chinese name. So Uh, some new New friends often ask me You are ever right never long I just told him yes. I'm ever right Ever right is me Okay, so uh, since they can quickly to remember me With uh, based on name I hope uh, I also hope hope here And this is my first time Ever a jubal call here fairly extended to be here today and Be able to share this story Also, this is my first time in us And during the Flight of the asian play asia airlines my wife Keep asked me Did you understand what is a broadcast speaking? I I told him Sorry my my darling. I Just understand the ladies and the gentlemen's and also smitha So he he said so Now we can eat on the plane So how to do after landed? And she said I think we will be dialling, uh, officer Staffel corn Staffel shins But I just can smile and think in my heart Baby, I I think we can we we have bling some noodles from China, I think so Today is a third day We come here and a little on Sunday Me and my wife still felt good here and she can uh, she has Drinking the starbucks coffee which she liked every day and also he Uh got a lot of shopping baggers from the alt letters yesterday without me so and she wanted to To go to a big list of outlets of the outside of the city so Guys don't tell he don't tell her how to go to I just needed to limit my credit card Thank you Thanks a lot and uh just last night he was asking me for some help on Chinese restaurants If anyone knows to help him was like I couldn't didn't have breakfast or anything Say look, I don't live here, but let's find something. Let's ask everyone later Thanks. All right, um Guys we're gonna go ahead with the introductions here at cint the company that we work for so both of us work together So ever write a Drupal developer my head of operations or work together At cint it's a global company focused on enterprise. So we we do most deployments of Drupal Looking large-scale end-to-end. So we start with the agency strategy All the way to all the services involved in Drupal We are relatively big. I think so 2000 employees now most of them in brazil Uh, so that's that that map is important not only to advertise cint, but To tell you guys how we did for this project how we worked for this particular project So the company's brazilian started 20 years ago. Most of people are there about 1800. We have plenty of offices here in us Including here in los angeles area I live in sydney Ever writes in china shanghai and we have our folks in japan. Unfortunately, I couldn't bring my japanese colleagues to to speak today But uh, but that's how we are distributed across the globe in terms of Drupal We have about 300 Drupal talents. So that's how we managed to to deploy and develop all those Focus on the large enterprise All right, enough about us. Let's talk about lush So lush it's a uk headquarter company. I'm just gonna briefly maybe it's better if I ask who doesn't know lush okay, so Good I brought this. Uh, so it's a uk headquarter company. It's uh, they basically produce fresh Handmade cosmetics. So we look at soaps or different type of products for cosmetics and um And they're basically okay, but they are global now. They are in about 80 countries 50 countries 800 stores You know those countries including us here It's it's awesome. I was just talking to uh, where is she? Uh, how I found out about lush either your girlfriend or or yourself if you like and then you're just passed by the store And that's how what happened to me like it smelled really good Let me find out and then you remember lush and then you buy something to to your to your person and then um and then I think what is interesting about lush compared to other cosmetic companies not only fresh handmade But it's also their philosophy and their values So basically the first thing they don't do animal testing. So they basically count on on people to volunteer for that They try to work as much as they can in terms of sustainability for the packaging So for example buy go buy a soap is not going to have any wrapping or any package Just grab that soap and that's going to take it and all the other type of packaging is trying to be a more like recyclable or post recycle material So when we started working for them, it's kind of a another motivation to work for a company with such values with with that mission And also on the other hand if you're like if you're a Drupal developer or a Drupal agency And you don't have many many work. You can also get some money volunteering to do the testing as well So that's lush. Of course, they have a branch in uk in japan. Sorry and Like I said, this story is a segue to the uk one But the vision started in the headquarters in uk and they put together this strategy as most of the companies the global companies, right So very shortly or very quick the story about lush uk About me 2013 They started so the the ceo everyone the company the marketing department They decided that they needed to bring the store experience online Was that me like I said, if you haven't gone to a lush store Try to find out later. Try to go to one of the stores around here And you you understand better what i'm talking about But the experience of what you see the colors everything and of course they smell it's a bit hard to bring it online, but But the whole colorful experience And knowing about the ingredients everything the whole interaction that you have with the products when you go to the store So they had this vision that they want to bring that online Because the online selling was not even closer to the the brick and mortar cell Numbers as well. So they wanted to bring that experience online, but not only uk globally Uh, so they brought uh, they involved a few agencies in europe. I think commerce guys Acura iKos those are the companies that I that I worked for for this So they they were engaged probably there there were other companies. I'm forgetting here They were engaged. They they helped them to choose Drupal at the time And they helped them build this what i'm calling a platform But basically it's the code base where the vision that will be the most features that all the countries will need Plus the most important part is the look and feel the design How this user experience is going to be this global experience that we want So they put that together and uh in q1 May 2014. Yeah about a year ago. They launched the new lush uk And um, you guys go online later But uh, that's what i'm talking about when uh, when we talk when we talk bring it experience online So if you go to a store, that's what you see and uh, you see nice pictures online, right? And uh back to the title of the session and and you keep seeing that more and more on the marketing trends This whole e-commerce and content getting together, right? So those that's one of the things we're going to be discussing here today But uh, that's that's how you bring it bringing more or bigger imagery better imagery to your website videos Uh blog Specifically for lush about the ingredients information about the ingredients very important on their business to talk about what is that? Soap made of so they don't use palm oil for example, right? So they use more I think all the products are 100 vegetarian. So there's no animal at all animal by product involved excuse me So uh having that information connected to the commerce. So that's the content and commerce getting together So if you search around the product you want to know more about it Eventually you buy as you have more information about it. So that's the whole experience that they brought together Uh, interesting enough there was a another great idea. I think That they brought into this new version or this new experience, which is what they called lush's kitchen Basically they produce daily Different products and they put a different menu every day almost like a restaurant with a chef and uh Once they sell out they're done. That's it Uh, but the good thing is apart from that having custom experience or personalized We're going to get one of the soaps that maybe nobody else has Uh, that serves as a lab At some point if somebody ordered that well, that was a huge success Let's put that product back into the the mainstream product, right? So, uh, that's very exciting to to see that happening also happening in japan And of course if you think about it Changing content so connecting to Drupal right changing content every day approval workflow everything So you need a platform to do that as well So after okay, the decision was okay. We're stable enough I think we can start we think we can start going global right the first two counters were brazil Which were not involved Although we are brazilian But we're first involved in japan For this rollout um I think it's also important to say I think I said before but uh, they decided to use this platform approach So they got the code base they built lush uk They tried to make it generic as possible I have a right to talk a little bit about the the technical requirements or technical components But then here's the code in japan. Here's the code brazil. Here's the code korea So that's the idea and if you have something that needs to be Or it can be generic once you customize to japan, but can be more generic for the platform Let's organize the governance and bring it back to the main source code. That's one approach compared to Create a distribution which is similar, but that's another one or site Which is something that also we built for the customers where we basically put everyone under the same umbrella Including the hosting part of it But here there was autonomy And I forgot to mention the beginning one of the things if there's one word one thing that I want you guys Especially you guys that are evaluating drupal One of the things that the word that I want you guys to leave the session today is flexibility So starting with this that's that's what we're going to have in mind when it comes to drupal You have different approaches. You have different options And we're going to deep dive a little bit about this flexibility capability as well But that was the first so we're going to build something we're going to Improve your time to market by building this baseline And then you have some freedom to customize to your local needs And then from uk we go to japan Getting to japan where we were involved And then we understood their goals First of course implement the vision that was coming from lush, okay, so leverage the drupal platform from lush But also as usual with with any project especially commerce related launch with a very aggressive timeline By october so we were engaged around july By by october last year in time for the christmas sales so the christmas sales start in october So those are the major goals, but then let's go another level under that but at a high level those are the goals So we were involved and then we we say look, okay, we can do it But let's lay out all the challenge and how we're going to tackle them First one is to replace the existing platform. We'll talk more about it. But basically that was the the previous website When it comes to the content and commerce was way different from what they have now So that was the main reasons that we wanted to do it But more importantly was the technical part of the platform. It's uh, it's uh, it was an esp platform not dot net esp Active server based platform, uh, and it was very limited in terms of expanding or customizing Any change we need to have a lot of custom development Very difficult or we take a lot of time to To bring integration like we did new social media, for example. So that was one of the issues with the platform And also the platform was kind of one monolithic application meaning The front and the oms order management systems all the back office for the order management And also feature fund. We'll talk about that now. We're all together in the same unique esp application So that was the first challenge to replace that at to some point not replace the whole thing second one um That's microsoft Sorry about that. Um, keep feature funds working So that's uh, the layout of the feature phone the dumb phones right the flip flip out phones I don't know if you guys know, uh, my friends from japan. They do know but feature phone is still huge in japan um Yeah, I saw a report quite recently two months ago that actually Last year the feature phone sales or shipment was even bigger than the smartphones So they're still investing on improving the interface for those new Feature phones so they they still gotta keep that whoever has a business or a user base with that You still gotta keep that so we gotta we had to keep that for less too What we we've been seeing for some customers that are starting a new We're creating a presence in japan now They might not go but it's really a business decision strategy, but it's still huge And in japan, uh There's there's a lot lots of material about that It's not only a feature phone, but there's some characteristics about japan That even there's a described as a galapagos syndrome that things have been developed or have were developed inside japan That you can find anywhere else and I think feature phone fits into that category too So, uh, everyone going to japan market needs to be aware of of the reality there and plan for that So we need to keep that was not just coming. Okay. Let's forget about this. This is old. No This is important for this market. So we got to put this in the plan if we're going to replace something We're going to make sure that this is still working So second challenge Third one The diving a little bit. So the couple that asp application Because the idea is to keep the oms the same Again the management the back office management the back office operation team They still wanted to do the same way they do all the tasks for managing the product orders and everything All the users etc. So we they didn't want to go in the first round the first phase and change the whole platform right away They decided to do in a few steps or phases eventually. They're going to replace the whole thing But for this phase especially because of the time frame they wanted to keep The back office the same way. So we need to decouple that meaning let's ignore the desktop front end And bring Drupal top of it, but make sure that Drupal can talk to this oms asp back end So which is the second topic here and again, let's not touch the feature phone that you got to continue working the next one is Well, imagine that we're bringing Drupal with its own database, right? And and we already have a live database. We have a bunch of users much of products and data a million registered users So how we make sure that once you log in into Drupal You have your experience. You're not not going to have delays getting data from the other database SQL server So how we can synchronize the data how we can migrate to start with right and the site's still running even during the project We still need to make sure that we test the migration and then we do a freeze in the end Then we do the final migration, right? So that was another challenge to be considered on the plan There's also ux translation localization um The idea is to use the whole design coming from uk but I mean you're going to another country, right? So there will be phones. There will be small things that you've got to change Uh, we we did a bit of getting the content the existing content product information ingredients from The existing lush site in japan, but also getting from uk And it's not just translating as well. You've got to go and check. Okay. Can we say those words in the ingredients in japan? So it's different like so it's almost the same thing if we bring it to us So that ingredient is something that is correct in japan. So it's not just pure translation So the agency that we involved in japan also had to consider that and discuss with the business in japan And everybody will talk a bit about about that. I think um for solar We we so this platform is deployed on aqua And they use uh apache solar diversion is still 3.5 Right and uh the 3.5 doesn't support the japanese Characters am I seeing this right? Yes So um, so we had to do some customization is not perfect to allow that the 3.6 already supports that So there was also this challenge, which of course we didn't know when we started So those things that come up and I think it's good you guys to to remember once you engage on this On this journey Less not us yet Communication as you you would imagine So we have ever right here from china. So like well, why we have someone from china or brazil But as if you remember the map of cint we have the local team in japan, which I couldn't bring you here today But part of part of the team that implemented this was in china together with everite And I was supporting Traveling all the time and and helping from australia But the core team we had in japan lush of course cint And a vendor to work on the esp platform The oms and also creative agency to do the whole translation everything uk we still got to communicate with the headquarters and also the team that created the platform for the government's purpose And in china cint So how how we manage that like the english the japanese Everything involved in chinese right so it was another challenge something that we do all the time So it wasn't not a bit of a difficult for us, but for the customer is different right so we engage with the customer that hasn't done that before And the last one timeline I said that before so move quick So because they want to leverage the christmas right if we missed then now stop the project only next year now right very aggressive So with that said let's deep dive a bit on the architecture Thanks, philip So guys, did you remember my name? This is a Simple architecture overview of this project at at a high level The architecture Included following components So jubile common common small joe Is already exist in the uk platform And the finish and Finish and the mammoth catch is used for improved site performance fields and heavily use the fields with operation manager interface along with the media so Operation manager can easily manage their products orders in the main interface And Adjust field is used for a user to type their address and also we have custom size New feature so user can easily find their address by Japan postcode and So the sorry In the outer circle We have some third party service here And for the third party service the first one clown july clown july is a image clown service and support image transformations like image resizing clopping and face detect service and also behind a cdn with akamai And the same code Guys know the same code And the same code was comfort the video to support multiple device and In our case we comfort also video to support iphone and Mac or pc iPhone and as a android device so when converted we have Save back to clown the in with a low format file to to provide a cdn access And Apache solar You know apache solace up provide as a whole site indexing and the whole site searching service with jubo it's great And soap i am Is used for client communicate And a little time chat for the client service Google tech management Google terminal is In our project is used to manage multiple google analytics settings in Of the fish phone and the new jubo site in one place So google management can manage multiple google site Settings in one place is fairly easily Sorry very in that particular case they wanted to For the feature phone Your website they want to track one id in google analytics Then for the desktop and the the smart phone Another id right and they wanted to have the same report All the interface so google analytics by itself the the simple google analytics wouldn't provide you have to have a separate report interface But with tag manager you can associate different IDs And and and see one single report So that's I think my at least my was my first time using tag manager. Yes, but that's that would help them in that case Manage different IDs in the same reporting view Thank you Okay, next here is google map is based from the uk district and we just Locosize the map to japan and support large shoppers in japan Mail trump is used for newsletter Also, yesterday. I have got a mail trump monkey head from their bag Is this It's a good gift for us And Twitter facebooker will be shows Latest social social information information for the large shops And last last is the important. This is the important part of this architecture is integration with the oms and oms is the last old large old large site build with microsoft asp and circular server so for For this launch he They just want to keep the old check out and all the management in their oms back end office So so we need uh, we need to change create a data synchronization from jubo and oms oms database Yeah, you explain more the next slide, right? We're going to deep dive on that one. Yes next one. Yeah So just before right, uh, sorry, uh, yeah Especially look at this and uh We we came with a drupal code base from uk and we still added more components We customized a few we created new modules like address field in japan Which is specific for japan A few configurations as well. So I think that is a when I when we put this together was like, look, this is what drupal is about That's what I said about flexibility. So it's still coming with something that was pre-packed We still were able to to add things and like like I said in just a few months Be able to support all the requirements not to mention all the back office We're gonna talk about so again flexibility. I think that's the thing that we can see on this slide too Okay, thanks. Philip. Sorry for my bad english So as we said Uh, so one of the challenge and the key features of this project is Uh, the texture's existing ASSP Uh front end From the oms Backstop, uh, so we just we needed to replacing the front end with jubo And so Also, so there is we have sorry Told the fish foam And the fish foam say just one uh, we wouldn't have to touch this is a fish foam Say keep it and remain the features with the fish foam So so sorry So the complex involved is the data migration of All the site to jubo such as migrations users products orders into jubo the next is uh data synchronized between the jubo and the oms when the use When the manager in jubo at the main interface say updates their product Informations or New user registered on jubo site or user updates their profile In jubo site, it will out synchronized to ASP database Okay, so next is so for the Data synchronization We just needed to create a web service to provide an api to Communicate with the jubo and the oms which For jubo site we use the service module is fairly easy to create an api so for the oms site the Oms oms aspt Provide the api but We but uh, we can load some coders Tell the guy how to connect to the jubo web service Use the oms and the rest for okay, so uh and for Say section say In the oms oms spec and so say just wanted to keep the payment and So check out in the in the other side. So we needed when the user in jubo site We blow the product and edit the card Then they kick check out on jubo site It will out post the date to the ASP side with the user cookies so the Oms can read the user's card from jubo then finishes following checkout And the benefit of the architecture is minimizes operation of the Backoff operation user and minimizes the complex pc i because the pc i is also handled by Oms side and For the data migration I had to share information with We just used my circle csv load Before we have tried to use jubo's Migrate module to import the users and the products but for For the one million users and to import is fairly slowly. So we have tried to use my circle csv Load import from csv file is very quickly and Finish all Data import cost one hour, but I think For the migrate module may be more than one hour or more hours And we just use the split write a sum splitter to transfer the data insert with the field field hookers structure to get the Field tables which used for Entity and Us tables Okay In this side, it adjusts the list A major features and modules added Into last japan Difference with uk plan form Service we have said For integration with oms Adjust field japanese postcode It is uh Customized with our team to support Adjust look up by japan postcode and also in japan Client want to manage To see their products Freshly after they update their profile in a product detail page or home page. So we use the x-ply and the aqua project module to auto x-ply so Finish cache in aqua cloud when the user updates their products But Another issue is the happen what happened is uh in some pages So, uh, it includes some blog data from Apache solar return So when it's a user update the product It will be check the solar to index, but during this index the data The page is auto x-ply So we have load X-ply arch module extra module based on based on x-ply module to support When So Apache solar index finish we created some page cache So the user can quickly to see our refresh product pages And net plus net plus is a Product limitation service in japan. So we have customized the code to integration with jubo and net plus So last currently we have told before she is It is a image cloud service and support the image transformations Behind the cdn service we also we can take more about this Okay, thanks. All right I think we started late, but I don't want to impact the next Session or lunch. So, uh, I'm gonna jump a bit ahead guys. We we did prepare I know maybe some of you guys will not go to the the website and check we did prepare the video I'll share later with uh, or just quickly how the site look. I think it's just a short video Um But that's that's the experience again because the the the session was about how effective This decision for lush was to bring this experience with commerce. So yeah, we thought about the background the The technical platform, but we drew full and be able to do all of that and those are the components that we use for some of the features So, uh, it's kind of an appetizing lush, but but also saying where we're using one of the components. How does that? In fact, actually what what is happening behind the scene? All right guys, so So that was the the the whole how it happened under the hood But in the end of the day, how was how was the result? How was the Christmas sale? Right? That's that's what they want. So in the end of the day, we launched the new lush japan.com Uh experience following the global strategy. So that was a success We brought the union of commerce and content again coming from this the same vision strategy And more importantly, if uh, if not as important is uh, it was reflected in the end of the year So compared to the previous year, there was a 50 percent increase on sales online So everything together, uh, actually brought financial results as well. So this is a just Giving a step that the work was was pretty good and and the platform and everything chosen was was a success And the platform and and there was all the demand coming So the whole combination of the hosting everything that was built all the decisions made Hold the platform as well for all the peak on the sales There's there's the sales in japan and then there's a couple days after they they can there's a there's a Some some product with a price off. So there's kind of two rounds of sales Near the the christmas time So that's just to compare lush uk lush japan. So again keeping the same experience Um, that's the the ingredients So you guys can look have a look at lush japan.com The back office was very important. I mean the beginning I myself I was a bit worried especially when it comes to Drupal Uh, it's not perfect when when you compare to some maybe other enterprise platforms Or especially when customers such as in japan, they're used to do their things on that way And how we're going to customize the back office In the past we often would just worry about end user experience You wouldn't worry so much about the the operation management experience So, uh, we we thanks to views thanks to a lot of things that were built on the platform base code in uk The the lush japan team was very happy with the back office interface They thought it was even better than of course the oms platform that they had so it was great awesome So in in japan My friends from japan can help me out here, but They they wanted to have very specific details each custom field. I want to search for that So, uh, from my experience working here in us and in brazil there you have more Uh more requirements. I wanted to have more flexibility. I wanted to have more there We're more details than what we found in lush So we had to customize that and thanks to Drupal wasn't that difficult It was just playing around with views and then updating one thing or the other configuring. So that was a good thing Um, another like in japan as well They want to even though we were supporting the platform for them. We managed the platform together with aqua But they wanted to have all the logs all the details Logged and I wanted to have this api log. I want to have everything So also we we easily could have that available for the team So to make sure everyone is engaged with the platform It's not something coming from the global the headquarters is something that you will be able to leverage and use right So it was important to get the buying from the local team right to have everything that they need So the takeaways just moving a bit quick guys So time to market was one of the key things So having this decision of a platform a code base built first Was definitely a good start for the pan We did we we did Go through some customization level as you guys saw um specific for japan, but I reckon if If we get the some a different market even even in brazil from my knowledge except for the whole tax in brazil, which is very complex, but Everything else probably will be faster So for smaller markets or for different markets having this platform called base decision Will therefore make things faster to hit the ground running for for those countries building investing on this platform at front But shipping the code and giving the flexibility so that was an important decision and drupal was fundamental for that technology choice so the flexibility as I keep saying all the time um the teams and the language so uh Communication i mean that's that's what we do we work with our chinese team japanese team our team in brazil so english So we use tools Different set of tools we can talk about that offline For to make sure that all communications is is working the project manager everything Uh and local presence. I mean in japan And uh and in china as well as we do business It's just without local press without someone that knows how to navigate there. It's just we can't it wouldn't be able to make it Uh and another challenge that we had that I think it was important to bring here That we planned but we didn't plan so so so good I think could be could have been better is for data cleansing so the site's live is from an old platform So every time we try a new round of migrating the data towards the uac phase It's just all there's something missing. Let's go back to the sequel server team. Well, let's do it again I guess all let's create a script to do data cleansing first Let's clean up the data then we start the whole round of validation of this data Right, so that's something to plan ahead look at the the platform investigate the scripts first the data first um So I ever write if you don't mind. I'm just gonna go ahead Running out of time Guys important things. I think that's something cint does and want to mention here. So as ever, I said Giving back So part of this project, uh We created this field ever write created this module address field specific for that just got promoted from sandbox So everyone can just go start using that Uh, we also created claudinaries already there sandbox Good Excuse me, uh, there's also code snippets snippets that we put it in github Okay, yeah, we put a video for that too, but uh, we're running out of time But uh, we can also get some code. So for example asp So if we're gonna ever do a project we're still gonna have to use an asp and authenticate against drupal You can use that code as well for for all. So that's what they do to send the data back to drupal in this this this project Another one that I think it's very important connects to my next to my next topic here Lush is not using this but we're doing this for another customer just right now in japan GMO payment is one of the biggest payment gateways in japan So they work with the so the other platforms that Grew in japan market for for cms and commerce They of course they use that and there wasn't there was just one module with uber cart version 6 for drupal and because of this project we're building right now for another customer We're finalizing this in In drupal 7 so we're going to be putting out there in june And and the expectation that we help evolve the uber cart one as well as create the one for drupal 8 And I'll mention why this is important in a in a few seconds or minutes Which is connected to this so we can finalize I think What I wanted to close the session with as I as I promised on the abstract of the Of the session is to give you guys a an overview of what's going on with drupal in that area So since we we are there we're working there and since we're here in LA I think it's good to have this overview of what's happening on the other side of the world In my experience so far so two years since I moved to australia working dedicated with china in japan I think there's a lot of potential so dris went over there to japan in china He wrote a couple blog posts. He had experience with us there He mentioned about translation one of the challenge But I think if we think about the potential for both markets japan in china And if you see how drupal is not there at all, it's not just small things. So there's a lot of potential So I wanted to leave this message with you guys here And we just need to tackle those challenges together Not only us not only cint, but also love to see more companies joining japan and china Because that's how we're going to build the ecosystem bring awareness as well But again think about the the potential in japan's market all the local CMS or even custom applications legacy see the asp. So there's a lot of potential there for drupal I think the first challenge that I wanted to bring here that we're working on and I think lush is the first thing lush japan is helping here But we wanted to do more is things that happen here us with the white house We see europe the governments australia the australia government So all those things help bring a flagship case Something big helps and we need to have that in china. We don't have that yet We need to have that in japan. We're building that up. But uh, that's that's one important It's kind of the egg and chicken flagship case will bring more developers And a business will go if there are enough developers as well, right? Translation I think the in terms of core and admin We are in a good in a good situation there with the translation team But again, like dris mentioned I I personally spoke to him last year We could still could do some work on sales and marketing assets So like in japan when we try to pitch drupal for different customers This is like look, I can't find anything about drupal in japanese. Sorry. I don't trust this platform So then we have to translate everything and then gets out of date So there's still some work and I have an answer but uh, we that would be some opportunities here there That would definitely make things move faster, especially in japan very technical very specialized teams um GMO payment as I said, I think As one of the biggest payment gateways and we expect that as soon as we launch that module that should trigger something in the ecosystem Look, it's a one less barrier for you not to use drupal because yes There's a module for that major payment gateway or union pay So in china if you didn't use visor most of the most accepted payment methods union pay, right? So I was pushing the guys to contribute to drupal 8 accelerate But then I said look, there's no union pay on the on the donation website So they couldn't say okay, I'll do it and then you pay me back somehow when I go there So there are specific things that we could focus on that market That is just one less barrier for the business to say no, I can't because you don't support this So we can think about other things. Now doesn't have to be commerce can be Post office or post service anything that would would be one less barrier to to just find not going to to drupal Talent pool we suffer that across the world Dries mentioned that a few times in the In there in his key notes, I think we're getting better around the world But it's still in china in japan if you look around chavin dot net traditionally And then you have a couple guys just in php HP is not so well seen yet. So we're building that we're especially in china We're building relationships with universities creating that ecosystem But that's something to keep an eye as well all the initiatives we have been doing across u.s. Europe And south america I think something we can leverage and start putting out there in the asian markets In parallel. Yeah In the community exists. There's there's not only variety. There's a couple more chinese guys here And from japan I'll definitely love to meet you guys and talk about that So dris went over there last year As was in japan. So japan is on the other side of china here. So that was jupo camsion high just in february We we did that together with the local team Uh, it's there. I think In terms of business definitely need more support. So cint is supporting both countries now, but we we have a lot more help But again the potential that they have especially china so big. So there's a community in shanghai in beijing Uh in south china But there's so much potential the language has a barrier But if companies start looking more into that, I think we can definitely build a better and bigger ecosystem Okay, I think we can show a demo about the contributing modules demo Okay, so uh Still have some time Yes, because that was the Guys what I showed is I think that's pretty much what we had to share today The lush case to talk a little bit about the state of the the community in japan and china Um, if you guys have any questions, I know we're running a bit late, but feel free to Just go to the mic or yeah Or we can also also talk. I think it's good because we can record that. Yeah, that'll be great Hello, okay. Hi. Um, just before I ask my question I just want to say that I was a developer in my japan myself and I know how difficult it can be to meet the requirements of Their needs and I think you guys did an amazing job doing that in only like 10 months. So that was great Thank you. Um, my question was um after you handed over the project to them and the website And did you have to offer some special training about how to use japan? Especially like managing the content and the products there was a whole phase in the project just for that So the last month was uat along with operation testing and training. Yes So, uh, so we had to paralyze that there was testing but also training the operation a whole month actually Did you find it difficult to train train them in druple? uh So like like I said, did they like interface but they they kept asking new things So that was the challenge. Okay. I like that. But please can you change this to add another field? So that was a bit challenge But uh, as far as druple now it was more about I want this field now. I want this type of search So that was the so back and forth then go back to the team do this go back. Yeah That's it. But uh, no not so much in the druple. Okay. Thank you. No worries. Thanks Hi, um, this is probably a little specific to the lush experience but I had a question about your integration with the an external checkout or fulfillment system and how it How and what challenges you faced? Running campaigns that flowed through multiple systems. So if you ran a an ad campaign On on one website which sent in traffic to the main lush site And then you also had the checkout the external checkout and fulfillment how you were able to Pull analytics so that you could see that 50 sales increase or attribute things to what ads and all that All right. So tag manager was a key part of it But uh, what was important in these architectures is everything was coming through druple for desktop smartphone After you create a shopping cart, then you get redirected to the OMS It seems seamless to the user because we can't change the interface, but it's a different system So the entry point for most of the usage is still druple from analytics campaigns standpoint only the checkout process But you're right at some point if you drop out in the checkout how you measure that So working with them sends them to improve the analytics and and to analyze that drop off when you get to the checkout Um, but we haven't I haven't many challenges. No not yet, but we're working on improving that experience. Yeah Thanks Thanks for your great presentation today. Thank you. It's been very helpful and I'm actually taking on a very similar project right now and I've never Uh worked on a Japanese translated site before I guess my employer thinks I need a new challenge And I'm sure they'll be watching this video and hearing me say that Um, my question is um, you know for each of your internationalized sites it and I'm just guessing here It looks like you guys did a separate Code base for each one. Is that correct? Yes. Um, and why is that? Why not? I mean I do one massive You know Drupal site for those translations. Are you viewing them as distinct audiences where they wouldn't be? You know English customer wouldn't be the same as a Japanese customer And you also mean like hosting all together in the same instance or not necessarily that necessarily I mean there's plenty of ways you could you know architect that Think there's uh, there was a decision of giving flexibility and avoiding back and forth in terms of the governance So I think the governance piece especially being on the other side of the world was a decision that let's take Look, let's give that freedom, but there's still some governance around. Okay. If you notice something that is more generic we can bring it back to the code base but um But they wanted to keep it because different teams will be building that wouldn't be the same I see UK team that started this So, um, if it was the same team would be like for CIT doing the whole thing, for example It would be easier to manage that I think So you add an extra level and you have four months to deliver So, um, but you're right. I think that would be Probably one one good decision that if you have time and have the teams to do our users on the uk site shared with the Japanese or their separate Okay, got you. Yeah. Well, thank you. No worries How are you? I'm in the middle of a big redesign with thousands of Articles and pieces of content and one of the big challenges of a redesign is losing your SEO ranking when you Change URLs and aliases and things like that. What was your approach to make sure that you kept, uh, You know took the minimal amount of hit with a redesign on that Do you I don't really feel I wasn't You mean SEO for the SEO we just import the old largest site To jubile site with a csv file. They have export the Exist URLs in the old OMS then give us so we have used The direct import module to import all the SEO so you kept the same path Yes Okay, thank you, right Exactly, that's really what we're looking at, but I just wanted to make sure that there's anything else that Yeah, because our site is a mess. It's a legacy site from 2006 and there's a lot of um You know file directory structure. We need to clean up and and stuff like that. So thank you You're welcome All right guys, I guess That's it. Uh, thank you very much for your time. Oh, we are out there in the Thank you. We're out there in the booth. We have a booth there. So if you want to stop by and have a chat Uh, I would love to hear more more case anything. Thank you