<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>block editor on Publishing House</title>
    <link>https://publishinghouse.org/tags/block-editor/</link>
    <description>Recent content in block editor on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/block-editor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The WordPress Block Editor: A Publisher&#39;s Deep Dive</title>
      <link>https://publishinghouse.org/the-wordpress-block-editor-a-publishers-deep-dive/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/the-wordpress-block-editor-a-publishers-deep-dive/</guid>
      <description>The WordPress block editor — introduced in 2018 as the Gutenberg project and now simply the default editing experience — has matured into a genuinely capable publishing tool. It was controversial at launch and the criticism was fair: it was slow, unstable, and a poor replacement for the Classic Editor many publishers had built workflows around. Several years and dozens of releases later, it is a different product.
For publishers either still avoiding it or using it without fully understanding its capabilities, this is a practical walkthrough of what it can actually do.</description>
    </item>
    
  </channel>
</rss>
