Gutenberg, One Year In: A Fresh Look at the Pros and Cons of Gutenberg

WordPress Gutenberg
This week, we’re happy to present guest author Eric Karkovack’s thoughtful and balanced take on the Gutenberg editor, one year into its inclusion in WordPress core.

The Gutenberg block editor has now been a part of WordPress core for a year. This milestone seems like a perfect time to revisit one of the most anticipated and controversial features ever to be added to the world’s most popular CMS.

Even after a year of Gutenberg, there are still a lot of questions, misconceptions and (of course) opinions. Meanwhile, some developers have happily moved over to the block editor as their go-to solution. But the transformation hasn’t been completed, as others have stuck with the trusted Classic Editor and aren’t in a hurry to switch.

With that in mind, I wanted to take a fresh, objective look at Gutenberg’s features and usability in comparison with the alternatives.

So, what are the pros and cons of Gutenberg one year into its run? Let’s dig in and find out!

Gutenberg at One Year: The Pros

First, let’s look at what I feel are the strongest aspects of the block editor. It has shown marked improvement over year one, and does a number of things well. Here are a few items that stand out:

Basic Layouts Are Within Everyone’s Reach

Maybe it’s no surprise, but one of the Classic editor’s true drawbacks is also one of Gutenberg’s biggest strengths. Previously, something as simple as a two-column layout required either custom fields, a page builder or (worse yet) writing HTML and CSS directly into the editor.

wordpress gutenberg two-column layout

This is an area where WordPress was behind the times compared to the likes of Wix and Squarespace, etc. Now, with the Columns, Media & Text and Group blocks, a simple layout is possible with a default installation. While not earth-shattering, it is a welcome addition.

Hidden Features Get Some Love

One of my favorite perks of using WordPress is its ability to handle embedded content from a wide variety of popular sources. Yet, outside of developers and serious bloggers, how many people actually knew about it?

Gutenberg has thankfully brought these features out of the shadows. With the Embeds category of the block editor, users can readily learn that they can embed content from places like Twitter, YouTube or SoundCloud.

The Flexibility of Custom Blocks

For many, the biggest selling point of Gutenberg was the ability to create custom blocks. The promise was in the variety of ways they could be utilized – including some we haven’t even though of just yet.

By and large, this has held true. Functionality-wise, blocks can do pretty much anything an existing widget or shortcode can. Plus, they can be used to create layouts and other design-related elements.

#Gutenberg's blocks can do pretty much anything widgets or shortcodes can, plus create layouts. Click To Tweet

Of course, this feature can only be truly successful if the WordPress community buys in. So far, so good. Many of the most widely-used plugins such as Yoast SEO and Gravity Forms have added blocks to their core features. Beyond that, a number of plugins have been released that are solely dedicated to bringing new blocks to your site. The plugin repository has added a new section to highlight these offerings.

And, as someone who frequently uses the Advanced Custom Fields plugin, I love the fact that I can marry the functionality of custom fields with the convenience of putting them into blocks (through the ACF Blocks feature). They can be used in multiple instances, easily repositioned and blend in well with the editor’s UI.

Overall, this is an area of strength that I would expect to continually improve over time. The community will find new and interesting things to do with blocks – something which we will all benefit from.

Better Standards for Extensibility

Among the more frustrating aspects of the TinyMCE-based Classic editor is that it gave developers too much leeway with regards to adding custom buttons.

For instance, adding a button related to a specific plugin could be accomplished in a number of ways. It could be implemented within the editor’s toolbar or by adding a somewhat larger button above the editor itself (next to the Add Media dialog). This led to some design inconsistencies and a more cluttered editing experience.

#Gutenberg's custom blocks have a standard UI and are searchable by keyword, a tremendous benefit to users. Click To Tweet

Thankfully, Gutenberg’s Block API provides a way to rein in developers. Custom blocks are implemented within a standard UI. They are organized within categories and searchable by keyword. This is a tremendous benefit to users, as everything they need is now in one place.

You Don’t Have to Use It

When the Gutenberg project was first announced, there was some concern about whether this newfangled invention would be forced down our throats. Would we still be able to use page builders? What about the Classic editor we’ve grown so accustomed to?

In keeping with the WordPress tradition, we still have the option to use whichever editing experience we prefer. Page builders still work just fine, and the Classic editor is now a plugin with over 5 million active installs. That’s good news, as it means we can still use WordPress in the way that works best for us.

