thank you @daniel_friis, really appreciate it :)

@joshuapinter the main difference is that Forestry is Git-based (that is, the actual content is stored as Markdown files within the repo), while we're API-based (the content is stored in a DB on our side and gets dumped as local Markdown files during build time). Obviously there are pros and cons with both the approaches.. with Git-based products there's less stuff to learn and you can start using them with existing static websites right away. With an API-based approach the content of your website, while being used during the build phase of the site to produce the static HTML files, can also be queried using client-side AJAX calls: this allows a whole set of new dynamic functionalities (ie. search pages), that would be otherwise impossible to achieve with static websites. Also, with an API-based approach, pretty much any present (and future) static website generator is compatible. You are also free to switch to a different static website generator at any time, simply editing the configuration files that map remote content to local Markdown files.

@steffoz Interesting. Thanks for the in-depth response. Looks like the perfect combination of an approachable CMS mixed with the benefits of a static site. Great job. Will try it out for sure.

@mrdobelina haha, grazie Filippo :)

@jevinsew we're an agency ourselves.. so we definitely feel the pain :)

@jevinsew ...and for complex sites. Like healthcare.gov see: https://developmentseed.org/blog...

@supamerz Thank you Antonio! :)

@itrepachko we have worked on a number of "static shops" using DatoCMS together with Snipcart (https://snipcart.com/) and a couple of custom Amazon Lambda functions. It works pretty well :) Example: http://www.linkingart.gallery/ (sorry, the website is in italian)

@andresgutgon thank you Andres! :)