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?


அக்டோபர் 8, 2019
Just because a developer thinks it has more features, doesn’t mean it works in a real business where people need to get sh~t done and not play with blocks all day. Yes, classic editor was not “powerful” but it was a pure and simple “block” that has what’s needed. Easy to use. Compact. Accessible for non-developers, virtual assistants and productivity fiends. Do not tell me these "features" will actually make my business any $. In fact it's just wasting everyones time AND $. make classic default again! or try gutenberg 2019 and be disappointed AGAIN
அக்டோபர் 7, 2019
Most of these 1 star reviews appear to be content managers who explicitly went and installed something without realising what it was, then got pissy when they broke stuff. Don't believe them, most developers are actually in support of this decision to modernise the WP editing experience. Gutenberg is good, it's clearly the future of the platform and it's actually very easy to develop custom content for, with lots of very powerful features. Certainly miles better than any of the page builders we had before. It's way faster to use as well as being more performant on the frontend and using far more modern methods to output content to the page. If you don't like it, disable it. So many people here clearly haven't even tried to solve any of their problems though, they just see a band wagon and their cave man brain goes 'yes boo change! Me and all my friends here hate this thing'. You and all your friends aren't very good web developers.
அக்டோபர் 14, 2019
Early Gutenberg was bad enough. Now with 6.60 NOTHING works! I have disabled my entire site, every single plugin, and used 4 alternative themes. NOTHING! When I try "ADD NEW PAGE" I get the "WHITE SCREEN OF DEATH." When I hit "EDIT" on an existing page I get "WHITE SCREEN OF DEATH." Sorry to be so harsh but is somebody at least testing this live? Thing is I'm beginning to hate Word Press for allowing this frustrating, UNuser friendly, time killer plugin to hang on. Put Gutenburg and everyone else out of their misery. Let it DIE and just start over!
அக்டோபர் 4, 2019
At the time of this review the Classic Editor plugin - which allows you to go back to the old editor instead of using Gutenberg - has 5+ million active installations and rising, and the Disable Gutenberg plugin has 400,000+ active installations and rising. Gutenberg should be an optional plugin like all other block editors. Adding it to core WordPress and forcing it on us was a terrible misstep. I hope this gross error in judgement will be remedied soon.
Read all 2,904 reviews

பங்களிப்பாளர்கள் & உருவாக்குனர்கள்

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


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



New APIs

  • Implement EntityProvider and use it to refactor the meta block attributes.