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 customisation (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 modernise the writing, editing, and publishing experience, with usability and simplicity in mind, benefiting both new and casual users.
  3. When singular block interface takes centre 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 customisation.
  5. Looking at the full editor screen also gives us the opportunity to drastically modernise 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 customisation.

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 centralised 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

This is a colossal disaster

Who, in their right mind, thought this could possibly work? The very essence of WordPress has been taken away! Yes, i’ve installed the classic editor and will continue along that path because this interface in not an update, it’s a setback of epic proportions. It just boggles the mind that WordPress would go down this road.

Adversarial Relationship

It feels as if Gutenberg is actively trying to fight me block by block. Things which work a certain way in every other online WYSIWYG editor work differently in Gutenberg. Setting up embedded links present a different behavior for each link. Block behavior is different for each new block.

I’m adding this more as a “me too” than raising any new issues. Gutenberg should be rolled out and WP5 reverted to the Classic Editor. UI and process logic re-evaluated and re-worked. A decent user manual created.

Flexibility required…

Not being one to knock a new interface, especially when it has some obvious improvements for new users, I do have some recommendations for future updates. WordPress is used more and more by web designers because they can offer their customers a non-frightening option. With that in mind the average web designer can easily navigate html. As such a person, I find it an irritation not being able to switch between the two editors. I like to build it then tweek it. Often cutting and pasting html snippets I have in my bag. Now I have to find the correct list to be able to switch over. This is a real time waster.

One of the other concerns I have about this upgrade is that it is steering away from the basic concept of WordPress. WordPress is meant to be a useful framework to hang your options upon. I feel the editor should be a plugin that we choose or reject. I feel on install, WordPress should ask you what editor you would like to use and recommend the preferred plugin. More like the way Themes are handled. Create a page that allows you to select and install your editor, keep it so you can switch between them as you try them out. This way the end users can vote with their feet.

Should be a plugin

I found this new way of writing my post too cumbersome and inefficient. Had to go back to the Classic Editor.
If WordPress is considering to have this vision for the future I think they will need to consider re-evaluate why so many people preferred they in the first place. If I wanted a visual editor I would use another tool, WordPress was different and that was a good thing.

Terrible!!!!!

How to get back to the previous editor? Guterbeg is a disaster.

Regards,

Francisco

Read all 1,883 reviews

Contributors & Developers

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

Contributors

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

  • Optimise isViewportMatch
  • Performance: BlockListAppender: 1.7x increase on key press
  • Date: Optimise the usage of moment-timezone to save some kilobytes
  • RichText: selectionChange: bind on focus, unbind on blur
  • RichText: only replace range and nodes if different
  • Cache createBlock call in isUnmodifiedDefaultBlock
  • Edit Post: Select blocks only once multiple verified
  • RichText: Do not run valueToEditableHTML on every render
  • RichText: Reuse DOM document across calls to createEmpty
  • Only initialise TinyMCE once per instance
  • Optimise the insertion point component
  • Avoid rerending the current block if the previous block change
  • Avoid getBlock in block-list/block
  • Pass the registry argument to withDispatch to allow selectors to be used

Bug fixes

  • Annotations: Apply annotation className as string
  • RichText: Ensure instance is selected before setting back selection
  • Meta Boxes: Don’t hide disabled meta boxes by modifying DOM
  • Fix: Problems on Media & Text block resizing; Load wp-block-library styles before wp-edit-blocks
  • When a post is saved, check for tinymce and save any editors.
  • Fix: Undoing Image Selection from Media Library in Image Block breaks it
  • Add an end-to-end test for the HTML block
  • Fix regression when copying or cutting content in the editor
  • Fix issue where default appender has icons overlaying the text
  • Set document title for preview loading interstitial
  • Fix: Upload permissions error on end-to-end inline tokens test
  • Ensure classic block caret is in correct position after blur
  • Fix tab navigation sometimes skipping block UI
  • Improve font size picker accessibility: Use a menuitemradio role and better labels
  • Don’t show trashed reusable blocks in the editor or front end
  • Rename functions, removing gutenberg_ prefix
  • Add block switcher end-to-end tests
  • Allow links in plugin group in the editor more menu
  • Introduce searching of block categories from slash inserter
  • Convert HTML formatting whitespace to spaces
  • Label link format with selected text, not full text
  • Ensure permalink panel is only displayed when a permalink is allowed
  • Allow the user to convert unembeddable URLs to links and try embedding again
  • Improve the top bar tools interaction and consistency
  • Fix overflowing content in the facebook embed preview screen
  • Add an action to set a category icon and correct block categories documentation
  • Fix: pasting a tag that is part of a transform and not matched ignores the content.
  • Packages: Extract Eslint config package
  • Add end-to-end test to catch revert of title during a preview after saving a draft
  • Avoid react warnings when merging two adjacent paragraphs
  • Avoid PHP notice in the recent comments block