<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hugo on Sam Debruyn</title><link>https://debruyn.dev/tags/hugo/</link><description>Recent content in Hugo on Sam Debruyn</description><generator>Hugo</generator><language>en-us</language><copyright>© Copyright Debruyn Consultancy</copyright><lastBuildDate>Sun, 20 Aug 2023 13:27:35 +0200</lastBuildDate><atom:link href="https://debruyn.dev/tags/hugo/index.xml" rel="self" type="application/rss+xml"/><item><title>Docker image for Hugo builds (with Wercker)</title><link>https://debruyn.dev/2015/docker-image-for-hugo-builds-with-wercker/</link><pubDate>Mon, 31 Aug 2015 18:56:39 +0200</pubDate><guid>https://debruyn.dev/2015/docker-image-for-hugo-builds-with-wercker/</guid><description>&lt;p&gt;This blog is built with &lt;a
 href="http://gohugo.io" data-umami-event="outbound_link_click" data-umami-event-url="http://gohugo.io" target="_blank" rel="noreferrer noopener"
 &gt;Hugo&lt;/a&gt;
, which allows me to use some great CI tools like &lt;a
 href="http://wercker.com" data-umami-event="outbound_link_click" data-umami-event-url="http://wercker.com" target="_blank" rel="noreferrer noopener"
 &gt;Wercker&lt;/a&gt;
. The first part of writing a &lt;em&gt;wercker.yml&lt;/em&gt; is picking a build container.&lt;/p&gt;
&lt;p&gt;A build container on Wercker is the environment in which your build or deploy steps run. Wercker used to build its own containers for that, but they&amp;rsquo;ve moved away from that approach to Docker containers. You can use all kinds of Docker containers, but most people just use one available publicly on &lt;a
 href="https://registry.hub.docker.com/" data-umami-event="outbound_link_click" data-umami-event-url="https://registry.hub.docker.com/" target="_blank" rel="noreferrer noopener"
 &gt;Docker Hub&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>Wercker step to validate Hugo themes</title><link>https://debruyn.dev/2015/wercker-step-to-validate-hugo-themes/</link><pubDate>Wed, 15 Jul 2015 13:21:45 +0200</pubDate><guid>https://debruyn.dev/2015/wercker-step-to-validate-hugo-themes/</guid><description>&lt;p&gt;So last week, I created &lt;a
 href="https://debruyn.dev/2015/material-lite-theme-for-hugo/"
 &gt;a material design theme&lt;/a&gt;
 for &lt;a
 href="https://gohugo.io" data-umami-event="outbound_link_click" data-umami-event-url="https://gohugo.io" target="_blank" rel="noreferrer noopener"
 &gt;Hugo&lt;/a&gt;
, a static site generator that I&amp;rsquo;m &lt;a
 href="https://debruyn.dev/tags/hugo/"
 &gt;quite fond&lt;/a&gt;
 of](/tags/hugo/).&lt;/p&gt;
&lt;p&gt;As I &lt;a
 href="https://debruyn.dev/2015/continuous-integration-with-hugo-and-wercker/"
 &gt;discovered Wercker&lt;/a&gt;
, an awesome CI tool, I went looking for a way to automatically validate themes.&lt;/p&gt;
&lt;p&gt;There wasn&amp;rsquo;t any, so I simply wrote a build step for &lt;a
 href="http://wercker.com" data-umami-event="outbound_link_click" data-umami-event-url="http://wercker.com" target="_blank" rel="noreferrer noopener"
 &gt;Wercker&lt;/a&gt;
. The build step validates a Hugo theme using &lt;a
 href="https://github.com/spf13/HugoBasicExample" data-umami-event="outbound_link_click" data-umami-event-url="https://github.com/spf13/HugoBasicExample" target="_blank" rel="noreferrer noopener"
 &gt;an example site&lt;/a&gt;
