<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>headless-cms on Regis Philibert</title><link>https://www.regisphilibert.com/tags/headless-cms/</link><description>Recent content in headless-cms on Regis Philibert</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 20 Dec 2021 08:32:27 +0000</lastBuildDate><atom:link href="https://www.regisphilibert.com/tags/headless-cms/index.xml" rel="self" type="application/rss+xml"/><item><title>Toward using a Headless CMS with Hugo: Building Pages from an API</title><link>https://www.regisphilibert.com/blog/2021/12/toward-using-a-headless-cms-with-hugo-part-2-building-from-remote-api/</link><pubDate>Mon, 20 Dec 2021 08:32:27 +0000</pubDate><guid>https://www.regisphilibert.com/blog/2021/12/toward-using-a-headless-cms-with-hugo-part-2-building-from-remote-api/</guid><description>We&amp;rsquo;ll use a straignt forward workaround. It consists of using Hugo to grab our data from a remote source using resources.GetRemote &amp;mdash; Hugo&amp;rsquo;s own fetch API &amp;mdash;, keep using Hugo to generate markdown files using its resources.FromString, and finally build our Hugo project with the aforementioned content files.
Building pages from a remote source With Hugo&amp;rsquo;s famous limitation, the only way to efficiently build pages from data (local or remote) while preserving the powerful Page API of Hugo has been to split your build into two steps.</description></item></channel></rss>