From 6fa536f3268bf7bd4fd85df7fa78fbc4c67eaaa1 Mon Sep 17 00:00:00 2001 From: Ben Burwell Date: Sat, 20 Dec 2014 23:13:09 -0500 Subject: Working on some major changes --- _posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown | 1 + 1 file changed, 1 insertion(+) (limited to '_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown') diff --git a/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown b/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown index c5e66f9..6762b7c 100644 --- a/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown +++ b/_posts/2014-05-31-less-file-compilation-for-jekyll-github-pages.markdown @@ -4,6 +4,7 @@ title: LESS File Compilation for Jekyll and GitHub Pages description: Git’s pre-commit hook allows one-click static site deployment — including LESS file compilation — to GitHub pages. category: writing date: 2014-05-31 00:00:00 +redirect_from: "/writing/less-file-compilation-for-jekyll-github-pages/" --- I recently wrote about [migrating my website to GitHub Pages](/writing/migrating-to-github-pages-and-jekyll) and noted that I wasn’t completely satisfied with my deployment workflow. Ideally, [creating a build should be done in a single step](http://www.joelonsoftware.com/articles/fog0000000043.html). As I wrote, my previous build workflow required me to manually compile my [LESS](http://lesscss.org) files before committing if I’d made changes. While my stylesheet doesn’t change often, this method is certainly not ideal. -- cgit v1.2.3