<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>content architecture on Publishing House</title>
    <link>https://publishinghouse.org/tags/content-architecture/</link>
    <description>Recent content in content architecture 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/content-architecture/index.xml" rel="self" type="application/rss+xml" />
    <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>
    
  </channel>
</rss>
