Wercker step to minify static resources
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.
The build step is available at https://github.com/sdebruyn/wercker-step-minify
and all you have to do is include samueldebruyn/minify as a step in your wercker.yml file.
You might also like
If you liked this article, follow me on LinkedIn, Bluesky, or other social media to stay up-to-date with my latest posts. You might also like the following 2 posts about related topics:
Wercker step to validate Hugo themes
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 .
Continuous integration with Hugo and 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?