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?


This solves wpautop and introduces many cool features.

There are a lot of negative reviews on here, most of which are from developers who are worried about this ruining WordPress. For those who are afraid of this change, STOP WORRYING, I’m a developer and I love coding my pages without page builders, I’ve tested Gutenberg and it is very versatile, it allows you to build pages like you used to, you can switch to code view and do your work in there or use the classic block if you prefer to build in tinymce.

Gutenberg has a block called Custom HTML which will render your HTML exactly as you enter it, NO MORE RANDOM P TAGS OR BREAK TAGS. Copying and pasting from MS Word works great, you can copy the whole thing and paste it in and Gutenberg will drop them into their own paragraph blocks.

All in all, no complaints, we get the best of both worlds, we can still work with the pages like we used to OR use the blocks. Most exciting of all is the dynamic block which allows you to pretty much convert your complex shortcodes in a block with options, as you change the options the block will dynamically update so you can see what each option will display on the output.

Please don’t force this into the core

I realize you all have worked quite hard on this, but please don’t destroy WordPress by switching to this. For those folks that don’t know how to code and want to use a page builder, fine… offer this as just one of the many page builder plugins that are available. As a coder/designer with very demanding clients it is simply not going to be possible to create the sites they are expecting, and the amount of time wasted clicking buttons and options in order to get anything done is just too inefficient and frustrating since it never seems to actually achieve what I’m attempting to build.

In addition, my clients are not going to pay to have their sites rebuilt just because someone decided to mess with things, and if forced to give up several months or work doing redesigns for free my business will be destroyed and I won’t have a roof over my head.

There is a reason that WordPress became the most popular CMS for both designers and our clients. As the saying goes, «If it ain’t broke, don’t fix it!»

Please, not in the core! You should leave it as a plugin

Hi Gutenberg devs,

I’m leaving this review because I feel that this is not a good move by the wp team.

There’s no need to make like Wix, Weebly or Squarespace. You guys provide that service through Why risk to break millions of websites just to add this «builder» in core.

There are a lot of free page builder in the WordPress Repo like Elementor, Beaver Builder Lite, SiteOrigin Page Builder, etc … and these plugins are way more powerful than Gutenberg.

You guys should listen the community. Look of the rating and you all can understand what the majority of users think.


Will be to cumbersome to use for high volume content creators

Gutenberg is still too cumbersome to use for high volume content creators.

Having blocks for every paragraph means that the screen to too cluttered for composing and editing extensive posts. The classic editor view produces Javascript errors, as do using some blocks in the Gutenberg editor mode. Media inserts do not appear available in the classic editor blocks.

Please do not add Gutenberg to core, OR create a fork for high volume, content, enterprise users with the old editor.

Also, we have made extensive additions to the old editor. This is going to cost us an insane amount of money to rework for Gutenberg. We might have to switch to another platform or go out of business. It might be easier to write our own platform!

Посмотреть все 502 отзыва

Участники и разработчики

«Gutenberg» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники:


«Gutenberg» переведён на 27 языков. Благодарим переводчиков за их работу.

Перевести «Gutenberg» на ваш язык.

Заинтересованы в разработке?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Журнал изменений


  • Fix regression in Columns block’s front-end style
  • Fix regression in SVG support for block icons
  • Build tooling: Add linting for package.json files