<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>enterprise publishing on Publishing House</title>
    <link>https://publishinghouse.org/tags/enterprise-publishing/</link>
    <description>Recent content in enterprise publishing 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/enterprise-publishing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Drupal vs WordPress for Large Publishing Operations</title>
      <link>https://publishinghouse.org/drupal-vs-wordpress-for-large-publishing-operations/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/drupal-vs-wordpress-for-large-publishing-operations/</guid>
      <description>Both Drupal and WordPress power large publishing operations. The New York Post, The Economist, and Condé Nast have used WordPress at enterprise scale. The Economist, Reuters, and major government and academic publishers have built on Drupal. Saying one is categorically superior gets the question wrong — they represent different engineering philosophies that create different strengths and different friction points.
For a publishing organization evaluating both seriously, the decision turns on a handful of specific characteristics.</description>
    </item>
    
  </channel>
</rss>
