1 The JAM stack with Hugo

This chapter covers:

  • Basics of the JAM stack for building websites
  • Principles of static site generators
  • Understanding the Hugo static site generator
  • Benefits the Hugo static site generator
  • Use cases best suited for JAM stack and Hugo

If you have been associated with websites recently or have friends who have been working for companies with web based products you must have known how much work it is to maintain a website. With the need for DevOps engineers, system administrators and database architects, keeping a website running on the internet is a full time job for an entire team, not just an individual. The upkeep of content is so difficult that creators have been moving at an unprecedented rate to managed hosting like WordPress.com or even giving away their content to platforms like Medium or FaceBook.

1.1  Parts of the JAM stack

1.1.1  JavaScript

1.1.2  Application Programming Interfaces(APIs)

1.1.3  Markup

1.2  How does the JAM stack work

1.3  How is JAM different from LAMP, MEAN or MERN?

1.4  Why use the JAM Stack?

1.4.1  Minimal Operations

1.4.2  Great Performance

1.4.3  Lower costs

1.4.4  Developer Productivity

1.4.5  Longevity

1.4.6  Tooling

1.5  Selecting the builder

1.5.1  Jekyll

1.5.2  Gatsby

1.5.3  Hexo, Pelican, VuePress, Nuxt and others

1.5.4  Hugo

1.6  Why choose Hugo?

1.6.1  Hugo is fast

1.6.2  Hugo is built for performance

1.6.3  Hugo is self-contained

sitemap