<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rss on ads' corner</title><link>https://andreas.scherbaum.la/tags/rss/</link><description>Recent content in Rss on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 14 Mar 2020 16:44:00 +0100</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/rss/index.xml" rel="self" type="application/rss+xml"/><item><title>Public previews in Hugo</title><link>https://andreas.scherbaum.la/post/2020-03-14_public-previews-in-hugo/</link><pubDate>Sat, 14 Mar 2020 16:44:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-03-14_public-previews-in-hugo/</guid><description>&lt;p&gt;&lt;a href="https://gohugo.io/"&gt;Hugo&lt;/a&gt; is a static templating system. It is (mainly) used to deploy websites/blogs which don&amp;rsquo;t have and need dynamic content. The content of all pages is pre-generated, and the webserver delivers files from disk (or rather from cache, once files are loaded into memory). This approach allows for extremely fast websites, as no dynamic content is generated on every request.&lt;/p&gt;&#10;&lt;p&gt;While I know &lt;em&gt;Hugo&lt;/em&gt; &lt;a href="https://engineering.pivotal.io/"&gt;from work&lt;/a&gt;, I haven&amp;rsquo;t really used it for private projects - until recently. I have started a new project where I present &lt;a href="https://postgresql.life/"&gt;interviews with people&lt;/a&gt; behind the &lt;a href="https://www.postgresql.org/"&gt;PostgreSQL Project&lt;/a&gt; - and this is perfect for a static website. Interviews don&amp;rsquo;t change, once published.&lt;/p&gt;</description></item></channel></rss>