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

Keep WP gutenberg-free

Please, do not add another layer of abstraction. Specially when it is only bound to React.
KEEP WP DEVELOPMENT free from Gutenberg.
As a optional plug-in is fine.

Not in the core please!

The idea itself is good. However, the implementation is outdated and, in my opinion, even suitable to permanently damage WP as a platform. As PlugIn okay, but please not in the core.

Time for a WordPress fork?

We have invested hundreds (more like thousands) of man hours into making WordPress work just the way we like it and have reached a point where we can design and build bespoke websites in a matter of hours with very powerful features. We’ve baked all of this in using the hooks, actions and extreme amounts of customisation that we’ve all come to love at the core of the of WordPress.

Having looked at Gutenberg, the issues posted on Github, the reviews on here and the seemingly laissez-faire approach by the Gutenberg team towards the push back by the community I can only hope that a WordPress fork appears at 4.9. We have to upgrade WordPress to keep up with security issues, but this force feeding of Gutenberg is like the Windows 10 saga all over again – forcing changes that nobody wants.

Gutenberg is bringing in so many breaking changes to WordPress I can only imagine the cost to businesses across the globe. I wouldn’t be surprised if it is in the tens of millions in lost revenue.

Please please please don’t merge this into core. Listen to your users – make it a plugin, turn it on by default if you must, but please make it optional.

I’ve got hopes but it’s not ready yet

I get it why WP wanted to update their editor. I’m all for change and keeping up with the times. Gutenberg does well in terms of overall look of it. I have hopes that it will get better and I’ll gladly update my rating if it does. As of today though, it fails in my book on these points:

1. Ease of finding features – some editing features are not where I would expect them to be and take a long time to find.
2. Basic editing is not so basic – I imagine that people brand new to web editing will have a hard time getting started. From adding blocks to editing text – it’s counterintuitive.
3. Still buggy – From latest WP update I gather that they want to push for a lot of developers to start using it already. But the plugin still has a lot of issues. How can you push a product knowing that it’s not good?

An editor is not good when only parts of it work well. That’s it. There’s no gray area here. If you’re frustrated because you’ve looked for something for an hour and can’t figure it out, it results in a bad experience. It doesn’t matter that some of that time everything else worked wonderfully. People remember only the bad.

I’m reminded of the first website I built many many years ago. No prior web dev experience. The crude editor of the free web host easily guided me through the steps and I had a site up immediately. Once I was ready for HTML and CSS, it was super easy to edit straight from the editor. Simple flip of the tab.
And compare it with all the steps I had to go through editing a WP site today. I hate to sound so cliche but I miss the good old days when web development was easy. We have so many better tools now and yet they didn’t make it easier at all.

Watch out, WP. Your “build your site in minutes” selling point is going to suffer if you don’t improve Gutenberg before adding it to core.

Make it easy again.

Suffering of Peter syndrome

After using Gutemberg, just one word : RUN, or AVOID, or QUIT, or ESCAPE…
I have no words to describe how sad I am.
WordPress WAS so smart, so usefull.
WHY this WordPress suicide????
Better is enemy of good, and Gutemberg illustrate the suffering of Peter syndrome of the team.
And I look for another CMS…
R.I.P. WordPress ! We loved U so much!

Love the new editor

The Gutenberg editor is the right step forward for WordPress. This editor is much more flexible and it’s easier to extend with custom blocks. There are still some small bugs but they didn’t bother basic use of the editor. I’m looking forward to seeing the editor pushed to the WordPress master branch.

Thanks to the WordPress developers and all who worked on Gutenberg.

Read all 559 reviews

Contributors & Developers

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

Contributors

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

