Once you activated WooCommerce on your website, you may notice that near 20 new blocks have appeared in editor. But do you really need all of them?
I already have a couple tips on my blog about “fixing Gutenberg”, for example I already mentioned that you have to double check that REST API is not disabled and in this guide I show what to do if Inserter Dialog is not available. But recently I faced with another issue.
In this tutorial – how to get posts in Gutenberg using REST API and create a select dropdown from these posts.
In my previous tutorial we talked about creating Gutenberg plugin sidebars and now I decided to make it a part of my plugin, so you can create sidebars easily with a couple lines of PHP code
The detailed tutorial about using PanelColorSettings and withColors for custom Gutenberg blocks.
In other words, I will show you how to add some settings for your custom block to Gutenberg sidebar.
In my previous Gutenberg tutorial we created a nice subscription form block. Now let’s make it editable.
Guys, I can not even explain how I was struggling with Gutenberg blocks ? Really. One more reason to this is that I am a back end developer, not a front end one! Really, in my life I do not need all that stuff like npm, webpack, react etc.
Either you create your own Gutenberg block or some buttons for block toolbar or maybe you decided to add some settings fields to the post – in any case you have to add icons. And in this tutorial I will show how.
The goal of Gutenberg editor is to display the website content while you’re editing it the same way it is displayed on the website. But if you’re using your custom theme, it isn’t going to happen just by itself.
Today I begin the work of moving my current website to Gutenberg. Well, I haven’t faced so many issues daily for a long time. Some issues are stupid and my fault but anyway I’m going to share the process here.
In this tutorial I will show you a super-simple way to remove any of the default Gutenberg blocks from the inserter.