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

Vanlege spm.

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 for beginners and simple to switch!

I like it! Gutenberg is a big step forward. Makes it really easy for newbies and takes just some minutes for the advanced to understand the concept. There is even a "classic" block, for those who don't want to say goodbye to the old stuff.


when my wordpress sites started automatically changing to the new block editor, i was not particularly pleased but i thought ok let's give it a try and see what the benefits are. but after a couple of weeks of testing it out, i'm installing the classic editor plugin and returning with relief to the former interface. i can't think of a single thing that the block editor makes easier for me. inserting and moving images is far less intuitive and easy than previously, when all i needed to do was put my cursor where i wanted the image and click on the add media button. if i decided it wasn't in the right place, i could simply drag and drop the image into the new place. with blocks this isn't possible. first i have to manually divide my text to make a new block, then i have to add a block, then add the image, then align it to make the text wrap around. then when i realise it should be further up or down in the text ... not possible to simply drag and drop it!! not possible to use the arrows to move the image block up or down - because now it's embedded into the text block. the only solution i found was to delete the image and then go through the process of reinserting it elsewhere. what a waste of time. i can't see any benefit or reason for making paragraphs be separate blocks. maybe this is somehow easier for newbies, but it's hard to imagine how, when most people are already familiar with text editor applications that resemble fairly closely the classic wordpress editor. i really cannot see how blocks offer any improvement over the normal kind of editor. and as someone who also works quite a lot with drupal, it introduces confusion as blocks in drupal are something else altogether. maybe this is where wordpress has taken the idea of "reuseable" content blocks from - but that shouldn't mean that every bit of content becomes a block. i mean seriously, how often do you want to repeat the same paragraph of a blog post somewhere else? please make the block editor an option, not the default.

A big step in the wrong direction

I develop websites for clients. WordPress is one of the main ways I build sites. But with Gutenberg building a site has become a steeple chase instead of a race on flat ground. Of course new things always make for a period of adjustment. But it's not just the fact that Gutenberg is still buggy, there is a larger problem: If I want a website development system that is 'easy to use' but a bit restrictive, I'd build websites on or similar services. Wordpress used to be flexible and highly customizable. This is now a thing of the past. I am constantly fighting the UI, trying to get CSS code implemented without breaking stuff, trying to get the lay-out I want, then having to give up because it just doesn't work. As far as I am concerned, Gutenberg is best buried and forgotten as quickly as possible. It is not the revolution it's name implies. It's a devolution.
Les alle 2  540 omtalar

Bidragsytarar og utviklarar

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


“Gutenberg” er omsett til 44 språk. Takk til omsetjarane for bidraga deira.

Omset “Gutenberg” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.





Bug Fixes