Most of the ten new WordPress.com features from Radical Speed Month only matter if the site is hosted on WordPress.com. Two of them, Desktop Mode and the Blueprints Gallery in WordPress Studio, work wherever WordPress runs, and those are the two I’d spend time on.
The list comes from the WordPress.com blog, which rounds up Workspace, WordCamp Agent, Blueprints Gallery, Milestones, Easy Site Editor, Lately, a short-form social theme, Social Feeds, Write, and Desktop Mode, plus Wapuu Studio and Clips as bonuses. The post also carries a note worth taking literally: many of these are still in beta and actively evolving.
Which WordPress.com new features run on other hosts?
Desktop Mode is the easy one. It’s a free, open source plugin on wordpress.org that turns wp-admin into a windowed, desktop-style workspace where posts, media, and settings open as separate windows. Install it on a self-hosted site or a WooCommerce store and it behaves like any other plugin, so you can try it on staging this week without moving anything.
The Blueprints Gallery lives in WordPress Studio, Automattic’s free local development app. Studio runs sites on your machine regardless of where production lives, so a self-hosted client gets the same benefit. The gallery gives you preconfigured blueprints to launch from instead of rebuilding the same setup for every project.
The rest is WordPress.com product. Workspace is a Mac desktop app for WordPress.com Agent, Social Feeds sits in the Reader, and Milestones is an account-level dashboard. Write and Lately are the new posting surfaces, and I’ve already gone over what the Write editor means for client sites. If a self-hosted client asks for that new WordPress thing they read about, the honest answer is that it isn’t on their host, and rebuilding a beta feature as a plugin is a losing bet.
What a blueprint looks like
A blueprint is JSON, the same format WordPress Playground uses. It’s readable and diffable, and it sits in the repo like any other config. You pin PHP and WordPress versions, install plugins and themes, set options, and can run WP-CLI steps on first boot. A short one for a WooCommerce sandbox looks like this:
{
"$schema": "https://playground.wordpress.net/blueprint-schema.json",
"preferredVersions": { "php": "8.3", "wp": "latest" },
"steps": [
{
"step": "installPlugin",
"pluginData": { "resource": "wordpress.org/plugins", "slug": "woocommerce" }
},
{
"step": "installTheme",
"themeData": { "resource": "wordpress.org/themes", "slug": "twentytwentyfive" }
},
{
"step": "setSiteOptions",
"options": { "blogname": "Client sandbox" }
}
]
}The file matters more than the gallery. Once the blueprint is in version control, every environment comes up with the same PHP version, plugin set, and options. That removes most of the works-on-my-machine debugging, and it’s a better onboarding doc for a new contractor than a README paragraph. I use a similar Playground and GitHub workflow for theme work, and the gallery mostly deletes the glue code around it.
Should any of this change how you build?
Mostly no, but two signals are worth tracking. One is ownership: the short-form theme and Social Feeds together push casual posting back onto a site the creator controls instead of a rented feed, and that argument is useful in client content strategy conversations today. The other is the agent pattern. WordCamp Agent runs on WordPress Guidelines, which stores instructions, memories, and skills inside WordPress itself, and if you build anything agent-shaped for clients, structured site context is the part I’d copy. (I’m not sure how far that pattern stretches for multisite, but single-site clients are the obvious fit.)
The beta label is the caveat. One user in the comments under the announcement hit errors generating a Clip, and staff replied that it’s still rolling out. That’s normal for an experiment, but it’s a bad foundation for a client dependency. I’d treat everything on the list as demo material until it survives a quarter.
If you want a repo-ready blueprint for your current plugin stack, or a Studio setup your whole team can spin up on day one, that’s the kind of work I do, so get in touch.
Download Studio, hit Add a site, pick the blueprint closest to your usual stack, and see how much of your setup checklist it deletes. Then save your own blueprint.json while the details are fresh.
