Gutenberg

Descripcion

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

Very bad idea

It’s the end of free choice. We have enough plugin to choose if we want another editor. Plugin that work very well. The current version of Gutenberg is a disaster, I do not see how you will solve the problems by the version 5.0 of WordPress. Gutenberg is a hell ;-), stop this wacky project !

Tried it and now deleted

Tried it and now deleted…

Not easy to use or intuitive. sends me around in circles, just to do something basic

I guess it may be easier once plugin writers add their own blocks

Please leave Gutenberg as a Plugin option, as the original WordPress editor is far more productive

Gutenberg needs more time

Gutenberg is going to be a great editor, but it still needs a hell of a lot of work to become the editor for Word Press. In my opinion it should remain as a plugin.
Biggest issue I found for a 2018 product, the editor in a lot of places you do not get what you see using the editor, you still have to preview then touch up to get the main publishing display correct.
Added some images then added caption which does not have any editing options for font size or color, these have to be added by editing HTML, not a problem if you edit code. But not for beginners there are 3rd party plugins that do all this for you in the editor.
Add some columns then add buttons there are no options for buttons, one shape roundish that’s it. Add one button with text of say 3 characters, then add second button more characters the button size changes to follow the number of characters. Again HTML spaces are required to get a reasonable desktop result, then try it in mobile its crap.
I got to the stage that I could not publish the results for my customers.
Have gone back to a working solution with PootlePress Page Builder.
Adding sections or blocks can work and is simple once you realize that to delete the section or block it must have at least one character typed into it.

Believe me this editor is not ready and should not be released in Word Press 5.0 as the main editor.

Frustrating

I wrote a very long review but, eventually, decided to delete it. In the end I find Gutenberg FRUSTRATING. I have been using computers for 30 years, with all kind of text editors and I feel like it is the very first time I am typing. That is my feeling.

Utter Crap – Totally Useless (Zero Stars)

I wish these guys had zero stars. This is the worst plugin I have used for a while. At first, I thought to myself that it was just me, but I realized how silly the stupid plugin is. Make things easier??? I’m lost for words…

Read all 1 280 reviews

Contributors & Developers

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

Contributors

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

  • Add Full Screen mode. 📺
  • Add UI for bulk managing reusable blocks.
  • Implement a more sophisticated Editor Styles mechanism. 🖍 It allows themes to register editor styles for blocks by targeting the blocks themselves without having to fight CSS specificity, and without having to know the internal DOM structure for the editor.
  • Move the block settings menu to the block toolbar, further consolidating the UI elements.
  • Switch to a new hand-coded default block parser implementation and expand documentation.
    • Implemented in both PHP and JS.
    • Brings great performance improvements in both time and memory.
    • Makes server-side parsing in PHP viable for accessing blocks as a tree.
  • Use flex-box to render the block inserter layout to address different issues with spacing.
  • Show a warning when a disallowed filetype is dropped on a MediaUpload.
  • Show « no archives to show » message on Archives Block.
  • Add AccessibleSVG component and use consistently for block icons.
  • Improve Classic editor and Cloudflare notification modals.
  • Refactor Draggable component to decouple the drag handle from the DOM node being dragged.
  • Move video caption styles to style.scss.
  • Treat Verse lines consistently on the front-end.
  • Make sure all available taxonomies are loaded in the editor.
  • Improve empty elements filters in Slot implementation.
  • Fix case with PostTextEditor where intended state value is not always reflected in the rendered textarea when empty.
  • Fix background clashing with some themes in Separator alternative styles.
  • Fix case where hasSelectedInnerBlock did not account for multi-selected innerBlocks. This caused an edge case in Spotlight mode where multiple blocks selected inside a column would appear unfocused.
  • Fix regression with margins around image captions.
  • Fix issue with author select overflowing on IE11.
  • Fix the publish panel top position in FullScreen mode.
  • Fix radio button alignment in post visibility menu.
  • Fix issues with centering of images.
  • Fix BlockIcon usage in embed placeholder when resource cannot be previewed.
  • Fix font size regression in PostTitle.
  • Fix codetabs block in extensibility documentation.
  • Fix import source of RangeControl in Readme file.
  • Fix broken link in documentation inside element/README.md.
  • Deprecate usage of RichText provider component.
  • Deprecate getI18n, dcnpgettext.
  • Remove deprecated selectors from docs.
  • Revert shortcut change in block-deletion e2e test.
  • Pin fetch polyfill to 3.0 UMD distributable to resolve an issue where it was no longer usable in IE11.
  • Ensure Gutenberg repository is clean after install.
  • Include block serialization default parser in plugin.
  • Change how required built-ins are polyfilled with Babel 7.