Gutenberg 22.9 features bring significant architectural updates, including the new background.gradient support for Group blocks and a foundational EmptyState component for developers. From command palette history to hidden form fields, this release refines the editor experience as we approach WordPress 7.0. Here is what senior developers need to know about the transition.
WordPress Iteration Issues are getting a major overhaul to solve the fragmentation of information in the Gutenberg repository. Senior developer Ahmad Wael explains the new 2026 standards, including mandatory update frequencies and the new iteration templates designed to make core development more transparent and predictable for everyone involved in the ecosystem.
WordPress 7.0 introduces real-time collaboration, but the default HTTP polling can be a performance bottleneck. Learn how to build a custom sync provider using WebSockets and Yjs to achieve low-latency editing. We cover the sync.providers filter, security considerations with REST API tokens, and architectural best practices for enterprise-level WordPress installations.
Explore the dominant WordPress Design Trends for 2026, focusing on the Interactivity API, AI-assisted block building with Telex, and the transition to app-like web experiences. Learn why manual coding is giving way to prompting and how theme.json v3 is stabilizing design systems for professional agencies.
Gutenberg 22.8 features significant upgrades to real-time collaboration, including text selection highlighting and presence UI polishes. Developers benefit from the new Connectors registry API and visual pseudo-state styling for buttons in Global Styles. This release also introduces client-side AVIF support and a ubiquitous Command Palette trigger in the admin bar.
Ahmad Wael breaks down the new Gutenberg Guidelines introduced in version 22.7. Learn how the new Custom Post Type architecture and REST API endpoints create a unified source of truth for editorial standards, and why this is a critical foundation for the future of AI in the WordPress ecosystem.
WordPress 7.0 introduces support for Pattern Overrides in any block that supports Block Bindings, finally breaking the “Core-only” limitation. Developers can now opt-in custom blocks using the block_bindings_supported_attributes filter. This shift allows for more flexible content editing while leveraging the HTML API for static blocks or render_callback for dynamic ones.
The WordPress 7.0 Roadmap is entering its final stages with RC1 set to ship tomorrow. This technical breakdown covers the major shifts from Beta 5, including new pattern override support for custom blocks and native block visibility controls. Learn why these architectural changes matter for your design systems and how to avoid tech debt.
WordPress 7.0 introduces native viewport-based block visibility, allowing developers to show or hide blocks on mobile, tablet, or desktop. However, there is a critical distinction between CSS-based hiding and DOM exclusion that affects performance and server-side parsing. Learn how to refactor your code for the new metadata structure.
WordPress 7.0 introduces native Custom CSS for individual block instances, finally eliminating the need for complex workarounds involving custom classes and Global Styles. This update uses hash-based scoped classes to ensure instance-specific styling remains clean, maintainable, and properly prioritized over default theme styles in the Block Editor.