This blog is built with Hugo , which allows me to use some great CI tools like Wercker . The first part of writing a wercker.yml is picking a build container. 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’ve moved away from that approach to Docker containers.
I recently blogged a lot about static websites and continuous integration . There was still one step missing in my continuous integration cycle: minification. Wercker is a great CI tool and it allows you to create custom build steps that can be reused in several projects. So I created a build step to minify HTML, CSS and JS files.
So last week, I created a material design theme for Hugo , a static site generator that I’m quite fond of](/tags/hugo/). As I discovered Wercker , an awesome CI tool, I went looking for a way to automatically validate themes. There wasn’t any, so I simply wrote a build step for Wercker .
Why? Who doesn’t love GitHub Pages ? It’s the easiest way to create a simple website about a repository and you can even use Jekyll to start blogging. As I recently switched from Jekyll to Hugo , I needed a new way to enable continuous integration for my blog. New to CI?