 team at the Australian Government Department of Finance. We're responsible for GovCMS. We basically do what Michael was talking about for government. I want to start just by setting a little bit of a scene and reflecting on the past two years and what it's meant for GovCMS. We have always had a pretty strong roadmap and things that we wanted to do to evolve the GovCMS program and the platform that we're hosting sites on. But during the pandemic, we really shifted our focus to BAU rather than picking up things on our roadmap. A few other things I'll be talking about tonight. We actually had started back in 2019 and early 2020. And for various reasons, we decided we need to stop working this for the time being. And unfortunately, that's taken two years to get to a point where we're feeling a bit more comfortable now taking that roadmap forward. The stability of the platform was the absolute key thing for us during this time. And also after 12 months, 18 months of dealing with all teams, pandemic, there was so much change fatigue going on. The risk of us doing anything substantial was quite high. So we decided, let's just wait it out for a little while. The impact on our BAU was pretty significant. We had very good resilience. We maintained a really good security posture. But as Michael and others will attest to, that takes a lot of work and to do it in a way that's kind of invisible to our end customers, while they were managing to keep their own websites up and running from a content point of view, was quite an impact on the team as a whole. We were really risking people burning out. Thankfully, we're coming on the other side of that now. BAU does not mean that there is no work to do. So I'm just putting this graph up here to put a little bit of context for some of the stuff. This graph represents the type of activity that the team's gone through over the last couple of years. You can see that really big blip that's yellow. That was our Drupal 8 to Drupal 9 migration for the SaaS platform. It was something like 120 sites had to get migrated from Drupal 8 to Drupal 9 on our SaaS platform. And of course, we had to have all that done before Drupal 8 went end of life. Oh, and by the way, we still had a pandemic going on at the same time. So that was an interesting project. The second blip you can see to the far right-hand side of the graph, that's the latest machinery of government changes that we've had to manage with the incoming government. Lots of sites getting moved around, agencies getting split apart. And of course, that means they all need new websites or major changes. So a lot of work behind the scenes just to support that transition as well. An interesting reflection that certainly we've seen and perhaps may not be front of mind for a lot of people. Citizens' interaction with government has definitely changed over this last two years. The graph that I'm showing here is just for our SaaS platform. We also have a Paz platform. SaaS is fully managed by the Department of Finance. Paz, the agencies that are using that have a bit more flexibility in what they run on the platform. It's easier for me to grab the data from the SaaS platform. So that's all I've got here. So ignoring the ridiculous spike that happened back in March of 2020 at the height of the pandemic where we had 127-odd million page views hit the platform in a single month, we used to get about 20 million page views a month. Well, we're now hovering around the 40, 42 million page views per month. In terms of the overall number of sites that GoCMS has got, we haven't really grown that much. There's been a fundamental shift in how citizens interact with government. They had to interact online because there was no other way for them to do it for a fairly significant period of time. That's now translated into maybe a larger part of the community has figured out that actually interacting with government online is one of the ways to get stuff done. So that trend has definitely changed. And that's got implications for all of us that are building sites, managing services, creating and publishing content. We're now putting that in front of more people, which means we have a broader range of people that we might need to provide those services for, and perhaps they haven't been seeing it in the past. We're not expecting this traffic pattern to change in any downwards direction. It's likely to keep gradually climbing. Quick summary to sort of show you some of the numbers that we're dealing with at the moment. This is kind of as of today and some numbers from over the last 12 months or so. GoCMS hosts more than 340 sites now. There's another 60, 70 sites in development. They'll go live soon. Some of those are Drupal 7 sites that are shifting to Drupal 9. So it doesn't mean we're going to add another 70 sites completely to our numbers. As of today, we've got 104 agencies signed up and a few more in the pipeline. We're really happy over the last two years. We've managed to have a 99.99% platform uptime for editors and publishers that the amount of work that the team put in to keep the platform fine-tuned is just phenomenal. The numbers start to get really scary when you start looking at the totals. The SaaS platform over the last year, it's more than a billion page views. That's with a B and more than a petabyte of bandwidth passed through the platform. For those of you that are not familiar with the terminology, a petabyte is 1,024 terabytes. So I'm going to focus now on some of the things in our roadmap, the stuff that we are going to be working on in the next 12 months. It may not be the most technical presentation either, but hopefully it gives you guys some inspiration as some of the things you might be getting to work on in the coming year if you're doing some GoCMS projects. We are already well underway with our roadmap, which is good to see because, like I said, we've kind of stopped for a couple of years. And at the moment, our focus is on DXP, digital experience platforms, transitioning to Drupal 9. We've still got a few sites that are hosted running Drupal 7. We've got some program activities that we need to do. Over the course of the financial year that we're in, some of you will know that Google is making fairly radical changes to Google Analytics and that there will be a shift to the GA4 platform. That means we've actually got to do some changes behind the scenes, particularly with our Drupal distribution to make sure that it's compatible with the new GA4 platform, and that our SaaS customers in particular can still continue to use that tool for tracking usage on their site. The DXP work itself is a fairly complicated procurement that was currently underway. We are currently at the stage where we've done some proof of concepts. I'll talk about more of that in a little bit later. There is a procurement exercise that will create a panel of suppliers that agencies will be able to use that should be in place by about the end of the year. Those of you that are familiar with GoCMS know that we have a contracted service provider at the moment. That's Salsa Digital and the AMAZEE team to actually manage the platform on our behalf. That contract is up for renewal. This year before Christmas, Finance needs to approach the market and start a whole tender exercise. That won't be completed until about July next year, and then we'll be transitioning to whatever the outcome of that process is. On top of all of that, we've got our transition to Drifl 10. Again, I'll talk more about that shortly. We're also doing some really interesting work with, of all things, single sign-on. The interesting thing for us there is we actually have to integrate with protected government networks. Another layer of complexity on top of what would otherwise be a relatively straightforward exercise. We're doing some proof of concept work in that space, and hopefully we'll have a working example of that again by the end of the year. As we get out towards the end of the financial year, we need to do a refresh of our cybersecurity tools. The tools we use weren't actually really mentioned by Michael. My comment would be in that sometimes you get what you pay for, and the tools aren't necessarily enterprise grade. You do need to choose and assess carefully to make sure that they're really up to the standards that you would need them to be. We have a particular set of tools that we're currently using. Early next year, we'll refresh the contract for that, and I'm very interested to see where that lands in terms of what we might be using next year. As we get into a little bit further down the track, we don't know exactly what this is going to look like until the tender process has been completed for the hosting contract. We might, and I have to say might because I don't know, we might end up with a different service provider, in which case there's some transition arrangements will have to happen. We also might end up with some changes to the underlying platform. Back in 2018, we were with Acquia for hosting for the GovCMS platform, but the tender responses that came in at that particular exercise led us towards the Kubernetes-based platform and Lagoon that we're on today with Salsa Digital and amazing managing it for us. Once we know the outcome of that tender exercise, we'll then know what the impact is on agencies that may need to migrate or have some other changes done, and certainly we may have to onboard some of the technical staff with our new service provider until we get to that stage. I really can't fill in the details of that. The new hosting contract has to be in place by one November next year, so it will take us about 12 months to get to that point. There are a couple of different places through our roadmap where government agencies and members of the community can potentially get involved in this process. Right now with DXP, we are doing some proof of concept showcases. There's four projects that we're working on with various suppliers, and there will be a community showcase that I'll talk about in a minute. For the Drupal Services panel, this is a group of 17 suppliers at the moment. Some of you in the room may work for companies that are on that panel. There is going to be a refresh of that panel to add some more suppliers. Well, we may need some assistance from our community to help with the evaluation of that work. Potentially there could be some subcommands if anyone really is keen to come and work at GovCMS and you're a government employee, we can have a chat about what that might look like. I mentioned the single sign-on. This is one of the foundation enabling pieces that we're looking at. A number of the agencies that we host sites for have some operational challenges. Not necessarily the same as what Michael described, but how do you share content with people inside your organization when it's not approved content, but you also don't necessarily have the capacity to add user accounts into your Drupal site? Surely a single sign-on solution would solve that requirement. Now add on to that, you start talking about protected networks. There's a little bit more work to do in that space. For the hosting contract, we are looking for government agencies to help us with things like vendor workshops. The evaluation exercise we know is a fairly big piece of work. Last time we did it, it took about three months to finish the evaluation process. Again, I'll be looking for maybe some secondaries to come over and work with the GovCMS team for a couple of months while we manage that process. Then again, depending on the outcome of that process, there's probably going to be some requirement for agencies to get involved during the transition. We'll keep information flowing out on that as more information comes to hand. There is some action required that we need agencies to do now. This is probably relevant to you even if you just work for a supplier. Maybe you're a supplier supporting an agency who's got a Drupal 7 website. You really need to start poking them, prodding them, tapping them on the shoulder and asking them what their plans are. We still have about 27 sites that need to migrate away from Drupal 7. Of course, it's now the 1st of September, which means time is running out fast. Our only saving grace at the moment is that most of those projects are underway. That doesn't mean they're close to finishing. That doesn't mean they're actually going to be able to deliver on time. This is something that we're watching and monitoring very closely. I have a few agencies, shall I say, on my shit list that need a bit of a talking too so that we can hopefully get them back on track to deliver. We don't support Drupal 8 anymore, so they are all moving to Drupal 9. Then Drupal 10 starts to become the next interesting challenge for GovCMS. Yep. You're probably all familiar that the Drupal Association pushed out the release date of Drupal 10 to December of this year. Looking at how the core is progressing, it looks like they're going to meet that December timeline. Quite frankly, they don't really have an option because there's too many dependencies that are also becoming end of life. It's December or nothing. Michael Richardson has just left the meeting, which means I think I'm not presenting to the room anymore. Keep going. Okay. So we now have some challenges in the Drupal 10 space, and it's all about readiness. So Drupal Core is not ready yet. A lot of modules in Contrib World, they're really not ready yet. And that means that we're not going to be ready immediately either. We still have to build the GovCMS distribution. And the biggest challenge that we have seen so far, and this is something I need you all to take away as a bit of something to think about, we've done a scan of the existing sites that are sitting on the GovCMS platform. And most of the issues that we are seeing right now for Drupal 10 compatibility relates to deprecated code in site themes. We are working to figure out a way that we may be able to fix some of this in an automated way. Talking to our service provider and some of our other technical guys as early as, sorry, as later as today, they're hoping they can get maybe 90% of the issues into a state where they can be fixed automatically. But we're suspecting some things are going to need to be fixed manually. And some of our agency site owners are probably not going to have femurs or devs on hand to address some of these issues quickly. So this is a challenge that we're going to have to try and figure out a way of getting around that resource problem. The next biggest issue that we've got is that there are a significant number of modules that are not yet stable for Drupal 10. A lot of work is still in the pipeline. Yep. But we're looking at some of the modules that we currently use in Drupal 9. And well, maybe the maintainers aren't particularly that active. And that's starting to concern us a little bit. If you're in a position that you can make a contribution to push a module along, maybe deal with something in their issue queue, get them a little bit closer to being stable, and you can contribute some time to that, that would be fantastic. Maybe we need to organize a code sprint. And that could be something that I could potentially sponsor with some caffeine and pizza. Because put a few heads together, we might be able to smash through some of this work. Now, code sprints are already going on. But maybe we need to have a slightly more focus code sprint around some of the things that we need to be looking at for GovCMS. So I'm trying to figure out what that might look like as well. We know that one of the options that finance or GovCMS has got is to potentially take on the maintainer status of a module or maybe fork a module and create our own instance of it. There are consequences for that option, because then who looks after it long term? It's not the kind of path I would want to take, but we may need to in a couple of places, particularly where some of the security modules are at play. If I recall correctly, I think even in the room she can scream at me if I'm saying this all wrong, but I think the two-factor authentication module is one of the modules that's not yet Drupal 10 compatible. For us, that's just not negotiable. We have to have that module, so we're going to have to figure out a way to get that module ready for Drupal 10. Hopefully the maintainer will actually come along and do their thing, but if I have to fork that module so that I can do the work myself, we will. The other option that we've got, I won't call it the nuclear option, but it's pretty severe. If it's a less popular module, we may actually remove it from our distro, and that means a site running on our SaaS platform won't be able to run that module. If they're on the PaaS platform, they will be able to run a module that's perhaps not quite ready to the same standard that we would run on the SaaS platform, but then they have the consequences of maintaining their code base as a whole. Again, not necessarily a direction that we would want to go in. DXP a little bit more about what we're currently doing and what we're planning. Interestingly, it was before Christmas last year. GOTCMS got in touch with a whole range of our existing customers, and we had a conversation with them about what does DXP mean? I probably asked about 10 different agencies, and I got about 14 different answers. It really means different things to different people. That's been our takeaway. No one really understands what it means. The way we're looking at it is it's all about enabling a much richer content experience for users, where you've got personalized content, where you've got content that adapts to something that you know about the user. It's tools that enable reuse, syndication, sharing of content. It's to create and manage a single source of truth. A lot of the agencies we're talking to recently say that that's their biggest pain. They have content that they've very carefully created and curated to publish on their site. Someone else also from government perhaps comes along and copies the content from their site and pastes it onto their own website because they want to be helpful and useful to the users of their site. That means when the original content gets updated, you've now got a content synchronization issue because they don't go back and recopy and repaste it back into their own site. We've seen some interesting side effects of that. Some of the bigger agencies, and I won't say who, but some of the bigger agencies drive content towards their online channels for good reason because operating their call centers can be very resource draining and it turns out to be very expensive. What happens if you get another website that is using more or less the same content, but they don't include the links to the online transactional services, they only provide the phone number to the contact center, undermines all the effort the agency has gone to to create that really crafted content experience to guide people into the online channel. We've got some proof of concepts underway in this space. There's going to be a community showcase on the 16th of September. I haven't actually got the link here. I should have done that. I can get the link circulated around. People can register to join. It will be an online event and you'll get to see four projects from four different vendors. The session will take about two and a half hours in total to get through. Each of the vendors is showing a slightly different approach to a slightly different problem, so they're not all talking about the same thing. We're hoping that this inspires some conversation and some, hmm, what if we could do something like that kind of conversations with site owners? I'm sure some of you will also appreciate the, hmm, how would I actually make use of that, maybe a project that you're working on? The end goal of this work is to have a panel of suppliers in place by the end of 2022. So I mentioned at the start of my chat that we're doing a refresh of the Drupal services panel. That's a separate exercise, but this panel of suppliers effectively will be through that same process. It'll be a different, um, think of it as a chapter in the price book. And if you want to come and buy some of this software or engage some of the services from these suppliers, uh, basically the procurement process becomes a whole lot easier. GovCMS is also looking at what a whole of platform solution might look like. Potentially a whole of government solution. We host a vast amount of government content already. We've got 340 odd sites. Um, some of those sites, I will name drop services Australia, they are one of the biggest sites in terms of traffic that the government has. Uh, and our total platform traffic is larger than the top four Australian banks combined. So in terms of the footprint for Australian government, we don't host everything, but we host a pretty big amount of it. So maybe a whole of platform solution actually creates some very interesting opportunities for sharing content and creating better experiences. We expect to start off small. There is a lot that the GovCMS team doesn't really know about DXP. None of us have done it at scale before. You know, I've been doing government stuff for the better part of 25, 26 years. I've done some stuff with what you would call DXP, but not at scale and certainly not with the tools that are available today. So there'll be a bit of a learning exercise, but maybe in the next year or two, there could be something a bit more substantial. So, yeah, we'll crawl, then we'll walk, then we'll run. Government as a whole has also got a whole lot to learn about what the XP means and how to implement it. To be honest, the technology is going to be the easy bit. Most government agencies have not done the upfront design and user research that would be required to build the kind of experiences that their citizens actually need. They haven't done the segmentation to understand their users yet. They couldn't probably even describe the kind of outcomes that they're looking for from a better experience. So that's where a lot of the work needs to be done in that kind of crawl stage while we figure some of this out. The key thing people do need to keep in the back of their mind though is that for us, GovCMS and Drupal is going to be still the core of whatever platform that we provide and that is not negotiable. It's absolutely essential that government maintains ownership of the content management component. It's essential that that CMS is open source because it means that government can modify those tools to meet the somewhat peculiar requirements that government has. The DXP tools we're looking to integrate with may be a mixture of open source or proprietary. They're likely to be hosted off the GovCMS platform. There might be a few things that could be hosted on the GovCMS platform at some point. We haven't quite figured some of that out yet either. But it does mean there's some interesting opportunities on the horizon and that may lead to some interesting projects that you guys get to work on as well. If you would like to know more about any of this, these are the ways that you can get hold of the team or me. Come to our website, chuck us an email. If you are a government employee, you have access to Gov teams. You can find me there. And if you are a social media freak, you can find me on Twitter. That's me. Questions, conversation. Thank you very much. I have to very carefully manage the mute and the mute button on two devices. So just very quickly, does anyone have any questions for Nathan? Just before questions, myself, Alisa and I are from GovCMS here tonight. So if you want to come and have a guest with us about anything as well, feel free to use us while we're here. Wonderful. Thank you. It looks like no questions. All good. All right. Thank you very, very much, Nathan. Wonderful to have you join us. I've got it I couldn't be there in person, but I'm gutted I couldn't be there in person, but I'm off to Newcastle on the weekend to visit my brand new grandnephew who was born two weeks ago. So I'm isolating at the moment. I know this is number two. Congratulations. Yes. As far as excuses go, that's pretty good. Well done. Thank you, Nathan. Thank you, Nathan. All right. I think that's basically a wrap. I wanted to ask a couple of little housekeeping questions. I mentioned earlier we're looking at doing this probably monthly or bimonthly moving forward. We'll skip October because we've got Drupal South. Really quickly, show of hands, who is going to Drupal South or thinks that they'll go to Drupal South? Fantastic. That's like half of you. That's so cool.