With GatsbyConf a few months behind us, and the new-conference-on-the-block HugoConf approaching on the horizon, we are now — temporally, at least — between Gatsby.js and Hugo. Distinctly different in their approaches to static site generation and developer workflows, both are popular and well established static site generators, with large and active communities surrounding them.
But which should you choose? The answer might be easier than you think, and it all depends on whether you’re building a ‘reference’ project or something that relies on user interaction. (Or at the very least, it depends where on that spectrum between those two points your project might land.)
Gatsby.js and Hugo are both fully compatible with CloudCannon’s Git-based CMS, and while both will work perfectly well for small business sites and blogs, each has different strengths. Whether you’re creating a documentation site with thousands of individual pages, or a single-page application with plenty of user interaction, or something in between, we’ll help you find the right tool.
Gatsby.js is a static site generator built with React; it uses React/JSX for templating and GraphQL for queries. It was the first SSG to really blur the lines between static and dynamic sites, allowing developers to hydrate their purely static sites with React components for dynamic interactions.
Gatsby.js is a developer-friendly SSG, with built-in features like code splitting, prefetching, routing and caching. Finally, Gatsby.js is well established, with an active community and a very healthy plugin ecosystem.
Hugo is one of the world’s most popular open-source static site generators. Even when compared to SSGs with venture capital backing, Hugo stacks up remarkably well in terms of overall installs, live sites, and GitHub stars. With its amazing speed and flexibility, Hugo makes building websites fun again.
Hugo’s popular primarily for its build speeds, though its flexibility and modularity plays a huge role as well. It’s simple to install, thanks to a single cross-platform binary, and has built-in features like i18n, image optimization, sitemaps, menus, and feeds. Oh, and if you’d like to start your Hugo build with a themes, Hugo has you covered.
|Plugins||Limited||Yes — thousands!|
|Themes||Yes — hundreds!||Yes — hundreds!|
|Installation requirements||None — Hugo is a single binary||Via npm|
|Remote data||Via getJSON or getCSV||Via GraphQL|
|Multilingual and i18n||Built-in||Yes, via plugins|
|Shortcodes||Yes||Yes, via plugins|
|Easy WordPress / legacy converter||Yes: gohugo.io/tools/migrations||No, but only slight configuration is required to use Gatsby with WordPress|
|Support communities||Hugo Discourse is a full-service forum with many active users; HugoConf promises to link Hugo users.||AskGatsbyJS on Twitter; Gatsby Discord for real-time chat with community and team members; GitHub Discussions for more involved questions.|
|Twitter accounts||Hugo Twitter||Gatsby Twitter, Gatsby Changelog|
|CloudCannon support||Yes — you can get your Hugo or Gatsby.js sites editable in minutes with CloudCannon.|
Choose Hugo if you’re building a site that doesn’t require dynamic content or interactions. If you’re working on large reference sites with hundreds or thousands of pages, or if you think your site will eventually grow to that size, Hugo’s fast builds will work in your favor. (Your content editors will thank you!)
Whichever static site generator you choose for your next website project, CloudCannon CMS will support you and your content editors with two-way Git syncing for collaboration, branch/merge workflows for adding new content and features, top-tier hosting, and best of all, an intuitive visual editor interface.
If you’re looking for tutorials, find out more about working with Hugo for beginners, or how to make the most of Hugo and CloudCannon. You may also find it helpful to dig into our Documentation to answer your SSG-specific questions about how to work with CloudCannon and Hugo, Gatsby,js, or any other static site generator.