Gutenberg

Descrição

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.

Blocos

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.

Perguntas frequentes

Como posso enviar feedback ou obter ajuda sobre um 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.

Como posso contribuir?

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?

Avaliações

Not liking it

I installed this on one of my sites as I at least wanted to give it a try but I have to say using it for the last three weeks I am really hating it. Can someone tell me whats wrong with the default editor?? If it aint broke…..dont fix it.

Amazing Leap Forward

Ignore the negative reviews. Editors like Medium.com are the gold standard for writing content these days and this is a substantial step in that direction. While there will be some bumps transitioning to the new editor for some out there, the naysayers are just those who probably overreact everytime Facebook or Twitter moves a UI button.

Great for building new sites, not so great for legacy sites.

The first time I installed Gutenberg I hated it, I mean I really did and I deleted it immediately. Anyway I thought I would give it another go as it seems that it is going to happen regardless, so I installed it on a local version of a site that is now live to have a play.

I also installed Beaver Builder to see how the two products worked together. I have been using BB a lot of the last couple of years, having resisted page builders before, but with the right amount of access it makes my life a lot easier and clients seem to love it.

The theme I am using is a child theme of Generate Press.

To me Gutenberg appears to be a good solution for building light weight sites quickly and I like a new toy, but what about the legacy stuff? That is where things start to go a little pear shaped!

It’s not that it doesn’t work with the legacy sites but it does make the process very confusing and messy for someone who doesn’t do this for a living, I got confused and I’ve been in the industry for 32 years so how is that going to work for a person who is a technophobe.

In short the process was very simple when creating a new page when the page builder was disabled but when it was enabled if I clicked new page I got a blank screen. I had to go to YouTube to work out what I was doing wrong! I know, user error, I didn’t click on the arrow, but hey it’s going to happen to a lot of people.

My honest opinion of Gutenberg is that I like it and would use it for some NEW projects but I do not believe that it belongs in the WordPress Core, it is just going to cause to many problems for to many people.

The other potential problem I can see in the future is that as major plugin developers port their software over to Gutenberg then how will that effect their on going support for sites with the Classic Editor installed? Sooner or later we will have broken websites IMHO!

It could be worse . . .

People hate change and a major change such as this is inevitably going to divide opinions. I can understand why WordPress is doing this but personally, I am not a fan of page builders or drag-and-drop editors. I like to have the control that a normal text editor provides. But having tested it for a while, I can honestly say there are MUCH worse commercial page builders out there. And as long as it’s possible to revert to the classic editor, I really don’t see what all the fuss is about. At least WordPress is giving us that option (for now at least) and is rolling the new editor out in a controlled manner.

This is so powerful after users get past the learning curve

I am gobsmacked that the reception is so harsh right now. Other page builders are often very clunky or too “opinionated” on the styles that they use. Gutenberg is a wonderful bridge between the classic editor and a fully-fledged page builder. I feel confident that I can create a Gutenberg-enabled project for a novice WordPress client and give them the right degree of customization.

The idea of reusable components is great! Being able to create your own components is likewise a huge deal and a better experience than shortcodes.

To the dev team, keep your chins up–people are always hesitant about change. This is powerful and valuable.

Ler todas as 1.027 avaliações

Contribuidores e programadores

“Gutenberg” é software de código aberto. As seguintes pessoas contribuíram para este plugin:

Contribuidores

“Gutenberg” foi traduzido para 34 locales. Obrigado aos tradutores pelas suas contribuições.

Traduza o “Gutenberg” para o seu idioma.

Interessado no desenvolvimento?

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

Registo de alterações

Latest

  • Restore min-width to popover.
  • Fix wide toolbar regression
  • Add e2e test for publishing a page
  • Fix typo for removing excerpt block stripping

3.6.1

  • Fixed an issue that caused page publishing to fail.
  • Fixed an issue with the block options menu appearing too narrow.

