<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Kirby on Flo&#39;s Thoughts</title>
    <link>https://flohei.de/tags/kirby/</link>
    <description>Recent content in Kirby on Flo&#39;s Thoughts</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 16 Feb 2016 19:14:37 +0200</lastBuildDate>
    <atom:link href="https://flohei.de/tags/kirby/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hey Kirby!</title>
      <link>https://flohei.de/2016/02/hey-kirby/</link>
      <pubDate>Tue, 16 Feb 2016 19:14:37 +0200</pubDate>
      <guid>https://flohei.de/2016/02/hey-kirby/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://flohei.de/media/getkirby.com.png&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;For the last couple of years I have been &lt;a href=&#34;https://flohei.de/blog/moving-to-jekyll&#34; &gt;using Jekyll&lt;/a&gt; for this website and I really enjoyed it. It&amp;rsquo;s nerdy nature spoke to my inner, well, nerd. Unfortunately, this nerdism isn&amp;rsquo;t always practical. Jekyll requires you to rebuild your website and sync the resulting website files to your host. I know there are solutions to this but they all seemed kinda hacky to me. This was fun for a while but I felt like it got more and more in the way when just wanting to quickly share something. Hey, who would&amp;rsquo;ve thought a backend can make total sense when you want to manage contents?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
