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?


Should be optional

While I understand the concept of blocks and page builders to compete with the other consumer-level website companies, forcing this new editor causes more trouble than it’s worth. I’ve tried using Gutenberg editor for a few weeks in Beta. I didn’t like it. It’s awkward and frustrating. Pushing this out to website owners unaware and unprepared looks bad for WP and WP professionals trying to manage clients.

Too much “help” is not helpful

I get that the WordPress developers want to “help” people with this new editor. The thing is, it would have been best to add the Gutenberg editor as a tab, alongside the “old” TinyMCE Visual editor tab, and the Text editor tab. Let the user decide what’s best.

In my case, the Text editor is best, since that allows me to know exactly what will be included within the body of a post.

I help manage some 50+ WordPress websites; if all the authors/editors start using the Gutenberg block editor, it’s going to be a huge mess in terms of layout on multiple devices and ad placement.

Changes my code, narrow default window

It automatically changes the code on my pages. It added in dozens of close tags in the wrong spots because of some confusion in its logic, I had to disable it for this alone! Add a setting to disable code completion.

The editing window is incredibly small by default. Probably wise to allow people to adjust this on the page via a handle and then sync the setting so that whatever people leave it at persists between sessions.

Might have been smarter to make this editor change an option… Then test and refine with those opt-in folks rather than forcing the change and likely damaging credibility.

Caption ABOVE photo on posts.

Not sure if this is related to the new Gutenberg but now the caption for the first photo on all of my posts is appearing suspended in space ABOVE the photo and it wasn’t doing this before I updated to WordPress 5.0. Even with the classic editor plug in I have to make an entirely new post to get rid of the caption above the photo. Very frustrating. Please create a way to delete the Gutenberg completely because the classic plug in doesn’t seem to ameliorate its negative effects.

Difficult To Use

I tried to get used to Gutenberg, but I just can’t. Simple tasks seem to take twice as many clicks as before. The whole concept of blocks is ridiculous and unhelpful. I still can’t believe they’re forcing this on everyone.

Disaster….in almost every way possible

The forced implementation of this update and what is represents is a joke! For the many valid and consistent reasons highlighted in this section of reviews on Gutenberg, I am shocked that this even made it out to a production version. PLEASE MAKE SURE THIS NIGHTMARE ENDS!!

Read all 1,819 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).