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 13 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?


October 21, 2019
I had high hopes for gutenberg but after using it a few times to get the hang of it, I couldn't get over how clunky and mundane it is. Blocks for everything, it's not user friendly, and it doesn't even work well with most top notch themes (i.e Enfold). I normally always switch to classic mode and I feel like gutenberg should be phased out and rolled back to classic. What was even the point of this though? I've used the advanced visual builders for Enfold and i've dove into Visual Composer(not my favorite) and Elementor (the worst one of all visual builders i've used in my life time)..Gutenberg is down there. I really really really tried..i really tried to love it and use it...but it just not friendly at all...Sorry wordpress!
October 21, 2019
Gutenberg is still difficult to use and not powerful. I'm always using the classic editor. Not because using blocks is bad : I often work with Elementor, Divi and so on. Gutenberg brings too many troubles. Just few examples : 1) A block per item. Why do we have to create a new block each time we had an element ? An image => create a block. A title ? Create a block. etc. 2) auto empty block Really often, it creates empty blocks for paragraphs. To delete them : change the block into something else, then delete. 3) Past from a text editor Work, collaborate, share articles with people and work off-line first (Word ...). With the classic editor : copy / past, and it's done. With Gutenberg : it adds blank spaces, we have to check each paragraph to find and delete them. 4) design Happened many times : impossible to correctly manage a simple alignment of a picture. Switch to classic : 1 click, done. Note : I tested Gutenberg since the beginning, and I still try to use it. Tested with many popular themes, always the same issues.
October 20, 2019
Personally I like it! This builder is absolutely in time!
October 19, 2019
I wrote a bunch of custom Gutenberg block-types this past year, and I am extremely happy about the results. Because clients can implement the functions that I make in their own way, it saves me a lot of time. 4 stars because the development documentation is still lacking. I have to check the source code a lot of times to find out how certain block-types should be made.
Read all 2,915 reviews

Contributors & Developers

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


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



Bug Fixes