Release notes,
guides, and journal.
I ship in public. Every release shows up here with its audit trail, every comparison with receipts, every essay with the specific thing I learned. No revolutionary, no supercharged — just the breath WordPress has been holding.
MCP 2026-07-28 is final. What changes for WordPress and Respira?
The stable specification removes protocol sessions, adds server discovery, hardens authorization, and formalizes extensions. Respira 8.1 implements it with a tested legacy path, while Webflow MCP 2.0 shows why production governance matters.
Get the release notes & guides in your inbox.
Ships when I ship. No drip sequences, no digests, no "5 things" lists.
No matches for ""
Try a builder name (Elementor, Divi, Bricks), a release version (6.0.0), or a concept (snapshots, MCP, CLI).
You're not the only one talking to WordPress.
The Respira community is where agency owners debug Divi migrations at 11pm, where vibe coders swap prompts that actually ship, and where the roadmap gets written out loud. Breathe with us.
From the workshop
A backup you have never restored is a hope, not a plan. Every recovery guide ends with "restore from a clean backup". This week, test it: restore your WordPress site to a staging copy, or ask your host to walk you through it, and time it…
Changing a WordPress page address takes thirty seconds. Cleaning up after it can take months, if you notice at all. The old address stays alive in Google, in emails people saved, in links from other sites. Someone clicks, lands on an err…
The AI editing your WordPress site can no longer approve its own work. If it tries to change its own permissions or sign off on its own draft, Respira for WordPress stops it and asks you instead. Nothing in your day-to-day changes. It ju…
Most AI assistants that touch WordPress sites this week are using tools people already have: Claude Code, Codex, Claude Desktop. 3,461 WordPress sites are connected to Respira for WordPress. 184 joined this week. Together they account fo…
An update closes the door. It does not check who came in. For the most targeted WordPress flaws, attacks start within hours of the fix being public, according to Patchstack. After any serious update, look at two things an update never re…
A NIST study found that people faced with too many security decisions start skipping them. So make fewer. One ten-minute check a week for your WordPress site, same order every time: 1. Dashboard, Updates 2. Tools, Site Health 3. Users, f…