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

Întrebări frecvente

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?


Great future with Gutenberg

I have to say that I’m looking forward to have a brand new user experience with Gutenberg. I already have two sites in production with Gutenberg and custom blocks. I’m big fan of React.js and WordPress and with Gutenberg I can build great user interfaces for page and custom post types editor. Cool and keep going! On the other hand I have to say that Gutenberg API is not stable, but hey, it’s not intended for production use at the moment, so it’s ok 🙂

Some suggestions

You are adding visual interface to the editor but they are in different places, it should be a bit handy. Maybe a drop-down above the editor.
While it’s good that you have added the visual part but it would be better if it can be a third tab in addition to the current two.
I would also request you to make the border more prominent, I keep low brightness and contrast to reduce strain on my eyes and I was not able to distinguish the border.

Going to be good

I see that lots of developers don’t want something like this and they think this is going to ruin their past works. I don’t think it is going to efect anything like that. I install it and test it a little. It seems it is just going to be a page builder just like others. Also, it is not going to be bad for the new projects. If you are a page builder user and creating a site with that to your customers and don’t want something like that I can understand. But this is going to be the same thing.

Content creating and template creating are different things. So a free plugin like that will improve the WordPress and I think we have more customers soon. Thanks and good luck with the development 😉

Better as an optional plugin

I Think this is an interesting effort, but it might be offered as a plugin, it does not make sense forcing everyone to use it. Specially if it’s going to break custom metaboxes and custom fields.

Citește toate cele 507 recenzii

Contributori și dezvoltatori

„Gutenberg” este un software open source. Următoarele persoane au contribuit la acest modul.


„Gutenberg” a fost tradus în 28 de locale. Mulțumim traducătorilor pentru contribuția lor.

Tradu „Gutenberg” în limba ta.

Te interesează dezvoltarea?

Răsfoiește codul, vezi depozitarul SVN, sau abonează-te la jurnalul de dezvoltare prin RSS.

Istoric modificări


  • 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