 Ciao a tutti e benvenuti a la seconda parte del nostro walk-in e adesso abbiamo con noi l'amico Amor Tios che ci parerà della nuova via, una vita di good and bad, di good and bad. Benvenuti a la seconda parte del nostro walk-in e adesso abbiamo l'amico Amor Tios che ci parerà della nuova via e ci parerà della nuova via di good and bad. Per esplorare l'amico Amor Tios e quello che sta andando a dire per il lavoro, è solo il meglio di iniziarlo immediatamente con il demo, quindi questo è tutto. Allora, cosa faccio quando sto parlando di Loomba e questo è, penso, l'unico tempo che ho fatto di parlare di questo, è che ho iniziato a prendere un po' del classico, perché sappiamo questo e siamo riusciti a lavorare. E mi piace prendere il tempo per apprezzare per un secondo per quello che fa, perché quello che abbiamo qui è un po' limitato, ma non ha lavorato molto molto bene e ha fatto questo per 14 anni. Allora, quello che abbiamo è solo un content editor, che sembra molto molto come qualcosa di Microsoft o un text editor, e che ti aiuta a scrivere content in modo che puoi vedere cosa che si sembra. Ci sono molte sensibilità e possibilità, ma quello che hai visto è che ho installato un plugin qui, che ha extra features. Allora, per il tempo che hai visto, hai un'altra cosa che puoi fare qui. Ho un plugin di gallery e puoi inserire il gallery in questa posizione. Ho aggiunto un plugin di subtitolo, che puoi aggiungere un subtitolo qui. You have the manuals with Yoast SEO, you have some information here about the state of your content. It's quite a powerful tool. Please come in, take a seat, participate, ask questions, you're welcome. So this is really nice and now let's take a look at what this is going to look like in Gutenberg. So let's say Gutenberg comes, it comes part of a WordPress where despite the lowest release. And it includes Gutenberg, what are you going to see in your screen? This is what you're going to see in your screen. And it's quite, it looks really beautiful, if you ask me. But it's scary because, you know, where is the subtitle? Where is that thing to have extra options? Where's my text editor? Where is my Yoast status? Where is the button to insert the gallery? The reason I started with this is to show you that this is really a significant change. And whenever Gutenberg ships with WordPress, it's going to impact everyone. And it depends on if you have a lot of integrations in the editor or not. But this is definitely something that you need to prepare for. Like you know, you need to prepare for, you need to prepare for everyone. And users need to be prepared for this. Because this is short. But there's a good reason that we're doing this. Because the previous editor that just showed you has a lot of short points. Who here knows page builders that use the page builder? And it's like, usually it's most people. These things are immensely popular. So just being able to add content often is not good enough. If you want to build pages. We have visual composure. And we have elements. And we have what's your code? And call it bridge. And we have deeper build. You know the page builder. And they have millions of users. What does this tell us? It tells us that WordPress is such a good platform for website creation. So we need to improve it. And then we see the rise of platforms like Squarespace, Wix. And other really intuitive website builders. That have become very popular. And become easier solutions to create a website for many people. So this also tells us we need to improve the WordPress experience. In Gutenberg and the new editor is the first step towards that. So, from an editor perspective. Plus change. It's still out of title. It's going to be hard to talk with one hand. I can still add content. It's going to be really intuitive to add an image. Cannot add an image here. Maybe I want to turn it into a gallery. I can do that in your house. It doesn't work entirely as a script. And I can configure a gallery to... Ok, this doesn't work as a script at all. Let me just add a couple of things at a time. A gallery here. And I can customize how many homes there are. And then I can just publish it. And what you saw there was a big workflow change. I'll show it to you again later. So I've configured here what it looks like. And then when I queue the process, I see here... It just works like you're used to. So we still have a good content editor, but it's become a little bit more intuitive. I have here elements like a blog switcher. I can just choose a blog that I want to add. And basically all the functions are reimbared up. That you're used to from the old editor. But it's become much more composable. And this, in itself, might not be revolutionary. I mean, you can still add a component, right? But as a platform for a future ecosystem with plugins and building new experience on top of this, it becomes really interesting. One thing, for instance, that I'm quite enthusiastic about is the possibility to reuse something. So what I can do here is I can convert a blog to a shared blog. I give it a name. And then I just add a new post somewhere to add that same gallery again. Just add it from the shared, from the saved blog. So let me repeat that accent and see what just happened. I want to add that saved blog. I go here to the shared blog. I create a gallery. And I just include it into my post. And this is another. Let me publish it for a second. Like something that's going to be possible is improved workflows. The one thing that we might do here is you see when you click the publish button, you don't publish immediately. You can ask me some questions. And this is really useful. For instance, maybe I haven't optimized or maybe I haven't set a metadata for Google. Or maybe you want to publish your content straight away to Facebook. You can create integrations here that just add a checkbox or add a warning, like hey, you still have to do your Google metadata and then before you do that then you can publish. And you see here also this is called the pre-published workflow. What we also see here immediately is that there is a post-published workflow. So something like posting to social media is something that could be included in the post-published workflow. This asks a lot of content management possibilities that improves workflows. We were talking about this thing before. This is a shared blog. Let me change this blog. Let me just take away this image. Save it. And then we go to that other post. And here we see this shared blog was updated here as well. So we can have pieces of content and information on our website that is shared amongst different places. And when you think about this who needs a metadata box for a testimonial that you can have a testimonial blog which you can just save. We need a testimonial plugin. Or maybe you have a testimonial plugin that just adds some slide into a testimonial blog. Who needs? Or maybe it's a useful plugin. Interior who needs a forms plugin which you can just have a form blog which you can configure and save and make sure it's data gets saved to some place. Things become so much simpler. The thing you see that what you see is what you get experience that Gutenberg offers is extremely powerful. And once we build on top of this platform you get a much better user experience. So now we go to a custom post slide. You configure a form that's complex you don't know exactly what it's going to look like. In the future we're going to add this form, configure it and see what it looks like. It's a much better experience. Another big change here is that everything is dynamic. Everything you see is real-time. I can maybe show you this. You see? Anything I customize I see immediately the feedback and the editor what it's going to do. Some presets and enable drop cap. It doesn't look like anything. When this works it's a much better user experience. And that also means that integration with the editor for any plugin anything anything that any page builder is going to be much more contextual. It's going to be much more possibilities of making a better content writing experience. I'm going to show you some examples of that. Based on this demo anything you want to see me try you want to see me do because I'm going back to the slides now. Because, as I said Gutenberg is going to offer a lot of new possibilities. And one thing that we are thinking about it just, like you know, right? Just is very deeply integrated into the content. So we have a content analysis still that constantly analyzes the content on the side and gives you instant feedback. We have many kinds of integration. We have in premium you have a general linking suggestion on the side, it shows you possible other articles on the side that you can link to. So we are thinking about how can we make Gutenberg more powerful to give inline feedback. And this is going to be probably one of our most beautiful contributions to the Gutenberg project. It's not finished. It's now only concept. It's a mockup. But the kind of thing that you can do in this new editor is just have collaborative features like this. You can comment. You can select a piece of text, you can comment on it. You can accept or reject the comment. You can have a discussion about it. It's like a conversation in the content editor itself. And when you are on that website and you are working with multiple people and you have maybe content writers and then you have content editors you don't need to do that whole process in Google Docs anymore. You can just do it in WordPress. And it's going to be a nice and clean intuitive experience. But what you can also use this kind of thing for is we can add an API which allows you to yeah. How do we do this? So this doesn't, if it's not in Gutenberg yet, this is an idea we're building this. So the first thing we're building is that you can highlight pieces of text. The second thing we're building is that you can comment. And then when you have you'll have like a button here I think here on the top you see that button to add a comment. But you can also of course automate that process. So you can maybe have a bot or a plugin automatically create a comment. So when you have here the first paragraph of your text, and you forget for instance the focus keyword in Yoast SEO you can put a comment here with the Yoast logo saying you should put the focus keyword here. Something like that. So the question is where would you like to save conversation information? The idea is that WordPress already has comments. So you want to add a comment type and you can just store all comments as a comment in WordPress like regular comments on the front end of the page. It's exactly the same kind of conversation. Why I give this example because it's a very powerful example of how Gutenberg can become a powerhouse can become a much better tool for content creation than the current WordPress editor. And plugins can utilize it for instance to give contextual feedback based on SEO copywriting or readability checks or maybe we can do suggestions for internal linking that is on the blog level itself. So we can just analyze the blog say well according to our analysis this blog is about this word, this information. We found other posts on your site that relate to that maybe you can link to them. So we give a list of links and we show you the words and it will be very easy and intuitive to link within your websites. All this kind of powerful intelligent kind of functionality can be built on top of the system like this. Another thing that we are probably gonna be have ready in the summer before we come here is a sidebar. We also have been very worried about how our plugins are going to integrate with Gutenberg. So we have contributed a great deal to the Gutenberg project with a lot of our developers and designers. One thing that we made available for everyone in collaboration with the Gutenberg team is the possibility to add a sidebar You can have there is a menu here you can have a drop down you can have your plugin listed in there I don't have a lot of that. You can even pin your plugin logo to the toolbar here and then you can just activate your own sidebar and then so WordPress becomes a very clean content writing tool and when you want to focus on SEO you just enable here the SEO mode and you get all the feedback from this. Because this is a big change for people we will keep having the metabox down below like I just showed you in the demo I think besides and will initially create a system that you can just eject it from the metabox and put it here because we think this is a better experience because you'll see on the right exactly feedback on what you're doing here I don't mean can create a sidebar like that we've added the APIs for that to Gutenberg itself there's documentation starting today actually a month ago anyone can add a sidebar if you're an agency and you're building a project for a customer you can also create a sidebar for that customer if you have metadata that you want to edit that you normally do in a metabox in the line of the content but you're actually on the side editing metadata that is about the content so the whole experience becomes better and it's relatively easy once you get the hang of it to do it other example of a recent example I think Andrea also showed it that was done by WooCommerce you can of course create your own custom blocks so basically what I said earlier any kind of piece of metadata anything you would use a custom field for something like t-shirt size or color or thing can all be a block setting we can just have it represented what you see is what you get fashion and you see what's gonna be published so this is really a major possible pretty much done you see you can make all kinds of customization things going on I'm gonna skip to the next slide because I started basically by showing you that a lot of things might break these were the examples these things for instance we have a maps plug we have a local SEO plugin and what this does it gives you an address code and a map and opening hours and store locator all that kind of stuff this is not gonna work anymore but what will and what makes much more sense lots so these things will still be insertable but through the block insertor you have to do work to make it happen but if you do so becomes a much better experience we'll no longer have these buttons in the Gutenberg editor but we'll just have blocks this functionality the advanced time emcee functionality is still available in Gutenberg on the classic editor block thank you it's not available on other blocks something like a subtitle it's a very good example something that should be a block because actually the title thing is also a block in Gutenberg it's a block that sticks to the top so you cannot move it but it looks the same it behaves the same as its own settings it also has a sidebar where things can be configured but you need to be aware that things might break ok, so what is the current status there's a lot of pressure in the worker's community to get this thing merged there are quite some reasons for that one is I think probably the most important reason is that right now WordPress core development is pretty much a standstill nothing is moving no one dares to commit anything that's not Gutenberg related this is really bad for the community so there is some pressure to get this thing out so we can start working on the other stuff again it's pretty bad reason probably but I think this is a social dynamic that we should be aware of because there might be some emotional pressure also that makes this land sooner than later and you just have to be aware that either Andrea ricefully says this might take another year or two but this might also take another week or two but really it could be merge proposal could land before work in Europe which is in six weeks maybe doesn't you see here that there is still a lot of work to be done so what the Gutenberg team considers the status is what they have listed here in all the milestones that they have so the accessibility still has 10 open issues there are many more accessibility issues than 10 but these are the 10 that are listed for merge proposal backwards compatibility still has quite some open issues rest API issues there's still quite some open issues so this is not gonna land tomorrow probably but we're working at a really fast pace and we're working really hard to get this in as fast as we can issues that have been around for a long time and are still around to some extent are extensibility so how easy is it for a plugin to integrate with this thing accessibility rest API issues because everything in Gutenberg is done in JavaScript so everything is done in the browser all the data is fetched from the server the page is no longer rendered in the server so it was just a form that was rendered in the server now it's completely dynamic JavaScript application that saves that of the server and gets data from the server and there's a lot of rest API implications so we need a rest API for that and not all of the endpoints are working as it should be not all of the data processing is working as it should be so that's something that has a big change in at the moment a lot of effort has gone to usability but I think we still need much more testing and backwards compatibility plugin compatibility well after what I just showed you it must be clear that this is still an issue and we might not solve it entirely so let me go a little bit deeper into those different areas in terms of accessibility a lot has happened since like a year ago we now have we've had for some time a block API so you can create your own custom blocks you can have settings with them you can install them all that kind of stuff you can add theme most of this stuff I think we also have a plugin API now you can register a plugin you can register components for sidebar for instance so you can render your own sidebar you can render your own models on top of the of the editor with settings you can have your plugin listed in that top right menu there's quite some stuff that's now possible with the plugin API we have a data API for developers this is especially relevant there's a lot like everything in Gutenberg everything in the editor is represented in data is a representation of some kind of data state this data is now fully observable so whatever the state application is you can observe it and there's documentation on how you can do that I'll point you to that documentation in a second and you can also to some extent you can also register your own data store and you can make your own data so Yoast will have its own data store in the browser everyone will be able to access it so this means integrating with Yoast SEO or any other plugin that uses this API will be much more powerful much easier, much more stable it's a pretty technical thing to talk about but I have to name it and you can also to some extent manipulate the data of the editor as a whole or even Yoast data and then there is something that's familiar to most of you there are there's a hooks API that was released a couple of months ago that is also being used in Gutenberg and it works like here used from the PHP we have actions and filters this is what we have right now we need some more UI accessibility features we need some more possibilities for plugins to integrate into the UI of the new editor this is all generic work so whatever we build after this we'll have all the tools necessary to make it accessible and to make it nice for plugins to play with and this was a really big problem in front current state of accessibility accessibility has been a major pain point from the start that's because the way this project has gone has been a lot of experimentation and if you have to think about all kinds of production concerns when you're experimenting that takes a lot of energy so they decided not to invest in that we're now paying the price the keyboard it's still hard to use Gutenberg with keyboard only I can show you a little example of that mobile there are still a few issues left I don't know anyone has an iPhone here if you have an iPhone you select text in Gutenberg you get a toolbar above the block but you also get a toolbar from the iPhone copy, paste, all that kind of stuff it's on top of the toolbar of Gutenberg so you can't do anything those kinds of issues screen readers still hard to use and the main problem is so a lot of energy has been invested already to improve these things and the problem is just that we have so much more moving bits and pieces in this system that discoverability is an issue for instance when you don't know how this thing works and you come to it for the first time it's hard to discover what all the features are if you're only using a screen reader and the plan right now is to focus as much as possible on the low hanging fruits and to make the baseline experience for using Gutenberg as good as possible it's important to know this plugin compatibility a lot of time is being invested by the community as well in exploring that as you know meta boxes will pretty much still work Daniel Vancouver has launched a project it's called pluginscompact.danielbancouver.com it's like a big database of all the plugins and you can see which ones are compatible with Gutenberg when you start working on that question that many people have is what happens to my custom fields like Andrea also pointed out there are solutions for that that are completely native to Gutenberg and advanced custom fields is itself also working on a native integration with Gutenberg so you should be covered whenever Gutenberg drops ACF will still work ok, and this is a famous tweet by Joost the Val CEO ask not what workers can do for you but also what you can do for workers so what can you do test, please get Gutenberg, go to frontenberg google frontenberg I'll put those links in my slides test the thing, try it out especially on sites that are using plugins if you have a local copy somewhere try, look what happens we need more feedback even though we've been working on this for one and a half year we've had a lot of feedback we still need more feedback because the scope of WordPress is just few moments, 30% of the web is running share it share your feedback and you can do that in Gutenberg itself I'll show you that and you can also do that on GitHub I'll show you how you do that in Gutenberg itself there's Gutenberg here and there's feedback here and you can just send your feedback it's very important spread the word anyone you know who doesn't know needs to know this is coming it might be one, two years I wouldn't count on it it might be a couple of weeks months we can fix a lot we won't be able to fix everything there are some solutions to mitigate the damage but you have to see that 14 years we've built on top of an ancient platform now we're building the platform to build the next 14 years some things are going to be a little bit less stable but it's important as many people as possible get to prepare for this and start integrating if you're an agency, plugin, theme try out those APIs those APIs that are available right now to integrate they are still not released I mean they are released in Gutenberg but they are still not in WordPress that means that if you have a problem with the APIs if it's too complex to integrate with Gutenberg if you want anything changed and made more simple this is the moment to figure it out because we can still maybe change something I think we've done quite a good job but I have to know we have to know and ask for help in your local meetup there's this site I just love it's called getting ready for Gutenberg if you have a plugin with over 500 installs I think or 5000 maybe we can get help from them and there's lots of resources you can go to WordPress Slack and people are very much willing to help out anything you don't get about Gutenberg and when all else fails there is the classic editable plugin but it won't be maintained forever probably and the other thing is that whenever Gutenberg lands in 5.0 in WordPress itself the default experience people will have is a WordPress with Gutenberg and basically whenever you install the classic editor like the first experience you will have is never downgrading your experience because we can because it's just not ready we're just not ready to deal with it it's not a pretty message if we can avoid it we should avoid it I want to take a brief moment to talk about opportunities because there are a lot of opportunities when a big change like this comes so plugins think about how you can integrate deeply with the editor whatever you do if you create custom blocks for content you add to a site if you give feedback on a text like Yoast does or whatever deep integration will make Gutenberg a better product and it will make your plugin a better product and it will ultimately benefit the end user experience themes, same thing if you have a theme make sure it's not that much work to include in Gutenberg if that's not easy enough give the feedback because it should be easy creating themes for WordPress has always been easy if it becomes much harder now then we need to know about it often themes have some custom functionality some custom elements these things need to be in Gutenberg they need to be able to access that and it's going to look like base builder plugins it's very simple you already have elements make sure those elements are stored as blocks and you're fine and if you do this and Elementor is going to do this and Beaver Builder is going to do this you're going to have an advantage that you never had before you're going to be compatible with everyone you have your own little systems for storing elements and all that kind of stuff was never compatible with Yoast and with other plugins if you store them as blocks people can go to the block editor for the optimization and they can go to the base builder for the customization and the design and the whole experience will be better Agency current agency or freelancer working for customers start putting together an information pack if you are together with other freelancers in a community like this work on that together and then start informing your customers and it doesn't mean oh, this change is coming I can fix it for you, you have to pay me money this is not what I'm talking about it's nice, you can probably make a good buck of this change but you say this is coming I know about it these are your options the classic editor won't cost you a lot I can optimize your site for you it will cost you something but your experience will be much better so you have a lot of flavors to sell to your customers and the most important thing is trust because you know you give the information, you warn them you help them get through this it's a good experience for end users in the end that brings a big opportunity for the end user because if everything goes well after the storm we'll have a much better user experience for workers this is some important resources in my slides, I'll share those slides after the talk there's an important thought piece from Matthias Ventura, I was the lead of the Gutenberg project it's called Gutenberg by the Ship of Theses at just.com we've written a lot about Gutenberg you can just follow the tag and Morten Brand-Hendrickson also a distinguished workers community member has written extensively about this as well there's some videos that you can watch and I would definitely also recommend the project that we have at Yoast it's called The Good Guys and it's a full YouTube series about Gutenberg explaining every little detail there is to tell about Gutenberg you can also send in questions and they'll answer it for you both of my colleague Anton and him are working lots of hours a week on the Gutenberg project itself and are part of the Gutenberg team and that was it do we have time for one or two questions in terms of page speed upload did you make some test about it on how it could affect speed, yes what size speed thank you in the beginning because everything is a block in Gutenberg you need some kind of parser on the front end to generate the page and this can be expected to be a little bit slow so in the beginning there were big problems with that now they fixed most of those problems and I think there's almost no speed decrease from what I've lost but this is also important to test especially on big pages and also how fast is the editor when there's a lot of content in it we need this to be better tested like one of the primary objectives for the Gutenberg project is to get more and more users so we get better and better feedback because we can't cover all the cases but so far so good we're not aware of any improvements is there any news about the features in the next version of of try the Gutenberg button we have talked about so I'm not sure if the next minor release of WordPress is going to include but I think they were planning on that so there's gonna be a minor release of WordPress 7 or something and it will include a notification inviting people to install and try Gutenberg and it will announce it like this is gonna be the new editor for WordPress try it now something like that we have responded a couple of times because it was supposed to land in April this notification but I think this might actually arise before we can hear it hi Yama you mentioned that being a structured data you need a parser on the front end to out the page does the parser have an API right now I'm not sure but I think I think it will because most of the PHP in WordPress is always using filters and actions so probably it will have a classic WordPress API thank you thank you very much for your attention