Mark Westguard was recently on the Do the Woo show and he shared some good points that plugin developers launching a product will find useful.

The theme.json file, which is used in block and hybrid themes, is getting a bump to version 3 in order to account for some default font and spacing size changes.

WordPress has an API for storing and loading options, the Options API. Some changes to the Options API are coming with WordPress 6.6. One of the settings when creating an option is if the option should be auto loaded with each page. Up until now, the default when an option is created was “yes” to auto load it. However, a large amount of auto-loaded data can hurt page performance. The default is being changed to “null” and a ceiling on the size of auto-loaded options is being introduced. These and other changes are discussed in this article on the make blog.

Here is a comprehensive tutorial on creating a block from scratch. It’s fairly advanced and touches a lot of areas. The tutorial is from Ron Huereca and he chose a Gravatar block as an example to demonstrate REST calls and saving attributes.

Here is a developer resource – A searchable directory of WordPress filter and action hooks created by Tiffany Brown.

A minimalist plaintext WordPress theme. This one looks like a Classic theme. I imagine you can do something similar with block themes.

Plugin developers – Are you working on the settings page for your plugin, or planning a refresh? Anh Tran took a look at the admin screens of a number of plugins and shared his favorite designs.

For plugin developers – Ronald Huereca has a straightforward tutorial about namespaces and using them in your plugin.

For plugin developers – Plugins hosted on WordPress org have an assets folder for icons, the banner, screenshots, etc. Here is a guide for using the assets folder.