Need advice about which tool to choose?Ask the StackShare community!
Decisions about Hexo, Hugo, and Jekyll
Manuel Feller
Frontend Engineer at BI X · | 4 upvotes · 68.2K views
As a Frontend Developer I wanted something simple to generate static websites with technology I am familiar with. GatsbyJS was in the stack I am familiar with, does not need any other languages / package managers and allows quick content deployment in pure HTML or Markdown (what you prefer for a project). It also does not require you to understand a theming engine if you need a custom design.
Pros of Hexo
Pros of Hugo
Pros of Jekyll
Pros of Hexo
- Ease of deployment16
- Easy GitHub Pages publishing12
- Uses NodeJS and npm12
- Powerful templating9
- Useful tools and plugins7
- Easy intergrating with js4
- Open source3
- Blazing Fast2
Pros of Hugo
- Lightning fast40
- Single Executable22
- Easy setup20
- Great development community18
- Open source17
- Write in golang10
- Not HTML only - JSON, RSS5
- LiveReload built in5
- Hacker mindset4
- Gitlab pages integration1
Pros of Jekyll
- Github pages integration74
- Open source54
- It's slick, customisable and hackerish36
- Easy to deploy23
- Straightforward cms for the hacker mindset22
- Gitlab pages integration6
- Best for blogging4
- Easy to integrate localization2
- Low maintenance2
- Huge plugins ecosystem1
- Authoring freedom and simplicity1
Sign up to add or upvote prosMake informed product decisions
Cons of Hexo
Cons of Hugo
Cons of Jekyll
Cons of Hexo
Be the first to leave a con
Cons of Hugo
- No Plugins/Extensions3
- Template syntax not friendly2
Cons of Jekyll
- Build time increases exponentially as site grows4
- Lack of developments lately2
- Og doesn't work with postings dynamically1