 Okay, so we're gonna start just for new arrivals. We are talking about Johnson and Johnson, this team. Okay, so why are we all talking about Johnson and Johnson? It's because we are working with this client since like about three years. So for those who doesn't know who is Johnson and Johnson, it's one of the biggest companies in the world. I think in the top 10, found it in 19th centuries and it's selling many kind of medical or healthcare goods. Just some figures, we got like, oops, so we got 65 billions of revenue, so it's quite big firm, 120,000 employees and 250 firms. And we have 1,000 websites running all around the world. Multilanguages is quite a simple websites, but there are a lot of them. And a lot of brands, it's quite a decentralized system, so each brand is quite independent. So there is no central IT, digital department, there is no even regional digital IT department. So the brand, individual brand are very strong. And so we face a problem there. So their problem was three, four years ago. They got like 100 vendors, about 50 different technology running websites. They got, of course, Drupal, but they have Joomla, .NET, Java, everything. And of course, because of all that mess, there was no standards. And the result of that is, the first thing is about the cost. Each project, you have like small website built in Russia, cost them 5,000 euros, but there are also some small website built in US, costing them $500,000 because of crazy idea of big agencies. And there are also so many security holes. They, for example, one day, if you was searching for a brand name, you was actually getting all the customers from the CRM system, emails, quality, performance, in case you're well, no standards, everything was not regular. So that's how it started with us. Guy just Googled us and find us on Google and sending me an email, like saying, guys, I need some Drupal help. And actually in France, I didn't knew that Johnson & Johnson, it's not famous brand. Nobody knows Johnson & Johnson. Everybody knows the brands. And I was saying like, I don't know what's Johnson & Johnson, I said to my partner, another guy called him, what is Johnson & Johnson, biggest company, please call me now and okay. So the needs was quite easy. We need one technology, they selected Drupal. And we also need distribution because we don't want, because all the websites of brands are quite similar, so we didn't want to reinvent the wheel each time. We need a centralized sources repository because we have so many vendors. Anybody, each vendor uses different source control or no source control at all. So we need like central way to see where all the sources are of all websites. Another thing that some of the websites were in flash, some of them had some mobile theme. Finally, we helped Johnson & Johnson in the email region to decide that all every single websites will be responsive design because they are quite simple. They are no need having a mobile theme. So we said, okay, you will do responsive design. Because it's a so big brand, there are hundreds of brands there, people are often contributors, marketing department are moving from one brand to another. So one day you are in need to generate, another way you're on OB, then you go to net, venue, and you're moving around. So each time you arrive at new technology, you will have a new back office or no back office or new contacts. So we decided to have a new one standard back office system for every single new website we are releasing. So people moving from one to another, they will not be shocked. Also, because we actually would like to build all the websites of Johnson & Johnson, we cannot. So we decided to audit every single website is released. So we have a lot of agency and vendors providing websites. So we ask them guys, if you provide websites for Johnson & Johnson, please first use Drupal. Here is a git centralized repository when you store your source code and you will be audited by somebody, Acway or Ajax, but anyway, you will be audited. And also what we noticed is there wasn't any process. Somebody will offer a tender and the agency will release some crash design and then we'll go live. Often they was working with some Indian company or big Capgemini, for example, working for them. There are more process, but a different one. So we set up quite one process that actually works from to create a website from zero within this organization. I didn't say that it's good process for everybody but within Johnson & Johnson, it was one. And finally, we need a centralized hosting platform because basically, performance security issues well are also not only related to the code of Drupal but also was related to the hosting company. So we helped them to set up this kind of platform to manage all those websites. So actually the first thing we've built is this kind of distributions installation profile actually with workflow, WeezyWeek, sitemap, CMS, see what I call CMS, it's actually admin team and then content types, standard content types, each brand have products, title, illustration, photos, whatever. We also had some articles about lifestyle sections or things like that. CEO, we finally grabbed not all the recommendation but all standard recommendation within this distribution. So we have like CEO footer, for example, you can change the footer links on each page not globally, small stuff like that. Social sharing, form, security, and we also set up Drupal. And then for each website, we have some custom features, very small of them, probably content types, things like that. And custom theme, of course, because all the websites are different. For the sources, we selected GitLab. We want, I know in the US, they are very GitHub oriented. It might be solution but the private GitHub will cost $25,000 minimum and you haven't, as much as control as you have on GitLab, it's smallest tool but it's easy to use. We also provided for all agencies working with Johnson & Johnson standard single branching model. So actually it's quite standard, not exactly standard like you will find on internet but actually they cannot commit to the production brand, production branch because of audit. So only somebody within Johnson & Johnson can commit on production branch after an audit. We've created a lot of responsive templates, also standard. So even if the look of the website is quite different for each brand, they are all based on the same 30 standard and reusable templates. Of course CSS will change, logo content will change but if the brand decides and have a low budget, they can reuse templates, standard templates. It works quite well, why change? So just an example, those two templates are exactly the same structure, even if they don't look exactly the same. The left is for Vania, the right is for Listerine. So the standard back office as I said previously, we have all these brands and people are moving around and you have also internal support in digital, all around counties. For each brand you have probably five, six, seven websites in different counties. For example Listerine, we have about 15 of them in Spain, Portugal, everywhere. So you have contributors all around the Europe and you probably need to find the same back office. So nothing extraordinary there, but just you have to keep clean up, simplify with your profile, not let them do anything else. How to deal with taxonomy specific layouts for taxonomy or panels or menu because they don't want to dig into admin menu things. So well, this is included within the platform. I think the most important actually is not the technology part because the websites are quite easy. There is nothing, if you take apart each website it's like just two weeks job or maybe okay, one month's job. But when you multiply the number of people you are talking to, the number of vendors, content agency, design agency, CEO agency, digital IT regional, digital local IT from G&J, the brand marketing department, the brand web mastering guys. So you have a lot of, you multiply this by the number of websites. So the standard process is quite important. So we found out that the best way to work is to let the agency, the entire freedom of creation in terms of design because this is what they want to do and the brand wants to be totally independent because often when you arrive to the brand and say, okay, we have a standard Drupal platform, please follow the rules and they say no, my brand is so different. Actually it isn't so different in terms of text but in terms of image and design and positioning they are quite different. So the idea was that we let the agency to create free master templates, what I call master templates is homepage article product and then the tech vendor actually us will make all the declination with all templates like site map and search results and listings and categories with responsive because what we also discovered that there are a few agencies knowing exactly how to do responsive design in the right way but a lot of them think they know and they actually doesn't, they don't know how to do it. So it's easier for us to let them the creative part and we produce the PSD for every single template and then HTML and we test it on all devices. Also what was really important in this process is the very beginning, the specs. Because many of, because the site seems very simple, very easy, many agencies go directly to design, okay, we created you this design and I think this is a big issue because of using the platform and standard content types and standard templates. We force them to create real specification wireframes for each page at the beginning of the project. So we help them to create sketching and wireframes for every single page, showing them a standard, natural website. So this is also something important because if you say, okay, Listerine, look there is OB, you can create the same website but we change everything, they don't understand. So we have to create a demo website which implements all the templates, all the features but in like gray, natural view. So there is no like, it's not shocking for the brand to see these templates and the agency is okay to see these gray templates but they can imagine and project themselves into the new brand website. Another point was the standard hosting. Actually what we contracted with, we didn't contract it but Johnson, Johnson contracted with a hosting company, not important which one is but we based all the platform on iGear which is quite right tool to use when you have a lot of websites to manage because of each brand being totally independent and each local market is totally independent, we cannot easily set up a multi-site system. We have some of the brands like Le Petit Marseille which is a French brand which is a very strong franchise and with strong decision and leadership in France. We can set up multi-site but for many brands each local market are totally independent and then we have to duplicate the websites and to easily duplicate the websites we need iGear because we have a lot of them. I think now we have like 60 websites running this and up growing because we migrating the new websites each day. So what offers you iGear is actually one click site is duplication. We have a centralized view of all websites so you can supervise them all. You're also going quite fast updating the code because when you're correcting one bug or implementing a new feature you have to deploy it across several websites. And you have also quite automated staging and deploy strategy so you can one click deploy from pre-production to product. For just a view for example you have an overview of this iGear back office for one Netherlands listering site so we can back up, we can delay it back up, we can clone the website. For example if you want to create the Belgium version of Listering we just have to clone the website and then the content editors can modify logo, site name, content, et cetera. We can also git pull so we can work with the git repository which is connected to this system. And we can easily create a website from brand new website using one of the installation profile which you see installation profile press for which is a brand clean Drupal or you can use Johnson and Johnson v3, v2 it's kind of different version of the distribution. But now Acquire have signed a global partnership with Johnson and Johnson so we are moving some of the websites to Acquire hosting so it will be quite the same because we have almost the same feature there. So finally what was the learnings of this? Well we are still in the process now it's just three years so the process is much more important than technology is. It's very easy to create such websites like Listering, Vania or whatever but it's much more complicating to deal with agency, local markets and IT departments because of the independence of the brands because of also some political reasons why this brand in Spain want to work only with this agency in Spain we don't know so when you put your fingers on the inside and say you have to use this Drupal you have to do this platform so it's very important to set up a process and also to sell the process to the brands because the brands finally are the sponsors of the projects you cannot just force them I mean within the J&J organization you cannot just force them you have to use this standard you have to sell and explain why it will be better why it will be more interesting more rentable with less cost. Also what we've noticed is that the first figures was very important before websites within J&J the cost was about 100,000 euros and it took them about six months from the initial decision to the real release. It seems very long but actually they have a lot of internal process founding process, project plan process then the development and they have validation, regulatory validation so this is and now we are able to roll out websites within two or three months and within 20,000 euros about or even less if there are clothes of existing websites. What we also noticed is that because you are working within so big organization it's quite complicated to make cost estimates with okay I need a new brand needs a website how much it will cost and you have so many different level of specs and insights so you cannot really make real estimates like standard tender or RFP. So what we find out is that it's much easier to work because these websites are very standard they are not many crazy features we can provide a standard price list for the brand saying okay one template is this amount of money set up of a new website is this amount of money clothing, page of content upload, content translation so we have quite standard we negotiated with the central price list, standard price list and so even it's very easy for a new brand to just connect download the price list and say okay I need 20 templates website with this, this, this, this feature they have a kind of catalog of features and they have a price maybe not the final price but inaccurate price. At the beginning it was quite easy because we were launching like websites, five websites, three websites it was okay but now we are running like 50 websites you notice that the amount of user and user support is just crazy. Guys at AdX receive like 20 calls per day just running websites like I don't know how to upload this article or oh my article disappeared or my homepage is all broken and like 95% is in error from contribution or maybe whatever. So you have to think about the user support because it's extremely time consuming because you are dealing with small overloaded guys which are in marketing department they don't have time to work on the website so they want an answer quickly so they will call you five time in the same day if they don't get the answer. So you have to set up something if you are working with such big companies you have to set up something like ticket based support or whatever they have to pay actually for that because you will need many hours, a lot of many hours to manage all that. Or you can try going with some partners like commerce guys or Acquia for the support but it depends of your capacity. I'm sorry I'm being very fast on that because I actually have a plane in the, so if you don't mind we could start if you have any questions right now because then I could be late and it would be, well not so good session. But anyway if you are still interested in some slides with short version slides you have, they will be on slide share you can follow me and well of course you have to rate this was a mandatory thing so mandatory slide. So if you have questions well just ask them. Yeah okay in terms of the team it's well in terms of G&J it's just not possible to describe they are all kind of teams. We have UK which very organized with project manager IT and we don't see the brand. We have direct relationship with the brands in France but we also have direct relationship with some agency because the G&J local brand don't have even time to think about the website so we have a new direct relationship with the agency almost without G&J. On our side we have about four project managers in a one team so it's organized with one coordinator, one technical and two functional project managers and we have about 10 or 15 developers and also five or six QA because we need QA. So it's a quite big team. Johnson Johnson is a big client for us but we are doing a lot, a lot of websites for them so all around Europe so well that's necessary. Philippa Limchit-Kistion. Okay, well thank you.