 how to turn your omni-channel digital experiences from dreams to reality. With an open digital experience platform or DXP, you can build and manage digital experiences across multiple channels, such as websites, portals, email, and mobile, keeping the visitor at the center at all times. And that while being connected with your existing ecosystem and back-end, such as your preferred CRM, ERP, and digital asset management solutions. 5. Managing Content Websites and Environments in Drupal and Drupal Cloud Building marketing campaigns across sites, email, and mobile with Modic Marketing Automation and adding data-driven personalization driven by an open customer data platform. You know me. Developers can manage projects and environments in Drupal Cloud, in fact, not just Drupal, also Symphony, Modic, or Node projects. Collaboration, code reviews, and deployments have never been easier with integrated GitLab repositories. Very detailed and transparent information. Logging and various CI CD features. Compliance and security will love the full history logging. Good afternoon everyone. I'm Dominik. I'm a co-CEO and co-founder of Dropsolid. And it's my pleasure to introduce the Drupal core initiative team. And it's really a pleasure for me because without this team, we would not be able to build our product because Drupal, as you can see, it's a central component. It's the heart of the product. And these people, they are the heart of the Drupal product. Give it up for the core initiative team. Welcome to this keynote. So before we start, I don't know if you've been here in the break, but we are in the last minutes of our little rooster auction. So the rooster is looking for their final home. And we are at this stage right now, but we only have 22 minutes left. So somewhere in the middle of our session, the rooster's final home will be decided. So if you go to the app, you have a chance to bid for the little rooster and then pick from five different organizations and pick which one you would like to donate that money to. So that goes to a good cause. So that's one reason to use the app while we're here. The other reason to use the app is to ask questions to all of the initiatives leads here. So please use the app to do that. And at the end, we'll have some Q&A, hopefully, if we have time for that. So with that, let's start with the Drupal Initiative Leads keynote for DrupalCon.lil. We are here to do this because I think it's really important to get together and to see all of these people for you to meet all of them and to see what they are working on. And more importantly is for you to see that they are really friendly and they would like to work with you all to make Drupal better in all of these areas. And I think what's really unique about DrupalCon, especially, is we have a very wide breadth of different people attending. So we'll have very developer-focused talks here. We will have very UI-focused talks. We will talk about developer tools. We will talk about promotion of Drupal. So a lot of different aspects that you could be involved with and you may be interested in. But this is all what makes Drupal happen. We need all of these roles to contribute and all of these roles to pitch in their part. And that's what will make Drupal successful. So first of all, we'll start with a developer-focused talk with Wim Lears. Hey, so I'm Wim. I work for Acquia's Drupal Acceleration Team. And actually I want to start with saying thanks to Morrison who's sitting over there from Calibrate without whom many of these slides would have been much emptier. And yes, you may also be wondering is that even a strategic initiative and you're right, it isn't, but it is an initiative or it's a grassroots thing, if you will, that is really going to help a lot of strategic initiatives, including, for example, recipes, automatic updates. And maybe you care less about config validation but maybe more about these high-level things like writing config via JSON API, GraphQL Arrest. Maybe you care more about more reliable advanced config management. Or maybe what you really care about is improved end-user experiences. But let me give you some context. How are we doing this? So in 2004, we started with a variable table. Key value pairs, the values are blobs of arrays of doom. So blobbyness is off the charts. Then in 2012, we moved it to YAML files. We made it diffable. Then we made it introspectable and translatable by schemas. And then we moved it back to the database performance. And then we added validation constraints. But this, this is where we are at today or at least a few months ago in terms of how many things you can actually write or validate via JSON API, GraphQL. So we're nowhere but the infrastructure actually exists and that's really unfortunate. So I believe we can do better. I think we should be aiming for this. Where only the few lines on the right-hand side of the screen need to be changed or added and you get the experience on the left-hand side of the screen where you get the familiar error messages when validating something. But the same messages should be appearing also in GraphQL, JSON API and other places. Unfortunately, this is the number, the percentage rather, of types of config in Drupal Core that are validatable back in December. And on the right-hand side is the only validatable piece of config type. So UUIDs is the only thing and every UUID is a string but not every string is a UUID and that is why we need validation to make sure it's actually what it is saying that it is. Back in December, we had 598 config types in Drupal Core. 27 of which were validatable. That's a lot of work. It's like a dizzying amount of work left to be done. And over those 27, 17 were just booleans and booleans do not have additional shapes besides true and false. So since December, we worked very hard to make sure that as many things in Drupal Core and Contrib would actually move forward significantly in terms of how much of it was already validatable. So we made things like labels validatable, config dependencies and we added new types, for example, machine name and langcode that are terms that are familiar to many of you. So today we're in a much better place. Today we're at 634 types in total. There's things that have been added in the meantime but 56 are validatable. So more than twice as many. And two of those, two of those 56 are config entity types. Menus and shortcut sets, config entities in principle are now fully validatable. We just need to start using it in JSON API, for example. So if we zoom out from the types, which is really low level and look at a fresh standard install profile, we went from nothing being validatable to 6% of everything in the standard install profile being fully validatable. Note that I say fully validatable. There's also partially validatable things. In fact, back when we started, 27% of everything in Drupal Core was already validatable. So the parts, the bits and pieces inside of config and now we're at more than half. So we're very much making progress but getting to 100% is going to take some time. But even then, even at this point in time I'm happy to say that this screen that I showed actually just the same exact slide before that is actually not a dream or an ambition. That is a reality today. In Drupal 10.2 this is possible as soon as you update an existing simple config form to use validation constraints but it's true that you only need to add those few lines to have it work in your config form. And so that's the first change record actually that I wanted to show you. Config form base now optionally supports validation constraints in Drupal 10.2. So it's going to be possible with a few lines of code being changed after that all you will have to do is add more validation constraints to your config schema. The other really important changes is that it's going to have a single test in Drupal Core and Contrib and it has been checking your existing config already but now it's going to also be verifying that it's matching the validation constraints. And we're going to make sure of course it's not going to disrupt Contrib. So if any of this interests you even in the slides but if any of the high level concepts that I showed you before maybe for example writing config for every issue in Drupal Core and Contrib to follow along or to contribute and we made it also really easy to contribute or to start exploring where things are at for your modules or your projects. The config inspector module now has additional columns on the right hand side that provide rich metadata so you see I know it's too small to read but that's fine the yellow warning signs. Those actually tell you precisely which types still need to be updated to have validation constraints and if you're exploring what could be next in Drupal Core or in your module we have a dash dash to do command that shows you low hanging fruit things that are almost fully validable and high hanging fruit things that if we were to make them validable would help pretty much the entire ecosystem. So we're making it easy to find the next thing to work on. So let's first get Drupal Core to 100% validatability. It's going to be quite a bit of work and we're going to do two live hands-on demos and you'll walk away with knowing exactly what to do for your module or for Core. So join us at the sprints tomorrow come find Boris or me and let's do it. Thank you. Yeah I told you it's going to be a deep developer topic but you care about this because you want your deployments to go smooth and you want your automated updates to go smooth and you want your headless applications to go smooth so this is the care that goes into enabling all of those underlying things and I really like the developer experience improvements that show you and help you prioritize where you can make the biggest impact faster. So our next topic is quite different but it's also really close to my heart so Philip is going to talk to us about localize.drupal.org which I helped create way back in the day and it enabled us all to translate Drupal into all of the world's languages and bring Drupal to everybody on the globe and it's very important to take care of so let's give it up for Philip. Thank you. Before presenting the localize port initiative, please let me pay tribute to a great Catalan linguist who died this year. Kathma Julienne was always concerned with preserving linguistic diversity. More than a way of communicating languages bear both social as well as even ecological value. Only a few of them are written languages but it is important to ensure they can all be used on the internet. Hence all the efforts that have been made throughout the history of Drupal particularly since the release of Drupal 8 and its multilingual API. The localize.drupal.org platform currently built in Drupal 7 enabled the community to translate Drupal core and country projects as well as share the translations. Any of you many of you who installed Drupal in this room transparent and downloaded translation from this very platform. Some translation communities use additional tools as a glossary for instance or they may wonder how they could retrieve statistics from localize and that means we should expose web services from localize and that was one of the first reasons I got involved in this initiative. And why we were inquiring people so this initiative originated in Ghent and we translators, developers, designers and local community members all interesting in improving this platform and making the translation process easier. And why we were inquiring people we had the feeling that translation communities were a bit isolated from each other and joining this initiative is certainly a great way of knowing each other and of knowing how we could help them. So while maintaining a permanent team is certainly not so easy we glad all these people have been contributing to this initiative for the last few months particularly people like Stefan who wrote a lot of code. So it's still time to join us here in Lille in Country Broom or later on on the internet. Now what is the current status of the initiative? We still have the first phase that is we at the initial port phase where we're porting features from the Drupal 7 platform to the Drupal 10 platform and as you can see we now have a working D10 backbone which is still alpha but it works and we have a second UI as well as a front end UI and as you can see we can already submit suggestions and translations. I said we were porting features as there were but some choices were a bit different for instance we now using the group module and also strings, translations, projects and release and so on and our content entities and also someday on the database for search we might actually rely on an actual indexing and search server. Since Drupal Dev Gant Drupal Dev Days Gant some communications efforts were made at DrupalCon pride last year in front of local user groups during DrupalCon warm up tool always was while wearing these fantastic t-shirts courtesy of the German community. Also some documentation efforts have been made we now have onboarding instructions and roadmap which sounds amazing but it's certainly not so easy. Here at Lille we're working on migration data migration from Drupal 7 to Drupal 10 and when we're done with this in collaboration with our team we'll be able to set up a staging instance so we finally have a demo that was the first phase and during the second phase we'll be able to bring new improvements to this platform. First of all we might expose web services like I said to in order to get statistics like the French community does or but we're already doing this thanks to Dominique on the initiative we could resurrect the localized client module which enables users to submit translations from the local instance which is easier and you can get more quality translations and this module was not in such a good shape but we're going to be able to use it again with the Drupal 10 instance. Also we could implement a tool that the French speaking community does but this time for the whole community for all languages on localized which will certainly be awesome. In the team we have UX designers who joined us and who worked on the interface for instance the filters were apparently not so easy to understand by newcomers so we got the proposal on this aspect and others which have not yet been implemented but I think that's why they certainly will. Yesterday I think with the Drupal association we had both about how we could credit exactly like we do on Drupal.org so you can get your credit the number of strings and translate it directly on your profile on your Drupal.org profile. So we are still in the initial port phase. Much work has been done you can help as well as you will help you will be able to help when we are at the second phase the improvement phase. You can join us on Slack hashtag localize or here during Drupal con leal tomorrow for instance in country broom you may flash this QR code to fantastic roadmap and onboarding instructions or you may even decide to join our weekly meetings. Thank you for listening to my presentation. Thank you Philippe. As you have seen this is really an initiative that you can be involved with if you work with migrations or if you want to participate in the ideation of how the interaction of translation submissions should look like as the Drupal 10 platform that's in development right now a recent development that offers shall help us with is a Git pod instance that's running the Drupal 10 version of this now so you can try it out and contribute there so we have a really easy way for you to get involved try it out and see what needs to be improved and so now for something again completely different so Sasha will now talk to us about not GitLab but the admin UI improvements that are happening in Drupal Core. Well thank you Gabor so today I want to highlight some of the great things which we're currently working on and with we as a community there's so much going on so I can just include some of the things or highlight some of the things we don't have time for everything Drupal has historically a steep learning curve most of you in this room know that that's a hard fact because Drupal is powerful Drupal is heavy but you can build complex products with it so it's normal that you have a hurdle to take to learn Drupal so how we want to improve that is by giving side builders the tools they need to make Drupal less complicated so that's very easy but it's a hard task to fulfill and this really matters as side builders are the ones who build the actual user or content editor experience it's not in our hands so by reducing the time it takes for them to reach that goal is our key so making Drupal the tool of choice for ambitious side builders on the open web that's like a bold, bold, bold claim so many great things currently happening in core, in initiatives in contrary modules that we just have to combine them somehow so in a nutshell making Drupal less complicated cutting down the learning curve and improving the out-of-the-box experience and I think this is the key part because if you install Drupal you don't have the knowledge of all those modules out there so let me some examples of how we're going to improve that so one great example is FieldUI where you get this nice new UI where we improve the page building experience by prioritizing fields make it able to group providing information on reuse so it's an easier, faster and better way for side builders to create or model their content types and then on the other end we have content editors so we want to improve the editorial experience for them improving layout builder, combining the strength of structured content with modern page building tools so creating an intuitive user experience as a whole and part of that is also a new navigation experience how do you access this data how do you access content because historically we have a navigation which is solely focused on site admins and site builders and we want to change that to incorporate content editors as well to do that we also need to modernize the admin UI as a whole because the new navigation might not fit in all those things so a layout really is only something we discussed for many years and we already incorporated something similar in the Chin admin theme and bringing more customization to those things like accent color and dark mode this is really key for newbies you know like to have a place where you can go and search for modules which might fulfill your needs for what you're actually trying to solve so Chris will talk about that a bit later and I mentioned it in the beginning because sometimes we just highlight all the great things which happening around core or initiatives but there is also so much innovation happening in Contrip and I will just highlight a couple of them because we don't have time for everything so the dashboard might make a return you know you might be familiar with the dashboard from Drupal 7 but this time we're aimed for a complete different experience so that means providing a more relevant and personalized experience tailored to the user's needs or on the other hand we have like modules like the same page preview and the module where it increases the content editor confidence in the changes by having like this side-by-side view where you edit content on one side and you have a live preview on the other side right so you're actually seeing what you're doing that's a great great little module there or I might be biased here but the chin admin theme as well right so we're still trying to integrate everything in chin first which is or which might be out of scope for core claro for particularly and we're trying to iterate on those things you know innovate and bringing up ideas which we later than might be able to integrate into core so there was a lot to take here right so I highlighted some of the great things but how do we actually approach them from a design point of view so there's like a process behind it how we validate those things so we highlighted that in our session earlier today Christina myself and we have like three main personas we're looking at which are like the site builder the site administrator and the content editor and they all have completely different needs you know there might be some overlap but they want to try to fulfill like different tasks so we need to ask the right questions to solve their issues and we integrated like a design process and you might all be very familiar with where we do like user research user interviews we're creating prototypes iterating on those prototypes and then we start building the stuff in Contrip because we can move forward way faster in Contrip than we can do in core so yeah you know you might ask yourself do I have a place in this and the answer is yes of course because we need more people to help out with all of this right and this is not like a finished list it's just like a few couple of things I picked here so you can go either to any of these Slack channels you see on the left so they're more topic based you know you might have a strong focus on what you actually would like to help us with they have weekly or bi-weekly meetings which usually are in text form or of course because we're all here at DrupalCon you can join us at the Contribution platform and I would really like to welcome you all go to any of the initiative leads or just show up at the room and we'll find the right place for you thank you thank you Sasha so there's a really a lot of things going on in Drupal core right now in terms of how we can improve the admin UI so it's great to see this overview and next up we picked one of them we could have gone into all of these in a lot more detail and we'll talk about that before some sessions after this keynote that you can get more information of so we picked the admin toolbar because that's I think the furthest ahead of all of these efforts and Mike will talk to us about that hey everybody my name is Mike Herschel I am from Florida in the United States I work for a company called Agilina and I'm here to talk to you about the admin toolbar initiative and I want to introduce the default core Drupal administrative toolbar and I want to specifically highlight a lot of key people that have contributed to this because it is it is a huge huge group effort I want to highlight some companies that have put in some dedicated resources time and money and that would be Lullaba Aquia and Onex Internet and without them we would not be even close to where we are this is where we're not going this is yeah this is Drupal 7 right here but you can I want to draw attention to the admin toolbar and how close it is to Drupal's 8 admin toolbar the look and feel has changed but the overall information architecture has largely stayed the same even as Drupal core has rapidly innovated this has stayed the same and so many people will use Drupal modules such as the admin toolbar module or the coffee module to help them navigate around and just make the overall user experience better a lot of people also go with the gin toolbar module when coupled with Sasha's gin theme kind of makes a very very modern experience gin has been doing an amazing job with prototyping different ideas some of which are good innovative and that has led to this I'm sure you all are just kind of excited to see what this looks like and this is a little video I have of just clicking around using the admin toolbar and you can see it feels very modern it feels I don't know it feels great in my opinion I just get really excited when I look at this type of stuff it also has a collapse mode which gives you a little bit more of a screen real estate and of course you have those flyouts that pop out and then you can kind of navigate around with that so a lot of work has been done on the design of this I want to give some special shoutouts to Christina Chumius Jared Poncha and Jen Ratowski of Lullabot but so I want to emphasize that these have not just been designed and then implemented they have been designed, tested, over and over again the mobile designs look like this they were recently implemented so when you download that you can see how this mobile we want to do usability testing to see if this mobile experience feels as you would expect as part of the overall information architecture plan of this we're redoing the content creation menu which does almost exactly what you think it does new nodes but not just nodes but media entities, taxonomy terms potentially user accounts and we're looking at the overall information architecture of the administrative menu in general so as you know sometimes finding where things are within the admin menu can be very difficult we've sent out surveys and card sorting surveys to show to ask people how they would categorize this and that graph that you saw shows the correlations with that there's a whole bunch of usability testing that has gone on and that is currently going on we've done lots of internal testing we've done some testing at the University of Minnesota in the United States some of the questions that we're asking is what are the main challenges for people who are not familiar with Drupal how can they find their way around the administrative UI of Drupal what about experience users like you and I that actually come to Drupal how do we perceive these new features and how do we find new features if we're adding something new into Drupal how are you made aware of this these are all really good questions and we need your help I'm going to talk a little bit more about how you can help out in just a little bit one of the things that's really really important for this for this whole admin UI initiative is for it to feel good it just doesn't need to look good it doesn't need to be organized good it needs to feel good at your core we want this to feel premium we want these animations to be smooth we want all the jank removed so when you reload the page things don't randomly pop in we just want it to appear and be quick and look smooth and look good we don't want to just meet WCAG standards we're not doing the minimum we want to exceed this we want when someone with assistive technology uses this toolbar we want it to be seamless we want it to be a joy to use we're planning on having dedicated screen reader and accessibility testing to make sure that this happens there have been a lot of lessons that we learned from the Olivero theme the primary menu system and all these lessons are being applied to this it involves all different types of accessibility and usability testing but there's still a lot of work to do right now it looks good but it's not there yet there's lots of known bugs and I'm pretty sure there's some unknown bugs in there so once again we will need your help so what's next we're planning on an alpha release soon when is soon I'm not quite sure you can keep an eye on the drupal.org slash project slash navigation as of last week it's included as an option with an agent admin theme so if you go into your theme settings and you look at the toolbar all the way to the right hand side there's an option to use this and so you can check this out and poke holes in it right away we're talking about testing we're not talking about to validate our ideas we want to improve our ideas so if there's something that we're doing that is not good we want to know about this if there's ideas that we maybe have not thought about hop into the admin UI channel and talk about this user experience testing is happening right here at DrupalCon it's going to happen tomorrow within the contribution room I am personally not going to be here on my way home but look for Christina Chumias and track her down and say I want to help and if you don't know who she is just go to the main mentoring table and we will make sure that you can help us out so how can you help well more developers are always good we need experience front end and back end developers I talked about usability testing we want you to use it on different devices phones, big phones, tablets does it work in Safari? in the admin UI channel in Drupal Slack that's where all of our discussion is with us as I said earlier the current project page is at Drupal.org slash project navigation and we have lots of issues in the issue queue above so go to that look for issues, submit patches or merge requests and stuff do any type of testing that's basically it from now I know you all love visuals so once again we are showing this for you right here and if you have any ooze and oz now is the appropriate time to say that thank you so this is a great initiative to contribute to this week if you have a digital device with you that you can test this out we can go easier than that so next up is a completely different topic again so yet another thing that enables Drupal to work is all of the underlying infrastructure that the Drupal Association is maintaining for us in collaboration with its partners and Fran is here to talk about all of the GitLab CI improvements that have been happening recently hi everyone so a lot has been happening in GitLab CI in the last few weeks months for core contrib space and Drupal.org itself hopefully the next slide is going to show you some of that progress and what we need going forward as many of you now Drupal CI has been the testing ground for core and contrib for many years we started working off with patches we needed to adapt the system and we had a lot of requests so as you can imagine over time there was more custom code creating around it which made the maintenance of it become a bit cumbersome at times with GitLab CI coming in we would be able to say goodbye to the Jenkins servers that we're maintaining and again with it all the custom code that we needed to write GitLab runners it's easy to extend there's plenty of documentation for them we made available GitLab CI to all contrib modules first adding it to your module could not be easier it's literally adding a predefined template through the UI after a few clicks you can copy paste it and that's it you don't need to write a single line of code out of the box you get pipelines running for your project and for your merge requests that will build your project enable it, it will validate the code coding standards all these other checks and of course it will run the test suite of your module once you do that you will see some little icons popping in in your project page next to the main branches and also next to the merge request when you are working on issues hopefully you have seen some of these already and also you can click through it and go and check the pipeline one of our biggest milestones though was moving to Drupal Core from the very beginning we built some amazing templates we started to use all the bells and whistles from GitLab but as you can see in there the performance initially was far from perfect it was even slower than the Drupal CI and this is where the power of the community came in we started to tweak the GitLab templates the GitLab rounded configuration we had some very long conversations and after some changes we managed to get it to run to around 30 minutes time that was twice as fast as Drupal CI but we didn't stop there we continued and we went to 20 minutes then 15 minutes and now we are even talking about sub 10 minute runs applause cool, that screenshot is actually the moment when it was committed to Drupal Core I managed to get it within the million conversations I had that day so it's there, capture once we see those pipelines for Drupal Core it looks something like this we are building all the assets that we need we are running multiple validation on the code and we are running a matrix of PHP and database versions against the match requests as you can see that's a lot of things that need to happen how did we get that fast that's thanks to concurrency so we are leveraging concurrency for Apache we are running multiple jobs in parallel and in order to do that we also needed to adapt the scripts that run the tests on Drupal Core so that we could load balance each of those jobs once the pipeline runs we will get this nice looking report where we can actually click through what went well or what went wrong it will just point us to the file to the line and we will be able to also download artifacts browse through them and the cool thing is that they are very easy to extend one example of this is the code quality which was just added recently we get a new tab with code quality suggestions and we even get inline suggestions in the code, in the MR how cool is that to get almost instant feedback on the code of course we didn't want to stop in there that was all Drupal 10 we also needed to give some love to Drupal 7 so we are working as well on the migration for Drupal 7 to get the FCI the pipeline in here is a lot simpler but we still do some validation steps we are building the environment of course we are running the tests and the big challenge here was to actually work out with the matrix and the database versions as you can see there at the very top we are going as far back as PHP 5.6 so getting all of those to get to green light wasn't easy but we are there so that's amazing the issues there is ready to be committed so you will find it soon as well in Drupal 7 and so many of you might be thinking about the test only part many of us have tried to contribute to core and at some point we've been asked can you upload a test only part with just the test that proved that there is an error and then another one with the fixes well, thanks to the FCI we've been able to fully automate that out of the box we will get a test only job which will get rid of all the non-test files keep the test files run those tests and therefore it will prove that there is an error you don't need to write an additional patch an additional MR everything is done cool that means that over the next few months you are going to be seeing this type of messages where we are just warning that we are going to be deprecating a few things we are for core we are already turning off some of the daily runs in favor of GitLab CI but we are not finished yet there are plenty of follow-ups for improvements and also for bugs MariaDB you can also test different PHP database versions you can get GitLab CI to your concrete module it's just a few clicks away you can use MRs instead of patches and you can hang out in this GitLab channel I don't want to finish without thanking everybody to help that help it was a big, big combined effort from the community and the Troopa Association it involves all the projects that I'm enlisting there just a few of the core issues and all the follow-ups that I could enlist and all the people that were there on the right so thank you all that's right for hyping thank you friend yeah it's amazing bringing down the test runs from almost an hour to less than 10 minutes so as one people said on Slack I don't even have time anymore to get my coffee so that's a problem now um okay so this really enables this really accelerates all the work that doesn't mean happening in core all of the other things happen faster because they get faster feedback on code quality they get faster feedback on test running etc so it enables all of the other things to go even better so next up is yet another entirely different thing about how all of these projects that will hopefully convert to these much faster and better GitLab CI runners soon will get to actual users at the end and Chris Wells is going to talk about that hello everyone I am glad you're here so I wanted to tell you a little bit about well what I wanted to name this piece of the presentation was like project browser the untold story and lessons learned but I realize it's not really an untold story it's really just been told in a lot of disparate areas issue queues zoom meetings a lot of Slack messages a lot so where did we really start from where did we begin actually this was an idea in the issue queue as far back as 2018 and in fact I think Tim Lennon not only opened that issue but currently has it assigned to him so just in case like if I'm duplicating effort here let me let me know but it was I think April of 2021 at Drupal con maybe global maybe North America it was one of those virtual ones in kind of the dark time so we couldn't meet in person but that's when Dries formally announced it as a strategic initiative and then in May he said who this was for and what a project browser should do and it should make it easy for site builders to find and install modules so we met with Dries and we came up with our problem statement or our project brief and focusing on that audience was super important to us at that time and now and we had a really good head start because Matt Grasmick or Grasmash if you ever see that come across in your composer installs as I do had already built a sort of pretty functional prototype using spelt on the front end and writing the PHP code in classes that was needed on the back end as a result of that we were able to step back and really look at the problem holistically say if we're going to build a project browser what are all of the components that need to happen in order to do that and Lowry had said to me a couple of months ago we're very good at building the thing but we're not always very good at solving the problem so what we did to make sure that we had our audience in mind is we split into two groups and there was one team who was really going to be responsible for building the thing and that's sort of the side of our initiative that I had up is I kind of keep my eye on the code but the site builder subcommittee spearheaded by Leslie Glenn those are the folks who represent our target audience and who are constantly thinking about the ability of it they use this Japanese term Shoshin, which I practice Aikido so I know a little bit about is beginner's mind if I'm new to Drupal what am I going to experience what is my experience going to be like and so the first thing that they kind of noticed was we hear this in computer science a lot garbage in, garbage out so not to say anything particular commentary but the data on Drupal.org that we need to source this from not necessarily consistent but not necessarily geared towards having a project browser so we took a look at our designs that were built for our project browser hat tipped to Jillian Chuka and her team for these designs and we identified our three main touch points which are really icons quick descriptions and the categorization of Drupal modules and we attacked those three things first and we looked at we took a lot of community input we did a lot of surveys and we decided to come up with an approach for all three of these areas while addressing them ourselves for the top 100 projects on Drupal.org meanwhile the other team, the developers were hard at work locked in their basements taking the prototype to something that was a lot closer to being feature complete it's wild what Mid Journey gives you if you say in the style of Renan Stimpy by the way that's a really good prompt if you're interested so we learned a lot of lessons through this process and I think most of our lessons were really about contribution what is it like to contribute to Drupal and we found that many of us are experts in the content the content is not the problem the problem is the process and the procedure and getting people to actually believe that they are empowered to make the kinds of changes that they need to make in Drupal so we solved a lot of that by getting rid of the content issue altogether and allowing people to work on Drupal with tons and tons of no code contributions and I'll say I struggle with this and I'm the initiative lead what gives me the right to re-categorize Drupal's projects and redo a taxonomy and another term that I had heard it was really pretty funny back in I think in DrupalCon Portland was this idea of drive by contributors people who sort of drive by and say I want to help I really want to help and we decided to look at this not as a problem but as an opportunity so we were able to take issues and get them down to so narrow of a scope that you might be able to advance four or five of them in a single contribution sprint so get your phones out if you want to help also because the next slide is probably the only one that has actual information on it that you might need so if you do want to help with this initiative especially if you're a maintainer we need you to take our suggestions for a suggested logo a suggested short description suggested categories and get them integrated into your module to get that data right whether you're in the top 100 or not we have people willing to help you write those or do a logo for those and so the road ahead now we're looking at an alpha release getting included into DrupalCore we're very close we have only two issues that are really blocking that and the work is really done on both of those issues they're just waiting on some other piece of the puzzle to come into place and then as we look ahead towards the beta inclusion what we're really trying to do is finalize the UI so if you have any expertise in usability accessibility front-end skills if you want to learn a little spell come on by and we're here to help you so if you see either of these two ugly mugs one of them is me, one of them is Leslie please say hi we are really very friendly and we would love to have you here we have a place for you and you are welcome here thank you Chris I think the project browser is a really great example of an initiative that not only solves the tool to build the tool but also tries to look at the whole problem space that needs to have all of these other things solved for the user to get a satisfying experience so I'm really glad that they take this overarching approach and it also gives you a lot of opportunity to contribute to that initiative as well so for our final talk we'll fly a little bit higher and Suzanne will introduce the promote Drupal initiative thanks Gabor so yeah my name is Suzanne Degacheva I run an agency called Evolving Web and I now play a sales and marketing role although I started off as a Drupal developer and promote Drupal as you heard at the Dries Note were community led initiative to really push Drupal spread the word outside the community and increase adoption and we're really trying to do this at a basic level building brand awareness for a product that has never really had product marketing done for in the past you might be familiar with some of the material we've already created using the existing Drupal brand like this beautiful one pager you can find on Drupal.org there's also slide decks and some other things but what I want to focus on today is talking a little bit more about the groundwork that we've been laying for some more fundamental changes and some bigger marketing efforts so one of those things is shifting Drupal.org and shifting it more towards orienting the content and the experience for evaluators so part of what we've done there is looking at personas for evaluators we've also looked at the analytics of Drupal.org where do new users actually go what content do we need to focus on if we're really focusing on them and in doing that be able to make more effective changes iteratively we've also looked at the governance plan around content if you've done any extensive web projects maybe you've put plans like this together and it's especially important here because we are collaborating with the Drupal Association sometimes we're collaborating with agencies that are working on part of the design or the brand and we need to have a good collaboration there's a group of us that have also been iterating on Drupal's social media presence and our PR having good press releases and external communications and so this isn't something we can take for granted you know Drupal needs a strong presence in these areas as well part of the team has been working on wireframing so if we're looking at those top priority pages on Drupal.org coming up with a better user experience and Shane on my team's actually even translated some of these into mockups so we can start to really see what Drupal.org could feel like now all this effort we've been putting in place but with the formation of the marketing committee we decided to take a step back and really think harder about the Drupal brand and I want to talk through that a bit it's really an opportunity to evolve the brand and help it better capture Drupal and express that to external audiences so Sean Parrot from Acquia has been helping out with this as part of Promote Drupal he's been working on a brand strategy and I want to share on the screen a little taste of the work he's been doing so he's done some interviews with people to try to capture some of the feeling of the brand some of the values and I have some of selected quotes up here we want the brand to be really unapologetic we wanted to capture this joy of building that I think we all get when we use Drupal but we also wanted to make people realize that Drupal is something worth thinking your teeth into worth investing in we wanted to be really true to the spirit of Drupal the fact that we are this community that we believe in the open web but it's also important that it captures the benefit of that for people who don't even know what we mean by community and aren't really sure what open source means to them and I think it's a hard thing to do but I think we can do this and one of what we need to do is to really express the brand in a confident way not be defensive and really speak to these external audiences with all the passion that we have about Drupal so what's next we have these lovely brand attributes that I'm going to show up on the screen in a second but there's a lot of work to do to take these ideas and to translate them into a visual identity a new visual identity that's going to capture people's imagination and we also have work to do to create a brand narrative so that we have a really consistent way of speaking with a Drupal voice that's really going to speak to these external audiences we want to have a tone of messaging that we can all use when we're writing case studies and writing these LinkedIn posts that we've been working on so there's a whole lot of brand work that I hope some of you will be excited to contribute to there's also an effort to reorganize Drupal.org so that this is something we can probably get out the door pretty quickly if we work hard tomorrow Emma from the University of Edinburgh worked on a usability test of a new site map for Drupal.org that we want to get a bit of testing on and push out the door at the same time if you're interested in getting involved we really need help scaling up our efforts so I just like the effort around all this code contribution has been scaled up we need to do the same thing for marketing so if you're a project manager if you're a marketer we'd love to get you involved I want to thank everyone who's been involved so far these are just a few of the faces that you'll see in the promote Drupal team there's been like I said a lot of effort behind the scenes things we've been working on that you haven't seen the light of day yet so thank you everyone for working hard on those types of initiatives and in terms of how you can help if you just have five minutes so that means right now again get out your phone and go to this URL we need help with this usability test it's to test the new navigation it's a very easy tree test that you can go through pretty quickly so we'd love to get your help with that and if you are engaged on LinkedIn who here has LinkedIn accounts pretty much everyone I've talked to at the conference so please follow the Drupal LinkedIn page engage with the content there and really consider like posting to it tagging Drupal getting engaged so that people can see the energy behind the project we'd love to for this to keep going so a few things you can do you can come to the contribution day tomorrow we have a buff at 4.15 today in room 2.2 and we'd love to have you contribute in any way so please come talk to me if you're a non-coder this is the top way you can contribute to Drupal right now thank you thank you Suzanne so this is our time for questions and while I get the backup iPad that did not log me out from the back I would like to ask my question is if one of you would like to recite a mistake or something that you did wrong that you learned a lot from throughout this process that you've been working on your initiative own your mistakes yes pick up your mic one mistake we made early on was just to have kind of a lot of meetings to discuss marketing because people love talking about marketing and not to organize our initiative into smaller groups and get project managers involved in organizing the work and having a better onboarding process for new contributors yeah yeah for me one of the things was actually not going into the cave and try to solve the problem myself I knew that the program was there I tried I tried couldn't work so for me the realization moment was to reach out to the community I mean as many of you were on the GitLab channel I was kind of writing every day asking for help for many small things because we're a community we all have different knowledge and that was amazing and encouraging we got so far so quick thanks to people's help people's comments people's suggestions a random suggestion on one was helping three other tickets I remember one coming from Wim for example why don't you try this let's try it and we got a 50% increase just out of doing that and we wouldn't have been able to progress so quickly without the help of the community reaching out and people willing to help as well an example I have is I was working on conflict validation things and I was really convinced that this was the one way to make it work I went all the way in I made a full proof of concept that worked and then Fabian Bircher maintainer of conflict exploited other things and awesome reviewer was telling me like but why are you doing it this other way and I'm like no that can't work and after a lot of back and forth I was like damn you're right I wish I had known this and understood this weeks ago would have saved me a lot of time so I went too far in a proof of concept direction didn't get enough feedback incorporated it's early enough but it's better now so when we were starting to work on the new toolbar it's at Drupal.org slash project navigation every little issue or every little change was managed individually through like Drupal.org issues because that's how you would do it but our goal it was to innovate very very rapidly and test very rapidly so we quickly kind of just made everybody gainers and said like we're not we're not concerned with cold quality at this point we just want to see something so we can put it in front of people so we encourage people to commit your own code commit directly to the main branch do this just keep moving keep momentum and and make things happen and that's been a big effect on how rapidly we could innovate for your exits usually you have the common UX pitfalls when you don't have enough participation or you don't have a well-defined process that you just go back to assumptions so I think back in the past we stumbled across multiple initiatives we have like over stuff we just made assumptions and then we moved on with it because of can be time or effort whatever and we really want to opt that with the recent changes we did one huge part is also for example that Christina had half an ear paid contribution to work on these things because for example I work always in my leisure time because I don't have company time to work on those things as an example so I think for designers it's a bit harder to participate in some of the initiatives and we need a way to solve that and by creating like the user research validating things, building prototypes getting it out there for you all to test it out and collecting this feedback and then iterate over it to make it better is the way forward and we sometimes lack that in the past I would say thank you so multiple people are asking that what's going to happen to Drupal.org for developers is it going to be like a promotional site so how will we retain the feeling of home for developers and at the same time being good for the market and at the same time is there any plans to localize it for multiple languages all good questions I think we face this like many of us of course work on website projects and we often face this where there's a primary audience that we have to orient the website around but there's this existing internal audience that is also really valuable and what I often recommend on these projects is that we have really good way finding for the internal audience in this case the developers that they have the page, the content they need that you can find it but maybe it's not the first thing you see when you come to the site so we are going through actually right now going through a list of content that we're de-emphasizing and making sure that that's still there that there's a path for that content that there's still going to be a way to find content if it's still useful but that maybe it's not in the main navigation maybe it's not highlighted on the home page and so I think that's the kind of thing we can expect and in terms of localization well I think if we can reduce the number of priority landing pages and really say this is the content we really want to focus on for these external audiences that's going to help make localization easier because it will be a smaller set of content that we say this is what really needs to be translated I think it would be amazing to localize a lot of Drupal.org but I also want to be realistic about how much effort that is and I don't think it's something we're going to see like in the next year all right thank you so one question for all of you I think so I don't think that we quite disclosed it but I think three of us here are mostly sort of funded to work on these things in our day jobs and the other people are mostly funded but somehow by their companies are doing it in their free time so we are really a mix of different sources of funding or how we organize these contributions so Jaydeep asks how an individual can balance their billable project and contributing to Drupal in a meaningful way given the person has the right intent to contribute so how would you balance that I've been doing a lot of that you have to have a little bit of buy-in from your company and a lot of it explaining the value to your company you know if your company is using Drupal you want Drupal to be successful not to mention like one of the primary benefits for me doing a lot of Drupal core contribution is just learning a lot of the lessons that I've learned doing things like the Oliveiro menu system have directly contributed to billable projects and things like that it can raise the profile of your company and that's that's a positive thing I know like at different companies I've worked at during the sales process they say well this person who's going to be working on your project has also worked on Drupal core they know what they're talking about there's lots of benefits for the companies but the company also needs needs to make aware of that that all being said I also like contributing to core in projects is a great way to meet people it's a great way to build enthusiasm with Drupal and that can carry you a long way it's also very easy to burn out especially if you're not getting paid to do this so just be aware of that and just watch yourself and that's very important I'm freelance working on my free time or we can consider I don't pay license for Drupal so I owe something to Drupal but in order to be able to be better organized and to structure the team better so that everybody can know what he or she has to do and we can be more efficient I think contributing really in my experience is a journey where you're taking little baby steps, little incremental steps towards you know sitting up here and suddenly finding yourself in an initiative lead still wild but where it starts I liked from Wim's presentation where he talked about low hanging fruit and that first baby step for us was always a client is reporting a bug okay well let's go find the source of the bug and fix it okay well we're gonna fix it let's go ahead and send that upstream we found an actual bug in a contrib project and that gets you started and it starts to get you to understand how the process works which like I said is really so much of the battle how does this work how does this community handle this you know and new feature requests bugs and new feature requests oh your client wants this well your client's probably gonna pay you for that feature and if you send it upstream that's wonderful news for everyone so always thinking about you know if I wrote this in a slightly different way could I send it upstream you know you get there and it's very incremental so just if you're taking a step in the right direction you'll get there alright so this is all the time we had for questions but all of these nice people will be around after and of course tomorrow so if you are coming tomorrow there's three options that you have on the contribution they would really love to see you here so first of all there's the first time contributor workshop which allows you to get to know the tools that we use to contribute to Drupal so all of the tools that are used to make all of these things happen and second of all there's the mentored contribution where a lot of people will be there to mentor you and help you pick issues and help you go through the process of contributing to specific issues and go through your hurdles and there's finally the general contribution room topic tables for all of these initiatives and a lot more initiatives that we didn't have time for because these are really high variety of initiatives but there's a lot more that you can contribute to tomorrow as well and you can also graduate through these three teams so if you are a first timer you can go into the workshop learn the tools and get hands on help from mentors and then join one of these teams or pick one of these groups to start with if you know the tools or already know which topics you would like to work on and tomorrow it's all going to be on the fourth floor where contribution has been all week all the rooms will be there so see you there tomorrow and throughout the rest of the conference thank you