Latest

  • Add new Archives block for displaying site archives.
  • Add new Latest Comments block to widgets category.
  • Add “Convert to blocks” option in HTML block.
  • Correct caret placement when merging to inline boundary.
  • Move block switcher from header to multi-block toolbar for multiselection.
  • Add video block attributes for Autoplay, Controls, Loop, Muted.
  • Remove HTML beautification and preserve whitespace on save.
  • Formalize RichText children value abstraction.
  • Allow transformation of image block to file block and vice-versa.
  • Support preload attribute for Audio Block.
  • Avoid popover refresh on Tip mount.
  • Introduce “registry” concept to the Data Module.
  • Convert successive shortcodes properly.
  • Hide “Convert to Shared Block” button on Classic blocks.
  • Update spacing in pre-publish panel titles.
  • Use do_blocks to render core blocks content.
  • Remove restoreContentAndSplit in RichText.
  • Hide insertion point when it is not possible to insert the default block.
  • Refactor block converters to share common UI functionality.
  • Replace the apiRequest module with api-fetch module.
  • Add audio/video settings title to settings panel.
  • Normalize the behavior of BlockListBlock’s “Enter” key handling to insert the default block.
  • Rename baseUrl entities property as baseURL in entities.
  • Rename UrlInput component as URLInput.
  • Give File block a low files transform priority.
  • Make tooltips persist when hovering them.
  • Optimise design of heading line heights.
  • Add a filter(‘editor.FeaturedImage’) for the FeaturedImage component.
  • Fix vertical arrow navigation skips in writing flow.
  • Fix incorrect polyfill script handles.
  • Fix template example so that it is correct.
  • Fix exception error when saving a new shared block.
  • Fix getInserterItems caching bug and add new test case.
  • Fix issue with spacer block resizing and sibling inserter.
  • Fix files configuration entry in package.json for wordpress/babel-preset-default.
  • Fix config and regenerate updated docs.
  • Fix dependency mistake in api-fetch.
  • Fix metaboxes save request (parse: false).
  • Fix issue with name field not being focused when a shared block is created.
  • Fix box sizing for pseudo elements.
  • Fix an error which occurs when assigning the URL of a Button block.
  • Improve usage and documentation of the landmark region labels.
  • Substitute the remaining uses of unfiltered_html capability and withAPIData.
  • Remove the “Extended Settings” meta box wrapper.
  • Remove NewBlock event handling from RichText.
  • Remove legacy context API child context from Block API.
  • Remove Text Columns block from insertion menus in preparation for Try outreach.
  • Remove unused autocompleter backcompat case.
  • Change label in Cover Image block for background opacity.
  • Change the text label on Image block from “Source Type” to “Image Size”.
  • Backup and restore global $post when preloading API data.
  • Move packages repository into Gutenberg with its history.
  • Enhance the deprecated module to log a message only once per session.
  • Switch tests away from using enzyme (enzyme.shallow, enzyme.mount, etc).
  • Unblock tests from being skipped.
  • Add basic test for shortcode transformation.
  • Add e2e test for block icons.
  • Add e2e tests for the NUX tips.
  • Add e2e tests for shared blocks.
  • Remove data-test attribute from UrlInputButton output.
  • Deprecate id prop in favor of clientId.
  • Rename MediaPlaceholder onSelectUrl prop as onSelectURL.
  • Remove unnecessary default prop from test.
  • Point the package entry to src directly for native mobile.
  • Use clearer filenames for saved vendor scripts.
  • Update local install instructions and add add more verbose instructions when node versions don’t match.
  • Reorder package.json devDependencies alphabetically.
  • Coding Guidelines: Prescribe specific camelCasing behaviors.
  • Regenerate docs using docs:build command.
  • Add documentation for ALLOWED_BLOCKS in Columns.
  • Add link to support forum in plugin menu.
  • Deprecate buildTermTree function in utilities.
  • Deprecate property source in Block API.
  • Deprecate uid in favor of clientId.
  • Deprecate grouped inner blocks layouts.
  • Improve eslint checks for deep imports.
  • Improve IntelliSense support when using VS Code.
  • Move the components module partially to the packages folder.
  • Add the blocks module to the packages folder.
  • Add wp-deprecated dependency to wp-element.
  • Add @babel/runtime as a dependency to wordpress/components.
  • Add @babel/runtime as a dependency for packages.
  • Add a new compose package.
  • Extract entities package.
  • Extract viewport package.
  • Extract @wordpress/nux package.
  • Create new spec-parser package.
  • Update Dashicons to latest build.
  • Update test for babel-preset-default.
  • Update code to work with Babel 7.
  • Update package-lock.json with eslint-scope version 3.7.3.
  • Update node-sass.