Vortrag am Donnerstag in der Digital Eatery: der Gutenberg-Editor

Digital Eatery, Unter den Linden 17, Donnerstag 19 Uhr im Rahmen des WordPress Meetup Berlin gibts nen Vortrag von Maja Benke über den neuen Editor für WordPress: Gutenberg.

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

Nice idea, bad bad BAD way of doing things

I’m just a writer/hobbyist who blogs. I just spent hours after the update finding out that the tools I had been using with the classic editor not only no longer worked, but fubared several pages/posts of my site.

Even worse, for me, one of the plugins I’ve been using and happy with, “Siteorigins Pagebuilder” pretty much requires the classic editor, and although it SAYS it’s compatible with 5.x, in reality, nopers.

In order to recover, I had to remove 5 different plugins and do a reinstall of the WP 5 update with the classic plugin. (Fortunately, that resolved my major problems.)

The only thing that saved even more headaches was the classic plugin.

An editor should BE A CHOICE. I can use LibreOffice, or MS Office, LyX or some other solution. Having a specific editor stuffed in an upgrade…especially one that can cause a major mess…smacks of hubris or at the very least an echo chamber within the company that isn’t hearing the community.

I’d expect a “wall garden” with ‘dot COM’…but ‘dot ORG’ should be wide open and all about choices.

To be honest, I’ve never been a fan of classic, but add-ons such as TinyMCE Advanced made it bearable…and plugins such as page builder opened up the creative juices for making interesting stuff.

I LIKE the idea of Gutenberg, but the way this was implemented…rancid.

C

Don’t do this!

Something as radical as Gutenberg should not be imposed as default. One of my customers updated and then couldn’t edit. It should be optional. In any case, is it as good as Elementor or Site Origin Page Builder? I don’t think so. There was enough feedback while it was in Beta to suggest that improvements were necessary, so why hit existing users, many of whom are not expert, with sometning totally unfamiliar?

Best Plug In is DISABLE GUTENBERG

this really is so poor.

Working in a narrow column, editor bar goes missing (or half of it)

I run 5 websites, and have installed the plug-in DISABLE GUTENBERG – thankfully it works!

How did anyone not test this ?

It may be me, (it sometimes is) – but I can’t see how it makes anything easier.

Thank goodness for Plug In !!!

So bad and nobody is listening

Tested it for a while and now I just had to come here and give a review for this new “writing experience”… The only experience I’ve had is frustration. First, because writing with Gutenberg is a disaster. All buttons are hidden, writing an article fluently is no longer possible at all. Secondly, because there is no standard solution to disable this part, only using third-party plugins. And thirdly, what counts most of all for me, because apparently the whole development team of WordPress closes their eyes and ears to the resonance of the users. 2.2 stars as average rating, almost three times as many 1 star ratings as 5 star ratings and meanwhile over 1 million active installations of the Classic Editor plugin speak such a clear language. How can you simply ignore these things and still stubbornly walk your way and run against the wall with your eyes open?

Worst descision ever

Why?

Did you for one second think about the millions of custom made websites that were built around the old editor? Hundreds of hours of development time for custom fields and adaptions, workarounds and whatnot. At least 10.000 of plugins developed solely for the purpose of subsidize the classic editor. Life’s & careers built upon that.

How did you imagine this would go down? For us devs at least.

“hey, a great new editor, lets just rewrite the last 50 themes and websites we made from fn scratch.” – “But Bob, will those customers pay us again?” – “Of course they will!”

Don’t be so negative it’s built upon *enter buzzword framework*. Who wouldn’t want it?

I tell you who wouldn’t want it: Apparently more than 1000 hard working devs and their customer, that’s only counted by the 1-star reviews here.

Read all 1,897 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

  • Optimize isViewportMatch
  • Performance: BlockListAppender: 1.7x increase on key press
  • Date: Optimize 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
  • Optimize 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 frontend
  • 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