<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>publishing platforms on Publishing House</title>
    <link>https://publishinghouse.org/tags/publishing-platforms/</link>
    <description>Recent content in publishing platforms 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-platforms/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Contentful for Publishing Teams: A Practical Overview</title>
      <link>https://publishinghouse.org/contentful-for-publishing-teams-a-practical-overview/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/contentful-for-publishing-teams-a-practical-overview/</guid>
      <description>Contentful is one of the oldest and most established headless CMS platforms. Launched in 2013, it pioneered the API-first CMS model that the broader industry has since adopted. It is a mature, well-documented platform with a large ecosystem of integrations, a capable editorial interface, and a content delivery infrastructure built for scale.
For publishing teams evaluating headless CMS options, Contentful warrants serious consideration — with a clear-eyed understanding of where it excels and where its costs and complexity create friction.</description>
    </item>
    
    <item>
      <title>Getting Started with Drupal for Publishing Organizations</title>
      <link>https://publishinghouse.org/getting-started-with-drupal-for-publishing-organizations/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/getting-started-with-drupal-for-publishing-organizations/</guid>
      <description>Drupal occupies a specific and durable niche in the publishing world. It is not the easiest CMS to get started with, and it is not trying to be. What it offers is a structured, extensible content management framework that scales to genuinely complex editorial operations — the kind where content types, taxonomies, workflows, and access control matter as much as the editing interface.
Major news organizations, government publishers, universities, and enterprise media companies run on Drupal.</description>
    </item>
    
    <item>
      <title>Getting Started with Eleventy for Publishers</title>
      <link>https://publishinghouse.org/getting-started-with-eleventy-for-publishers/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/getting-started-with-eleventy-for-publishers/</guid>
      <description>Eleventy (11ty) is a JavaScript-based static site generator that has grown into one of the most flexible options in its category. Where Hugo makes strong structural decisions and asks you to work within them, Eleventy makes almost none — it is a set of tools for turning content into HTML, with minimal opinions about how your project should be organized.
That flexibility is genuinely powerful and genuinely requires more upfront decision-making.</description>
    </item>
    
    <item>
      <title>JAMstack for Publishers: What It Means and Why It Matters</title>
      <link>https://publishinghouse.org/jamstack-for-publishers-what-it-means-and-why-it-matters/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/jamstack-for-publishers-what-it-means-and-why-it-matters/</guid>
      <description>JAMstack is an architectural approach to building websites that has reshaped how publishers think about performance, security, and hosting. The term has become somewhat elastic with use — vendors apply it broadly — but the underlying principles are specific and worth understanding clearly.
What JAMstack Actually Means JAM stands for JavaScript, APIs, and Markup. The original definition describes a web architecture with three characteristics:
JavaScript handles all dynamic functionality, running in the browser rather than on the server.</description>
    </item>
    
    <item>
      <title>Sanity CMS for Publishers: Structured Content Done Right</title>
      <link>https://publishinghouse.org/sanity-cms-for-publishers-structured-content-done-right/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/sanity-cms-for-publishers-structured-content-done-right/</guid>
      <description>Sanity is a headless CMS built around a principle it calls &amp;ldquo;structured content&amp;rdquo; — the idea that content should be modeled as data first, with presentation a separate concern. For publishers whose content is genuinely complex — articles with rich metadata, multiple content types with relationships, content repurposed across channels — Sanity&amp;rsquo;s approach delivers a level of flexibility that database-backed traditional CMSes struggle to match.
It is not the simplest tool in the category, but for the use cases it is designed for, it is among the most capable.</description>
    </item>
    
    <item>
      <title>The Best Static Site Generators for Publishers in 2026</title>
      <link>https://publishinghouse.org/the-best-static-site-generators-for-publishers-in-2026/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/the-best-static-site-generators-for-publishers-in-2026/</guid>
      <description>The static site generator landscape has matured considerably. What was once a niche developer preference — choosing a build tool over a CMS — is now a mainstream option for publishers of all sizes. Performance, security, and hosting cost advantages have made static generation attractive well beyond the developer blog use case.
The challenge now is not whether to consider a static site generator, but which one. The options differ in speed, flexibility, content modeling, and the technical profile they assume.</description>
    </item>
    
    <item>
      <title>What Is a Headless CMS? A Publisher&#39;s Guide</title>
      <link>https://publishinghouse.org/what-is-a-headless-cms-a-publishers-guide/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/what-is-a-headless-cms-a-publishers-guide/</guid>
      <description>The term &amp;ldquo;headless CMS&amp;rdquo; gets used loosely enough that it has started to lose meaning in some conversations. Publishers evaluating content infrastructure deserve a clear definition, a realistic picture of the tradeoffs, and an honest sense of when the architecture is actually the right fit.
What &amp;ldquo;Headless&amp;rdquo; Means A traditional CMS — WordPress, Drupal, Joomla — couples content management with content presentation. The system stores your posts in a database, applies templates to them, and renders HTML pages.</description>
    </item>
    
    <item>
      <title>WordPress vs Hugo: Choosing the Right Platform for Your Publishing Site</title>
      <link>https://publishinghouse.org/wordpress-vs-hugo-choosing-the-right-platform-for-your-publishing-site/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/wordpress-vs-hugo-choosing-the-right-platform-for-your-publishing-site/</guid>
      <description>For publishers setting up a new site — or reconsidering an old one — the choice between WordPress and Hugo comes up constantly. Both are capable, widely used, and well-supported, but they represent fundamentally different philosophies about how a website should work. Picking the wrong one creates friction you will feel every day.
The Core Difference WordPress is a dynamic content management system. Every time a visitor loads a page, WordPress queries a database, assembles the page from PHP templates and stored content, and serves the result.</description>
    </item>
    
  </channel>
</rss>