Gutenberg at One Year: The Cons

On the other side of the coin, Gutenberg still struggles in some areas. Given the break-neck pace of its development and inclusion in core, that’s to be expected. But there are also some existential questions about what it is and who it’s meant for. Let’s take a look:

Still a Work in Progress

If you were one of the many users who tried the pre-release version of Gutenberg, you likely noticed some bugs. Selecting the correct block within your post, for example, could be a real challenge. And not everything was intuitive.

To the credit of everyone who works on the Gutenberg project, many of these bugs have been resolved. Building something like this from the ground up and releasing it to millions of users is no easy task. They’ve made great progress, for sure.

Some #WordPress editing tasks are actually more difficult in Gutenberg – which shouldn’t be the case. Click To Tweet

However, the editor still lacks some of the fit and finish of the alternatives. And some seemingly essential things that were part of the Classic editor are still maddeningly absent. In that way, some tasks are actually more difficult in Gutenberg – which shouldn’t be the case.

wordpress gutenberg needed features

It’s Not a Page Builder… Or Is It?

This is one of the trickiest questions to answer – one that causes me to go back-and-forth. On one hand, Gutenberg is there to boost the baseline editing experience in a default WordPress install. It’s a means of accomplishing those little things that the Classic editor made difficult. As mentioned above, it’s pretty well up to the task.

But if you want to go beyond the basics, you’ll have to either install or create new blocks. Either way, it requires some extra steps. The problem is that, inevitably, not every block out there will meet our needs. And, despite some tools out there that make block creation easier, there’s still a barrier for some users.

A page builder, on the other hand, generally comes packed with everything you need (along with some things you don’t) right from the get-go. Their plug-and-play nature means that you can get working on page layouts and features more quickly.

#Gutenberg is a half-way solution as a page builder. Click To Tweet

In that sense, Gutenberg feels like a bit of a half-way solution. Yes, it’s got advantages over the old way of creating content. But it isn’t necessarily going to let you do more advanced things right out of the box.

The Divide Continues

From my own experience, mentioning Gutenberg in certain company still elicits a negative reaction. This isn’t always a judgement of the editor itself, but more about the process that led to its inclusion in WordPress core.

As such, this may mean that some people will never fully accept blocks as part of their daily workflow – and that’s fine. Change, regardless of how it’s implemented, is always going to be difficult.

But, even after a year in the wild, the fact that this division still exists is a bit troubling. It may not be enough to slow down Gutenberg’s progress, but it will be part of its legacy. Therefore, I’ve put this in the Cons column, but with hope that it serves as a lesson for the future of WordPress.

The Bottom Line

Whatever your initial opinion of Gutenberg and the process leading up to its launch, it would be hard to deny that the editor has steadily improved over its first year. The UI is easier to use and the new blocks added have increased flexibility. It certainly feels like a much more viable option than it did previously.

As someone who has built websites using both early and current versions of the block editor, I can honestly say that the experience is much better today. Part of this may be that I’m over the initial learning curve. But I also believe Gutenberg’s continual evolution plays a role. It is a different animal today than it was in December 2018.

Yet, I don’t see it as a must-use feature. And, despite all of the fuss, maybe it never ends up becoming one.

#Gutenberg is much better than a year ago. But it's not a must-use feature, and it may never become one. Click To Tweet

So much of working with WordPress is about having choices and deciding your own path. In that way, Gutenberg presents itself well enough. As of now, it’s not going to fully replace a page builder and it lacks the comparative simplicity of the Classic editor.

But Gutenberg does its own thing pretty well. And there’s a roadmap for further improvements. After just a single year, that may be better than we could have reasonably expected.

It will be fascinating to see what year two has to offer.

