<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jekyll on Flo&#39;s Thoughts</title>
    <link>https://flohei.de/tags/jekyll/</link>
    <description>Recent content in Jekyll on Flo&#39;s Thoughts</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 13 Oct 2015 19:26:26 +0200</lastBuildDate>
    <atom:link href="https://flohei.de/tags/jekyll/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Jekyll Auto-Build With Git Hooks</title>
      <link>https://flohei.de/2015/10/jekyll-auto-build-with-git-hooks/</link>
      <pubDate>Tue, 13 Oct 2015 19:26:26 +0200</pubDate>
      <guid>https://flohei.de/2015/10/jekyll-auto-build-with-git-hooks/</guid>
      <description>&lt;p&gt;&lt;em&gt;tl;dr: Use the full path to your &lt;code&gt;jekyll&lt;/code&gt; executable when running it from a git hook.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;As much as I love Jekyll for it&amp;rsquo;s nerdiness and it&amp;rsquo;s speed, as much can it be annoying at times when you have to &amp;ldquo;compile&amp;rdquo; your website and upload it to your server every time you fix a comma. This situation lends itself to get automated.&lt;/p&gt;&#xA;&lt;p&gt;First things first: I host my website on &lt;a href=&#34;https://uberspace.de&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Uberspace&lt;/a&gt;. I mentioned before that they&amp;rsquo;re just the best, right&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;? Anyway, at Uberspace, they don&amp;rsquo;t have Jekyll pre-installed so you have to install it yourself. And since you can&amp;rsquo;t just install it for the entire machine, you have to install it on a per-user basis:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Combining Matt Gemmell&#39;s Staging Script and Jekyll-Post-Link</title>
      <link>https://flohei.de/2015/02/combining-matt-gemmells-staging-script-and-jekyll-post-link/</link>
      <pubDate>Sun, 08 Feb 2015 15:00:00 +0200</pubDate>
      <guid>https://flohei.de/2015/02/combining-matt-gemmells-staging-script-and-jekyll-post-link/</guid>
      <description>&lt;p&gt;Last week, Matt Gemmell released a pretty handy &lt;a href=&#34;http://mattgemmell.com/staging-drafts-with-jekyll/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;staging script&lt;/a&gt; for Jekyll.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; This temporarily removes all your posts from your site and copies a draft into &lt;code&gt;_posts&lt;/code&gt;. This way, building your Jekyll site with your new draft post is way faster than your regular builds with all your content.&lt;/p&gt;&#xA;&lt;p&gt;Unfortunately, this does not work when you&amp;rsquo;re using the &lt;a href=&#34;https://github.com/liabru/jekyll-post-link&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;jekyll-post-link&lt;/a&gt; in one of your &lt;em&gt;pages&lt;/em&gt;. (Yes, I mean pages, not posts.) The build process for your staged website will fail with an error like this:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Two New Jekyll Scripts</title>
      <link>https://flohei.de/2015/02/two-new-jekyll-scripts/</link>
      <pubDate>Sat, 07 Feb 2015 14:00:00 +0200</pubDate>
      <guid>https://flohei.de/2015/02/two-new-jekyll-scripts/</guid>
      <description>&lt;p&gt;Every now and then I try to make the process of writing posts in Jekyll a bit more pleasant. &lt;a href=&#34;https://flohei.de/2014/08/jekyll-script-to-easily-create-new-posts&#34; &gt;Last time&lt;/a&gt;, I shared a script that was supposed to make the post creation process a bit easier. It turned out, though, that I almost never really use this script because of its complexity. There are just too many switches and configuration options. (Of which some don&amp;rsquo;t even work reliably.)&lt;/p&gt;&#xA;&lt;p&gt;Though this script did not help me as much as I hoped it would, it led me to two new, extremely simple scripts in my toolchain.&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Password Protected Pages With Jekyll</title>
      <link>https://flohei.de/2014/11/password-protected-pages-with-jekyll/</link>
      <pubDate>Wed, 12 Nov 2014 15:04:06 +0200</pubDate>
      <guid>https://flohei.de/2014/11/password-protected-pages-with-jekyll/</guid>
      <description>&lt;p&gt;When I moved to Jekyll &lt;a href=&#34;https://flohei.de/blog/moving-to-jekyll&#34; &gt;I didn’t have a way to password protect pages&lt;/a&gt;. Actually, I didn&amp;rsquo;t really need it so it wasn&amp;rsquo;t a real concern to me and I did not yet look into it. Until today. I was contacted by &lt;a href=&#34;https://timesvr.com&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Osama of TimeSvr&lt;/a&gt; who asked me about this and so I thought it might be a good idea to share what we came up with.&lt;/p&gt;&#xA;&lt;p&gt;Since we only needed to protect pages within a certain context we decided that &lt;code&gt;.htaccess&lt;/code&gt; protection would be sufficient enough.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jekyll: Script To Easily Create New Posts</title>
      <link>https://flohei.de/2014/08/jekyll-script-to-easily-create-new-posts/</link>
      <pubDate>Sat, 16 Aug 2014 19:39:12 +0200</pubDate>
      <guid>https://flohei.de/2014/08/jekyll-script-to-easily-create-new-posts/</guid>
      <description>&lt;p&gt;Jekyll is amazing for me. It gives me full control over all my content in an easy to maintain way while keeping it in a sustainable format.&lt;/p&gt;&#xA;&lt;p&gt;Though creating a new post is as simple as creating a new Markdown file and setting some variables within the &lt;a href=&#34;http://jekyllrb.com/docs/frontmatter/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;front matter&lt;/a&gt;, this usually takes a few moments and most of these steps are the same over and over again.&lt;/p&gt;&#xA;&lt;p&gt;To make life a little bit easier (and to just have something to fiddle around with, to be fair) I wrote a small script that helps jump-start on new posts. It creates the file, sets the title and date and tags and categories if I wish to and opens that new file in my favorite text editor.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Searching Jekyll</title>
      <link>https://flohei.de/2014/07/searching-jekyll/</link>
      <pubDate>Sat, 26 Jul 2014 23:39:57 +0200</pubDate>
      <guid>https://flohei.de/2014/07/searching-jekyll/</guid>
      <description>&lt;p&gt;Using a static site generator like Jekyll for your personal blog brings a few new challenges in some areas. Searching, for example is not possible in pure HTML. There are a few different options to find posts on your website, though.&lt;/p&gt;&#xA;&lt;h2 id=&#34;tldr&#34;&gt;&#xA;  tl;dr&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#tldr&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;&lt;code&gt;jekyll-lunr-js-search&lt;/code&gt; is great, just head over to &lt;a href=&#34;https://github.com/slashdotdash/jekyll-lunr-js-search&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;GitHub&lt;/a&gt; and get started.&lt;/p&gt;&#xA;&lt;h2 id=&#34;external-search-engine&#34;&gt;&#xA;  External Search Engine&#xA;  &lt;a class=&#34;heading-link&#34; href=&#34;#external-search-engine&#34;&gt;&#xA;    &lt;i class=&#34;fa-solid fa-link&#34; aria-hidden=&#34;true&#34; title=&#34;Link to heading&#34;&gt;&lt;/i&gt;&#xA;    &lt;span class=&#34;sr-only&#34;&gt;Link to heading&lt;/span&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Both &lt;a href=&#34;https://www.google.com/cse/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Google&lt;/a&gt; and &lt;a href=&#34;https://github.com/seanredmond/jekyll-ddg-search&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;DuckDuckGo&lt;/a&gt; offer search engines for your own website which are more or less easy to integrate in your own site. Unfortunately, DDG did not seem to index my site {% post_link 2014-07-02-moving-to-jekyll since I installed Jekyll %} and this plugin a few weeks ago.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Re-Routing RSS Feed</title>
      <link>https://flohei.de/2014/07/re-routing-rss-feed/</link>
      <pubDate>Sun, 06 Jul 2014 15:08:30 +0200</pubDate>
      <guid>https://flohei.de/2014/07/re-routing-rss-feed/</guid>
      <description>&lt;p&gt;Quick follow-up on &lt;a href=&#34;https://flohei.de/2014/07/moving-to-jekyll&#34; &gt;the Feed Forwarding section from that other post on Jekyll&lt;/a&gt;: Turns out, the forwarding in the header of that HTML file did not work as expected. Opening the URL in the browser passed you through to your favorite RSS reader if you have one installed. Feed readers that had already subscribed to the original feed before did not get any updates, though.&lt;/p&gt;&#xA;&lt;p&gt;So I changed that re-routing to be handled in my &lt;code&gt;.htaccess&lt;/code&gt; file.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Moving to Jekyll</title>
      <link>https://flohei.de/2014/07/moving-to-jekyll/</link>
      <pubDate>Wed, 02 Jul 2014 21:48:05 +0200</pubDate>
      <guid>https://flohei.de/2014/07/moving-to-jekyll/</guid>
      <description>&lt;p&gt;Listening to Brett Terpstra&amp;rsquo;s podcast &lt;a href=&#34;https://esn.fm/systematic&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Systematic&lt;/a&gt;, I found out about the static website generator Jekyll. After hearing and reading about it for a while I startet wanting to try it for my own website.&lt;/p&gt;&#xA;&lt;p&gt;There are some great tutorials out there that describe the basic setup of a new Jekyll website, like &lt;a href=&#34;http://pixelcog.com/blog/2013/jekyll-from-scratch-core-architecture/&#34;  class=&#34;external-link&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;Jekyll From Scratch&lt;/a&gt; by Mike Greiling, so I don&amp;rsquo;t want to talk about that. What I want to talk about, though, are the bits and pieces that these tutorials were missing for my very own situation. There might be some more people with a similar setup. There were three major questions I still had after reading the different tutorials:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
