When comparing Webhook vs Harp, the Slant community recommends Webhook for most people. In the question“What are the best static site generators?” Webhook is ranked 20th while Harp is ranked 26th. The most important reason people chose Webhook is:
A very flexible license to do whatever you want. Code available on [GitHub](https://github.com/webhook/webhook).
Ranked in these QuestionsQuestion Ranking
Pro MIT Open Source
A very flexible license to do whatever you want. Code available on GitHub.
Pro Friendly CMS that clients can use
Webhook has a CMS admin page that can be access on the live site. This lets your clients login and edit the site like a traditional CMS system.
Pro Works with Firebase
Rather than store the data in flat files, Webhook stores your data in Firebase, where it can be accessed similar to JSON from other applications.
Pro Flexible Content Creation
Lets you describe your own content types and their own fields easily from the admin interface.
Pro Compiles assets on request
Rather than regenerate the whole site when a file changes, Harp only reloads what is necessary, keeping the compile time fast.
Pro Supports popular languages
Harp supports a large variety of languages, including Jade, CoffeeScript, Stylus and Sass. See the full list here.
Con Requires registration
Even simple command line tools require registration.
Con Limited extensibility
There are no plugins available to extend the functionality or language support of Harp.