<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>publishing infrastructure on Publishing House</title>
    <link>https://publishinghouse.org/tags/publishing-infrastructure/</link>
    <description>Recent content in publishing infrastructure 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/publishing-infrastructure/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>
    
    <item>
      <title>The Indie Publisher&#39;s Case for Owning Your Infrastructure</title>
      <link>https://publishinghouse.org/the-indie-publishers-case-for-owning-your-infrastructure/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/the-indie-publishers-case-for-owning-your-infrastructure/</guid>
      <description>Every few years, a platform that indie publishers relied on changes the rules. Algorithm changes cut organic reach. Monetization programs introduce new requirements or reduce payouts. Accounts get suspended without clear appeal paths. The terms shift in ways that favor the platform over the publisher.
This is not a new dynamic. It predates the internet. But the specific form it takes now — where a significant portion of an independent publisher&amp;rsquo;s audience, revenue, and distribution lives on infrastructure controlled by companies whose interests regularly diverge from the publishers they host — is worth examining directly.</description>
    </item>
    
    <item>
      <title>WordPress Multisite for Network Publishers</title>
      <link>https://publishinghouse.org/wordpress-multisite-for-network-publishers/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/wordpress-multisite-for-network-publishers/</guid>
      <description>WordPress Multisite is a feature built into WordPress core that enables a single WordPress installation to power a network of independent sites. Each site in the network has its own content, users, and settings, while sharing a single codebase, plugin installation, and server infrastructure. For publishers operating multiple properties, it is worth understanding clearly — including where it helps and where it creates problems.
What WordPress Multisite Is Activating Multisite converts a standard WordPress installation into a network.</description>
    </item>
    
    <item>
      <title>WordPress Security Hardening: A Publisher&#39;s Checklist</title>
      <link>https://publishinghouse.org/wordpress-security-hardening-a-publishers-checklist/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/wordpress-security-hardening-a-publishers-checklist/</guid>
      <description>WordPress is the most attacked CMS on the internet not because it is inherently insecure but because it is the most common. Its market share makes it the highest-return target for automated scanning and exploitation. A default WordPress installation is not a hardened one — but hardening it is straightforward, well-documented work that most publishers skip until something goes wrong.
This checklist covers the high-impact measures that materially reduce your attack surface.</description>
    </item>
    
  </channel>
</rss>
