Welcome to the static world. Your sites scale easily, load faster and more efficiently, and you and your clients are already seeing the benefits. The Jamstack ecosystem is thriving, with tools and support for static sites growing day by day, and CloudCannon has just launched Eleventy support, alongside Jekyll and Hugo. There’s never been a better time to be a web developer. But we return to the perennial question: which static site generator (SSG) should you choose for your next project?
Here we’ll compare two distinctly different SSGs: Jekyll and Eleventy. They’re both fully compatible with CloudCannon’s Git-based CMS, and both are ideal for marketing sites (such as this one, built with Jekyll), as well as documentation and blogs. But let’s compare and contrast, shall we?
Tom Preston-Werner’s “simple, blog-aware” SSG, released in 2008, kicked off the recent web dev trend towards static sites: Jekyll is the basis of GitHub Pages, serving verbatim or Markdown files to visitors, and enabling GitHub users to host their own blogs, documentation, and even books. Written in Ruby by Preston-Werner, Jekyll has since been maintained by Parker Moore, and is currently sitting at version 4.2.0. Nice.
Because Jekyll has been around for so long, there’s a huge amount of documentation, support, plugins and templates available for users. Think about it like this: the existing users have asked the tough questions and largely figured out the edges of the generator so you don’t have to.
For many developers, part of Eleventy’s appeal is that it doesn’t make assumptions about your content. The default hierarchies are logical if you’re starting a new project, but you can also bring over your existing project files and directory structures, and just point Eleventy in the right direction.
|Plugins||Yes, via Ruby Gems||Yes|
|Themes||Yes||Yes (11ty uses the term ‘starter’.)|
|Open source licence||MIT||MIT|
|Installation requirements||Ruby must be installed.||Via npm|
|Build speeds||Fast-adjacent, though growing sites build increasingly slowly.||Faster|
|Multilingual and i18n||Via plugins||Via plugins|
|Easy Wordpress et al. converter||Yes: Jekyll converter||No; you’ll need to convert to Markdown and then clean up with layout templates.|
|Support communities||Jekyll Talk
|Eleventy Discord and eleventy-community both have helpful communities.|
|Twitter accounts||Jekyll Twitter||Eleventy Twitter|
Neither Jekyll nor Eleventy is difficult to set up on your local machine, though in any case, CloudCannon makes setting up (and connecting to your chosen Git repo) a single-click proposition.
Choose Jekyll if you want a quick solution to importing existing blogs from legacy dynamic monoliths. For new Jekyll builds you’ll find dates, drafts and sorting posts are ready to use immediately, but as some users have pointed out, Jekyll has a relatively strict structure, meaning it can be more difficult to customize. Jekyll build times might remain a concern for some, particularly with larger sites; you’ll find that as a site grows it will take progressively longer to build.
Choose Eleventy if you’re looking for a future-proofed SSG, where content is decoupled as much as possible from the SSG itself (and is therefore easier to extract, should you need to). Even the templating engines — and remember, you can mix and match between ten, within a single project — are by design as Eleventy-independent as possible. If build times are a big concern, Eleventy is likely to be the SSG for you. Add to that the widest flexibility for templating languages the Jamstack community has seen so far (including Liquid, for those particularly interested in transferring from Jekyll).
Whatever your choice, CloudCannon is here for you. Our Git-based CMS works seamlessly with both Jekyll and Eleventy (as well as Hugo, if Go is more your speed, and more speed is more your thing), letting you empower your content team with robust publishing workflows, and spend more time on the development work you enjoy.