<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator><link href="https://vincesoft.co.za/feed.xml" rel="self" type="application/atom+xml" /><link href="https://vincesoft.co.za/" rel="alternate" type="text/html" /><updated>2026-04-30T12:26:39+00:00</updated><id>https://vincesoft.co.za/feed.xml</id><title type="html">VinceSoft Blog</title><subtitle>VinceSoft Blog is a place where I share my thoughts and experiences with new and existing technologies. LLM&apos;s, GPUs, PC Hardware, Microcontrollers, and more.</subtitle><entry><title type="html">Why Jekyll?</title><link href="https://vincesoft.co.za/jekyll/blog-updates/2025/12/29/why-jekyll.html" rel="alternate" type="text/html" title="Why Jekyll?" /><published>2025-12-29T16:45:20+00:00</published><updated>2025-12-29T16:45:20+00:00</updated><id>https://vincesoft.co.za/jekyll/blog-updates/2025/12/29/why-jekyll</id><content type="html" xml:base="https://vincesoft.co.za/jekyll/blog-updates/2025/12/29/why-jekyll.html"><![CDATA[<p>tl;dr: Jekyll is established, simple, open source.</p>

<p>For those who don’t know, this blog uses Jekyll. Jekyll is old, established, and has a lot of plugins and themes available. It’s also free and open source. It uses Ruby to convert Markdown files into static HTML files. Meaning i can keep the posts in a non-proprietary markdown format, and change to whatever format I want in the future.</p>

<p>Not being tied down to any provider formats is mostly what kept me from ever starting a blog. I used to run a Wordpress blog, but honestly in this day and age, I’d prefer something static that can be served from anywhere.</p>

<p>Ruby is the elephant in the room, used by Jekyll to convert the Markdown files into HTML. I have’nt coded much and I dont have any of the setup for it. But Docker to the rescue! I have a simple docker image, that builds the site and puts it in the right place. I can easily extend this with Github pages, which is coming soon.</p>]]></content><author><name></name></author><category term="jekyll" /><category term="blog-updates" /><summary type="html"><![CDATA[tl;dr: Jekyll is established, simple, open source. For those who don’t know, this blog uses Jekyll. Jekyll is old, established, and has a lot of plugins and themes available. It’s also free and open source. It uses Ruby to convert Markdown files into static HTML files. Meaning i can keep the posts in a non-proprietary markdown format, and change to whatever format I want in the future. Not being tied down to any provider formats is mostly what kept me from ever starting a blog. I used to run a Wordpress blog, but honestly in this day and age, I’d prefer something static that can be served from anywhere. Ruby is the elephant in the room, used by Jekyll to convert the Markdown files into HTML. I have’nt coded much and I dont have any of the setup for it. But Docker to the rescue! I have a simple docker image, that builds the site and puts it in the right place. I can easily extend this with Github pages, which is coming soon.]]></summary></entry><entry><title type="html">Welcome to Jekyll!</title><link href="https://vincesoft.co.za/jekyll/update/2025/09/22/welcome-to-jekyll.html" rel="alternate" type="text/html" title="Welcome to Jekyll!" /><published>2025-09-22T13:45:20+00:00</published><updated>2025-09-22T13:45:20+00:00</updated><id>https://vincesoft.co.za/jekyll/update/2025/09/22/welcome-to-jekyll</id><content type="html" xml:base="https://vincesoft.co.za/jekyll/update/2025/09/22/welcome-to-jekyll.html"><![CDATA[<p>You’ll find this post in your <code class="language-plaintext highlighter-rouge">_posts</code> directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run <code class="language-plaintext highlighter-rouge">jekyll serve</code>, which launches a web server and auto-regenerates your site when a file is updated.</p>

<p>Jekyll requires blog post files to be named according to the following format:</p>

<p><code class="language-plaintext highlighter-rouge">YEAR-MONTH-DAY-title.MARKUP</code></p>

<p>Where <code class="language-plaintext highlighter-rouge">YEAR</code> is a four-digit number, <code class="language-plaintext highlighter-rouge">MONTH</code> and <code class="language-plaintext highlighter-rouge">DAY</code> are both two-digit numbers, and <code class="language-plaintext highlighter-rouge">MARKUP</code> is the file extension representing the format used in the file. After that, include the necessary front matter. Take a look at the source for this post to get an idea about how it works.</p>

<p>Jekyll also offers powerful support for code snippets:</p>

<figure class="highlight"><pre><code class="language-ruby" data-lang="ruby"><span class="k">def</span> <span class="nf">print_hi</span><span class="p">(</span><span class="nb">name</span><span class="p">)</span>
  <span class="nb">puts</span> <span class="s2">"Hi, </span><span class="si">#{</span><span class="nb">name</span><span class="si">}</span><span class="s2">"</span>
<span class="k">end</span>
<span class="n">print_hi</span><span class="p">(</span><span class="s1">'Tom'</span><span class="p">)</span>
<span class="c1">#=&gt; prints 'Hi, Tom' to STDOUT.</span></code></pre></figure>

<p>Check out the <a href="https://jekyllrb.com/docs/home">Jekyll docs</a> for more info on how to get the most out of Jekyll. File all bugs/feature requests at <a href="https://github.com/jekyll/jekyll">Jekyll’s GitHub repo</a>. If you have questions, you can ask them on <a href="https://talk.jekyllrb.com/">Jekyll Talk</a>.</p>]]></content><author><name></name></author><category term="jekyll" /><category term="update" /><summary type="html"><![CDATA[You’ll find this post in your _posts directory. Go ahead and edit it and re-build the site to see your changes. You can rebuild the site in many different ways, but the most common way is to run jekyll serve, which launches a web server and auto-regenerates your site when a file is updated.]]></summary></entry></feed>