Gutenberg

Kuvaus

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.

UKK

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?

Arvostelut

What really? ’Intentional’ crippling of the code editor in Gutenberg

Just installed the Gutenberg editor. Have to disable, because of the Preview not working (so, really, I need to go through each plugin and contact them?? Yeah, I'm a volunteer doing this stuff). And second reason to return back to the Classic plugin: because the code editor is completely useless. The reason I had to learn code and use the code editor in the first place---is having lost much time to changes made in the tiny Visual editor, and then one switch to Text editor, and lost all style changes (you only do that once and not again...). Code is code. Make it work. Some of us actually use coding to style (I know, shocker). A shame, I would like to learn how to use Gutenberg. I'll look for more functionality (i.e. time efficiency) with the next updates. And what, I don't know enough to figure it out? Yep, again, shocker, some of us trying to use WordPress (years, now), aren't programmers or developers. Over and out.

Beyond Awful – Nonfunctional

It's seriously astounding that WordPress has rolled this out with the latest update. Look at the reviews here, how could you just shrug off your entire customer base like this? The editor is simply nonfunctional on my site - any older post I open with it can only be edited through code. In the visual editor it will only show the "block" that contains my post title and then the rest just don't appear at all. Sad to say, but this may be the beginning of the end for WordPress. I'm beginning to look into other options for my site. Thank god for the plug-in that allows you to disable gutenberg and return to the classic editor, otherwise I'd literally be unable to edit a single post on my site without dealing exclusively with HTML. Ridiculous.

Not getting any better with age

Make a 2 column layout with a image left, text right, 1 column full container width below it. Go on, try, it will take a long while! Boom, layout is messed up beyond belief, everything crashing into itself, justified incorrectly, forcing flexbox on people who can't even code. Even in the most modern of browsers, this sucks. Badly. This is my experience of using it AS A THEME DEVELOPER. I literally have no idea who they used to test this - certainly not the average user - but I think there's a whiff of arrogance in pushing the 'new way'. People hate the new way anyway, even if it works. This doesn't. At all. People who use WordPress because its easy are going to be jumping ship. WP 5.1.1 promised massive improvements! What in? I don't see a single thing any better. It sucks more, because now it's lying to itself to save face. Stop pretending something works when it doesn't. You've cost me a lot of hours and I've got half a clue. Goodness only knows the hit the community has taken from it but they won't be thanking you for it. Squarespace and Wix might though!

Too early

I like the idea behind blocks a lot. But as it is right now, the blocks only add to the inconsistency of WordPress editing. Editors have to work in a jungle of Shortcodes, Plugins, Widgets and now blocks. Also, the new editor feels so different to the "old" widgets and so on. There will be more of the new editing in Gutenberg phase 2, I guess. But why release it now (in the core). I'd rather wait until everything fits together.

This is so bad

The editing isn't too bad but doing simple things like fixing your title or permalink, no where to be seen. A quick google to see if your missing anything will indicate yep it's official guttenberg is the worst thing I've seen in awhile. Good concept, poorly executed.
Lue kaikki 2 637 arvostelua.

Avustajat & Kehittäjät

“Gutenberg” perustuu avoimeen lähdekoodiin. Seuraavat henkilöt ovat osallistuneet tämän lisäosan kehittämiseen.

Avustajat

“Gutenberg” has been translated into 44 locales. Kiitoksia kääntäjille heidän työstään.

Käännä “Gutenberg” omalle kielellesi.

Oletko kiinnostunut kehitystyöstä?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Muutosloki

For 5.3.0.

Features

Enhancements

Bug Fixes

Documentation

Various