YouTube Video HVnSxcvTxss ![rw-book-cover](https://img.youtube.com/vi/HVnSxcvTxss/maxresdefault.jpg) ## Metadata - Author: [[YouTube]] - Full Title: YouTube Video HVnSxcvTxss - Category: #articles - Document Tags: [[community]] [[drupal]] [[ux]] - Summary: YouTube Video HVnSxcvTxss - URL: https://www.youtube.com/watch?v=HVnSxcvTxss for coming to our session Drupal CMS now and beyond. My name is Pamela Baron. I am the Drupal CMS product owner and I'm also the CTO of Technocrat which is a Drupal agency based in Australia. >> And I'm Christina Chilez. I'm the Drupal CMS product design lead and uh Drupal core front end framework manager and specialist UX manager and I'm also Camrio Coo a company based uh in Spain. So what we're going to talk today is uh about Drupal CNS but most importantly uh a little bit of a uh an intro to the vision and strategy because that's quite important to understand the rest of the things that we're coming uh we're going to say later and um to understand why uh all of that the current run state and the most interesting part what is coming. So let's start with the vision and strategy. But first, how many of you have installed Drupal CMS at least once? Okay, there is some people that have haven't. Okay, so how many of you have actually seen uh the original keynote where threes talked about Starshot and they introduced Starshot. Okay, that's a well that's a lot. That's great. Okay. So, um Drupal CMS 1.0 was uh launched in January for the 24th uh birthday uh of Drupal. Small detail. And uh Drupal CMS 2.0 is planned for really early on 2026. Um we're going to ship uh with a lot of things. uh I would say probably a month, a year and a half might have passed since we originally started that and uh we would have loved to have a lot of more things earlier but obviously with Drupal when you start doing things there is a lot of complexity and um different things that might happen but the message that I would like to share first the most important and it's on my favorite slide And um and I put some colors there uh because I really like it and it's the most important message I want to share you and it's not that much about the numbers, it's about the evolution. Um the message is that Drupal CMS has accelerated innovation and yeah it's in there uh it's the title of the slide but the most important thing and it's a small it's the this is organization credits on strategic initiatives I'm not sure if you were uh paying attention when mentioned that and it's that a lot of the contribution comes from companies people that is working at a company and this investment ment is strategic for the future of Drupal and that's why it's important that this is going up because the more investment there is in Drupal the more contribution the better the product. So that's why it's important and that's why it's important that this has happened. So um this is like uh this red line uh I learned that exact the numbers exactly are not exactly these ones but that's something that happened. This right slide sorry this slide uh the right bar means that we're keep having more and more contribution specifically coming from companies. So it's important not the numbers it's important that we're getting more contribution and that Drupal can keep growing. So what's the strategy for Drupal CMS? Basically uh it's enabling marketing teams to launch in ours and that's the most important thing as you are seeing here. We're not talking about developers. We are talking about marketing people. We are talking about people that is not going to work on the common line and it's super important that it's going to be in hours not in days not in weeks not in months and obviously not in years. So to actually make that happen, to realize this vision, we need to provide something that is the starting point, something that is going to be useful for literally everybody that is starting. And that means making hard calls or making informed hard calls. That sounds a little bit better. But that important part of deciding what's the best thing to provide to users at the starting point, it's the main difference that is going to change from hours. Sorry. So from months to hours and that means that a lot of the things or a lot of the initial decisions or research that would happen on any project, it's already shipped with Drupal CMS. This one is yours. >> Yeah. So during the development of 1.0, we realized that we really couldn't um make something super useful if we didn't know what the end result was supposed to be. So we tried to make it generic, but by making it generic, we found that it wasn't actually as useful as it could have been. So we came up with this idea of site templates which is a near feature complete starting point for a website based on a specific use case and the specific use case is the most important piece because you just can't give somebody everything that they're going to need if you don't know what they're trying to do. Right? Building a website is not enough. That's not specific enough. So we came up with this idea of site templates which is um basically bundling the the fundamental tools. So, Drupal CMS itself, Drupal canvas, um a Drupal canvas based theme with using single directory components or code components and some default content, but most importantly, it bundles functionality that would be typically useful for the use case that you're um that you're aiming for. So, I'll talk a little bit in more detail about how this is working in practice later, but um the the the way we're describing the current phase is making easy things less hard because I think everybody knows in Drupal sometimes doing things that should be easy don't always turn out to be easy. So, we're starting small. We're starting with making easy things less hard and then we're going to move into making easy things easy. So, that that's going to be the next phase. And I think also one of the core um pieces of the Drupal CMS vision was to move toward more of a no code. We start with low code and move toward a noode uh ability to build websites. Uh where you know Drupal core itself is really high code. You really can't build a a highly functional Drupal website without doing a lot of coding. Drupal CMS 1.0 we feel like we kind of took one step. Um 2.0 we think is another step. And then we've got a little bit more work to do to get to the fully low code, no code space. So I'll talk to you a little bit now about the current state of where Drupal CMS 2.0 is up to. Uh we currently have an alpha release and we're aiming to launch in January. What will it ship with? So Drupal CMS 2.0 will ship with the world's first Drupal site templates. Right now we have two and we have another one that's coming soon. So we have a starter, we have something called bite, and then we have one coming soon called lumen. And I'll go into a little bit more detail about what each of these gives you. So starter is just basically kind of vanilla. It's it's very basic. It's Drupal C. It's all of the things that Drupal CMS 1.0 had pretty much plus um a a canvas friendly theme called Mercury and a basic page content type. It'll have basically you can create landing pages out of the box using canvas and you can also use it as a starting point to develop a custom theme with your own branding. So it's more of a DIY. It's not a fully complete. It's sort of if you want to um have a little bit more flexibility and you don't necessarily want everything done for you. And the second one that is currently available is called BTE and this is designed for a SAS product use case. So essentially what bite is, it's Drupal CMS plus bite which will be forked from the mercury starter theme. Um then it's got a canvas the canvas page it's got a blog content type and some associated functionality and it's got a basic page. So again it's ready to go with canvas out of the box and it has some additional recommended recipes that will be optional add-ons that you can apply to the site based on things we think you might want to do. And again I'll talk a little bit more about that later. This is um a screenshot of essentially what you get out of the box when you install bite right now. The content may change but roughly the functionality is this. And I have to say I mean I don't know if um you all agree but when I install this and I see this rather than Olivivero it just brings me joy every time um Lumen is the one that we're working on. So we've kind of we're almost finished with the designs and we're going to um develop that site template next and that's designed around the nonprofit use case. So that'll be similar. It's Drupal CMS plus a custom theme and then um maybe some additional content types. So we think probably event would be useful for um a nonprofit site, maybe some others and then some additional again some additional functionality that we think might be useful for that use case. So the big headline of Drupal CMS 2.0 is obviously canvas. It's ready. Well, it's almost ready, but um it's here. It's usable. You can see it. You can touch it. It's very very exciting. So this is an example of a landing page that Drupal CMS ships with in the byte site template. And then we've also got canvas for node displays. And if you haven't seen this, I cannot stress enough how cool it is because basically you can create your content type layouts using the components that you've developed. So in this in this um screen you can see we we have a heading text field that maps to the title of the node and the publish date which also displays on the on the content type maps to the publish date of the node. And when you add a new component so if you drag in a new component to um style it basically when you click on that little link icon you can see the list of fields that map to it. So it's essentially replacing the tools um well there are many many many tools we know to do these things in Drupal already. This simplifies things to a kind of mind-boggling degree. And then we're also really working on this concept of recommended add-ons because I think one of the biggest strengths of Drupal is obviously the contributed modules and all of the many things that you can do. But at the same time, it's a bit of a weakness because it's often very difficult to figure out how to do that. So, what we're trying to do is surface some features that we think will be useful for the site template that maybe you don't necessarily automatically want, but that would be useful for you and would make it easier to achieve your goals. And the the thing we've also decided to do here is that in Drupal CMS 1.0, we ship with some recommended recipes, but in 2.0, the list of recommended recipes is a is sort of a dynamic external source. So, we can update that at any time. So if you install our site template, as we develop new functionality, we can add new things to that recommended tab and that will kind of allow us to keep innovating and and keep providing value. So what is available now? Integrations are one of our biggest focuses. And so um I mean I think again one of Drupal's strengths is not necessarily that you can build everything you want. You can but you probably shouldn't. What it allows you to do is really easily integrate with best of breed solutions that are already out there. So we have a Mailchimp module for Drupal. Obviously Mailchimp is a very popular newsletter software. We have a Mailchimp module. Um setting it up is a bit of a journey and I I actually did this for a client a couple of months before this all happened and um that's kind of what what sparked the idea to to try to improve this. So before this is this is the before times you had to install the Mailchimp module. You had to figure out how to authenticate your site with it. Then you had to figure out what to do next. You actually had to install a different module, which is the signup module. Then you had to figure out what to do with that. Then you had to create a signup form block. Then you had to figure out where and how to use that block. So it was a multi-step process that if you had not done it before could take you many, many hours. And what we've ended up doing now is we've created a recipe uh where this is called the Mailchimp signup forms recipe. So you click install um that runs when it runs you go to um the authenticate uh page in the module authenticate your site um this we're we're trying to improve even this to make it a little bit simpler make it more of sort of a one-step thing but this is what it is now so you allow no note you're not getting any API keys you're not doing any complicated configuration so now you're done and once that's once that's done what the recipe does is it automatically goes to your Mailchimp and it creates a signup block for any list that you have active or now they're called audience but um so now what you have is essentially a signup form for every audience that you have and then all you have to do is go into Canvas, find your Mailchimp signup section, drag it into your page and you have a Mailchimp signup block. That's it. That's all you have to do. [Applause] So um some people might be wondering why we chose Mailchimp for this and the very simple answer is that uh Intuitit which is a company that owns Mailchimp actually pays a Drupal agency called Thinkshot to maintain their integration. So as may many of you might know if you try to integrate a system that your client has asked you to integrate with you end up trying to kind of do it yourself. You know you're going through the docs you're trying to figure out what to do. It's an absolute nightmare. Um, best case scenario, there's a module out there that may have support already, but doesn't do all of what you want. The Mailchimp module has incredible support because they're paying for it. So, I think this is actually hopefully something we can use and take to other third party providers to say if you're willing to make a I'm what I assume is a relatively small investment um for them, we can put your module on the recommended page of every Drupal CMS site that's relevant to it. So this is a really exciting possibility. I think the next thing that we looked at is Stripe. So Stripe is a payment processing platform that um it does provide already some pretty easy tools. You can sort of just drop an embedded form in. So you don't even really need integration directly. But if you did want to say take a payment as part of a a web form that you have on your site, that's also possible. But but and there are there are modules that do it. But it's still again it's many steps. you know, you install, you click, you try to figure out, you do, you know, it's it's just kind of a um it's like a maze that you have to navigate yourself. So, um again, we've created a recipe. You literally install the recipe. It pops up a form to ask for your API keys. Now, you have the form and you go to your Canvas page and you drop the form into your Canvas page and then um the way the web form block works, you search for the form that you're looking for and then you can preview the form. And this is literally a page where you can accept a payment within your website that goes straight to Stripe. That's all you have to do. That's it. So, um, again, why we chose Stripe is because it's a very well-maintained contra ecosystem. I'm not sure whether Stripe themselves contributes, but there are a lot of modules that are already there that made it really easy to set this up. And the other piece is because we're looking at doing a nonprofit site template next, the idea of providing a very easy way to take donations was something we wanted to do, but we were actually kind of thinking is that even possible? Like is it even possible to make it, you know, flip a switch and you can accept donations? And it turns out it is. And of course, you know, not everybody may want to use Stripe. I understand that their um fees can be a little bit higher than the others, but it's so easy to use. And I think as an entry, it's good, right? you know, if you want to um if you want to set up something as sort of a proof of concept, you can do this in literally minutes and see if it works. And if it works and you're taking tons of donations and you're paying tons of fees to Stripe, then you can invest in maybe a more robust solution using a commerce um a commerce solution that actually does exist. There's a recipe that lets you set up Drupal Commerce to take donations using any essentially any payment gateway that you want. So, this is I think speaks to what Dre was saying before about sort of the top of the funnel. this is how we can draw people in with really simple things and then um grow basically they can grow their site with Drupal and and we can help them do that. So the the key thing here is that we really need other integrations. Obviously we have um some specific things in mind that there are some things that are more popular than others but um any integration that we think can be made easy is worth spending time on. So if you have a module that you use a lot or if you have a client that has a module that um they want integration for and and you know it's it's something that's a popular system we would love to talk to you. We would love to hear from you. You know these things are happening because the community is already doing stuff. Um the Drupal CMS team for those who don't know is essentially me and Christina and a developer named Adam. And then we have obviously some other leadership folks that contribute um to strategy but working on the the thing itself. There's really not many people. So, we can't do all of this ourselves. We're really relying on the community to provide us with the tools that we can then piece together. Um, and then another thing that we're we're going to be focusing on soon and and kind of are already thinking about is how to support uh how to add canvas support for contributed modules. So, the world of canvas is a whole new world. It's a whole new admin UI. We need a basically need a new kind of framework to think about how contributed modules will integrate into this space. We need new designs. Um it's a totally new workflow, totally new capabilities and with that comes new constraints and limitations as well as new possibilities. So that's something that we're in the early stages of and we know we have a lot of work to do but um but we're definitely thinking about that. I'm gonna hand back over to Christina now. >> Thank you. All right. So, um this is what we have. But we are not just working and implementing. We're already at the same time planning what is coming. And that's really important because we need to grow the as was saying we need to grow the team. We need to uh convince people that what we're going uh where we're going and what we're going to do is actually on everyone's interest. So, um, as she said, we are right now trying to make easy things less hard. And seriously, that's not easy. Um, it's it's it's a perk and it's a it's it's the good and the bad of Drupal. It's you can do almost anything, but it's complicated to do so. So, to reach that first point, that's what we are trying to do now. But what comes into the future and what we want to make make a change like really change things on on how we've been working so far it's making this easy things easy so we smooth uh the entry point for users. So basically um the role that UX and when I say UX uh at the end there is someone that came when you say UX you should say all these things and I think it's enough in here to say UX it's about design it's about experience it's about the users it it conveys a lot of things but the most important thing is that whoever decides what is going to be in there it's not the developer that has came up with an idea and then says make it pop. It's the whole team. It's a developer. It's a designers. It's a strategist. It's a business person that it's going to need to sell all that. It's a marketing person that knows the users. So, it's a whole team that needs to decide that. It's a whole set of skills that need to participate on the the definition and the UX role is really important here and what to make sure that it it's uh embedded on at the origin of of any new feature or any decision. So we as you all know probably we have a lack of UX experts involved within the community. You might all have uh them in your agencies, but we don't have them participating on Drupal. So, we really need that. So, if you know somebody that wants to try to help with UX, we will take care of them and translate a new uh developer conversation to them. So, we need them uh if you know them. It's not just that they have to come, it's that they have to stay and ideally they would need to grow into decisions decision decision makers. And here a great example is Emma. Emma is a UX researcher. She started I don't know f four years ago. I'm not exactly sure when she started. I remember when she started coming to the UX meetings. She was really quiet at the beginning. At the moment that she opened the mouth, she really knew what she was saying. So that really important that we empower the people that knows what can happen and has the knowledge that developers don't. So uh Emma uh helped uh with all these tasks. She helped uh testing the things that we were developing and some of these contributions were really important uh to know for example do people understand the difference in between models and recipes. Do people understand where they have to go if they want to improve and increment the amount of functionalities that they have in Drupal? And that was really um a huge amount of work and it really proved really important and uh insightful. So uh we did a lot of interviews, we did a lot of surveys, uh we integrated a lot of this feedback and uh we had a lot of direct engagement with a lot of people. So um a lot of our community members came and told us what they thought about Drupal CMS, good and bad things, what was conflicting and uh we already started some round of inter interviews with um people that has distributions agencies that have internal distributions where they start from Drupal not from scratch but they start somewhere. So we are doing these uh interviews in and if you want or you think you have something that is valuable for Drupal or could be helpful for Drupal C CMS let us know. So as we keep saying we want to make uh it easier to get started and we want to make it easier and faster to build because at the end it's a wave uh cheaper product and more competitive product to get to these new clients and use. So some of the things that we've been working and we are uh for me this one of was one of the mind-blowing things. Um it's it's just an app. It's just an app. You download it, double click and you have football. Do you know we at the beginning we were working with I think it was six several designers and all of them were like yes I'm designing something but how can I actually go and try Drupal and try to get a designer installing Drupal it's it's an adventure to say the least uh and just this like completely changed what they were able to do they could try what they were doing they were they could try the uh interfaces that they were going to design and see the problems that users might have. So that was a really um breaking point and a few months ago I was in Germany giving a session and after this I was saying yeah I really like the app and there was this guy that came and said hi so FYI I'm developing all my sites with the app why can't I export what I've done in here so I can upload it to the uh to the server and I was like wait what so people is already finding ways for using this. So seriously this is uh this has a lot of future and makes me really happy to make things easier even for the developers to develop something as uh D and P mentioned uh this is going to be a I really hope a game changer no not by itself uh but the marketplace it's going to be a way to be an an enter point for those users uh that don't know how to start making things easier. Uh starting with just a few hours and by itself it's just another drop in uh the amount all the uh innovation that is coming over the last uh months years but it's going to be something something really important uh on how people actually start with Drupal. So as they were as they said is uh work in progress. Hopefully 2026 we'll have uh the MTP and multilingual. Um I I really think this is a game changer also. Um obviously uh when everything started we needed things working. um canvas needed to work obviously at least with one language but now that it's working literally everyone in Europe asks okay all my websites by law for example governments or a lot of people just saying I need to translate things so when this is ready this is going to be like a game changer for so many countries and they will be able to adopt a tool with canvas that will completely change how we will uh how we build Drupal sites. Uh at the beginning we assumed that it would be okay let's just make everything for example you install Drupal and you have everything in French and then said we will postpone the um for example having two languages English and Spanish for a second use case. So we um Yolanda is in there uh designed this and uh Angeli helped obviously implementing a lot of these things. both are there uh helping uh with this new uh installer that we have with Drupal CMS and having this design and we came up with all these uh interesting ways and really nice ways um to actually uh have translations and the first part is the result of I think it was a three or hour session or something like that or maybe a little bit more or less I don't know uh with Gab a few of us uh Gabbor was the person that uh was involved on how uh translation and multilingual sites um work and the top one is how um it works right now translating a Drupal site it's a small the important part is the green ones the green the green points is where somebody has to make a call make a decision so each of them is a step and at some point somebody has to make a call. Basically the second one even though you it looks like there are a lot of steps a lot of this is just clicking next being informed of whatever is happening there are only two decision points and that's the most important thing. Somebody that doesn't understand what they are choosing they you don't you can't just like ask them to choose some kind of things. So basically we came up with a solution that would make things way easier. So um this is early uh designs. I know there are like nicer designs now but basically the moment that you activate the translation recipe you will have a few steps where you choose one or two things and that's it and you have your Drupal site translatable work in progress. Basically uh we will have the installer and then Drupal itself has different things that need to be translated. Drupal itself, Drupal core can be translated. Um but recipes, config actions and canvas uh they are working in progress. So those are the different things that are being worked on uh to get translations and get Drupal CMS and Canvas multilingual. And uh some of the other things that we're trying to do uh to make it easier to start with Drupal is the on boarding uh and the next steps. Um it's not just about design, it's about really understanding when somebody is landing in a Drupal site, what are they expecting? What are the first steps that they want to do? Which are the ones that we've already designed or decided for them? And uh this is how you land right now. And it's a lot of information or too not enough information. It depends on what you want to do. So basically we want to uh improve these initial next steps. Um for example setting up your site uh setting up the I don't know the which is the the the contact form which is the the privacy. Do you actually have to do through all of this? We are integrating this with a new navigation for example and this is the we need to define all the steps and we need to integrate it in a way that is not an uh obstruive and at the same time use all these designs on other uh initi uh other initiatives and other um uh recipes that are going to use all these. So we are trying to collaborate several of that of us uh into improving the on boarding experience. So um it's a big priority to make the part that is the administration interface um better and we need to decide which of these areas are actually the main areas that are going to remain in the future that are not going to be changed by canvas are not going to be changed by AI and we are trying to see which of those areas are actually going to have a bigger impact in the future. So one of them is for example the content area. This is an early exploration. A lot of this has changed over the last two three weeks. Um this is an exploration of for example what is the content section going to have because if we have the pages for canvas and we have the content types uh that is the blog post the event for example that is a structure content is a drupal CMS uh it's a CMS content and we have for example utility pages like form one or um web forms or in the future we have products how are we going to pro uh uh present all this information and all this content to a user that actually makes sense and it's a center to actually control all this content. So we are um coming up with ideas and uh trying to solve incrementally uh or improve incrementally this experience. Something else that we're trying to uh plan ahead is how is actually people going to uh extend an existing Drupal site or a new site because uh right now you have the extend section and inside the extend section you have actually models that you have in your local and at the same time you can go to project browser and what's the difference? What is the one why is some of them are enabled on my list page and some of them are not. So a lot of that things are conf confusing for the users. So we are trying to um separate which is the uh job to be done which is uh enabling or improving or extending your site and the other is managing what you already have. So this is work in progress and as you can see there are some white friends and we are like thinking ahead on how we're going to implement all these things and something else and uh this is an and early exploration. Uh but as you can see here, we're thinking on how we in the future make creating content easier because if you think a little bit uh about of the different parts and again this is a prototype. It's not the thing that is going to happen but it's more the concept at the end Drupal CMS is a content management system. The most important thing is content and right now I'm not sure if you have in your man in your mind how we create content and it's a form step by step then you go and decide the fields and the fields um you don't see how they look like and so in here if you want to have an overview for example of the different content types what's the relationship between them all these things it's not just about the content creation how does it relate with others so this getting a visual picture of all this in the future might be strategic to compete with our um competitors out there. So, we're starting to think about that. >> I'll take this one. >> Um so, then the I guess we shouldn't say the last area because I think this is a really important area, but something that we haven't really talked about specifically. I mean, we keep talking about making it easy to launch websites, but one aspect of launching a website that we haven't really talked about is hosting. So, I think what we know that we need are to create some really clear pathways that allow you to go from your site that you've built, wherever you've built it, to having it be live. And the key areas that are kind of um needed for that are support for UI based tools like project browser and automatic updates. Um because obviously having to pay a developer to do your updates for you is kind of a a non-starter like that that sort of breaks the model of the low code no code model. So we need that and we need the pricing to be competitive with other platforms. And um we have we have tools we have UI based tools like project browser but I had the pleasure uh earlier this year of testing those tools out on what we call the the shared slashcheep hosts um hosts like host armada or hostgator and what happens is they they technically work but what happens is that because the package manager creates an entire copy of your website using composer stager it essentially creates an entire copy runs the updates in the copy and then deletes the copy and replaces is your website with the copy. That equates to I think the creation of about 50,000 files then the deletion of about 50,000 files along with all of the rs syncing and moving things around which uh so far every host except DreamHost has flagged as malicious and resulted in the website being blocked because it thinks that something very bad is happening. So literally you go from you know you click install on the module and then all of a sudden you get a 403 and your site is just completely broken. You can wait a couple of hours and it comes back, but the same thing happens again. So, these are things that are not insurmountable, but they're definitely challenges that we have to figure out a way around. And the way around them might not be, you know, to make it compatible with HostGator, but there definitely has to be one or two hosting options that allow you to use these tools. And just for anyone that that's um wondering why why aren't we mentioning tools that exist like Platform SH and and Pantheon and Aquia, those tools generally don't allow you to write directly to the file system for security reasons, which is a very good idea. However, um many of the users that we're talking about don't necessarily care about that as you can see from from all of the use of WordPress and all of its automatic update tools. So, we don't think that we can just kind of assume that the that the security concept is going to kind of win the day and people won't care about that. we need to assume that people will want those cheap and easy hosting tools. And then the second thing that really speaks to the maintenance is just the ability to update easily. So improving the existing workflows for updates. And um right now we have an automatic updates module, but it's somewhat limited in that it only does patch releases of core. You can't update minor versions of core with it yet. And I I think potentially what that looks like is minimizing the complexity of major release updates. I don't necessarily think that Drupal has to provide UI based updates for major core releases but I think we probably have to come to some kind of happy medium where you know you can get by for a year or two and then when you have a big job you might need to hire a developer but definitely we have some we have some room to improve there and then I think um another thing to call out as I mentioned earlier we're not a big team and um we're we're really kind of thinking about the future plans now and we would love to get help defining the road map from all of you I mean obviously this is really for you um we are also users of Drupal, but we only know what we know and there's lots that we don't. So um so especially when we have conferences like this, we often have a lot of conversations about the future plans and and we try to kind of define some strategies. So we would love feedback from you. Um you know, you can come grab us anytime and if you haven't installed Drupal CMS, we would recommend that you do so and um and come find us. And Christina, I don't know if you want to say anything about this too. Yeah, basically uh we are not just like hoping you that you approach us in here. We are already like planning and scheduling some meetings with agencies with providers and if you want to like schedule a meeting or like plan with some time or like send us feedback on any way. We are really looking forward this is gold for us like any kind of feedback on how you actually develop or what your clients or yourself actually need. that's going to be really really helpful for us. So, um if you want to connect uh on Drupal Slack, those are the most important ones. Um we try to help uh and answer as many things as we can. If we are not all day in there, uh just give us time. uh yeah different time zones and different like um burdening deadlines and things like that but in general we should be able to answer that there and it's not just us there's like the other um Drupal CMS committers like um well apart from Adam all the team that is working on that so um you will get help uh and answers and especially ways to get involved in there and One last slide and I think um I usually don't do that but that was a little bit surprising in a positive way. I would like to thank uh digital the digital center of excellence uh because they actually sponsor my trip here. I'm not sure while you as a context um I've been like searching for um sponsors to contribute to Drupal CMS for a long time and uh they actually sponsor my way here to actually be able to make that possible. So thank you. Basically they are a place their mission is to grow the Drupal ecosystem by helping out agencies and um FFP and talent get together. So thank you to them and thank you to all of you [Applause] >> questions. Uh go ahead. Oh no, we have one minute. That's all. >> Oh, >> I think. >> No. Yeah, not anymore. >> Oh, not anymore. Sorry. No more time for questions. >> No, we do have time for questions. >> Just kidding. >> Any question? >> No. >> Any fun experience? >> Oh, sorry. Do you want to use the microphone? >> Yeah. Um, >> can you go up to the microphone? >> Can you hear me? >> You might have to turn it on. >> Can you hear me now? >> Yes. >> Okay. Lovely. Uh just a question about the the UX work you're doing. Um have you been looking at the objectoriented UX initiative? Any of that? Have you heard of that? >> Object orient. >> Okay. Great tip. So I'm just beginning to explore it now, but >> is it a Drupal initiative? >> No. >> Oh, >> no. Completely out of the Drupal ecosystem, but it's all around UX and it's it's fairly recent. that might be a really good tip to help inform all of the content type things. So maybe I I only need to start I've just become aware of it in the last sort of six weeks. Cool. >> Seems interesting to talk. >> Please let's talk later. >> All right. >> Thank you everyone. >> Thank you., YouTube Video HVnSxcvTxss, YouTube, 01kac4qw686rkzt8dxpnh2ffzs.