Gutenberg

Descrición

The block editor was introduced in core WordPress with version 5.0 but the Gutenberg project will ultimately impact the entire publishing experience including customization (the next focus area). This beta plugin allows you to test bleeding-edge features around editing and customization projects before they land in future WordPress releases.

Descubre máis sobre o proxecto.

Enfoque na edición

O editor creará unha nova experiencia de creación de páxinas e entradas que fará que escribir publicacións enriquecidas non implique esforzo algún, e que terá “bloques” para facer fácil o que actualmente require shortcodes, HTML personalizado, ou os imprevisibles incrustados automáticos. — Matt Mullenweg

Unha cousa que distingue a WordPress doutros sistemas é que che permite crear estructuras de publicacións tan completas como te podas imaxinar — pero só se sabes HTML e CSS e constrúes o teu propio tema a medida. Ao pensar no editor como unha ferramienta que che permite escribir publicacións ricas e crear fermosos deseños, podemos transformar WordPress en algo que os usuarios aman de WordPress, en lugar de algo que elixen porque é o que todos os demáis empregan.

Gutenberg considera o editor como algo máis que un campo de contido, e revisita un deseño que permaneceu prácticamente inalterado durante case unha década. Isto permítenos deseñar holísticamente unha experiencia de edición moderna e construir unha base para o que virá.

Velaquí por que estamos a mirar toda a pantalla de edición, en lugar de só o campo de contido:

  1. O bloque unifica múltiples interfaces. Se agregamos iso na la parte superior da interfaz existente, agregaría complexidade, en vez de eliminala.
  2. Ó volver a visitar a interfaz, podemos modernizar a experienza da escritura, edición e publicación, tendo en conta a facilidade de uso e a simplicidade, o que beneficia tanto aos usuarios novos como aos ocasionais.
  3. Cando a interfaz de bloque singular toma o centro do escenario, mostra un camino claro para que os desenvolvedores creen bloques premium, superiores a shortcodes e widgets.
  4. Considerando que toda a interfaz senta a base para a seguinte prioridade, a persoalización de todo o sitio.
  5. Centrarnos no editor a pantalla completa brindanos tamén a oportunidade de modernizar drásticamente os cimentos e dar pasos de cara a un futuro máis fluido basado en JavaScript que aproveite ao máximo a API REST de WordPress.

Bloques

Os bloques son a evolución unificadora do que agora está cuberto, de diferentes maneiras, mediante shortcodes, incrustacións, widgets, formatos de publicación, tipos de contido personalizados, opcións de tema, meta-boxes e outros elementos de formato. Adoptan a amplitude da funcionalidade que WordPress é capaz de ofrecer, coa claridade dunha experiencia de usuario consistente.

Imaxina un bloque “empleado” persoalizado que un cliente pode arrastrar a unha páxina Acerca de para mostrar automáticamente unha imaxe, nome e biografía. Todo un universo de plugins que extenden WordPress da misma forma. Menús e widgets simplificados. Usuarios que poden entender e usar instantáneamente WordPress — e o 90% dos plugins. Esto permitirá redactar fácilmente publicacións fermosas como este exemplo.

Consulta as FAQ para obter respostas ás dúbidas máis comúns sobre o proxecto.

Compatibilidade

As publicacións son compatibles con versións anteriores, e os shortcodes seguirán funcionando. Estamos explorando continuamente cómo se poden acomodar metaboxes altamente persoalizados, e estamos buscando solucións que van dende un plugin para deshabilitar Gutenberg ata detectar automáticamente si cargar Gutenberg ou non. Se ben queremos asegurarnos de que a nova experiencia de edición dende a escritura ata a publicación sexa fácil de usar, comprometemonos a encontrar unha boa solución para sitios existentes altamente persoalizados.

As etapas de Gutenberg

Gutenberb planea ter tres etapas. A primeira, con inclusión prevista en WordPress 5.0 enfocada na experiencia de editar a publicación e na implementación de bloques. Esta fase inicial está enfocada na perspectiva de priorizar o contido. O uso de bloques como detallamos máis arriba, permiteche enfocarte na aparencia do contido sen a distración doutras opcións de configuración. Isto axudará a todos os usuarios a presentar o seu contido de forma completa, directa e visual.

