 So I'm newer to the community. I've been around WordPress for about two years now. So a lot of you don't know who I am, so I wanted to include an introduction slide. I'm the dad to two nerds in training. These are actually the fourth generation tech nerds in our family. It goes all the way back to my grandpa who worked at IBM from the 50s on. My dad worked at IBM. He's on his 37th year there. I thought I could do something different with my life and here I am. So I've been in open source for almost a decade. I got started in Drupal and yes, we're going to be talking a lot about Drupal and WordPress today. But I got started in Drupal and I'll go into why in a bit, but then transferred over to WordPress as I started creating our product. I'm the founder and CEO of Locker and I'm getting more and more involved in privacy policy and also governance issues. If you were here earlier this morning, you heard me talk about that a little bit as well. So this is an old picture, but I really like it because it defines what a lot of us do on the web. This was the browser wars, right? And so you had Chrome and Firefox and they're like battling it out. And then you have Internet Explorer over there eating paste in the corner, wondering why nobody likes them. I think that a lot of the times when we talk about Drupal and WordPress, we end up having this type of mentality. It's Drupal and WordPress battling it out. I'm not going to say who's eating the paste in the corner. I'll let you fill that gap in yourself. But a lot of the times when I go to a WordPress event and I say I do Drupal, the first thing I get is what's it like over there? What is it over there? What do you guys do? And then I go back to Drupal. I was like, oh, I was just at WordCamp and they're like, what's WordCamp like? It's the exact same reaction and I feel like I'm a double agent or something going back and forth. But a lot of the times I also get the question of which one's better, right? Who's the best? And there is no better. There is no best. And this is a comic that we like to circulate in the Drupal community. I don't know if you can see it too well in the back, but it's the learning curves of the popular CMSs. And this has been around for a while. And so down at the bottom you have ModX, which is just kind of this straight line. You got WordPress and Joomla, which start out low and then kind of come up. And then you got Drupal, which is this hanging cliff with bodies hanging off of it and crucifixes and bulldozer pushing bodies off the top of it. And you look at this, I look at this from a Drupal perspective. And we kind of take this as a badge of honor of like, yeah, I survived the crucifixes and the bulldozer and I'm on my way now. Like I'm a, I'm a lead dev now, right? And then you look at it from a WordPress perspective or an outside the Drupal perspective and you're like, why would I ever go to Drupal if that's what it looks like? Funny enough, this was written during the, or drawn during the Drupal 6, Drupal 7 era, Drupal 8. I would add a couple more crucifixes up there and maybe like a bulldozer or a giant dump truck dumping bodies off the end. We've gotten a lot more complex. And so I'm going to have some real talk today. If you know me and you'll hopefully get to know me better, that's what I do. I don't hold my words too often and both platforms do things really, really well and they have their strengths and we need to be able to look at those. And also we do things less than ideal. And fortunately I've been in both and have had the experience of both so I can see kind of both sides of the coin for each of them. And what we need to do is we need to play to our strengths. I got involved in Drupal because I was starting an app in 2009 as everybody was. And I said I need to go build a website for this app. And until that point I had coded my own websites and done a little bit of HTML and dabbled here and there. And so I went on ThemeMonster. And I apologize if anyone is here from ThemeMonster or watching the stream. I love your product. But I went on ThemeMonster, I bought a theme that I liked and it happened to use this thing called Drupal. So I just happened to fall into Drupal. Probably one of the worst decisions I made at the time because as a brand new developer to the CMS world you pick the hardest thing out there and you didn't understand it. I installed it, sure enough, nothing looked like it I wanted it to. So then I said and this is kind of my mentality in life, I just got to do it myself. And so I went and built my own theme in Drupal and slogged through that and started getting involved there. And that's basically how I got into Drupal. I didn't pick it because I thought it was better. I didn't pick it because of anything. I literally picked it because ThemeMonster had a cool design for it. But as I started getting into WordPress recently within the last couple of years I started seeing more and more of what it does. And I realized that the strengths that I thought that Drupal had were good but they were limited. And I had always heard WordPress is insecure, it's not, it's really secure. It's too easy, it's not, it's actually pretty complex. But I heard all these things from the Drupal community. I started getting into WordPress and I realized, ah, this isn't actually that bad. And if we play to our strengths WordPress has a large focus on design and usability. That's first and foremost, democratizing publishing, right? The idea that anybody can pick up WordPress, install it and start running. The themes out of the box are gorgeous. They're useful, they work. A lot of websites just use that theme and nothing else, right? In Drupal this year we just launched the out of the box initiative, which now when you turn on Drupal and you install it with the out of the box initiative it actually looks like a website. That was a big thing for us in 2018 to finally make Drupal look like a website. Design and usability is at the core of everything you do. You have privacy by design. You have privacy and core. That's huge. And then you have the media management. Again, this should seem like table stakes for most of you sitting here going, yeah, I know, I know. But media management, the ability to do embeds and videos and pictures and have libraries and all that type of stuff from Drupal, that again is just starting to get modernized and just starting to mature in our ecosystem in 2018. And so play to your strengths. You have this capability. One of the things that is not often talked about in Drupal and in a lot of the, I guess, open source world in general, is the economy of open source. It's kind of the thing that people don't want to talk about. We all have to make money off of open source, but how do you do it? WordPress has a really, really robust plug-in and theme economy. There are graveyards among graveyards of companies in Drupal who thought that they could sell a module or sell a theme. It does not work. The community rejects it vehemently. Whereas in WordPress, you embrace it and you build these plug-ins, you sell them. And by doing that, the person who's making the plug-in gets money and in turn makes a better plug-in. It kind of helps that whole ecosystem run. And so I look at this as a strength and something that you and we should all embrace. And then, yes, Gutenberg. I know it's a controversial topic right now and a lot of people have a lot of differing opinions on it. But it is one of those radical changes to how the web will be consumed in the future. And because of that, other projects, including Drupal, are looking at Gutenberg saying, how can we do that? And so you're setting the path. You're building the infrastructure that a lot of the web is going to work on. And Drupal is looking at that and we're saying, wow, that's pretty good. And again, it goes back to design and usability and everything that WordPress has for its strengths. And then for those that are looking to work with Drupal, here's some of the things that I would say. So going back, this is all items that when I talk to people in the Drupal community, we need to do this because we still haven't figured this piece out. Now I'm going to tell you kind of what Drupal does and hopefully nudge you along the way to thinking about maybe this is something that we could do in WordPress. And the number one thing is data architecture. When people ask me, what's the difference between WordPress and Drupal? It's data architecture. Drupal is a really good content modeling system that happens to make websites, in my opinion. It has a really strong data architecture. And because of that, you can create these really complex contents and entities and put them all together and then break them all into pieces and put them all back together in a different format in a different place. And that data architecture lends it to be used in a lot of interesting scenarios in powering apps through headless and all the various things that it can do there. Core APIs, as I was building a WordPress plugin for our service, I had realized that I came to rely on the core APIs that Drupal had and I took them for granted. I didn't realize how good they really were. One of them for me is a form API. In Drupal, you have a form API where you can declare a form, create an array of all the different types of inputs that you want, you send it to Drupal and out pops a form. You don't have to write any HTML, you don't have to write anything. Everything's already built for you. And oh, by the way, by creating that form, you also get a validation handler and a submit handler that are automatically called back to you. To create that ecosystem in WordPress is not very simple unless you start using some of the plugins. And so what I'm talking about here is if core can adapt some of these frameworks, it's not that we're trying to, or in my opinion, that portions of the plugin economy need to be replaced. I think it would actually strengthen some of the plugin economy and themes to have some of these core APIs and some of these core functionalities. Another one is views. And if you're not familiar with Drupal, views is our database querying UI and it allows you to build these complex pages. Again, from the complex data structure, I can say I want a page of all the news articles with this image, the field that is the subtitle and the date and the author. And I want just that. And it will create a page of just that. And every time I add a new article, that page is updated. I don't have to worry about it. That's in core. It's super powerful. It's also what runs our core REST API. And so you can declare here are all the fields that I want the REST API to have and publish it. And then anytime somebody hits that URL, they get a beautiful little JSON to go run a headless app or a mobile app or anything else they want. And again, REST API is now baked into core. If you talk to people about what the future of Drupal is, that's what it is. It's going to be a headless system. So we need to play to our strengths. We need to be able to look at and figure out what are we doing well and how can we learn from each other. Because a lot of our learning comes from inside the community right now. Drupal likes to stay on its own little island. WordPress likes to stay on its own little island. And I think there's a lot that we can kind of cross-pollinate and learn from each other. So let's find ways to share ideas, code, and make all of our projects better. I'm a big fan of open libraries that can be shared in between. And so with that, unfortunately we don't have any time for questions, but I will be at the Happiness Bar later. I'll be grabbing lunch and walking around. So please come find me and I'll tell you all about Drupal and what we really do over there. Thank you.