Gutenberg

Description

Gutenberg est plus qu’un éditeur. Bien que l’éditeur soit au centre des préoccupations, le projet aura, à terme, un impact sur l’ensemble de l’expérience de publication incluant la personnalisation (le prochain centre d’intérêt).

Découvrez-en plus sur le projet.

L’éditorialisation comme focus principal

L’éditeur créera une nouvelle expérience de construction de pages ou d’articles qui simplifiera la rédaction de contenus enrichis. Cela passe par les « blocs » pour unifier ce qui aujourd’hui se fait avec des codes courts, du HTML personnalisé ou tout autre truc spécial dans ce genre — 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. Le bloc permet d’unifier de multiples éléments d’interface. Si nous le faisions sur l’interface existante, nous aurions ajouté de la complexité, alors qu’en la remplaçant, nous simplifions l’ensemble.
  2. En revisitant l’interface, nous modernisons l’expérience d’écriture, de modification et de publication, en nous concentrant sur l’utilisabilité et la simplicité, ce qui bénéficie à la fois aux utilisateurs futurs et actuels.
  3. En donnant une importance centrale à l’interface de blocs, nous encourageons les développeurs à créer leurs blocs dédiés, ce qui sera bien mieux que les widgets et codes courts actuels.
  4. Le fait de refondre l’ensemble de l’interface pose des fondations solides pour la prochaine étape, la personnalisation complète de votre site via le back-office et les blocs.
  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.

Les Blocs

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.

Compatibilité

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.

Les étapes de 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.

Contributeur·ices

Gutenberg est bâti par de nombreux développeur·ses et contributeur·ices. Voici la liste non exhaustive : CONTRIBUTORS.md (en anglais).

FAQ

Comment puis-je envoyer des retours ou être aidé par rapport à un bug ?

Nous adorerions entendre vos retours de bugs, vos suggestions de fonctionnalités et tout autre retour ! Veuillez consulter la page de retours sur GitHub pour rechercher des problèmes existants ou pour en ouvrir un nouveau. Bien que nous essayerons de trier les problèmes signalés ici sur le forum des extensions, vous obtiendrez une réponse plus rapide (et limiterez les doublons) en gardant tout centralisé dans le répertoire GitHub.

Comment puis-je contribuer ?

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.

Voyez également CONTRIBUTING.md.

Où puis-je en savoir plus sur Gutenberg ?

Avis

Overly complex and not intuitive

I don't know why they choose this Plugin as default editor, but when I showed it to the people who should use it they didn't want me to update. Lucky for me I test WordPress updates always on a Local-Test-Server so I just didn't bother with that editor in the live environment. But when I was playing around with that thing it felt not really intuitive, why fix was was not broken. I've seen this a lot on many projects/websites these days. It's trendy to make things more difficult. I always though Software should make the life more easy instead of getting you more work? It should not be rocket since to write something with some basic formatting. I mean when its more easy to write it in plain HTML, then something went really wrong Now I installed the Disable-Gutenberg Plugin and everything is like before!^-^

Real world usage…

The UI for the plugin is a nightmare, for instance, I find myself mousing over several areas of the block UI elements to find the block configure/options menu. I have no clue where things are. This plugin component has potential but the UI/UX just needs to trashed and redone, by a different designer.

Serves no useful purpose…

...other than to frustrate. The Dashboard admin menu and Appearance > Menus still 'work' almost exactly as on day one, have basically become a UX nightmare, but 'berg' made it to the front of the line. So they tried to implement something that has been done so much better 100+ times over instead of updating core mechanics. Well, kudos to the authors of all those 'disable' Gutenberg plugins. You are my heroes.

Why???

I am not a developer. I am not a coder. I am simply a person who has and maintains their own sites, and on occasion puts up and maintains the sites of others. As soon as I updated my test site to Gutenberg, I was immediately completely unable to figure out how to manage the site that I have successfully looked after for 10+ years. Thanks WordPress. Gutenberg Sucks. Big time. Now I"m dependant on yet another plugin to keep my site functioning. I also have to worry about that plugin developer abandoning their plugin, or deciding to charge for it. Or perhaps it becoming incompatible with another WP update in the future. I don't know who the mastermind was who came up with this brainchild, but like when NGG was sold years ago, this is an epic fail. Paint me disillusioned and dissatisfied.

Absolutely incompatible

With nearly all existing plugins a big disaster! As soon as several blocks are generated in the editor, an HTML mutation occurs in one block, the whole page (!) is output as a single HTML script and can no longer be reformatted to blocks, to the annoyance of the Content Manager. I can't understand how WordPress, as such a big CMS, relies on such a flawed and poorly implemented editor. Crazy...
Lire les 2 564 avis

