<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Contentful on CSP Guide</title>
    <link>https://csp-guide.com/tags/contentful/</link>
    <description>Recent content in Contentful on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 01 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/contentful/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Contentful and Headless CMS: A Real-World Fix</title>
      <link>https://csp-guide.com/posts/csp-for-contentful-and-headless-cms-setups/</link>
      <pubDate>Sat, 01 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-contentful-and-headless-cms-setups/</guid>
      
      <description>&lt;p&gt;Headless CMS setups make CSP harder in a very specific way: your page looks static, but the browser is talking to half a dozen origins you forgot about.&lt;/p&gt;
&lt;p&gt;I’ve seen this pattern a lot with Contentful, Next.js, and marketing teams that add analytics, consent banners, preview mode, embedded videos, and rich text assets over time. The app starts simple. Then one day you flip on a strict CSP and half the site breaks.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
