A panoramic view of the audience at the State of the Word address. Photo credits: @heyadamsilver.
It was an excellent turnout for this year’s WordCamp US. Over 2,000 people gathered at the Music City Center in Nashville, Tennessee to catch this year’s fantastic line-up of speakers. This included TinyMCE’s CEO Andrew Roberts, who delivered a presentation and talked about the lessons learned on commercializing TinyMCE as an open source project. To view the slides from Andrew’s the presentation, click here.
The conference ended a high note with Matt Mullenweg’s State of the Word address. Matias Ventura performed a live demo of Gutenberg, and members of the WP Core team walked through the updates on 4.8 and 4.9. In case you missed the livestream, you can watch Matt’s State of the Word address on WordCamp.tv. We’re pleased to once again bring a full transcript of Matt’s State of the Word address to the global WordPress Community, edited for readability and brevity. We hope you enjoy it.
Dustin: Well, well, here we are. My name is Dustin Meza. I’m the local lead organizer for WordCamp US, 2017 and 2018. How cool is Nashville, pretty cool? I love it. It’s so cool. We got this big boot, I don’t know if you all have seen him on Broadway, there’s like a buy one get two free special, but we could only literally buy one; these bad boys go pretty steep, so we are waiting on those two free ones. I think Matt is going to take us up on it. That’s good.
Raise your hand, how many of you is this your first WordCamp ever? That’s nice. Look at that, excellent. Excellent. Raise your hand if you’re from the Nashville or Tennessee area. Okay, I like it, nice, showing up. Who flew more than six hours, anybody? A lot of them, look at that, almost as many as Nashville. I love it.
Who flew more than 10 hours? Wow, that’s just good. Who flew halfway around the world? Welcome. I am so happy you could join us. That’s awesome.
When we were looking at venues we fell in love with this place, because it has things like a live-size digestive system that you can go through, spacewalks, flight simulators, VR adventures, a three storey jungle gym, and a planetarium where they created a show just for us, just for WordCamp US, yes.
Nobody can say we didn’t tell you, but you have to have your badge if you want to get in; got to have it. Everyone’s going to keep wearing their badge all the way until the party so that you can get in and it’s nice and easy. No guests, everybody has got to have a badge. For real, badges.
Same applies, just like here in this building and any other official WordCamp event. The code of conduct is in session. Please give it a read, if you’re not familiar, but that’s how we expect you to behave tonight. If you have any concerns during the event, please just grab a volunteer or an organizer; the organizers are wearing rainbow lanyards and the volunteers are wearing turquoise shirts.
Speaking of; big thank you to our volunteers, give them a round of applause please, over 200 of them, and a real big thank you to this year’s organizing team; 22 of us, they worked so hard guys. I can’t tell you how many hours they put in. We had three babies born, four people moved, and one person get married all in the time that we planned this WordCamp for you guys.
I told the organizing team, the other night, “We wouldn’t be here without the community, and the community wouldn’t be here without us.” It’s a great relationship, I love it. Give them a round of applause. I also want to say thank you to our record setting 44 sponsors this year; you allowed us to put on an amazing event at an amazing venue and you allowed us to keep everybody’s ticket, once again, just $40, all of this for $40. Sometimes I can’t believe it. Yeah, give it up.
We are back next year, right here in Nashville. Buy your tickets.As soon as we walk out tomorrow, go get your tickets, set your plans, we are going to do it even bigger next time. It’s going to be even better. I’m super excited. There’s nothing more than I love than giving this to the community, and Nashville is a great place to do it. Who wants some swag? Emily? Okay, okay. All right. Well, thank you so much. I’d like to welcome Amanda Giles to the stage.
Amanda: I’m going to stand by the boot. This is a poem I wrote about WordPress.
Now, I like to code and I like to rhyme. Neither is perfect, but I’ve still got time.
Code is poetry, so the saying goes, and in my mind it’s the bomb of credos.
Now, don’t you be thinking of young men with Fritos with nowhere to go,
who can’t touch their toes, because I am a coder of the first degree.
If they gave out belts, midnight black mine would be.
Still my gender is rare, minorities too, reflects of black pepper and in all white guys too.
Times are changing, and the need is great.
Computers are in everything, and more coming. Just wait.
Now, where am I going, how did I get so off track?
It’s poetry, and [inaudible] code, let’s go back.
One’s from the heart, and one’s from the mind.
One fueled by caffeine, the other by wine, though when I’ve had both is when I truly shine.
See, the two aren’t so different, as you might believe.
Both go from point A to point B, though one may weave.
Lines of code have a function, several in fact.
The goal of poetry more subtle, while keeping form intact.
But the best of my code has a grace all its own,
You would see perfect in dense if the lines you were shown.
Now, it’s not just the spacing that fills me with glee,
It’s pure elegance woven with efficiency.
Code is not just a straight line, at least rarely for me
It’s a journey you take while staying bug free
You do it with style and you do it with smarts.
If you’re doing it right, it should rival most arts.
It’s likely a beauty only true geeks can see,
But you’re still listening, so I think you get me.
What I’m trying to say is that code fills a need
For my soul to express itself artistically.
While poetry isn’t always my rap, I can’t turn it on like I do with a tap
Every day I write code of beauty untold
Hopefully by now I’m not yours sold, but I don’t do it for glory, money or fame
For code is poetry and that is my game.
Thank you very much. You guys are the best audience I could ever hope for, for that poem. It is now my great honor and pleasure to get to introduce the man you really came to hear. He really needs no introduction, Mr. Matt Mullenweg.
Matt: That’s beautiful. Thank you. Thank you so much. Wow, wow, wow. Can we get another round of applause for Amanda? That was great so cool, to actually open up with some real life poetry.. They are doing some research, they think that code as poetry actually came from WordPress. They are having trouble finding earlier references to it. We might have originated that one.
Hello everyone? This is the State of the Word. As Amanda said, my name is Matt Mullenweg. I’m available @matt.blog, ma.tt, and photomatt, all major social networks. Before we get started, I do want to do a quick thank you to our sponsors. This year’s top sponsors are bluehost, SiteLock, Jetpack, sporting a new logo, and WooCommerce.
Have you all been having fun in Nashville? You got some hot chicken? That’s … Can’t say bingo yet, barely started. We got the poetry and the hot chicken, but you need at least five to get bingo. There’s a bingo game going on right now apparently, so someone is going to yell it out relatively soon.
I’m really, really excited. Nashville, I’ve been here since Monday or Tuesday, and I’m really impressed with this city. There’s so much soul to it, so much amazing music, barbecue even a Texan can love. I had some not hot chicken before I finally got the right hot chicken, but I’ve been enjoying it quite a bit. Really, number one, the music; it’s just everywhere. At lunch we’ve had great music. Like, has anyone gone out dancing yet, or had some fun out there? Cool.
I’m so excited. We’ve got the dancers over there. I’m so excited that we are going to be able to come back here next year, and I definitely have already been making some list of places I want to return to and some places I haven’t made it to yet that I really want to check out.
Matt thanks the WordCamp organizers
Matt: We should thank the people who brought us here, helped bring us here to Nashville. If you’re a organizer for WordCamp US, could you please stand up really quickly. As you might have seen, there were many cities vying to host WordCamp United States this year. In fact, we had some in the booths earlier, by the way; the sponsor area, and all the booths were packed.
That was a really good … Thank you all for supporting all the people who help make this happen. Nashville had just an amazing application, so thank you all very, very much for bringing it together. This has been a really fun WordCamp. I love the art and the venue, I love the music, I love the food, I’m looking forward to the party. One more round of applause for the organizers. That was really cool.
This is actually the 128th WordCamp we’ve had so far this year, one of our fastest paces ever, across 48 countries. Just under a hair of 40,000 tickets sold, 39 something, something. Who makes this happen? It looked like there were 15 organizers here, so 1,000 total across all the WordCamps that happened this year, so about eight organizers per WordCamp.
Raise your hand if you’ve organized a WordCamp somewhere in the world. That’s a good quarter of the audience. Raise your hand if you’ve spoken at a WordCamp. That’s actually the quarter. The first was maybe 10%. So that lines up. We’ve got 2,300 speakers and over 1,000 unique sponsors that make this all happen, enable it to happen at such an accessible price for everyone.
One of the more exciting things that’s been happening this year, you know WordCamps, that is they happen once a year in a city, they feature local speakers, but I feel like a lot of the community in WordPress comes from these more frequent events, and we’ve had a huge up kit of over 4,300 meetups now happening in 73 countries.
You might have seen that Meetup actually just sold as a company, they sold to WeWork. Usually I get worried when acquisitions like these happen, but I think that WeWork is going to be an excellent partner for Meetup and we hope to continue to work with them in growing it. We are just a hair under 100,000. I was kind of like, “How many meetups can we do before the State of the Word,” and it’s been growing quite a bit
I'm honored to have worked with such an amazing group of organizers. I wasn't expecting to see my face in the State of the Word slides, but thanks to everyone who made #WCUS possible. I ❤️ my volunteers! pic.twitter.com/toxhF8iVXX
— Andrea Lee Bishop (@andrealee_b) December 2, 2017
WordPress meetup attendance increases
Some of you all might have noticed, in version 4.8 of WordPress, we added this new events widget. The idea was it would show you, in addition to just the news, it would show you the events, meetups, and WordCamps happening near you.
As a result of that widget launching, monthly attendance to meetups are up 31%. As you might know, we split out WordCamp and the WordPress Foundation a few years ago, so all of the meetups from WordCamps are now running through this WordCamp subsidiary of the foundation.
We announced last year that we would be taking some of the foundations to support educational endeavors, which I’m going to update you on now. The first being that we wanted to support three organizations; we were hoping to do about a 10 grand donation each. We actually were able to donate $15,000 each to Hack the Hood, Internet Archive, and Black Girls Code. We are very excited about that.
Also, all over the world in Johannesburg, Beirut, Cape Town, and Montreal, we have these do_action events. If you’ve never been to one of these, they are very, very exciting. The idea is that non-profits can come and serve like a weekend hackathon, WordPress volunteers, people volunteering, we’ll help them get a great website or get updated, or anything like that.
We had four that we supported this year. These are one of the coolest things I’ve seen happen around the WordPress community in a while, and I love the name. Such a good kind of geek joke. We are hoping to see more of these coming up.
Donating to The WordPress Foundation
One of the things I’m excited to announce today is that supporting the educational work of The WordPress Foundation is now easier than ever. We have a donate button, which we never really had working well before. What is going on is that now that all the WordCamp stuff is outside of the actual foundation, the foundation needs more diversity of donors for its non-profit status.
We’ve set up where you can do a yearly donation, I think starting at … Was it 30 bucks a year? $10 a year, from $10 a year and the max is $1,000 a year, if you’re a fancy business, or something like that. It is coming up at the end of the year. This is all fully tax deductible and we are going to continue paying taxes in the future; I don’t know.
You can get in your end of year giving, and it’s a yearly thing. We want to develop different folks, or different regular contributions, and basically as you know, the WordPress Foundation has no employees, no executive pay, no anything. So this all goes back out into the community. We are hoping to do more of the grants that we are able to do this year for organizations like the ones I just talked about. Check that out.
WordPress puts bounty on security issues with HackerOne
Another update for next year is, in May of this year we launched HackerOne. HackerOne is a way for, basically a bug bounty system so people can all over the world, who do security research for WordPress, now have a completely organized way they can say, “Hey, I found an issue,” and we can check out that issue, and if it is valid, then provide a bounty.
We had 52 security issues that were resolved this way this year and reported that were valid, from 46 different people, and 39 of them got kind of a real reward, so that they were serious, including someone I just want to highlight, skansing; I’m not sure how to pronounce it, who had nine valid reports.
This has been a really, really great program. It’s allowed us to make WordPress a lot more secure, and as we get better at we doing it we want to roll this out to top plugins and themes as well. As I said before, not all of the plugins and themes, or we would run out of money, but for the top ones.
Having your WordPress be as secure as possible is a big, big priority, and this HackerOne program has been really great. It is … If you ever hear someone say, “Hey, I know a WordPress problem,” or anything like that, point them here because it is where we triage and where we look at them and everything happens.
A new look and feel for WordPress.org homepages across the globe
WordPress.org has also had some pretty cool stuff this year. The one I want to highlight the most is that this time last year, this is what es.wordpress.org looked like, which is a Spanish version of WordPress.org. This doesn’t look too, too bad but if you would scroll down on this page, there was actually several thousand pixels dedicated to editing a wp-config file, talking about when WordPress 2.5 comes out you have to change this and that. S it was a little bit old school; 2.5 was a long, long time ago.
I’m excited to say that we were able to launch a new homepage that we launched for WordPress.org for over 26 different languages. They now have a very stylish cool way to introduce people all over the world to what we are doing with WordPress. We have now over 47,000 plugins, getting a bazillion downloads, or actually a bazillion hundred million downloads.
I talked a bit about language packs last year and how those are going to enable more and more of plugins and themes to be localized the same way that WordPress is. I can now say that we now have over 1,100 themes and 2,000 plugins with a language pack. I’m so glad that’s not like 19,990 or something.
Of the top 10 plugins, all I wanted to see was actually when it was 56 fully translated language packs, but you can see that in these top plugins we are getting really, really good coverage all over the world and the local communities that are doing translation days and everything else have done just a fantastic job making this happen.
WordPress launches Tide
Plugin and theme directories are a really important part of what I want to focus on next year. Related to that, you might have heard a little bit about a new program we’re launching called Tide. Thinking of it like a rising tide lifts all boats, not a way to clean things, although it actually will clean up the plugin and theme directory so it works on multiple levels.
Kudos to whoever … I think XWP came up with that. Was that you, Aston? It was a group event, he’s a very modest guy. What Tide is, is basically a series of automated tests run against every plugin and theme in the directory.
Here’s how to imagine this, some of you might know unit tests or continuous integration; imagine if we were able to run a set of tests against the entire plugin directory basically in real time as things get updated, and now you as consumers there’s a page on the plugin, a tab on the plugin page that allows you to see the status of all those tests.
Some of the tests we might consider really, really important, like saying if this does not work with the minimum version of WordPress’s php compatibility we might actually use a test to say, this plugin will be temporarily delisted and so that it fixes this thing.
Well, basically the idea is to give developers much better tools and information for how to improve and know how their plugins are doing, and then for users, to give them a bit more information on choosing things, but over time of course we hope that every plugin has 100% here.
This is just getting started. Each test that will show you the kind of pass, fail will also have what the results are. It will tell you what lines are being talked about and it will have a link to the test on GitHub so that anyone can update it. There’s a problem with the test, someone could say, “Hey, this has a bug, it caught something it shouldn’t, or submit new test.
— Alex MacArthur (@amacarthur) December 2, 2017
Then of course, we will add a way, because automated testing and code sniffing isn’t 100% perfect, so we will have a way for plugin authors to say, “Hey, now I really did mean this line. I know it looks like this an escape variable being written directly to the theme, but it’s not really,” and so they can leave a comment that will overwrite things and those will be visible in the plugin page too so you can see how this is all going.
I’m very, very excited about this It is with the support of some great organizations including XWP. Keep an eye out for Tide stuff coming. There is a makesite for Tide already and a slack channel at #Tide. I’m very much looking forward to raising the quality of every single plugin and theme in the entire directory. Thank you. I like when you all clap, because I can drink. It’s water, but watermelon water which I like.
WordPress Growth Council
One of the other things I talked about last year was the Growth Council. This has been a little bit slower, which I’ll take complete responsibility for in getting started, but I’m proud to say that the first meeting of the Growth Council is going to be next week.
It’s actually a scheduled thing. Not like I set a deadline for myself. The idea behind the Growth Council is that all across the WordPress ecosystem community there are dozens, now hundreds of organizations, that are helping grow WordPress and sort of bringing to bear, whether that’s advertising, whether it’s advocacy, creating documentation, creating websites, all sorts of different things, writing books, that are part of the flywheel that really helps WordPress grow.
We want to bring these different folks together, including a different commercial company so that they can talk about what they’re doing and share best practices and also raise anything that maybe they are learning, like perhaps that we find that in this country that the lack of plugins being translated is really hampering growth, or advertising is not working as well, whatever it might be, so bringing folks together.
We got hundreds and hundreds of applications, and we decided to break it into two different councils. There will be an enterprise council; the way I describe this is people the enterprise side of WordPress, there’s lots of agencies and people working on things that the typical customer is going to be a very, very large site and over investing over $100,000 into making it an amazing site, things like big enterprisey things, and then the consumer side, which is often very much in line with the idea of democratizing publishing for WordPress, which is bringing people who might never have had a website before or might have a website on a closed source platform, liberating them and helping them find the coolest open source way to publish online.
That will be meeting next week, and I’m looking forward to getting some notes and some agenda and everything posted, and next year having a bit more to talk about what’s happened there versus just saying, “Sorry ya’ll that it didn’t happen yet,” but it is now.
WordPress sites with SSL certification increase
One final thing I want to chat about was, last year we talked about Let’s Encrypt and sites that were starting to go over SSL, and WordPress, the project, different hosts, everyone had been doing a fantastic job getting more sites on SSL. I’m happy to say that we’ve more than doubled; we are now 36% of all the sites, that we know about, all the WordPress’s that we know about in the world, over https which has again more than doubled what it was last year. Thank you all for making the web a more secure place.
The big shift this year was that we moved from a feature driven release schedule versus saying we were going to do a release every four months, like we had in many years past. I’m glad there’s a fan of that, and that was a good whistle. I don’t know where it came from, but it was a really good whistle.
Even though, you know , when I was on stage I said, “Hey, I don’t know how this is going to go. We might not have any releases this year because we are going to work on things that we think are great and then release them when they’re ready and the version numbers will follow that,” in spite of that sort of warning we actually had two really fantastic releases around the three focuses.
The releases … I talked about the three focuses being editing, customization, the REST API. Around the customization focus, we were able to do some really, really cool stuff, and that was in releases 4.8 and 4.9 and led by Weston, Mel, and Jeff who did a really, really fantastic job getting some stuff out there.
To talk about this, I would actually love to invite Mel and Weston up to the stage. We’d all love to hear direct from the awesome people behind us. Hello, hello. Mel, Weston are going to talk about what’s going on in 4.8 and 4.9.
The first focus: Customization
Rich media and text formatting brought to widget updates
Mel: There are a lot of people in this room. While Gutenberg has been underway for the entire year, we’ve been trying to make a lot of improvements still to WordPress, as it is now, and to make all of your lives a little bit easier. In 4.8 and 4.9 we tackled some long term pain points and introduced also some great new workflows for building WordPress websites.
If you visit any popular cooking blog or news website you’re usually going to find some sort of media in their sidebar, usually an image. Actually adding that image to your sidebar is a disaster. You need to upload your image in your media library, you need to hunt for the URL, copy it, open the customizer or the widget panel and then manually actually write the image tag in a text widget. It’s super complicated and it’s just way more than we should ever ask people to do.
Now you can actually just do everything in one place. Pop an image widget into your sidebar, click to open your media library, and then just upload it directly there. You could do the same for audio and video and then also as of 4.9, you could now do it for galleries as well.
Weston: In the same way that it was painful to add images to your sidebar, it was also painful to add formatting to text in your text widgets, and so in 4.8 we added the visual editor to the text widget to do basic formatting and also to be able to now, with 4.9, add things like images into your text widget as well.
The post editor has had visual editing forever, and even before that it had those quick edit HTML helper buttons that you can use if you have the text have focus, but the text widget didn’t have either of those, and so finally now you don’t have to mess with HTML unless you really want to.
This was a kind of a cringe moment for the 4.7 release, when we made the video, because we had the starter content that allowed you to populate a blog with your business hours, but in the release video when we added the starter content widget that had the business hours there in the release video it’s showing in HTML, and that’s not something we can expect for users now to be able to have to do unless they want to. Now in 4.8 and 4.9, you only have to mess with HTML if you want to.
— Weston Ruter (@westonruter) December 2, 2017
Mel: In the past year or so, WordPress has made some really cool improvements to links. In a previous release you can now paste a URL on top of some text repeater link, which is actually my favorite feature ever and I find myself using it in Gmail, it doesn’t work, and Google docs – it doesn’t work – it’s really frustrating.
We’ve actually taken that a step further. I’ve personally run into tons of problems where I’m trying to update some text that’s linked, and so I’ll click at the end then it adds the text after the link, not in the link, so I’ll do this hack where I just click in the link and then type it and then delete the rest of it; it’s a mess.
Now we actually have this background that appears when you’re clicked into a link, so it’s awesome. You can double arrow into and out of a link, so it’s easy to know whether you’re actually editing the text in it or around it. It’s awesome.
Also, as Matt previously mentioned, we introduced this new dashboard widget showcasing WordPress events near you, and since launching the widget we’ve seen meetup attendance go up by almost a third. So 4.9, just released before Thanksgiving here in the States, and it ended up being a bigger release than I think any of us were expecting.
We had a total of 443 contributors, many of whom I’m sure are in this room or watching the live stream, so give yourselves a round of applause, and 185 of them were actually new contributors. This is the first time that they contributed to a WordPress release and got props. Pretty huge.
Scheduling customization drafts
Weston: One of the features that I’m personally really the most excited about with this release is something that we’ve been working on, building up to for so long now, and that is being able to draft and schedule changes within the customizer.
Now the customizer is really like a staging environment in your live site. Now you can go in and start making changes, and instead of just having to decide whether you want to publish them or not now you can just open that little gear icon and change the status to, save a draft, and then you can leave the customizer, come back again, make some work changes, leave, come back again, and then you can schedule them to go live when you want to or you can publish them right away.
Mel: Imagine you have an e-commerce site and you’re like, “Oh, great, it’s the holidays, I want to have a sale. I want to push it live at midnight but I don’t want to stay up that late,” you can now schedule that change to go live, while you’re sleeping, it will get pushed out to all your customers and then later that week when you want to end it you could schedule it to end maybe midnight the following week. That’s all now native to WordPress.
— Gloria Antonelli (@GloriaAntonelli) December 2, 2017
Sharing a ‘Live Preview’ link
Weston: Part of that new functionality is the ability to have front-end preview links for those changes that you’ve drafted or scheduled. Now, if you make changes you can save a draft and then this little link at the bottom, in the panel, will give you a URL that you can share with a client, a stakeholder, to review those changes that you’ve made and then they can review them on the front-end of a site without ever going into the customizer without even having to give them a WordPress user account.
This gives you the ability as an agency or a freelancer to be able to give to your client the ability to see what you’re going to do before those changes go live so that there’s not the rush to, “Oh, this is broken, please fix this right away,” now that there’s more time you have to iterate on those changes.
Mel: A couple of months ago I attended a hackathon where a bunch of teams made WordPress websites for non-profits, and since we were working in groups we kept running into issues where team mates would accidentally overwrite each other’s changes in the customizer. About a week later, after this hackathon of course, Weston came to me and was like, “What if we added post and page locking to the customizer?”
Now if you’re collaborating on a site with other people, you can’t overwrite each other’s changes. If you see somebody across the room chatting and like they’re, the customizer says they’re working on it, you can take over, like you can when posting pages, and then their changes will be auto saved so if there’s something that they didn’t save they won’t lose them either.
Restoring autosaves in the Customizer
Weston: Speaking of auto-saving, now when you’re making changes in the customizer and you, say, your computer crashes or you close the tab accidentally and you want to restore those changes you made, now it’s much easier to pick up where you left off and restore those changes to not lose the work that you’ve done, just like when you’re editing posting pages, that same kind of auto saving functionality, the auto draft, is part of the customizer.
Better native coding
Mel: WordPress has long been a really great tool for learning how to code. I’m sure many of us in this room started out tinkering with WordPress websites, that tinkering became a job, which became a career, which has brought us all to this room and this city with really delicious hot chicken.
Weston: In 4.9, we focused on making code editing faster and easier and much safer so that you can make changes with confidence even though you may not be a coding expert without requiring you to have your IDE open. We added syntax highlighting and autocomplete features to the code editors in WordPress, including the CSS editor and the customizer, the HTML widget and also the theme and plugin editors.
Mel: However, editing code live on your site can be very dangerous. I’ve personally white-screened more than one site in my day, just trying to make some quick edits to my theme, and that didn’t turn out so quick, did it?
Weston: In addition to improving the usability of code editing with the syntax highlighting and the autocompletion, we’ve also integrated linters into the code editing to do error-checking. Now if you have a syntax error in your HTML widget, now it will tell you that you forgot to close that nested div, and so if you publish that widget change it’s not going to … It’s going to stop you from doing that so that you don’t break the whole layout of your site.
In the same way, if you’re editing .php files in a custom theme or a plugin, now if you try saving a syntax error, instead of white-screening your site now it will stop you, it will tell you that this is an error and it will give you an opportunity to fix the change you made.
Mel: We just want to give one final shout out and thanks to everybody who contributed to WordPress 4.8 and 4.9, especially Jeff Paul. Jeff, where are you? Stand up.
Weston: There in the back.
Mel: Yeah, there in the back. Jeff has been totally instrumental with these releases, just kept this on track. Awesome. Thank you all.
Matt: Nice, great job. Mel, Weston, and Jeff have not just been doing amazing at that presentation, they’ve been doing a really amazing job really all year. Thank you, again. It’s showing how … Part of the idea was changing how … Traditionally we’ve only had like a lead developer role in WordPress, and that’s really kind of the only hierarchy that we’ve had.
One of the things we tried to do with the three focuses was say that, like peanut butter and chocolate, you pair a designer and a developer, and I think some of the work that’s happened around the customizer this year in particular, all the things they just talked about, really shows when you take a design first approach for some of these problems that you can really find sometimes some things that actually aren’t that hard.
There are some things that were hard in there too, but some things that like, “Wow, I’m so glad that we did that,” because we are going to make a lot of people’s lives easier and better without taking a year or two to have to implement it. Thank you very much.
Now, what were we talking about? Sorry, just had to. Even though we’ve been doing a lot more design this year, we decided not to do a default theme. This was because we wanted to keep the focus on the focuses, and so we … This is the first time since 2010 there will be no 20 something theme, no 2017. That just means we are going to have extra cool stuff for next year.
The second focus: WP REST API
The second of the three focuses was the REST API. The big update here is that there’s still room to improve, and we’ve done some great work around Gutenberg and the posting kind of content API’s, we found that there were some areas where it didn’t fully deal with capabilities or maybe have some fields that we needed.
We’ve done some improvements there, but we have a lot to do still to really make the REST API kind of a first class citizen in the WordPress world. The goal which is in the future, to have the vast majority, if not all of WP Admin, actually go through our own API, so that way by using our own API we make sure it’s fully great for everything that we possibly want to do.
The WordPress-CLI project
We did pick up a bonus focus this year, which you may have noticed, that the WordPress-CLI, WP-CLI project, became an official WordPress project. This is very cool. When it became official we did some fundraising for it. So, we’ve had four releases there, four major releases with some milestone features, 124 contributors, and there have been 46 talks on WP-CLI at different WordCamps. That’s unique different talks.
If you haven’t used the CLI before, it’s official, check it out. It’s basically a way to interact with your WordPresses via the command line. It’s ultra-fast and you can do really cool stuff, like the trunk version actually has a way to do scaffolding for Gutenberg, which is pretty cool.
The third focus: Gutenberg
I’m going to get to what you all are probably curious most to hear about, which is the third focus, editing with Gutenberg. I don’t know why we’re laughing. Gutenberg has been the longest-running major feature development that we’ve ever had.
Typically, we work on things anywhere from two to … Really the longest I can remember is maybe, it spans two releases is the better part of six months in our previous release approach, but with Gutenberg we’ve now been working on it much, much more.
For those of you who don’t know what Gutenberg is yet: it’s basically an effort to simplify all the different things we have going on in WordPress; short codes, widgets, menus, and the random stuff that people put in TinyMCE in the one elegant concept, which is a block, which we demonstrate with this non-trademark copywritten Lego block there.
It’s been about 11 months since the kick-off. A post from Johan Matías and I talking about what the focuses were going to be and how to do it, in that time, in just those 11 months, it’s already have over 4,300 commits from over 100 contributors, 1,700, almost 1,800 issues of which 1,377 have been closed. Don’t think those are all open issues, most of them have been closed. It’s really drawn together the community in a very cool way.
We’ve been doing almost weekly releases since the first beta that came out. It’s had 18 major iterations over just those 11 months, and these are plugins that people have been testing. They’ve done all sorts of cool stuff. In fact, I heard that some of you might have seen … Did anyone do the Gutenberg testing down at the booth area? We actually ran 90 user tests today, which is incredible, 90 different user tests, all recorded, all ready to go. Anyway, to talk a little bit Gutenberg, I want to bring up my good friend, Matías. Round of applause for Matías.
Matías, alongside Johan, who had started as your design pair at the beginning, and lately Tammy, along with of course many, many others have been working diligently at Gutenberg all year and we are going to try something that we have not done in maybe the history of State of the Words, which is a live demo. You’re ready?
Matt: All right, take it away.
Matías:: Thanks Matt.
Matt: I’ll be right here if you need me.
Matías:: I’ll need to do this delicate operation first. Let me see …
Matt: Low tech …
Matías:: Let’s see …
Matt: Login. I’ll narrate what’s going on here. Can you make it so it shows your password?
Matt: Okay, there we go. All right, we are in. I’ll let you take it away.
Matías:: Seems I’ll be following Morton’s footsteps, brave footsteps in attempting the live demo. However, this version is not … It’s not even trunk, it’s a mismatch of branches, so happy accidents might happen. I apologize in advance if things break.
I will start by … Following the Spanish vibe of the WordPress vibe or the WordPress.org design, I’ll start by copying the piece of the beginning of the Don Quixote, the work by Cervantes, and I’m going to … I copied it from Google Docs and I’m going to paste into the editor to start working a bit with this.
The first thing is that nothing should really look unfamiliar, it’s just some text on an editor, you can go through the paragraphs and the elements. But as soon as you start interacting, you’ll see that you’ll get this contextual toolbars and elements. This allows you to, say, focus on this paragraph; let’s make it a big bigger, let’s switch it to be center aligned, let’s select it all, apply some italics.
Let’s move to … If you focus one thing with … When everything is a block, you get this little plus buttons here between blocks so you can add other kinds of blocks. This opens the blocking starter, which is what Matt referred to as trying to simplify all the ways you can insert different kinds of content.
In this case, I want to add … And I can search here, and it shows me the things that are there, I can navigate all this with keywords, most of it, a lot of work still remains to be done on there, but I can still access this, insert the separator. I might add another one here, just for repetition.
The other nice thing is you can … You can access the inserter from multiple places, but you can also … And we show a little hint here when you … I don’t know if it’s too visible on the screen, but it’s such that you can use the slash command, which is writing a slash, to insert any block.
I’m going to add an image here. Let’s scroll a bit. I’m going to drag an image that … When you drag an image, it immediately shows, even while it’s uploading, it shows you the results so you can start continuing building that. Let’s add another kind of block. I went to the bottom here, and I’m going to add a cover image.
Cover image is very similar to image in its current state. It allows you to select an image from the media library and then write some text. In this case, let’s do “¡Gigantes, Sancho!”, and then we can bump it like this, and we start to get some rhythm to this little story. I’m going to add the final block here, text columns. Let me get some more text. This is a long paragraph. I like these long paragraphs. One column, and this for the other one.
This looks a bit tight, but we can expand it a bit here. Now let’s add a final separator. Let’s close these … Actually, let’s add one more thing, the little drop cap of course, and a title. This shows how you can quickly get into an interesting looking post with more variation. Basically, the idea is that the block is there when you need it and it disappears when you don’t. It’s not a trivial balance to accomplish, but I think it’s getting better with each release. If you just use the arrow keys you can navigate through the whole post. You don’t see the UI, but once you start moving you can get these additional tools.
— David Bisset (@dimensionmedia) December 2, 2017
I’m going to move to a demo that we have prepared. When you install Gutenberg, you get this menu item on the sidebar that has a few utilities; one is a demo, you also have feedback on documentation. If you looked at them … This is meant to be like an already put up post so that you can play with some of the settings. Here you can … If you load this in the plugin you can just check how some of these blocks behave.
This is a longer post that has more of the variety of blocks. You can check the different styles that a specific block can give you. One nice thing in this kind of long post is that we have this utility called, table of contents, that allow you to basically browse all your headings.
If you change the headings to be an incorrect size, incorrect in the document table line hierarchy, we also warn you about that so that we … [applause]… That should be a nice way to still let users do whatever they want but still inform them about the best practices of what really WordPress has to that for all these years, which is a semantic and accessible web.
I’m going to show a bit the gallery, which I really like the gallery block because … I don’t know if you have seen other people try to do this kind of mosaic layouts , but very often I have friends that would just create this in Photoshop and upload a single image with all the mosaics.
I think it’s good that we offer something that can be … And you can play with it and just change the columns, change the width if you want three images, go back to single one to play with different layouts and see what works while still making sure that the markup is the best we can produce and that everything remains semantic. You can also remove some images and play with this.
I think this allows a lot of layout possibilities and is quite nice. Let me move back … The other thing is embeds. If we go back to the inserter, you can search here for, like YouTube or whatever and you can … It exposes all of the embeds that WordPress already has but sometimes users don’t know that exist. The embeds, of course, can be played directly on the post. We also have things like buttons and little emojis that you can also increase in size [laughter].
Let me show you … This is just working with the blocks that come with WordPress, but you can also … Like, sometimes you will need to write your own HTML for something. We have a block, a custom HTML block. I’m going to add everyone’s favorite HTML element [laugher]. You can keep this HTML between all your blocks and it will just work. You can also preview it in place. We can see our nice marker[applause], we can also move the marker.
Let me add one more. This is a fun little tag, but you can imagine the kind of custom HTML things that people might need in their site, and without having to switch the whole editor to the HTML node and you can add these little snippets which will be more powerful when we introduce the reusable blocks.
Let me show you another, a more interesting example of a block, which is the latest posts. This is a dynamic block, it means that it’s rendering posts that already exist. I cannot edit this text, but it allows you to configure things, like how many posts to show, and it allows all of this in real time. You can enable the post date, switch it to agree, and you get a nice thing with your latest post. You can add this to whatever post page. You can imagine all the kind of dynamic blocks that you could have like this.
Let me go here. I’m going to stop this video so that it doesn’t slow things down. This code is poetry code. This is something that has come up a few times, that we were working on reusable blocks. That’s one of the reasons why I’m running this mix of branches in trunk, is so that I can show you how it actually works.
We have this code is poetry that we want to use in some other post. We are going to convert it to a reusable block and we are going to give it a name, and we’ll save it. Now we are going to switch to a new post. It’s still saving, okay. Here, if I do … If I go to the … Let me see, save blocks, code is poetry, okay.
You can reuse this. …[applause]… You can see how this could be a very convenient tool for, especially when you need , when you think that you might need a custom post type for something, but really what you just want is to reuse a testimonial in some other page, like these kind of things. It’s basically a way to create blocks on the fly without having to write any code.
If you consider, we could have nesting, I think Morton showed a block with an autobiography, all these kind of things you can combine them, save them on the fly, and then just have them all here in the inserter if you see there’s a save – Here I have a bunch of weird blocks, but you can just have different kinds of blocks that just output to the thing.
I want to show you now some integration with some code. In the last version of Gutenberg 1.8 we had the support for templates. Templates are really just a list of blocks. I hope this is kind of readable, but this is just a register_book type, it’s adding a post type called ‘books’, it is showing the REST because we use it with the API. The interesting thing is this template attribute which defines an array with different types of blocks, in this case an image which has some attributes; a heading, and a paragraph.
If I come to my editor and I go to, ‘books’, and I add a new ‘book’, instead of seeing a blank page now I get an already setup thing here where the … I can do something like drag an image here so I get my cover. I’m going to grab the full title because I don’t want to type it, and I’m going to add a little description.
— Matt Mullenweg (@photomatt) December 2, 2017
This is, like very quickly I can get into the intended display that the author, the developer, the themer intended for this post while still giving the user a very intuitive way to input that information quickly. I think templates – and if you expand templates, right now they work with custom post date but they can also work on the fly, you can see a lot of interesting mixture especially once we add nesting. All of those things together I think will give a lot of flexibility to create in these kinds of layouts.
One last thing, before I extend too much, is – Let me go to the ‘testing in post’. The other thing is how things can extend certain blocks, or even general Gutenberg functionality. One thing that we have on the paragraph log is that you can add certain colors and just have … What happens if the theme was to have a different set of colors? We support … We allow things to specify in an add things to protocol.
You can paste an array of color values. Let me save … If we reload, now the colors at the surface are the colors offered by the theme. It’s a nice … Another thing we show is if your contrast ratio fails, we warn the user that this is not very legible [applause], and once you get into the legibility, it fades away.
— David Bisset (@dimensionmedia) December 2, 2017
The other thing that themes can do … Let me add some filler text here, the other interesting thing is this looks like, and especially if I collapse this, this is a very white, clean layout but your theme might be different. In this case, I am going to enable my theme to modify the editor styles. My theme is mostly modifying … Let me add a heading, heading one and some more text. This is saved.
Now I’m going to reload the page, and now this is applied in my theme Styles to the editor. The heading is changed because the theme said so; I have the … This remains, but I can remove it. Something like ‘Latest Post’, which we saw before, come with their own theme specific styles so it looks like the theme wants it to look like, but the functionality is the same. If I enable these things, all the functionality remains the same.
One more thing is that you can … Let me disable this theme. I’m going to load them again. You can also, since everything is a block, you can also select multiple blocks and move them all together, if you need to. This also allows different transformations, like to make a list out of multiple paragraphs, if you have multiple images you can convert it into a gallery or a slide show, all the things that plugins can hook into.
That’s about it. I would like to … If all the people that have contributed so far to Gutenberg, before and even through the WordCamp, if you can stand up and have a round of applause for everyone. Hand it over back to Matt.
Matt: I’m just trying to plug in …
Matt: Let’s do the theme again.
Matías:: I’ll let you work at it. My favorite part of that is actually where the theme styles came into the editor. It was easy to miss … Thank you Matías.
Matt: Thank you.
Matías:: Flew in all the way just for this. That was front-end editing, that was WYSIWYG, in the real sense of it. If you would like to see some more awesome kind of Gutenberg introduction, actually check out Morton’s presentation yesterday. Morton, where are you? Somewhere, right there. Stand up. It was funny … They’ve got some questions and they kept bringing these questions, it’s like, “I’m not actually on the Gutenberg team.” Now you’re honorary Gutenberg team member, because your presentation was so great, and we will get it online very soon. Thank you.
You saw that cool stuff, I know what you’re wondering, how long will it be. Well, to that, we did some non-traditional measurements … You might not know-
Matt: We got a bingo, but I haven’t said it yet. I’ve been … This thing on my face is because of Gutenberg, so I’m calling it the Gutenbeard. When Facebook changed the React, or didn’t change the React license, I was like, “Argh., that’s like another inch.” We think that this kind of a before and after, how long we think it’s going to be, and that’s [inaudible], who also helped design all this modeling over there, but really I think it needs about 12 more iterations.
— WordCamp US (@WordCampUS) December 2, 2017
We’ve done 18 so far … Or about four months. That puts us back until around April for when I think that this will be ready for the widest audience, even wider than is seeing it now. In the meantime, we are going to keep doing a lot of 4.9 releases.
We’ve already had a security release for 4.91, but we’ll push other stuff out there in the meantime, including perhaps some enhancements of some really good ones coming, certainly anything with security, and then at some point as part of the path to Gutenberg there will be sort of a plug for it, so that people can install and test the plugin.
What needs to happen first? Well, we need to get some really great documentation for Gutenberg, which is not there yet. We need continued conversations around it. There have been 77 meetup events and 20 WordCamp sessions so far. We need plugin developers, so really start to re-imagine what their plugins and their functionality will look like in a Gutenberg world. It’s actually interesting.
WordPress introduced WYSIWYG in version 2.0. That was 12 years ago. Outside of some relatively incremental updates, including like link boundaries and other stuff, that experience has remained pretty much the same for about 12 years.
Gutenberg is what we want to build on for the next 12 years. Think of it as the thing that will be around for a while. We are going to keep working on it. There’s many, many much more to come after the main release, but this is the basis for so much of what’s going to be happening on WordPress, is going to be Gutenberg-based.
Finally, it needs you. I love these Wapuu’s, they were extra cool. Thank you. That was so cool, with Sally the riveter and everything. You can contribute to Gutenberg; we have sort of a site that talks all about it, WordPress.org/gutenberg, we’ve got it at GitHub, and also of course make.wordpress.org/editor is where … Right? Editor, is where all the Gutenberg stuff is.
As I like to think about it, forget 280 characters, let’s 280 blocks. Right? How can we make it so that we can build things that people never even imagined before, things that … To do like some of the stuff Matías just showed, which isn’t even in the final version that we are going to ship. You would have needed lots of plugins or basically to be a developer to get even close to that. Now we are making it available to a much, much wider audience, very much in line with our mission of democratizing publishing.
The Classic Editor
Now, I realize that for some people in the room … Well, a lot of people are obviously very excited about that, some people saw that and were terrified, thinking about everything that was going to break, everything that isn’t going to work, all the clients are going to need retraining, everything. Actually, the Gutenberg team has created a plugin called Classic Editor.
It is on the plugin directory today. You can install it. This isn’t a joke, this is real. If you think April, the plugins you use or the site, whatever, is not going to be ready, install this plugin now. It will make sure that when 5.0 comes out, the editor, that will be default on … Kind of when you click, edit, in WordPress, it will still be the Classic Editor.
It also allows us to gather usage data there and make sure that we can let people know that as Gutenberg evolves, that maybe where they thought it wouldn’t work with, say, a plugin that they have, it might now be 100% compatible. Check out the Classic Editor plugin if any of that terrifies you. This will work for at least a little while.
The three new focuses for 2018
During all that, we grew about another 2%. This has actually out of date, we are now at 29.1%. That’s top 10 million websites. I’m really proud … My sister got bingo. I’m really proud of what everyone contributing in WordPress has been able to accomplish this year. This is kind of a lagging indicator, but it’s nice to be able to see that our continued adoption among this cohort shows that we’re making something that people want.
I will be keeping on my lead hat through 2018. Originally I planned it to 2017, but I want to see Gutenberg all the way through. The next step, what comes after what you just saw when we finished the editing experience, is Gutenberg-based site customization.
If you imagine, like those blocks, including some of the dynamic blocks that you saw, something like reusable blocks, well, what’s the ultimate reusable block; everything else that goes around the post a page. You could imagine a header, a site title, social icons, related post, all of this as different blocks that could be put in a post a page if you want to, as dynamic blocks, but also be really, really cool to do just laying out the whole site.
This is a powerful enough concept that I think it warrants doing a new default theme. We will start working on that in 2018. I think that this customization part of Gutenberg can actually happen a lot faster than phase on. I want to announce as the three focuses for the coming year there will be Gutenberg editing, Gutenberg customization, and a Gutenberg theme.
I think that most of the hard stuff is out of the way already, but these might be my famous last words. Depending on how the year goes, next year let’s maybe forget about this slide, or if it goes well I’m really looking forward to sharing with all of you, when we return to Nashville, all the cool stuff that’s happened with Gutenberg customization, a new 2018 theme, and what the next 12 years for WordPress will look like.
Man, a live demo! I didn’t know if we’ve done that ever before and might not do it ever again. I actually went on the audience so I could see everything. Now you’ve heard the idea, what we’re looking at, this is where we ask questions and answers. If any of you all have something … I see you’re starting to line up the mics already, I will do my best to answer it or pass it to one of the very capable people, WordPress contributors that are nearby.
We’ve got spotlight, wow! This is mad fancy. I also, just before we begin to QA, want to take this opportunity to say hello mom, this is the first year we’ve gotten the livestream working before WordCamp US. I believe that my mom is watching this, and so I want to say I love you, thank you. All right, let’s kick off with the questions. To the right here, say your name, where you’re from or something, and then question.
Fahad: Hello, Matt. This is Fahad, from Pakistan. I’m here to attend the WordCamp. With the Gutenberg, just a question came into my mind, I apologize if you find it a little critical.
Matt: It’s okay.
Fahad: Actually, there are a lot of plugins, there are a dozen of plugin who are already capitalizing on this idea, different page builders; I don’t want to name all those plugins, but with the growth of those plugins they always kept on capitalizing and branding WordPress. Don’t you think that it’s more like a … You can say it’s a serious trouble for them with the Gutenberg and WordPress is in fact demoralizing those plugins to grow?
Matt: That’s a good question. I think that the very many page builder plugins out there show that there is a demand for this, but even the largest of them only have, in the hundreds of thousands, a couple of hundred thousand users, and what we want to do is bring this to everyone and for free and core.
And the other thing that is sort of balkanization of this approach is that it makes it really hard for other plugins to interopt with that. I know, like Yoast, for example.Because everyone presents the content differently, any plugin that wants to look at the content has to build support for, well, 20 different things.
Any theme that wants to support the plugins really natively has to support 20 different things. By standardizing sort of some of that core functionality into the core of WordPress, I think it will actually create a huge opportunity for all of the people we just talked about; other plugins, the page builders, and themes.
You saw some of the cool stuff that can happen with themes. One, this has been a common concern any time we’ve brought anything into core, or in the Jetpack. For example when contact forms went into Jetpack people were very, very concerned that it would hurt all their contact form plugins. Well, it looks like they’re doing great.
I think that it will allow that the plugin page builders premium, whatever, to focus on what’s different about them than focus on sort of reinventing the wheel and we can standardize the things, the wheels, so that everyone can drive on the same car. Will that work?
Fahad: During your speech somewhere, I came to know … You said there won’t be any 2018 theme or something, but in the end you said that we are going to build the 2018 theme.
Matt: There will be no 2017 theme. There will be a 2018 theme. I apologize if I misspoke there.
Fahad: Thank you very much.
Matt: Man, these lights are bright. There will be no 2017, there will be a 2018. Thank you for your questions. Over here.
Scott: Hi, I am Scott. I’m from Dallas, Texas, and I have a question. I find it pretty important, but I think Gutenberg kind of changes the game there. Do you think that a potential Fields API could be just as important as the REST API, the developers needing to manipulate fields throughout the six plus screens inside of WordPress, or do you think that Gutenberg will negate the need for a Fields API in most other areas?
Matt: That’s a good question. I think a Fields API will still be needed. It’s not one of the focuses for 2018, so I wouldn’t bet that it happens that year, but Gutenberg will cover a lot of use cases but not all of them and I think the Fields API would still be really useful.
Scott: Thank you.
Matt: Thank you, and thank you for your work on Pods. All right, let’s go over here to the right.
Phil: Hello. I’m Phil, from the UK. You mentioned-
Matt: Not a lot of UK love in here, come on. [Inaudible] the UK a lot.
Phil: Don’t mention Brexit. You mentioned about the customization stuff in Gutenberg, and that’s really exciting, kind of more excited about that than Gutenberg itself now.
Matt: I’m having a little trouble hearing. Go closer to the mic.
Phil: Sorry. I’m excited about the customization stuff in Gutenberg. How do you think … Do you have a vision for how you think that might pan out with the customizer? How do you see the two working together, or will one be substituted to the other, or how … Do you have an idea of how that might pan out?
Matt: Yes. Well, I mean, yes that they will work together. Weston’s actually sent me a mock up just like a day or two ago. When you look at it … One of the coolest parts of Gutenberg is we can take this arbitrary HTML and create a rich semantic sort of structured version of it and doing that for a wider theme and allowing themes to perhaps even provide styles that look just like the front-end will.
Either we can move customization totally to the front-end, so you’re actually rearranging things, or maybe we create something much like we just showed in Gutenberg where NWP admin is a cool way to move things around, and that would also be nice because then there could be toggles for like show me what it’s going to look like on mobile, show me what it would look like on App, show me what it would look like on a tablet. You can kind of do some cool things for testing that out.
A lot of what’s in the customizer, like I said, we want to replace shortcodes, widgets, menus, all that, so all that stuff that’s currently there all turns into blocks, so some of that interface moves out, we are trying to squeeze into the customizer or sometimes it can feel a little bit tight. I’m reminded of … Have you all seen Aladdin, where it’s like ginormous intergalactic powers, itty bitty space.
Sometimes the customizer feels like that; it’s amazing powers but in a small space. It allows to break some of that functionality up. There’ll be like a full block interface that can really be both responsive in full screen for editing menus and things like that. That is the plan for how it’s going to happen.
However, like in everything we’ve been doing that’s really been design led, I imagine that we’ll start with how this is going to look and work and do lots and lots of testing iterations along the way, although I think that customization can happen faster, because we’ve done a lot of the technical underpinnings with the editor part of Gutenberg.
It doesn’t mean that we don’t need that we don’t need just as much testing and things like that. We’ll definitely want to test the customizer at meetups and do all the same stuff that we’ve been doing with Gutenberg editor so far. Cool, thank you. All right, over here to the left.
Audience member: Hi Matt, can you hear … Good. Thank you. I really love the Gutenberg demo. I saw Morton’s yesterday and yours today and I’m really getting excited. I really appreciate you guys. I wanted to ask you about some vocabulary you used right at the end of the Gutenberg demo. You said this is true front-end editing and I … We never saw the front-end. The front-end is the thing the user sees; we never saw it.
My definition of front-end editing is editing that happens on the front-end, which we never saw. I just want to make sure that there’s not a “move-the-goal post” thing going on here, especially because I think one of the advantages that something like Beaver Builder has is that it literally is on the front-end the same way that Squarespace is. My question to you is, what does front-end editing mean to you?
Matt: I talked about a little bit about this in this last question, where there is the version of front-end that literally means you’re on the front-end, so that we’re serving a dynamic version of it to you that actually isn’t what you users see, we’re adding a bunch of controls that allow you to move things around. By the way, it’s really hard to do that multi-modally, which is how all this content is being consumed, people are looking at in lots of different devices; different DPI’s, different shapes, different everything, and that will only grow.
If you saw Morton’s, he’s really excited about VR, I was like, “Wow, this is a lot of VR,” we haven’t even … Gutenberg and VR has not even imagined to me until that presentation. The way that the content needs to be responsive and display different ways does not lend itself well to a pure front-end approach. But when you talk to users, so although as developers we might have a technical definition of what’s the front-end and the back end, a lot of users that talk about it really want a better WYSIWYG. Because our WYSIWYG, as Morton said in his cool presentation, isn’t actually a WYSIWYG.
It’s kind of a visual editor but actually how that turns into your theme, oftencan be very, very different than how it displays in the back end. Maybe we can’t call it front-end editing, because people won’t like it, but I do want to bring that distance between what you’re seeing when you’re in the editing interface and what your users are going to see as small as humanly possible.
Audience member: Thank you.
Matt: Thank you. How about to the right here?
Kevin: Hi, I’m Kevin, from Give WP. I’m a plugin developer.
Matt: Move a little closer.
Kevin: I’m a plugin developer. I have not contributed through code to Gutenberg, but I have been following very closely, testing it and involved in GitHub issues. I just want to say as one of the more vocal critics, I think throughout the past year, what we saw today is really impressive. Hats off to the folks who are actually contributing in the code, first off.
Second off, I remain really concerned about the extensibility of WordPress from a plugin developer’s or theme developer’s perspective. I’ve witnessed the needle shift from one end of the spectrum to the other over the past year, where our first look at Gutenberg was meta boxes did not exist at all, to this past week where a commit was entered that said a single meta box could ‘undeclare’ support for Gutenberg which would cause the entire editor to shift back to classic mode.
Hearing you suggest the classic editor plugin and different ways to un-declare support for Gutenberg leads me to this idea that we are headed towards a split admin interface with no finality to the transition, meaning that I don’t see a time in the future where everyone will be on Gutenberg, we will always have these people in classic mode, and as plugin and theme developers, we will always have to support two different types of users.
My question to you, based on that, is how do we reach that point where we are past the transition however long it might take where we cannot have this box of chocolates effect where you click, edit post type, and you never know what you’re going to get?
Matt: That’s a good question, and it really gets into more the human side of it than necessarily technical side. Like you mentioned, technically we’ve taken different approaches; we have some meta boxes we can put at the bottom, we have some ideas that maybe we should just turn off Gutenberg totally if there’s meta boxes. There’s different ideas.
Think of that as different things we’ll try and we’ll pick whichever one seems least hard. You bring up the much bigger issue, which is there’s 40 something thousand plugins and themes, at what point do the support for Gutenberg out there matter or not.
My hope and my expectation, based on how this has worked out with new interfaces in the past, like for example when the customizer came out, many themes had their own kind of customization interface and that was something each one did its own way, much like we have different page builders or different ways that plugins interact if I stuff other things into meta boxes.
Over time, once this great unified interface that had this front-end preview was added, that has basically shifted and is very, you’re very hard pressed to find a theme that has its own customization … Doing the stuff that’s easy, that can be done in the customizer, doing it in their own way anymore because people expect it in the Customizer.
The truth is, if you’re a plugin or theme developer, people are going to expect things in Gutenberg, so you really need to develop for Gutenberg. Then at some point, I’m totally okay if you drop support for the classic, and so there will be themes and plugins that say you need to have Gutenberg or newer, 5.0 or newer, if you want to use this.
We already have that existing now, plugins only support so far back in .php in WordPress, there will be plugins that don’t support under WordPress 5.0. So let’s say the plugin author wants to do different things, as you know that’s not going to be that much different because we’re in different WordPress versions where people choose sometimes to go way, way, way back, sometimes a year or more, several years, and support WordPress 3.8 or 3.9 and some don’t bother anymore.
There’s lots of API’s and other things have changed in that time, and at some point you just have to make cost benefit analysis and do things maybe like Yoast is doing for upgrading php and say, “Hey, if you really want the best of this, check out this new thing.”
Kevin: If I could quickly respond, I think this is a different situation because from what I’ve seen in undeclaring support for Gutenberg, it’s not up to the plugin developer or the team who is developing a single plugin, literally if you have 10 plugins installed and that 11th undeclared support, they are going to affect the other 10 that have modernized and adopted support for Gutenberg, and that’s where I’m concerned mostly.
Matt: Sure, and so we’ll want to highlight that, right? Nine out of 10 of your plugins are totally Gutenberg compatible, this one isn’t. Is there an update available, is there … Can we work with the plugin developer to help them get up to date? Yeah, you’re completely right that one could throw it off.
Kevin: As of this week, it reversed to the classic editor when that happens.
Matt: Don’t worry too much about what it’s doing today. Think more about how we are going to navigate in this future, and what we want is every single plugin, every single theme to support Gutenberg. It’s basically how do we get from A to B as quickly as possible. Through talks to documentation, through support, through maybe going in there and actually helping people code up their Gutenberg version of what they’re doing, this is an open source community and we’re all working together on it. It will take a lot of work, but that’s because this is the new interface.
When WYSIWYG was first introduced, there were ton of plugins that didn’t work with WYSIWYG. We forget it because it was 12 years ago. Everything works with WYSIWYG now. It would be kind of weird to have a plugin that didn’t work with WYSIWYG. This will be the same way. 12 year from now we’ll be like, “Wow, there was a time when things didn’t work with Gutenberg.”
Kevin: Thanks, Matt.
Matt: Thank you. All right, to the left here.
Mitch: Hello, my name is Mitch Canter and I live here in Nashville. Welcome to Nashville first of all.
Matt: Thank you.
Mitch: There’s an old adage about opinions and that everybody has one. That’s only part of the adage, I’m sure. We are developers, a lot of us are, and developers are a pretty opinionated bunch. With what you’ve shown today with Gutenberg, first of all it looks fantastic, but how do you and how does your team plan to navigate through all of the noise that comes from all of the opinions that we all have about what Gutenberg is, what it isn’t, what it should be?
Do you have any … You talked about it being on the human side of things in the last question, I’d love for you to talk a little bit about more of that and what you see is … How do we as the community, how can we help you best and how do you sort through all of the noise to find what is the best direction for that.
Matt: That’s really the art and science of software development. My personal philosophy there is that even in the harshest, toughest feedback there’s a nugget of something really that you can learn from it. Any feedback you all want to contribute, even if it’s critical, someone apologized for being critical earlier, that’s all right.
As a Gutenberg team, as WordPress leads, as everything, we’ll try to pick out what is going on there. The better we can understand it, the better we’ll look at it. If you notice, people … Some people are giving Gutenberg one star reviews. Every single one of those one star reviews actually has a response, often from Tammy, the guy who responded to 102.
Some were really good. Someone wrote this amazing poem, that the night before Christmas is the night before Gutenberg, or something; it was a really good poem. I wanted to give the review five stars. There are some I fundamentally disagree with.
There was one I almost put in the presentation but I didn’t want to call them out, which I guess I’m doing now. There’s a review that said that people used to work on their cars, now everyone uses a mechanic, just like people used to design their own websites, everyone is going to have a professional who shouldn’t be doing things that enable people to design more of their own sites. I get that. I want to have the ability to empathize and understand with what that person is bringing to the table.
Until I understand it, I can’t necessarily say I disagree with it, because I might just be misunderstanding. Once I understand it, then you can make the decision and we can say, well, fundamentally WordPress’s mission is to democratize publishing. We want to open it up for the 7.4 billion people in the world who don’t have a website yet, and to do so we are going to need to make it customizable and doing what WordPress does differently than any other publishing platform in the world a lot better and more accessible.
We are going to decide to work on Gutenberg regardless of this one star review. Thought about stopping after I read it, but … That’s really all there is, whether it’s through the tests, through the reviews, through the whatever, however people submit feedback the team will do its very, very best to learn from it and understand it and then make whatever we discern to be the best decision to move forward.
Mitch: That sounds great, thank you.
Matt: Thank you. We’ve got a few more left, right over here.
Cheryl: Hi. My name is Cheryl, and I’m from Charleston, South Carolina.
Matt: Cool. About to go there for the first time ever, I’ve never been.
Cheryl: Please come. We’ll be-
Matt: … two cities I’ve never been to.
Cheryl: … glad to show you the city. We’ve got a good WordPress users group down there.
Matt: We should do a meetup there actually.
Cheryl: Yeah, cool. My question is about who ultimately do you think is going to benefit the most from Gutenberg? I heard what you said in the last answer and it’s interesting to me because in some ways it seems that the average user may actually have a harder time with this, visualizing how to use the blocks.
Those of us who use this every day and we understand a little bit more about information architecture, we understand how things fit and maybe what usability is best. I want to understand that average user’s experience, and are you building for them or are you building for us?
Matt: We are definitely building for people brand new, to publishing and brand new to WordPress. It’s kind of a user core that we are doing a lot of testing with, a lot of learning from. What we want to do is create something that’s really powerful. Like you said, there’s lots of things you can do that is intuitive.
If you think of some of the technology that you love the most, maybe it’s your phone, maybe it’s something else, it actually has a ton of really deep functionality, and you can mess it up too if you get the wrong way, but because it’s intuitive it provides a path for you to go from this is my first time picking up, say, a touch device to here’s how I unlock, here’s how I take a photo, here’s how I do every different thing that you do even though there’s like literally on the average mobile phone probably a hundred different things that you can do, not even counting the apps that all have their own interfaces.
We really work on making it intuitive. That said, I think that developers will benefit a ton too. When I think … One of the personas we’ve been thinking about is like clients people saw and built the site for them and they’re just trying to update it and not mess it up, the ability for Gutenberg blocks to basically preload different templates for different pages or blocks or custom post types, the ability for the theme to suggest colors and to keep it so the legibility of the text – like are trying to provide some guardrails as well.
We want to give people a ton of power but also make it easy to do the right thing. Another great example of that is the IDE features we’ve been putting into 4.9. We’re actually letting you go in and enter the code. This is more on the developer’s side of the spectrum of features, but if you make a mistake we are going to tell you about that and we are going to try to keep you from doing something that’s irreversible.
The beautiful thing about everything that’s going on here is – and Matías didn’t show it – but Gutenberg has a unified ‘undo’. I actually think that the structure that we’re showing, although it seems like more, will be more intuitive over time, because before we showed something that looked like a document but when you tried to move around embeds or do certain things with images … Did you ever have an image that’s right floated and then you’re moving it around and it ends inside a link or doesn’t and like you could get so mixed up there, and that’s what we really saw.
We are trying to make it so that as much as you’re moving things around in Gutenberg there’s never anything you can’t undo and it never does anything you don’t expect.
Matt: Thank you. All right, to the left, and then you aren’t staying the night we’ll aim questions after these four that we’ve got on each side. Bring it in.
Johnnie: Hi. I’m Johnnie, from the UK.
Johnnie: The work on the customizer and editor is obviously amazing, but WordPress isn’t just those parts, there’s lots of different components; you’ve got feeds, users, multi-site. Have you got a plan on how to keep those parts not getting stale and people contributing to those parts, because I contribute a lot to the less glamorous parts of core, those parts shouldn’t get stale and not get contributions just because we’re all focused on these main focuses.
Matt: It’s true. It was actually one of the things I was really worried about this year, because I didn’t know what was going to happen with the focuses and basically would that starve things like multi-site. As you know, if you contribute, there have been some really cool multi-site improvements this year.
Johnnie: I know. They’re mine.
Matt: Then, thank you! I think the answer is we keep doing what you did. We are definitely saying no to features outside of the focuses, but that still leaves a lot of room for improving things. In fact, coding style improvements just came in. I see Gary is looking a little guilty there.
There’s a lot that we can do to clean up things that WordPress does, improve to bring ourselves to our own standards, or like you said make some kind of … Catch some low hanging fruit from different areas of WordPress, like multi-site.
The only thing that I ask, as people work on these things, is that they really try to make it as user-centric as possible. The improvements I … I love it when we do back end improvements to multi-sites, I would love to see some of those admin screens become more intuitive, and I bet there are some designers in this room that would love to help with that.
Johnnie: Yeah, we are working on the API’s at the moment. Once those API’s are in, we can do a lot of really cool stuff. The main stuff to me is performance stuff; that’s not really glamorous at all, but it does actually affect users, like shaving milliseconds off hair and 29% of the web is kind of a big deal, and that’s not on the focuses at all.
Matt: It depends on how the performance improvement is going to look, and this is the thing. There’s a lot of tickets on core track that we are saying we are not going to work on this year, because they are a distraction. If there was something that shaved 10 milliseconds off every single page look, yeah, that would of course be worthwhile depending on how much it affects otherwise.
I would say that the door is not closed for WordPress development, and in fact one of the things I’ve been excited about this year is that we had even an increase in number of contributors. What was it Mel; you said 140 new contributors to WordPress entirely, in 4.9? Yeah, something like that. We are still getting new people contributing to areas outside of the focuses, outside … Gutenberg is not counted in that at all, by the way, that’s all completely separate and I think we can keep it going. Thank you for your own contributions there.
Johnnie: Thank you.
Matt: Thank you. I think that question from Morton is on the bingo table.
Morton: Hello. I’m Morton, from virtual reality. Can I talk about something other than Gutenberg, for a second?
Matt: Yeah, just get a little closer to the mic.
Morton: Closer to the mic, sorry. Last year I asked a question by proxy about WordPress using its power to influence how the web evolves by having representation in the bodies that make up decisions about the web. I think your answer was along the lines of just do it. I’d like to continue that conversation, because we have great people in our community that are working on accessibility that should represent WordPress in the fora that make decisions about accessibility.
We have great people who work on GDRP in Europe that should represent WordPress in the fora that make these decisions. We have people in the US that work on political decision around that, but we don’t have a methodology for making decisions about what WordPress stands for. No one can actually represent WordPress in any of these groups.
We have all the power and none of the ability to do something about it. How do we as a community make decisions about what WordPress stands for and then find representatives to front those decisions into the bodies that make decisions that impact us and our users so that we can truly help democratize publishing and to do other great things, like just bring democracy to the world?
Matt: First, thank you for the question. I think you’re highlighting that … There’s kind of two issues embedded in there; one, how do we know that we are aligned, so that the person doing the representation is actually aligned with something that we can call WordPress, whether that’s the … It could be the community at large, although … But we are more of a representative democracy, I think so, perhaps aligned with other leaders; and then two, we don’t really have a way to recognize or give autonomy or authority outside of developer roles in leading releases.
We just introduced that for designers. We don’t have that yet for accessibility and in fact … Or many other areas that we work on. In fact, sometimes we might roll something back because the committee … Typically, how these groups operate is by committee, and the committee might agree on something and then someone else, like a lead developer, might say, “Oh, that’s not actually what we want to do, or what we want to happen.”
What I would love, love, love, love, love is for more of this to not be as committee-driven as it is today. Because what I have seen happen personally, I’m not going to call out any of the groups, but sometimes it’s like the lowest common denominator of what can be done. And that’s not necessarily going to move us forward.
To this sense, I bet a lot of people I think have been hesitant to step up and say, “Okay, I’m the head of XYZ for WordPress.” If there were, I could meet with them regularly; we could have a every month or two meeting and these sort of things could come up, or we could make sure … We could put something to some sort of quorum to say, “Okay, so and so is going to go to this meeting in Brussels,” I guess is where all these happen, whatever it is, for whatever kind of area that you’re talking about; I would love that
To the extent … It’s been like pulling teeth sometimes to even get some of the committees to elect a lead. To extent, we can have more of that, I think that would enable exactly what you’re talking about. I think there is a bit of a vacuum there and it can be filled by people who step up, and I would love for it to be. What are you going to lead, besides virtual reality?
Morton: A lot-
Matt: … I didn’t mean to put you on the spot. Thank you so much-
Morton: Make it accessible-
Matt: Thank you for the question. Last couple, I’ll try to do these a bit faster so we can get out.
George: I’m George Pennsylvania, also from actual reality. With last year’s three focuses being customization, editor, and the REST API, customization shipped two releases, the editor is going to be the main focuses for this release or for this coming year, that just leaves the REST API behind. The REST API will be getting some ancillary benefits as Gutenberg develops and starts using it more, but there’s one big gaping void in the REST API, and that’s authentication.
There is no real good way in core currently, and my doomsday scenario that keeps me awake at night and leaves me scared is that some app is going to start building a cookie jar to ask for username and password and just do cookie based authentication to grab nonces and then fake the REST API’s as though it was a browser. What are your feelings on the possibilities of Oauth potentially with app broker, versus basic auth, versus application passwords, versus something custom and actually getting something shipped?
Matt: Well, first I want to say that I love cookies. Just full stop there; I want that to be on the record. In terms of … You nailed it, and in your question you kind of had the answer to that. I expect there to be a lot of improvements to the REST API this year as we start to use it ourselves.
I don’t know if that will be … I don’t know if authentication is necessarily the highest priority simply because I don’t think our API’s are good enough that they can really be fully used outside of WordPress, because they are not able to be used inside of WordPress either.
Then, two; some of the predicted … We talked about a Cambrian explosion of things built on the REST API once it was in core, and it’s fair to say that hasn’t really happened. Some of the posts people did, even something like the example apps don’t even work anymore even though the API is now in core, and we haven’t seen as much built on it, again, outside of what I would call the agency/enterprise usage of the API, which has been really super awesome.
All the things I had on slides and stage in previous years was all enterprise stuff. If there were to be an app built on, let’s say I’m making super press and I’m going to use the API to post to WordPress or whatever, I could have a plugin, and in fact there’s current API’s that would make it easier to install plugins, that would enable some authentication that would be right from my app, and it could be secret, it could be something like Oauth, it could be lots of other things.
I guess it’s a long way of saying that we are probably not going to work on it in 2018. It is not outside of the realm of possibilities and more, and more sites being on SSL does open up some things that weren’t previously there, but I just based on the usage, it doesn’t look like this is a huge need.
Something with the page builder, there’s 20 of them out there and some of them are really big and some of them are full companies, we know this is something that there is a huge need for. Plugins are often a good indicator for that. Based on the plugin use and plugins built on top of the REST API, like doing auth and everything like that, it doesn’t look like there’s a huge need for this in the community right now. It’s probably best for it to remain in plugin territory for enterprises and agencies and other people to use.
Matt: Thank you. All right, we’ll have the last couple.
SJ: Hi. I’m SJ, also from the UK.
Matt: UK representing on the questions.
SJ: Yeah, we are here in numbers. I’ve kind of buried my head in the sand with Gutenberg a little bit, and then coming to this, the presentation was great. Thank you. I was 90% scared, 10% excited before and now I’m 90% excited and 10% scared.
One of the things that scares me is when we look at how the block array is added into custom post types, which is brilliant. Users can still just add to that. If I’m creating sites for clients, I’m now giving them the onus on the design, whereas what would be great was a way to limit that so I can create blocks that are in a content, in a custom post type and then say, “And that’s it.” Is there going to be a way to do that?
Matt: Yeah, Matías is nodding. There will be a way to lock it down.
SJ: Okay, cool. Thank you.
Matt: Thank you. That was a quick one.
Ian: Hi. My name is Ian, from Jacksonville, Florida. As a front-end person, I look at the improvements to the Gutenberg editor and some of it is really exciting, but it seems like there’s inevitably going to be a few shortfall areas, for example determining visibility based on breakpoints or, say, typography that changes sizes, so you know your 80 pixel font is not 80 pixels on an iPhone or something, but then getting into just providing a billion options, that’s kind of a slippery slope too because now you just have this huge thing and you have to be opinionated in some places and not others. How do you guys envision you’re going to draw the line between this is something you need to customize, versus this is really something that you’re just going to have to figure out your own solution for, for front-end responsive styles?
Matt: That’s a tough one. We are probably going to err a little bit more on allowing people to do stuff, including perhaps mess it up, but give themes and plugins, the ability to bring in the guardrails even more. We’ll see. This is part of the reason that I think we’ll learn a lot, developing in 2018, the theme 2018.
For people outside of WordPress that we call the themes of the year is very confusing, they’re like, “Wait, you’re working on 2015, what’s going on?” I think we’ll learn a lot through that and that’s when we’ll probably get the most polish there, both by other themes adopting it and by our own usage particularly around the customization of Gutenberg.
Ian: Okay, thank you.
Maria: Hi, Matt. I’m Maria, from Lawrence, Kansas. I was hoping you could talk a little bit more about our philosophy of forcing a change on our WordPress customers as big as Gutenberg is, making them instead of opting in, having them download a plugin to disable that functionality knowing that we have so many themes and plugins yet to build any support in for Gutenberg in four months’ time. I’m wondering if you just talk a little bit more about that decision.
Matt: Well, we’ll have to figure out. Some of this is still to be determined. Today, there’s a completely opt in plugin, and we want to get that used more widely and widely and widely. There’s that kind of thread happening. At some point, and that also means that people can start to develop support for it in the plugins and themes. Plugins and themes can also update before then to say, like turn Gutenberg off, and then finally we are given this kind of explicit opt out that will turn it off even once it’s in core.
What we are trying to do is basically provide a gradual ramp on a few different axes to bring people along with it. Now, of course, it’s a big change and this is one of the things that I hoped we would learn from Gutenberg because we are going to need to make more big changes in the future.
To the extent where WordPress is still successful today, and when I look at other CMS’s that have stagnated, I’m talking about stagnating in growth but it’s because their user experience stagnated. We need a way to evolve that, and this is our latest best practice for how it is and where we are … This is the idea for how it’s going to happen, and of course we’ll tweak it as we go along to give the gradual ramp on’s to lots of different people, and there’s also a committee aspect to is as well; it’s the meetups, it’s the WordCamps, it’s the developer outreach, it’s everything that we are doing, the videos, it’s being online and tens of thousands of people watching it later.
All of this is going to be part of bringing the community along for what’s going to happen with Gutenberg, not unlike when a new iOS comes out or something; they present it first and some people watch the video and then blogs write articles about it, and it might be in the news. Hopefully we are not in the news with this update.
That would probably be a bad thing, based on how WordPress gets covered in the mainstream press, but I hope that with the efforts of everyone here that by the time that Gutenberg ships in core it will actually feel a little bit anti-climatic, because for many people the future was already there and now it’s just going to be the default.
Maria: I feel like there’s a little bit of a difference when you compare something to an iOS update, I opt into that versus right now we have automatic updates within WordPress and there’s a majority of WordPress customers out there that don’t follow along with the community, or even know that their theme is retired and that there’s no more support for that theme. I just have a little bit of concern that was echoed a lot in the usability tests we did in the last two days.
Matt: Yeah, and we don’t do automatic updates for major versions, and Gutenberg will come out in a major version. People, for those who don’t have it configured to auto update they’ll need to click a button for it. This is one of the struggles, and that’s why we are trying to provide all these different levers that people can customize and giving as much heads up as possible.
We first started talking about this in January, so by the time it comes out we’ll have been kind of beating this drum for well over a year and I think we’ll have reached … It doesn’t mean it’ll be perfect, but we’ll have made our best darn effort to reach as many people as possible and then be on hand to help folks who maybe are surprised.
We’ll definitely make sure that the forums are well attended therein then and we’ll maybe even open up a chat or something where people can ask questions. Whatever we can do to help people, we want to. That’s WordPress’s way.
Maria: Thank you.
Matt: Thank you. You’ve got the very, very, very last question.
Matt: Yeah, I was really worried about that too earlier in the year. As you all know, we announced we were going to move away from React and within a week Facebook changed … Took out their patent clause from the license, which allowed us … Which was really smart of them because WordPress didn’t say, “Okay, well, we’ve doing React for a while, there’s all this awesome stuff in React, 16 that we’ve built into Gutenberg that actually makes it more performance …” all these sorts of things.
All the licensing concerns that I and many others had were gone. Facebook could of course say that React 20 is going to add something bad back in, but the advantage is now that the GPL version is out there then we can branch from that point. It wasn’t like before where with the clause applied to every … It’s a much, much better situation than it was in the past, and we definitely would fork it if Facebook did anything like that and we would have a ton of support it turns out, because as you saw with the patents thing, it turns out most of the open web agrees with us for how this should be licensed. I imagine that we wouldn’t be alone, perhaps even existing React developers would move over.
That’s kind of the defacto. We still though want to do the bridges between some other frameworks and Gutenberg. That’s nothing to announce now, but you probably saw some of the chats in some of the demos that showed that you could write something or view and then compile it to Gutenberg or write something in a different framework and compile it to Gutenberg.
I don’t have any huge announcement there, but that’s kind of the defacto and the way we’ll probably continue. What I will say and what I hope you’ve learnt over the past 14 years of WordPress is that we take these principles very, very seriously. We will fight for them and we’ll stay true to them as long as we are alive and kicking, as long as I’m alive and kicking certainly. Don’t worry too much, and I’m looking forward to what’s coming.
Morton: Thanks kindly.
Matt: Thank you, and with that we are all done. Thank you all. Thank you.