What's new for developers? (June 2024)

[justintadlock]

This is a rolling discussion for a new monthly series that is intended to keep track of the items, PRs, Trac tickets, and Make blog posts that are interesting/important for developers. The goal is to publish a post on the 10th of each month with the previous month's updates.

Everyone is welcome to contribute to this monthly document. If you find something interesting, just create a new reply to this discussion below.

Google Doc: https://docs.google.com/document/d/1I3msotKyqE1ChKJz5Ha45u2Gl9eytL8U671h4uJxArI/edit?usp=sharing

Resources to track:

• Keeping up with Gutenberg: Index 2022
• A Week in Core
• Gutenberg plugin release posts
• Core editor chat, dev chat, performance team meeting summaries
• Dev Notes

Writer: @ryanwelcher will be the primary author on this post.

[github-actions[bot]]

Heads-up @bph @adamziel @bgrgicak @pbking @mikachan: To include your project's news for developers, please add the information or a link as a comment to this issue. Deadline 8th of next month

[justintadlock]

Some tickets to watch that may include breaking CSS changes for themes (particularly around CSS resets):

• https://github.com/WordPress/gutenberg/issues/57537
• https://github.com/WordPress/gutenberg/pull/57908

[juanmaguitar]

@justintadlock @bph Has it been discussed previously sharing the resources used to curate this content ("Resources to track") in the post itself? I think it could be interesting for developers as a way to help discover how to keep track of changes happening in WordPress.

[justintadlock]

I don't see anything necessarily wrong with some sort of resources section, but I would say that I use that list as more as a rough guideline. The only resources that I use 100% of the time are:

• Gutenberg changelog from the repo
• Trac changesets (you have to manually configure this each month)
• Replies to the monthly ticket

I also note things from other sources like Twitter, Facebook, and third-party blogs (none of which we can link to).

[annezazu]

Want to flag this PR https://github.com/WordPress/gutenberg/pull/61577 I'm not sure if it'll be ready for June but I think it's the perfect thing to include whenever it lands as it'll need feedback and testing from plugin authors.

[ryanwelcher]

Want to flag this PR WordPress/gutenberg#61577 I'm not sure if it'll be ready for June but I think it's the perfect thing to include whenever it lands as it'll need feedback and testing from plugin authors.

The PR is still in draft but it it gets merge before Monday, we can probably get it added.

[ryanwelcher]

This is ready for review

[justintadlock]

Moved this to 2nd review since the first was completed.

[justintadlock]

Nice work, @ryanwelcher! Second review is done and ready. Once finished, you're ready to publish on the 10th!

[ryanwelcher]

Social copy:

Get caught up on the latest changes for WordPress 6.6 and more in the June edition of the monthly developer roundup:

https://developer.wordpress.org/news/2024/06/10/whats-new-for-developers-june-2024/

[justintadlock]

👏 Good work on your first What's new for devs? post, Ryan!

[colorful-tones]

Just wanted to note that this phrase feels out of context and out of place.

Studio by WordPress.com is now available for Windows.

A conversation took place in Post Status Slack.

I would vote to remove it. I do not think there was ill intent in including it but it is dissparaging for some outside folks.

[ryanwelcher]

I would vote to remove it. I do not think there was ill intent in including it but it is dissparaging for some outside folks.

As per the conversation in Post Status slack, the line has been updated to include (external tool):

Studio by WordPress.com is now available for Windows (external tool)