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?

Mācā ulang

Agustus 24, 2019
After I activated Gutenberg, I wasn't able to edit via the customizer. When I turned it off, regained functionality. Totally useless as is.
Agustus 24, 2019
I really gave Gutenberg a shot, but it's just about the worst writing-editing tool I've ever seen in my life. It is also the most inflexible editor in the history of mainkind, and it was easier to format in DOS Word. Even incredibly basic stuff like line spacing is totally broken, and there was no way I could get 2 line breaks between headers no matter how many times I hit "Return" or "Shift-Return" - I even edited in <br> <br> using HTML and Gutenberg deleted the code once I went back to the Visual Editor. What the hell? Hey guys, ever heard of WYSIWYG? If I want 200 spaces between headers I need to get 200 spaces between headers - instead I get what a pile of "change for the sake of change" nerds decided I should get, which is a hardline piece of bloated crap designed for morons. Again, WYSIWYG, What You See is What You Get - that is a tenet of web publishing and is impossible to achieve in Gutenberg simply because the "Visual Editor" is exactly the opposite and nothing you see visually will actually turn out that way in the published article.
Agustus 23, 2019
Lo peor que le pudieron hacer a wordpress. Deberían tener verguenza de su penoso trabajo.
Agustus 22, 2019
The thing literally is not intuitive. Drag and Drop features are inconsistent, not well marked, you have to hoover and play hide-and-seek to find things. How WP decided to go with a still under developement editor is shocking to me? Why? Gutenberg still needs a lot of work before I would let any of my clients on it. The likelihood of something bad happening is high. If I could help you, then I would steer you AWAY from enabling Gutenberg on your site for now. It will cost you time and money. There are better builders out there, even the old classic builder is better than Gutenberg still. I am not being a hater, I am stating facts and other reviews prove it. Gutenberg is a step BACKWARDS for WordPress. You can argue that point all the way to the unemployment line, because that is where you will be if you try to use it for production sites and legit brands. We need a more intuitive user interface, specifically related to site structure elements like ROWS, COLUMNS, AND SECTIONS. We need Gutenberg to start using the right terminology in the first place, a column inside a column inside columns is not working. You should be using the terms "ROW" or "SECTIONS" and then "COLUMNS" within that. The way you have it makes no sense and the user interface makes working with it a horrible experience. Don't use it yet, wait until they fix it or ditch it...
Agustus 22, 2019
I'm not saying that other page builder plugins have got it totally right but most of them have nailed variable column widths.
Read all 2.847 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.

Caathetan Owahan




New APIs

Bug Fixes