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

A step in the right direction

After my limited testing today, I’m less anxious about what impact Gutenberg was going to have on our development workflow.

From what I can see there will practically be no change for us, but the editing experience will be more robust for clients. For years it’s been far too easy for a client to accidentally delete a shortcode or malform some HTML in the old editor, and problems like that could be mitigated with the new block editing experience.

The Drop Cap option is an odd choice though. If you’re going to have that, why not pull quotes as well? And perhaps other magazine layout tropes? That sort of thing is like cat-nip for content creators. I picture a world where suddenly every WordPress website is going to be drop cap city.

As for the core vs plugin argument, I’m on the fence. Either way won’t have any meaningful impact on our development workflow, but I can understand why developers who rely heavily on page-builders might take issue with this being in core.

That aside, I like what I’m seeing so far.

Resistance Is Futile

I thought that devolution is abstract word until i tried this. While great creative people made exceptional advances in page builders in 2018, this unusable half-product is forced upon us leaving real scent of 15th century. The team behind it is convinced that system of blocks is so modern and progressive. Well newsflash….the way you made it is terrible and dysfunctional no matter what you believe in. The fact that you’re still forcing it upon core despite numerous pleads to do otherwise reminds me of good old Borg…resistance is futile. The only good news is that I have one of those page builders whose team heavily invested to work with this piece of joke, otherwise i would have abandoned WordPress for good.

Question: Why have you set up rating system? I mean if Guttenberg plugin cannot score more than 2.7 you should reconsider release or try to make some revolutionary changes. It worked for many others. Unless, you don’t really care what WP users think. For those Guttenberg enthusiasts it could have stayed plugin they could always install, and you would be able to really see how competitive it can become on the market. But now we will never know, want we?

It does not add any new features. Remove it from wordpress.org

You are irresponsible. The business of millions of people depends on this. Your plugin is useless. All the same as in the classic editor. Only with problems. It does not add any new features.
This is the beginning of the fragmentation of WordPress.
I already turned off core auto-update for my clients.
And I’m not going to install 5.0.0

Not yet

I have heard many comments saying that Gutenberg will bury the page builders. I think the focus is different. Whoever uses builders can sleep peacefully, Gutenberg will hardly meet all the page design needs we need today. But as a text editor, I’m glad that finally they are upgranding this feature. I think something like build native tables would be welcome, force justify and something more about line spacing control.

Love it, but still I don’t understand

Firstly, I should mention that I really love this plugin and the work which is being undertaken on Github and how quickly the plugin is being developed.
However, I see multiple issues with this plugin being added to the core.
I really hope that you guys, including Matt, did proper research into what people wanted in the first place.
I want to keep this short, but also informative.
My issues with Gutenberg:
1, If you don’t care about small bloggers and websites, are you sure big corporations, like Coca-Cola, The New York Times and other want this plugin included in the WordPress core?
2, If you are putting this into the core, are you confident enough that Gutenberg won’t impact release schedules beyond 5.0?
Let me elaborate, you guys mentioned that you intend to include Gutenberg into the core ‘when it is ready’, most likely to be included in version 5.0, however minor bugs, future browser updates causing incompatibility and other potential issues along the way – in my own opinion – can and will make very hard to maintain the codebase of Gutenberg within the codebase of the WordPress core to resolve said issues. Upon resolving those issues everybody will have to update WordPress again, regardless if Gutenberg is switched off or not. Gutenberg, being included in the WordPress core may adversely affect the number of minor updates in a single year.

You should really explore other opportunities regarding Gutenberg and the WordPress core. I see the reasons why you would like to include it, but including it directly into the WordPress core is just foolish.

In order to keep Gutenberg relevant and bug-free you could adopt a new approach to Gutenberg.
You could include Gutenberg as a ‘core plugin.’ A core plugin would be included in the default WordPress package, could be updated at any time through the plugins page, while it could not be deactivated through the WordPress plugins page. Site admins would have the means to delete it and remove its code, satisfying their cravings of not being forced to have Gutenberg.
Making Gutenberg a ‘core plugin’ as described above is also going to support its ongoing development, making updating Gutenberg in the future with improvements and bug fixes a breeze

Read all 488 reviews

Contributors & Developers

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

Contributors

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

  • Ensure the Title uses the same max-width as blocks
  • Center the background of the cover image block
  • Fix formatting controls regression
  • Fix classic editor visual mode regression