I'm Mark Goodwin. I'm the web team manager for Rentokil Initial. And I've been working there for 21 years. So I've got quite a bit of experience in CMSs and running a small team which delivers probably 180. Hello, hello. Which delivers 180, that's better, 180 websites globally. We've got a very small team of about four or five developers and then we rely an awful lot on VASS to help us deliver the content and also the templates and the code for us. So Simi, would you like to say a bit about yourself? Hello. Good morning, survivors. How many of you have like a heat hangover today? Yeah, I see the lots of you. So I'm Simi and in my current identity I declare myself a Magnolia consultant, a team lead at VASS. And I had the honor and the pleasure to work now for four years with Mark and the Rentokil team. And I'm kind of very happy for you all to get to know a lot more about them, what they are doing and how they are doing it. With this said, Mark, would you like to introduce Rentokil to all of us? So Rentokil Initial global brand, probably most of you have heard of the Rentokil brand, which is the pest control business we've got. But we do have two other brands, one being initial, which is normally the washrooms, not here, but hotels. Normally you have your soap dispensers and your hand towels, etc. And then we also have an Ambius division, which decorates rooms, puts plants in, makes the well-being really good. But the Rentokil brand became the world's largest pest control company a couple of years ago when we purchased a company called Terminix in North America. So we are now 65 people across 92 countries with North America delivering probably most of our business these days. Digital is at the core of Rentokil, everything we do. It's not just the websites. All the technicians that go out and survey rooms looking for pest problems, they used to do it all by hand on paper, but now they can measure a room digitally. They can place the traps on there and don't really need to do anything by hand anymore. We've got a lot of portals that customers can log into. Again, it's all digital. We had a really big push about five years ago to get rid of paper. And we're a global reach. As I say, we're in 92 countries, 26 languages, and we will cover some of that later. Simi, do you want to tell us a little bit about VASS? Well, yeah. VASS is a global digital solution partner that was now in the space for more than 25 years, supporting our clients in all their digital solution needs. And as I said, we have worked with Rentokil for four years now, supporting their digital transformation journey. It's like how I like to call it, a digital transformation journey. And mostly what we are doing, we are ensuring that, well, all those 160, I don't know how many sites you already have, because last week we had a go-live. We have two go-live in Sunday, so I have absolutely no idea. Well, that everything runs smoothly. Okay, so we collaborate with them on that. Ooh, Mark, please don't tell me that we have to migrate all that stuff. No, no, no, no. Don't panic. Don't panic. So this is a little bit of a timeline over the last 20, well, since I started Rentokil. The images on the right-hand side, they were how our websites looked back in 2005. There was no consistency. There was no branding. They all were run by IT teams. No marketing wrapped around them at all. And at that point, we decided that it would make sense to pull all these sites into one platform. Hopefully you have a standard feel, get some branding around them, make it look like Rentokil Initial, or Ambius. So that's where we started in 2005. We pulled as many sites as we could into a CMS. It wasn't Magnolia at the time. And we went through that process of templating and making them standard. And we spent the next, well, 14, 15 years going through that process, reiterating, and eventually we ended up with 180 websites in the system. But they were still individual websites. Every site still needed a developer to go and do something to actually make it function. Contact forms, wrapping PHP around pages to make them dynamic, et cetera. So we decided that it was time to move on to something a little bit more modern, a little bit faster, and a little better for our content authors. So that's where we started talking to Magnolia. And in 2020, of course, COVID kicked in just as the project kicked off. So it got delayed a little bit. But then we spent the next, again, the next couple of years learning about Magnolia, understanding how it could work and using our learnings from the previous 15 years to build a better templating system and make the user, the author experience a lot better. We didn't really start the migration from the old system to the new system until late 2021, maybe into 2022. So it took us a couple of years, but we migrated 120 websites manually, copying and pasting a lot of content. Which isn't a bad thing, but obviously these days with AI would have been a lot quicker. Moving on to 2026. Today, we've now got 150 websites in there. And as Simi said, it's growing. And Rentecure had a... We have a lot of acquisitions. At one point, we were buying a business every week. So every business we buy, we've got to do something with that website. Some of them fold into the master brand. Some of them need to go on their own site because they're big enough. So we tackle those, and we'll talk a little bit more about how we do some of those later on. Now, this is a story that I have heard lots of times, but as a Magnolia fan I am, I like to hear it over and over again. So, Mark, could you tell us why did you choose Rentokil when you switched CMSs? Well, we actually chose Magnolia, not Rentokil. Do you see, guys, it's the heat hangover. What can I say? Of course it was to work with you. Seriously, support. In the old system, I think there was one person in the UK that could support it for us as the system was dying, apart from our own internal team. So we had no external support. It was an old system. It was out of support. When we spoke to Magnolia, a room full of partners, we could pick anyone we wanted to work with, and we ended up with Simi. But as you know, you weren't our first. We also wanted headless. So we're not just serving websites. We've got, as I said, we've got some portals. Portals have got content in them, multi-language. We want to be able to serve that content from a CMS that a developer doesn't need to build into a release. It can be done by a non-technical person. So we want to be able to serve that Magnolia, tick that box. Wizzy Big Experience. I know a lot of people complain about the green bars in Magnolia. Tell you what, that's heaven for what we had before. So, yeah, we want to make sure that it's not quite editing in place, but at least you can see what you're editing rather than just filling in some forms, waiting sometimes an hour, sometimes overnight for a publish to see what you actually did and see whether it was right or wrong. If it was wrong, of course, you've got to go through that process again. Flexible. We've got a lot of bespoke systems within Rentokil that have been written internally. We want to be able to talk to those. We want to pull data from them. We want to push data back out to them. The APIs that Magnolia's got, that ticks that box. It's got to be able to support 180 websites globally. I've put 26 languages, but I think it's more than that. It's constantly changing. I think we've got Chinese in Argentina or something at the moment. I don't know what's going on there. But yeah, and then rapid edits. As I said, it was taking a long time to make any changes to any of the content in the old system. Magnolia, we can make changes in minutes and publish, and it's out on the web for our customers to read. That's me done. Okay. I think I've been speaking enough now. My mouth's gone dry. Fair enough. So, as you see, Mark likes to remind me each time that we were not the first ones as partners for them. Okay. So, now let's discuss. What do we need in order to manage global websites? Well, the first thing, we need a team, like the correct team. And in Rentokil's case, this team is very diverse. It's us, the IT Magnolian fellows, with the support of us, of course, and of our dear colleagues from Magnolia. But it's not just us. We have, of course, the marketing team split between the ones that generate the content, that contribute the content, the SEO team, the data team, you name it. And, of course, all individual markets. Mark already said, multi-country. So, imagine each country has mostly its own marketing team. All of them have, on top, of course, a managing line. So, that's the first step. You need a team, a dedicated, specialized team, in order to achieve this. Everybody works, of course, with Magnolia. Cloud Magnolia 6.4 at this stage. But talking on tools, like what will be the highlights? Because we could talk probably for hours on how we do things and what we do to manage globally these so many sites. But one of the core things is this single code base. Okay? So, everything that we have, we share it across all of our sites, all of our brands, because there are lots of brands. Of course, we use the components library and we just make it look different. Okay? This is important. Why? Because if you want to manage the code, if you go wrong for so many sites and so many brands, it will get to a point where it's unmanageable. Of course, also from the perspective of scaling, because, yeah, we want to do new things. And from the perspective of the innovation, on which we will talk a bit later. In relating to this, I mentioned the brands. We have lots of brands. Okay? So, this single code base also allows us to have a very smooth brand transition. What does that mean? That means that when we have a new acquisition, and Mark said at some point there are one acquisition per month or something like that, it's quite easy to put in life a new site, a new brand. So, work that may have taken months, now it may take weeks. So, it's quite quick. You have heard about the 26-something languages and that we have Chinese in Argentina. Well, for us, one of the core tools that Magnolia offers is the live copy. We are those freaks, you know, that we go on Magnolia webinars and they introduce, I don't know, some cool AI tool and whatever. And we are the ones, yeah, yeah, yeah, but does it work with live copy? Because if that doesn't work with live copy, eh, not for us. So, yeah, that's important because we have lots of countries in which more than one language is taught. So, our approach to the live copy, it's probably the most simple one, okay? Because we do like a like component and content. Again, this is because there are 160-something sites, lots of countries, lots of continents. I think that just Antarctica, we are not there. But, well, give us time. So, as I said, when we do this management like a like, it's much more easier to maintain all the branding dialogue, let's say, like this, all the information. And also, when something is changed, you make it much more easier to change across the rest. With this in mind, of course, content translation, it's also quite a big one. Now, I would like to ask, Mark, do you know exactly which Magnolia version we are in? Six? Of course I do. 6.4.6. Okay, 6.4.6. The next release? And 7 in the next release on the 8th of July. Okay. And 6.4.7 in the next release. Cool. Any Magnolian in the room can tell me which is the latest released version? 6.4.7. Oh, cool. So, in the next release, we will be in the last Magnolia release. Nice. Now, we have seen the hands yesterday, you know, the one that has raised the hands or who were already in 6.4. And, well, not that many. We will have some conversations a bit later in some minutes on why it is important. But, until then, Mark, do you want to talk a bit about the multi-region? Because I know that you are quite proud of it. Multi-region is an example of when something bad happens, it's good. So, as we were starting to go down the Magnolia route, we got DDoS'd on the old system. And that meant we were in the spotlight. We were losing $600,000 a day when the site was down. So, people were, how can we stop this happening again in the future? We were in the process of building the servers ourselves, to host it ourselves. And, of course, then, how can we make it? How can we make it? Magnolia have got cloud free. Let's go with cloud free. Give Magnolia the problem. We don't have to worry about the infrastructure. Let's stick a Cloudflare over the top of it. So, we were then protected. We've moved on. We went through to, we've moved to DX Cloud last year. With the intention of looking at multi-region. But, how do we need, I don't know. We then had some campaigns go out in Asia, which took down the Magnolia servers. That, again, flagged to the money people that we need to put more effort, more money, more resource, more resilience into our platform. So, of course, multi-region is the opposite answer. We've now gone, we've got an instance in North America. We've got an instance in Europe. And we've got an instance in Singapore with one author, which pushes to all three instances simultaneously. So, we've all, and then load balance with Cloudflare. So, if one goes down, the other two will pick up the slack and serve the content for the rest of the world. And then, just this week, I don't think he's in the room, we were handed the keys for China. So, we're looking to go live in China towards the end of August. So, we are covering the globe. It's how we are. Would you like to talk about the AI project and metadata? I kind of have the feeling that after yesterday's topics, we will kind of change what we are seeing in here. But, okay, let's stick with the plan for now. So, of course, we will continue our AI project. Metadata, metadata is the first of them. Tagging, not just assets, but also content. The content authoring. We are working also, of course, with the text-to-components now, docs-to-components, it seems. So, hell yeah, let's see how that will go in. And we all have already started the data insights and analytics. So, it isn't what's next, but we are there, there. So, Mark, more things? As you said earlier, what's the advantage of being on 6.4? We get all the latest toys, one of them being Swift Publishing. So, again, we're experimenting with that at the moment, and we're hoping to turn that on in the next few months. But, again, with the size and the amount of content, we've got 30,000 pages, 30,000 assets in Magnolia. Multiple teams working on content at the same time. They want to be able to publish. We find that every now and again, someone publishes a whole site of 500 or 600 pages, and it becomes a bit of a slower performance for the other authors. So, we're hoping that Swift Publishing, I'm told that Swift Publishing, will solve that problem. And, again, making it a better experience for the authors, not just for our customers. So, yeah, getting quite excited about that. As you see, single code base, subliminal message. So, we're coming to the end now. I just want to just really give a bit of an overview summary there. We've gone from the chaos and the mess of IT-managed websites with very little common look and feel between them, very difficult to manage, through to these lovely images on the right-hand side here. They are all coming out of a single template, single set of components, just with different content, different images, and different CSS. And it gives us, I think, a bit of a brand identity. And hopefully, people can look at most of our sites and go, yeah, that's friend to kill. Maybe dated, but that's my own opinion. And, again, you can see we've got it in Arabic there. We can go left to right, right to left. And I think that's it. You can't run away too quickly. Sorry. We've got the tough bit now. Tough bit? This is the easy bit. You've done the hard stuff. Thank you very, very much for walking us through that journey. So, just... No, I'll take that. Do you have any questions from the audience? We're doing live questions today. So, does anyone have any questions they'd like to ask Mark or Simi? Sorry. Just wait for the microphone, if that's okay. Good morning. Thanks for the talk. I would be interested in the Swift publication combined with your search appliance. What kind of search are you using at the moment? And how do you put the content there? We don't talk about search. We have SiteSearch360 plugged in, which is very, very basic. So, we found that not many people were coming to our sites and using the search. Most of our customers are panic customers because they've got a rat running around the kitchen. So, they just want to come to the rat page, pick up the phone, or fill in a form. They're not searching around the site looking. They're not researching, really. So, we don't put an awful lot of effort into search at the moment. But it is something we do need to look at in the future. Thank you very much. Do we have any other questions from the room? No? Oh, sure. Thank you very much. Seb is on the way with the mic. Hello. Yeah. Well, thank you for your talk. So, I'm Rafael from Geberit. And in many ways, what you've said here, it's similar to our web setup. It's just a third of the countries, but one more language. But anyway. So, I'm curious to know how you handle the content distribution process. So, you said it is globally created, but locally adjusted. Now, we face a similar challenge. It's just that the master content tends to change and the local content tends to be adapted. So, after several versions, it gets a bit tricky. How do you handle that challenge? I'm not sure. We have here in the room with us our content specialist. So, probably if you approach us after, we can put you in contact with him directly and he can explain far better how they are managing it. But generally, we've got a central team that will cover and come up with the standards, the processes of pushing content out to the market. It's the local regions. And then we have local marketing teams as well who can then adapt it or take it as is. But, yeah, the strategy comes centrally from a global team. Which, Rasto in the green over there, if you'd like to talk to him more about it. Perfect. All right. Well, on that note, thank you both very much. I think I need to take the microphones, if that's all right. Thank you. Thank you.