 Hi, everybody. My name is Josh Wahey. Nice to see folks again. I'm a director at Acquia. I work in the product management organization. Although I've been with Acquia now for about seven, seven and a half years, for the longest time as a technical account manager, moving to product organizations being sort of a pretty new move for me. Today I wanted to talk about the state of Drupal 7 Exodus, as we've sort of been seeing it from our side. Drupal 7's been with us for like a really long time, pretty much a decade right now, which is crazy. I think there's probably a number of us that are a part of the Drupal community that maybe remember when Drupal 7 came out, which also speaks to how well we've been around. I joined Drupal in 2007 and started contributing to the community. Got my chance to contribute to Core as part of the database layer in Drupal 7. Got to celebrate that at Chicago in 2011 when it went live. It was kind of the same time that the internet really kind of took off in a whole new way. What I mean by that is just kind of give some people a walk down memory lane of what it was like way back then. The iPhone 1 had just come out just before Drupal 7 had landed and things like Google Maps on your phone didn't exist yet. There's like a real kind of testament to what was going on. The big thing, I think shortly after Drupal 7 landed, was things like sharing and embedding social media links onto your website. A lot of user traffic was driven by people coming to your website and then going from your website over to social media to engage or by liking posts that you were having, things like that. Of course now the world's pretty different. We've got things like mobile first and headless strategies that came much after the release of Drupal 7. Yet why is that all kind of significant? The real reason for that is, let me get to my slides, this, which is to say that Drupal 7 is still incredibly prevalent today in the industry. I think that speaks to a couple of reasons for that. One is we had really long development life cycles back then. It was about four years between Drupal 6 and Drupal 7, another four years between Drupal 7 and Drupal 8. There was a lot of opportunity for the adoption of Drupal to get onto Drupal 7. Since then, it's been slowly adopting towards the 8 slash 9 architecture, but a lot of this community or users of Drupal still sit on Drupal 7 today. At least that's what the Drupal org data tells us. This is a graph of Drupal weekly project usage by core version. This is literally taken from today, so you can still see there's quite a substantial portion of sites to the reporting Drupal 7 usage. This may not be entirely accurate. There's things like maybe people using the update module as much as they were in 7 because of things like Composer, but still points to a relatively large amount of Drupal 7 usage. When we look at other measurements in the market today, builtwith.com finds there is about 313,000 different Drupal 7 sites out there in a production capacity. Even though all data might report things like other non-production environments, there are tools out there that can identify Drupal 7 sites and see that there's still a lot out there. If you think about the kind of cost to upgrade to Drupal 7 for all of those sites, it's somewhere in the vicinity of about $4.6 billion. You put that into the context of an end of life. That's about the amount of money customers are going to spend getting off of Drupal 7 in the next 12 to 36 months. We have this challenge that this tells us. If we think about how many of our users use Drupal 7 today, keeping our Drupal 7 users requires us to find better ways to help them get to Drupal 9 or 10 because it's the best CMS, the easiest, and the fastest path forward for them. I think that is the real focus that I've been thinking about and how our customers get off of Drupal 7 is where do they go? When you think about moving off of Drupal 7, because it is a migration and because it has been potentially a decade since you last looked at refreshing the CMS, Drupal 9 may not be the only option available. This is also a really big risk to our community because it may be that some of those people go to other providers and further diminish the usage of Drupal across the internet. This means to us as a community we have a stewardship role to play with the Drupal 7 users to help them choose Drupal 9 and to commit to a migration or an upgrade path to get from 7 to 9. In order to do that, we have to show how Drupal 9 is the best option in terms of the cheapest option that provides the best value and we can get them there in the fastest way. This is the plan that we're putting together at Acquia on how we can help customers achieve that. Not just customers but everybody in the Drupal community. Number one, we need to help Drupal 7 users plan their upgrade path. It's a really difficult thing for your migrations in general. It's filled with a lot of unknowns. It can be tricky to know there's often a lot of data that doesn't need to migrate or work you through a lot of things like that. We've helped in two particular ways there. One is through an automated migration assessment. This assessment looks at a Drupal 7 site and it helps quantify the data that you need to migrate. How many content types, the volumes of data that's published and unpublished, taxonomies users, views, blocks, all of that kind of, the common data that you'd be familiar with inside of Drupal, helping quantify a lot of that. Showing which parts Acquia Migrating Delerate will help migrate and which parts won't so that a conversation can be had with partners, with internal dev teams or with business about what's left over and how we would go about migrating that. Acquia has also had a lot of community contribution on the upgrade path and that's by-large because of the Acquia Migrating Delerate project. That project has helped identify migration paths for a lot of different modules in the community and it's helped provide a ton of patches into the community to help support that migration path as well. Those of course are all available today in the community as well. The second part of our plan is to make sure that they, the customer, has the resources to execute. We want to help our customers figure out how to support the resources they need to have by building a partner accelerator program. That's really around a specialization in Drupal 7 migrations, making sure that we have competent partners that know how to do that. The second way we do that is by providing Drupal 7 LTS long-term support or VES as it's known in Drupal.org, which is vendor extended support. That basically gives customers a longer runway to be able to get off of Drupal 7. If they can't hit the end of life in November 2022, there is a much longer runway that's currently planned out in 2025 that will help give customers a longer time to figure out how to get off Drupal 7. The third part of the plan is to speed up execution by automating what is common. Again, that is a lot to do with migrate accelerator and being able to, if something is migratable for one customer, we can do it the same for many customers, why not automate that and make it common. As our customers use our tools and discover new things and new challenges, we look to take from those learnings and put them back inside of the tool. There's also Acquia Site Studio, which is a site building tool that uses load code as I talk about, or really it's like another way of empowering less site builders and less developers, but more people in the content creation space to be able to build and control the site layouts by having a predefined theme that they can build from inside. That's also another tool that's available to customers who want to be able to rebuild their presentation layer, which they'll have to do as they move from 7 to 9 anyway. Finally, make building with Drupal fast and powerful. That's something that I think Acquia has been committed to for quite a while now with the Drupal acceleration team. That's a team at Acquia that commits 100% of its time to the contribution of Drupal projects. That's largely things like Core, where we help build out some major features of Drupal Core, but it's also in the Contra space with the Acquia Migrate accelerator program as well, which helps contribute a bunch of contra patches to help the migration off of 7 to 9 as well. Another way that that can be useful is through Acquia CMS. We know today that compared to Drupal 7 and the type of websites we need to build back then, the sort of ecosystem that marketers need to build on is much, much greater. They need not just a Drupal site, they need to have lots of other tools like personalization, data analytics, all kind of integrated to the website and feeding into other systems as well. Acquia CMS is a useful tool for customers who are wanting to leverage more of the Acquia platform and easily connect into a lot of those other products that Acquia provides. So here is also another way of looking at our current strategy for helping customers upgrade from 7. So there are ways to think about it. Where do we help in upgrade planning, and upgrade execution, and how do we help in rebuilding and modernize? And then there's the three dimensions here about reducing cost, reducing time, and adding value. So the three assessments making those automated and bringing in the partner accelerator program is going to help customers and some of those 300,000 sites out on the internet figure out ways of getting off of Drupal 7 and doing that in a context that sees them through to Drupal 9. The Migrating Data Rate Program is then designed to make sure that getting to Drupal 9 is faster than migrating to some other CMS or some other project and really reducing the cost of the migration of the transition for customers completely. And then finally, the rebuild and modernize, and that's the option of using something like the Site Studio or Acquia CMS to help leverage some of the more modern functions and features that are available today opposed to a decade ago in 2011. So lastly, maybe if you have looked at any Acquia Migrating Generator content in the past, you have seen something like this before, which is when you think about planning your migration, or at least a customer thinking about planning a migration, you will see something like this. You could spend about 25% of your time in analysis and planning, 25% of your time across DevOps and data importing, and then 50% of your time reprogramming business logic and presentation. What we're really trying to aim for here with these sort of improvements and focus on the migration strategy, there's something more like this where we can reduce a lot of time and analysis and planning by providing some upfront analysis, how to start a conversation, being able to migrate or support the migration of a large number of contract modules that a customer may already be using. Then we'll also help speed up the import process by providing a nice UI and self-managed capability through Acquia Migrating Generator, and then also providing Acquia Cloud to help handle your DevOps architecture. Finally, in terms of improving the business logic and the presentation layers, business logic can be a really difficult one to say how we can optimize it because it is very bespoke to the customer, but an Acquia certified partner is someone who'd be able to help navigate through that one quickly. Then Acquia Site Studio is a potential option for being able to expedite the presentation layer if that's the right direction to take for the use case. So kind of wrapping up now, Drupal 7 is end of life, as I mentioned, November 2022. The commercial extended support is through to end of 2025, on November most precisely, and that's the VES program vendor extended support. You can see there's no Drupal 8 on here because Drupal 8 of course is now end of life and we have just Drupal 7 and now Drupal 9 with the event of Drupal 10 coming out in Q2 of next year. So we're here in the sort of pink square and there is kind of like a small or a closing window on this opportunity for getting these 300 plus thousand sites that are Drupal 7 sites on the internet, be able to bring them across into Drupal 9. If you have any questions feel free to drop them into the live Q&A or discussion forum, happy to take an answer of those now. If you wanted to get in touch with anybody about the PART program, how to work with customers here in APAC getting them from 7 to 9, it'd be great to get in touch with either our country manager here Keith Pettinger or a partner manager at Korean Condor. I'll answer Q&As in the in the discussion forum but I will pass now over to Murray to go forward with convening your CMS. Thanks Murray. Okay thanks a lot Josh, that was a really great presentation, I enjoyed that one. So yeah just a quick reminder there if you would like to ask Josh some questions please do that in the live Q&A and I would also encourage you to do the same thing for my presentation as well. Please just ask away and I'll answer at the end. So okay. Welcome everyone, my name is Murray Woodman, I'm the managing director at Morft and we're a Sydney based Drupal agency. Thanks so much for coming along today to find out a little bit more about Convivial CMS. Convivial is a starter website that we use at Morft to build out our customer sites and I realize today we probably have two kinds of audiences. Well that's what I thought when I was writing this speech but we probably have one kind of audience really that is the Drupal developer. So maybe you guys are more interested in finding out about some of the patterns or techniques that we've used and certainly I'll be running through some of those things as well but if you're a potential customer who's interested in some of the features of Convivial I've got a very sort of quick demo of a couple of its features to have a look at. So what is Convivial? Well it's certainly not a cookie cutter site where we just install it and expect you know one one distro to solve all problems. It really is a set of techniques and patterns that we use inside Morft and so it's fair to say that you know as the years have gone by what we do is we continuously improve the way we develop Drupal websites and of course this is not an unfamiliar thing for Drupal agencies certainly it makes sense to have a little toolkit there of all of your best practices. But when we're developing Convivial because we are using it as a set of techniques it means that we're able to implement different design systems on top of that. So for example on the the left hand side there we have Bootstrap 5. This is our latest and greatest version of Convivial and you know it allows us to utilize any module we want and this is really where we're road testing a lot of our personalization and customization features so that really is the cutting edge of what we're doing. But we also have other versions of Convivial as well so we've got Convivial for GovCMS over on the right hand side so that's a GovCMS9 SAS implementation which uses the Australian Government Design System almost recently as it's been forked to being called gold so we do have a GovCMS9 version they're ready to go if that's if that's what you're looking for. And then most recently you know for the New South Wales Government they have the New South Wales Digital Design System. They're currently on version two of that and we do have an implementation for that. Version three will be released soon and we're currently working on doing a full version three implementation of the New South Wales Digital Design System. So hopefully you can see that yeah it's not really a one size or it's just sort of one distro it really is you know a collection of best practices that we have and we can roll them out to different design systems but yeah it's fair to say the one on the left that the Bootstrap 5.1 is where the most activity is. Before I jump into the demo I would like to just touch on a few different sort of layers and these are the things we're thinking about when we're trying to build you know a starter kit because you're not really trying to solve a specific use case you're really trying to design for something more generic in general. So you know at the top we have the style guide or the branding of the organization and this is where color palettes and typography and these kinds of things are defined you know as a thing it exists on its own and it's specific to the organization and on top of that we have the design system and this is where the patterns and components are defined from small things like atoms like buttons all the way up to organisms such as you know full page templates. We really like using design systems because you know it makes this process you know a whole lot better you're standing on the shoulders of giants and you have you know a known sort of set of functionality that you can target. Coming down into the implementation section this is where Drupal fits into the picture I'd like to break that up into two parts you know the first one is fairly obvious that's the structure how do you you know implement those components and of course they're going to map fairly closely into what the design system is offering but I think the really interesting area is around the editor controls or what I call degrees of freedom you're able to look at the style guide and the design system and work out which parts of those you want to expose to editors you know what's going to give you know an editor that expressive freedom to tell the stories they want to tell and how can you provide that freedom in really easy to use you know options that their editor is able to select so that's very much part of our philosophy is morphed is that we're trying to you know build an editor experience you know based around configuration rather than necessarily a developer or a theme sort of driven way of styling sites. Okay and then some principles here so you know I've I've spoken about this kind of stuff over the years cross-cutting concerns and these really the things that run across all of your content types in the website so I think if you can nail all of these things you're really you know building a system that is going to be scalable for the future if you have consistency and you know coherency with these you're going to have a system that will be able to scale out to easily add in new content types and to you know build build a site based on a very solid foundation some of them are to do with content modeling others are to do with you know components but these are all of the things that you've really got to get all working together. The flip side of this is that we avoid vertical concerns so convivial is not a a solution in an individual vertical it's not really solving one particular application it is just a set of sort of common patterns that we're using. I'm a firm believer in that each site each project has its own problems and they need to be solved in their own way and the way you do that is through content types and taxonomy so we really make no commitments to content types that's not what we're about and in a similar vein we have when we're working with the different components that we're implementing I'm calling it pattern smell here but similar to you know code smell you can basically look at a piece of code or a component and work out you know is that making sense is it consistent you know is it breaching some rule and I think when it comes to snowflakes or you know oddities I think if you see those things that's a time to pause step back work out you know if you can generalize it if you can encapsulate it and then finally can you then expose that to the editor to you know to build the sites that they want I'm bringing up freedom and safety here as well because these are two guiding principles about you know how we've built convivial both of them are good things right you want freedom and you want safety you know you know it's a little bit like the welfare state and democracy you know they're both good but there's a balance and a bit of a you know tension there sometimes another way to look at it is you know how can we give editors enough rope but not quite enough to to hang themselves so yeah on the safety side of things these are all the things we want to guarantee in a in a distro right and we want to make sure the site is on brand accessible responsive secure consistent and performant but we also don't want editors to feel that they're in a straight jacket and can't you know build the kinds of content that they want so each of those things on the right are essentially you know the degrees of freedom that we're able to open up to editors you know based on what is in the design system and in the and in the style guide so yes there are a couple of sort of principles that we're doing in the demo I'm about to show you and I promise I will get there eventually what you're going to see is convivial which is a start of the kit that morphed uses on its own client projects but I really do want to say that a lot of the stuff we've developed over the years has been released as open source so each of these modules here are things that we have released and this really does form the core of the way we sort of build a lot of our sites so the first three you see there they are really all about separating presentation from content and that's probably the first phase of convivial is working out how can we make a that really good editor experience each one of those three modules is in GovCMS by the way and this does allow us to build GovCMS sites the way that we do the final four modules that you see there are really more around personalization and customization we're particularly proud of the work we've done on Personified and JSON template because this allows us to do deliver personalized experiences and we'll see that very soon as well as Rekombi and Sejari Rekombi is an AI powered recommendation engine it's a really easy way to get up up and running with item recommendations to your users and you'll be seeing that very soon as well so yeah there we have it sort of the two phases of what we've been delivering with convivial so yes we're there now this is the demonstration and I'm going to show you guys two things firstly the editor experience and you know secondly a little bit around our personalization so we're going to flip over to the convivial demo site now and what you see here is a test or a demo site of a bookstore and I've chosen this domain because you know books have topics and they have audiences and authors and there's there's quite a few dimensions there which around which we can personalize so I'll be showing a little bit of the personalization soon but before before we do I will just go in and show a tiny bit of the editor experience so here we are in the back end I've just created a very simple page here called demo and the demo page is a very simple listing of what we're calling big teasers right so fairly fairly simple design this has been built with a paragraph called the node list so we're going to go in and have a look at just how that's working so I'll just scroll down to the components here now what you're going to notice immediately is this UI looks different to the normal paragraphs view of the world paragraphs UI is usually all around form elements and nested form elements essentially what we have here is the layout paragraphs module in play and layout paragraphs has two main features the first is that it allows you to embed different layouts into your paragraphs so you can kind of think of it as like a little bit like a section in layout builder but that's the way you know we can inject layouts into paragraphs but the other really cool feature is that it does have this whizzy wig kind of experience so you're actually seeing the rendered entities here of these nodes in the node edit form and for me that's a big win I'm a believer that editors should be working in the node edit form not necessarily in an overridden layout so let's come in here and edit this so as we see this is our demo content for a node list I'm going to hide that heading and here we have the content here now we're not going to change the content the content is important what we're worried about here is changing the presentation so these are what I'm calling the degrees of freedom so the first one here is we've got a view mode okay this is a big teaser let's change that to an image card now this particular field here is handled by the entity reference display module one of the open source ones I mentioned before then we've got the color palettes right so let's change this to the light color palette so this color palette is defined in the style guide and it's been implemented here and this has been done with the entity field sorry entity class formatter sorry about that this is the entity class formatter handling this this will just drop a class onto the entity and we're also using another similar approach here but we've got you know some styles that maybe we want to show or hide on this particular one here we're using the breakout class to break it out of the container we have a layout so rather than doing alternating items let's let's have them as thirds okay so we've configured a few of those options up there we click save on that and you can see that the the display is immediately being updated that's great editor feedback good user experience to see to have a preview of what that's that's going to look like so we'll do save we'll come back we can see we've we've got our node list you know the the content is broken out of the container we've got the light gray background here we've got the changes in the layout we've got the changes in the view mode so these are all the different dimensions that we're exposing and these dimensions have come from the design system and the the star guide and they've been implemented and this really is our main aim is to take those dimensions and to to expose them to editors so really that that's just a quick sort of demo of some of the principles that under underlie convivial and how we've you know approached the building of it flipping over to the the home page now we're going to have a look at some of the personalization features so you know one of the goals we had with convivial was to build a site with a home page that was 100 percent personalized now you may not want to do this on every every site you build you may only want to personalize one or two blocks but you know here we've kind of gone a bit overboard and and we've done it for absolutely everything so before I just show you the page I just want to show you that this is a little bit of the stuff that's going on under the hood so essentially there's some local storage variables that are being stored on this page and we've have like essentially user context that's stored there locally and each one of these variables is driving what you're about to see on the on the site so for example I visited this site at 212 times and the system thinks okay that's pretty high experience this person likes the site so essentially this tag is then able to drive the experiences that we're going to see on the site we have an ip geo geo ip lookup it knows that I'm in Australia it knows it's therefore spring and you know that's able to to you know drive you know the time of year and just interestingly here we've we've sort of got some affinity kinds of topics here where the system's able to work out you know what topic I'm interested in and what audience group I'm interested in so if we have a look at what's going on here this top block is driven by the experience level so you can see I'm on the high experience level but it's saying hey why don't you go to the next level and you know get in touch with us basically so there's a bit of a call to action there these next promo blocks are based around the affinity we have so this one here is based on my topic affinity it knows I'm interested in sci-fi so it's going to you know basically promote some sci-fi stuff to me uh likewise the second one here is an audience affinity it knows I like youth content therefore it's going to serve me up a youth block so all of this stuff that you're seeing here is um you know done in a decoupled way you know with javascript on the client side getting that context and and pulling the content out of Drupal the next block you see here is all around recommendations coming out of recombi which is a you know recommender as a service recombi has taken my click trail across the site it's also taken the click trail of everyone else has been on the site and it's worked out what I would be interested in so if you have a site with a large corpus of information that's um you know got some metadata attached and you would like to use the wisdom of the crowd you know recombi's a great a great approach for that um finally down the bottom we have a block here promoting um something to do with spring hey at spring why don't you come out of hibernation so this is giving you an idea of you know how you can have that kind of call to action so yeah that was a very quick run through some of the personalization features there it is important to note that um there is some pretty smart javascript under the hood working out this kind of stuff you might want to think of it as like kind of like a cdp light you know written in in javascript it's basically uh sort of a very simple way relatively simple way of keeping track of this data to uh to personalize the experiences okay so coming back back to the presentation I'm almost at the end so get those questions ready everyone um so let's just look to the future you know I think you know Drupal's 20 years old right and this conference is all about you know reaching that milestone and looking ahead so Drupal's come from the area of the era of the CMS but I think it's it really is moving into the next era of the cxp that's the content experience platform where Drupal's not just used as you know a manager of of content as a CMS but it's actually serving out experiences to different uh different channels and by taking this decoupled approach and by having sort of the concept of different channels uh different audiences and different topics we're able to you know get Drupal to operate in this cxp kind of way and I really that's what the next phase of convivial is going to be all about it's it's building it out as an omni channel content experience platform and so you know as development proceeds on it you know we'll be working out building out some more of those kinds of features so that's it that's um my presentation um there I'm pretty easy to find on the the web um my net my handle is Murray W so I'm on the uh the Drupal Slack Twitter and uh Drupal.org uh with that handle I'd love to uh you know hear any questions uh that you've got there um of course you can check out uh convivial CMS on the morphed website as well if you'd like to um do that I'm just looking at look at the time it looks like we've got nine minutes up our sleeves and uh I really uh appreciate that time so I can answer a few of your questions so I'm just going to come back now and uh hopefully I'll be able to come in and see what questions you guys have been asking there and I encourage you to um ask away so I'm looking in the uh the Q&A there I'm not seeing any any questions bubble up but I will uh check the form okay nothing in the form so if you guys have any questions there please please drop them into the forum or the live Q&A and I'm happy to answer them uh there's one in the live Q&A thank you hi Lee thank you how do you feel about layout builder and paragraphs so we are using layout builder and paragraphs um thanks for that one uh Lee um and it's you know if if you look at what morphed has done over the years it's it's really been hilarious you know we we started off with paragraphs and then we went to panels IPE and then we flipped back to to um to paragraphs then we went to layout builder and then we've come back to to paragraphs so um we've really enjoyed implementing everything twice as a block and a paragraph about four four times in our history um but yeah our current recipe is using um layout builder you know we do enjoy using layout builder as essentially what the site builder is using across the view modes um but I do prefer to use paragraphs for what the editors are working with on the node uh node edit screen so like we're sort of happy with that layout paragraphs module and the experience um that's got I I do think it's better for editors to to feel that they're in that node edit form rather than doing things presentationally um in layout builder but you know I understand people have different opinions on that but that's really where we've sort of landed on that one and Bevin is information for these features processes available are there particular modules we can have a look it's probably dangerous me reading the questions out live Bevin you could have put anything in there and I would have read it out um well yeah so the I mean those modules that I've I've I've listed in the presentation you know have been released as contrary and I've I probably have presented on them um uh you know various conferences and uh and things like that over the years um no doubt the documentation could be improved on some of those um um Bevin but yeah that's what I'm trying to do here is yeah show the way uh we're uh addressing some of these things um that there's a whole stack of other modules that we are using for editor experience as well which I really didn't get to to touch on um for instance the the moderation sidebar you may have seen that up the top right hand side that's a pretty cool module I can't believe you know that's not on every single um site as well so you know there are yeah a number of contrary modules out there obviously that do improve the editor experience okay um so I do have another question here can a history of transactions and purchases when integrated with CRMs or Salesforce be used for personalization as well as navigation so yeah this is a really uh interesting um one and you know that that's something we've actually been looking at at Morph we're looking at releasing a module called enricher which is actually a connector between things like CRMs and um marketing software you know down into Drupal which is meant to act as a bridge you know going from one down into the other so we can get access to that user profile so I think yeah pulling that profile out of you know a secure store and bringing that down into that local storage and being able to personalize around that is definitely something we want to do I don't really want to see content stored in Salesforce or a marketing software as a cdp and then just getting injected into Drupal in a dumb kind of way I want to see Drupal being the first class citizen for managing the content and being able to serve that content from Drupal and for me the aim is to try to get that profile information from the CRM down into the down into Drupal so that is an open source module we do hope to release that um you know in the near future um but you know of course you've got Salesforce you know integrations and things like that that you can run um for logged in users but yeah a lot of the work we've been doing has been based around anonymous uh users I'm not sure if that's answered the the question but I think you know that is kind of like the holy grail isn't it is having that sort of that rich user profile that first party data that you've got in the CRM and making that available in the website and that is that the aim of the the game basically so you have to work out how to um to do that bridge and that's what this enricher module is is trying to do and yep that's what we'll release soon okay uh one more are racombi and sojari open source or proprietary so firstly their software as a service you go sign up for them you know you're going to pay whatever a hundred bucks a month or something for them so they're quite price competitive um from that um perspective uh morphed has released a couple of open source modules there um racombi sorry search api racombi search api sojari so we've got the back end uh integrations uh with their indexes and we've also got modules that will expose blocks for those so that you can play place them um on the page so yep that's open source so um I encourage you to have a look at that you know there's a bit of setup for them right you've got to push the index across and you've got to put the block on the page um but uh yes they are open source by the service okay guys so we've got two minutes to go and uh I've run through all of the questions are there any final things there that people would like to ask I'll flip across to the forum um okay so Lee's made a little comment there thanks Lee and back on the questions no other questions there I might uh I might leave it there if there's nothing else but uh so I'd like to say yeah thank you so much to everyone uh for coming along today and as I said I'm more than happy to to uh talk about this or anything else we've really just sort of scratched this the surface there but hopefully I've given you a bit of an idea of um what we've been working on and what's possible so thanks a lot everyone and enjoy the rest of the conference