 My name is Thiago Oredo, I'm trying to get this bigger, yeah, and I'll try to present very quickly this, about our bill of plugins in Gutenberg. So first of all, thanks for all the organizing, all the people that helped building this data center you have here now, and to the sponsors as well. So a disclaimer before, is that I'm not associated with these plugins I'm going to talk about, all the opinions are my opinions here, and the criteria for selecting them was from just how popular I feel they are, and how close to the Gutenberg bill these plugins are. So these are the plugins I'm going to talk about, Yoast, an SEO plugin, Advanced Custom Fields, which is a plugin that facilitates inputting content inside a post. WooCommerce, eCommerce plugin. Tynemc Advanced, which is, if you guys don't know it, Tynemc is the rich stacks editor that has been with WordPress for a long time, and it's just an extension of that. Ninja Forms, a form, plugin, Next Gen Gallery, and then the three page builders to the end, and how they're interacting with the change that is coming to WordPress. So first of all, Yoast is probably one of the companies slash developers that contributed the most to Gutenberg by either investing in the project or giving time and resources and educating people on how WordPress, Gutenberg is going to be. One of the earlier adopters, and they have this series on YouTube called The Good Guys, and these are two of their employees, and it's a very cool series of videos, very short, very informative giving tips on how to use Gutenberg and how it can interact with Yoast. So that's the old look of Yoast in the page level, in a post level. You have that box here, you have this box here, which you can, inside that box you can change SEO information of the post you're writing, the page you're about to publish. That's the old look, and Gutenberg, that's how it looks, it's all the functionality is here. The same for nothing new, it's just the same old functionality, but presented in a different way. So from this part there's nothing, they had to do an effort of course to port this to Gutenberg, but it doesn't add new features to the project, at least not in this part. Another thing is that, remember there was this box here where you could see search snippets, now it's an overlay on top of Gutenberg. Again, same thing, no new functionality, but there are two, one nice feature of Yoast, very close to content, take your block, so it's just like a template, it's a block, that is very easy for you to add questions and answers. And the advantage of doing this, instead of just going the classic way and writing it in plain text, is that it's going to give you a schema out of the box, you don't need to write it. And that's schema for you guys who don't know, visit schema.org, adding schema to certain bits of your code kind of helps the search engines to understand your content better and present it in a nicer way. So that's that block that I was writing here, it becomes this once it's published. And you don't have to be aware of this part, Yoast will do it for you and it's nicely presented. So right now the newest version of Yoast is, by the way, it's very recent. They add the FAQ block and how to block, which is kind of a similar concept. It's a structured text that is very easy to add it and put text, or just click, add a question. This is how to, you add a time that it takes for you to complete a certain task. And the steps, you can add images to it, very simple and cool. What you see there is what you're going to see, it's very close to what you're going to see once you publish. Same thing again, like here, sure, okay, so good here, oh, here, sorry, and then turn it to there. Then start to click here again, okay, here, all right, is it better now, is it better now, cool, awesome, sorry, I'll stay right here and I'll go anywhere. So that's how it looks, by the way, once you have this schema, Google, for example, we will show your how to in this nicer way. This out of the box, this comes, you don't have to do anything special. If you add that how to block, there's a good chance that your result, if it's higher ranked, is going to show this way on search engines. So that was a search I did, by the way, when I was searching about this block, I searched for Yoast how to block, and it gave me that search snippet about how to implement a how to block. And I think that's one of the coolest examples of Gutenberg usage is the annotations API, it's very new, and it was developed by a guy engineer at Yoast, one of the good guys, he was the guy that developed this API, which is, as you type, as you input content, there is a way for Gutenberg to analyze your content on the fly. So this is very important for SEO stuff, like when you're writing a text and you want to know if that text is good for SEO, you want to have this feedback on the fly, not after you publish, you want to have it as you type. So I just pasted this content inside Gutenberg, and the results on the right, on the right bar there, just on the fly, and it shows what text can be done differently, and this is very powerful. Like you can have plugins analyzing your content as you input, and Yoast is probably the first one that I saw using this cool feature called Annotations API inside Gutenberg. The roadmap for Yoast, they want to align the classic one, they're still going to support the old editor, they're not dropping it, so there's no risk of that, and that's it, and they want to focus more in the Annotations API a way to analyze your content as you input. The other one that I'm going to talk about is ACF, version 5 of ACF provides support for Gutenberg, and version 5.18 introduces ACF blocks, that's the classic, this here, on the bottom, is the classic, this on the bottom here, is the classic ACF field group, like the section there, right, and it will work with Gutenberg, you can add new pieces of information that you can extract inside your post, and that works the same way as the old editor, so this you're seeing on the bottom of the Gutenberg editor is the same as this, it's the very same as this screen you can see in the classic editor. The new thing is that now you can have ACF blocks, and the only difference is that when you're defining where your ACF is going to show up, you can say now I want it to be a block, it'll be a new option, this by the way is better, I don't think it's available in the main version, it's 5.8, it's very recent, like 10 days ago kind of thing, and this is the code, it's not really important now, but that's the code it takes for you to render an ACF block inside the Gutenberg editor, so let's see if we can see, play the video, that would be hard just a second, so the same block I had before, I just, that it was not a block, sorry, the same ACF group I had before, sorry, the same ACF group I had before, I transformed it into a block, so as I type you can see that the content is being displayed there, I'm not publishing it, it's very dynamic and that's all with ACF, the advantage of that is that you don't need to do any React, any JavaScript code to display that and to make your blocks, so it's very useful if you don't want to go into the JavaScript realm, you can just use ACF to that. WooCommerce is the next one, the WooCommerce is not changing and I couldn't see any plans that they have to move the product editor to Gutenberg, so what I've heard from WooCommerce is that they want to make the experience inside WooCommerce to get as close to Gutenberg as possible, I might be wrong on that, but that's the notion I'm getting is that they're not moving initially to Gutenberg, the product editor, I mean, but there are plugins on top of WooCommerce that provides this functionality of transforming WooCommerce pieces into Gutenberg blocks, one of them is made by the team, by the automatic, it's called Gutenberg products block, which is just a way that people can showcase their products inside Gutenberg, so I added this block there and you can choose what kind of products you're going to pick, it displays right away how it's going to look like, and you can change for example the number of columns and the number of products you want on the screen, and once you publish what you're going to see is pretty much what you have in the editor, there it is, there's another plugin on top of WooCommerce that's kind of popular, which is Advanced Gutenberg, it provides other kinds of blocks, including WooCommerce blocks, then there are a lot of plugins popping up like that now, they just provide various blocks for you to use, it's a five-stars plugin so far, and it's the same idea of the plugin I showed before, it's just a way to display your products, this one has a little bit more options, including a slider, see, you can slide your products, and it also adds all sorts of plugins, it's not a WooCommerce specific plugin like the other one, but the future of WooCommerce, at least in the WooCommerce project itself, you can follow this link to see what are their plans for WooCommerce, not a lot related to Gutenberg so far, but I think in the plugins for WooCommerce there's a lot of stuff going on, mostly to display your products in a nice way, and if you want to search for new plugins for WooCommerce or plugins that offer blocks for WooCommerce, there is this nice link here called Editor's Blocks WP, which is a kind of marketplace just for blocks, it's not a marketplace for plugins, it's just like you can find your block here and it's going to have a description of the blocks you can find, and the plugin that offers them. TinyMCE Advanced, so TinyMCE is this editor that has been with WordPress for a long time so far, is a rich text editor made in JavaScript, and there are some options for formatting our text, but it's kind of limited, some people need a little bit more power to format their text, and so there's where TinyMCE Advanced comes, because it adds the option to create tables and format your text, like apply font family to it, apply color, and this you cannot do with the regular editor, and it works with Gutenberg by the way, so that's the Gutenberg editor, and if you can see it here on the bottom, let's wait for this thing, sorry, let me try, yeah a little bit there, sorry, this on the bottom here is the classic block, you're going to have the classic block on Gutenberg, which is the classic editor, you're going to have the same capabilities you have in the class editors right now, but it's inside a block, and TinyMCE Advanced also works with this block, so the same capabilities I had before, I have here now, I can add the color of the text and stuff like that. Next one, Ninja Forms, it's I think from the popular form plugins is the one that offers Gutenberg block, and it's still in beta, so I couldn't make it work with doing some tests here, I couldn't make it work, so this GIF is coming from their page, so very soon they will have a stable version, they'll be just like this, you add a block and then you can move your form as a block, that's how it works, you're not going to add the block from this interface, you're just going to select the block that you already created in the other screen, and you can also do the short code way, because there is a short code block. Next one, next-gen gallery, similar concept of Ninja Forms, you can add a gallery elsewhere or add a gallery, so that's how it looks, sorry, let's go one step back, you can, in the usual way, you can add a gallery, that's a classic editor, you can add a gallery by just pressing this button, and it will show this block here inside, not a block, because that's a classic editor, sorry, it's going to show this inside a classic editor, and you know that by clicking edit, you're going to have all the capabilities for editing your gallery there, with Gutenberg it's similar, so you can press there, there'll be a block for next-gen, once you add, you're going to have the very same overlay you had in the classic editor, same experience, no new feature, they're just transporting what they had before to Gutenberg, and that's it, nothing really, nothing new just for Gutenberg, just transporting stuff, but it takes time, this is not, plugin developers, they have to take the time to make it work with Gutenberg, it's not a lot of work I think, it depends on how complex your plugin is, but there is definitely work that has to be done from plugin developers, next one, now is the, I'm going to talk about the builders, and how they are reacting to Gutenberg, first one it's one of my favorite ones, Beaver Builder, and what I feel is that most of these builders, they're focusing, they're playing nice with Gutenberg, they want to be part of it, that's the sense I get, and the initial effort is to be able to translate from one experience to the other one, for example going from Beaver Builder to Gutenberg and vice versa, so they want it to make it nice so people don't lose whatever work they've done, once they, if they want to transition between the two, so all of them will have some sort of capability to, the ones that I'm analyzing are, by the way, Beaver Builder, Elementor, and DV, and all of them have this capability of like you're writing a post and you want to now switch to Beaver Builder, it's possible, the translation process itself, it's what varies between them, how well they do this translation, and they're not afraid of Gutenberg, I think this idea that some people have that the builders are afraid of see Gutenberg as a competitor that might trust them, I think in real life they're not, they know the market that they're in, and they know that there'll be space for them, that's my opinion, I know that there's a lot of debate on that, and by the way, and they know they, they are, they were these people that are developing these plugins, they were like the first ones to initiate this kind of revolution that Gutenberg is part of, and they behave the same way, it's like you have blocks, you have controls, specific controls for each block, they've been doing this before Gutenberg, the problem with Beaver Builder is that they don't have a Gutenberg block itself, and you're going to see soon what I'm talking about, that's the translation process by the way, it's hard for you guys to see that, but what I have here on the left, supposing I have these three blocks here, once I move this post to Beaver Builder, Beaver Builder is going to understand it as a full classic Beaver Builder block, it's not going to translate one to one, one Gutenberg block doesn't become one Beaver Builder block, so that's the state Beaver Builder is, when you go back to, when you go from Beaver Builder to Gutenberg, it does some translation, your Beaver Builder content becomes, some of your blocks there inside Beaver Builder will become Gutenberg blocks, but as you can see here, the translation is not the same, so what you see is here as circles, here will become the word circle, it's not the same thing. Next one is Elementor, if you can see how it works, it's very similar to the way a lot of things that you're seeing Gutenberg, they're choosing blocks, in this case you're dragging to where you want to place them on the screen, and you can have, once you click on these blocks, you're going to have more control for editing these blocks. Same thing for this translation thing that I'm talking about, once you go from Gutenberg to Elementor, all you have is going to be a big Elementor block, when you go from Elementor to Gutenberg, what I got was also a big Gutenberg classic block. There is a very nice plugin, that's why I think what differentiates Elementor from all the other plugins is that they offer Gutenberg block, and it's very powerful, it's a middle way between the two approaches, and it's a plugin on top of Elementor created by the Elementor team, which is, here on the left I created a section or a page template, and I'm going to use this page template inside Gutenberg. You see, that's exactly the section that I created here, and now it's inside Gutenberg. If you see it again, I'm going to add Elementor block, and then I choose from the list of my previously created Elementor block, and then it displays there nicely. It's a nice transition, and it's very interesting they're working on that too, so early. I just saw this in Elementor, I don't know if there are any other page builders offering this kind of transition, but they are, and it works nice. The last one is DV, a page builder like all the other ones. Here is an example of how they're transitioning from Gutenberg, so here they are in Gutenberg, and they offer a nice button there to move this content to Gutenberg, to DV, and once you're inside the DV screen, it offers the option to use the existing content or start from scratch, you're going to have both options. In this case that I already had text here, they're just using the existing content there, and from there you can have all the DV capabilities again, and you can improve whatever you wrote on Gutenberg. The ideas that a lot of these page builders are having is that use Gutenberg to write your content, not to style it, and once you have your content, bring it to the page builder, and then you can style it to your taste. But that's it, sorry I was very fast because of the time, and if you guys have questions, let me know. Oh, question there, sorry. There are a lot more differences, so the question is if the only difference between Gutenberg and some page builders is the fact that they have columns. Is that correct? Yeah, so it's more than that. Page builders will do the column bit better, far better than Gutenberg at this point. There are more differences, they've been around for more time, so they have blocks that have better controls than have more controls and stuff, and the way they save information is also different. So I'm not sure how these builders, how they store the information, if it's in form of pure HTML, but Gutenberg has it's own way, so that's also different in the development side. It depends, yeah, I think for simple cases, Gutenberg will do it, and if you're starting on WordPress, what you're going to see now, it's Gutenberg, right? If people are already in the builder realm, they will have a lot of plugins, they will know how to play with it, and these plugins have been around for some years now, and they can continue it, there's no damage, but they are offering transition paths to both people, the ones that are in Gutenberg and want to transition to a builder and vice versa. Any other question? Cool. The question is which one of these builders integrate best with Gutenberg? The translation bit, I liked the way, they are pretty similar, they will have, they will fail in some parts, so it will require, once you transition, once you translate, you require some fine toning, I think there's no way to go around it right now. The one I liked the most was Elementor, even though I'm a big builder fan, because of the block, because it has a nice way of you creating your blocks in Elementor, there's something you can only do in Elementor kind of scenario, I know how to do in Elementor, but I don't know how to do in Gutenberg, but I want to use Gutenberg, and this scenario specific, it's great, it's great, it's great, because you can just pick your block, you can create your block separately inside Elementor, which right now will have better styling capacities out of the box, Gutenberg not so much, if you just use vanilla Gutenberg right now, they had a head start on Gutenberg, they had like two, three years ahead of Gutenberg, so now if you want to do very fancy graphics using a page builder, using WordPress, using a page builder, sorry, go for a page builder, Gutenberg, I feel that Gutenberg it would need some way to go, or some plugins to add on top of it, to reach the kind of same level of designing visual stuff, any other question? One question there, the question is if using a page builder, if Yoast is going to play nice with this page builder, is that? I'm not sure, I don't think so, so because Yoast won't understand some of these blocks, I feel, I never heard of any integration of with Yoast and these blocks, I might be wrong, but for example if you use the FAQ block from Yoast, I don't know if this page builders will have FAQ blocks too, they probably will, and if they add any SEO goods in it, it's probably going to be from the own plugin, from the own page builder, and that's not their business, right, like it's, their business is created a page builder, it's not their focus, they can, it's not their focus, so I would say no, they don't, they don't offer it, but I'm just guessing, there's a WP glue, integrations for Yoast with different type of content like for ACS, yeah, yeah, that's nice, that's, that's amazing, yeah, he won't be out of the box, I'm pretty sure they won't be out of the box because it's, if you're a page builder, you don't want to go too deep into SEO, you know, any other question, one question there, yeah, the FAQ Yoast, does that tend to be part of the visual page, or is it something that when Google scans the page, it's just sort of a fire attack out of Google with the structured internet? So the question is if the FAQ block is intended to be part of the visual page, of how it's, what's published, yes, yes, I can show, I can show again, so what, what you're going to see there, what you're going to see there in the editor, ah, it's gone, ah, okay, what you're going to see in the editor as you're adding the Yoast FAQ block is it's what you see in the end, let's see, obviously having, giving a helping hand to Google to be able to make sense of it before you can have a page, there's obviously a marketing campaign there, and I'm just trying to figure out what it is, do they have an intention of creating a whole series of blocks? I think so, I think so, because it doesn't really make sense to create just this two, I think it's just a starting point, because there are other entities, other schema entities that a lot of people use and they're not there yet, so I think Yoast is kind of moving in this direction of offering this templates for, for information input, kind of, and this is a starting point for them, and they started with probably the popular ones, which is like FAQ and how to, but I didn't see anything official about it, about direction and stuff, even on interviews of Yoast, yeah, they're working on lots of plays on different fronts on Gutenberg, so yeah, they are there, they're there and they probably want to provide more support, more features, probably the, the new features of Gutenberg will come from Yoast, I feel, they'll be always pushing it, it further, they have, they have resources in the company directly working for Gutenberg, so that's how inside of it they are, so the FAQ block is only available once you load the Yoast plugin, so the question is, the question is if the FAQ block is inside Yoast, there's no, and there's no, yes, that's, that's, it's part of Yoast, it's part of Yoast, it's Yoast providing blocks that are for content, that's, and that's new, yes, yes, it's part of, once you publish it doesn't matter where it's coming from, it's going to display, it's a plugin that provides you a new block inside Gutenberg, once you disable Yoast for example, you're still going to have your post there, but you're not going to be able to input new ones, any other question, one question there, the sliders, I show, so one of the plugins that I show there, the, the question is if there are any sliders integrated with Gutenberg, probably, I'm not sure, sure, yeah, you can integrate them in Gutenberg, and I show one of the plugins I had a slider in it, so it's probably not a, not a crazy challenge for people to add, there are a lot of plugins that will add a bunch of different blocks, gallery, probably gallery, the gallery one, the next-gen gallery probably offers a slider of, a slider of images, there are, there are a lot of plugins, there's like a pack of blocks, and I show one of them, the slides will be available by the way, I cannot, okay, it'll be on my Twitter, see if I can show it here, yeah, it'll be on the screen soon, any other question, nope, cool, thanks guys, yeah