Gutenberg

Описание

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 11 blocks.

core/archives
core/rss
core/legacy-widget
core/categories
core/block
core/latest-comments
core/search
core/shortcode
core/calendar
core/tag-cloud
core/latest-posts

ЧЗВ

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?

Отзиви

Horrible

This is the WORST feature wordpress could have added. Very bulky, can't see the editor at all, not user friendly. Thankfully a plugin is available to revert, but I hope WP goes back a step to get rid of this.

Worst editor I’ve ever seen

I disable it for all my clients, it's awful and a huge mess, and it adds extra stylesheets and garbage to the sourcecode so now I have to do more work to de-register all that crap. The whole thing is a huge slap in the face. This should be an OPTIONAL PLUGIN not default.

This is the Future of WordPress

I have 3 perspectives to look at with when I'm reviewing the new editor. First, as a developer: There've been extremely frustrating times when I started developing blocks for Gutenberg. Continuously altered styling and code, catching up with all the changed bits and plugin crashes after almost every Gutenberg update were hard times. But especially after 5.5 update and above, everything has become much more fun since it's evolved nicely! As a designer: There are zillions of UX dead ends and UI bits to be improved with the new editor, but I can see with each new update team are working hard to overcome those. I see there's still much to fix but so far so good (also contributing to fix those). I developed a block library for Gutenberg, and when developing it I've put myself into user's shoes to deliver the most out of a Gutenberg experience. For example, what's lacking was indicators of what I've changed in a block, so I've placed indicators. But most of the earlier improvements I've added have become obsolete with each update of Gutenberg, which is super cool! As a user: Back in November 2018 when I had a first glance of the plugin, yeah I hated it like the most. But this is a trending concept and new direction for content editors people are slowly getting used to. And the more I used it, the more it grew on me. Today, I'm just loving it tons more times than I would love Elementor, Visual Composer or Divi. Message to the haters My suggestion is; if you didn't like this new editor at first, maybe don't come over here and puke without hesitation just yet. Give it time, you will love it 🙂
Прочетете всички 2 797 отзива

Сътрудници и разработчици

“Gutenberg” е софтуер с отворен код. Към разширението са допринесли следните хора.

Сътрудници

“Gutenberg” е преведено на 44 езика. Благодарности на преводачите за техния принос.

Превеждане на “Gutenberg” на вашия език.

Имате интерес към разработване?

Преглеждане на кода, разглеждане на SVN хранилище, или абонамент към програмната история (log) чрез RSS.

Списък с промени

For 5.9.2:

Bug Fixes

  • Fix Regression for blocks using InnerBlocks.Content from the editor package (support forwardRef components in the block serializer).

For 5.9.1:

Bug Fixes

For 5.9.0:

Features

Enhancements

Bug Fixes

Various

Documentation

Mobile