<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Jeremy</title>
    <description>The latest articles on Forem by Jeremy (@jerr).</description>
    <link>https://forem.com/jerr</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F5175%2Fc6f4b95e-9cfe-4079-b52a-82e34a47dda9.jpg</url>
      <title>Forem: Jeremy</title>
      <link>https://forem.com/jerr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/jerr"/>
    <language>en</language>
    <item>
      <title>Fun in Setting Up a Blog</title>
      <dc:creator>Jeremy</dc:creator>
      <pubDate>Sat, 31 Aug 2024 15:11:21 +0000</pubDate>
      <link>https://forem.com/jerr/fun-in-setting-up-a-blog-ice</link>
      <guid>https://forem.com/jerr/fun-in-setting-up-a-blog-ice</guid>
      <description>&lt;p&gt;I created this five years ago and then haven’t written any posts. To be honest, I didn’t know what to write about, nor did I have the energy to do so. What I realized now though is that I quite enjoy the thrill of setting up the infrastructure to be the fun part. That probably reflects in my professional work as well, being a Python developer but also being heavily involved in infrastructure.&lt;/p&gt;

&lt;p&gt;So perhaps this can be motivation that it’s ok to setup a blog and not post, or that you can just setup a silly single-purpose website just for the fun of it. You can get a cheap domain, setup GitHub or Cloudflare Pages, and have a lot of fun with that, and learn a bunch. For instance, I have my &lt;a href="https://jeremy.mayeres.be" rel="noopener noreferrer"&gt;CV website&lt;/a&gt; running with Jekyll and this blog set up with Hugo. The build process is quite different between them (Jekyll requires a lot more messing with Ruby versions), but that makes it interesting.&lt;/p&gt;

&lt;p&gt;So, will I be writing more? Who knows, time will tell. This is probably still a good idea to write down things I’ve learned so it doesn’t get lost. I’m also getting more into 3D printing, so if I’m waiting on a print maybe I can write up a post about what I’ve done.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>How to set up Atom for Jekyll blogging</title>
      <dc:creator>Jeremy</dc:creator>
      <pubDate>Sun, 11 Feb 2018 22:32:06 +0000</pubDate>
      <link>https://forem.com/jerr/how-to-set-up-atom-for-jekyll-blogging--29m5</link>
      <guid>https://forem.com/jerr/how-to-set-up-atom-for-jekyll-blogging--29m5</guid>
      <description>&lt;p&gt;I like to use &lt;a href="https://atom.io/" rel="noopener noreferrer"&gt;Atom&lt;/a&gt; as a relatively lightweight code editor. I also really like using static website generators like Jekyll, and writing in Markdown comes naturally to me. If you write a post on &lt;a href="https://dev.to"&gt;dev.to&lt;/a&gt;, you'll also see the same Markdown with YAML front matter. This short post should help you set up Atom for Markdown editing and previewing with support for the YAML front matter. &lt;/p&gt;

&lt;h2&gt;
  
  
  Prerequisites
&lt;/h2&gt;

&lt;p&gt;Obviously you'll need &lt;a href="https://atom.io/" rel="noopener noreferrer"&gt;Atom&lt;/a&gt; installed, but you also need to install &lt;a href="https://pandoc.org/" rel="noopener noreferrer"&gt;pandoc&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Atom Packages
&lt;/h2&gt;

&lt;p&gt;I tried a few different combinations of packages before finally getting the right ones. I believe the following is all you need to set up Atom for Markdown support:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;a href="https://atom.io/packages/language-markdown" rel="noopener noreferrer"&gt;language-markdown&lt;/a&gt; - Markdown syntax support&lt;/li&gt;
&lt;li&gt;
&lt;a href="https://atom.io/packages/markdown-preview-plus" rel="noopener noreferrer"&gt;markdown-preview-plus&lt;/a&gt; - Preview Markdown with live updates&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Configuration
&lt;/h2&gt;

&lt;p&gt;There's not too much configuration needed, but the Jekyll front matter by default will not parse well with the default settings. In the setting for Markdown Preview Plus, do the following:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Enable Pandoc parser&lt;/li&gt;
&lt;li&gt;Set Markdown flavor:
&lt;/li&gt;
&lt;/ol&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;markdown-raw_tex+tex_math_single_backslash+yaml_metadata_block
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The Markdown Preview Plus settings should then look something like this:&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7cb8p1pi5vhx8jgx7zl3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7cb8p1pi5vhx8jgx7zl3.png" alt="Settings screenshot" width="800" height="497"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let me know if I missed anything or if you have a better setup you'd like to share 😉&lt;/p&gt;

</description>
      <category>markdown</category>
      <category>atom</category>
      <category>setup</category>
      <category>jekyll</category>
    </item>
  </channel>
</rss>
