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?


Ruined WP

Why they did it. WP was a great before Mullenweg forced his stupid ideas.

Gutenberg is great

The idea and implementation of Gutenberg is great. Developer who have less JS skills will definitely have face a lot of problems but that's a thing that you can't ignore JS. The only bad thing about Gutenberg is its Documentation.

I hate it!

It might be a good tool for total newbies, but if you're serious about site building you just need to know some html and css code. Trying to avoid that with building blocks just limits things for serious builders. You should have done it the other way around: leaving the old editor and bringing the Gutenberg as a plugin for the newbies. Now serious builders need to install a classic plugin? Really? anyhow, I installed the classic plugin

I.Can’t.Believe.This! @_@

You could have at least provided us with an option on whether or not we want to use Gutenberg or simply stick to the old editor. That's instead of forcing Gutenberg into our interface knowing that we need to learn how to use it. We can learn new things, and it is common knowledge that change can be initially met with resistance. But not giving us time to tinker with a new thing while making the old thing still available? That's a blow to our productivity and our efficiency. I've been used to WPBakery, and right now from what I've seen, I can tell that it's way better than Gutenberg. Now, I'd have to download the Classic Editor plugin - an extra step that would have been avoided if you didn't feel it necessary to fix something that's not broken.

Moving backwards, not forwards

The update to Gutenberg has been nothing short of a head ache with the only bright side being that my production site's content is currently intact. However, I'm unable to edit any of it due to the insistence by Gutenberg's code changes to decide how I want my content formatted by removing p and br tags and adding p tags where it sees fit to replace. Stuff. This has, much to my annoyance, added additional work to a website overhaul I have been working on as now I have to go back and touch every page an effectively redesign them to work around the idiocy that is Gutenberg and its decisions on how my content is formatted. So, THANK YOU for telling ME how MY CONTENT should look on MY WEBSITE.

Major productivity blocker

I've been patient, really patient. I gave this a chance to proof itself for 2 months. But my conclusion is clear: It doesn't work. The idea behind is great, but the implementation is horrible. It actually prevents me from writing end editing content. Quick keyboard/mouse switches are made a tedious process. It's almost impossible to work quickly and precisely at the same time. The ever distracting UI items popping up in the middle of my content are supper annoying. Multi-paragraph selection turns into a luck thing. Sometimes it does what you want, sometimes it doesn't. Folks, no professional can work like that. We all have better things to do than to continuously bend our minds trying to figure out what the editor wants from us. Honest advise: Get rid of that thing quickly before it leads to a disaster, or start over from zero again.
Read all 2.548 reviews

Contributors & Developers

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


“Gutenberg” has been translated into 44 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.





Bug Fixes