| Hugo provides many of the same features of Harp.js which is also a good project. Hugo provides a server for local development like jade. Hugo is a bit easier to install as it doesn't have dependencies and doesn't require an existing environment. Hugo is noticibly faster. The big difference between the two is that Hugo has not focused on compiling all the other assets like scss, less, coffee script, etc. While this is planned for a future release today Hugo users have experienced a lot success pairing Hugo with Gulp. You can read more in this discussion on the forum: https://discuss.gohugo.io/t/gulp-hugo-hugo-npm/1121 Unfortunately by introducing gulp it negates some of the benefits of Hugo's one binary install. Hugo does provide some advanced features that I don't believe Harp provides including: * Data file loading https://gohugo.io/extras/datafiles/ * Live data https://gohugo.io/extras/datadrivencontent/ * Live reload (this is a huge feature) https://gohugo.io/extras/livereload/ * Menus https://gohugo.io/extras/menus/ * Themes https://themes.gohugo.io If you are happy with Harp and it serves your needs than there's not really a reason to switch. The big difference is Hugo + Gulp is a workflow that works really well and has all the features that Harp provides (plus all the Hugo features). If you need a feature that only Hugo provides there really isn't a way to add that to harp.js. I'm the author of Hugo and haven't ever used Harp so take all of this with a grain of salt. |