<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>8pod</title>
    <atom:link href="/feed.xml" rel="self" type="application/rss+xml"/>
    <link>https://8pod.github.io/</link>
    <description>A website with blog posts and pages</description>
    <pubDate>Fri, 21 Dec 2018 04:09:11 +0000</pubDate>
    
      <item>
        <title>The Obligatory &quot;Hello World&quot; Post</title>
        <link>/2015/03/13/hello-world.html</link>
        <guid isPermaLink="true">/2015/03/13/hello-world.html</guid>
        <description>&lt;p&gt;Well, it is Friday the 13th, and while I would not consider myself an overly superstitious person, I have been known to avoid sticking my chopsticks into my rice bowl, scrambling to avoid stepping on the entrance threshold of any particular jinja I may be visiting, and partaking in various other Asian superstitions (I live in Japan.) I am going to throw caution to the wind, and published my new blog today regardless.&lt;/p&gt;

&lt;p&gt;I have spent a couple of days now building out this site in &lt;a href=&quot;http://jekyllrb.com/&quot;&gt;Jekyll&lt;/a&gt;, which is touted as a true “hackers” endeavor. Two months ago, and some change, I had created a repository in my &lt;a href=&quot;https://github.com/8pod&quot;&gt;GitHub&lt;/a&gt; account to take advantage of &lt;a href=&quot;https://pages.github.com/&quot;&gt;GitHub Pages&lt;/a&gt;, a free offering from the fine folks @ GitHub. Initially I had planned on using &lt;a href=&quot;http://octopress.org/&quot;&gt;Octopress&lt;/a&gt;, but given its lack of apparent ongoing development, and my lack of experience with the underlying technology that Octopress extends, Jekyll, I opted to go with the later.&lt;/p&gt;

&lt;p&gt;Jekyll is fairly painless to get running. I wanted to validate my &lt;a href=&quot;https://github.com/Shopify/liquid/wiki&quot;&gt;Liquid&lt;/a&gt; and &lt;a href=&quot;http://daringfireball.net/projects/markdown/&quot;&gt;Markdown&lt;/a&gt; syntax and &lt;a href=&quot;http://sass-lang.com/&quot;&gt;Sass&lt;/a&gt; preprocessing directives before submitting it to GitHub. This means I had to test it locally, and given Jekyll’s Ruby origin, I had to install &lt;a href=&quot;http://rubyinstaller.org/downloads/&quot;&gt;Ruby and DevKit&lt;/a&gt; on my Windows machine to perform that step - which took the longest time. This &lt;a href=&quot;http://jekyll-windows.juthilo.com/&quot;&gt;Jekyll page&lt;/a&gt; made that easy, but I spent too much time swapping out Ruby versions and troubleshooting things like this and this.&lt;/p&gt;

&lt;p&gt;I decided to start things out with a &lt;a href=&quot;http://jekyllthemes.org/&quot;&gt;theme&lt;/a&gt; rather then starting from starch, and I thought the &lt;a href=&quot;https://github.com/rohanchandra/type-theme&quot;&gt;Type Theme&lt;/a&gt; was nice. The developer of this theme had implemented Sass, and included a nice setup in &lt;a href=&quot;http://jekyllrb.com/docs/frontmatter/&quot;&gt;YAML front matter&lt;/a&gt; to allow references to various social media channels, and went to the effort of including a &lt;a href=&quot;https://disqus.com/&quot;&gt;DISQUS&lt;/a&gt; reference. Nice.&lt;/p&gt;
</description>
        <pubDate>Fri, 13 Mar 2015 00:00:00 +0000</pubDate>
      </item>
    
  </channel>
</rss>
