<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Netlify on scarbrough.co.uk</title>
    <link>/tags/netlify/</link>
    <description>Recent content in Netlify on scarbrough.co.uk</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 20 Sep 2022 00:00:00 +0000</lastBuildDate>
    <atom:link href="/tags/netlify/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Netlify CMS and Continuous Deployment for Hugo</title>
      <link>/post/development/netlify-cms-hugo/</link>
      <pubDate>Tue, 20 Sep 2022 00:00:00 +0000</pubDate>
      <guid>/post/development/netlify-cms-hugo/</guid>
      <description>Netlify CMS and Continuous Deployment for Hugo Having experimented with this, I think Netlify&amp;rsquo;s idea of tacking a CMS onto a static site generator is tailored for situations where multiple developers, through Continuous Deployment, are providing a corporate site for which the content is being edited by non-technical users. At least it appears that way, because it takes a lot of work to develop the site and configure the CMS for anything more generic than the template provided, and an individual developer working on this as a personal project would most likely dispense with the CMS entirely and modify the files in the /content directory themselves (I&amp;rsquo;ll explain why).</description>
    </item>
  </channel>
</rss>