. It also checks if you included some files required for a future Hugo themes site.&lt;/p&gt;</description></item><item><title>Continuous integration with Hugo and Wercker</title><link>https://debruyn.dev/2015/continuous-integration-with-hugo-and-wercker/</link><pubDate>Tue, 14 Jul 2015 12:45:28 +0200</pubDate><guid>https://debruyn.dev/2015/continuous-integration-with-hugo-and-wercker/</guid><description>&lt;h2 id="why"&gt;Why?&lt;/h2&gt;
&lt;p&gt;Who doesn&amp;rsquo;t love &lt;a
 href="https://pages.github.com/" data-umami-event="outbound_link_click" data-umami-event-url="https://pages.github.com/" target="_blank" rel="noreferrer noopener"
 &gt;GitHub Pages&lt;/a&gt;
? It&amp;rsquo;s the easiest way to create a simple website about a repository and you can even use &lt;a
 href="http://jekyllrb.com/" data-umami-event="outbound_link_click" data-umami-event-url="http://jekyllrb.com/" target="_blank" rel="noreferrer noopener"
 &gt;Jekyll&lt;/a&gt;
 to start blogging.&lt;/p&gt;
&lt;p&gt;As I recently switched from Jekyll to &lt;a
 href="http://gohugo.io" data-umami-event="outbound_link_click" data-umami-event-url="http://gohugo.io" target="_blank" rel="noreferrer noopener"
 &gt;Hugo&lt;/a&gt;
, I needed a new way to enable continuous integration for my blog.&lt;/p&gt;</description></item><item><title>Material-lite theme for Hugo</title><link>https://debruyn.dev/2015/material-lite-theme-for-hugo/</link><pubDate>Mon, 13 Jul 2015 08:00:00 +0200</pubDate><guid>https://debruyn.dev/2015/material-lite-theme-for-hugo/</guid><description>&lt;p&gt;Last week, &lt;a
 href="https://debruyn.dev/2015/an-introduction-to-hugo-a-static-site-generator/"
 &gt;I wrote a post&lt;/a&gt;
 about how awesome &lt;a
 href="http://gohugo.io" data-umami-event="outbound_link_click" data-umami-event-url="http://gohugo.io" target="_blank" rel="noreferrer noopener"
 &gt;Hugo&lt;/a&gt;
 is and why I switched from Jekyll to Hugo.&lt;/p&gt;
&lt;p&gt;Then, a few days later, Google released an awesome template called &lt;a
 href="http://getmdl.io" data-umami-event="outbound_link_click" data-umami-event-url="http://getmdl.io" target="_blank" rel="noreferrer noopener"
 &gt;Material Design Lite&lt;/a&gt;
. It&amp;rsquo;s basically Google&amp;rsquo;s famous &lt;a
 href="https://www.google.com/design/spec/material-design/introduction.html" data-umami-event="outbound_link_click" data-umami-event-url="https://www.google.com/design/spec/material-design/introduction.html" target="_blank" rel="noreferrer noopener"
 &gt;Material Design&lt;/a&gt;
 in HTML, CSS and JavaScript instead of in &lt;a
 href="https://www.polymer-project.org" data-umami-event="outbound_link_click" data-umami-event-url="https://www.polymer-project.org" target="_blank" rel="noreferrer noopener"
 &gt;Polymer&lt;/a&gt;
.&lt;/p&gt;</description></item><item><title>An introduction to Hugo, a static site generator</title><link>https://debruyn.dev/2015/an-introduction-to-hugo-a-static-site-generator/</link><pubDate>Wed, 08 Jul 2015 14:50:29 +0200</pubDate><guid>https://debruyn.dev/2015/an-introduction-to-hugo-a-static-site-generator/</guid><description>&lt;h2 id="a-good-blogging-platform"&gt;A good blogging platform&lt;/h2&gt;
&lt;p&gt;What makes a good blogging platform really good? Well, that depends on the blogger. Programmers would need different features than make-up bloggers. As a programmer, I need to be able to easily integrate pieces of code with syntax highlighting in my posts and I&amp;rsquo;d prefer writing them in my favourite text/code editor instead of in a WYSIWYG editor.&lt;/p&gt;</description></item></channel></rss>