11 Responses


  • Luke Cavanagh says:

    The block editor still seems very much like a beta product.

  • Kinda getting sick of people saying that those of us who don’t like Gutenberg, don’t like it because we don’t like change. That’s just absolute nonsense. I personally don’t like Gutenberg because the UI is horrible to use and it’s still extremely buggy. And I’m not talking weird edge case bugs, I’m talking common use bugs. Try adding a URL to a button block without the protocol (i.e. http/https) and see how far you get, as a simple example. Or perhaps try selecting the outermost container in a Column Block. It’s almost impossible. There’s no way I’d give this to a client to deal with.

    As Luke commented, this is still very much a beta product, and with approximately 1900 issues still outstanding, it’s got a very, very long way to go before it’s even half decent and semi-reliable.

    • Eric Karkovack says:

      They’d never do it, but Gutenberg should have stayed a plugin until it was more mature. I think if the product we see today was the first core release, it would have made a much better impression.

    • Thebgt says:

      Change is not always good per se.

  • Tim says:

    Hey Eric,

    Agreed with a lot of your pros/cons. I think WP has made the right move in that they’re setting up their API with a ‘agnostic’ approach to a lot of the functionality that should be handled by developers, and then stepping in and fixing major issues as they’re identified for things like buttons, previews, etc.

    It’s certainly made my life easier pitching a custom WP site given that the editing experience is just as good as Squarespace or Wix. Potential clients of ours see the frontend matching the backend, and it’s an easy decision for them to go with WP cause they dont’ want to be locked into Squarespace which isn’t as extendable as WP, and they don’t want to have to have 50 pages of documentation and settings pages to deal with from ‘the old way’ of WordPress admins.

    We developed our own blocks plugin that handles a lot of the complex responsive layouts, and made a few other blocks we use frequently that we felt were missing from stock WP with the help of Bootstrap–and that’s been quite a steep learning curve, but ultimately worth the investment for us.

    My personal opinion given my experience with our clients and end users is that Gutenberg-built pages not only happen faster, but they’re easier to work with long term. Can’t say the same for the sites we built in the past with ACF + lots of fields with the classic editor. Clients still reach out to us constantly with support requests cause they can’t remember what field does what, or they spend hours flipping back and forth from the admin to the frontend to see what’s changed.

    Having a matching frontend/backend editor has made their lives easier and ours, and can’t imagine going back to how we used to build sites.

    • Eric Karkovack says:

      I’m glad to hear it’s working for you! It sounds like you have built a great workflow that lets you use the editor to the max.

  • I run two WordPress sites: my own, on which I use Elementor in the main, and a club on, on which I run with the various incarnations of Gutenburg.

    I get on well with Elementor, and experiment a bit with it for fun.

    I am required to update the club website four or five times a week, so use it a great deal. It has grown on me. More than that, the club members whom I allow their own pages love it. Instead of getting phone calls a couple of times a month to the effect that ‘It’s gone wrong. I didn’t do anything abnormal’ that could often take half an hour to resolve, they now not only do it without problem, I get no requests of ‘Could you just explain that bit again.’

    I change the appearance every year (or so) and it gone through smoothly.

    I’ve had only two occasions when things went a bit wrong, both when adding plugins. One took a fair bit of solving, but the other was simple enough. Given the problems I occasionally had with pre Gutenburg WP, I reckon it’s pretty good.

    It doesn’t beat Elementor, although with the increasing number of blocks available via plugins and updates, it’s improving no end. I can’t see me moving away from Elementor for the foreseeable, but there’s no way I’ll say never.

    It’s improving no end. It looks good. It’s free. I can’t complain.

    • Eric Karkovack says:

      You make a good point regarding the problems/confusion with the Classic Editor. A lot of users want to do more than just write text and upload images in a straight line. Anything more complicated than this could lead to confusion for users.

      At the very least, Gutenberg makes some of this a bit more intuitive. No hacks required.

  • thebgt says:

    They should have introduced this as something completely new, like “New WordPress” or something. But they didn’t dare…
    Change is fine, as long as it makes your life better.
    And Gutenberg makes nothing better, only unnecessary complicated.
    Wordpress TPTB act like if they had never realized who are the users of the platform or like if they do not care and want a completely new target audience. So they screw their users to try something new.
    In any case Gutenberg does not improve anything in WP.

  • This is a very balanced take on Gutenberg. I agree with you that is not a full fledged page builder right now and what’s stopping me from uninstalling my page builder since I cannot create a post template with Gutenberg and also some other stuff like opt-in forms.

    But it has definitely improved the content creation process and I don’t have to use my page builder to create nice looking posts.

    Warm regards,


    • Eric Karkovack says:

      Thanks, Trishan! It definitely feels like Gutenberg is in no man’s land at the moment. It has a lot of positives, but not necessarily enough to dump your page builder.