Should not be included by default

By nspirov on February 10, 2025

This and all other bad reviews are for the Gutenberg feature inside Wordpress.
OK I get it. Some people want to have this. But it SHOULD NOT be pushed down the throat of everybody else (as in "included in every Wordpress install in the world"). When millions of users choose to deactivate it, it is OBVIOUS it should be a plugin. We all know the dangers of having huge amounts of dead code in our websites.

9 million people uninstalled this plugin

By AlexPTY on January 24, 2025

Do you have DOGE in your company? Maybe you should, why bother developing this if nobody using it. It's really a hustle to uninstall this plugin every time i build new website. Maybe you shouldn't include it in a package?

A simple and promising approach to content creation!

By Nels (nelsj5r) on January 23, 2025

Gutenberg et son extension pour WordPress sont de très bonnes initiatives, offrant une approche simple et fluide de la création de contenu. Ces outils méritent davantage de soutien de la part de la communauté open source. En tant qu'utilisateur, je privilégie la simplicité et la frugalité, que j'espère trouver dans Gutenberg, contrairement aux page builders payants qui privilégient la complexité. J’encourage à poursuivre dans cette direction.

Gutenberg and its WordPress extension are great initiatives, offering a simple and streamlined approach to content creation. These tools deserve more support from the open-source community. As a user, I value simplicity and frugality, which I hope to find in Gutenberg, unlike paid page builders that focus on complexity. I encourage continuing in this direction.

Thanks the team even if lot of things still to be done...

"Do not fear being slow, only fear being stopped..."

not born to be default wordpress editor

By brkard4141 on January 8, 2025

Hello. Unfortunately, this Gutenberg editor seems not to be born to be an editor. It’s very difficult for it to become one as it grows. Many of my acquaintances and clients are struggling to use it. We try to teach them, but it’s so hard that they give up. That’s why they all feel very happy when they switch back to the classic editor.

Because they are just adding text and images. They still use the classic editor for e-commerce.

For these reasons, Gutenberg will never become the default editor in WordPress.

I have a suggestion to make this work better.

When content is added with Gutenberg, it could initially be a simple WYSIWYG editor, still using Gutenberg. Similar to the comment box we use here. If it had tools for adding images and other Word-like features like bold, italic, image addition... Maybe it could also just be a simple column where text and images can be added. In other words, a default block similar to TinyMCE. Additionally, there could be a button for switching to block mode at the top, which opens the block editor when clicked. If a design is required, this button would be used; otherwise, there could be a simple interface similar to TinyMCE by default... I think if something like this is implemented, many people will start to like the Gutenberg editor.

Good luck!

The worst UI UX

By jxenarios on January 7, 2025

Gutenberg is unusable, so many redundant options, common actions moved into sub-menus adding extra clicks everywhere. Very frustrating to use and delays progress when working.

It takes time to get used to, but it’s a powerful editor

By wilcosky on December 26, 2024

When I originally reviewed this editor I gave it 1 star. Months later I changed my review to 3 stars and now I’m going to 4 stars.

In the beginning there were too many bugs and it wasn’t integrated enough. It truly was a 1 star editor when Automattic decided to ship it with whatever version that was that this first appeared in core. I still believe it needed more time.

In fact, it shouldn’t have been included in core until around now. The gun was jumped.

Now that I’ve had time to enjoy full block themes with the full site editor, and now that there are many add on blocks out there, it’s nice. It makes creating a new page with multiple columns very easy. Or, as a great example, I found a contact form block. I’ve never been able to add a contact form that quickly.

Overall, once you learn where everything is, it’s very powerful and fun to use. Most of the time.

There are still quirks. One is that depending on the height of a block, number of columns, and alignments, you might click forever trying to select one column and never succeed. Unless you revert changes and try again.

But, when it works, it’s a better editor than the classic TinyMCE editor.

Now I don’t want it to go away. I just want it to continue to improve.

5+ years and still terrible

By daniel (tj0ckis) on December 19, 2024

After years of development, Gutenberg still sucks just as much as when it first came out.
Matt W, who forced Gutenberg on us all doesn't even know how to use it properly. He lost a speed build competition because he didn't find GB easy enough to use (see the competition here: youtube dot com/watch?v=BzduYKuZAIg)

