<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Static-Site on Thomas - A blog about information security and IT</title><link>https://thomasbrinkman.nl/tags/static-site/</link><description>Recent content in Static-Site on Thomas - A blog about information security and IT</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 28 Nov 2021 11:00:10 +0100</lastBuildDate><atom:link href="https://thomasbrinkman.nl/tags/static-site/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I chose a static site generator to serve content for this blog</title><link>https://thomasbrinkman.nl/posts/my-first_post/</link><pubDate>Sun, 28 Nov 2021 11:00:10 +0100</pubDate><guid>https://thomasbrinkman.nl/posts/my-first_post/</guid><description>&lt;p&gt;For my first post it feels fitting to explain a decision I made before writing a
single word of content: serving this blog from a static site generator instead
of a Content Management System (CMS) such as the well-known WordPress, which
powers roughly 65% of all sites that use a CMS
&lt;a href="https://w3techs.com/technologies/overview/content_management"&gt;at the time of writing&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;A CMS like WordPress is powerful, but for a personal blog it brings along a
database, a server-side runtime and a plugin ecosystem that I simply don&amp;rsquo;t need.
A static site generator takes my content, renders every page ahead of time, and
hands me a folder of plain HTML, CSS and JavaScript that can be served from
anywhere.&lt;/p&gt;</description></item></channel></rss>