 So welcome to the session on what's new with the Project Browser Strategic Initiative. I'm Leslie Glenn, I'm one of the Initiative Leads for the Project Browser. So this session is just a real high level look at what we've done, what we're working on and how everybody in this room can help out. There's something for everyone, so that's what the session is about today. All right, so real quick, I'm the Manager of Client Success at Redfin Solutions. I'm the co-leader of this initiative with Chris Wells. I was on the Drupal Association Board for a couple of years, so I learned a lot, so if you're not a member of the Drupal Association, join, because they do great work. A lot of things behind the scenes that you don't even know about. And that's it for introduction. All right, so what is the Project Browser Strategic Initiative? I know some of you have been to other sessions and know what it is, but others might not. Basically, Dries introduced it at DrupalCon North America in 21. Basically, the idea is to make it easy for site builders and those new to Drupal to find and install modules on their Drupal site. He expanded that this year to say, the idea is to be able to discover great modules from within your website without going out to drupal.org and to click a button to install those right on your website. So all in one place to find and install modules is the goal. So how do site builders today find modules? Most people go out. They go out and either look on drupal.org or they go to Google and search for modules. We wanna make it easy for you within your Drupal website to say I wanna add some functionality and be able to search, filter and find modules that'll help you do what you're looking to do. Right now, the filters on the Drupal.org page, how many people have looked at the Drupal.org page to find modules and you see the list of filters and you say, oh my goodness, and you never find what you're looking for, right? So that's- There's so many great modules that you're never finding. Yep, so that's what we're trying to help with, okay? Right now it's going to be a contrib module, so it'll be in the contrib space for now. So the project browser's strategic initiative, if you wanna read about it, there is a strategic initiative page. If you have the bit.ly link, there is all the links on the slideshow in that Google Doc that you'll open up. But the goal is to make it easy for, again, site builders and those new to Drupal, so we're targeting people that aren't developers and don't know about modules necessarily as well as others do, have an easy way to find things. One note is the screenshots here for decorative purposes only, you can go to the Google Doc to see the screenshots much better than you can up on the screen today. Not that you can even see my screen today, but that's another story. Is there a brightness control in this thing? No, Shawn tried in the last session and now we couldn't. Okay. All right, so what's the problem we're trying to solve? The Drupal community has made it much easier to install a Drupal site, much easier than it used to be, right? You can just go to drupal.org and hit try now and call up a Drupal site. But how do you find modules? It's like walking into a grocery store and you walk into the cereal aisle and there's 100 different types of cereal. How do you know what to look for? And once you find it, is it the correct thing? So that's what we're trying to solve. One of the first things most people do when they have a site they install it, the next thing, what's the next thing you wanna do? You wanna add some functionality. You have something that you wanna accomplish with your website, how do you go about doing that? So our MVP goals when we first started with this initiative when Chris and I said, okay, we'll help out, we'll lead this thing, were the ability of browse modules compatible with a version of Drupal for the website you're running. So if you're running a Drupal 9-set, you're not gonna get Drupal 7 modules like you do when you go to drupal.org. You're only gonna get modules compatible with your website. We wanted to provide instructions for downloading and installing modules. Again, this was for MVP. We wanted to filter by category and maybe add some advanced filtering, which we did get that in. And we were gonna start out having this be a contrib module because it's a lot easier to get something into the contrib space than into Drupal core. So we've done all these things. Here is a contrib module. You can't see that right now, but we do have a contrib module. We released a beta version back in July. If you go to the project browser page, which is just drupal.org slash project slash project underscore browser, that's our project page. There's a try it now button. Just click on the try it now button. It'll spin up a Drupal 9-set with the project browser installed, okay? So basically that comes up in Gitpod. So you'll get a website. It's gonna be in the top right-hand corner up here. That's where the actual website is. There's a lot of other code, a lot of other great things for somebody that's more sophisticated into a lot of the different nuances of a Drupal site. But if you just wanna go test it out, go to this operate, and there's a button up the top to expand this full screen. So, contribution room is open today and tomorrow. Come on down, check it out, give us feedback. We've been having things called listening sessions where we do interviews with people as they sit and look at this. And it's been extremely helpful in having us change things, target things so that it's useful for the intended audience and for people who are knowledgeable or Drupal. We want it to be good for everybody. So come to the contribute room and look at that. So basically, once you spin up your Drupal site, we have a new underneath the extend. Everybody's familiar with the extend to refine modules. We have a new link called browse. Now we've recently got feedback that says why when you hit extend doesn't go to browse automatically? Well, that's great feedback. Why should I have to get out here and click on that? So things like that that we might not see because we're so heavily into this, your feedback would be super helpful on that. So basically, you just go in there and say browse modules. So here's your first look at the project browser. Well, let's just pretend you can actually see my screen. Close the back, can you see my iPad? Ha, ha, ha, ha. Basically it has categories on the left. There is text up here, text at the top is temporary. The text at the top basically says that we do not have a Drupal 9 version of Drupal.org right now. So this is pulling from the Drupal 7 and we created like a mock API to kind of pull data from the Drupal 7, but it's not real time. This will be Drupal 9, it will be real time information. Now it's slightly off. So you might not find an exact match between what's on Drupal.org and what we're pulling from the most popular modules, for instance, because it's just a mock just to make sure that we could do that. So that's what that tells you. There's a contains, find me a module that has a name like or something like that. And then this is a key part here. What are the default filters? Basically it has to be covered by security and it has to be maintained, actively maintained. So those are the two things and it has to be compatible with the version of Drupal that you're running. And then what are the cards that are displayed? Oh, the default sort by is most popular. So this will show you the most popular modules in terms of usage for the version of Drupal that you're using. So we've made great progress so far based on all the contributors that we've had. We're gonna get into what's on those cards in a few minutes, but we had listening sessions like I talked about. We decided what the default criteria would be based on feedback from everybody. We created a grid view and a list view. We did a first cut of proposing. The descriptions for the categories. We'll talk about categories later, man. Categories are a fun thing to try and figure it out. We did the mock API. Right now we're getting a detailed page from Drupal.org. We released an alpha and then a beta version. Currently we have instructions which I'll show you for downloading. I'm sorry for downloading and installing it using the poser. And then somebody that I talked to you this morning, we allow multiple sources of data. I think it was somebody from University of Colorado. They have their own little set of modules that they can, their websites can only use a certain set. So working on the ability and config for you to add, this is my source. And only pull modules that you want to. So you can create like a curated list then? Yes. Like a curated list, yep. So that's all stuff that we have accomplished so far. So what are we working on now? Where can you help out? Big thing is we're trying to update the content on the Drupal.org project pages for display on the cards. So we're starting with the top 100 modules. We're looking at adding logos where there aren't logos. Proposing short, short, non-technical descriptions. Non-technical is key there. If you go to Drupal.org right now and look at any of the modules or project pages. Correct. No consistency. Well no, I mean the module many times work really hard. They do a great job with their modules but they're always, for most part, very technical. So their descriptions are very technical. So we're trying to put it in terms that anybody can understand why would I want to install this module. So if you can help us do that, that would be great. And we're also looking at proposing one to three categories for each one of the modules. But we're starting with the top 100 just because that's what will be displayed first. We'll eventually get to the 50,000 with your help. I'm going to go through each one of these with a different slide. We're going to create a base template for making the project pages more consistent. Every project page you go to, completely different. Everything's everywhere. Where do I find the information I'm looking for? I'm trying to compare modules but the descriptions are wildly different. So we're looking at how we can make that more consistent. Trying to get maintainers involved. We're going to migrate with the help of the Drupal Association and some folks that are helping them out to a real Drupal 9. So they're trying to get Drupal.org on Drupal 9. They're doing that piecemeal but we'll need the Drupal 9 endpoint to be able to pull from real-time data from. Let's see. Drupal work is still DA. I'm sorry? Seven and D7. It's in seven still. Yeah. Oh my goodness. It's in seven. So they're working on moving it to nine. It's a big project. We're working on replacing those install instructions downloading and installing modules with an actual button to install it right there on the spot without you going to Composer and having to know the terminal and all that kind of stuff. It'll be a push button that install it. I'll talk about that in a few minutes a little bit more. Converting from GitLab CI to, I'm sorry, from Drupal CI to GitLab CI. You have a slide for that and then we're making Svelte more themeable. And I'll tell you what Svelte is. Svelte, the JavaScript API. Yeah. Okay. All right, so the first thing we do is updating the top 100 modules as I said and we're updating the three things. The logo, the short description and the category. So that's the first thing that we're doing. So for those who want to contribute there is a meta ticket. A meta ticket just means a high level ticket with a couple of child issues on there. So there's meta tickets for each of the top 100 modules then there's a child issue for the logo because a designer might want to work on that. There's another ticket for the short description because somebody might want to do that and then there's one for the categories. So you can choose to do all of those child issues or just one depending on what your expertise is. Once all three of those get done and these are suggestions, we're then gonna move that meta issue into the maintenance queue, the module maintenance queue so they can look at what was suggested because they have to actually make the changes on their project pages. So we're just suggesting. So we have this Kanban board to make things easy to find. So there's a Contrib Kanban and I forget, I'm sorry, I forget who actually created that but we have a project browser and the link is in the slide deck. Actually go and see what's available to work on. So as I said, there's three child issues. It's gonna go from needs work which means no one's worked on it yet. Needs review which means somebody might have suggested a description and we need you to just review it and say, is it non-technical? Can I understand it? So that's a great way to contribute. Just read through what other people have done. Same with the logo. Is it 200 by 200 pixels? Is it a PNG? Is it recognizable for this module? So those are easy things for anybody. You just sit down here 15 minutes, sit down and help us out. But the instructions were in the meta issue so instead of creating the instructions across all the child issues, the meta ticket has the three children but it has all the, so if we have to change the instructions, we change them in one spot. All right, so the three things are, propose a review logo, pretty straightforward and you just upload the logo that you create and then somebody reviews it and then we send it over to the maintainer. We've had a lot of designers actually who haven't had a chance to contribute to anything say, wow, here's my chance. So if there are people on your team who are good and they don't have to be designed by trade, that if they're just good at graphics, have them create some of these. That's an easy win for that type. Go ahead. Is there a standard or design guide? There is. There is a standard. It's in the meta issue. It tells you exactly what we need you to do. Okay. Yep. All right, the short nontactical description again. So you just basically put it up in the summary there what you think the proposed description would be. And again, we'll help you walk through all this. Once you do one, you can keep going and then the categories. So where you begin, basically go to the con bond board, look at the needs work. If you want to do something from scratch, look at the needs review. If you want to review someone else's work, don't touch the active ones. The meta tickets are just there as a container for the children and we'll give those to the modular maintainer. We can't put these in the right order. Needs work, needs review. This contoured con bond doesn't let you do that. So just go to needs work if you're looking for new stuff to do. Now let's talk about those project detail pages. The project detail pages are where you find information. So you go to the serial, now you've narrowed it down. I want to get this particular type of product. How do you find more information about that product? Well, you go look at the box, look at the ingredient label and other information. How do you do that on Drupal.org? There is no consistency and often, very often, there's more than one module that does something very similar and how you determine which one of these modules is a better fit for you. All right, so here's an example of a project detail page and this one happens to have description and it has some features and has some dependencies but as you notice, it combines Drupal 7, Drupal 8, Drupal 9, there's information for all of those all in the same basic thing. Our target audience, again, remember, site builders and those new Drupal. So we want to make these project pages easier for them to consume to say, does this module, at least on the surface, seem to do what I'm looking to do, my goal, whatever I'm trying to do. I'm adding a publishing workflow or I'm adding a storefront or whatever I'm doing. Does this module at least seem like it's gonna help me out? So we have a proposed template for improving the body field in terms of what we think should be at the top of the description here. What should be at the top here, what are the most important things? If you know down the very bottom, it tells you how many modules have installed this. Why not move that up? How many people scroll to the bottom to see the usage when they're looking for a module? Probably pretty much everybody, right? Why not move that up and make that more accessible? We've had different fieldings on whether the maintainers should be high level. Do we, doesn't matter who maintains these modules. Well, to me, I know a lot of people in the community, so I know if a module is written by somebody more than likely, it's a really good module. But if I'm new to Drupal, that's irrelevant to me, right? But how did you learn which of the maintainers were who you were trusting, so I know what the model is, maintain those modules, so it's still important. Yeah, exactly, yeah. If you know, if you're part of the community and kind of know that, yes, that's important information. All right, so so far, so our first MVP was the Alpha version was pulling in the Drupal.org page. So we had the card and then we'd link up to Drupal.org to do the details. Now, if you go to the, remember I told you, you can click on and spin up a site. Now, basically, you're gonna say, oh, that project detail page, that isn't very good. Well, it was just a proof of concept. So our current project detail page just says we can go out to Drupal.org and pull information from the project detail page. No thought has gone into what should be where, that's something that we're working on. So don't be confused when you go to the detail page and say, oh man, what are they doing? It's just a proof of concept at this point. Go ahead. Is there any, going to be any requirement for people to write actual module documentation? Because I think that's where one of the things that's really lacking on those product pages is like, there may be a documentation link, but it may be very vague or minimal. So the question is, are we going to be creating any documentation for the four module maintainers, maybe people that are creating new modules in terms of, this is best practice for how to create, yes, yes, that is something that's gonna happen. If you'd like to help us to write that, more than welcome. Awesome. All right, so let's talk about categories for a minute. How many people actually, when you go look at a Drupal module, care about what the category that the module is in. If you remember when I showed you the browser, categories on the left, because people typically want to, they're looking for something, they're looking for a storefront, so let's go look in the e-commerce category, right? But right now on Drupal.org, there's 55 categories, or 56, I think one was added. There's 56 categories, and modules have anywhere from one to 30 categories assigned to them. There are modules that really are in 30 categories. Yeah, so we're trying to clean that up. Our first attempt at that was to take the 55 categories and say, how can we combine them? Which ones can we throw away? Do we need a, I think it was C tools. Do we need a C tools category, or no, sorry, CCK. Do we need a CCK category anymore? No, we don't need that. That was way back in the old Drupal days. So there's some categories we can drop, but can we combine them? Do we need to add new ones? What makes sense in terms of categories? So we've spent the last six months or so trying to attack it that way, looking at the 55 categories. Then we had a Boff and Prague recently, DrupalCon Prague, where somebody said, actually Suzanne Dekochewicz from Evolving Web said, why don't you just start with a minimum number of categories? So we came up with like 14 categories during the Birds of the Feather session that we had with some, you know, we probably had 20 people from the Drupal community, all different skill levels and interests. We came up with like 14 categories. So let's start there. Let's see how many modules fit into these 14 categories and then let's just add a few more. So instead of taking the 55 and trying to work with that, we're working up now. So we'd love to have feedback on that. We have a one hour survey that you could take where we have those 14 categories and we give you a bunch of, just a handful of modules and say, why would you, which category would you choose and why? So we could use help. So again, to come to the contribution or this links in this slide deck. Do I have the contribution time? I'm there all afternoon today and tomorrow. So stop by anytime. Okay. Okay. So that's for the categories. That's going to be a lot of fun. All right. So then the real Drupal.org API. So right now we're pulling the module name description categories and security coverage from Drupal.org, Drupal 7, and we're using that in the current mocked version. We will be using a real API eventually, but for now we're just using this mock API to pull that information. One issue that we have is that the fields on Drupal.org, because it's Drupal 7 and going to Drupal 9, they don't want to add any new fields. So there are things that we wanted to add. But right now they're too busy trying to get it to Drupal 9. So we have to work with what we have. So eventually we'll get what we want in Drupal 9. What are some fields that you want to add? We were thinking about something called use case. For instance, use case being the goal. What's your goal? So I want to do a publishing workflow. I want to do a storefront. I want to do a library site. I want to do, but now Drees introduced a recipe of the starter kit initiative, which basically takes use cases out of our hands and now recipes will do that. So our use case was going to be, I want to create a storefront. What are the 20 modules that I need? I don't want you to have to go out as a new person and say, okay, I need this one. I need this one. You want to create a storefront? I want to give you a collection of 10 modules and install all 10. So that was our idea of a use case. Recipes has gone beyond that to actually say, we're going to install these 10 modules plus the configuration that ties everything together. So it's gone a little beyond what we had originally considered, but that's the recipe initiative, which is working hand in hand with us to actually, or working closely with us to actually make that all happen. So that's all really exciting news for somebody new to Drupal, you know, to actually just be able to do that with a couple clicks of buttons on the website versus go to Drupal.org and say, oh my goodness, I'm lost, I'm out of here, right? All right, so automatic installs be a composer. So the goal is to, like I said, decide what you want, click a button and automatically install it. So Ted Bowman and his team are working on the automated updates initiative. As of yesterday afternoon, they did a big merge into Project Browser, which is they got all the back end code on how to figure all that out. And it's very complicated. What version, what's compatible, what dependencies, what this, what that, so that whole composer stuff. I'm not that technical. I'm a developer long ago, but I'm not a Drupal developer right now. So they figured all that out. There's a whole great team that's working on that Drupal Association staff, plus all kinds of contributors. We don't have the UI built yet. Right now there's a download button that brings up some instructions. This says go to composer and it gives you the commands to run, go to a terminal, open proposal, run these commands, but they have figured out how to make that all happen. We don't have the UI in place yet, but that's the next step. So if you want to help get that UI going, but the automated updates initiative has done great work to enable the Project Browser to do what we need to do to make this easy. Question? Have you given any thought to alternative ways of, but if you've got, but one of the scenarios I see quite commonly is that the people who are making decisions about we want these modules and we want, because we want to do this with the content and not the people who understand how a workflow of configuration management of getting the site in production in a way that it stays on are familiar with. So they have to make a request to somebody else. Do you know whether anyone's given any thought to whether the UI could have the option of going straight to the Mac end or perhaps go where people want to redirect it to a different workflow so that effectively raises a ticket or something for somebody to go on there? All right, so. Have it in a controlled manner. Okay, so I believe the question is when we're doing this on American stall, have we given any thought to having the user give some input in terms of what they would like to do as opposed to what will be done by automatically? Is that your question? And no, what I'm thinking of is the people you're catering to are people who are building the site and worrying about what is it that they, people using the site are going to see. Then in a lot of sites you have a team of technical people behind the scenes who are making it all happen and the sites stay up. But they tend to be people who do be in stores and modules. So what I was thinking is that when the UI comes along has anyone thought about there is another scenario where you want to actually say that put this all through configuration management? And probably that means you want to tell somebody who has the technical expertise to go and do that. Right, okay. So let me rephrase, I believe the question is have we thought about allowing, disallowing the user who's just deciding what they want to install from actually installing it and defaulting to a more technical group to actually do the install? And I think that's probably going to be permission-based. I can't say specifically, but my guess is that it would be permission-based. We're also in terms of the automated updates. I know there's a lot of thought that went into what do we have to tell the end user about what would go behind the scenes so they have some, there might be some options and they might not have to. I mean, in some cases, your production environment might not be even writable. So what you're automatically installing wouldn't happen, but maybe you would create a patch file and then you could take the patch file and apply it later or something. I don't know, but yeah, there's a lot of different scenarios. I'm going to tell you how to get involved and how you can reach out to ask all these type of questions. I'll come talk to you later. But yeah, but those are all excellent questions. Thanks for bringing all that up. There's so many different aspects to this whole thing. All right, so anybody interested in DevOps? Any DevOps folks in the house or no DevOps folks? All right, anybody interested in converting from Drupal CI to GitLab CI? That's where we're going. Everything in Drupal is going to GitLab, right? They're working really hard on that. They've made great progress on that. So, Irina is giving a talk tomorrow on this exact subject. GitLab, Drupal CI to GitLab CI. So I recommend going there as a starting point and then get involved. Project Browser has volunteered to be one of the initiatives that's going to do this first as part of a, you know, let's see if this works and let's see how this works. So if you want to get involved in doing it, hop into the project browser. I put the issue in the ticket here, in the slide here for you to be able to do that. All right, and then, I'm just checking the time here, 10, 34, okay. Frontend, anybody interested in the frontend or have folks on the team interested in frontend stuff? Svelte, anybody heard of Svelte? Svelte JavaScript? My goodness, people who abuse React and all these other frontends, they use Svelte. They say it's so intuitive and so easy to use. The initial group of people, Matt Grasman and a few others, I believe, when they first built this, built the mock, you know, the very first, while we're having our first meetings, actually they were sitting at their desks on the call creating this prototype. They created the prototype using Svelte. Well, this isn't contrib, we want to get it in core, right? So how do we get it in core? We need to get Svelte into core, right? So we've got agreement that Svelte will be able to be brought into core. So if you want to be part of that initial group of people that knows Svelte, definitely come work on the issue. Come hop into the calls and learn that. Anybody that's in New England or wants to come to New England, there's a full day Svelte training being held in November. Chris Walsh, who's the other initiative lead, is giving that training. So if you're interested, come to Netcamp in November. Very inexpensive and it's a good camp. All right, so that's Svelte. Oh, there's other things to frontend folks to do as well, not just Svelte. We're trying to make Svelte themable, I guess, and I'm not a frontend person, but it creates HTML, not HTML, sorry. The HTML is rendered by Svelte, it's not HTML native. So we have to try and make that themable. So that's a whole initiative to make that themable. So if you're interested in doing that, you want to run accessibility audits, anything frontend-wise we can use help. Just give us feedback on the UX, you know? Those are all frontend things that people can do. All right, so looking forward to some of the goals. I did tell you about recipes and installing the configuration, but we also have something called ecosystems, which is something on dooble.org right now. Like there's an e-commerce ecosystem, and it's all the modules, like e-commerce payments and e-commerce this and e-commerce, all the things that work together. So do we want to have a filter or a category for ecosystem? You know, I want to install everything that has to do with a particular type of functionality. So that's something we're looking at. That's downstream. How is the ecosystem different than use case? Use case is the goal. So use case is across categories, across things. These are all the different things I need. I might need a workflow module. I might need the media module. I might need something else where ecosystem is more, I depend on this module. So e-commerce payments depends on e-commerce. So it's more like their own little ecosystem versus this is the goal of what I'm trying to accomplish. Yeah. And then we, at some point, we might expand to include themes. I think recipes will get in there before themes because you don't typically install multiple themes, or switch themes that often. So that's further downstream, but it is a project. So this is the project browser. We started out with modules, recipes will be next and then maybe themes. And we're hoping to get this in core. So the goal is to get it in core in Drupal 11. If you saw Dries's Portland talk, he spoke a lot about getting project, project browser was a big part of his strategic plan and getting that into Drupal 11 in core is the goal. We're hoping to get it in Drupal 10.2 as a contrived, as a release contrived module. That's the goal. So, but we need all your help to make that happen. It's a big job as you can see. Recipes, again, I said we used to call these use cases, I've discussed that already. Why should you contribute? For those of you who have been around Drupal a long time, trying to install a Drupal site in the old days was really hard. Trying to create a development site. Man, they used to take the whole contribution day just to get somebody to spin up a development site, right? So why not make browsing for modules easy too? Contribute to that. One of the first things people are gonna do is go to the project browser. Wouldn't you love to be part of that group that actually creates that experience for everybody that uses Drupal going forward? So there's a lot of great reasons to get involved and consistency across the project page is that it helps everybody in this room. So there's many reasons. So I do have a link on here with all the contribution opportunities. Talked about listening sessions, helping with the categories, helping with the project description, helping with just the content, the content strategy. How can we make those descriptions better? You come to the card, choose your logo. The name of the, the chosen logo, the name of the module, a short description, and then the three categories. Let's make those cards. So when somebody goes to browse, let's make those cards as good as we can so that it really helps people out. And then we'll get to the rest of the project page after that. How do you, how can you join the initiative? We have a project dash browser channel on the Drupal Slack. Hop in there, say hi. We meet on Tuesdays at 4 p.m. Eastern. We meet on Wednesdays at 10 a.m. Eastern. Now what's the difference? Tuesdays is usually more the site builder, the front end, the UX, that kind of stuff. Wednesday is the more tactical group, the people who are actually implementing it. So Tuesday we talk about what we wanna do. Wednesday they talk about how they're going to do it. You welcome to come to both. They're asynchronous, they're in the Slack channel so you don't have to come at those times. Hop in anytime, read the different threads and put in your comments, put in your feedback. Super helpful to us. Never make that one send me in too early. No, no, I know that you were early, but I know. So they're asynchronous. They're asynchronous, right. So you can just hop in anytime you want and join those calls. I'm supposed to leave Mopin for 24 hours, but honestly, doing all the other issues, I haven't even closed a lot of those so they're still sitting there. So hop in, I will close those, I promise, and give credit. If you wanna just do that, help us close issues. You can help that, create issues. I've only created 50 of the top 100 so somebody wants to create the next 50 plus three child issues on each. There's 150 issues that we need to create so we can use help on that, anything. We can use help with everything. So come by the Contribution Room today or tomorrow. Test the latest version. Give feedback on the project pages. All these things I've talked about. The content, but everyone's welcome. So if you know somebody that's here, they're not a developer and they're not a coder, they feel like I can't contribute. Everybody can contribute to Project Browser. There's something for everybody. We had a room full of people at Probe, two rooms. We had people in the technical room, the general contribution room, and then I was in the mental contribution room. I had so many people I couldn't even handle them all. I just said email me your feedback because I couldn't talk to them all. There's too many of them. So great feedback, thank you to the community for that. And we need to get current maintainers involved. If you maintain a module, and you know somebody that maintains a module, give us your feedback as well. How can we help you make your project pages better? As you said, how can we make a documentation in terms of going forward? How do we make this all better for everybody? All right, so Chris and I had the initiative leads to reach out to either of us. Chris from Redfin. I'm Leslie G. We both work for Redfin Solutions and I want to just give them a shout out for sponsoring our work. There's a whole list of resources here in your slide deck. And that's it. I know I've answered questions during it, but any questions now? Anybody? Go ahead. So how many people are taking part in this initiative so far? Oh man, I'd say easily 50 people. You know, they come and go. They might come and give us five logos because they contribute at a particular event we're at, but that's five logos that are done. Other ones have stuck right with us from the beginning. We do have a group from the Drupal Acceleration Team, or the Aquare Acceleration Team, there's like three or four individuals. We have some people from the DA, Drupal Association, that are contracting, that are helping out. And then we have a lot of community members that just come to every meeting and really have done a lot of work for us. So yeah, the more the merrier. This is something that everybody can be involved with, and I think it's a good win for people who have never contributed. He has a place for them to come, just go to the issue queue. The issue queue is super scary, right? For somebody who's new. So come and we'll show you how to just create a logo, update the issue, and then wow, that's not bad. That's easier to do. So yeah, any other questions? Yep. Do you have any kind of rating on how involved, how involved the configuration of the module is, or how technical you need to be, or how much Drupal knowledge you need to do, and what are you getting yourself in for when you install this module? Because some modules are easy and some are hard, and that doesn't necessarily map to the function app to what it's doing, but knowing upfront that I'm gonna have to spend some time or know what I'm doing to use this module. Right, so the question, just to repeat it, is how much do you have to know to use the configuration of this module? How easy is it to install? Out of the box, simple, you just install the module. That's it. Is there a configuration? Yes, there's a configuration. I don't think I talked about sources, which I probably should have at some point here. Somebody was talking about, I think I did talk about this. My college has these certain things that you can install to this source. There will be configuration for that, but if you have your own configuration, your own source of modules that you want people to stick to, you're gonna have enough knowledge of Drupal to be able to go into the configuration and select or deselect what you want to include, right? There's also gonna be, right now it only brings back contrib modules. Do you wanna see core modules as well? So that'll be a configuration, but that requires some knowledge of Drupal to be able to do those types of configuration. Have I seen it personally? No, I know of its existence, but we're trying to make this, remember, Dries's intended audience is site builders and those new to Drupal. So we have to make it as simple as possible, but yet give all the flexibility that everybody else wants at the same time. So we're trying to do that. I was thinking more of a temperature or a gauge of easy to hard as far as... Should be easy. I mean, out of the box you just install it. Well, I mean, you can just install any module, but to actually... I think it's usually more like a module attribute on the browser, on the browser. I see what you're saying. Yes. So that when, you'll take one module and it will be like a redirect module. Yes. It's very easy to use. Yes, okay. I understand. But then another module will be like, well, you got to configure rules and the rules takes 20 hours to get it together. Yes. Yes, yes. Yes, thank you. Yes, thank you. It's like this, if I install this module, I'm not done. Right, correct. That's good feedback. I got a lot to do. Yes, that's good feedback. I was thinking you were thinking the browser module itself. You're talking about having that attribute on modules and having you be able to filter, at least have that displayed. Maybe that's something we put in the documentation for the module maintainers. How difficult is it to then install and configure your module? Markety or something? Well, I was just saying that's more on the module maintainers to work on the documentation pages than it is for, you know. It'd be great if it added a documentation page for you to have that link available for it. But, you know. But maybe we do have some kind of a flag that says easy to install and not easy to install. Yeah, if you could put that in the, if you could hop into the Project Browser Slack channel and just put that suggestion, any suggestions you have. But I think we're running out of time. Any last question, one time for one more maybe and then we have to let the other, the next presenter in to set up. Go ahead. How happy are you with the current state of the project? The question is how happy am I or are we as a team about the current state? We're really happy. We've gotten way more done than we thought we'd have done at this point because we've had all these different groups come in and help us. The automated updates initiative, having them be where they're at and be really close to just hitting a button to install, we thought that would be a lot further downstream. Having some of the advanced filtering that we have in place, we thought that would be further downstream. So we've gotten a lot of help from the DA from different companies from different individuals to be able to get where we are today. But yeah, it's going really well. All right, very good. Well, thank you so much and we'll see you in the Contribution Room or on the Slack Channel.