WordPress 5.9: Fahrplan, Neuigkeiten und Ausblick auf die Features

[tarifa]

Nachdem die Version 5.8 vor einigen Wochen freigegeben wurde, geht die Arbeit unvermindert weiter - das nächste Major-Release, die Version 5.9 wird Mitte Dezember erwartet.

weil hier noch niemand aktiv geworden ist, mache ich das mal eben kurz:

WordPress 5.9: ein Ausblick auf den Fahrplan und Neuigkeiten https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/

Die Timeline - Schritte zur Version 5.9

Go / No Go Date: – October 12
Feature freeze : ab jetzt werden keine neuen Features mehr eingehen: (Bug Fix-Phase) – November 9
Beta 1 – November 16
Release Candidate 1 – November 30
Stable Release – Dezember 14, 2021

Gutenberg-Projektleiter, Matías Ventura, hat kürzlich im Make Core-Blog den vorläufigen Weg zu 5.9 angekündigt ( https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/ )


Unter den angesprochenen Neuigkeiten sind etwa die Folgenden:

• verbesserter PHP8 support
• update für jQuery 3 ( https://core.trac.wordpress.org/ticket/37110 )
• Full Site Editing Verbesserungen
• Möglichkeit den login screen in verschiedenen Sprachen zu zeigen ( https://core.trac.wordpress.org/ticket/43700 )
• Updates für den Gutenberg-Editor ( https://github.com/WordPress/gutenberg/issues/33094 )
• neue Blöcke,
• erweiterte, weiterentwickelte und verbesserte Navigationsmenüs
• Ausbau der Designtools
• ausgebaute und verbesserte Bearbeitungsabläufe für Blockthemen. Es
• Schnittstelle für theme.json
• Gallery-Block-Überarbeitung ( https://make.wordpress.org/core/2021/08/20/gallery-block-refactor-dev-note/ )

Einer der Schwerpunkt von 5.9 dürfte auch auf der Vertiefung des responsiven Designs auf Blockebene liege, so Ventura.

Mehr zum Thema hier: https://make.wordpress.org/core/5-9/

Blocks + intrinsic web design​

vgl. https://make.wordpress.org/core/5-9/

• One of the biggest points of friction for pattern and theme builders are the lack of responsive tools available at a block level. This needs to be solved in a way that doesn’t disproportionally increase interface complexity.
• The block model is a good case to apply some intrinsic design principles, since a block can occupy a place in many different layouts and containers, for which prescriptive media queries that don’t take context into account are inflexible.
• Each block area should be intrinsically responsive allowing blocks to compose together, wrap, stack, and organize themselves to fit the different spaces and screens. For this to work well, container blocks need to absorb more layout controls. (Container queries might help expand this further in the future.)

Patterns​

• With the initial rollout of the new directory there’s a growing need to expand the inserter integration to accommodate broader categories of patterns and the experience of browsing them.
• There’s more work to be done within the setup flow of single and multi-block selections. This also includes improving the mechanisms for transforming to and from patterns, which are still nascent.
• Creation flows with patterns also need expanding from template parts and blocks to pages and templates.

Navigation Menus:​

• The navigation block and navigation screen projects have been underway for quite some time and are a main target for 5.9. With the principal tracking issue about to be completed, a large part of the remaining work is to improve the user experience, reduce complexity, and test as much as possible on themes.

​

An interface for theme.json.​

• 5.8 introduced the scaffolding necessary for themes to take the reins over how various aspects of blocks render and how the interface is controlled. The natural next step ahead is to develop the user interface that will allow users to interact with these style properties. This goes by the project name “global styles” and an updated design is currently in prototype stage.
• It should be appreciated how important it is to leverage the global reach of CSS rules as we combine it with the power of blocks. The current structure deals with two large groups of design targets: blocks and elements. Elements represent things that can be styled globally and across blocks (such as “text”, “links”, “captions”, etc).

mehr insgesamt hier https://make.wordpress.org/core/5-9/

 

[netzgestaltung]

also was mir bei 5.8 aufgefallen ist, ist das die Gutenbergwidgets ein 403 Forbidden bei Legacy Custom HTML Widgets anzeigt und nicht mehr bearbeiten lässt: https://github.com/WordPress/gutenberg/issues/32648