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 CONTRIBUTORS.md.



Bug Fixes





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.

मी योगदान कसा करू शकतो?

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.


Where can I read more about Gutenberg?


Johannes Gutenberg should’ve stay in the 1400’s!

While I'm an old school webmaster that prefers coding sites in notepad, I'll admit my clients prefer WordPress. So, I bow to their request. I admit 15+ years ago when WP came out I was skeptical. Though, I've adapted to it. Having run my own bulletin board system (BBS) back in the late 80's, even I am perplexed by Gutenberg. Sure, they picked a snazzy name (after Johannes Gutenberg who did some printing back in the 1400's), but the difficulty he must've faced is what we're facing with this update to the core. Go back to the previous editor and let others develop plugins like WPBakery, Elementor, MotoPress, the list goes on. For those of you who want to get rid of Gutenberg, this plugin works great for me: https://wordpress.org/plugins/disable-gutenberg/

New writing experience

The new Gutenberg writing experience, is not bad, it's a new way of adding content, and it is more advanced in terms of content unity across multiple editors in your websites. The modularity is very usefull for combining multiple types of content. The problem is that it is not currently polished enough. Our feedback will develop the plugin further more.

It’s has a ton of potential, after you get used to it

I've spent a couple of months getting used to Gutenberg, and I'm pretty happy with it now. It adds a lot of functionality for which I used to have to use separate plugins. Not everything works perfectly... it will take a little time for theme developers and plugin developers to make the switch, too, but overall, I like it now.

Can you say Netscape?

Gutenberg is the worst editor I've ever worked in. I might as well be using Netscape from the nineties or the old Adobe Go Live. I'd get better results. This was not well thought out at all. Time for me to say goodbye to WordPress. The original editor is being supported til 2020, but I'm out now. It was fun. Why not just expand on the existing? Developers think we all want change, not really, I just want consistent upgrades and new features. Gutenberg is not worth my time. If I could give 0 stars , I would.

Not good

If I could give this zero stars I would, this is probably the biggest disappointment and it hasn't gotten any better. I have trouble writing, typing, using code, and trying to make the size in my browser mess it up and not at all usable. It's not user-friendly at all, and the fact that everything is a block, why? I can't use any shortcuts correctly and if I try to use code it messes it up. I dislike that word count was hidden when it has always been right there in the original editor. Trying to convert to gutenberg from the original editor is a mess, and messes up things. I've used WordPress since 2011, and if this is the future than that is a shame.
Read all 2,744 reviews

Contributors & Developers

“गुटेनबर्ग” is open source software. The following people have contributed to this plugin.


“गुटेनबर्ग” has been translated into 44 locales. Thank you to the translators for their contributions.

Translate “गुटेनबर्ग” into your language.

Interested in development?

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