https://67ea45403ad50a0008fd0d16--broersmadev.netlify.app/tags/hugo/ Recent content in hugo on Rouke Broersma Hugo -- gohugo.io rouke@broersma.dev (Rouke Broersma) rouke@broersma.dev (Rouke Broersma) Fri, 21 May 2021 19:56:08 +0000 https://67ea45403ad50a0008fd0d16--broersmadev.netlify.app/hugo-modules-for-themes/ Fri, 21 May 2021 19:56:08 +0000 rouke@broersma.dev (Rouke Broersma) https://67ea45403ad50a0008fd0d16--broersmadev.netlify.app/hugo-modules-for-themes/ The hugo tutorial tells you to use git submodules for themes. However hugo has a better system for dependencies called modules. I’ ll show you how to switch from git submodules to hugo modules! https://67ea45403ad50a0008fd0d16--broersmadev.netlify.app/why-i-chose-hugo/ Sat, 08 May 2021 20:44:16 +0000 rouke@broersma.dev (Rouke Broersma) https://67ea45403ad50a0008fd0d16--broersmadev.netlify.app/why-i-chose-hugo/ This blog is currently powered by Hugo, a static site generator built in Go. However this was not my first choice. Initially I was going to use Jekyll for the simple reason that I had heard of it before and it is what Github uses to power Github Pages. Almost immediately I decided that while Jekyll seems fine to use I did not want to be limited to what Github natively offers, and I didn’t have to.