Round up of updates for theme developers on Major Releases

[bph]

From the Summary post by @annezazu

Managing updates for block themes

The discussion around 6.1 feedback led to a conversation about managing updates for block themes. In particular, there were some layout changes that needed to be managed. Keeping up with these changes for each release can lead to a feeling of "Why did we build these themes already?!" when there's so much to keep on top of with each release. It is still taking a lot of work with each release.
@bph the idea was brought up to have a compressed set of links to follow based on audience perhaps for the Developer blog, inspired by Rich Tabor's twitter roundup. We discussed how there were also 2x the number of dev notes for this release compared to 5.9 and 6.0.
In general, there appears to be a cycle of finding a solution to work around current limitations > the gap getting filled in core > needing to update > cycle repeats. There are questions around when this process will get less intense.

[bph]

Looking to how the Fieldguide for a major release is organized, having everything in one spot would be the two sections:

• Themes
• Updated Settings and Styles in Theme.json

A screenshot of the Fieldguide.

There is a third section for the rest of the - Block Editor updates

When we discussed the proposal of the Dev Blog, it often came up that there is a danger of duplication of information. It fragments the information even more the information and also added the burden to update in different places. Especially block themes have already the problem that there is duplication in the Block-editor Handbook as well as in the Theme Handbook.

[bph]

The latest WordPress releases might be covered with the topic idea #45