 Welcome to State of the Word, Nashville, Tennessee, at World Camp United States 2018. There's been a lot that's been going on, so I'd actually like to allow WordPress a chance to reintroduce itself. It is the reason we're here. WordPress isn't a physical thing, it's not a set of code, it's kind of an idea. It's backed by the full faith and credit of every person and company that depends on it. It only exists in the space between our heads and our minds. It has a constitution, it's built on the four freedoms, the freedom to run the program for any purpose, freedom to study how the program works and change it, to redistribute it and to share your changed versions. This is like our Bill of Rights, it's the fundamental things that's included with every single copy of WordPress and every single plugin and theme that you get from it, certainly the ones you get from WordPress.org. This freedom is not just theoretical, it's practical. The data in WordPress is totally portable, you can run it just about anywhere, from Amazon Web Services to Raspberry Pi, and as we like to say, it is both free and priceless at the same time. Another beautiful thing about WordPress is its scalability, and I don't mean this purely in the sort of technical sense that it can run a small site to something that runs hundreds of millions of pages per day, but you can keep WordPress with you your entire life, and it will grow with you, and you can grow with it. It's one of the few things on the internet and in technology that you can be sure that what you put into it, you'll be able to either use it or get out a decade later, and we've been doing this now for 15 years. And who got to make it to the sponsor section today? See some of the booths, get some cool t-shirts, some cool socks, you really don't even need a pack for WordCamp, you can just come with that day's clothes and you can kind of fill up the rest once you get here. WordPress is supported by a really robust commercial ecosystem, one that I estimate represented by the companies in that sponsor hall and others to be over $10 billion per year. So we add all this up together, and we're united by the common mission, which we say is democratizing publishing. Now what does that mean? I know Morton talked a little bit about this earlier. To us, democratize means that everyone can use it, regardless of the language they speak, the device used, physical ability, income or economic ability, location, and finally technical proficiency. You add all this up and you look at the last 15 years of work, it combines to about a 32.5% market share, which come along almost to a third. And like I said a few years ago, we're building a web operating system. It's an operating system for the open independent web and a platform that others can truly build on. It's also why we're all here. And if you are watching this on the live stream or later on a video or you're here in this room, we'll put some more chairs in next time. Sorry. You're in verified air compared to the vast majority of WordPress users that will never watch a video like this, that will never come to a WordCamp. And the primary experience of it is just the software. And as you may have noticed, as we were filing in, we had some inspirational quotes on loop, might have been something you recognized in your own experience or someone you've helped. As far as WordPress has come, I think it's good to remind ourselves that we have maybe even further to go, that we do have a lot of problems. A lot of, there's been a lot of questions this year about why we're doing certain things, like why we're working on Gutenberg. And I think it's good to return always to users to find that. So we're going to go through something that is super awkward. And this is watching user test videos. Who's ever done this before? For those of you who didn't raise your hands, please prepare yourself. Like something like this needs to be easy to use. And I wouldn't say any of this is easy to use. This is frustrating to use. This feels like writing a blog back in 2005. Feels like writing a blog back in 2005. Next up. I have two images side by side. Why can't I do that? I would, yeah, I'm thinking that I want to start here and then we'll put the cursor here and go back. But I'm not able to do so. So. It gets worse. Instead, I'm just going to see what other options I have. Let's see, so. Don't click that. If I do an online, I'm going to, now they're going to go right underneath each other. Add two images side by side. Why can't I do that? Image on the left now. Some text on the right. So I guess online, right, hello. It's not exactly to the right of it. It is, okay. I didn't do that. I was just clicking enter. It's not directly to the right of it, but that's about as best as that's going to go. And then a paragraph below it. So, it's hard to get the actual thing. So we need to go back there. This is very finicky. This does not work. Just move this image up. Why? Why are you not moving? There's more. I'm not seeing an option. So when I go to the add media page, there's no video available for me to add. Video. How would I add a caption? No clue. This is getting pretty painful. How do I add a caption? I have no clue. I want to not subject any of us to any more of those. But that kind of was painful, right? I've likened it before to, like, when you're watching a horror movie and you're like, no, don't go in that room. You see, folks, just trying to do nothing, by the way, that was just described there. I think a reasonable portion of it would say it should be that difficult, right? Why should it be that hard to have an image with some text next to it? We've all seen that on web pages hundreds, not thousands of times. So when you start to try to lay things out, particularly as you might have guessed those were all tests with WordPress 4.9, it can be very, very difficult. There's also other things. This is a quote from a review that says, if you've ever tried to copy text from Microsoft Word and then paste it into a poster page with WordPress, then you know it never looks right when you publish it to your blog. Suffice it to say, Word and WordPress are not very compatible. I like that little closer there. Suffice it to say. Well, suffice it to say, this status quo is not good enough and this has been our editor experience for over a decade now. And for many of us, we've gone used to it or learned to work around. For me, one of the big learning moments was when I realized just how often I was clicking over to CodeView from the visual view in the WYSIWYG. So I enjoyed composing things in the visual view. But sometimes I'd be trying to put text inside or outside of a link or put an image at a certain point in a paragraph and it just wasn't going right. And I'd be like, I wouldn't even think of it actually because I'm fluent in HTML and CSS. And we made the CodeView switcher so easy to get to. So I started writing a post at a certain time. I started to just count that and then, of course, I'm writing a post, a simple post, something that shouldn't be difficult. I would sometimes do that five, ten times. And I bet if we looked around this room to the most elite folks in the WordPress world, we probably have started to take that for granted. So the concept that we think can fix this is blocks. So what are blocks? Blocks are predictable, tactile. That you can kind of zoom into when you go to a block. So the problem with WordPress and many other CMS's approach in the past with what we were calling WYSIWYG is we tried to hide everything. Gutenberg takes that HTML structure that's behind the page and makes it more explicit and then simplifies it into the mental model of blocks which is something that is both more apparent to people and we can reuse across the entire interface. Regardless of how powerful like a block is, for example, e-commerce one or video one or some of the ones I'll show you in a little bit, you can interact with them in the same way. They have a consistent interface for adding, deleting and moving them around and laying them out. Let me show you some videos that are a little bit more fun which is let's build a quick little site with Gutenberg. As Babo Valdez, who the release was named for, an amazing Cuban musician, also the father of Tutro Valdez, one of my other favorite pianists. We're coloring the image. I'm going to text next to an image. That was possible. Adding a YouTube. Found one right there. Make it a little bigger. Let's put a little gallery just to fill it out. And voila. And what we saw looked just like what you can now see on the site. Whew! Oh, thank you. Copy and pasting has also been improved. So, this is a Google document. Pretty complex. Got some layout, got some images, got some different things. About to control A to select all. We can paste right there. Look, exactly what we saw works just fine. This works for Google Docs. It works for Quip. It works for Office 365. It even works for Microsoft Word. So word and WordPress suffice it to say can now work together. We also had some cool developer features that we're curious to see how people are going to take advantage of. So this is actually exporting a block. So you can take any reusable block and it'll give you a little chunk of JSON. You can then go, take that chunk of JSON. This is a pretty meaty one. And upload that into, we can import from JSON. Creates a reusable block. And then you can use that to start a page. Or post or anything. Building on a common pattern that we've seen in WordPress page builders. Ta-da. That's everything we just saw. So this is what we've been calling Gutenberg. It is the bulk of what we've been working on in the past a few years. And it's been going fairly well. We put out Gutenberg as a plugin. It started first actually, if people might not remember, but the first few months, it was actually just purely in JavaScript, which is part of the reason it's been so embeddable and really easily reused by other projects. We turned it into a plugin, kind of somewhere last year. Somewhere this year, we started promoting a lot more. And prior to the 5.0 release, got it to 1.2 million active installs and a run rate of about 40,000, just under 40,000 posts per day. It's a huge amount of activity. Over 8,000 commits from over 340 unique contributors. And we've also been talking about it everywhere we can. At WordCamps, we've had 277 WordCamp talks on it, 555 meetup events, and over 1,000 blog posts done across the various WordPress related things talking about Gutenberg. So Gutenberg was out as a plugin, and the reason for doing that was both to get it more widely tested and to allow the ecosystem to start to build around it. We've seen some great results there so far from themes. So we've got over 100 Gutenberg themes that we've been working on for a long time. We have a new Gutenberg block tag that is currently live for plugins and will be live for themes very soon. We're launching with that the 2019 theme, which, as you can see, has both a beautiful front-end. That matches exactly what you see in the WP admin. So 2019 was our idea to show off what a sort of Gutenberg native theme can do, and it's not even what's going to be able to come. Here is the Indigo Mill and showing both the site and some of the blocks that it's using. There's paragraph block, button block, image blocks, media and text. A really cool one called Lumina Solar that was actually using some more custom blocks, but again, this is a site that if you were to tell someone to do in a WYSIWYG of WordPress before, only using a WYSIWYG, not using a special theme, not using special templates, anything else, would have been basically possible. If you might recall a few years ago, I exhorted everyone to learn JavaScript deeply. How's that been going? Who feels like they've gotten JavaScript deeply down pat? We've got at least a dozen people. All right. Phase two will be easy. It is a challenging language. So I'm going to actually say something a lot easier as homework from this one, which is to learn blocks deeply. This is actually pretty fun. So I'm going to go ahead and talk a little bit about this one. I'm going to go ahead and talk a little bit about this one. XWP made a Jenga set that corresponds to Gutenberg blocks, which I thought was some of the coolest swag I've seen this year. So good job, XWP. But as I said, the blocks are the new fundamental building blocks, the DNA. They're the sort of musical notes and basic chords. These are what you can create almost anything you can imagine from. So far with blocks, we have about 70 native blocks, over 100 third-party blocks, over a thousand different layer configuration and different blocks related to that. Here are some blocks in the wild. So built into Gutenberg, and now in your new block editor, and we're pressed 5.0, there's a selector that lets you kind of search, find things, go for it. Now we're going to go ahead and talk a little bit about this one. We have a block that allows you to embed UST SEO, now being able to give you per block readability analysis. We have blocks like this one, 360 image by Kevin Bazeera. It allows you to embed VR, 360 images, so the sort of marrying of Gutenberg and VR is finally happening a little bit. Google did their amp block, in front row, shows you can kind of bring in images and gifis and things. eCommerce has been early adopters of blocks, so this is an equid store. By the way, I love that preview. It embeds the entire store right there, you can click through it from that one block. For moocommerce there's a products block that lets you choose what you're showing, so this is choosing the music category. It shows it very in line right as you're editing the video. It looks great on the front ends right there. Then big commerce, new entrance to WordPress, and also new sponsors, so thank you. Shows, you can add products, remove products, show what's there, and then on the front end it looks fantastic. We've got profile blocks, we've got recipe blocks. Yeah, someone likes to cook. We've got tarot card blocks. I think you can use this one. This was a block written with only about, I think it was 137 lines of code by Dennis Snell, just kind of showing off using the new React JavaScript framework that you can create this really cool little sketch thing. We've got blocks within blocks within blocks, so one cool one to check out is a jetpack contact form block. If you check it out, it's actually just an example. It provides each of the sub-blocks both as the functionality, full blocks, but also the accessibility, so all the work we did for accessibility around aria labels, keyboard navigation everything is inherited by all the sub-blocks. Some fun ones longtime WordPress community member has made some fun ones including a guide post. This is kind of like an automatic table of contents, so as you add a little bit of content to it, you can write the wordpress. Five people got that reference. So make it ghost writer, publish it, and then on the front end, see, it's coming in. See, that wasn't too scary. I also really like his spoiler alert block, so that says out. So you ever write about a movie? Everyone lives. Make it a spoiler alert. It's also styled a little better, so we can do it. Large fonts, maybe a different background color, publish it, and now on the front ends, click to reveal. Ta-da! Movie reviews and spoiler alerts around the web will now be safe. We've also seen the design aspects of Gutenberg started to be really taken advantage of. This is one of my other favorite ones I've seen so far. It's called the Kaxton shape divider block from 2014. So as you can see, what they're doing is sort of choosing different kind of shapes that can go in between the blocks, matching the colors of the blocks that came before and after it. So I think we got some waves in there. I think we're also going to show a cloud one, which I really like, because sometimes I get asked whether WordPress runs in the cloud. I love that preview animation. Go watch it all day. I think it addresses one of my key worries when we started creating blocks was that everything people were creating with them looked, well, rather blocky, so bringing the different shapes I think really helps. There are block collections being created everywhere you can expect, and these are plugins that include many, many different blocks. And there's even third-party libraries, so places you can go online. This is editorblockswp.com has a huge library, and it's called .org, which is also the same folks who have already ported Gutenberg to Drupal and are launching sites for clients live with Gutenberg and Drupal combined. Amad Awais, I hope I haven't pronounced that right, created an amazing framework called the Gutenblock Toolkit that is actually responsible and behind it's kind of been used to create the vast majority of all the content, so it's kind of amazing. So let's do a quick round of applause for Amad for creating that. It's very impressive. There's been a few others, like the block lab, the lazy blocks, which allow you to create blocks right from within WP admin, so it's kind of a visual builder for blocks, and on amazing sites like CSS Tricks, there are now Gutenberg and tutorials for blocks. So that's where we've been. Next bit, I'd like to invite on, is Ginny nearby? We've got this is a very real support message that came in, actually on WordPress.com, because as WordPress.com was rolling out there were different states you could be in where you'd get some Gutenberg or some not Gutenberg, and you're going to read, it's actually in French, and you're going to read the French? I'll read the English. You do the English? I'll do the English. You've got a mic already. Ready to go? Yes. What does that mean? I thought you were going to tell us. There's no notes. Oh dear. This job is more than I thought it was going to be. I cannot make my page, it's too difficult. And then it goes on to say, je veux avoir un éditeur simple éditeur, je veux un éditeur simple éditeur pour pouvoir construire mon page. And then the support response was, oh, there's one more. Do you remember what it looked like? Was it this with the plus signs that you could click to add content? Initially, the support person thought they were asking to go back to the old wizzy wig, because it's been so much in the community saying how the older one was simpler. Did it have the plus content, like blocks of content, and the response was like, yeah. Despite word camp Paris, I did not quite get my fringe down. This was so cool that actually this person new to WordPress was saying that this thing, which in some ways is much, much more difficult and has a lot more complexity, more buttons to click and things to do, was actually simpler than the wizzy wig that it replaced for what they were trying to accomplish. This is exactly what we're trying to do with this whole two years of work was make it so it was both easier for new people, like this French person and more powerful for developers, which we just demonstrated. Again, thank you very much, Jane. One of the other parts of democratization was that it's regardless of device used. These are our current stats that show desktop being a bit more than mobile, but mobile is growing faster than almost everything else out there and it will be where everything is in the future. Everything that's in 5.0 in Gutenberg is completely responsive. As you can see, it works at every single size on the web version of it and we test on iPads and Android tablets and phones and everything and we're also been investing into our mobile apps. This is a more invisible part of WordPress but I think one of our most important long-term investments. In the past month, there have been over 1.3 million posts and over 1 million photos and videos uploaded. I'm also very excited to announce that the mobile apps are going to be getting Gutenberg in February 2019. This is everything that you just saw with this. Some of what you just saw will be available on mobile apps. You'll be able to navigate and manipulate blocks in the native apps just like you could on the web. This also means that just like Gutenberg is open source and has been adapted already, there will be fully open source implementations of parsing and manipulating Gutenberg blocks available for iOS and Android with beautiful open source code and available to even be embedded in other apps which I think is pretty darn cool. So, to review WordPress exists to increase access to publishing. We had a fundamental core problem that I hope I demonstrated to you, that many parts of it that we might take for granted are too difficult to use. We started the Gutenberg project in phase one, I think makes a strong progress into addressing them. We've created this new fundamental building block, the blocks I just showed you which are a mental model you can use right now for editing posts and pages, but really across all we want to apply it across all of WordPress and we're going to be bringing all this to devices of the future. So I think it's a good point to say thank you and particularly highlight the work of Matias who couldn't be here, Yoan and Tammy Lister. Tammy, are you here? Could you please stand up since you're representing the entire team? This is a big round of applause. Congratulations. How does that feel to see all that stuff? I know, it's been a long road to here. I think 46, 47 major releases in iterations of Gutenberg in the wild. So what's coming next? This is not a finish line, this is a starting line for the next generation of WordPress. So we've been talking a bit about Phase 2 and I'd like to re-explain some of the things that we have in mind for Phase 2 since we're going to start working on it tomorrow at contributor day. So the next challenge of WordPress is now that we've made kind of the stuff inside the box easier, you still have these other things on your page. So if you were to look at an average website, this is your site. It's inside the post content field, there's one way to think about it. Phase 2 is the rest of it. I'm going to show you a scary part of WordPress you might now have looked at in a while. Remember this screen? It's still there. This is widgets.php a little bit old school. This is a widgets plus Gutenberg could look like. The idea that you can bring every single block and actually manage your sidebar content with Gutenberg blocks. Anything you can put in your post and page you can now put inside bars. Because they're fully responsive, the interface adapts and the block should fully adapt. This is what that could look like in the customizer. You can have blocks and contents. We've converted widgets and elements in the blocks. We will convert widgets and elements in the blocks. This will now, we will eliminate one additional thing that people when learning WordPress have to figure it out . The next thing we'll show next year is someone saying we won't need to do it because it will be done by next year. People are starting to get support requests and say, hey, why can't I put this widget into my post? Why can't I put these cool blocks in my post, into my widget areas? The other nice thing about bringing along widgets is it brings along really the past decade of WordPress themes that all already support widget content areas. This, we're going to need a little bit of experimentation, but you could definitely imagine a way of editing menus in line, or that we could create a different interface where there's sort of a restricted number of blocks that you could then arrange into a different menu, and perhaps even preview live on the front as you're doing so. Basically, a simple way to imagine this, and actually one of the full projects that will be going for 5.1, is taking everything that you can create. We're also going to try to rename it because menus is confusing for restaurants. They're like, oh, yeah. How many menus do I need? Lunch, dinner, what else? We're going to bring that all over. So phase one is done. We've got the fundamental building blocks for writing and editing. Phase two is thinking outside of post content. The focus of phase two is really about how to upgrade themes, widgets, and menus. And if you want to test this out before the new versions of WordPress come out, we're going to be re-experimenting with all this in the Gutenberg plugin, just like we did during phase one. So if you have upgraded to 5.0 and Gutenberg was deactivated for you, consider reactivating that plugin, and you'll get the latest and greatest of what's going to happen. So I have publicly promised that I am going to reveal what I think phases three and phases four could be right here in front of you all today. Any guesses? Just out of curiosity. What's that? Emoji? That's all phases. So we've been looking a lot again at I think if you ever, never know if you ever, never know where to go with software. It's always great to go back to users and listen to what they're doing, listen to what they're struggling with, and also to look in the ecosystem. What are people installing plugins for? What are they sort of working around? One of the areas that I think is really key for that, and a place we can start to explore using the new fundamental building blocks of Gutenberg and the developmental framework that allows is collaboration, multi-user editing, and workflows. Now, I'll be actually 100% honest. One of the reasons the copy and paste from Gutenberg, from Google Docs to Gutenberg is so good is that when I'm writing a post that I'm going to get reviewed and collaborate on with a bunch of people, Google Docs is better for that. But if we can integrate these workflows directly into WordPress, we can integrate with them with user systems, we can integrate them with revisions, and we can allow them to be fully extensible in a way that a SaaS service can do. So that's an idea for Phase 3, and you might notice that this is listed as 2020. I should also clarify that Phase 1 and Phase 2, Phases 1 and 2, that makes more sense, are not done. Everyone is not leaving the editor and moving away from the things inside of post content. There's a lot more work to do there. In fact, the next sort of minor update to WordPress, enhancement release, it just, we can now build some more things on top of it. There's already been some demos using things like WebRTC to allow real-time co-editing, you can do per-block locking for collaboration. It's some really exciting stuff that block allow you to do. The other exciting thing about this is as you are able to use blocks to lay out your entire website, bringing that workflow, approval, statuses and revisions to the entirety of your site design is something that right now is really essential. Phase 4 gets a little mercure, but you might remember earlier I said that part of democratizing is doing things regardless of language. So one thing I think it's important for us to address in WordPress is an official way for multilingual sites. This is something that I get asked every single year whenever I do a work camp in Quebec or anything in Europe and I'm very excited that now we can say that it's open. Core is now open. So we basically froze all new features coming into WordPress core to get all the focus and all of the effort on Gutenberg. Now that it's open, I think there's a few different areas that we can sort of subdivide what I just described into you that can be projects with individual leaders and individual teams. These are a few of them. Don't worry about writing all this down. So, and that is where we'll be able to discuss it. The one thing I will highlight though is auto updates, optional auto updates for plugins, themes and major versions of WordPress. I think we're ready for this now. We need a block directory that sort of makes it easy to discover and I would like to have actually inline installation and activation blocks when you're inside of Gutenberg. And finally, we need to do a lot of triage and work. We have started open issues in our core track right now. There have been some requests like moving to a different bug tracker or things like that. I would feel bad about doing that before we cleaned up some of our home first. So that is some of what's coming. Other things that we have in mind, that maybe a few of you have asked about before, but who would like us to raise our minimum version of PHP? Look on the Make Core P2 post. There's an amazing post from Gary now proposing that we move to PHP 5.6 in April 2019. And by this time next year, have PHP 7 be the minimum version for building things on top of WordPress. It's kind of funny. Things like 8,000 commits worth of work. I got a little bit of applause. Changing a minimum version number. People go wild. I would like to say thank you very much. Thank you for the service, version 4.9. I thought it was our longest release of WordPress ever, but actually it came in one day shy version 2.0 to 2.1, the cycle. There were over 173 million downloads of the 4.9 branch. And we got up to 68 .4% of all the known WordPresses in the world running the 4.9 and I would like to thank 4.9. So please join me. It was a hearty release. We also slipped a lot in there. So since we had this kind of longer period where we weren't shipping major versions, we actually put some really cool things like widget updates, enhancements of code editor, everyone's favorite, the months of GDPR work, and a very successful try Gutenberg call out, which was part of what led to Gutenberg being so widely adopted prior to the release. It's actually the best tested code we've ever merged into WordPress. The other exciting thing, and I don't know if you notice this, but release WordPress 5.0. This was a release date that was discussed perhaps more than many others that have been in WordPress history. It was a little bit controversial putting it out on the 6th. So we released it on December 6th, which was Thursday a few days ago. It was ready. We put it through the testings. We were a bit worried about doing it before work camp, so there was some very good discussion about should we do it after this event. But like I said, the vast majority of the WordPress world actually isn't here. And we collectively some of their needs outweigh the needs of us here in this room. But I was also kind of curious because we had a number of plugins that were sort of telling people to hold off on upgrading to WordPress 5.0 . So we had a kind of nice A-B test in that version 4.7 of WordPress was actually released on an identical December 6th in 2016. And so looking on the second day after the release, we had about 2.2 million installs of WordPress 4.7. For WordPress 5.0, we already have 2.3 million installs. This is as of day two. This is continuing to grow. So we're going to go back to our future version of Gutenberg for the holiday season, which is totally fine. They can delay their release. But we're seeing that the kind of early adoption numbers are very similar. It's also worth noting that because it came out on a Thursday, many of the hosts have not started their auto updates because many managed WordPress hosts will actually update your WordPress for you. You don't have to click a button or do anything like that. You can see that the support loads and the feedbacks and the support forms and everything have been pretty smooth. I was even very excited that you shared in the core editor channel the other day that the support loads they see for people upgrading to 5.0 are about the same as what they've seen before. 5.0 also has an interesting effect on the Gutenberg plugin. Because 5.0 deactivates Gutenberg and it's basically 2,000 of the testers of the Gutenberg plugin deactivated. Of course, part of the making this big a change and part of what we started promoting over the summer in addition to Gutenberg was a classic editor plugin because we want people to be able to install something, a plugin we created actually called the Classic Editor, and we've committed to supporting to the end of 2021, so a few years. They could install that and add a version number, perhaps some other ancillary benefits that have gone into WordPress 5.0. So we were hoping to remove the fear that people had. It's also probably a good way to track people opting out. We promote the Classic Editor and post-upgrade screen for WordPress 5.0, so pretty prominently for anyone who prefers the old editor or uses integration or a plugin or assistive technology or anything the Classic Editor go up by 124,000 installs. So, that was 2018, and yeah, all that happens. Thank you. I would drop the mic, but it's on a thing. There's a saying I love, like either you win or you learn. We also learned a lot in 2018 and since the last day to the world. I wanted to highlight a few lessons that I'm personally taken away from this entire cycle. I think that we need the various teams across WordPress working together better. I don't think it makes sense to have entirely separate meetings and everything for PHP and accessibility and privacy and all these different things. This should be a part of every single feature and everything that we develop from the very beginning. So whatever core is, those elements should be integrated from day one. I think that we need to continue to work together as perhaps demonstrated by the show of hands a little bit earlier. People's ability to participate in this new generation of WordPress is limited by JavaScript knowledge. I feel that is one of our biggest gating factors. I think that we need to continue to do every single, probably even move to where we have more JavaScript talks at work camps than PHP talks that are written about WordPress 5.0 and above. I think should teach people the basics of JavaScript so they can learn the syntax and learn that is not that scary. And start to promote more tools, amazing tools like our meds that actually show how easy it is to create blocks. We learned the tough way the importance of triage and code freezes. As you might have noticed, we missed the date originally scheduled date for WordPress 5.0 and that was trying to fix an edge case, a small bug, and that merged and caused a regression. There were some people updated to one of the betas that actually got a white screen on the editor from a JavaScript error, really bad experience. We fixed it within hours, but it really shook people's trust in the 5.0 release process and that's why we had to delay it for a few weeks. We did not rush it though, as I pointed out on one of the previous releases, which was exactly two weeks, which is exactly the average of the previous few releases distance from release candidate to release date, but another mistake that I'll take extra personal responsibility for was we were scared to announce a new release date after we missed our previous one and that created a lot of sort of fear and uncertainty where I was trying to give symbols, signs, that means WordPress is coming out really, really soon, but we never talked about the average date between release candidate and a normal release until we announced our new date, which was a few days before the 6th, so I completely understand where the date seemed to come out of the blue and was very stressful for people. Some of the more positive things we learned were that the betas were more tested than any other releases. We've talked about that a lot in the past. Not many people know this, but for betas and release candidates of core WordPress versions, we usually have under 10,000 and usually under 5,000 active sites using them, so having six, 700,000 sites running the Gutenberg plugin was over 100 times improvement in the number of testers that were happening before release. Part of the reason Gutenberg was able to become so much more robust is because it's open source is difficult to develop in public. We had a lot of struggles here. Gutenberg happened entirely in the public eye. You can go back all the way to the beginning, you can see the change sets, you can see the arguments, you can also see the people reviewing versions from a year ago and giving it one stars, which isn't necessarily bad. You can see people essentially using our review in the plugin. It's more expressing what they thought the future WordPress would be. Perhaps we need a different medium or way for people to go to. So that is, I think, just something we have to keep in mind as we move forward. A lot of people who have come up to me so far at this WordCamp have said 5.0 seemed like it was going to be terrible and post-release it's been pretty quiet. Or there seemed to be like this kind of commercial or more acrimonious release processes that we've had in a long time, maybe ever, if you're new to WordPress. Some of the old ones were pretty bad. But I blame Twitter partially. You can blame almost everything on Twitter. Between Twitter and Facebook, we have all their world's problems. But I also think that it was part of the result of some of this development and some of the warts and some of the debates that we've had over the last couple of years. And I think that's the most important thing for all. For us, we have all of this happening in public and it's all archived and linkable and version controlled and everything. So we just have to keep in mind that, well, in addition to trying to treat each other well and have good etiquette and really converse in a productive way for whatever we're doing, we also have to be representative of the basics or fundamentals or first principles of the software. Finally, one exciting thing that didn't really fit, but I just wanted to show you all because I think it's pretty cool, is this year sites using SSL, WordPress sites using SSL actually crossed over the non-SSL sites. I'm very proud that we were one of the earlier supporters and adopters of the Let's Encrypt. We've had a low cost or free SSL certificates and we move people onto them. We've had, I mean, the 20% increase, that's an absolute increase, so that's going from around, like, a 37% to a 57% in one year and it looks like it's continuing. So we are approaching, we are seeing the possibility that when you get the right technology in the hands of people for a low cost, it can actually really change your life. Now, I'm going to briefly go through some of the community stuff because the community is, of course, part of what makes WordPress so exciting. At different WordCamps, we've been growing every year. We've had about 145 WordCamps in 48 countries this year, which is wild. 45,000 tickets sold and one of the things that I think is most exciting is the organizers, which is a 50% year-over-year. 2600 speakers and also an exciting 1100 sponsors. WordCamps are cool, but of course we know meet-ups are bigger. These are typically the monthly get-togethers that WordPress folks will organize and sometimes there's even a few in a given town. We're now up to over 350,000 members of the meet-up group, which is a 50% year-over-year growth. That is wild. We have 87 meet-up groups all around the world. 687, that's a lot of different cities. That's a lot of different neighborhoods of cities. On the foundation side, we were able to do 12 events, which is tripling the amount that we did last year of the due action. So these are where WordPress and other folks get together to support charitable organizations by creating them an amazing WordPress website that is totally free and doesn't lock them into anything. They were as far ranged from McCallan, Texas, which notice doesn't really have like an airport code or anything. Bristol, Stuttgart, Germany, Beirut, Montreal, Port Harcourt. Where is NGA? Nigeria? Oh, wow. That's really cool. We had a number of open source workshops. So these are bringing folks into learning how to contribute to open source, often starting from a more basic technical level. We had these in Ghana, India, St. Lucia, and Columbia. And this year, we're proud to announce that the WordPress Foundation is able to donate and support with grants to Internet Archive, Girl Development, and Black Girls Code. We were very excited to be able to do 30,000 of grants this year. Our ability to continue to do so might be very important. So as I talked about last year, you can donate to the WordPress Foundation, and there's a little straight button and everything for it. Since last year, $3,445 have been donated. That is total for the year. It's not per month, not per day. So let's give a round of applause to the 85 donors. Thank you. We are working on updates that will actually highlight the donors on the website. If you're interested in WordPress and would like to support organizations and events like we just spoke about, please consider going and perhaps becoming an annual recurring donor on wordpressfoundation.org. WordPress.org, by the way, different website, we finally kind of loosened and were able to ship a number of really great improvements, including a completely new about page, a completely new about page, and then, of course, this beautiful slash Gutenberg, which actually allows you to live use the Gutenberg interface right on the landing page. I am very, very proud of all the teams that worked on this. I think, do we actually mention support? Did I go through that? Yeah, we've got the help help launched on support. That's a project three years in the making. There's been a lot of work that's gone into making this happen. As we improve, WordPress.org is where we make the things that we make, and so any improvements we go there, I think, have great effects down the road of both making our work better, but also making it easier for new folks to get involved, because remember, the vast majority will not come to work camps or even ever see this. We haven't done this before, but I'd like to pick a theme song for 2019, a theme that goes through everything. We're going to play it, but we weren't sure about the copyright, so I don't know. Amazing song, a lot of fun. It's actually in the intro, they talk about how it's a little band from Houston, Texas. I'm from Houston, Texas, so I was very happy about that. Thank you, Texas. A lot of what we want and need to do in 2019 is tighten up. We've built this new foundation. We now have the foundation that we can build the next 15 years of business. We've got the JavaScript, we've got the APIs, we've got the development frameworks, we have the user interface frameworks that can scale from the simple to the complex. We've got the themes, we've got the plugins. You notice on the plugins page now, we've actually put Gutenberg-ready plugins above the featured plugins, so we're really going all in on getting everything Gutenberg enabled, capitalizing on the work thus far and starting with all haste . We need to tighten up everything we do. We need better engineering management processes. I talked already about release management. We need to start to really whittle down those 6500 issues. I do understand that open issues are not a reflection of project health, but I don't think it would be bad if we really went through and we're able to triage them all, at least know that each one has been touched on. I think it would be better if it was something that was rather explicit than something inferred by the abandonment or no responses on the ticket. When you get home or if you're listening to this online or whatever, play this song. It's pretty catchy, makes it wiggle and dance a little bit and as you go to contribute and as we build what is coming next, the next 15 years of work. I would like to thank some sponsors. We got key sponsors, Bluehost, Google, WooCommerce and Jetpack for the top sponsors for this WordCamp. I want to thank the organizers. Can we give them a round of applause? I don't know about y'all. This was the smoothest WordCamp U.S. I've ever been to. Great. Music, food, everything. It's partly put together by over 200 sponsors. Thank you very much. Thank you.