Need advice about which tool to choose?Ask the StackShare community!

Hexo

264
300
+ 1
65
Hugo

954
838
+ 1
141
Jekyll

1.3K
1.1K
+ 1
225
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.

See more
Pros of Hexo
Pros of Hugo
Pros of Jekyll
  • 16
    Ease of deployment
  • 12
    Easy GitHub Pages publishing
  • 12
    Uses NodeJS and npm
  • 9
    Powerful templating
  • 7
    Useful tools and plugins
  • 4
    Easy intergrating with js
  • 3
    Open source
  • 2
    Blazing Fast
  • 40
    Lightning fast
  • 22
    Single Executable
  • 20
    Easy setup
  • 18
    Great development community
  • 17
    Open source
  • 10
    Write in golang
  • 5
    Not HTML only - JSON, RSS
  • 5
    LiveReload built in
  • 4
    Hacker mindset
  • 1
    Gitlab pages integration
  • 74
    Github pages integration
  • 54
    Open source
  • 36
    It's slick, customisable and hackerish
  • 23
    Easy to deploy
  • 22
    Straightforward cms for the hacker mindset
  • 6
    Gitlab pages integration
  • 4
    Best for blogging
  • 2
    Easy to integrate localization
  • 2
    Low maintenance
  • 1
    Huge plugins ecosystem
  • 1
    Authoring freedom and simplicity

Sign up to add or upvote prosMake informed product decisions

Cons of Hexo
Cons of Hugo
Cons of Jekyll
    Be the first to leave a con
    • 3
      No Plugins/Extensions
    • 2
      Template syntax not friendly
    • 4
      Build time increases exponentially as site grows
    • 2
      Lack of developments lately
    • 1
      Og doesn't work with postings dynamically

    Sign up to add or upvote consMake informed product decisions