Gutenberg

Skildring

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.

Vanlege spm.

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?

Omtalar

OK, but not quite there yet

I help friends with their websites in Jimdo and Squarespace, and after testing Gutenberg I am much happier with it than with those editors.

Still, there are some things I noticed right away after 15 minutes working with Gutenberg:

1. When I add a new block it doesn’t always appear where my cursor is. I have deleted several blocks already, which popped up at the wrong position.
2. So far I haven’t found out, if/ how I can move a block to another position. The only option i found is copy + paste the content to a new block.
3. I love the option to build columns. In the past I had tested various plugins and all had some issues messing things up. But, please give us an option to determine column width (in percent of available space would be sufficient for me).
4. It took me sometime to find the preview after editing a block in HTML. To me the location of the preview button is not self-explaining. I did expect it below the «edit HTML» option.
5. The editor interface wastes a lot of place to the left and right of the content (I have a 21 inch screen). That means a lot of scrolling, when editing content. Please make better use of the available space.

Tout ce boulot pour en arriver là?

Je pense que les concepteurs de Gutenberg sont tombés sur la tête! Hééé toc-toc!… Sortez vos têtes du clavier! Allez respirer un bon coup à l’extérieur, cela va vous remettre les neurones en place!!!
On aime WordPress depuis des années pour sa simplicité, son ergonomie et ses possibilités en terme de copié/collé etc. C’est vrai certes que l’éditeur visuel à quelques défauts ou qu’il manque quelques bouton de mise en forme, et qu’il n’a pratiquement pas évolué ces dernières années.

De grâce ne nous imposez pas ça!!!
Cela fait 5 ans que j’utilise WP (seulement par rapport à certains), et je dois vous avouer que je n’ai jamais pensé aller lorgner vers un autre CMS, mais si vous installez Gutenberg sans nous laisser d’alternative ou bien de revoir votre affaire sérieusement, il n’est pas dit que je ne me penche pas un peu plus sur la question!
Et il n’y a pas de honte à admettre que l’on c’est planté! A bon entendeur Salut.

Errors, too many clicks to get things done

The plugin does not appear to be ready for release. I’ve dealt with multiple errors and barely got the basics working after installing and uninstalling Gutenberg and the classic editor multiple times.

I finally got a couple of blocks to appear to work, but as soon as I inserted an image the errors returned.

Simply doing something like adding bold or inserting an image takes double the number of clicks or more. In making the interface look more simple, they’ve made it more complicated to accomplish simple things.

I will check back in 6 months to see if anything has improved, but likely will still use the classic editor.

Add block button suggestion

It would be great if the add new block button was also available below an existing block and not just top centre.

Also, sometimes the small cross in the circle is barely visible between paragraphs or when a line in inserted above two paragraphs.

Gutenberg is not ready

as of August 14, Gutenberg has 988 issues and they want it ready by the end of the year for core? WordPress Developers are trying to learn the new development but with the amount of current issues out there and current fixes/changes it is like trying to hit a moving target.

Great idea in the right hands but very bad in the wrong hands

Please do not make this plugin the default editor in WordPress. I agree with other people that it has a lot of potential but I think that the classic editor should still be default.

I really like the concept of blocks and have coded my own version of this for many years. In hands of a designer or a competent web editor I think this could be very powerful and will use this plugin in some cases. However…

From a web design point of view
I’ve designed and coded websites for my clients for 20 years and in my experience if you give the average person too much freedom to change page layouts then the website will end up looking rubbish. You know what I’m taking about… you spend weeks designing and making a lovely website and as soon as you hand your customer the keys, they get «creative» and ruin it.

From a usability point of view
For most people, updating their website is just one task in their already busy working day. Most people want to be able to edit their websites very easily, with a minimal learning curve. That means they need something very simple and similar to what they are used to. Unfortunately this means that they often want something that resembles Microsoft Word. The classic editor is easy to use and very easy to understand. It’s familiar to non-techies and that’s why it’s great!

Please leave the classic editor in place and keep this plugin as a plugin!!

Les alle 970 omtalar

Bidragsytarar og utviklarar

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

Contributors

“Gutenberg” er omsett til 32 språk. Takk til omsetjarane for bidraga deira.

Omset “Gutenberg” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.

Endringslogg

