 Hello, I'm Rachel Larson from the Drupal Association and today I've got some people together who are going to be running and one of the initiative days at DrupalCon North America coming up in second week in April. So I'd like to introduce them all. This is the team for an initiative called Decoupled Menus and we have Teodor, we have Gabriel, we have Tara and we have Badi. So hello everyone, how are you doing? Thank you. So Decoupled Menus will appear on Tuesday at DrupalCon, but what do we mean by this? I know it's the name of a strategic initiative, but can you tell us a little bit more about what that means, Teodor? Sure. So it comes from the fact that Drupal is an old CMS or older CMS and we need to keep up to date about the practice on the web to make sure that we're still relevant today. And this is the way for us to start to bring Drupal into a new kind of phase where the front end is a bit more involved into the decision about what to use to build websites, because usually it was backend developers that did that. Now it's a bit more front end developers that have some of the decision making. So we need to make sure that we have a good fit for front end developers and that Drupal is still relevant for front end developers today to implement large scale project and smaller scale project as well. Yeah, absolutely. So that sounds great. But why is that important? Why is that important to the future of Drupal, Gabe? Yeah, so there's been a lot of excitement about decoupled Drupal over the past few years. But what I've noticed is a trend to go towards more progressive decoupling and people are giving up things when they decide to decouple or not to decouple Drupal. They lose what they get kind of for free with a more traditional architecture. So what decouples menus is is it's just pushing a snowball off a mountain. Menus themselves might not be the most exciting thing, but underneath there, there is tons to work on. We have to figure out how do you do routing in a decoupled architecture? How do you do URL aliases? Do you handle authentication? Things like that. And then we're also establishing new patterns. So we have already made it possible to have projects on Drupal.org that aren't just Drupal modules. So we can have standalone JavaScript packages. And those can even be part of and considered part of Drupal core, even though they don't live in the core code base. So what we're doing is we're establishing these patterns that are going to set us up for success over the next decade. And that's really exciting. Oh, fantastic. Yeah, that would be great. Actually. And yeah, as you say, there's so much in the background that has to take place to make that happen as well. Yeah. So just thinking people are going to come to Drupal Khan on Tuesday, they will hear all about you talking about this in a keynote on the Tuesday morning. And there will be lots of sessions on the Tuesday around decoupled venues. What especially what do you think people might learn at Drupal Khan about your initiative. So I think first of all, people are going to learn what has been done. And what has already like from the Drupal Association has also been helping a lot. So I think that in the keynote, we are probably going to be talking about what has been done in the background and where, where are we, you know, we're, how far are we with the initiative or, you know, are we starting to think about the next to be done or so that is what you're going to learn in the keynote and we are hopefully going to have some cool sessions that are going to be supporting that maybe some use cases and we've been doing these lightning talks. If you haven't seen that yet, go on our YouTube channel decoupled many initiative where we have actually been trying to like talk about what is happening in the couple Drupal world. So we're going to be going over that. And then the idea is of course to see and test if this is actually working out so we are hoping that we're going to be that far that people can actually come and start to play around and create like JavaScript components and, and you know, play around with menus and so the idea would be like to have a little hackathon or something like that we are just, we are creating this idea now. And hopefully going to be working them together with Tara and other from the mentoring team to see like if we can create like some kind of a cool things to be doing on Tuesday and hopefully on the days after too. Fantastic. So it sounds like you already have some ideas about how people can participate in the later parts of the day on Tuesday. So when we go into the second phase into the contribution that you will have some specific things that people can be doing. And I mean, Tara, you're, you're working as with the mentoring team to make sure that we're going to have some mentoring people to help with that and so on. Yes. Yeah, so we'll have mentors on the day available even if you've never contributed to Drupal. We can help you understand how the issue queue works, what the issue queue even is if that word is not familiar to you. So like body was saying there's still kind of a lot being decided and we know work work is actively happening so we'll figure out as we get closer what exactly those tasks look like. But we're probably, you know, we're going to need people with coding skills, writing skills, testing skills, lots and lots of different kinds of people to come help make sure this decoupled Drupal is the way you know the way of the near future not the far future. We do actually, as you say, we don't just need coders, and especially we do need all of those people who are going to help make it easy for the next people to come along. So those people who can write down in a really clear clear way, what the whole team are working on and producing so that someone can really easily build those components into the future. And not only that but actually sell Drupal once we've made these amazing things. Yeah, we need all those people who can produce that. Exactly. So we did, we did a survey and it's just coming out now hopefully in the beginning of March, the results of the survey but we asked the community how they want what they are expecting and how they are using Drupal in a decoupled way today. What JavaScript frameworks are they using and not just those who are using Drupal but those who are actually building decoupled applications we got like hundreds of 100 plus you know we got like 150 I think responses. And one of the main things that people said there were they they want to have code examples. They want documentation they want to have examples. So it would be great if we can have like people like Drupal con, helping us to create these code examples so you can say like now next time I'm building a view jazz application. And I can just go there and I can look at the example and I can know exactly how it's being done and I can just take it and take it further so this is what the result of the survey set. We want more code examples we want more documentation of how to do decoupled applications. So that is definitely going to be a big part of the Tuesday Wednesday contribution in in our initiative. Absolutely. I'm, do you know what I've been having listened to you all telling us about this. I'm now I'm really excited for the Drupal con on Tuesday. And I hope that all of the other initiative teams that we come across next will be equally inspiring, shall we say, so thank you. We'll catch up later in a few weeks and see how far you've got ready to be prepared. Thank you. Thank you. Thank you. Thanks.