 Hello. Good morning. Good afternoon. Good evening. I'm Audra Martin Marek. I'm a secretary of the Drupal Association Board, and I am very happy to welcome you all to this session. You may have heard about the Olivero theme, which is an official Drupal core initiative to create a fresh and modern default theme for Drupal. My cursor and Putra Bonacorsi are here to discuss the history and future plans, and I'm very excited to welcome to the stage Mike and Putra. Throughout, if you want to ask some questions, you can put them in the chat, and if we've got time at the end, we'll get to them. All right. Over to you, Mike and Putra. Welcome. Thank you, Audra. Yeah. Yeah. So this is turning a wild idea into a core initiative, and we're talking about the Olivero theme. Basically, we're going to talk about our process of taking our wild idea and putting it into an official strategic initiative, and the thought process is you can hopefully take your wild idea and make this into an initiative and get it into core, too, if that happens. I also want to give a huge shout out to everyone who made this possible, and that's especially the Drupal Association. I've talked to, I think, people from 18 countries, which is completely wild, places like Bolivia and Cameroon and Rwanda, and I've talked to people from there, and my mind's been blown. This is definitely not a substitute to meeting people in real life because I miss you all, but at the same time, this is really, really amazing. Yeah, and I just wanted to echo the same testament as well, too. Especially during these challenging times, I'm so glad that we're still able to get together in this virtual conference and still be able to share ideas and also be involved in this amazing community. So thank you to the Drupal community. Yeah, totally. So my name is Mike Herschel. I'm a senior front-end developer at Lullabot, and you can find me on Twitter at Mike Herschel. Hi, my name is Putra Bonacorsi. I am the technical project manager at Lullabot and also a formerly front-end developer as well, too. You can also find my handle at Putra Bon, and my website, I am puttra.com as well, too. Yeah, so as soon as we work at Lullabot, Lullabot is a strategy design and development company, and we also do support and maintenance, which is relatively new if you're into that type of thing. We tend to do like strategy, and when we do strategy, we always mix around cards like this picture. And we also make websites, and here's some screenshots of websites if you've never seen one before. And yeah, and we're essentially the leads of the Outbound Initiative. So for this particular sessions, we'll be going over how we actually found our ideas as far, too, and also identifying whether or not your ideas and the works. We're also going to be putting together your, or going over how we put together our initial team in addition to identifying stakeholders. We're also going to be walking you guys through our design and also documentation process in addition to how you can submit your formal proposal to the community. And at the end of the presentation, we'll give you a sneak peek of the algorithm as well, too, as far as the current updates that we have so far. So yeah, so this is essentially just a quick outline of what we are going to be discussing today. So I'll hand this back to Mike as well, too, just so he can talk about the beginning of our idea. Yeah, totally. So thank you. Yeah, so let's talk about like finding your idea and maybe like how we found our idea. So what are you passionate about? You know, for us, we were passionate about like making Drupal look good. Drupal is this amazing, amazing content management system, but Bartik is a little bit older, you know, it was great for a very long time, but it's kind of getting a little bit dated, you know, and something else is like, what are you good at? I am, I'm not the best backend developer, everybody, I'm a fairly competent front end developer. And so that, you know, I can, I can work on this. And I also have access to like designers through my work and things like that. And a third, a third item to think about is someone already working on your stuff, you know, or your idea. If someone's working on it, well, you know, it's time to join forces. So for Olivero, this kind of started last year at Drupal Con Seattle, and this kind of reiterates like the importance of these meetings are between all of us, you know. So I ended up having this conversation that was with Putra, Lowry, Angie, Lowry Escalas, the front end maintainer for Drupal, if you're not familiar with it, Angie Byron, aka WebChick, is everything to Drupal. And we ended up having this conversation, we were talking about Bartik and how it's kind of, you know, older, it looks like a little dated. And what, what would we want something to look at? And is, is that, is it already in the works? And so what we found is like, well, you know, Angie and, Angie and Lowry were in kind of a similar frame of mind as us. And, you know, our idea was not so wild, you know. So if you want to find out if your idea is already in the works, the first thing to do is look for the Drupal ideas issue queue. So the Drupal ideas issue queue is basically a Drupal.org project is Drupal.org slash project slash ideas. And there's no code up there, but there's a huge issue queue. And if I want to say like, you know, I want to make Drupal, I don't know, pink, or I want to, you know, do this with Drupal and add in maybe this type of feature, or something like that, I can go ahead and create an issue and say, I think we should do this. And then you're going to have people, people respond to that, and they're going to say, well, I think that's a great idea, or I think that's not so great of idea. And it's really cool because you can get buy-in from people in the higher echelons of the Drupal decision-making process before you actually, you know, start committing your time into code. Thanks, Mike. And, you know, now that you have an idea that you like to include in Drupal core, let's stop and ask yourself, what's your motivation and why this project matters to you? So for us, our main motivation is to create a good first impression for the users, which is typically the first experience that people get when they first install Drupal. The current BoreTech theme has served as the default Drupal theme for almost a decade, as Mike mentioned earlier. And the design had begun to look dated and no longer spoke or reflects the kind of modern backend that Drupal ships under the hood as far too. And basically, we want to change that perception, bring something fresh and modern to this default front-end theme. So our initial goals for the project is to essentially have an updated modern design. We want a theme, like I mentioned before, to feel more modern and also convey a better perception of Drupal as a CMS as well, too. We want the design to support new features as far, too. Leverage the amazing out-of-the-box features that Drupal provides as far, too, like second-level navigation, embedded media, layout builder as far, too, which is amazing, and more as far, too. And we also want the theme to be fully accessible as far, too. So aligning with the WSCAD AA performance as far, too. So setting these goals helped us stay focused on what we needed to do. It got us prepared to open the idea queue, as might mention, for the redesign and development of the theme that could shift the beliefs of Drupal 9 as well. So as our idea started to take shape, we continuously documented all of the discussions, right? We had, we got on the project. And here's just a screen capture of what many, the many documents that we have sorted for this initiative between Mike and I. Documentation isn't fun or exciting as writing code, I'm sure. But it's one of the key factors to us keeping track and hitting the deadline for a release and a proposal to the community as well. And here is essentially a screen capture of our idea queue that we submit as far, too. So in this idea queue, we spent a lot of time outlining some of the key sections, such as our problem and also motivation. We also took this time to also outline our proposed resolution as well, too, in addition to highlighting some of the processes and tools that we like to incorporate for this initiative. In addition to some of the key features that we want to see such as secondary navigation and also other features that we felt that was great to include as far, too. We also try as best as possible to also include the timeline and also scope of work for the project just so that people can have a sense of the workload. And also the initial team as far, too, which is really important because you need a good solid team to help bring everything together. So basically putting the team of what I would call Mike's epic scheming to bring people to participate in a work and work with him. It's important that you form your your band, the core team that's going to be helping you out with this effort. So like I mentioned, with any big or small initiative, you can't do everything all by yourself, right? You need a core team that can bring new perspectives and fill in areas that are outside of your discipline. So in the case of Mike and I, we're just front end developers. We don't have any great design skills. So for us to kick off the project, we need to make sure we can bring in talented folks. And luckily, we, I mean, Mike knows a lot of people. So we were able to form the band with the following folks to make this initiative happen. So we have Mike, who is our community coordination and also project manager and a front end developer for this project as well, too. And myself, I am part of my responsibility as part of the community interaction and also finding development as well, too. And we have Jen Bakowski, who is our lead designer, and also Jared Ponchan, who is also our design architect as well, too. We also have Mike Tiff, who is our community interaction, and also Kat Wranglin. He runs our weekly Slack channel, Meetup as well, too. And we have Katcha, who has been helping us out with some of the accessibility as well, too. Here's a group shot of all of us from DrupalCon and SDM doing tree snows presentation, which I'm sure you guys have probably seen as well, too. So now that you've formed your core team, it's time to identify stakeholders that would help with the proposal process, which was one of the key points for us getting traction and building excitement for this initiative, to be honest with you. So this phase was really crucial for our team for sure. However, before I talk about who are stakeholders for the Alware Project, let's take a step back and examine how you can identify stakeholders as well, too. The following are questions that we ask ourselves, like, who is the person that will make a break my idea, right? Who is the maintainer of the issue that I need to follow up with as well, too? And what core committers or product managers might be interested in my idea as well, too. So here are some of the questions that went through our minds as we're going through this discovery phase of figuring out who would help advocate for our idea, essentially. So the following folks are chosen as stakeholders for the Alware Project. We have Dries, who is the creator and project lead of Drupal, as you all know. Dries' motivation for this initiative is similar to ours as he wants to create a better first impression of Drupal, especially for new users as well, too. And we also have the lovely Angie Baron and also Gabor as well, too, who are the core committers and product managers. They help us out tremendously by letting us know the key players that would help advocate for our idea. So a big thank you to them as well, too. And in addition to Christina and Larry, who were involved in the design process, and just be there to answer any of the questions that we have as we navigate this crazy world of core contribution. So here's the screen capture for all of us in one of our design meetings. As you can see, we look really serious. It was a fun and productive design review. Yeah, so the next one that we have up is essentially document and also design as well, too. Now that you have your issue queue, take it, create it, and identify the core team and also the stakeholders, let's get into the weeks or what I would say, the fun stuff, right? More documentation and design. Documentation. So documentation not only clarifies our thinking, it also helps others to understand what we want, may and also want as well, too. Having a clear documented vision keeps us focused on the scope of work. In addition to that, it also helps you avoid scope creep from other contributors as well, too. So defining the requirements for the user interface for the minimum viable product is definitely very important as well, too, and also helps us keep focused as well. So during the discovery phase, as a team, we started to conduct an audit of all the components and features that are available within Bartek. Here's the screen captures of all the available components within Bartek. We use, you know, a simple dropout paper to gather all the patterns to help us better understand what we were designed for and feature that we feel that's kind of outdated, right? Once we identify all the key components, we create five frames to review what our stakeholders to ensure we capture all the important elements as well, too. So at this point of the project, we have several documentation created, and it's difficult to try and keep track of everything, especially if you're also balancing a full-time job as well, too, right? So we created a centralized document that houses all the notes for all of our internal meetings, and that also includes notes from our stakeholders meeting as well, too, and other design documentation. This was really helpful for us to keep track of the many conversations and makes it easier for us to say no when something doesn't really fit within the scope of work, as mentioned in the previous slide as well, too. It also makes it easier for people to pitch in, also help out as well, too, by providing just some background and contact of the project as well. So design, what I've said, the fun stuff as well, too, right? So once we felt like we were at a good place with the component documentation and also discovery, we were able to start with the design phase as well, too. I won't go into in-depth detail about this phase of the project, but I highly, highly recommend checking out Jen's and also Jared's talk, which is going to be epic, actually, as they go into more detail about the design process behind the alabaro theme and some of the pain points designed for the masses, right? However, in this section, I'll be outlining some of the key exercises that we went through in order for us to form a proposal for the community. So this here is what we call the spectrum analyst. This was a great exercise that helps us figure out what the stakeholders are thinking when it comes to the voice and tone of the project. On the one end that you see here is an action that could describe the look and feel of the site. And the other end are action tips that usually come fixed with the first one. So basically, what we want to get at is that should it feel more formal or casual? Should the theme be more friendly or professional? So luckily, all of the stakeholders were in agreement on what the new theme should look like and become what a really awesome list of design principles to go by as well too. So here are the design principles that came out from our exercise. We want to make sure accessibility is the top on the list. We want to keep the theme and design simple. Avoid unnecessary visual clutters and effects or complexity. We want to theme the field modern. So take advantage of the capabilities and strengths of the modern browsers and also interaction patterns as well too. And we want the theme to last, you know, maybe for the next five to 10 years as well too. Again, that's a big challenge there, right? And we want the theme and the design to be focused as well too, like embracing high contrast, saturated color and also negative space to draw the eyes to the most important information within the page as well too. And we also want it to be flexible as well too, providing options to override any type of white features and also preferences as well. Weekly meeting and also feedback loop. So once we have established the design principles for the new theme, we set up a weekly internal meetings with the stakeholders to discuss our discoveries as well too and also present them with some design options as well too. So here are some calm explorations that Jen and also Jared put together. As you can see, we explore different styles from your typical traditional default theme to once a little bit more modern, like the one that you see on the right-hand side. We were able to incorporate the edge tips from the spectrum analyst exercise and use them to help guide us through the design process, make sure that we're on track and in alignment with the goals that we set out in the beginning as well too, which helps us land on the design direction that would be best fit this new front-end theme that we're trying to get into Drupal 9. Here is the final design mock-up that we end up with, excuse me, big thank you to Jen and Jared for putting this beautiful design together. We couldn't have done it without them as well too. So next, now that you have the design, we have to decide on the name and naming things are difficult, especially being a developer, I hate naming things. However, with the current theme, Boatech being named after Gene Boatech, who was one of the original programmers, we wanted to continue in that tradition and name the theme after a pioneering female programmer as well too, which I love. And we named the theme in honor of Rachel Alvaro. Rachel had touched many people in both the Drupal and also accessibility communities. She worked at the National Federation of the Blind and she was committed to making technology accessible for all people, which is incredible. We chose that name Alvaro not just because accessibility is one of our goals, but we aspire to build this theme in our community in a manner that is consistent with the qualities that Rachel embodies, which are patient generosity and also inclusivity as well too. Yeah, so especially that shout out to Teran Amadero. I'm sorry, I think I put you your last name. So I think you have this name and how about us name this theme after Rachel was supposed to. So thank you so much on that. So I'll toss this back to Mike. He's going to be talking about our proven concept process. Yeah, so totally. So at this point, we have a design. We have a beautiful design and how is this design going to look and function? So we needed a way to investigate the use of the header and scroll interactions on mobile and tablet devices. Will this work like we think it will work? Will it be intuitive? In addition, we have some technical challenges like validating the use of CSS grid. We want to use modern technologies like CSS grid, but we support Internet Explorer 11. How is that going to work together? And on top of that, if we do that, is it all going to be accessible? Are these header components going to be accessible? Is CSS grid going to be accessible? How is all this stuff going to work together? And one of my favorite quotes that I have right here, and this is not just regard to literature, but also websites is the first draft of anything and what that means is once you create your website, if you can create it exactly the way they explain it to you, well, they're going to see it in person and they are going to say, well, can you move that over there? I really don't like this. I don't like the way this functions now that I've actually seen this. So we wanted to have this first draft within our proof of concept. And we wanted to do this and we wanted to do it in the most simple way possible. So that includes just like using static HTML. So we don't have to muck around with twig templates. We use minimal JavaScript without behaviors or anything like that. And I didn't even worry about architecting CSS. I was just plop right in there. I'm going to name these CSS classes whatever I want. And I was actually looking back through our initial commits. You can see it's an open repo. It's at the Lullaby GitHub account. And my first ever commit was initial commit with a bunch of poop emoji. And that was like my whole thought process of getting this in there and kind of starting to validate stuff. So you can kind of see what the proof of concept looks like right there. And the URL for the proof of concept is at the bottom. And it's actually kind of interesting. Like you can kind of take a look at this. Like obviously the URLs are not dynamic or anything. This is static HTML. But compare this with the actual theme itself. And it's pretty close. And in some cases a little bit different. Thanks, Mike. So now we have the proof of concept to validate our complex design elements. We need to start to draft our proposal to the community and start feedback for the work that we have done as well too. So this phase is definitely really important. Here's our design proposal for the new Jupyne theme. This announcement issue included several processes that we took to get to where we are today. I must admit I was nervous when we submitted this issue. And I'm sure it was the same for everyone else within the team as well too. I wasn't sure what the response would be, whether or not people would be receptive to what we're introducing or what we're taking out from what they're used to in Boat Tech as well too. However, the response was overwhelmingly positive. And we were thrilled to see the excitement that folks have within the community about this initiative. So that was fantastic to hear. So now that we have the proposal out in the world, it's time to start setting up your project page as well too. So here is an example of our viral project page where we include the description of the project in addition to some information about our weekly meetings and how people can also get involved as well too. So in addition to the project page, we also added some contribution documentation just so that folks can come in and just say, hey, what are you guys working on? How can I get involved? And there are some helpful links that folks can get into to get started as well too in terms of creating a patch and also contributing to this theme. We also set up a documentation page for the involvement setup as well too just so that we have the necessary steps that folks can come in and use in order to get everything in place as well too. And a big thank you to Clara and also Umami, the two initiatives. They really done the hard work of getting post-CSS into core. So we were able to leverage a lot of the tools that they introduced into the our viral project as well too. So a big thank you to the teams on those projects for helping us out when getting our initiative at a spot of where we at right now. So speaking about where we at right now, let's talk about the update of the status of the Drupal viral theme. So right now we're at the final stages of alpha. We're mainly focusing on stabilizing regions, bug fixes. And to be honest with you, I feel like the version that we have right now are fairly stables and we have some early adoption as well too. Like I've seen a couple folks actually download the theme and also install on the page as well too. So it's kind of nice to see the theme in a while but also kind of nerve-wracking because we don't know what it's going to break but it's good that people are adapting it and also utilizing it as well too. So here is basically what the theme looks like and so as you can see it position nicely with the Drupal other box menu bar. Here we also have a screen capture of the drop down as well too which includes some indicative content but here it's just like a preview of what it looks like but I highly recommend you guys checking out this link which is essentially you know a placeholder site where we have indicative content that showcases the complex navigation that we have in addition to forms and it also gives you like a list of what the views look like looks like as well too and a big big thank you to Tuckball for hosting this site and helping us get our preview in place as well too. In addition to that I just want to give a big big thank you to the following contributors as well too and also the folks that work on the project as far as like creating tickets, testing patches and also just being there on our weekly Slack meetings as well too. Thank you all for all your hard work we could have done this without you, without you also. I'm sure I'm probably missing some names here but I just want to make sure that you know folks who have contributed you know are being highlighted as well too so yeah so right now our main focus is to get the theme into core so here is just a list of our roadmap to core essentially so as I mentioned earlier we're at the final stages of alpha but we also want to get into the beta release as well to making sure that for our beta release accessibility and also code quality and bug fixes are at a good place and we definitely are looking to get the theme included into Drupal 9.1 version and work into getting the theme set as the default theme as part of Drupal 9.2 release as well too so those are the areas that we're currently focusing on as well so once we have everything in core post core roadmap is essentially looking into some of the features that we're not in our VP list so the Drupal mode featured and also color changing is also something that's on the top of our list we also want to make sure the theme can also be a sub theme as well too and other possibilities that are in our issue queues but we can't get to it right now given that you know we just want to make sure that we have a stable theme that can be included in core as well so I'll toss this back to Mike he's going to walk us through some of the challenges that we face within this project yeah so Mike take it away yeah so you know this is my first significant this is our first significant core contributions you know so and there's been a there's been a learning process involved right here you know talking about managing scope you know nice to have versus must have like I've been fairly strict on this if it can't be done at the theme layer well then you know yeah let's do it but we'll push it back to some other time you know or yeah managing enthusiastic contributors are very skill levels holy cow there's a lot of people that really want to help out and it's I'm so thankful because a lot of people are just like kicking butt and taking names and it's just it's just pretty amazing but geez keeping track of everyone managing people being able to review and stuff like that is a heck of a lot of work and like and honestly just like kind of managing my own mental health I know you know it's it's easy to to look at other people and and and say like hey settle down it's not that important you know we're going to get by regardless but like when you're in the middle of something and just like you have you know people saying you know there's so many issues that are either rtbc or ready for review and you have like a whole bunch of work it does get a little bit stressful and like like there's that thought process you know that we do have like you know a deadline to get it in decor and there's there's a lot going on and that's something that like I've been like struggling with managing you know myself and I'm pretty sure Putra and others have too and on top of that you know it's finding finding the time to contribute you know like we are we work you know we work for Lullaby and and we do our you know our full weekly allotment of billable hours and on top of that is when we do our aloe vera contribution and like other contributions and you know on top of that we have to balance you know our lives and our families and stuff like that you know I also want to highlight some dependencies that we need that we want to get into core I'm kind of switching gears here I'm going to add a number of post-css plugins post-css is already in core I mainly thanks to declare a team and thank you we want to add some some additional functionality some plugins to this and I'd love it if you all could just like kind of click on these and comments and and you know tell us your thoughts on these issue cubes that'll that'll kind of inform the conversation right here so custom media is just one that allows you to use like the equivalent of like CSS variables in your media queries post-css RTL is just a plugin that basically converts your your you know your your you know your left to right layouts to right to left layouts so you know you could you I might be typing in margin left and it will convert that to you know dear RTL margin right and it's just like super handy and works perfectly post-css nested talking to Larry it's kind of like a long shot but I'm still hoping we could get it in there that's one where you can use like kind of like SAS like nesting syntax within CSS and and it just makes the code so much readable for me and then there's another plugin called picks to RAM and it just converts all pixel units to RAM units which are more accessible because they scale at different and different scenarios where pixels do not and right now we're just writing our our CSS and pixels because I find it personally easier to kind of understand and so like join us we need help like I like I tell you like there's a lot to do there's a lot to do yeah yeah and um so I know you can't click on this link right now but we're going to share our slides and and then you can do or you can just like navigate to our project page and there's documentation link at the bottom right and then you can you can find it right there we have a we have a weekly Drupal Slack meeting it's in the D9 theme channel and if you're not in Drupal Slack you should totally join it's a lot of the community conversations there and we do weekly meetings Matthew Tift moderates the thank you Matthew and yeah um so coming up right after this like so like after we're done with our question and answer session you know maybe go get take a little break and go into sessions and take a look for designing for casts the process behind Oliver that's Jen and Jared who are the amazing designers that put this together and I've seen this presentation before and it is fantastic and if Jen and Jared if you are listening no pressure but but it's it's awesome so yeah uh so uh question time if you have questions uh for getting your uh idea into core and or questions about Olivero uh go ahead and go ahead and ask him and I'm gonna I'm gonna bring up my dog here too I'm gonna bring in my dog as well too everybody wants to see the dogs everybody wants to see the dogs we also have a slide for the session evaluation as well too um if you can provide some feedback for us that would be helpful as well yeah totally this is Dexter all right welcome welcome to the stage Dexter um so we did have a couple questions that came in um during the presentation um so and if anybody has any others um please do pop them into the chat quickly as we can get to them um the the first question I was gonna pose to you is from Gabor he says um how did you make the case for your company to sponsor the effort yeah so we just kind of did it and didn't like really say we were gonna do it and then we said by the way we're doing this you know and you know this is gonna make it yeah I think when it comes down to it like um Lullabot as a company um you know we're open to like um collaboration and um we also like to encourage people to um contribute back as well too and when Lullabot we also have 20 percent time so you know we can take spend some time on um you know doing contribution work so it's it's really the culture at Lullabot that allows us to you know take the time um to really dedicate into this project so thank you to Lullabot as well too did you ever have a formal conversation like once you'd already been doing it with 20 percent time did you ever have a formal conversation that said we're doing this you know let's kind of make it an official thing totally not yeah yeah Lullabot has a very rich uh rich history of contribution like like going all the way back into like Drupal 4 like we've done like a lot of work on the form API Karen Stevenson was like getting like fields uh into like Drupal 7 core like CCK and like all of like Lullabot has a huge a huge uh um culture of doing that and honestly I didn't feel the need to say hey can we do this you know because there's kind of an implicit understanding you know in in addition to that Jared Poncha is one of the directors um our design architect is one of the directors of Lullabot and and we're like we also have a culture of just like being open and and you know we have these team calls and I said well hey I'm starting to work on this you know I'm doing this and you know it wasn't so much of a conversation but like hey this is what's important to me at this given time and this is where my efforts are going that's great another question we have from Tim it says what advice do you have for someone who wants to propose an initiative but doesn't feel ready or feels like an uh has imposter syndrome um that is holding on that I have the same feeling as well too going to this project to be honest with you um because you know I've never done any contribution work until the Albuero project so it's essentially you know that imposter imposter syndrome is going to come up but at the same time I think if you do your due due diligence as far as like doing the appropriate research and also forming your documentation and have a really solid um you know game plan going in it I think people would be receptive and would be able to you know help advocate for what you want as far too I think the goal here is making sure that you have um your roadmap in place and laying out all the different work that are going to be going into it so that other people understand the work and also help make it happen as well too yeah I want to reiterate what Putra said like having a solid plan just makes things better so you can kind of like talk intelligently about it um you know you I would say throw your ideas into the Drupal ideas issue cube but like that being said like there's always a possibility that you might not get like some responses and stuff like that so in that case I would I would say like number one you are welcome to reach out to me personally like on Twitter or through my Drupal.org contact form or my email address is mike at hershal.com if you can spell my last name properly and I can help you through there um I can tell you that Angie and Gabor have been like very helpful for me because you know I remember having these conversations with Gabor and saying like listen you know like we're creating this like you know we're exposing our designs to the community here what do we need to convey and uh you know I think he was saying like you just need to make sure that you know people understand that there's a thought process behind this whole thing and then you know and and and he like he and Angie have just like so much experience and and I I would say like um I don't want to kind of put them on on on like out there but like you know if you're able to reach out to them uh like they're super great resources and like you know part of their job title I think like if I recall correctly is Gabor is like the initiative manager of initiatives or something like that sorry Angie and Gabor great thank you very much um any questions I'm just looking at the chat to see if anything else has come in uh it does not look like it Gabor says Angie and I are happy to help and get started with my initiative so there you go totally awesome well I hand it over to Tim thanks very much guys thank you thank you all so much it's wonderful to have both of you Mike and Putra talking about the process of actually starting a core initiative and using using your amazing work on the Olivero theme as a case study for that I think is just extremely cool as someone who's proposed a couple core initiatives myself um having that end-to-end example of how it worked and how it works so successfully is incredibly valuable and I think um I suspect we might take this recording and put it right on the core ideas page of here's how you do it right so we'll get that out um yeah you say you say that now but we're not in core yet we'll get there we'll get there um uh so um Mike you mentioned that you'll be sharing the slides I think there's some folks in chat asking so if you want to just let folks know where you're going to do that we can also upload speaker slides to the nodes on events that Drupal.org so we may repost them there for anybody who's asking um in the meantime I'm going to briefly stop our broadcast here we're going to be coming back for a live intermission with some desk yoga so if you're like me and you've been sitting in an office chair for 12 hours a day you'll you'll probably really enjoy that get energized um and then we will have a session on uh making the transition mentally and technically from CMS to DXP CMS to digital experience platforms so stick around if you want to join us for that or take a look at the rest of the session schedule thank you again to our speakers and we will talk to you all soon thanks everyone bye everybody