When comparing Roots vs Wintersmith, the Slant community recommends Wintersmith for most people. In the question“What are the best static site generators?” Wintersmith is ranked 5th while Roots is ranked 18th. The most important reason people chose Wintersmith is:
Wintersmith has an extensive Markdown support. Default, it is rendered by [Marked](https://github.com/chjj/marked). However there are plugins available for [others](https://github.com/jnordberg/wintersmith/wiki/Plugins) (such as [Markdown-it](https://github.com/dwaite/wintersmith-markdown-it)).
Ranked in these QuestionsQuestion Ranking
Pro Active development
Roots has heavy corporate sponsorship and is worked on very actively as a full time job. That means you can rely on it.
Pro Quick deploys
You can deploy to heroku, github pages, s3, etc. with a single command.
Pro Dynamic content
Roots supports dynamic content like jekyll for every compiler and language.
Pro Currently going through an upgrade
Roots is currently in the process examining how to leverage newer technologies to make Roots even better. You can see the new project on github: https://github.com/carrot/roots-mini
Here is the blog post explaining the next phase of Roots: https://medium.com/@jescalan/eaa10c75eb22#.uacjziaej
Here is the stack they're experimenting with:
- jade - for markup - babel - for JS and JS transforms - postcss - for CSS transforms - webpack - as the core compiler
As this is a work in process, it just means the future of Roots continues to look great.
Pro Custom compilers
Not only does roots support a huge number of languages and compilers out of the box, it also allows you to insert custom compilers if you want. Fun fact, roots is the only static site generator that supports dogescript
Pro Multipass compiles
Roots compiles files once for each extension, which allows for some advanced options if you get to that stage
Pro Client-side templates
Roots will precompile your templates into js, which makes it really smooth to work with client-side MV* frameworks.
Since roots is written in node, everything is compiled in parallel rather than in series, making it very quick.
Templating engine comes with Jade plugin and many third-party plugins.
Pro Very flexible
Wintersmith only has a predefined directory structure, everything else can built any way you want.
Pro Built on node.js
Node.js is a software platform for scalable server-side and networking applications.
Con No i18n (Internationalization)
There is no i18n support out of the box. And there is only one extension that does i18n compilation with a limited feature set.
Con Thin and disorganized documentation
The documentation for Wintersmith is lacking examples and clear explanations. It's also quite disorganized, making it difficult to find what you're looking for.