 Rwy'n edrych ar gyfer y tro. Rwy'n meddwl'r cyfrifiad. Rydw i'n cael ei tawr, mae'n gwybod ar y cwmwyng ac rwy'n credu'r cwmwyng o'r gwleidol ar gyfer y cyfrifiad o'r ddweud mwythio. Mae'n meddwl i'r LMS ac mae'r cyfrifiad. Felly, felly rydw i'n meddwl. mae gennym heddorol o Edward, yn ymwneud. Efallai yma yma yma'r ydych chi'n cyflawn. Felly, rydyn ni'n helpu bynnag y cyflawn strategiaeth, ond fod y cwmaint o'r ymdannig, rydyn ni'n helpu bynnag y clywed o'i cyflawn i'r cyfrifwyr yma. Mae ein proses yma, ond rwy'n gweithio ymdannig, ond rydyn ni'n gweithio yma. Rydyn ni'n rhagwch gydag o'i cyfrifwyr o'r ymdannig, Tytus. Tytus is a premium certified model part, now I think I've got that right, we help create engaging, personalised and integrated learning platforms through our products, solutions and services. So these are some of the key things or slides rather that I'm going to talk through. So when it comes to upgrading, it seems to be a bit of an upgrading afternoon actually, based on what's in this room, but I'll be coming out from a slightly different angle. So what were our challenges when upgrading to Moodle 4? Why did we happen to create a theme? How did we create the theme? So I'll go through some of the tools and processes at a very high level, some of which have kind of already been reflected in Jason's talk earlier from UCL. And then I want to cover but not spend too long on some of the key features, especially around workplace and everything being tenant aware, which is very important for us and some of the clients that we work with. Mobile access and accessibility as well are some key areas, it doesn't matter if it's workplace or LMS, it doesn't matter if it's Moodle, there's still really important areas that we've had to focus on, especially over the last 12 months. And then a little bit about the future, if I have time, lock the doors, no one's getting out. Right, okay. So what were our challenges? So one of the key things that we have come across just like many Moodle partners, I'm sure, is around when we're actually going to upgrade the Moodle. So whether it's LMS or workplace, feel free to correct me if that date is right, I'm pretty sure that's right. The long term support for Moodle LMS is the end of 2025. Oh, sorry, yes, yes, correct. 3.11, sorry, the long term support for Moodle 3.11 is the end of 2025, not Moodle in general, don't worry. Moodle, in terms of, well, someone's attention, so it worked. So in terms of Moodle workplace, I don't think, and that's why I've not put it on here, that there's a specific date around supportability ending. That was enough on the LMS side to get us to need to take action here. So some of our challenges are listed here, not all of them. So the first one is plug-in compatibility. So obviously the plug-ins database is thousands of plug-ins. Some are supported on different versions. This is a key thing for us. As soon as we upgrade a client, if they're using 30 plus plug-ins, for instance, we have to obviously check to make sure that they work. Similarly, I mean a theme is a plug-in, but we've got theme compatibility that's obviously very relevant. A lot of the work that we've done is, in the past, was quite bespoke and custom. That led to quite a lot of technical debt, which I'll come back to. But we needed to make sure that anything that we're going to be providing our hundreds of customers with is going to be compatible, of course, on Moodle 4. And there was a lot of change, a lot of positive changes between Moodle 3 and Moodle 4. And that's for LMS Underworkplace. Testing process. So not only did we need to test things internally at Titus in terms of the plug-ins, the theme, et cetera, but our clients often have their own testing processes. So there's a huge amount of time there. The user training element, if we're upgrading people, it's not just a question of the DevOps team upgrading a platform. Obviously the customer needs to be communicated each step of the way. They might have multiple platforms, test platform, staging platform, separate sandbox production platform. There's a lot involved, and it takes a lot of time. Similarly with the upgrades, there can be a lot of downtime as well. We need to make it as slick as possible with our DevOps team. In terms of customisation, re-implementation, I've got a word of that a little bit better, but that's probably a huge one for us. So any custom development work and huge bits that have been bolted onto the side of Moodle required a really thorough testing process when we're upgrading. All of this does plug into the theme as well, because on 99% of our sites, we have some form of either productised now or previously bespoke theme. Compliance and accessibility. I'm actually going to come around to later. I'm not going to bother my notes. There's a documentation and support side of things. We need to keep everybody informed of the new functionality, make sure people understand what's coming next, how to use the platform. There's so many steps involved. I'm definitely behind on time. Why did we create a theme? I've already mentioned around the need to upgrade from Moodle 3 to Moodle 4. We need these bug and security fixes. We need people to be in support. We wanted to reduce the amount of technical debt that we had from all of our bespoke developments, and that's where at Titus, we've decided to take more of a productised approach. Where applicable? Because it means we can liaise with our clients and understand their needs and what we can potentially build into the theme or a supporting plug-in to the theme and then allow all of our clients to benefit. I'm not going to go into each of these points now just because of time. I'm very aware of it. Some of the key ones, again why we created a theme, was really around the customisation and control and being able to allow organisations to change as much as they want to change. Change as much as possible. The Moodle default theme, the Boost theme, is very, very clean. Massive improvement on Moodle 3. But a lot of our workplace clients in particular needed a lot more. They needed to be on-brand. LMS, we find, people can be a lot more flexible, they want it nice and clean. Workplace ever so slightly different. Some of the other points that are listed on here I will cover on further slides. This is just an example of a couple of the clients that we work with. LMS and Moodle Workplace, Network Rail, Labour Party, UCL, CNN, Superdry, et cetera. You can see that we work with quite a range of organisations, basically. How did we create the theme? The first thing I wanted to mention was the tools side of things. These have been incredibly beneficial. From the product side, I probably couldn't live without any of these tools. The Gira side is really more so for the developers and having our backlog and picking up tickets, adding the user stories in there were applicable, making sure we get everything planned in. Product Board, something I started using this year. Super useful. It allows me to track the cost of things a lot better as well. Anyone that uses Gira a lot, it's a very powerful tool, but it can be an absolute utter nightmare at times to try and customise and configure. Product Board is very specifically focused on products. You can have your own roadmaps, et cetera. I'm not trying to upsell that product, don't worry about it. Mirror, so that's a super useful whiteboarding tool. I actually came across it because the Moodle workplace product advisory group used it first. I'd heard about it, not used it, and they used it in a workshop. I just thought, I need to get on board with this. I need to use this. We use it. You can probably not really tell how we're using it from these screenshots, but to collect our user stories and we share these mirror boards with our clients and we have a collaborative approach to make sure we understand what features they want in the theme and prioritise them accordingly. So, just again, based on time, I will speed through this slide a little bit quicker. So we work in a Kanban methodology, so we'll have a list of tickets and our developers just kind of pick them out as they're prioritised in that area as opposed to working to strict individual sprints. We're now very customer led, more so than we were in the past for sure. So we have a customer portal where people can vote on ideas and submit new ideas. We do that through Product Board, again, because that's why it's super useful. Anyone product-based team is definitely worth checking out. And we collect all of our customer insights through there as well. And that's been absolutely invaluable for me on the product side. Some of the considerations, I have to be very aware because I'm part of the product advisory group. The last thing I want to do is to either design or implement something that's going to directly conflict with what could be released in the main product. So particularly the product advisory group on the workplace side, that's super important. And also, huge consideration is around what versions of Moodle our plugins are going to be supported on, because the more we build, obviously the more testing that needs to happen on these different versions. And obviously Moodle has its long-term support version of 4.1, so there's been a lot of considerations around that. So I will zoom through some of the key features. Huge amounts of customisation. The amount that you can rebrand on the workplace platform is huge. You can see some of the settings on the left-hand side. We've got configurable login pages with different variants. We've got a site home page that allows for marketing tiles and carousel shortcuts, similar kind of features to what you'd expect on a WordPress website. We have... Where's my GIF? My GIF wasn't showing. Pretend you can see it. The ability to choose the order of login options on the login page. So, for instance, a lot of people prioritise Office 365 logins, for instance, so you don't want the manual options at the top. So we move those under a collapsible area. Site home page I already mentioned. That's just a quick example of a screenshot, at least that one's showing. Other key features, simple things like colour gradients that match people's branding. If you want that on the top navigation bar, you can see there's a screenshot there, almost as proof on the left-hand side that our theme is kind of workplace compliant as well. So that's one of our key points, really, is that it's tenant-aware. So all of our set... I'm not going to say that, actually. 99.9 of our theme settings are compatible with multi-tenancy on Moodle workplace. So you can brand up all these different sub-platforms completely differently, which is fantastic. And also a game changer for our sales team as well because it's a lot easier to have conversations with people when you've got a site with someone's branding on. The course library. We wanted to make some initial improvements. This is just two examples of... I'm not going to say dark mode, it's not dark mode. A dark background, a darker theme and a lighter theme. We're aware of the changes that the workplace team are kind of implementing. We've introduced course banner images, activity navigation, changes to the course index menu. Huge one for us was a site-wide footer. A lot of people really missed that, especially people that had some of our older themes at Titus. They had a footer that sits at the bottom of the page. So we have that alongside the standard Moodle footer as well. Mobile access was huge for us. So we are taking a lot more of a mobile-first approach now. The Moodle app isn't always an option due to restrictions around branding, especially with workplace. It has to look in a very specific way. The app can be a little bit restrictive at times. Certain circumstances, the Moodle or the workplace app is great. Other times it doesn't quite work. You can see we've introduced extra navigation banners under certain resolutions as well, just to make the experience on mobile devices more friendly as well. Accessibility, I've got two slides on this and I've only got about a minute left. So there's been a couple of talks on this already. Essentially, we didn't know anything about accessibility. I think it's fair to say really about 12 months ago. But a lot of our clients have been really good in educating us. That includes the accessibility expert at UCL. What is accessibility? It's essentially led by these four guiding principles. Is your website perceivable, operable, understandable and robust? I know Moodle LMS has just been WCAG 2.1AA certified. I think Moodle workplace are looking to do the same as well. Our theme is built with accessibility in mind. So we're making constant changes and iterations to that. What are the end results? Well, essentially creating this theme, especially on the workplace side, has enabled us to simultaneously upgrade our customer base to Moodle 4, while massively improving the personalisation and building on functionality within the platform. In terms of the future, that's just a few extra things that we may consider doing in the future, looking at other technologies to improve the theme and improve performance, like React, potentially having accessibility audit ourselves, and creating a product advisory board with our customers as well as something that we want to do to get even more targeted feedback. That is a quick summary slide that I'm going to leave on there as I run out of time. Thank you very much. I hope you took something away from that.