 All right, thank you. So yeah, first off, I'd like to open and acknowledge Drees for presenting the opening for Drupal South 2021. It was really, really nice to see how humble and grounded Drees is and presents. I'd also like to thank all volunteers and guests for being a part of this new event, in this new format, and particularly under these tough times. So hello, my name is Alfred Dieb, and I am the founding director of Sousa Digital. Is a GovTech company that is really focused on helping governments become more open, more connected, and more consolidated. I'm really pleased to introduce this next session. It's a panel discussion on Drupal's place in the Australian government. So to give some context, among the many responsibilities of our government, our public servants are responsible for delivering us citizens quality information services that is easy to find and easy to understand. Thanks to some key influences, leading digital authorities and digital pirates within government, open source has become a big part of many official digital standards policies and guidelines. You combine this fact with a powerful content management system supported by a highly engaged community. It should be of no surprise that Drupal has become the choice for government in Australia to deliver us our information services. To celebrate Drupal's 20th year anniversary gives me great pleasure to introduce today's government panel made of digital leaders on behalf of the key jurisdictions using Drupal as their whole of government CMS. On behalf of the Federal Department of Finance and Gov CMS, we have Mr. Nathan Wall. On behalf of the Western Australian government, we have Mr. Bill Bell. And on behalf of the fine state of Victoria, no bias, and the single digital presence, we have Ms. Philippa Nihil, aka Pip. And to facilitate this panel discussion is my colleague, Mr. Akhil Bandari. Thank you all, and I wish you a great event over to you, Akhil. Thank you, Alfred, for the introduction of the panel and session, and thank you all for your time to attend this year's Drupal short events. Firstly, I'd like to acknowledge the traditional custodians of ACT, who's where I am, the non-normal people, and acknowledge and respect their continuing culture and contribution they make to the life and the city of this region. So as Alfred mentioned, my name is Akhil Bandari and I work for Solstice Digital and I work with Drupal. So in this session, we're going to look at Drupal's success in Australia and in particular, its rise in government in recent years. As mentioned in an earlier session with Drupal, Drupal is suited well as an enterprise CMS, which makes it ideal for government, especially in recent years where Australian government jurisdictions have been adopting it in various distinct flavors to advance Australia's digital innovation. Now, today we have some of those government agencies represented on our panel to show how Drupal has helped them solve challenges and their users to meet their user needs and to succeed. As Alfred mentioned today, we have Bill Bell from the Department of Premier and Cabinet for the Western Australian Government. And we have Nathan Wall from the Federal Department of Finance and Pip Nehill from Victorian Government's Single Digital Presence Program. Thank you all very much today to take time to speak with us. Now, the format we have, we have five questions that will ask each of our panelists and provide an opportunity to answer them. And you, as the audience, if you have any questions, please feel free to type them in the Q&A feature in the session here and we'll try and answer them as we go along. We'll also leave some extra time at the end of the session to answer some general questions. So, first question for each of you is where did you start with Drupal and what was growth like working with Drupal? I might start with you, maybe, Bill, with Western Australian Government that runs native Drupal for its websites. So, how did you guys start or gives a bit of information there? So, I'm part of the, well, I lead the platform team for a digital government within DPC. In 2016, the state finished and published its first total government digital strategy and, of course, part of that was a citizen-centric services and the state didn't actually have any citizen-centric or one portal for citizens to go to where we were and, for the major part, still our agency-driven so our citizen must go to an agency and then another agency to actually get government services. So, part of that strategy was we needed one portal or at least a couple of central portals. So, we looked around, we did an alpha. The alpha was done in WordPress because we made sure that whatever alpha we were going to develop and then ask our citizens what they wanted, we couldn't reuse. And at that time, WordPress was very security-prone or had security issues so we knew we could never use it. After we got like 7,000 pieces of feedback, we went into procurement exercise and chose Drupal. It wasn't a case of just a choosing Drupal because of its secure, its extensible, it integrates and also its value for money. It was the actual best platform for what we wanted it for. There were pressures outside of our project to go down the proprietary path but the story I have on where Drupal wins the day every time is it's an open-source community and the support for that platform. It doesn't matter what proprietary platform that you have, if you've got an active community supporting your open-source platform, then it's very competitive. So that would be my two minutes for that question. Excellent, thank you, Bill. And maybe next to you, Pip, Victoria has its own kind of Drupal program called the Single Digital Presence, or STP. Can you tell us maybe a little bit about how that started or a bit about that? Yeah, sure. And just first off the clock, then I'm coming from the lands of the Wurundjeri people and I acknowledge their elders past and present. So in March 2017, Drupal 8 was selected as the content management for the Single Digital Presence. I guess our implementation is slightly different to some where we're running headless. So running multiple VUJs front-ends from the one Drupal backend. This has enabled us, though, to consolidate about 54 websites onto VGaVAU and a further 42 websites have been transitioned across into the STP platform. We've got over 500 CMS authors from across nine departments now working and using that platform. We're in good shape, but there have been a few growing pains. We do have clear pathways to upgrade with the security and the liability that Drupal's offering. But sometimes things that might normally have been easy for a standard Drupal implementation haven't been so easy for us. So sometimes it does feel like we fight against Drupal a bit. We now, our headless state means that we now need to put a little bit more effort into things like third-party customizations. Drupal scales, well, we still struggle sometimes with the way it's handling scale from the CMS point of view. And that is kind of our main area of work. For me personally, working in this space now is a real eye-opener after sort of being first introduced to Drupal via a different kind of government intranet about 12 years ago. So at that point, Drupal was very new to us. And after a couple of days or a week of training, I was kind of blown away at that point about its capacity for configuration and the way that it might suit government. And I think we're seeing now with the single digital presence that it really does have the capacity to suit big government implementations. No, it's excellent. It's very interesting that you mentioned, you know, the headless and decoupled architecture that Drew's mentioned earlier, that Drupal has the capacity to do. And it's good to see that some of the jurisdictions are kind of playing on that and using that to their advantage. Lastly, we'll come to you, Nathan. GovCMS is probably one of the more well-known government programs. Maybe you can elaborate on how that started. Thanks for Kil. I'd also like to acknowledge the none of all people as the traditional owners of the land. We quite celebrated our 6th of March live on the plant. In March. And we're now working with it's nearly 100 agencies and departments. And that includes some local councils too. So GovCMS actually provides hosting and the actual CMS tools to basically any government entity that would like to use this. We've got more than 330 sites on the platform. There's another 55-odd sites already in the pipeline. So our growth is ongoing. Has to create and manage some distribution. In the process of retiring the Drupal 8, just showing yes, the Drupal 7 will be around for a little bit longer. But we can centrally manage that code base and it allowed the agencies to go on to the platform to focus on managing their content. It doesn't need the information and not necessarily to have to have the strong technical capabilities in-house. I mean, some of the smaller agencies in particular around government that their resourcing doesn't really allow them to invest in strong technical skills. They're not big enough to actually have that in-house. So the growth is for us has also come from building that strong community around the platform. We are centrally managed, yes. We do things in a central, coordinated way, but we're community-led. We're highly involved with the agencies that are using the platform. And they have a say in what we do and sort of where we go. Growth has been constant, gradual. And the 330 sites live that we've got now doesn't, I suppose, really attest to the level of activity that we've seen in the last couple of years. With all the upgrade work that's been going on from moving off Drupal 7 and Drupal 8, just last year alone, my team launched 145 websites. So there's a lot of activity going on and it's just been fantastic to see. And from all of it, it's going to continue. Excellent, and that's obviously the success of using Drupal for this program. So I guess the second question, and I can open this to anyone, is what did Drupal solve for you and has helped with your program in particular? Anyone can kind of jump in. I might start with you, Pepe, if there's something. Yeah, sure. I think Drupal has allowed for us the very core of what it is that we're doing, that multi-tenancy content management system. It's given us the starting point for that. And that flexibility is a massive, like a massive driver of value for this government, really. It supports a really diverse array of content that meets user needs, while supporting kind of rapidly changing priorities in contexts like, for instance, this current pandemic that we're going through. The flexibility that we've had, particularly over the last 18 months, has just been fantastic. So when that comes down to a case-by-case kind of situation, when we're looking at it, a lot of government digital presences don't necessarily require a website. A lot of them just require a presence. So in that instance, it's been easy. Drupal's enabled us to be able to easily spin up these instances for them on something like FICAVAU. We leverage the workflows quite heavily, so roles and permissions, where they don't work completely in our favor, we've extended those a bit. But they provide us with the ability anyway to govern and apply standards to help improve the information that gets finally published to Victorians. Yeah. One more thing, too, is that it's open-source nature. The intention is that that allows us to kind of stop or limit the amount of duplication that's going on in development across government, that we can harness one good idea and just reuse it many times. Yes, exactly, I guess. The open-source nature is probably one of the strongest points. Let me dive in there, Akil, because Mike's opening thoughts here was open-source as well. One of the reasons why the Department of Finance chose Drupal, this was even before Guff's CMS really was being open-source, meant that the whole procurement exercise was a whole lot easier. And it doesn't necessarily reduce the total cost of ownership, but it allows agencies to allocate resources into more rewarding parts of their activity, the kind of payback sort of value, rather than just paying license fees for software. And we also really appreciated that there was a strong local developer community, government in many instances. And the private sector, as Jerry's reflected this morning, there's a lot of websites around the world using Drupal, so we were able to leverage that to give us access to that skill set that the government doesn't always have in-house. And yeah, like Pip said, there's such a range of sites and content and things that you can do. Arguably, a lot of government stuff is still brochureware, and that's perfectly fine. There's nothing wrong with that. But in the past few years, we've seen some of the agencies we work with do some really stunning stuff. Visualizing data from very... ...stepping the toes in water with things like content APIs. And this is actually helping agencies create services that are easier to find, easier to use, and it's making government a bit more transparent and accountable. And that's always a good thing. That's excellent. And that whole nature of open source, obviously, you can leverage what work has been done across different agencies and then use it within your own site or instance that you need it to, it's really good. And speaking of APIs and things, maybe Bill can jump in here about how you guys are using Dribble. For us, looking at it from a high-level point of view, so we started off being multi-tenanted right away. So we have 40-plus agencies with their entire content and hundreds of a campaign or, you know, small websites, all on the one platform. But what it gave us was... It gave us that single pay portal. It gave us a standardization, WCAG, the look and feel of the site. Well, not everybody agrees with it. Everybody had a say on how that site was going to look. And inadvertently, it helped us start to build whole-of-government operating models and SLAs between agencies. A classic one was, well, our current website does this and you don't. Well, if you just want to upgrade, why don't you invest in that feature for everybody and then we all benefit? So that's where the funding comes from. There's no specific allocation to get things done for WCAG-AU. If they're coming on board and it doesn't have a feature, then that agency contributes and other agencies benefit. The other one was it gave us insights across user journeys and using that silo approach, an agency knows very well how the community is using their website. But having that whole-of-government website, you can see where there's an actual relationship between two agencies and how citizens transact with them. Much like the other guys, I would say that the open-source part was made easier to experiment with whole-of-government. It was a risk, less risk, well, there was less risk because we didn't have to outlay to begin with. But in the last couple of years, it's demonstrated the power of open-source in its community and demonstrated the power of public cloud. And we would never have been able to do this without public cloud and both in its development and also in its management. Since we've had COVID, we have moved from between three and 600 continuous users to six or 7,000 continuous users. And when we have a lockdown event, that can go up to 45,000 continuous users and you see those servers start to spin up and we could never have done that using any other method or approach. So yeah, it's good. Yeah, I'm sure I know you can attest to the usage of some of these sites, especially during this COVID period. So I guess you go for it. I was just gonna say, yeah, the numbers, as Bill said, they're astonishingly high. But yeah, we've had to put some sort of layers of infrastructure around Drupal to, it does give this to that resilience, but if we didn't have the underlying feature set of Drupal in behind that, that wouldn't have been a whole lot more difficult. Yeah, absolutely. So we've heard a little bit about how it's worked for that you, as the agencies, is there any specific functionality that suited your users or audiences, right? Is there something specifically that Drupal grew for your audiences? Happy for anyone to kind of take that question. Can I start this one if that's okay? I'm a little old school when it comes to Drupal and I have to say this, the thought that was ever in Drupal is views. Because you can do so much with it. It can be a little overwhelming at times and for a less experienced site admin or a less experienced content publisher, yeah, it's easy to break stuff because you kind of get it a little bit wrong, but once you figure it out, you can do some pretty amazing stuff with it. And there's a real big payoff there because content editors can just focus on managing the content that they're actually responsible for. If those views are really well-defined and well-built and integrated into the rest of the site, all of that kind of supporting content and landing pages and indexes for things can all be created automatically. And to make the value that that provides, basically the site could almost look after itself other than just I'm just gonna publish my content, here's my latest media release, it's gonna get sort of distributed into the correct parts of the site. You don't even necessarily need to know or remember where it goes. So it's a big powerful thing. I'm actually gonna change tack a little bit though in terms of functionality. It's the reusable functionality. I think Bill mentioned this as well with the sort of the COVID response and you've reflected on this in terms of the consistency that we're getting by sharing and reusing things. It gives government some transferable skills in a situation like we're in now with the COVID response. If government needs to move resources around from project to project agency to agency, the training overhead to do that is comparatively low. A lot of the features in Drupal have a fairly consistent way of working or functioning the interface. Okay, yes, it needs some improvements. The admin interface, like Dries reflected on earlier, yeah, it needs some enhancement, but there's a degree of consistency in there. And it also then means that resources can pick up stuff quickly. I would add to that that if you have that whole of government platform, you can save a machinery of government changes. And one agency saved half a million bucks that are estimated. So yeah, it's amazing how much you can save when you start to add up where if you consolidate into that whole of government looking field, then machinery of government becomes a non-issue. Yeah, absolutely. I mean, the power of the views to be automating things and aggregating definitely is a fantastic feature there. And Pete, maybe from you, what suited your audience and users in terms of Drupal? All of our contents are sampled from paragraph modules. We're using, so our Vue.js front end is calling on that headless interface, but we are actually now starting to see other government agencies using non-Vue.js calls as well. So it's kind of broadening out beyond just our implementation, which is great. The other big win for us actually has been, it's maybe a bit mundane, but it's been the publication feature. So we, a publication feature that we've leveraged off the book module. So across the Victorian government, and I don't think we'd be alone here, there were a lot of PDFs and they came in the form of annual reports, monthly reports, daily reports, minute reports, there were a lot of reports. They were hard to read on mobile and they cost a lot to produce. So we've put together a publication feature based on that book module that allowed long form information to be presented in a more user-friendly way. So since then, we've created 130 publications using that rather than making PDFs. So a good example of that one is the Family Violence Reform Rolling Action Plan that we did, you can have a look at that online. But yeah, that's really saved our bacon quite a lot. No, absolutely. There's a lot of reporting in government and especially with annual reports, it all has to be done. Yeah, yeah, yeah. And it needs to be readable, it needs to be accessible. Absolutely, absolutely. Yes. Okay, no, absolutely. And I guess now moving on to the next question about it, I would say that you guys are experienced power users at Drupal, so maybe some feedback on improvements in Drupal and maybe if Dries is listening, you can listen here. But where do you think Drupal can be improved and maybe you first can answer that if you'd like? Yeah, sure. And again, clocking that our particular instance, the way we're using Drupal, obviously determines where we think it should be improved. But we've spent, we spend a lot of effort in that CMS. And for instance, this year, we've just done a big piece of content, a big piece of work, sorry, around making, I mean, at the high level, it's really about trying to make the creation of content easier for users of different capability. So what we're trying to do is hide little used applications from people who aren't going to use them, but also then trying to make those sorts of things available to people who can use them. So we've done, I guess, a lot of work creating wizards to enable the easier creation of content by, remember we've got what was at 500 CMS users currently and rising. So that sort of stuff, putting in things like a dashboard around the CMS, that whole thing about making the dashboard, the CMS public and the authoring process just a lot easier for people to use. So that's, please, please, anything you can do with that space. Absolutely, absolutely. And anything from you, Bill? Yeah, when I was thinking about that question, it was more around pain points, but I agree with Pip, self-authoring, empowering our authors to do more and be more creative and not tie it to needing developers to give that extra functionality. The improvement part, whatever I say, there's gonna be a module for it. So, and maybe there's too many modules. I, you know, how you use that platform is driven by what value you want out of it. So for me, it is always gonna be performance, even though we have the infrastructure behind pushing it. There's always a lag when we scale and as the infrastructure comes up and from a technical point of view, it's the telemetry that logging, the more logging the better, the more we can get ahead of any potential issues. The more time we have to resolve that is gonna be helpful because as we have found out, we moved from an informational website where we could be done for hours and I don't think anybody would have noticed to where the premier is on the phone to my boss within 15 minutes asking why is the site slot or where is that document? So it's, we've moved from something that was governmenty to where people complain if it's that. So it's, yeah, I don't know what to say, more instrumentality so that we know that there's gonna be issues coming up or we can fix them better. Absolutely, excellent. And Nathan, any? Yes, Joris, if you're listening, bring on Clara, please. Absolutely. Sorry. Another comment, I'm gonna reflect on paint point again because sorry also, if everyone's asking, this is Cesar, he's my cat and one of my off-siders. Web forms. So I'm gonna give you a user story. As a site admin, I need to set up my site to collect personal information from citizens. I want to use the admin UI to configure a separate production database where the information can be stored so that when my developers clone the live website to work on the next feature I've asked for, there's no need to sanitize the databases, they don't get access to it in the first place. Now, this is entirely possible today but it relies on a bit of a heavy technical solution maybe integrating with a third party CRM or some other kind of tool set. And that's really good for heavyweight transactional sites that have a lot of incoming queries or it has to connect to a really solid workflow. But governments also got a lot of stuff that kind of falls in between forms on our website. Yeah, they're relatively straightforward but we've got a lot of government agencies and programs that need to collect information, do it securely and sometimes it's kind of personal sensitive information as well. And doing that in a way that kind of protects the information is still a little problematic and wouldn't it be great if a site admin could just with some basic configuration inside Drupal rather than relying on developers, build a web form pointed at the secure form repository and also have the ability to say who's got access to that data. I mean, that would be pretty amazing. Yeah, I mean, the first thing I think of is the heavy assay, everyone almost all government agencies have to do a consultation at any one point in time. So yeah, that's definitely, definitely interesting point. I've got a couple of questions from the audience. Got Lee Rollins, can each of the panelists talk a bit about their strategies for investing back into Drupal? It's an excellent question, considering that it's open source. Yes, anyone like to take that question first? Maybe Nathan, it's a bigger, bigger. I think for us really it's about encouraging the community that we're working with to be part of that. Pip, you also mentioned it where agencies that are creating functionality, it can be shared. Well, we're trying to encourage that as well. We're talking to agencies regularly because we know that even our current platform doesn't have all the features that it needs. So if we can approach that almost like as a, I wouldn't say a single cohort but as a coordinated cohort of agencies, maybe we can build a feature once or maybe we can enhance a module and do it once and leverage the expertise in the technical community still but then make sure that if we're creating something, it's done in a generic way. So this is one of the things we always encourage our agencies, don't create custom modules, even if you're a Paz customer and have that ability on our platform, create it in a way that you could actually put that on Drupal.org and let others use it or don't go off and create something custom when there's a perfectly good module out there that with a slight enhancement might actually sort of complete your requirements set. Yeah, exactly. Open standards and reusable, thinking reusable as much as possible, absolutely. Pip, do you have any questions at how? Yeah, no, I think, I mean, certainly to that point of reusability and the notion that we would stop duplication completely because I found myself saying it earlier, just earlier. And I think the idea is not that we will completely stop duplication but at least clock that it's happening and where it is, then you guide it a bit towards these patterns as both Bill and Nathan have been mentioning, that we can see, ah, okay, Department A needs this and they've done that. Department B, wow, they really urgently need this thing so they have to go and start building tomorrow. Quick, get them to do that but we think we're heading towards C so why don't we ask them to build it a little bit differently so that it can get there easier? So we kind of then have, because we're using shared technology, we can have a shared vision and bring our knowledge and experience to bear and build, hopefully, better things that then, yeah, can be reused. Absolutely, and I guess, being as it's open source with Tripoli, anyone can use any of the work that's been developed by government. So let's definitely keep track and Bill. So now we deliberately built our own workflow module and we were going to give it back to the community and then we saw that there were better workflow modules out there and they scrapped it. So we would love to, but we're a consumer of a Drupal. We support Drupal, that's why we're here today. We invested in companies in Perth, Australia, and in Victoria because we see the value of Drupal. Nothing brought up a good point. While I know that there's Drupal government groups out there, I don't really have an understanding of how they collaborate. Well, we collaborate with Victoria and APIs of me collaborate with the federal government with regards to identity and it's very active. So it actually triggered me that, yeah, we should actually work together to at least design the stuff and be aware of what each other's doing so that then we can either build it ourselves or build it for everybody else. So yeah, thank you for that, that was good. Excellent, excellent. So at the very least, we've got more jurisdictions talking to each other. So we've got another question from Drew Robinson. He's mentioned Bill, I've worked on Drupal in WA state government as an agency that was uninterested moving to Drupal. I'd be interested to know if there's any strategy on how to increase engagement of some of the more resistant agencies. This is probably an interesting topic about this. We have many panels. We actually have a policy where if an agency spends more than 100,000 then they need to go for an exemption before they could not come onto the platform. That's one way. But then we see that some agencies might be extending the length of their website or breaking their projects down into small components and thus they're extending the life of that website. The main one is that we're getting momentum that people are coming on board because it's cost them too much to run outside of the platform. They have to justify why they want that extra 300 or 400 or 900. In fact, one of them saved 930,000 a year just by moving onto the platform. So it's becoming harder and harder and the message is a lot easier since COVID. So we have the DGs, the governance around how we operate. The DGs are starting to talk about well, why aren't we on it? And it's only the technical arguments that are coming back. They should start to break down in the next couple of years. Excellent. And just jumping back to the Contrib question there, I guess, is obviously there is Contrib between the different jurisdictions and the work and the programs that they have, I guess, is how do you see if there's any savings that agencies are receiving because they're obviously building within their modules? Is there any way to kind of give back to the wider community, right? If there's a savings there, is there some way to contribute directly back into the Drupal community? Is there anything that you guys have in place that could give back to the wider community rather than just the programs that you have there? Okay, I want to find out if I'm going to find out. That's a neat question. Well, yeah, so I guess it's more about that. Do you have requirements about and vendors to contribute back directly to? So vendors maybe contributing back to Drupal and not just the agencies? We've certainly taken that approach with some of the engagements we've had with commercial suppliers where maybe they've volunteered to contribute some hours in kind to maybe reduce the cost of a project but actually progress something. And obviously we're always amenable to that. The whole question of savings is a complicated thing for government because often it gets tied directly to their budgets and for us directly, we're not actually interested in scooping up their savings. We would rather see them take those savings and invest them somewhere else in their program. If anything though, what it may do is give them some extra resources to actually do some more work and maybe that's where the investment back is. It's like they're actually able to progress things a little more than if they didn't have those savings in the first place. And it's sort of, I think sometimes it just comes down to where your focus and your effort is. So I think we've found that we have been able to contribute back on an ad hoc fashion. Like it's no dedicated program of work but we have been able to build patches and fixes for the modules that we use. And as you're building and working on stuff if you see something that you can easily fix then it does, we are able to put that back in. But like I say, I guess it's because we've got a consolidated piece of work going on in this space. And I think that as we see the uptake sort of for instance in Victorian government as we see that uptake kind of spread across the government we'll start to see, I would hope and expect we would start to see more of that because it's just the nature of the game. The nature of the open source game you see the benefit from being able to make the most of the great work that somebody else did six months ago and you go, oh great, I like that. And that's our great starting point. So when you've done something that's fixed some bug you kind of go, oh, somebody else is going to want to use that, we'll put it back. Excellent. That's right, exactly. Now we're just looking at the time we're going to go to our last question I guess. And so more about looking forward now and what are you guys hoping to achieve? And maybe, otherwise, what potential threats do you see to droop or within the government in the longer term? A bit of a curveball there. Happy for anyone to take that. Oh, I'll give it a go. Yeah, go. I'll give it a go. So I'm going to think about that curveball while I can. So in terms of us for the future, we're at a point where we're at a next stage of expansion. So that's very much our focus. We're all about establishing those patterns because they'll work for us. They'll save us time, they'll save us effort. They'll hopefully help us implement better things. So we're looking at wherever we can, we're using existing government infrastructure. We're forging the easiest connections that we can to those things. So we're using APIs. We've got our whole of government API gateway and the great work that's being done there. We've got incredible geospatial services being provided by DELP, the Department of Too Many Letters. And we're using our core products like Datavik to kind of both promote the use of open data, but also it's our main sort of funnel for the dynamic data that we bring into our visualizations. So setting up those patterns. I mean, they're patterns with partners, I suppose, but as well as with the code and with the modules, we're doing the same, just looking for patterns. We've just recently been working on a new pattern, a new data visualization pattern that's really just, we're calling it a location finder. So we're knowing that Victorian governments and governments all around the world always have services that are in a location and people need to find it. So when I need to find my bushfire recovery center, when I need to find my COVID testing hub, when I need to find my thing, we'll use this pattern. And that will be the pattern that will give me a map, give me a list, give me an accessible, usable thing that I can use on my mobile while I'm out on the street. I can use my desktop. So patterns, they're our way, that's what we're doing for the future. I think the other thing that we'll sit in support of there is a real extension of this developer community for us. So we've got a roadmap and we can only fit so many things on that roadmap, but we know that working with departments, they're gonna, we're gonna come across many things that we can't help them with. So we encourage them to work with developers to build. And this comes back to this idea of reuse and collaboration that we're talking about. So we're really gonna be putting a lot of effort into the development of that community over the sort of coming period. They're kind of our two big things. Excellent. And Naysa, maybe to you about the future, I guess. Well, yeah, the future is a little uncertain, isn't it? Our roadmap has, to be honest, it's slowed down a little bit over the last 18 months. The whole COVID response has been our top priority and the resilience and uptime of the current platform has absolutely been in front of mind for everybody in the team. Really pleased to hear Dries and his remarks this morning about some of the things that he's looking at in broader priorities. Scareally, they kind of align to what's on our roadmap at a big level. So content personalization, government doesn't have a lot of experience really doing this. So we're looking at how do we start small? How do we kind of figure out some of the patterns that need to be useful to make it work? APIs, a lot of agencies are talking about how they use APIs for content aggregation and content consumption. Again, they don't necessarily understand how to go about doing that. So there's a lot of work to happen in that space. That overlaps into the whole headless CMS implementation. Dries now that exactly, I think this morning where he said, you know, you've got that content repository and you're using that content in all sorts of different places. And it's like, that's one of the powerful things that Drupal can enable. So we need to tap into that. And I'm going to answer your curve ball a little bit to Kil. It's not so much a threat to Drupal, it's just a threat. And that's the changing cybersecurity landscape. We are witnessing very dramatic shifts in cybersecurity, dare I say, malicious activity in a couple of places. So front of mind for us is, how do we stay in front of that as best as we can? And we're looking at things like static rendering of our content. So using Drupal to manage the actual creation and distribution of that initial content, but then statically rendering it so that you sort of put a few more layers of defenses in before you actually get to anything close to your database. Now, we had some ideas on how to do that, but it's still some time off for us. Excellent. And now with about 30 seconds per minute, Bill. Okay, I'll be very quick. We have a program of work for 11 digital strategy, digital platforms. Drupal will be the content delivery of those two of those platforms. The threat to Drupal for us is that it's a Swiss army now where we can do anything. And we as an organization need to define what it's going to do rather than, so we've picked any unstructured information and we're gonna put our structured information in our CMSs and our bigger databases. We did find that we were using it for everything which was bad. Excellent, that's great. Now we've kind of run out of time to open up to general questions, but I'll start wrapping this up. Excellent, thank you very much all for your time. Let's quickly check if there's any questions on the Q&A. Yep, okay. And so that's all the time we have for today. Thank you very much to the panelists for sharing their insights and experience on Drupal. Clearly, Drupal's not gonna be going anywhere soon for Australian government at least. And if you have any questions or you'd like to chat to the individuals here on the panelists, just please get in touch with them after the session. And I think we've got a, let's take away now. Yes, ready to thank you very much everyone and enjoy the rest of your Drupal event today. Thank you. Thanks very much. Thank you. See you. Thanks to Kil and thanks to Solstice Digital for bringing us that panel session. Coming up next is our hallway track. And this is something a little bit different for us in the conference. While most of us are sitting around here in our bubbles, here's a chance to virtually get out and about and meet some of your fellow conference people. There'll be 30 minutes of hallway track coming up. That's three times 10 minute sessions with breakout rooms for small group chats. To get in there, simply exit the session, click into the hallway track and join the conversation. And thank you, Heaps, the team at Morph for choosing to support this activity. Really awesome to support community and collaboration. And we appreciate you making this one possible. So I'll see you there.