When comparing Jekyll vs Roots, the Slant community recommends Jekyll for most people. In the question“What are the best static site generators?” Jekyll is ranked 4th while Roots is ranked 19th. The most important reason people chose Jekyll is:
You can host your site with great stability and Jekyll support out of the box for free by using [GitHub pages](http://pages.github.com/).
Ranked in these QuestionsQuestion Ranking
Pro GitHub Pages offers free hosting with a github.io subdomain
You can host your site with great stability and Jekyll support out of the box for free by using GitHub pages.
Pro Can use HTML to set up your page templates, and markdown for your blog posts
Pro Has a built in server
You can spin up a static server at localhost:4000 by running
Pro Code highlighting with pygments
Jekyll has Pygments code highlighting built in so you can create syntax highlighted code blocks on your blog.
Pro Excels at blogging
Jekyll pages are structured by posts, which makes it easier to build a blog.
Pro Decent documentation
Link to docs
Pro Import your existing blog from many sources
Jekyll supports importing from many dynamic blog engines:
- Drupal 6
- Drupal 7
- Google Reader
- Movable Type
Pro Has built in watch mode
Watch mode will reconstruct the site as pages are updated which is great for testing.
Pro Large, active and helpful community
Thanks to it's popularity, Jekyll has a large and active community of users. This means there is plenty of learning material available for Jekyll and it's easy to find help from other users when needed.
Pro Customisable with data and collections
Can make sites very different from blogs but with a lot of pages by making templates using data and collections.
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.
Con It's slow for sites with a lot of posts
Con Little Windows support
Windows is not an officially supported platform and setting it up on Windows requires a lot more tinkering than Linux or OSX.
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.