An off-the-shelf AI plugin left a client with a slow backend and alt text that had nothing to do with the images. The core AI discussions point somewhere better: content summaries, post titles and image descriptions behind one PHP AI Client.
A client wanted AI features on his WordPress site and every plugin used a different API. The new WordPress AI Client SDK gives plugins and themes one consistent, WP-native API for multiple providers.
A client spent six months stuck on API plumbing before any AI features shipped. The lesson: build WordPress AI on a proper AI Client SDK, with a standard way to register providers, before chasing features.
Custom capabilities get messy fast on big WordPress sites. The Abilities API, in development for 6.9 as part of Core-AI, gives a structured way to define and manage them.
A client’s AI prototype broke because their site ran PHP 7.2 while our code used PHP 7.4. Here is how the WordPress Core AI team handles the same version gap, and how to build for it.
A client inherited an AI setup that was really just API calls held together with duct tape, and it kept breaking. Here is the architecture I use instead: provider interfaces and DTOs that let you swap AI models without rewriting everything.
A real question from WordPress Core AI work: should a shared AI adapter ship as a canonical plugin or a Composer library, and why that architecture choice shapes maintenance later.
WordPress.org has started running the Plugin Check tool on every plugin update, new and existing. A look at what the automated scans catch and how to run the same checks before you upload.
Tying a WordPress site to one AI provider’s SDK makes switching painful later. This walks through an abstraction layer with per-provider adapters so you can change models without rewriting your core code.
A hardcoded AI API key in front-end JavaScript is a security hole and a performance drag. This shows how to move the calls to a WordPress server-side proxy using the REST API and wp_remote_post.