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?


Awful editor

I get what the wordpress team was trying to achieve with the new Gutenberg editor, and I suppose it probably works great for people who want create media heavy posts with unusual layouts. But the editor has turned into a “What you see is what you *might* get”.

Just writing some text in a nice layout with and image or code block here and there is tedious and far more trouble to get done with the new Gutenberg editor.

No thank you. If this ever becomes mandatory, I’ll happily migrate 10+ years of posts and comments to something that isn’t wordpress.

I totally welcome this

I just tested this on a theme for a client and nothing broke. If the theme is well-written (as when installing 3rd party plugins) then you compatibility issues should not be as bad.

I build WordPress themes/plugins for non-techies and the hoops you have to go through to make sure content is displayed properly takes a lot of time and the end customers still finds it confusing.

The Gutenberg editor might feel weird to begin with but the process for end users to update the website is much simpler. It allows them to create without having to know HTML or to deal with that clunky editor. And get this, things actually appear where they expect – how about that! That old WYIWYG editor was OK for the 90s, but it’s time to let it go.

I welcome these changes and am looking forward to leave behind all the legacy crap I had to write to make my customers happy. Thank you for this and keep up the good work!

very bad editing experience

We don’t need it… time wasting… we have better page builders that works in blocks. this is very bad that many people giving you 1 star while reviewing. You should consider them. you are forcing them to choose Gutenberg. do not like your attitude.

Fatal architectural mistake: Should replace TinyMCE not the editing screen

The idea of Gutenberg basically is great: Providing a standardized block building interface will greatly improve layouting possibilities and compatibility in WordPress. Developers can share their custom blocks and clients finally do not have to use clumsy shortcodes for layouting. To be honest – the time for this has come.

However we think that the Gutenberg project has made a fatally wrong decision regarding its implementation which is also the root cause of most of the bad feedbacks: Gutenberg is designed to replace the post editing screen. In short: Do not do this. Rewrite part of this project!

Gutenberg should be an editor – maybe even a page builder. But you should keep the editing screen as it is – including all the meta boxes, the post update box, the category selection boxes.

Changing this would give the following tremendous advantages:

Perfect Backwards compatibility of existing projects

It would be easy to switch between Gutenberg and TinyMCE per page

Not one single existing plugin is broken except for the ones which directly involve TinyMCE specific JavaScript

Please reconsider the implementation of Gutenberg and think of creating the project this way! It would save 15% of the whole web and countless unecessary development hours!

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



  • Raw Handling: fix consecutive lists with one item
  • Avoid showing draft revert message on autosaves
  • Honor the Disable Visual Editor setting in the Gutenberg editor page
  • Docs: Fix dead links in
  • Fix undefined index warnings in Latest Comments & Latest Posts
  • Add react-native module property to html-entities package.json
  • RichText: List: Sync DOM after editor command
  • Fix RichText infinte rerendering
  • Fix keycodes package missing i18n dependencies