There is a change coming in 6.9 and continuing in 7.0 which is going to impact block developers and people using older blocks that haven’t been updated. The Post Editor is going to be moved to fully be in an iframe. This will mean that block.json v.3 will be needed.

This is a round-up post of the changes related to the Fields API and DataViews that are coming in WordPress 6.9. It looks like the Fields API is maturing. The Fields API may become significant in the future for those interested in dynamic data.

Katie Keith runs Barn2, a plugin shop that sells a number of Woo extensions. She did a survey asking people why they choose WooCommerce. It is interesting to see, or be reminded, that WooCommerce is very flexible. Today with SureCart and FluentCart that flexibility and range of extensions is one of Woo’s advantages, if you need it.

Dries, the Drupal founder, invested in ActivePieces and in this post talks about what comes after automation.

404 Media summarizes the trademark issue between Matt Mullenweg / Automattic and Kevin Geary / Automatic.CSS. Automattic has asked that the Automatic.CSS product name be changed.

For plugin developers, should you use the REST API or admin-ajax? This article says its time to switch to the REST API.

Here is an update on the current status and a high level roadmap for phase 3 of Gutenberg. It looks like block notes will be included in the upcoming 6.9. There is also some progress on data views and data forms.

Beginner and intermediate CSS – This video by Kevin Powell shows how to use CSS combinators. This is standard CSS that you will need to know.

The Breakdance team released beta version 2.6. It includes a number of enhancements and fixes, such as an improved Code Editor, performance optimizations, increased support for some 3rd party plugins, and other quality of life improvements.