Gutenberg is more than an editor. While the editor is the focus right now, the project will ultimately impact the entire publishing experience including customisation (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 modernise the writing, editing, and publishing experience, with usability and simplicity in mind, benefitting both new and casual users.
  3. When singular block interface takes centre 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 customisation.
  5. Looking at the full editor screen also gives us the opportunity to drastically modernise 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 meta boxes 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 customisation.

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


Very Disappointing

I am a web developer and have been building sites on WordPress for years now. I love the platform, but this is truly a disappointment and I am very surprised this was something actually released. There was extremely poor responses to your gutenberg plugin people tested before you pushed it out as a core feature… wish you would have listened. Your ‘block’ approach seems to make since when you talk about it, but in practice it is a disaster. It is built very poorly and does not work well with robust page builders such as Beaver Builder, which is much, much, much better than this shabby attempt at using a block builder in place of your very popular wysiwyg. It also does not pull in the theme styles via the customizer and does not allow you to easily edit the html. Please read these reviews and you can clearly see that no one actually likes this change. You can try to argue that it is because the feature is new and something the people have to get used to, but you will be wrong. I have worked on many platforms and the old wysiwyg was such an integral piece of WP that made life easy for both the novice and advanced developers to work with. Now you have ruined it for both sides. Just take it as a very bad choice and go back to the drawing board. Otherwise, people will be looking for better alternatives.

If I could give Gutenberg negative stars I would.

Gutenberg is by far the worst thing to ever happen to WordPress.

I know this is just for the plugin, but I am reviewing the new Gutenberg 5.0. It is terrible.

I used to recommend WordPress all the time to people who want to build their online platform through blogging. I told them “If you can use Microsoft Word, you can use WordPress.”

But no longer.

WordPress is now unusable. It is just a mess.

Delete this.

Why would you for us to use this? And as you can see by the reviews, no one wants this.

what a waste..

took me few minutes to see where to change the permalink of the page.

took me another few minutes to see how to delete a block.

took me.. nevermind 🙂

Really Slow.. Waste of time

Hello all,

Really, just one question to WordPress developers : Why wasting time and energy to create something like this while you know that 70% of WordPress users are Professional coders ! We love use the SIMPLE editor.. without geting this Block features.. blablabla which SLOW down everything.

Plus, why the gutenburg force me to use Paragraphs…and force me to use its own code… i think it’s beter to keep the old editor that all WordPress users are used to… integrate new features is good but keeping the things simple to use is more better…

Best Regards


how do you say “usine à gaz” in English ?

This editor is crap for basic users. It should be included in wp core as an enabling option for more advanced users, with some sens of visual editing

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.



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