3.6.0

  • Updated block inserter and library with new icons for all core blocks.
  • Allow showing the sidebar and inspector controls when editing a block in HTML mode.
  • Add new block keyboard shortcuts and consolidate their display in menus:
    • Insert Before / After block.
    • Duplicating block.
    • Toggling the inspector.
    • Remove block keyboard shortcut.
  • Updated block inserter and library with new icons for all core blocks.
  • Allow showing the sidebar and inspector controls when editing a block in HTML mode.
  • Add new block keyboard shortcuts and consolidate their display in menus:
  • Insert Before / After block.
  • Duplicating block.
  • Toggling the inspector.
  • Remove block keyboard shortcut.
  • Add new keyboard shortcuts help modal documenting available shortcuts.
  • Hide keyboard shortcuts on mobile screens.
  • Open new window if prior preview window has been closed.
  • Bring the preview tab to the front when clicking the preview button.
  • Avoid changing the label of the “publish” button if an auto-save is being performed.
  • Update the Block Inserter to allow searching for terms that contain diacritics.
  • Take into account children blocks when handling disabled blocks.
  • Offer chance to add and revise Tags and Post Format during pre-publish flow.
  • Let menus grow based on the length of its elements.
  • Add visual padding to menus.
  • Avoid scrollbars on Audio block when shown full-width.
  • Improve permalink UI and make it responsive.
  • Change color of links in gallery block caption.
  • Simplify the styling of the “Toggle publish panel” aria-region to avoid content jumps.
  • Make active pill button look pressed.
  • Make sure Latest Posts alignment class behaviour is consistent.
  • Show drop-zone background when file is dragged.
  • Reset active sidebar tab on initial load.
  • Apply new checkbox CSS to radio buttons and fix border radius.
  • Add a couple new dashicons for insert before / after block.
  • Add styles for Spinner component (was relying on core before).
  • Add styles for Notice component.
  • Refactor template select field to use SelectControl.
  • Correctly handle per_page=-1 in the queried data state.
  • Create dummy context components for type switch.
  • Add RegistryConsumer export to data module.
  • Add has_blocks function to the repertoire.
  • Add has_block function and unit tests.
  • Add has_block function and unit tests for it.
  • Introduce strip_dynamic_blocks() for excerpts.
  • Fix issue with default appender placeholder on IE11.
  • Fix issue with shortcode block UI on IE11.
  • Fix tag input interface on IE11.
  • Fix issue with custom element serializer on IE11.
  • Fix issue with meta boxes overlapping the content on IE11.
  • Fix invalidation case of custom block classes.
  • Fix unhandled error dialog styling issue.
  • Fix paragraph splits on react native implementation.
  • Fix code block style regression.
  • Fix issue with code font-size on heading contexts.
  • Fix case where crashed block would overlap with surrounding blocks.
  • Fix issue with block styles on IE11.
  • Fix the heading level buttons on IE11.
  • Fix issues with drag and drop over text.
  • Fix small bug with recent blocks hover style.
  • Use argument swapping instead of named arguments for string placeholders.
  • Pass the the search result object to props.onChange on UrlInput.
  • Add localization context to occurrences of “More” string.
  • Add a Heading block implementation for mobile app.
  • Add the react-native entrypoint to all runtime packages.
  • Move MoreMenu specific styling away from Popover CSS.
  • Ensure meta box functions are available in editor context.
  • Ensure the full content integration test is run.
  • Remove client-side document title updates.
  • Remove TinyMCE shim that was removed in WP 4.9.7.
  • Remove the workaround for intermittent multiple-tab preview test failure.
  • Remove Promise.resolve call that’s already handled by the JS runtime.
  • Remove redundant event handlers from default block appender.
  • Deprecate withContext HOC and remove its usage.
  • Some localization & spelling fixes.
  • Update docs for templateLock’s insert option.
  • Extract Core Blocks to a block-library npm package.
  • Add a license checker script.
  • Allow access to the WordPress installation if DOCKER_ENV=localwpdev.
  • Bring the handbook design up to date.