New on the blog: Secret Selves and Fading Faces
https://robertafidora.com/news-press/blog/secret-selves-and-fading-faces
Join the Neighbourhood: https://robertafidora.com/music-shop#join-the-neighbourhood
#Music #Musicians #Fediverse #FediMusic #Electronic #Blog #MusicBlog #Blogs #BeYourOwnPlatform
If you want to support me in the meantime, it would be nice to at least have enough paying subscribers for https://geryow.com that my monthly hosting costs are covered. Currently covering a 1/3.
(A one year anniversary post currently in the works, along with an analysis of Freeports in Daredevil: Born Again vs the Real World.)
https://medium.com/the-story-well
NEW MEDIUM PUBLICATION!
Medium writers, Submit Your Story Now.
Fiction or Non-fiction. Literary and all genres.
#TheStoryWell #newpublication #publications #medium #stories #articles #blogs #writingcommunity
Another find from #powRSS:
After saying their goodbyes to Dr. Chorus1, the gang sets about chasing the gnolls off in exchange for the Nail-Eater goblins guiding them through the sewers. A brief debate ensures...
Random click, courtesy of #powRSS:
https://www.vknabel.com/posts/2021-11-19-uinavigationbar-black-after-xcode-13-upgrade/
In case your UINavigationBar has been set to a custom color and the navigation bar is not translucent, you will experience a visual regression when updating to Xcode 13. The navigation bar background will be black - until you start scrolling. Then it behaves as expected.
WordPress 7 Is the Most Significant Release in Over a Decade—Here’s What It Actually Changes
Five days ago, on May 20, 2026, WordPress 7.0 “Armstrong” shipped. Named after jazz legend Louis Armstrong—the man who transformed jazz from an orchestral art form into a solo act—this release carries weight that matches its namesake. WordPress 7 doesn’t just add features. It reframes what the platform fundamentally is. After an unusually quiet 2025, the core team delivered a release that introduces native AI into the CMS, rebuilds the admin dashboard for the first time since 2013, and officially opens Gutenberg Phase 3. That’s a significant set of structural changes for one version.
So why does this matter right now? Because the CMS landscape is changing fast. AI-native competitors are entering the market. Teams expect collaborative tools that behave like modern software. And WordPress—powering over 40% of the web—has to keep pace without breaking the ecosystem that made it dominant. WordPress 7 is the platform’s direct answer to all three pressures. Whether it succeeds depends entirely on the details. Let’s get into them.
What Does WordPress 7.0 Actually Change at the Platform Level?
WordPress 7 is built around one defining idea: infrastructure first. The release doesn’t chase shiny editorial features for their own sake. Instead, it lays a technical foundation—particularly around AI—that future versions will build on. That’s a deliberate strategic choice, and it’s worth understanding before looking at individual features.
WordPress 7 merges Gutenberg plugin versions 22.0 through 22.6 into core. That represents roughly six months of focused development work. The core theme across all of it, as defined by the release team, is “Workflows.” Better tools for creators, better infrastructure for developers, and a modernized environment for everyone in between.
Furthermore, WordPress 7.0 raises the minimum supported PHP version to 7.4. Sites running PHP 7.2 or 7.3 will remain on the WordPress 6.9 security branch and won’t receive new features until they upgrade. For best performance, the release recommends PHP 8.3 or higher. That’s not a minor footnote—it’s a meaningful technical line in the sand.
The Gutenberg Phase 3 Transition
Gutenberg has followed a four-phase roadmap since it launched. Phase 1 improved the writing experience. Phase 2 delivered full site editing. Phase 3, officially launched with WordPress 7, focuses on collaboration. Phase 4 targets multilingual support, expected from 2027 onward.
The transition to Phase 3 means WordPress is evolving from a solo publishing tool into a shared workspace. As one widely cited comparison puts it, Phases 1 and 2 gave you Microsoft Word. Phase 3 is the move toward Google Docs. That shift changes everything about how teams think about WordPress—and it starts here, with WordPress 7.
Native AI in WordPress Core: What the WP AI Client Actually Does
WordPress 7 ships a native AI client in core. This is not an AI-powered feature—it’s an AI infrastructure layer. Understanding that distinction matters enormously for developers, agencies, and site owners.
The WP AI Client is a PHP API built into the WordPress core. It gives WordPress a standardized, provider-agnostic mechanism for communicating with external generative AI models. Critically, no data leaves your site until you configure a connection yourself. There’s no passive data sharing, no background AI calls. The AI Client is a conduit, not a service.
The Abilities API: Human- and Machine-Readable Capabilities
Paired with the AI Client is the Abilities API. This is one of the most technically significant additions in WordPress 7. The Abilities API allows plugins, themes, and WordPress core itself to register their capabilities in formats that are readable by both humans and AI agents.
In practical terms, this means an AI assistant inside WordPress can understand what your installed plugins can do—and use them. A plugin that manages e-commerce orders can expose its “create order” capability through the Abilities API. An AI agent can then discover and trigger that capability in response to a natural-language request. That’s a genuinely new paradigm for WordPress plugin architecture.
WordPress 7 also ships a JavaScript counterpart: the Client-Side Abilities package. It brings a built-in UI and command palette integration into the browser, extending AI abilities across the full stack—both server-side and client-side. Together, the WP AI Client and the Abilities API create what the release team describes as a “full-stack AI layer” that plugin and theme developers can build against without needing to manage provider-specific integrations themselves.
AI Connectors: Managing Providers from a Central Hub
The Connectors screen, accessible under Settings > Connectors in wp-admin, serves as the central management point for all external AI connections. WordPress 7 ships with three official provider presets: OpenAI, Google Gemini, and Anthropic Claude. You can also add custom connections for any AI provider through the new Connectors API.
One credential entered at Settings > Connectors is shared across all compatible plugins. That solves a real friction point that anyone managing multiple AI plugins will recognize immediately. Previously, every plugin managed its own API keys and connections in isolation. WordPress 7 centralizes that entirely.
Additionally, an optional separate AI plugin—available as a manual install, not bundled with core—extends the experience with concrete editorial tools: image generation and editing, title and excerpt creation, and alt-text suggestions. That distinction is important. The core AI infrastructure is deliberate and minimal. The editorial AI features require an explicit opt-in.
My Take on the AI Architecture Decision
Personally, I think this is exactly the right approach. Baking AI features directly into the core would create maintenance overhead and vendor dependencies that could fracture the ecosystem. Instead, WordPress 7 makes AI a first-class architectural concern without mandating how you use it. The Abilities API in particular feels forward-looking—it treats WordPress not just as a publishing tool but as a platform that AI agents can operate within. That’s a meaningful shift in how we should think about CMS architecture going forward.
The WordPress 7 Admin Overhaul: Finally, a Modern Dashboard
The WordPress admin interface hadn’t seen a significant visual overhaul since 2013. That’s thirteen years. WordPress 7 changes that decisively.
The new dashboard ships with a fresh color scheme, cleaner finishes, and smooth view transitions that animate navigation between admin screens. Technically, this is implemented through the View Transitions API within the boot package. WordPress now orchestrates zoom and slide animations during state changes without remounting the canvas on route changes. The result is a dashboard that feels like a modern web application rather than a legacy CMS backend.
DataViews: Replacing the Legacy List Table
One of the most visible changes in wp-admin is DataViews. This is a React-based replacement for the old PHP-rendered admin list tables—the grid of posts, pages, or users that you’ve been navigating since WordPress 2.x.
DataViews loads instantly without page reloads. It supports grid and list layouts, inline filtering, and bulk editing all on the client side. As a WordPress Design System component, it also enforces consistent spacing and interaction patterns across all admin screens. Consequently, the admin starts to feel like a cohesive product rather than a collection of independently built screens.
The Command Palette
WordPress 7 introduces a Command Palette, accessible via Ctrl+K on Windows or ⌘K on Mac. A persistent icon in the upper admin bar gives you access from anywhere in the dashboard. You can jump to any screen, setting, or action without navigating through menus. For power users, this alone meaningfully changes daily workflow inside wp-admin.
Dedicated Font Management
A new Fonts page under Appearance > Fonts gives you centralized typography management regardless of which theme you’re running. This works for block themes, hybrid themes, and classic themes alike. You can install, upload, and manage your font collection from a single location. Previously, font management was fragmented—block themes handled it one way, classic themes another. WordPress 7 normalizes that experience across the board.
Visual Revision Interface
WordPress 7 ships a visual revision scrubbing interface. Instead of reading a list of revision timestamps, you can now scrub through a visual timeline of page versions, see what changed at a glance, and restore any revision in one click. For editorial teams managing high-revision content—landing pages, editorial articles, and long-form guides—this is a genuine workflow improvement.
New Blocks in WordPress 7: Icons, Breadcrumbs, and Heading Controls
WordPress 7 adds several new blocks to the core and extends existing ones. Each addition fills a specific gap that developers had previously solved through custom code or third-party plugins.
Icons Block
The new Icons block lets you embed SVG icons directly within content without a plugin. You can scale, color, and position icons from within the block editor. For designers building content-rich pages, this removes a persistent dependency on icon plugins that added unnecessary weight to the plugin stack.
Breadcrumbs Block
A native Breadcrumbs block is now available for navigation markup. This brings a long-requested structural element into core with full block editor support—customizable separators, styling controls, and schema-compatible output. SEO-conscious site builders will appreciate not having to rely on theme functions or plugin-based breadcrumbs.
Cover Block Video Backgrounds
The Cover block now supports video-embed backgrounds. You can use a video embed URL directly as a background source, opening more dynamic design options without custom code. This extends the Cover block’s usefulness for hero sections and featured content areas significantly.
Responsive Block Visibility Controls
WordPress 7 ships viewport-based block visibility controls. You can now show or hide individual blocks based on screen size directly within the block editor, without writing custom CSS or using a visibility plugin. This is a feature that page builders have offered for years. Having it natively in the core removes another reason to reach for a heavyweight builder plugin.
Enhanced Pattern Editing
Pattern editing gets a dedicated Spotlight mode and an Isolated Editor mode in WordPress 7. Spotlight mode focuses the canvas on the pattern you’re editing while dimming surrounding content. Isolated Editor mode opens the pattern in a clean, full-screen editing context. Both changes make pattern management significantly more intuitive for teams building reusable layout components.
Developer Tools in WordPress 7: PHP-Only Block Registration and New APIs
WordPress 7 introduces PHP-only block registration. Developers can now register blocks entirely in PHP without requiring a corresponding JavaScript build step. This dramatically simplifies the workflow for blocks that don’t need client-side interactivity—utility blocks, structural blocks, query-driven displays. The dependency on Node.js tooling for every block type has been a friction point for backend-focused developers for years. PHP-only registration addresses that directly.
Beyond block registration, WordPress 7 ships updates to the Block Bindings API, Interactivity API improvements, and continued DataViews and DataForms work. The Field Guide for 7.0 documents each of these in developer-facing detail in the official WordPress developer documentation.
Theme developers gain another meaningful tool: block theme patterns as a replacement strategy for building new themes. The expanded Style Variations system means you can deliver a range of visual options from a single theme codebase without maintaining multiple separate themes. For agencies maintaining large theme portfolios, this is a real operational simplification.
What Didn’t Ship in WordPress 7—And Why It Matters
The biggest story in WordPress 7’s development is what isn’t in it: real-time collaboration (RTC). This feature—simultaneous multi-user post editing with live cursors and instant syncing, essentially Google Docs inside the block editor—was the flagship promise of Gutenberg Phase 3. It was pulled from the 7.0 release on May 8, 2026, less than two weeks before launch.
Why Real-Time Collaboration Was Removed
The official statement from Matt Mullenweg cited concerns around race conditions, server load, memory efficiency, large feature surface area, and recurring bugs found through fuzz testing. RTC had been in private beta since October 2025 for enterprise WordPress VIP customers. The editing experience tested well at scale. The infrastructure underneath it did not.
The deeper issue, as technical analysis since the decision has made clear, is architectural. Real-time collaboration isn’t just a UI layer on top of existing WordPress behavior. It fundamentally changes how content changes are stored, broadcast, and merged. Furthermore, it requires a new core database table. And it shifts the load pattern of WordPress sites from occasional writes to continuous synchronization. Those are infrastructure-level concerns, not feature-polish problems.
Mullenweg’s call to pull the feature was the right one. Shipping unstable real-time editing across a CMS used by hundreds of millions of sites would have been damaging in ways that no feature win could justify. The community response was, by most accounts, a collective sigh of relief rather than outrage.
The Framework I’m Calling “Deferred Ambition”
What happened with RTC in WordPress 7 illustrates a pattern I’d define as Deferred Ambition: the strategic decision to remove a marquee feature that works in testing but creates infrastructure risk at the platform level, in favor of shipping a more stable foundational release that makes the feature possible long-term. This is different from a simple delay. It’s an architectural judgment call. And in the case of WordPress 7, it was the correct one.
The realistic timeline for RTC, based on the current technical trajectory, is WordPress 7.3 in 2027—not 7.1 in August 2026, and probably not 7.2 in December 2026. Anyone planning editorial workflows around real-time collaboration in WordPress should plan accordingly.
No Twenty Twenty-Six Default Theme
WordPress 7 also ships without a new default theme. There is no “Twenty Twenty-Six” in this release. The existing block theme remains as the default. This is less controversial than the RTC removal, but it does signal that the release team chose to invest resources in infrastructure and tooling over presentation-layer additions.
WordPress 7 vs. the Competition: Where Does It Stand?
WordPress 7 arrives in a market that has changed considerably since WordPress 6.9. Webflow, Framer, Ghost, and various headless CMS platforms have all made meaningful moves in the creator and agency market. AI-native tools are entering the content production workflow from multiple angles. WordPress’s response with 7.0 is characteristically its own: open, extensible, and infrastructure-first rather than feature-first.
The AI Connectors framework is provider-agnostic by design. WordPress doesn’t pick a winner between OpenAI, Google, and Anthropic. It builds the plumbing and lets you connect what you want. That’s philosophically consistent with everything WordPress has done for twenty years. It’s also strategically smart in a moment when the AI provider landscape is genuinely uncertain.
What WordPress still lacks, compared to some newer platforms, is out-of-the-box speed and editorial elegance for non-technical users. The Gutenberg editor remains complex for casual users. The plugin ecosystem is powerful but introduces maintenance overhead that simpler platforms avoid by design. WordPress 7 doesn’t fully solve those gaps. It does, however, invest in the infrastructure that makes closing them possible over the next several releases.
WordPress 7.0 Pros and Cons: An Honest Assessment
What WordPress 7 Gets Right
The AI architecture is genuinely thoughtful. Centralizing connections through the Connectors screen, building a provider-agnostic Abilities API, and keeping core AI features minimal while enabling extensibility—that’s a well-designed system. The admin dashboard overhaul is long overdue and meaningfully improves daily usability. PHP-only block registration removes a real developer friction point. The visual revision interface solves a real editorial workflow problem. And the decision to pull RTC rather than ship it broken demonstrates editorial discipline that the platform hasn’t always shown in the past.
What WordPress 7 Still Needs
The absence of real-time collaboration is genuinely significant for teams that were planning workflows around it. The 7.1 and 7.2 releases in August and December 2026, respectively, will need to deliver meaningful progress on RTC, or the gap between WordPress’s collaboration promises and its actual capabilities will become a competitive liability. The editor also still struggles with complexity for non-technical users—something no feature release has fully addressed. And performance optimization for AI Connectors on shared hosting, where outbound HTTPS restrictions can interfere, needs clearer documentation and community guidance.
How to Upgrade to WordPress 7 Safely
WordPress 7 is a major release. Upgrading production sites directly is not advisable without a tested staging workflow. Here’s the approach I’d recommend for any site with real traffic or revenue implications.
First, verify your PHP version. WordPress 7 requires PHP 7.4 as a minimum and recommends PHP 8.3 or higher. If you’re on 7.2 or 7.3, upgrade PHP before touching the WordPress version. Second, create a complete site backup before doing anything else. Third, set up a staging environment and run your full plugin and theme stack against the WordPress 7 release candidate before pushing to production. The new iframed editor detection logic and changed pattern editing defaults are the most likely sources of unexpected behavior in existing setups. Fourth, audit your plugin stack for compatibility—particularly any plugins that build their own AI integrations or manage their own admin list tables, since both areas see structural changes in 7.0. Finally, after staging validation, push to live with a rollback plan ready.
The official download is available at WordPress.org. The WordPress developer documentation includes the full Field Guide for 7.0 with developer-specific migration notes.
What Comes After WordPress 7: The Road to 7.1 and 7.2
WordPress returns to a three-releases-per-year cadence in 2026. Version 7.1 is scheduled for August 19, 2026, timed to WordCamp US. WordPress 7.2 is expected around December 8–10, 2026, aligned with the State of the Word address. Matt Mullenweg has indicated he wants WordPress to target four releases per year starting from 2027.
For WordPress 7.1, the likely priorities are continued Phase 3 collaboration work, including further RTC development in the Gutenberg plugin. Additional AI Connectors ecosystem growth, as third-party providers build connector plugins, is also probable. The groundwork laid by WordPress 7’s DataViews system will likely expand to more admin screens in 7.1 and 7.2. And the multilingual Phase 4 work will begin building momentum as Phase 3 matures.
My prediction: WordPress 7.1 will be a quieter release focused on stability and ecosystem growth. WordPress 7.2 may be where real-time collaboration returns to the conversation, at least in a feature plugin form. The platform’s trajectory over the next eighteen months depends heavily on whether the AI Connectors ecosystem develops the depth and quality needed to make the Abilities API genuinely compelling for non-technical users.
The “AI-Integrated WordPress” Framework: What It Means Long-Term
I want to name something that I think gets undersold in most coverage of WordPress 7. The AI integration here isn’t about adding AI features to a CMS. It’s about repositioning WordPress as a platform that AI agents can operate within and extend. The Abilities API makes WordPress capabilities machine-readable. The Client-Side Abilities package brings that into the browser. Together, they make WordPress the substrate for an AI-augmented publishing workflow rather than just a recipient of AI-generated content.
That’s a fundamentally different architectural posture from “add an AI writing assistant button to the editor.” It treats WordPress as infrastructure—and it opens possibilities that aren’t yet visible in WordPress 7 itself but will become concrete over the next two to three release cycles.
Whether the developer community builds the plugins that make this vision tangible remains to be seen. The infrastructure is now there. The ecosystem has to show up. Based on how the WordPress community responded to Full Site Editing—slowly at first, then comprehensively—I’m cautiously optimistic that AI-native WordPress plugins built on the Abilities API will be a significant growth area by 2027.
Where to Get Started with WordPress 7
If you’re ready to build on WordPress 7, WordPress.com is the most direct path in. It’s the managed hosting platform built and maintained by Automattic—the company behind WordPress core—which means new releases like 7.0 roll out natively, without you managing servers, PHP versions, or update compatibility. Plans range from a free tier to fully managed business and commerce options with priority support. For designers, developers, and content teams who want WordPress 7’s AI infrastructure and modernized dashboard without the hosting overhead, it’s worth a look.
Try WordPress.comThe WordPress 7 Q&A:
What is WordPress 7.0?
WordPress 7.0, named “Armstrong” after jazz musician Louis Armstrong, is the first major WordPress release of 2026. It was released on May 20, 2026. The release introduces native AI infrastructure into WordPress core, a modernized admin dashboard, new blocks and design tools, and officially launches Phase 3 of the Gutenberg roadmap, which focuses on collaboration workflows.
What is the WP AI Client in WordPress 7?
The WP AI Client is a PHP API built into WordPress 7 core. It gives WordPress a standardized, provider-agnostic way to communicate with external generative AI models—OpenAI, Google Gemini, Anthropic Claude, and others. No data leaves your site until you configure a connection at Settings > Connectors and explicitly enable it.
What is the Abilities API in WordPress 7?
The Abilities API is a new interface in WordPress 7 that lets plugins, themes, and core register their capabilities in formats readable by both humans and AI agents. This allows AI tools operating within WordPress to discover and use plugin functionality automatically, without manual integration per plugin.
Does WordPress 7 have real-time collaboration?
No. Real-time collaboration was removed from WordPress 7.0 on May 8, 2026, due to unresolved concerns around race conditions, server load, memory efficiency, and architectural complexity around content synchronization. It remains a priority feature for a future release, most realistically WordPress 7.3 in 2027 or as a feature plugin in the Gutenberg testing ground.
What PHP version does WordPress 7 require?
WordPress 7.0 requires PHP 7.4 as the minimum supported version. PHP 7.2 and 7.3 are no longer officially supported. The recommended version for best performance and security is PHP 8.3 or higher.
What are DataViews in WordPress 7?
DataViews is a React-based replacement for the legacy PHP-rendered admin list tables in wp-admin. It loads without page reloads, supports grid and list layouts, and enables inline filtering and bulk editing on the client side. It’s the most visually significant change to the WordPress admin interface in WordPress 7.
What new blocks ship with WordPress 7?
WordPress 7 adds a native Icons block for SVG icon embedding and a Breadcrumbs block for structured navigation markup and extends the Cover block to support video-embed backgrounds. It also adds responsive block visibility controls, letting you show or hide blocks based on screen size directly in the editor.
Is WordPress 7 good for SEO?
Yes. The native Breadcrumbs block produces schema-compatible markup. The visual revision interface makes content quality management easier. Font management improvements and responsive block visibility controls reduce reliance on heavy plugins that can affect page performance. The overall admin modernization also reduces workflow friction that can slow publishing cadence.
What is the WordPress 7.1 release date?
WordPress 7.1 is scheduled for August 19, 2026, timed to align with WordCamp US. WordPress 7.2 is expected around December 8–10, 2026, aligned with the State of the Word address.
Should I upgrade to WordPress 7 now?
Yes, with preparation. Test your full plugin and theme stack on a staging environment first. Verify you’re running PHP 7.4 or higher—PHP 8.3 is recommended. Pay particular attention to plugins that build their own AI integrations or rely on admin list table behavior, as both areas see structural changes in WordPress 7. After staging validation, upgrade with a full site backup in place.
Check out WE AND THE COLOR’s Web Design section for more.
#ai #blogs #webDesign #wordpress #wordpress7 #wordpress70
Minal day of Premier League season
After a 22 year wait, Arsenal have their hands on the Premier League trophy again. Tottenham just about managed to stay up, with West Ham relegated to the Championship. https://youtube.com/shorts/Vutg_AJ-nig?si=rppl8B1AmMR42ETwhttps://nexoraplay.wordpress.com/2026/05/25/minal-day-of-premier-league-season/
¿A quién pertenecen las imágenes?
https://fed.brid.gy/r/https://elpais.com/opinion/2026-05-25/a-quien-pertenecen-las-imagenes.html
Thanks to all for the suggestions of suitable sites for my RSS reader. This looks like a good start.
Roberta Fidora
Emily King
C. L. Nichols
powRSS
WE AND THE COLOR
NEXORAPLAY ▶️
EL PAÍS: el periódico global [Unofficial]
Tim Richards