I really tried to use it, as i believe in websites with as few plugins as possible.
But there is no way my websites will be better without using pre-made blocks by premium providers (kadence or similar). So i might as well stick to page builders.

I have delivered websites to 50+ clients, and all of them need tutorials on how to use the GB editor for something so simple as blog posts (which is only text and images).
They all knew how to use the previous editor, but this one overwhelms absolutely everyone.

Until the feedback is obvious enough to change direction of this horrible editor, i'm sticking with Bricks Builder (which is amazing btw).
Bricks Builder has existed for a shorter time span than Gutenberg editor, and it's a full-blown site editor. I don't understand the scope of the failure of this project (except for the obvious fact that Matt doesn't listen to the thousands of feedback and complaints from the community).

Good luck!

I like your Idea but it's Crap

By rishiichaudharyy on December 15, 2024

I know my review doesn't matters, But let know the others. Previously I'm using Oxygen Builder now switched to Gutenberg for flexibility and many other things, But after 3 months I'm not only disappointed but frausteted for six reasons.

  1. I don't want to develop block and build each time for basic things. I want to use JavaScript library ( alpine, parallax, splide and many others ) for any kind of interaction.
  2. There is no native HTML elements, neither Attribute Support. When applied classes to image block after inspection I get to know it's wrapped inside figure element where my classes applied. No Custom Html Tag support, it has not even basic tag like span, html tag support on only group, stack, row and grid this is rigid.
  3. It has bunch of predefined classes which I don't need many times so I have to rewrite and override the element again and again. There is limited design elements available on many blocks basic things like overflow, back-filter, row reverse on mobile. You Proudly say create website without css let me I ask you again can you create website without css it's core heart of website and you are saying you will remove and it will work try with your own body and let me know about it.
  4. For responsiveness, I thank you first off all to make me learn about fluid typography and fluid dimensions. Now get to point atleast there should be atleast one breakpoint for every elements. Look your Intrinsic Design is good Idea but it is not working with Clients, So please understand this there is many times there complex layout by UI/UX designer. As dev I need to do it.
  5. E-commerce - mainly i create e-commerce website with woocommerce in two or three months ago, now I'm creating with Medusa.js it is because woocommerce and WordPress both make me do it. If I have to create e-commerce website I have to control each and every macro element/components like your Product Collection block or repeater block. There is problem in structure ( ul ( image, name, price, Add to Cart )) it' should be like this ( ul (li ( image, name, price, Add to Cart ))) inside block editor but li is missing from block editor so I can't add any kind of classes to it I have to add through JavaScript same goes with price there is two price element sale price and regular price I can't able to change basic css of one element through block editor and almost same goes with add to Cart i can't even add icon beside add to Cart text. There is many things missing.
  6. You want to to choose how rivers flow but you should know rivers will always find their own way. Last but not least I have good journey with With WordPress and Woocommerce now it's time to say Good Bye 👋

历史上最差的编辑器

By cuiyujun on December 11, 2024

多听听大家的心声吧。这个项目建议放弃,为了节约你我他的时间。

ANOTHER STUPID DUMBING DOWN

By (nospam22) on December 7, 2024

As someone who had an award-winning site that garnered millions of hits, I abandoned the site years ago only to return and find WP has changed over to Gutenberg. This will now take its place with Microsoft Office as yet another prime example of what happens when you try to dumb things down only to make them more complicated and difficult to use. The classic editor was great, but the folks upstairs decided that using code was too complicated for people so they came up with the dumb idea of blocks. The only problem is blocks are difficult to edit or modify. To name it Gutenberg and compare it to the invention of movable type is ridiculous. It is as if Gutenberg's movable type were replaced with blocks of type all glued together under assigned arbitrary uses like headlines, ads, etc. so that it is impossible to actually write an original headline or even modify the typeface used for it.

Overview

  • Latest version 20.2.0
  • Last updated
  • Active installations 300,000+
  • WordPress version 6.6 or higher
  • Tested up to 6.7.2

Ratings

3,815  · 
1 stars
2,474
2 stars
217
3 stars
142
4 stars
150
5 stars
832

Contributors

3
Matias VenturaJoen A.Tammie Lister