Estes elementos fundacionais cimentarán o camiño das etapas dous e tres, planeadas para o ano que vén, para levar a publicación alén dentro de modelos e, finalmente, unha total personalización.

Gutenberb é un gran cambio e haberá maneiras de asegurar que a funcionalidade existente (como códigos curtos e metacaixas) continúen funcionando mentres se lles permite aos desenvolvedores o tempo e o modo para facer a transición efectiva. Ao final, abrirá novas oportunidades aos desenvolvedores de complementos e temas para servirlles aos usuarios unha máis completa e visual experiencia que se beneficiará dun conxunto de ferramentas facilitadas polo núcleo.

Contribuíntes

Gutenberg está sendo construído por moitos colaboradores e voluntarios. Aquí tes a lista completa CONTRIBUTORS.md.

Blocks

Este plugin proporciona 17 bloques.

core/categories
Gutenberg
core/block
Gutenberg
core/site-title
Gutenberg
core/tag-cloud
Gutenberg
core/post-title
Gutenberg
core/latest-comments
Gutenberg
core/archives
Gutenberg
core/calendar
Gutenberg
core/social-link-
Gutenberg
core/legacy-widget
Gutenberg
core/navigation
Gutenberg
core/latest-posts
Gutenberg
core/shortcode
Gutenberg
core/search
Gutenberg
core/post-content
Gutenberg
core/template-part
Gutenberg
core/rss
Gutenberg

Preguntas frecuentes

Como podo enviar suxestións ou pedir axuda sobre un erro?

Encántanos que nos informes de erros, suxestións de características ou calquera outra idea! Por favor, pásate polapáxina de problemas en GitHub para procurar problemas existentes ou informar dun novo. Aínda que tratamos de facer un seguemento dos problemas aquí, no foro do plugin, obterás unha resposta máis rápida (e redúcese a duplicación de esforzos) mantendo todo centralizado no repositorio de GitHub.

Como podo axudar?

Chamámoslle a este proxecto de editor «Gutenberg» porque é un gran traballo de fondo. Traballamos nel cada día en GitHub e encantaríanos contar coa túa axuda en construílo. Tamén serás benvido/a en comentarios, o máis doado é unirte na nosa Canle de Slack, #core-editor.

Ver tamén CONTRIBUTING.md.

Onde pode ler máis sobre Gutenberg?

Comentarios

