 Thank you. As mentioned, I'm actually the designer of Goomba. We have two leads, we have a technical lead and a design lead for this project. I think I'm getting a bit of feedback on this, but it should be okay. So the Goomba journey starts with the editor. And it's been mentioned this is the current focus of WordPress and the code name for the project looking at the new publishing and also the content editing experience. And today I'm going to explore why that journey is needed and show where the path was going so far within that journey. And along the way I'm also going to show you kind of the foundations for this project. And I'll end up looking into the future because this journey doesn't end with writing. So all journeys start with a reason. A quest for a dragon, a mission to a far distant planet they all start with a why. And the why of this journey is actually more a series of whys. It begins with WordPress. So, imagine WordPress is actually a place. It's safe. Probably a kind of isolated place as well. A little like this, a nice saving, safe, cozy castle. Why should anything change? Because we're safe, things are nice here, everything is great. There is this sort of building and there's no need to upset that or change anything to it because change is hard, we're human. And it's scary that we don't mind change. Is that really the situation? Is the castle actually built? This is kind of what most of us assume it's like learning WordPress. After all, it's easy to add a plugin, right? You think that? We just turn it on and that's how you add a plugin. And it's incredibly simple to type something, calibrate and publish a post. We do that daily. And who on earth wouldn't understand this? It's just something that you know. If you use WordPress, you know these things. And we may have been recognised that a few themes and plugins have little learning bumps, but they're not curves. They're gentle little, under-hour learning. You can watch a video, watch a WordPress TV, anything and it's going to be fixed or just common sense because that's what you know with WordPress. This is actually the reality for most we're learning WordPress. It starts out with a good intention, but rapidly goes up and up and up and then confusion and then you have bits where you're just completely lost. And truly, knowing WordPress is a really, really long journey to get to that point. And most of this room, you've probably used WordPress for quite a while. That's the norm. And whilst we all have different paths, we are mostly really far removed from that starting point. And as a result, it's natural that we don't remember that as much. And WordPress to most new people is a trial they have to get over while we're all here sitting comfortably in order to use it. We bring our head space of bias to this because to us WordPress is easy. But that wasn't always the case. And even when WordPress has been learned, we have to recognise what isn't easy that we accept in a daily basis because it's WordPress, fundamental flaw in WordPress. And that comes in the phrase so many of us use and I would probably say that most of us have used this and it's the phrase, the WordPress way. It's expected that users understand this. It's expected that those creating learn the WordPress way, work around the WordPress way. It's expected that page builders have to jump through hoops to get even the simplest of things done because of this WordPress way. And the WordPress way has made us all obviously very clearly everything. It clouds. It's forced us to become limited and overgrown around us like a wood. And many of us create in this dense wood. We're working through and around the legacy trees and fallen around us. And should we cope? It is coping really the way to get beyond anyone or whatever it is today. It's open the way. I would argue it's not. So the word started out, just words. And text was the currency. It was just words. And as time moved on, the occasional, if you've been really fancy, very poor quality image that probably took longer to download than cooking a four-course meal. That's what you have on the web. But it was also a different way. It was a flat way. And the content was delivered simply. And people now want to publish rich content. It's something that's expected. We expect to be able to create that content wherever we are as well. We want to post photos on the move. We want to write bold posts during a trade line. We expect to really be engaged to not just simply read the words of text. And if we want that, we use an offline service to save that and to reduce that. So we have these options. The word has basically become an entertainment platform over one that just delivers straight text. This video shows Snowfall. And whilst it's a little overnapped as opposed, this is a story from New York Times. And this has been somewhat of a guiding light during creating Guilford. This story, and this video transcends the restrictions of just a post. I don't think you can just call this a post. It truly tells the story. It engages. It's a natural. Creating content rich like this should be really easy within WordPress. Straight before WordPress. And for WordPress to truly democratize publishing, it needs to reflect the needs of publishing in a chain of world. Your thought now is someone could use a plugin or a site builder to achieve what I am showing. To get that content rich experience. And yes, some combinations are going to get you pretty close to that. And it is fair, and we expect... But is it actually fair that we expect pretty early on people to find care, use, or care time? You actually saw a site that had less than two. It's not normal, right? And to that point, when was the last time you saw a site that actually had seven plugins that were doing the same thing? That's also normal. And most sites are held together with hope. Those tiers of plugins mesh together. But the same for next, I would say, is a game of Tetris. So if any of you have actually played Tetris for a while, you know how incredibly hard to manage it is as you get into those later levels. Because as flowy after flowy a blocks happens and showers down, this is actually someone who feels most people's experience of WordPress. They are just coping. Everyone's situation actually blocks and holds back innovation. Anything done has to be done within the strict, relentless boundaries of WordPress. And agencies are held back. And they create amazing work. And everybody creates amazing work, but we're not creating what we possibly could and are not here. And those that create content are limited. And those creating products have to find hacks around the blockade. This wasn't the intent, but it's what happens to all software and all products after a while. At some point, you have to rethink and an evaluation. And for a while, WordPress stood unchallenged. A little like maybe a surviving single planet in a system. But that web was changing because new planets are being discovered and we aren't alone in this universe anymore. There are real challenges to the position of WordPress. And this has to be recognized and responded to. It's no longer the only or most obvious choice to have a WordPress site. Co-working spaces are no longer just filled with people using WordPress. Take a look around if you're ever in one. And you will see that many are using different apps on such as Squarespace, potentially. Designers and developers are writing blog posts on Medium, choosing it over their own blogs. A week's immediately to name a few. Kind of inviting at the heels of WordPress and what they're offering. And whilst most are hosted bid, that's always the comment when you think, like, oh, it's hosted, it's not self-hosted. But they are all orbiting and pulling in users from what was once the WordPress and the only space that WordPress commanding. People don't want the hassle that caring for their own WordPress is. And who even has any time for that anymore? People don't have time for that. And we have to recognize that and come up with really creative and opening solutions. Without a change, the future WordPress is pretty uncertain. We have to face that fact. Whilst right now, it kind of might feel a bit bleak. The talk's taken a bit of a turn. What I really want to show is there's a project we need to do that change. And that's where Google comes in. In itself, this project isn't going to save WordPress. It's not a super heroine or a miracle cure. It is a start, though. And it's a step in the right direction to making and shifting WordPress into the future and into relevance. So all journeys to Google has been no different. I want to share some of the foundations of Google. And these great cruise and output work that's being done, you can see them in the patterns of interactions and in the way the project has shaped. I'll also note that I'm not going to get into the technical foundations here. There's lots of really interesting talks throughout the next two days that are going to teach how to build a block and teach you different aspects. This really is going to look like a handout and really those kind of topics. So everything starts with blocks. These are the essence. So thinking in blocks and patterns, that isn't new. If you think about what you ever learned are, you break down the complex shapes into similar shapes and then build them up. That's the way that our brains work as humans. And in digital experiences, components really aren't new either. Because humans are amazing pattern-recognizing machines. It's in our brains, it's just part of us. And the layers may change, but the principles are really the same. You just go down to the smallest group and the smallest element and then you build up. If everything is a block, from that point you can then combine blocks to get this incredibly rich content. And blocks have a few advantages. One of them is they isolate errors. So block by block HTML editing or errors serve as a barrier when breaking the entire post. You can just edit that block and you're all going to have that problem across the whole post. Just that block will stop working. And you'll get a message and you'll be able to deal with that there. The block is a boundary, a safe container for content. And they also, in blocks, allow for quick understanding. A foundation principle in Gutenberg is once you learn how to use the block, you understand how to use all the blocks. And blocks also allow for a lot of drop-in functionality, not just the core ones that come with it. The potential is really only just being touched as to what is actually new. These are an essential part of the new editing of the series. These indicate what a block is going to contain and also have a few different states. Each state guides you through the interaction. So here, on the first loading, you get this call to add an image and really kind of engage and you know what the content is. Placeholders can also be interacted with. The image block has an image you can resize right there and there. The gallery block, for example, has a way you can click in and add captions. And these states are something you could take advantage of potentially in a template and also these placeholders. Imagine a template uploading showing just placeholders. Well, that's a lot better than what happens now with templating because it's an empty giant box that you input in and you have no concept of what that's going to look like on the front. And it's a confusing experience and this is part of what we can achieve with Uber, we can reduce those confusions. And placeholders really progress us to that more what you see is what you get now. Another principle that we thread through is that of direct manipulation. What is direct manipulation? Well, in simple terms, you need something and you can interact with it and see why there's a change. So there's no way, there's no pause, you change it, you see it. And this is born interface interaction we actually expect now. That we kind of demand it from interaction. We're so used to seeing this from the apps to the browser web. And touch devices have trained us to get this sort of direct feedback and you just expect to have that. Here you can see direct manipulation in Google Work. You can make the change and then it reflects it right there in the block even with a secondary action like this. And seeing the change is so crucial as your engagements are creating that content you know what you're doing. And now you can have this. Talking about news-based options, I'm going to talk about eating soup first of all. Because if you want to eat soup, you probably just want to spoon, right? You don't want to have a utensil with every single possibility that was. That's probably not going to work. And imagine the sheer size of that utensil. It's not really going to function right for that. And our brains on built have everything surface because we freeze. That's just the way we work. And likewise, we're also not built to have to search endlessly for something. We grow impatient and reject an experience fast if we've had to work way too hard for it. And frustration leads to a broken experience. And that's when we have a trust problem. And nobody wants to ever use anything that destroys the trust of experience. Being able to have just what you want when you need it without hunting for options or being overwhelmed is something that Google Work is really trying to achieve. And there's a few ways that this happens. The biggest one is through primary and secondary actions results. Primary actions are here beside the block. They are the most tasks. The things are blocked and can't function without the expected options for a lot of people or what they would expect to have there. And they are right there when they need it. But unlike the kitchen sink options, they aren't going to be so many that they overwhelm. Just enough. And the secondary actions are in the sidebar. And these are reached by a key interaction element which can even be the more menu or the setting to blocks. And we bring in some outside application here for the ellipsis menu. You know, those little icons that you see which kind of make more content being extra. Things are okay to discover as they aren't essential to the usage of the block. Now for styling extras, I've seen here in the paragraph block. By following a needs-based approach to options, the person creating the content feels more in control. And by having the secondary actions, exploration can happen now. There's actually a kind of proof and record that if people have safe exploration, that's actually a key to interaction delight. So just enough finding something and having that delight and discovering for those new options really makes absolutely sense. Experience covers an awful lot of things. However, it's a foundation consideration in Google Work. From the actual interface to the performance, the delight, the copy, so many things make up what someone is going to experience and make up the experience of Google Work itself. And improving this, making a better experience than the one in WordPress now. That's all at the core of the work really that has gone into this project. WordPress right now, as I've said, is people coping just using it. And with the new editor, this can begin to change and we can start moving on the path to people climbing and really growing with the experience. Accessibility is a foundation to good experience. Not just for those you may think that you did either. An accessible experience is better for everybody. And Google has had some incredible work done along the way and it continues to be done. The accessibility team has just been incredible with this project. They have taught and they have guided those of us that are creating it. Google brings some new accessibility features like this one which I really like that checks the color combination. These little nudges are something that we can build in and then expand across WordPress. They are a way to guide everyone to make a more accessible experience and they are really helpful in that. They educate as part of that. It is a WordPress. But within Google there is an attempt to respond to this with some of the tips so that first experience can really be responded to. What this does is a little welcome guide that right now just takes you through the first few steps done in the editor. And this is the time to expand a little bit more to give more of those nudges the guides along the way to help you really level up when you are using the experience. And over time perhaps this could also expand to get really as towards more conversational interface between WordPress. The editor itself and WordPress itself has to work well across any device. Now we often think of just the visual and we say mobile when we are talking about this. The truth is that all manner of different devices can be used in different situations, mobile or not. And whilst for some things an app is always going to be the right choice, having it work well, better than the current WordPress editing that is on the smaller screen is really an essential part of the project. And it's also worth noting as you move into thinking about mobile this is where performance really, really matters. If a site takes too long to load it's pretty useless on a mobile device. That's primarily because of data plans but also because of sheer frustration using it. That's worse than talking about an experience which has been lost. Nobody likes loading high costs. So WordPress is built on backwards compatibility. And anything built has to really respect past, it also has to respect things like blocks giving plugins or things that someone really isn't using anymore. These graceful fallbacks and checks are built into Bloomberg and have been typed in and added more and more. Along with that we really need to respect the changes you make in custom editing HTML and if all else fails and something doesn't actually go wrong offer those good default options like maybe becoming a classic blog that's the editor that we have on WordPress now in a blog format. The new experience also adds and really builds on the existing principles within WordPress. There's a recognising of the publishing flow, what way to tag and categorise. Patterns from the older editor exist also within good work like the toolbar, the site bar and many other interactions. There is a progression from what we have currently. Ugly one of the survivor traits of WordPress is the way that it can be extended. Plugin for that you can do this and customise everything. By code you might do it or as I say by just talking about the theme WordPress can be moulded to be the experience that anyone wants it to be and that's a credit to it. Google is going to be no different. You can at the low level just add blogs but beyond that there are so many different ways that you can extend. Plugins can do this and custom code experiences just for single cases and client experiences. Extensibility opens up a whole new world within Google of creating these easier to have more app-like experiences because of WordPress so you're actually having it like that it's not like it's a separate thing it's more part of the interface and it's going to be really exciting how this is explored. I said why the journey is needed and I've also shown what is in the Google it's been on and this all starts with the phases. So there are three phases or focuses and let's take a look at each of these. So the editor is the first one and that's the one we're in right now today and whilst this is focusing on editing the groundwork has been set for the next phases in the first. This is the reason it's going to take longer and it has taken longer to this point because we've been really setting that foundation for going forward. The next one is going to be customization. This is where the more page-building aspects are going to happen and while we're then really having a hard stop in between phases the next one is going to transition that's why I actually like the term phases and what focuses because it kind of gives that feeling that we're going to be having and it's just kind of progressing through and we're going to be really having that overlap towards the end of phase one which is what we're entering. And like this is potentially going to be by looking at 10 by 3 and that's one area of WordPress that is powerful but problematic which is so many people when they first come across it. The last phase is a lot of things. This will involve potentially taking the work in past two phases maybe creating a theme that showcases that it's kind of undetermined what this will be but that's quite likely. It's going to be a really exciting time to see as these phases change the next one's coming and that kind of influence how. So whilst that's on the GitHub repo really only show a particular view of what has happened so far the sheer number of issues and poor, quite close is really incredible within Google. I actually love this bottom graph showing the commit activity a year ago just kind of you can see these kind of flowings of work. This is actually just the number and there were released versions before Goomba 1.0 was reached on August the 20th 2017. This project started a long time before that it was worth coming over to GitHub repo as it is now. The team throughout each kind of phase of this and the project have been meeting each week in the co-editor on the WordPress Slack and released by release already. Features have been added and the numbers rolled around into the high ones and then into the twos. And so many people that have contributed to this project this is going to be quite a props list when Goomba actually is released and WordPress 5.0 goes out. There have been more or less a release every few weeks sometimes every week for over a year and this is told over 30 releases and counting so many releases happen you know what happened just yesterday so we kind of have to be careful about the numbers here so 30 plus I thought I was going to be safe with this slide. On July the 6th 2018 3.2 was reached and the project has reached feature complete. This means for the minimum things wanted to get into version 1 are there. This is quite the monster and we continue to meet in Slack each week. The conversations have grown and those contributing have grown significantly in numbers. Today as a project the focus is on bug fixing iterating and responding to feedback as the project rounds that final corner. As I said we went on and get her and in many ways this has allowed new contributors to dive in and be involved. Both designers and developers have been open to issues and weekly meeting discussions. Teams all across the WordPress project have also joined the journey. Advising and really contributing. It's not just people contributing to the code base itself though. Many people have taken this opportunity for experimentation. They have used it both and as a result also given feedback in ways that have shaped the direction of the project. Really those agencies and freelancers who have become the adopters have made the product what it is today through that information back. I'd like to share a few examples of things. Atomic blocks is a great example I think of exploring what things or blocks could mean together. This is a theme but also a suite of blocks in a plugin. This is a really interesting approach and it's one that I'd like to see of as exploring. The atomic theme is actually available now I think on the WordPress theme group. I'd encourage you to check me out. It's a really good example of a theme that responds to do the work. As more people explore what things and plugins mean in a good look world having tools around to jump in and use is going to be really important. This is a part of this and this post I'd encourage you to check out because it's a really great example of just exploring what kind of things look like and this will actually allow for a massive new creation of Google Chrome and there's that kind of a locking of through blocks. Feedback has been at the heart of the project shaping and molding through that new creation. Throughout the entire life of the product so far feedback has been listened to and responded to from many, many different resources. Daily reviews have been given feedback, usability tests, blog posts, issues. The feedback has been for so many different places as well. From universities through to a usability testing booth of WorkCamp UX every single person that has given any tiny little bit of feedback has helped make the product what it is today. Regarding the feedback I wanted to call out just one of the many awesome blog posts about usability testing done in the community. So James and Tena ran some great usability tests and wrote a really detailed post going through the feedback. If we post like this the product has a continuous need to be shaped. So keep your feedback coming and at the end I'm going to give a link so you can kind of get some more resources and find out how you can give back feedback. There's been quite a journey in two phases then and after that. For what lies ahead where do we go now? This is what the roadmap roughly looks like. The next stage is opening up the experience to many more people and this will be done likely in 4.98 with the tribe group that will call out. This encourages people to discover it if you haven't before. And it also has a little bit of information so if someone doesn't want to do that they can install the classic editor plugin. So they have that option. That call out, a period of feedback and iteration is going to be entered. This is where all the wider feedback and then kind of gets more and more people exploring it is going to be processed and iterated. Bugs are going to be fixed stress cases are going to be served, flows are going to be smoothed and it's going to be a hectic time. It's needed to make sure that on entering the next stage the best possible editor is really going to emerge. A point is going to be reached when it's ready to get into the call and this may be the start of WebEx Franklin app. Just like any release this one will have a timeline it will have leads and it will also be done in public with posts and processes just the same as before. Like these are a lot of beta releases to really ground this in and get that feedback leading all the way up to the release time. The big milestone after all of this is 5.0 but this is just the start of the journey as then the next phases are really going to be in full focus and so this is all expected to happen within the next few months. In that days though are going to be variable as you can likely understand and listen to that feedback and let that guide us where we respond. So that's a lot coming up. It's going to be a busy time for everyone involved in WebEx but I hope and I think and excited for too. And it's been quite a journey to get in but what about the future? I've outlined the phases but what exactly could lie ahead? So I'm actually going to take a little bit of the end of this talk about the personal views here and these are things that I think they're not facts necessarily but these are what I think that could be and maybe could should be the future journey of WordPress and I'm saying that because it wouldn't really be Googlebird at that point it's going to simply be WordPress. The future here is the future of WordPress because Googlebird is just a project name. So I think the theme the phrase if you don't know there's elephant in the room there's giant elephant in the room because that's kind of weird to do. There is no excuse for things to have everything in them and my own feelings are that we're likely to be being shipped more into being like Starlight and that's something that a lot of agencies and a lot of people are creating no views and maybe they become configuration files with those but nothing really more. Things always were best when supported not overwhelming content and I see them really moving back to that supporting role a whole lot more as we progress. The customized editor where they end is going to blur it ends up being there's yet to be seen and those who are going to be leading the customization phase are going to be guiding that. I've mentioned before that direct manipulation is kind of important and expected because it's getting more and more pulled up throughout the whole of WordPress. Things are probably going to provide boundaries but the ultimate content art direction is going to be in the hands of those creating it and of course just like anything in WordPress user models can be used to boundary this and really prevent people from just making a box. Really anyone should be able to create beautiful posts and beautiful content. How those taste boundaries are set up is going to be quite a challenge to work out but it's a really great one and exciting one to design around. How we enable people to take what they have in their mind and actually create that and make that with WordPress and really create that content at the next level. WordPress has to become more welcoming. It needs a new user experience. It needs things like tips to be expanded out from the editor. That's my own personal feeling and this type of conversational interface is something people expect. It's no longer okay for someone to read an article or watch a tutorial to have to use something. The interface should at least allow someone to take their first steps and be inviting about that. And this experience really needs that helpful personality not to overwhelm and feel exclusionary like you have to be in the know to be able to use this. I think Google mode in the copy has actually been something focused on and as a project WordPress really has to step up its use of copy and it's using this kind of text to interact with people. And as a project we have to not retreat back into the bubble I mentioned earlier. We have to isolate it. There are other planets that have been discovered and we aren't going to undiscover them. The reality is those products doing the same or better are only going to get more and more. They're only going to grow in what they do. This is good because this is a challenge to be answered. And being mindful of this is really the key to progressing. This is going to get us where we should have been through Google probably a few years ago. It's where we go from here that really decides the fate of WordPress. This is a product that has to be the right tool for the right time. This means kind of a lot of different things. From being the most accessible it can be through performing well no matter where or what or what you're doing to access it. And this is the base requirement for any experience today and it's just going to grow from now on. And likewise continue to refine research and listening to those that are using it. Surfacing the right action at the right time can lead to fine. And this is not just people that are developing for it. It's people that are using it in all the different capacities. Anyone that does anything different or anything with WordPress needs to be listened to. A truly adaptive experience is one that works kind of how you need it in particular time. That's what we were required from it. And WordPress has its roots in adaptions and platform that mould it and get it to extend it and do anything you want. And this needs to be built on because this is a great quality. So as you can see it's been quite back to any from the first commit up until today. There's a little bit to go in this first part of the quest but the end of this chapter is kind of close. And WordPress really needs this project. Without it the future as I said probably isn't that right. So many amazing people have come together and this is the nature of WordPress because these people have trapped me along my Google journey. I'd like to say thank you to everyone that so far done that and invite anyone here to really come and join that journey and help get this chapter written. So here are my slides and also there's this link. This is from another talk I gave and you can kind of follow the information. And I think I should have some time for some questions. If you say your question because it's going to be different based on the different page builders. So work has been done talking to different page builders. So it's going to be dependent on which one you have. There's some exciting explorations that have already happened within that. But they're going to be exploring now. Any more questions? I'm going to try and repeat that question because you haven't gone like that. Correct me if I'm wrong. Sometimes I break words. So you're asking how to concurrent creators when you give feedback better. Write a blog post which is something that content creators like is great because that blog post can give information as you saw the server going into the core test channel and a support editor channel and say hey, there's this within the Google plug-in there's a feedback form. That's also a great deal. So all these different ways are just great. If there's something you're like oh, he did this and we can kind of have that discussion I know that that sometimes is not as comfortable a thing for someone to kind of say go on GitHub and make an issue that's not necessary but if you're in the stock already on WordPress.org come into the channel and someone will be through and happily make that issue for you and then kind of loop you with that discussion as well for the blog post. Also different ways and please give that feedback because as I said it's not just one particular type of person that we need this feedback from we need anyone that does anything with WordPress needs to be kind of giving those insights and they're valuable. Next question. They're going to be a specific theme for Google extra things that so there's the technical term that themes support so that extras that themes can do within Google. Those are things like a bigger image and colour palettes. So most things should work. I'm just saying test your theme Google is kind of and if it doesn't report that because that's absolutely the kind of information we need as a project to know where that is. My kind of conversation about themes is when I'm looking to the future and seeing quite a way ahead past the phases, past 5.0 as having a bit of a dreamy moment and thinking what things could be there. So I do want to kind of give that course information there but you will not need a specific theme. There will be things and there already are theme expressions. I think later today there's a toll specifically on Google what Google has been in company and the exploration of that so I encourage you to go with a listen to that. Possibilities are being explored now. As you see, atomic blocks is already in the dot all repository for theme. There's really just a case of these things bring extra stuff with Google but you don't need to have that today to do that but I think I heard you. Will Google become the WordPress page builder? So Google is the code name for their content editing experience. The site builder page builder people interchange those words aspects of it is when you bring customization and layout and all that kind of extra to it. What Google currently is is the editor, that's simply there is extra functionality something that's going to be explored in the customization focus. How much those go is undetermined yet but site builders and page builders are really exploring what they can use and build on top of Google work. So what they're seeing as is I've kind of mentioned a lot of people have to work around WordPress at the moment to achieve this because WordPress gets in the way of it and they will not have that so they're saying it's going to be incredible the experiences that people are going to create from this and I'm personally excited about that I'm focusing on shipping the product but I'm really excited when I'm not shipping the product and what people take and run with this because that's the WordPress way and particularly it's incredible, very different probably experiences. So your favorite page builder will boost that they can kind of do different things with. They're going to explore in different ways like do they take over the whole screen or do they come into the block lots of different explorations are happening now so if you have a particular page builder that you kind of follow and use all the time I would encourage you to kind of see what their plans are, lots of them are running in a blog post and exploring that. So do you mean there is a way that you can are you talking about you being able specifically in that? Okay there's a thing and you can just do that exactly within Googlebot there. There's also an advantage with Googlebot you can do that per block which is kind of handy that's the thing and you're like well I don't want to write my posts normally that's with text and then I actually want to go specifically into this HTML just one block you can do that the functionality of WordPress is still there within Googlebot in slightly different places potentially to something. Think what to say. You've got to pay so editor now good for the classic editor that you used a little bit for what happens back then. I'm repeating it so that because it's new video I'm not a part should respect that you've done something already with your content a WordPress should respect that whenever I write. So there's a few options that you have one if you've done something really really custom you have the classic editor plug in you would have that. Majority of pages and this is something the project will cover. They will either become just like the normal page but that's not a word. There's actually a classic editor block so that could be something that they do so you find that you have an editor in an editor. That is something during the feedback yes we need to know and why this try doing but it is great to know like if you did this and if you turned it on and then turned it off what happens. So all these different variables we need to do to really respect the content in the dashboard that's going to say hey there's this thing coming you can install this plug in and you click to then get the plug in or you can install the classic editor plug in so you have these options because of WordPress making sure that people know that option and can make that choice. So not everybody is going to do that it's kind of an early adopted thing if you click that you'd be like hey I want to try this and I want to give feedback but to get to that point we're going to a place where we're really confident that turning on and off Google Bird will not have that problem we'll have those fallbacks so that's why at this point before we get there giving the feedback is really really important about what happens for people's content but you have so many different fallbacks so you have like that and I think we have a filtration system then you can kind of go through to make sure that we can catch all that content. More questions I think I'm not sure if I have time for more questions one more question does anyone have one more question I don't think we have one more question we do have if you use the plug in today and then if I've got O happen I don't know if it was in there if there would be any problems be sure that that doesn't happen because that's going to be really likely and those people that have been amazing and given us 30 feedback that's going to be on my sites as well where I put POOM work on and then 5.0 happens so making sure that we have that that's the people who are awesome they were early tested and they were early adopters here and then 25.0 happens