Greg Ziółkowski
@gziolo.pl
Husband, father, open sourcerer, and basketball fan. Writes code at Automattic and contributes to WordPress core.
Reposted by Greg Ziółkowski
This new cadence creates more space to focus on performance, bug fixes, and community contributions. Learn more about what’s changing and why:
make.wordpress.org/project/20...
make.wordpress.org/project/20...
A New Cadence for WordPress Core
There have been a few questions around our decision regarding the WordPress Release cadence, which I’m glad to address. After years of releasing WordPress three times a year, and a recent discussio…
make.wordpress.org
April 16, 2025 at 5:44 PM
This new cadence creates more space to focus on performance, bug fixes, and community contributions. Learn more about what’s changing and why:
make.wordpress.org/project/20...
make.wordpress.org/project/20...
That’s a great project idea. I saw your post shortly after I asked @felixarntz.bsky.social on LinkedIn whether he considered adding MCP to the AI Services plugin. WP CLI sounds awesome, too. Good luck at CloudFest!
February 27, 2025 at 1:28 PM
That’s a great project idea. I saw your post shortly after I asked @felixarntz.bsky.social on LinkedIn whether he considered adding MCP to the AI Services plugin. WP CLI sounds awesome, too. Good luck at CloudFest!
I was thinking about it this week after watching your video explaining how to use Cursor to write a WordPress plugin. The applications for Create Block will quickly drop as AI improves or the scaffolding will be mostly responsible for providing the configuration for AI 😀
January 24, 2025 at 10:54 PM
I was thinking about it this week after watching your video explaining how to use Cursor to write a WordPress plugin. The applications for Create Block will quickly drop as AI improves or the scaffolding will be mostly responsible for providing the configuration for AI 😀
An interesting example is the Avatar block in core which renders differently inside the comment, inside the post, and outside of both of them. It sort of implements visibility pattern internally.
December 11, 2024 at 3:34 PM
An interesting example is the Avatar block in core which renders differently inside the comment, inside the post, and outside of both of them. It sort of implements visibility pattern internally.
For me these go in pair as today is randomly handled in core blocks:
- Logged in/out block could be represented as two blocks controlled by user session state
- Query and Comments block have the block with no results that render only when the items count is 0, the rest of inner blocks otherwise
- Logged in/out block could be represented as two blocks controlled by user session state
- Query and Comments block have the block with no results that render only when the items count is 0, the rest of inner blocks otherwise
December 11, 2024 at 3:28 PM
For me these go in pair as today is randomly handled in core blocks:
- Logged in/out block could be represented as two blocks controlled by user session state
- Query and Comments block have the block with no results that render only when the items count is 0, the rest of inner blocks otherwise
- Logged in/out block could be represented as two blocks controlled by user session state
- Query and Comments block have the block with no results that render only when the items count is 0, the rest of inner blocks otherwise
I personally also would like to see a working group that shapes the development of core blocks so we figure out the process of adding new blocks to core or as canonical blocks. There should be also guidelines introduced of how to structure more complex blocks with children blocks.
December 11, 2024 at 1:07 PM
I personally also would like to see a working group that shapes the development of core blocks so we figure out the process of adding new blocks to core or as canonical blocks. There should be also guidelines introduced of how to structure more complex blocks with children blocks.
These issues I shared are already triaged so we want to solve them, or close them if we decide they should not be implemented. Overall, I think it’s all the same problem of who makes these decisions no matter what project board gets created.
December 11, 2024 at 1:06 PM
These issues I shared are already triaged so we want to solve them, or close them if we decide they should not be implemented. Overall, I think it’s all the same problem of who makes these decisions no matter what project board gets created.
I mostly shared it for inspiration if you decide to create a project. From my perspective the projects with defined scope and duration work best so I would be happy to see the format replicated for every major WP release.
December 11, 2024 at 12:43 PM
I mostly shared it for inspiration if you decide to create a project. From my perspective the projects with defined scope and duration work best so I would be happy to see the format replicated for every major WP release.
There is this issue with the frequent discussion topics about what’s missing in WordPress core in terms of extensibility: github.com/WordPress/gu...
Tracking: A curated list of high-priority extensibility issues and enhancements · Issue #64848 · WordPress/gutenberg
The following is a curated list of extensibility issues that have mostly been identified through various channels and events by DevRel teams, such as Hallway Hangouts, Developer Hours, the #outreac...
github.com
December 11, 2024 at 8:03 AM
There is this issue with the frequent discussion topics about what’s missing in WordPress core in terms of extensibility: github.com/WordPress/gu...