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


This plugin provides 11 blocks.



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?


August 17, 2019
I normally never leave 1 star ratings, let alone rate any plugin, but I couldn't stand to just give my honest feedback about this complete nightmare called "Gutenberg". I am a developer and have many customers, and there are just so many conflicts and issues with so many plugins, it's just terrible. The very first thing I will do for each WP install will be to install the "Classic Editor". I really do hope they will not go through with this "Gutenberg". I understand the devs did a lot of work and put new technology to the test, but honestly don't break things if they work. I expected a lot of this gutenberg year ago, but didn't expect it to be this buggy. Another really anoying thing is that if you are developing a simply shortcode and do a "var_dump()" you can't even Publish the page anymore...
August 16, 2019
Odeio esse editor Gutemberg, não é intuitivo, é confuso. Só me dá um trabalho extra de sempre ter que instalar o Editor Clássico para ser compatível com temas e outros Plugins. Tinha que ser opcional.
August 16, 2019
Gutenberg is not intuitive, at all. Its difficult for my clients. I don't know why such a drastic change was made to something that didn't actually need it.
August 16, 2019
For those who continue to give one star reviews to the new editor because it either breaks your site, is totally different, too many problems, too long to learn, or you just dont like it - I say please take a moment and recognize that not only is this a full codebase rebuild, but you also have the ability to stay within the realm of the Classic Editor until 2022. That's pretty incredible to be able to do that. Furthermore, you have enjoyed an incredible management system whose original codebase effectively goes back to 2008. Gutenberg is the future. I already have teams and clients using it and *wanting* to use it. We are already building custom blocks and plugins that support frameworks we use for our sites, that honestly, we were not inspired to do with the old system. Welcome to the new.
August 15, 2019
I read a lot of bad reviews about Gutenberg, but try using it and be open-minded. Gutenberg is great. I know it's overwhelming at first sight. If you use a WordPress builder like Divi, I think switching here might be troublesome, not sure... haven't tried that... But building a NEW website from scratch using Gutenberg is a GREAT choice, with the Gutenberg blocks plugin, it's super easy to CREATE professional web pages without a WordPress builder, at all... So from now on, whenever I build a new site, especially if clients would permit me to use my resources of choice, I would prefer Gutenberg! Thanks to the plugin developers!
Read all 2,837 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.





New APIs

Bug Fixes