Write is the minimal editor WordPress.com just announced, and the easy take is that the block editor finally got too heavy and the Classic Editor crowd won. The announcement leans that way too: in last year’s Creators survey, “simplify the editor” was the single most-requested improvement from people already publishing there, and the tool grew out of a plugin by Jamie Marsland. If you build sites for a living, the more useful fact is that the WordPress Write editor saves ordinary block markup to ordinary posts. The content doesn’t change, so what I care about is what a curated surface does to the process around it.
The WordPress Write editor still writes blocks
A post drafted in Write is a post in wp_posts, rendered by your theme like any other, and you can reopen it in the block editor whenever you want. The announcement is short but explicit on this:
Your Write posts are real WordPress posts. They live alongside your other posts, work with your theme, and you can open them in the block editor.
Compare that with the Classic Editor plugin, which restores the old experience for real: one HTML blob in post_content, meta boxes around it, and no block boundaries to hold onto. Classic markup versus block markup becomes an actual cost the day a client asks you to restyle five years of old posts or drop a reusable pattern into them. Write doesn’t reopen that split. The content model stays one thing, which is the main reason I don’t read it as a classic comeback.
What changes is the process, and the process has visible gaps. Tags work by typing a line that contains nothing but hashtags, separated by spaces; commas break the parsing. That detail came out in the comments on the announcement, along with the fact that images upload from your computer and there’s no route to the site’s media library from inside Write yet. Fine for a personal blog. If your client’s writers already know a 4,000-image library by heart, that’s the first thing to check before you recommend anything.
Write versus distraction free mode
The block editor has had distraction free mode for a while now. It hides the top toolbar, the block toolbar and the settings sidebar. It’s a per-user preference, it ships in core, and it costs nothing, so every self-hosted client already has it. Underneath, nothing changes: the same inserter, media library, meta boxes and custom blocks. It’s a view on the same editor.
Write is a different editor. It’s a separate surface with its own entry point at wordpress.com/write-editor or yoursite.com/wp-admin/admin.php?page=write, a short toolbar, and a curated block list. A lot of the usual editor is hidden on purpose. You get a page with almost nothing on it, and for drafting prose that feels better than a settings sidebar breathing on your neck. You lose the editor plugin ecosystem, because Yoast, ACF field groups, WooCommerce product panels and whatever custom block library you built all hook into the block editor’s slots. None of that exists inside Write.
There’s also no path from the New Post button into Write yet; the team said making it easier to find is on the list, and their support article confirms the URL is the way in. A writer has to know a magic link. It’s a beta detail, but it suggests Write isn’t meant to be anyone’s only editor today.
For drafting, either one gets you to a quiet page. The difference shows up the moment you need something outside the curated set.
What I’d do on a self-hosted site
Self-hosted sites don’t get Write at all, and there’s no announced timeline for that. If a client’s complaint is that their writers get lost in the block editor, the closest thing you can ship is distraction free mode plus a trimmed inserter. The allowlist is one filter:
add_filter( 'allowed_block_types_all', 'bbioon_writer_block_allowlist', 10, 2 );
function bbioon_writer_block_allowlist( $allowed, $context ) {
if ( empty( $context->post ) ) {
return $allowed; // Site Editor: don't touch.
}
// Writers get a short list; editors keep everything.
if ( ! current_user_can( 'edit_others_pages' ) ) {
return array(
'core/paragraph',
'core/heading',
'core/image',
'core/quote',
'core/list',
'core/spacer',
);
}
return $allowed;
}Don’t skip the check on $context->post. The same filter runs inside the Site Editor, and you can break pattern editing with it. I wrote about limiting blocks without wrecking the Site Editor after hitting exactly that. Because the cap is on capabilities rather than roles, writers get six blocks and editors keep the full set. That gets you most of what Write is selling without waiting on a WordPress.com-only beta, and every plugin hook stays alive.
If you want a calm editor for your writers without losing the panels your workflow depends on, that’s the kind of work I take on. Tell me which plugins your writers rely on and I’ll tell you what survives a trimmed inserter.
Which editor for which site
A WordPress.com writing blog, mostly text, one or two authors: use Write for drafting and the block editor for the final pass. It’s available on free and paid plans, so there’s no purchasing decision to make, and posts round-trip between the two surfaces.
A content site with custom patterns, ACF field groups or a real SEO workflow: block editor, with distraction free mode on for drafting. Write would hide the exact tools the workflow runs on, and a hashtag line is not a replacement for a tags panel for anyone who cares about taxonomy.
Classic Editor holdouts: in my experience their complaint is the chrome, not the data model. Write answers the chrome complaint and keeps one content model, so I’d sooner point them at it than install the Classic Editor plugin on a new build. On self-hosted, the trimmed inserter plus distraction free mode is the honest equivalent.
WooCommerce stores: keep writers in the block editor. Product copy sits next to pricing, inventory and shipping panels, and Write is a posts surface; I haven’t seen it handle product post types and the docs don’t claim it does. WordPress has been shipping simplified surfaces over the full editor for a while now, and I had similar mixed feelings about the Easy Site Editor. Both make one job convenient and hide their limits everywhere else. The block editor handbook is still the layer all of these sit on top of.
This week I’m not switching any client. I’ll turn distraction free mode on for the two people who write long posts on the current build, cap their inserter at a short list, and watch Write for when it leaves beta. If the media library and a real tags field land, it becomes worth a client conversation instead of a curiosity.
