Gutenberg is more than an editor. While the editor is the focus right now, the project will ultimately impact the entire publishing experience including customization (the next focus area).

Discover more about the project.

Editing focus

The editor will create a new page- and post-building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery. — Matt Mullenweg

One thing that sets WordPress apart from other systems is that it allows you to create as rich a post layout as you can imagine — but only if you know HTML and CSS and build your own custom theme. By thinking of the editor as a tool to let you write rich posts and create beautiful layouts, we can transform WordPress into something users love WordPress, as opposed something they pick it because it’s what everyone else uses.

Gutenberg looks at the editor as more than a content field, revisiting a layout that has been largely unchanged for almost a decade.This allows us to holistically design a modern editing experience and build a foundation for things to come.

Here’s why we’re looking at the whole editing screen, as opposed to just the content field:

  1. The block unifies multiple interfaces. If we add that on top of the existing interface, it would add complexity, as opposed to remove it.
  2. By revisiting the interface, we can modernize the writing, editing, and publishing experience, with usability and simplicity in mind, benefitting both new and casual users.
  3. When singular block interface takes center stage, it demonstrates a clear path forward for developers to create premium blocks, superior to both shortcodes and widgets.
  4. Considering the whole interface lays a solid foundation for the next focus, full site customization.
  5. Looking at the full editor screen also gives us the opportunity to drastically modernize the foundation, and take steps towards a more fluid and JavaScript powered future that fully leverages the WordPress REST API.


Blocks are the unifying evolution of what is now covered, in different ways, by shortcodes, embeds, widgets, post formats, custom post types, theme options, meta-boxes, and other formatting elements. They embrace the breadth of functionality WordPress is capable of, with the clarity of a consistent user experience.

Imagine a custom “employee” block that a client can drag to an About page to automatically display a picture, name, and bio. A whole universe of plugins that all extend WordPress in the same way. Simplified menus and widgets. Users who can instantly understand and use WordPress — and 90% of plugins. This will allow you to easily compose beautiful posts like this example.

Check out the FAQ for answers to the most common questions about the project.


Posts are backwards compatible, and shortcodes will still work. We are continuously exploring how highly-tailored metaboxes can be accommodated, and are looking at solutions ranging from a plugin to disable Gutenberg to automatically detecting whether to load Gutenberg or not. While we want to make sure the new editing experience from writing to publishing is user-friendly, we’re committed to finding a good solution for highly-tailored existing sites.

The stages of Gutenberg

Gutenberg has three planned stages. The first, aimed for inclusion in WordPress 5.0, focuses on the post editing experience and the implementation of blocks. This initial phase focuses on a content-first approach. The use of blocks, as detailed above, allows you to focus on how your content will look without the distraction of other configuration options. This ultimately will help all users present their content in a way that is engaging, direct, and visual.

These foundational elements will pave the way for stages two and three, planned for the next year, to go beyond the post into page templates and ultimately, full site customization.

Gutenberg is a big change, and there will be ways to ensure that existing functionality (like shortcodes and meta-boxes) continue to work while allowing developers the time and paths to transition effectively. Ultimately, it will open new opportunities for plugin and theme developers to better serve users through a more engaging and visual experience that takes advantage of a toolset supported by core.


Gutenberg is built by many contributors and volunteers. Please see the full list in


How can I send feedback or get help with a bug?

We’d love to hear your bug reports, feature suggestions and any other feedback! Please head over to the GitHub issues page to search for existing issues or open a new one. While we’ll try to triage issues reported here on the plugin forum, you’ll get a faster response (and reduce duplication of effort) by keeping everything centralized in the GitHub repository.

How can I contribute?

We’re calling this editor project “Gutenberg” because it’s a big undertaking. We are working on it every day in GitHub, and we’d love your help building it.You’re also welcome to give feedback, the easiest is to join us in our Slack channel, #core-editor.

See also

Where can I read more about Gutenberg?


If I were a developer

If I were a developer, I would have focused on modernizing the classic editor.
Gutenberg undermines the simplicity and scalability of WordPress.

To make Gutenberg a success, first of all you need to modernize the UI of the Classic editor like Gutenberg. And Gutenberg will have to be offered as an option for the modernly modified Classic editor.

Gutenberg developers have ignored the natural procedure for users to get used to the new editor.

However, I admit that I have put a lot of effort into developing Gutenberg. I will give you three stars.

Wordpress should return to the Classic editor.
Make the Classic editor modern / simple and then release Gutenberg(by optional).


And I’m not typically the kind of person capable of hatred – but this newest update to WordPress (Gutenberg, is it?) – I absolutely HATE!!!

I hate it so much I am inspired to post a hate thread, venting my frustrations – but will WordPress even care to listen to me, to you, to any of us? Probably not.

What they think is best is what goes – and this is going right down the toilet.

The mechanics of this are incredibly clunky, I can hardly make out where what is and what to do, among so many other little hiccups it’s almost impossible to edit any articles.

Normally with new updates and changes, I may be unhappy with it at first but eventually am willing to learn – but not this, I DO NOT see that happening, ever.

When I switch back to using the Classic editor plugin, I seem unable to edit in HTML – and I’m not going through each individual plugin (all highly necessary that I use, same with my theme) to find which is the culprit, WHEN NOTHING WAS BROKE TO BEGIN WITH. I don’t have time for that so why would I do it?!

This new editor situation has me highly irritated and confused and I want nothing to do with it but it would seem I am being forced to learn it or not use my website, which I am building as a career and have been working on upwards of 5-6+ years now.

So annoying WordPress – why would you do something like this to us? Just plain rude.

Needed more testing

I sort of like the idea of blocks but I suspect Gutenberg will be too confusing for my clients. They are just not going to want to learn it, so I’ll probably just hide it and use ACF Fields instead. However, at the moment, there’s no way to hide the new Gutenberg blocks so I’m sticking with the Classic Editor plugin for now. It doesn’t seem like the WP team prepared the WP community for this massive change to the Dashboard. Disappointed.

Absolutely appalling release

Clearly Mullenweg and team didn’t listen (or, more than likely, didn’t care) about the numerous concerns about this release.

From the timing – oh, look, a national holiday! – to the clumsiness, to the breaking of sites, to the absolute terrible UI…. what a mess.

This could be the straw that breaks the camel’s back for anyone concerned enough about WP’s direction to consider other platforms.

Read all 1,854 reviews

Contributors & Developers

“Gutenberg” is open source software. The following people have contributed to this plugin.


“Gutenberg” has been translated into 42 locales. Thank you to the translators for their contributions.

Translate “Gutenberg” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Parser: Make attribute parsing possessive (Fix High CPU usage).