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


New APIs


Add knobs to the ColorIndicator Story.



This plugin provides 14 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?


November 12, 2019
What an absolute mess this editor is. Sure. It looks nice. But factor in these other points: Want to put your content next to eachother? When you align it, the next block's content will just wrap itself next to it if there is enough space for it or not. What is the point of blocks then? Where are the block responsive options? Can't even choose how the layout will be shown on mobile vs desktop! Really basic. Changing a block's HTML will give you a warning or Gutenberg will just delete it Generates HTML output with display:table on it. Why? I will for sure not use this editor ever again to prevent endless hacking and fixing hours.
November 11, 2019
Gutenberg é um grande erro. Sempre existiram page builders e eles sempre funcionaram bem como plugins à parte. Porque forçar isso pra todo mundo? O conteúdo do post (the_content) sempre funcionou bem como um simples campo de edição de textos e mídias, agora ele virou esse monstro que interfere em todos os demais campos. Sei que ainda dá pra usar o editor clássico (e uso em todos os projetos que desenvolvo), mas já estou pensando lá na frente quando eles removerem o suporte. Qual a necessidade disso?
November 11, 2019
Don't bother me with this plugin, we never wanted this...also there are many better block editors. This should be removed from the WordPress core asap.
November 11, 2019
This editor is counter-intuitive and confusing to use. The amount of extra training required for normal users to be able to use this new feature will be staggering. Anyone supporting multiple WordPress clients will have many challenges adapting their user base to this editor. For these reasons, it should be made optional, and users should be allowed to remain on the Classic Editor indefinitely (no EOL date!). As a community, users of WordPress get unwanted, forced updates from vendors all the time. Some of them result in way too much extra work in order to adapt. This would be one of those times. Please listen to your user base and make the Block editor an OPTION. Thanks.
November 10, 2019
I think it works well for blog websites. I've had no issues with Gutenberg so far. If you need something more than a blog, install the classic editor and (optionally) use your page editor of choice!
November 9, 2019
Gutenberg / Block Editor is a great extension to WordPress that allows to build in a much more modern way.
Read all 2,941 reviews

Contributors & Developers

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


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