10 de Decembro, 2019
So many of the reviews of Gutenberg are binary—black or white. They claim Gutenberg is either total garbage not even worthy of existing (the vast majority), or the best editor that has ever been built (far fewer, but still there). The reality is far more nuanced. The editor doesn't completely suck. But it also isn't perfect. Are their problems and rough edges with Gutenberg? Yes. Is the editor a move in a positive direction for WordPress? Absolutely. Like many reviewers, at first I hated Gutenberg. Looking back, I think a lot of that hate came from a gut reaction and aversion to change. Some was definitely attributed to the early days of Gutenberg indeed being a hot mess. The editor has come a long, long way since the initial release and is now far more functional and useful. I now exclusively use it for new sites and am working on transitioning a number of existing sites over (more on this later). In total I am using Gutenberg on 12 different sites. The good: My clients who are trained on Gutenberg love it! It is far closer to WYSIWYG than the old editor. Now that they are used to the difference in how the editor works, I often get comments about how simple things are. Gutenberg makes it is easier to do advanced things such as column layout. Many reviewers claim that even simple tasks require several more clicks. That simply isn't true. And now all tasks are essentially treated the exact same. Everything is a block. Once you understand blocks and that they can have individual settings, the rest falls into place. My clients also make far less mistakes, especially since they used to rely on error prone shortcodes for so much of the advanced functionality. It was inevitable that a client would inadvertently delete a ] for a shortcade and email me asking why their site was broken. When you embrace it fully, Gutenberg can be incredibly powerful. As a developer, the editor being completely written in JS, and having complete access to core data stores means I can create plugins and tools for users I could have only dreamed of before. For example, I recently built a live accessibility checker. It checks the content and metadata (as the user types!) for common accessibility issues, like missing alt attributes on images or incorrect heading hierarchy. My users now make far less accessibility mistakes when publishing content! This makes for a better web for all. There are more keyboard shortcuts. Saving a post, true undo and redo, block insertion with / etc. All great additions. That said, I do miss the heading shortcuts of the old editor. Of course, Gutenberg still has some rough edges: The number one is speed. It is still fairly slow to load the initial edit page (6 or 7 seconds, even in a local dev environment) and pages with a large number of blocks (i.e. a few hundred) can make the interface less responsive. I would love to see a release dedicated to performance and bug fixes. I know development is charging ahead on things like widgets, content areas, and editing site wide content, but I would strongly recommend shoring up what is already in place a little more first. The second biggest issue (at least from the perspective of a plugin/theme developer) is documentation. It sucks. As a developer working with WordPress for a dozen years, I'm used to very detailed and descriptive documentation, with lots of examples. The documentation for Gutenberg is largely missing or cryptically worded. Only the very basics (like registering a simple block) are decently documented. As soon as I start branching out beyond the basics (like working with data stores or APIs) I spend a large amount of time digging through Gutenberg's JS files looking to see how the developers of Gutenberg did something. I'm a less productive developer because of it. Some interactions can be cumbersome and clumsy. For example, if you have a number of blocks nested within each other, it can be very difficult to select the exact block you want. I end up needing to use my up and down arrow keys, or the block navigation far too often. Another example is around finding the exact right place to click to insert a new nested block when using InnerBlocks. If your block has any padding, this can be maddening. Migrating existing sites is very difficult and time consuming. I have only moved a couple sites to Gutenberg, but it has often involved completely reworking the content of every page/post. This especially applies to more complex sites with numerous shortcodes and layout builders. I'm honestly not sure what can be done to address this, but it is a big burden. Finally, a minor gripe, the HTML and CSS of the editor makes styling blocks in the editor challenging. All the negative margins, absolutely positioned elements, and dozens of nested HTML elements mean I spend a lot of time digging through the web inspector. Conclusion: For all those asking to abolish Gutenberg entirely, I feel that is a rash judgement. Gutenberg offers a lot of benefits, if you're willing to embrace it fully. In hindsight, I would have suggested only enabling Gutenberg by default on new installs of WordPress, and perhaps waiting a little longer for some of the major shortcomings to be worked out. That said, today Gutenberg is quite powerful and heading in the right direction.
7 de Decembro, 2019
I hoped that the kinks would be worked out by now, but there are still tons of normal things that you can't do in Gutenberg because of how blocks work. I try to minimize plugins for performance and security, but I have had to install way more than usual just to do things that were simple in the old editor but impossible in Gutenberg. And it's cumbersome as well. I haven't yet bailed out and installed the Classic Editor plugin, because I thought I should give Gutenberg a fair chance, but I might have to. For the minority who like Gutenberg, it would be fine as a plugin, but why can't the default editor simply be an editor?
6 de Decembro, 2019
How did this abomination ever graduate from beta to prime time??? Simply put... it sucks BDD! No one likes it... everyone is screaming about it... so, move on!!! The only proof you need is that the #1 trending plugin simply reverts Gooberberg to the previous editor! Wanna make a REAL GUI block editor? Shoulda checked out the successful ones first... Elementor comes to mind first. #ShamefulWP #PhotoMatt
Ler todas as 2.971 opinións

Colaboradores e desenvolvedores

“Gutenberg” é un software de código aberto. As seguintes persoas colaboraron con este plugin.

Colaboradores

“Gutenberg” foron traducidas ao 46 locales. Grazas a os desenvolvedores polas súas colaboacións.

Traducir “Gutenberg” ao teu idioma.

Interesado no desenvolvemento?

Revisa o código, bota unha ollada aorepositorio SVN, ou subscríbete ao log de desenvolvemento por RSS.

Rexistro de cambios

Features

Enhancements

Bug Fixes

APIs

Experiments

Documentation

Performance

Various