Gatsby and Hugo

JAM when you want

• BYOF: bring your own front-end
• Continuous deployment

Hugo when you:

• need Faster builds
• no time to spend on configuration
• Limited search locally, extensive search with Algolia.
• SPA- possible. more work. -Go’s template libraries
• Basic Understanding of GO
• Work offline. YES (Service Worker)
• Nice docs.
• Quick start. Hugo

Gatsby when you:

• need PWA
• need GraphQL
• good understanding of React
• need huge ecosystem of plugins.
• Not as fast as Hugo
• uses React
• deeper understanding of React
• Work offline- (creates a service worker)
• steeper learning curve- but a lot of tutorials & examples with API's
• Easier start with Gatsby with some familiarity of React
• understanding of JavaScript
• more features/more bugs
• Lot of Node modules to run
• more dependencies- more code - that you might not trust.
• advantages of the JavaScript toolchain (a lot of plug-ins)
• disadvantages of JavaScript fatigue (Too Many Tools)
• SPA… a plug-in.
• using Algolia or Lunr or ElasticSearch

 {
    allStrapiBlogs {
      nodes {
        slug
        desc
        date(formatString: "MMMM Do YYYY")
        title
        category
        id
        image {
          childImageSharp {
            fluid {
              ...GatsbyImageSharpFluid
            }
          }
        }
      }
    }
  }

(Ref: Hugo, Gatsby, Wikipedia, and Google)