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.

Blocks

This plugin provides 13 blocks.

core/latest-posts
Gutenberg
core/shortcode
Gutenberg
core/rss
Gutenberg
core/categories
Gutenberg
core/legacy-widget
Gutenberg
core/search
Gutenberg
core/latest-comments
Gutenberg
core/social-link-
Gutenberg
core/calendar
Gutenberg
core/block
Gutenberg
core/navigation-menu
Gutenberg
core/tag-cloud
Gutenberg
core/archives
Gutenberg

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

21 An t-Sultain 2019
Isn't there a way to give it ZERO stars? This is the worst thing that's ever happened since I started using, building with, and developing WordPress back in 2005.
19 An t-Sultain 2019
It is very rare when I write a review, but really guys, improve the plugin, do a user testing to see what happens, the most annoying thing is when you work with a blog and have some empty space you must eliminate in several steps because each paragraph becomes a block. Do not separate each paragraph in a different block is very annoying.
19 An t-Sultain 2019
Who thought that removing commonly used features and drastically changing functionality that was working, that people were used to was a good idea? They probably used to work at Oracle. Bring back the classic editor by default.
18 An t-Sultain 2019
Not worth your while. In an age of advanced tools such as Elementor Page Builder, a plugin like this is a complete waste of time...
17 An t-Sultain 2019
I do not understand why the developers replaced the classic editor with this horrible, horrible system. Doing something as simple as trying to insert an image into existing paragraph/text is now incredibly difficult, if not impossible using this system, without employing a whole host of counter-intuitive steps. Blocks is broken. Blocks doesn't work for most people. Gutenberg should not be standard in WordPress. This is one of the worst decisions ever. I guess if your wordpress site consists of graphic memes and youtube videos, this editor makes sense, but for the rest of us who want to add actual information, in the form of text and then worry about formatting later, this editor is an assault on any attempt to create a cohesive workflow that aligns with industry standards. Not everything needs to be modular. This plugin is a failure as a standard. It would make an ok add-on, but the classic editor is what should be in WordPress by default. It works the way most people expect. A whole new user interface in order to figure out how to add/edit content is unreasonable.
Read all 2,877 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

Features

Enhancements

Bug Fixes

Experiments

APIs

Various

Documentation