<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Posts on Edd Armitage - Software Engineer</title><link>https://eddarmitage.com/posts/index.html</link><description>Recent content in Posts on Edd Armitage - Software Engineer</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Sat, 17 Jun 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://eddarmitage.com/posts/feed.xml" rel="self" type="application/rss+xml"/><item><title>Hosting a static site</title><link>https://eddarmitage.com/2023/06/hosting-a-static-site.html</link><pubDate>Sat, 17 Jun 2023 00:00:00 +0000</pubDate><guid>https://eddarmitage.com/2023/06/hosting-a-static-site.html</guid><description>&lt;p&gt;I&amp;rsquo;ve wanted to host a simple little website for many years now, but never had the inclination to invest too much (be
it in terms of time, money or thought) into it - the obvious solution was to serve some kind of pre-baked static site,
removing the need for any real kind of infrastructure maintenance, leaving me to worry about &amp;ldquo;content&amp;rdquo; (whatever that
means).&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve gone through various systems in the past - trials and experimentation with most workflows including fully-hosted
Wordpress; locally run static-site generators with the output synced to a traditional webhost; and even writing my own
static site generator that was little more than glue around common libraries for parsing markdown.&lt;/p&gt;</description></item></channel></rss>