Contributeurs & développeurs

« Gutenberg » est un logiciel libre. Les personnes suivantes ont contribué à cette extension.

Contributeurs

“Gutenberg” a été traduit dans 44 locales. Remerciez l’équipe de traduction pour ses contributions.

Traduisez « Gutenberg » dans votre langue.

Le développement vous intéresse ?

Parcourir le code, consulter le SVN dépôt, ou s’inscrire au journal de développement par RSS.

Journal

Bug fixes in 5.1.1:

  • Fixes a Firefox regression causing block content to be deleted.

Features:

  • Add a new Search block.
  • Add a new Calendar block.
  • Add a new Tag Cloud block.

Enhancements:

  • Add micro-animations to the editor UI:
    • Opening Popovers.
    • Opening Sidebars.
  • Restore the block movers for the floated blocks.
  • Consistency in alignment options between archives and categories blocks.
  • Set the minimum size for form fields on mobile.
  • Disable the block navigation in the code editor mode.
  • Consistency for the modal styles.
  • Improve the FormToggle styling when used outside of WordPress context.
  • Use the block icons in the media placeholders.
  • Fix rounded corners for the block svg icons.
  • Improve the CSS specificity of the paragraph block styles.
  • Require an initial click on embed previews before being interactive.
  • Improve the disabled block switcher styles.
  • Do not split paragraph line breaks when transforming multiple paragraphs to a list.
  • Enhance the Quote block styling for different text alignments.
  • Remove the left padding from the Quote block when it’s centered.
  • A11y:
    • Improve the permalink field label.
    • Improve the region navigation styling.
  • Remove the 3 keywords limit for the block registration.
  • Add consistent background colors to the hovered menu items.
  • Allow the editor notices to push down the content.
  • Rename the default block styles.

Bug Fixes:

  • Fix a number of formatting issues:
    • Multiple formats.
    • Flashing backgrounds when typing.
    • Highlighted format buttons.
    • Inline code with backticks.
    • Spaces deleted after formats.
    • Inline boundaries styling issues.
    • Touch Bar format buttons.
  • Fix a number of list block writing flow issues:
    • Allow line breaks in list items.
    • Empty items not being removed.
    • Backspace merging list items.
    • Selecting formats at the beginning of list items.
  • Fix the color picker styling.
  • Set default values for the image dimensions inputs.
  • Fix sidebar panels spacing.
  • Fix wording of the nux tip nudging about the sidebar settings.
  • Fix the translator comments pot extraction.
  • Fix the plugins icons color overriding.
  • Fix conflicting notices styles when using editor styles.
  • Fix controls recursion in the redux-routine package.
  • Fix the generic embed block when using Giphy as provider.
  • Fix the i18n message used in the Gallery block edit button.
  • Fix the icon size of the block switcher menu.
  • Fix the loading state of the FlatTermSelector (tags selector).
  • Fix the embed placeholders styling.
  • Fix incorrectly triggered auto-saves for published posts.
  • Fix missing classname in the Latest comments block.
  • Fix HTML in shortcodes breaking block validation.
  • Fix JavaScript errors when typing quickly and creating undo levels.
  • Fix issue with mover colors in dark themes.
  • Fix internationalisation issue with permalink slugs.

Various:

  • Implement the inline format boundaries without relying on the DOM.
  • Introduce the Registry Selectors in the data module.
  • Introduce the Registry Controls in the data module.
  • Allow extending the latest posts block query by using get_posts.
  • Extend the range of allowed years in the DateTime component.
  • Allow null values for the DateTime component.
  • Do not render the FontSizePicker if no sizes defined.
  • Add className prop support to the UrlInput component.
  • Add inline image resizing UI.

Chore:

  • Update lodash and deasync dependencies.
  • Use addQueryArgs consistently to generate WordPress links.
  • Remove merged PHP code (partial).
  • Disable CSS animations in e2e tests.
  • Add ESLint rules to:
    • ensure the consistency of the import groups.
    • protect against invalid sprintf use.
  • Add e2e tests for tags creation.
  • Add the feature flags setup.
  • Implement block editor styles using a filter.

Documentation:

  • Add a new tutorial about the editor notices.
  • Add JavaScript build tools documentation.
  • Enhance the block’s edit/save documentation and code examples.
  • Add e2e test utils documentation.

Mobile:

  • Add bottom sheet settings for the image block.
  • Implement the media upload options sheet.
  • Implementing Clear All Settings button on Image Settings.
  • Avoid hard-coded font family styling for the image blocks.
  • Improve the post title component.
  • Fix the bottom sheet styling for RTL layouts.
  • Support the placeholder prop in the RichText component.