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

Unusable and enraging.

Had I not been already using WordPress, experiencing the Gutenberg editor for the first time would have made me switch to using a different CMS entirely. I tried to give it a few weeks, it just became more and more upsetting by entirely getting in the way of how I want to create content.

Great potential but not ready for prime time

Gutenberg is a great concept but it's not ready. Too many plugins aren't ready for it, and the mobile WordPress apps aren't fully compatible. This should be beta for quite some time yet.

Great Design and Bad Performance

Been using Gutenberg for several months now. Love the design concept behind the product. However, using Gutenberg on website can slow the loading of the website greatly. Hopefully this would change in future.

the worst a cms can get

Would go to a zero rating if I could. Gutenberg basically takes all the progress of wp and throws it back to WP and moveable type time. OR any blog that uses markup to layout pages. It kills creative layouts and substitutes them for safe plugin code updates that's easy for the WP team to do. It's so disappointing that WP had done this taken us back to the stone ages in terms of functionality and page layout sophistication. Thank you for killing wordpress.

Horrible. WordPress abandoned users for agenda

This plugin has terrible reviews, and now WordPress v5 has this as the default editor. WordPress apparently no longer cares about what users want. For someone who has been using WordPress since before v2, this is a sad indication of the end of the road for me. I have many sites running WordPress, but I don't think I'll use WordPress for new ones. Sad, because it has been half a decade since I even bothered to look at another CMS and now I am ONLY looking at other CMS options. It isn't so much about problems. I've survived all kinds of things with WordPress. Plugin compatibility used to be a nightmare. White screens could come out of the blue any time. FTP uploading was a routine thing. Truly bizarre and inexplicable things and unpredictable results could happen before the current stable standards were the norm, BUT none of this was intentional. I stayed loyal. All my sites run WordPress right now. But not in the future. When something the community reviews as two stars is made the default, time to accept what we want isn't a goal anymore and sooner or later, the beloved feature will be a liability. Writing posts is an important part of any site with regularly updated content and while I can use a plugin to revert the editor for now, it is just kicking the can down the road if default functionality is simply not what I need. One really has to wonder exactly WHO it is that wanted this editor used at any cost regardless of the terrible reviews. ONLY good thing about it is reusable blocks - and plugins did that before too.
Read all 2,346 reviews

Contributors & Developers

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

Contributors

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

Performance

  • Improve page initialization time by optimizing the addHook function and the viewport state initialization.
  • Improve typing performance by splitting the state tree.
  • Optimize partial application of runSelector.
  • Move selector calls to the event handles to avoid useless component rerenders.
  • Render DropZone children only when dragging elements over it.
  • Initialize variables only when needed.

Enhancements

  • Add error messages to the image block on upload failures.
  • Merge similar i18n strings.
  • Disable clipboard button in file block during upload.
  • Persist alignment when transforming a gallery to an image and vice-versa.
  • Copy enhancement to the embed block help text.
  • Improve the scrolling of the WordPress navigation menu.

Bug Fixes

  • Fix RTL support for the DatePicker component.
  • Change the header level in the BlockCompare component.
  • Show all the taxonomies in the sidebar.
  • Fix the latest posts date className.
  • Fix the “align center” button in Latest Posts block in the backend.
  • Fix block height when DropCap is used.
  • Fix converting caption shortcode with link.
  • Fix edge case in addQueryArgs function.
  • Don’t return the permalink if the CPT is not publicly viewable.
  • Fix error when saving non public CPTs.
  • Properly disable the Publish button when saving is disabled.

Various

  • Show a message in the browser’s console when in Quirks Mode.
  • Improvements to the @wordpress/scripts package: A new a check-engines command, a lint-style command and an update to lint-js.

Documentation

  • Add a getting started with JavaScript tutorial.
  • Document the blocks’ setup states in the design guidelines.
  • Add content to Contributors index page.
  • Improve the components documentation:
    • The MenuItem component.
    • The RadioControl component.
    • The ServerSideRender component.
  • Organise the documentation assets in a dedicated folder.
  • Clarify immutability of the block attributes.
  • Fix the metabox back compat code example.
  • Fix incorrect data module example.
  • Improve the plugin release docs.
  • Remove useless property from the colors code example.
  • Improve the contributing documentation.
  • Fix npm README links.
  • Update the design resources link.
  • Typo fixes.

Chore

  • Run e2e tests with popular plugins enabled.
  • Add new e2e tests:
    • The permalink panel.
    • The categories panel.
    • Blocks with meta attributes.
  • Update node-sass to fix Node 11 support.
  • Move the dev dependencies to the root package.json.
  • Improve the Pull Request Template.
  • More logs to the CI jobs.
  • Code style fixes and expand the phpcs coverage.
  • Disable fragile e2e tests.
  • Avoid PHP notices when running the e2e tests in debug mode.

Mobile

  • Make a simple version of DefaultBlockAppender.
  • Stop using classname-to-style autotransform in react native.
  • Fix SVG styles.
  • Implement Enter press to add a default block.
  • Hide keyboard when non textual block is selected.
  • Fix undo/redo on new blocks.
  • Pass the blockType prop to RNAztecView.
  • Expose unregisterBlockType.