Back to Archive

AI moves inside WordPress

Welcome to the first issue of WP.email. The loudest thread this week is AI working its way into WordPress itself: a proposal to expand the core Abilities API in 7.1, agencies wiring their workflows st...


Welcome to the first issue of WP.email. The loudest thread this week is AI working its way into WordPress itself: a proposal to expand the core Abilities API in 7.1, agencies wiring their workflows straight into host APIs, and the first class of formally credentialed "AI leaders" walking the stage.

Around that sit a few pieces worth your time on the harder questions, like what enterprise buyers actually pay for, why accessibility is an operational discipline, and how publishers might get paid when AI does the browsing. Here is the week, sorted for wherever you sit.

Beginner

Vibe coding real WordPress workflows with the Kinsta API

Kinsta makes the case that an agency's edge now comes from automating repetitive work through its API, not from hand-writing more code. A grounded look at where "vibe coding" actually saves time on client sites.

Yoast's June SEO recap: search in the AI era

The monthly roundup digs into Google's shifting stance on AI search, new publisher controls, and staying visible as classic SEO erodes. Worth a skim if any of your sites live or die by search traffic.

The first "AI Leaders" graduate

Around 40 students became the first cohort to earn the AI Leaders micro-credential, a sign of how quickly AI skills are being formalized around the web industry. A short, optimistic read on where the next wave of talent is coming from.

Developer

The Abilities API is set to grow in 7.1

A merge proposal adds three read-only abilities to the permission-checked framework that shipped in 6.9. This is the layer AI agents will use to read and act on WordPress sites, so read it before it lands.

What enterprise WordPress RFPs keep getting wrong

Human Made argues that most enterprise RFPs measure the wrong things, leaving buyers comparing proposals that miss what actually decides a project's success. Useful whether you answer briefs or write them.

How Gutenberg code now flows into core

The way Gutenberg code gets imported into WordPress core changed during the 7.0 cycle, moving from published npm packages to prebuilt asset bundles. If you contribute to core or track trunk, here is the new flow.

The enterprise CMS costs nobody quotes you

A clear breakdown of the costs that never appear on a license quote: implementation, maintenance, and the expensive surprises in between. Good ammunition when a client only wants to talk sticker price.

Business

Stop free users from running up your AI bill

One free user asks a quick question and costs you pennies; the next pastes in a novel and burns $18 of tokens. Freemius walks through capping that exposure before it eats your margins.

WordPress is no longer the whole stack

The WP Minute argues WordPress is becoming the content layer inside a bigger stack of frameworks and deploy tools, rather than the whole site. Sell WordPress work, and it reframes how you position what you deliver.

Non-WordPress

Trying to delete yourself from the internet

Troy Hunt on why erasing yourself from the internet is mostly futile, told with his usual bluntness. A grounding read on what data privacy can and cannot realistically deliver.

Getting paid when AI crawls your site

Cloudflare's new Attribution dashboard shows which AI crawlers hit your site and what that traffic might be worth. It is the first step in turning "AI scraped my content" into "AI pays for it."

Accessibility is a capability, not a feature

Smashing makes the case for treating accessibility as an ongoing operational discipline rather than an end-of-project audit. Especially relevant now that teams ship AI-generated UI faster than they can check it.

PHP 8.5.8 is a security release

A security fix landed for PHP 8.5, and the team wants every 8.5 site on it. WordPress runs on PHP, so this reaches your host eventually, and sooner if you manage your own server.

How GitHub cleared 20,000 secret-scanning alerts

GitHub had more than 20,000 secret-scanning alerts across 15,000 repositories and got to zero in nine months. A concrete playbook if you are staring down a security backlog you cannot triage by hand.