Hexo vs Jekyll: What are the differences?
Hexo: A fast, simple & powerful blog framework, powered by Node.js. Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds; Jekyll: Blog-aware, static site generator in Ruby. Think of Jekyll as a file-based CMS, without all the complexity. Jekyll takes your content, renders Markdown and Liquid templates, and spits out a complete, static website ready to be served by Apache, Nginx or another web server. Jekyll is the engine behind GitHub Pages, which you can use to host sites right from your GitHub repositories.
Hexo and Jekyll belong to "Static Site Generators" category of the tech stack.
Some of the features offered by Hexo are:
- Blazing Fast - Node.js brings you incredible generating speed. Hundreds of files take only seconds to build.
- Markdown Support - All features of GitHub Flavored Markdown are supported. You can even use most Octopress plugins in Hexo.
- One-Command Deployment - You only need one command to deploy your site to GitHub Pages, Heroku or other sites.
On the other hand, Jekyll provides the following key features:
- Simple - No more databases, comment moderation, or pesky updates to install—just your content.
- Static - Markdown (or Textile), Liquid, HTML & CSS go in. Static sites come out ready for deployment.
- Blog-aware - Permalinks, categories, pages, posts, and custom layouts are all first-class citizens here.
"Ease of deployment" is the top reason why over 15 developers like Hexo, while over 65 developers mention "Github pages integration" as the leading cause for choosing Jekyll.
Hexo and Jekyll are both open source tools. It seems that Jekyll with 38.1K GitHub stars and 8.31K forks on GitHub has more adoption than Hexo with 27.1K GitHub stars and 3.6K GitHub forks.
According to the StackShare community, Jekyll has a broader approval, being mentioned in 111 company stacks & 125 developers stacks; compared to Hexo, which is listed in 6 company stacks and 24 developer stacks.
What is Hexo?
What is Jekyll?
Want advice about which of these to choose?Ask the StackShare community!
What are the cons of using Hexo?
What tools integrate with Jekyll?
With limited knowledge of CSS/HTML5, Jekyll makes it easy to create templates for static HTML5 sites. Unless I really need a database for something, this is the tool I prefer for standing up websites.
I settled on Jekyll to be the CMS for my research blog. Out of the box it works, and over time I added to it... why write a dissertation when you can instead hack templates to tweak things.
This static site generator is used with "contentful-import" ruby plugin, which allows to fetch data from Contentfull and generate new web-pages based on it. Easy and fun to use.
Content for blog posts and pages is written in markdown format, using Emacs. Hexo generates the site using my own customised theme. The site is then deployed to Github pages
We wanted to pay the cost for website generation up front. Doing this allows us to put our website up in AWS S3 where it can be served reliably and for cheap.
We use Jekyll to build our website. We created a collection for talks. We handle speakers and sponsors via data files.
To build my site blog. I also created a tag plugin for Hexo that enables you to embed Deezer objects in your page.