Latest

  • Add an edit button to embed blocks to modify the source.
  • Improve margin collapse within column blocks.
  • De-emphasize inline tokens within the inserter for a better user experience.
  • Polish focus and active styles around buttons and inputs.
  • Polish styles for checkbox component, update usages of toggle to checkbox where appropriate. Update documentation.
  • Improve pre-publish panel styling and textual copy.
  • Prevent duplicate DotTips from appearing.
  • Integrate «queries data» into the entities abstraction for data module.
  • Hide block movers if there are no blocks before and after.
  • Initial improvements for responsive image handling in galleries.
  • Use correct color for primary button bottom border.
  • Allow transitioning post status from scheduled to draft.
  • Improvements for auto-completer keyboard interactions.
  • Place strikethrough formatting button after link as it’s less important.
  • Resolve issue with preview sometimes opening redundant tabs.
  • Align timepicker with calendar on pre-publish panel.
  • Expand date filter select box width within media library.
  • Constrain media blocks to content area width in front-end.
  • Reapply box-sizing to slider thumbs.
  • Avoid showing line separator in block settings menu when it’s the last item.
  • Introduce additional keyboard shortcuts to navigate through the navigateRegions component.
  • shift+alt+n to go to the next region.
  • shift+alt+p to go to the previous region.
  • Replace all withAPIData usage and deprecate the higher-order component.
  • Add persistence via data plugin interface.
  • Introduce new redux-routine package for synchronous generator in data module.
  • Move embed API call out of block and into data module.
  • Remove no longer needed workaround targeted at resolving a TinyMCE error.
  • Abort selection range set on unset range target. Resolves an issue when merging two empty paragraph blocks created while at the end of an inline boundary.
  • Removing or merging RichText should only trigger if the selection is collapsed:
  • Fix issue with backspace not working as expected when deleting text content from the first block.
  • Fix case where paragraph content could move to previous paragraph when deleted.
  • Remove provisional block behaviour to improve reliability of various interactions.
  • Restore horizontal edge traversal implementation to address issue where pressing Backspace may not place the caret in the correct position if within or after a RichText field.
  • Ensure Gutenberg is disabled when editing the assigned blog posts page.
  • Initialize the Autosaves controller even if revisions are disabled. Fixes several bugs around saving with revisions turned off.
  • Display warning when Cloudflare blocks REST API requests.
  • Improve validation for attribute names in serializer.
  • Add Slot to block menu settings for extensibility.
  • Fix File Block center align behavior.
  • Fix behaviours when deleting on an empty RichText field.
  • Fix parent-dropdown missing for custom post-types.
  • Fix import style statements in ColorIndicator.
  • Fix height of used-once block warning.
  • Fix link for innerBlocks docs.
  • Fix link to server-side-render component.
  • Fix race condition with DomReady.
  • Fix awkward capitalisation in demo post content.
  • Fix warning for unrecognised forwardedRef prop.
  • Fix regression with URL input focus box.
  • Fix error in custom HTML preview when block is empty.
  • Fix colspan bug in table block for tables with thead tags.
  • Fix issue with image inspector controls disappearing once an image block is set to wide/full alignment.
  • Fix issue when image size remains blurry if manually set to a smaller size (i.e., medium) and then changed alignment to wide/full.
  • Fix issue with meta boxes being absent when script enqueued in head depends on wp-edit-post.
  • Resolve an issue where removing all text from a Button block by backspace would cause subsequent text changes to not be accurately reflected. Broader issue with TinyMCE inline elements as containers.
  • Avoid using remove() because it’s unavailable in IE11.
  • Address further feedback on duplicated DotTips implementation.
  • Update re-resizable to version 4.7.1 — fix image & spacer blocks resizing on IE.
  • Use a unique querystring package instead of three different ones.
  • Introduce filters to allow developers the ability to customize the Taxonomy Selector UI for custom taxonomies.
  • Introduce RichText component for mobile native and implement the Paragraph Block with it.
  • Use standard label for Alt Text input.
  • Consolidate similar i18n strings.
  • Remove title attributes from the Classic Editor warning.
  • Remove unused code in taxonomies panel.
  • Remove oEmbed fixture files.
  • Remove jQuery dependency from @wordpress/api-fetch.
  • Remove filler spaces from empty constructs.
  • Remove REST API shims for code introduced in WP 4.9.8.
  • Remove unused terms, taxonomies, and categories code.
  • Replace the apiRequest module with api-fetch module.
  • Add inline comment that explains a stopPropagation() within tips implementation.
  • Add gutenberg_can_edit_post filter.
  • Add watch support for stylesheets in packages.
  • Add JSDoc comment to Popover’s focus() method.
  • Add readme docs for all components.
  • Autogenerate documentation from readme files.
  • Add doc note about automatically applied attributes in save.
  • Add test for block mover.
  • Allow demo content to be translatable.
  • Update CSS selectors from :before to ::before.
  • Export the description for server-registered blocks.
  • Export getBlockTypes on react native interface.
  • Expose redux-routine to react native.
  • Expose unknown-type handler methods for mobile.
  • Specify missing wp-url dependencies.
  • Improve JS packages descriptions.
  • Downgrade Docker image version for WordPress for test validation.
  • Move CI back to latest WordPress version and bump minimum version to 4.9.8
  • Use @wordpress/compose instead of @wordpress/components.
  • Update docs for Button component.
  • Update package-lock.json.
  • Updated dependencies: jest, npm-package-json-lint and read-pkg-up.
  • Add Babel runtime dependency to redux routine.
  • Prevent Travis from running when changes are only made to .md files.
  • Add stylelint for SCSS linting.
  • Set babel dependencies to fixed version and add core-js2 support.
  • Trigger E2E test failure on console logging.
  • Update doc links to resources moved to packages folder.
  • Update api-fetch package documentation.
  • Update Lerna to 3.0.0-rc.0.
  • Generate source maps and read those from the webpack build.
  • Rewrite e2e tests using jest-puppeter preset.
  • Introduce a new Extending Editor document specific to editor filters.
  • Improve test configuration and mocking strategy.