When comparing Nanoc vs Roots, the Slant community recommends Nanoc for most people. In the question“What are the best static site generators?” Nanoc is ranked 8th while Roots is ranked 18th. The most important reason people chose Nanoc is:
Nanoc is a good choice if you need to support a site with a more complex structure than a simple blog. Nanoc is more agnostic to the types of pages you have, and allows you to do finer tuned refinements like customizing the URL structure.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Flexibly built
Nanoc is a good choice if you need to support a site with a more complex structure than a simple blog. Nanoc is more agnostic to the types of pages you have, and allows you to do finer tuned refinements like customizing the URL structure.
Pro Extensibile
Nanoc has a modular architecture which makes it easier to incorporate plugins and functionality from other projects as well as extend functionality.
Pro Helps you create multilingual sites
Nanoc takes multilingual sites into consideration and has features to make translations easier to implement.
Pro Unit testing integration
Nanoc has a check command to run tests against your site and make sure it meets requirements you define.
There are built in checks to validate HTML and CSS, as well as validating internal and external links.
Pro Works well with compile to languages
Nanoc is friendly with different CSS and HTML preprocessors, so you can easily use SASS, LESS, HAML, Markdown and more.
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.
Pro Quick
Since roots is written in node, everything is compiled in parallel rather than in series, making it very quick.
Cons
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.