
We’re excited to hear your project.
Let’s collaborate!
“It depends...” This is the very first honest answer to your “Jekyll or Hugo?” dilemma. Since your own use case scenario is (obviously) different from all the rest:
Once you've answered this “questionnaire” and you've identified your website's profile, delve into the Jekyll or Hugo 2017 comparison that our team of Toronto developers has prepared for you:
Here it goes:
“...instead of a dynamically generated one?”
Remember how the web used to be, back in the old days? “Databases-less” and static! Meaning: ideally simple and blazingly fast!
Well, that's precisely what you get when opting for a static site generator:
“But is a static site generator the best fit for my own website?”
Now, this is just the right type of question to be asking yourself right now. Our answer is:
What do you gain from using it?
When not to use Jekyll or Hugo or any other site generator:
The powerful “younger” rival of Jekyll with an ever-growing community of followers ”seduced” by all those features that it's been equipped with and which Jekyll lacks:
Key limitations:
The most widely used static site generator! Favored for its:
We need to admit that both Hugo and Jekyll provide you with very good documentation and great quick-start guides. So, you can launch your site with just one simple command:
Still, if we are to compare the two based on this criterion only, we need to add that Jekyll does have a slight advantage: you get a default theme and some example content to start with.
It depends on your own site's needs if you take it as an advantage or not quite (for you might not even use the default theme and content when you start up a new site anyway).
There's no debate here: Hugo is a static site generator way faster than Jekyll!
It's built on Go (compared to Jekyll, which runs on Ruby) and that explains a lot.
So, if:
“Extensibility” is, no doubt, Jekyll's trump card!
Thanks to its plugin architecture it enables you to easily add extra functionality, to extend your Jekyll-powered website's features once you've set it up.
So, the “Jekyll or Hugo?” question is primarily a “speed vs extensibility” debate.
The provided workflow for building your website is another aspect where the 2 static website generators seem to be neck-and-neck.
Both the Jekyll server and Hugo server are configured to automatically catch up with any updates that you make to your theme, images, content, or configuration while working on your website.
Also, they both enable you to add new content to your website's backbone structure just by creating new files in the right place.
Note: it's here that we can still “detect” an advantage of Hugo over Jekyll (so they're not THAT even after all); it provides you with certain functions which automatically check that your new files get created precisely in the right parts of your site's frame.
In a “Jekyll or Hugo” dilemma the theming aspect does weigh a lot, doesn't it?
Well, we have 2 types of news for you: a good and a “so and so” one:
... since you're not provided with sufficiently detailed information on each one of them
And here we have a clear winner: Jekyll!
Since it was the very first modern site generator ever built no wonder that it gathered such a large community around it!
In short: if support is crucial for you, you'll be thrilled by Jekyll's wide community of peers generating content, backing you up, and being there to answer your questions.
So, which one of them has won you over so far, now that you've defined your site's specific profile and you've scanned through these 2 major static website generators' strengths and weaknesses: Jekyll or Hugo?
We’re excited to hear your project.
Let’s collaborate!