Need advice about which tool to choose?Ask the StackShare community!
Gatsby vs Jekyll: What are the differences?
Gatsby: Free, open source framework for building blazing fast websites and apps with React. Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future; 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.
Gatsby and Jekyll belong to "Static Site Generators" category of the tech stack.
"Generated websites are super fast" is the primary reason why developers consider Gatsby over the competitors, whereas "Github pages integration" was stated as the key factor in picking Jekyll.
Gatsby 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 Gatsby with 36.2K GitHub stars and 5.4K GitHub forks.
Sentry, New Relic, and Tilt are some of the popular companies that use Jekyll, whereas Gatsby is used by FashionUnited, Hazeorid, and Policygenius. Jekyll has a broader approval, being mentioned in 111 company stacks & 125 developers stacks; compared to Gatsby, which is listed in 49 company stacks and 139 developer stacks.
Hi everyone, I'm trying to decide which front-end tool, that will likely use server-side rendering (SSR), in hopes it'll be faster. The end-user will upload a document and they see text output on their screen (like SaaS or microservice). I read that Gatsby can also do SSR. Also want to add a headless CMS that is easy to use.
Backend is in Go. Open to ideas. Thank you.
If your purpose is plain simply to upload a file which can handle by backend service than Gatsby is good enough assuming you have other content pages which will benefit from faster page loads for those Headless CMS driven pages. But if you have more logical/functional aspects like deciding content/personalization at server side of web application than choose NextJS.
I have experience with Hugo and Next.js, but not with Gatsby. I would go with Next.js. However, I used Astro for my last project, so I would recommend Astro. Astro is much faster and you can use almost any frontend framework if you need to.
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 Gatsby
- Generated websites are super fast28
- Fast16
- GraphQL15
- Progressive Web Apps generation10
- Easy to connect with lots of CMS via official plugins9
- Reusable components (React)9
- Allows to use markdown files as articles7
- Static-sites5
- All the benefits of a static website + React+GraphQL5
- Images5
- List of starters as base for new project4
- Easy to connect with Drupal via official plugin3
- Open source3
- Gitlab pages integration1
- Incremental Build1
Pros of Jekyll
- Github pages integration74
- Open source54
- It's slick, customisable and hackerish37
- Easy to deploy24
- Straightforward cms for the hacker mindset23
- Gitlab pages integration7
- Best for blogging5
- Low maintenance2
- Easy to integrate localization2
- Huge plugins ecosystem1
- Authoring freedom and simplicity1
Sign up to add or upvote prosMake informed product decisions
Cons of Gatsby
- No ssr6
- Very slow builds3
- Documentation isn't complete.3
- For-profit2
- Slow builds2
- Flash of unstyled content issues2
- Problematic between develop and build commands1
- Difficult debugging1
- Too many dependencies1
- Plugin driven development1
- Difficult maintenance1
Cons of Jekyll
- Build time increases exponentially as site grows4
- Lack of developments lately2
- Og doesn't work with postings dynamically1