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?

Vi vil elske at høre på jeres fejlrapporter, funktionsønsker al anden feedback! Fortsæt venligst over til GitHub problemside og søg blandt eksisterende problemer eller opret en ny melding. Selvom vi forsøger videresende problemer rapporteret her på pluginforum’et, så vil du få meget hurtigere respons på (og reducere dobbeltarbejde) ved at holde det hele centraliseret på GitHub repository.

Hvordan kan jeg bidrage?

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?


Bullshit plugin

This is the worst plugin I have never used. Bullshit!
We own the right to use it or not, wordpress just fucked it up.

Do not shove things on people throats

Dear Automatic you’ve fucked up.

I’ve got to sad point where I had to postpone your update since it’s a bad direction enforcing it on people, since it will basically break all of my client’s websites.

The direction it’s good, Guttenberg looks awesome, but not when you shove it on people throats and there’s no way to reverse the process without a version roll back.

How come ? Well I have to deal like everybody else with clients that already have procedural steps on working their websites. And people love changes. Even with my younger editors that are in their late 20’s, so they were born in technology, they are functional technologically impaired and they barely know how to use the Classic Editor since it looks like Office Word. And I’m fwcked since I did some hands on test case and they look at the editor and none of the current functionalities are intuitive anymore since there’s no relatable env like the gutenberg editor.

So the problem it’s not the editor, it’s the Automatic making a idiotic and incomprehensible decision to force the gutenberg editor.

Now why wouldn’t I just change to Drupal or Octobercms ?

We want to CHOOSE what we want to USE!

Beyond that this new future is useful or not; I think this policy that makes people to adapt themselves (without the choosing rights) to new situations is going to somewhere bad!.. its like to bulling people who make them great! they should know they are great because we want to! not aliens!

What is this #&%$?

Please remove this editor from WP, keep it as separate plugin for people who really want it. It is crap.

I want to be free to choose!

Why not develop a controll panel to let me disable all the crap you put in WP: rest API, xmlrpc, embed, emoji, … WordPress is not Facebook!


I updated to version 5 and then all of a sudden I couldn’t see anything else but the disaster that is gutenberg.

Editing via blocks? Really? There’s a reason why I’m on wordpress and not on wix.

Gutenberg should be an option and shouldn’t be forced down our throats.

It’s bad. Divi is way more awesome. What gutenberg should be. And I don’t even use divi!

Thank goodness for the classic editor plugin! It removed gutenberg and then showed the previous format again. There’s also another plugin I saw which is named remove gutenberg or something that I haven’t tried yet.

Really, really, really hate it!!!

Got to give it 1 star because I cannot give it no stars! This is a huge cock-up and so irritating. I now have to install editor plugins across a hundred sites. Why not leave it as a plugin. I have used WordPress for 11 years and this is the worst thing that has ever happened!

Read all 1.804 reviews

Contributors & Developers

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


“Gutenberg” er blevet oversat til 42 lokalområder. Thank you to the translators for their contributions.

Translate “Gutenberg” into your language.

Interested in development?

Gennemse koden, tjek SVN repository, eller abonner på udviklerloggen via RSS.



  • Parser: Make attribute parsing possessive (Fix High CPU usage).