Gutenberg

Description

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

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.

Compatibility

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.

Contributors

Gutenberg is built by many contributors and volunteers. Please see the full list in CONTRIBUTORS.md.

FAQ

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

Where can I read more about Gutenberg?

Reviews

Such a disappointment

The Gutenberg editor should have been an option not a forced change enacted upon WP users. From my experience most WP users enjoy working on the nuts and bolts of every part of their website/blog/ecomsite. Gutenberg obfuscates and confuses the prior classic editor layout. I was quite happy knowing my around the classic editor. It gave me one more powerful tool that I knew well enough to construct deployment ready pages. Now the primary tool for my page construction has been changed and it forces me to relearn a new tool. Nothing wrong with learning something new - I do it all the time - but if it ain't broke don't fix it! Now instead of "my old trusty hammer" I am force fed "a fisher-price rock" that looks like a hammer but just has a bunch of blinky lights and whizzy noises on it. Had to install the Classic Editor plugin on all my sites.

So bad

I have issues updating pages. Not to mention poor usability.

Horrible!

Why in the world was this awful editor forced on WordPress users? On all of my sites, I had to install an app in order to use the classic editor.

Dreadful

I lost count of the number of things Gutenberg messed up. I love WordPress but this was my worst WordPress experience ever. This is a failed project, take the one star hint and put classic back by default and make Gutenberg a plugin only option.

Why?

I genuinely tried to like it. That's a problem. At no point did I feel like I wasn't forcing myself to find some value in it. I waited until I started hearing that it was usable and tried again. The state and direction of the whole thing makes me question why this is a thing. I wouldn't care if this were just a plugin but considering it's part of the core and been shoved down everyone's throat means I have to care. That and the classic editor will be supported for so long. The new editor takes what was done with the classic but with extra steps. Shoving everything into the sidebar kills productivity for me since what took one click is now hidden in unnecessary sidebar panes. It's removed the new page/new post button and now I have to find it in the dropdown. The code editor button is in an inconvenient place and is about 1/3 of the overall page width for... reasons? I'll admit I don't focus much on accessibility, but its quite literally a dumbed down classic editor with extra steps. Editing text is quite difficult since there are suddenly rules to what used to be a freeform editor. I'm not a huge fan of the tinymce but this made me appreciate it so much more after forcing myself to use Gutenberg a few times. I've seen endless posts praising it and stating that this needed to happen but, again, why? What's actually been accomplished here? I've seen people compare it to a competitor to wix or squarespace but it genuinely isn't. From a market standpoint the rating alone should deem it an overwhelming failure. Anyway, I don't think the thing should be abandoned by any means because there are some people that genuinely love the thing. That's awesome. That's the beauty of wordpress plugins and wordpress as a platform. I love using Elementor for some sites, for example, but I wouldn't force it into the core.
Read all 2,684 reviews

Contributors & Developers

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

Contributors

“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.

Changelog

For 5.4.0.

Features

Enhancements

Bug Fixes

Documentation

Various