[pavlov]

After reading the docs, I'm still not quite sure what Shunter does.

I do understand the use scenario. I've done some sites with this same model using Prismic.io as the backend. It's a nice customizable CMS-style system that provides JSON APIs, which a Node.js app then translates into HTML (basically just filling out templates with data selected from the JSON). This has worked well and I've been really quite happy with Prismic.

So it looks like I could be using Shunter for this scenario, but I'm not sure what the benefit would be over my hand-rolled Node apps. Can someone illuminate?

[dotcode]

This probably indicates that we need to do a bit of work on our documentation :) You're right about the general purpose - however Shunter also handles front-end assets: images, CSS, and JavaScript, as well as making it easy to extend the rendering engine.

In terms of benefits of using Shunter over a home-rolled solution, the same question could/should be asked of any framework. Shunter is very well tested, has been used in production on a large site for a number of years, and is used to serve hundreds of thousands of requests. It will also be supported by a large development team for the foreseeable future.

[pavlov]

Thanks! I'll keep it in mind and will try Shunter next time I do one of the Prismic-backed sites.

[dotcode]

Cool - let us know if we can help in any way :)