The central question nowadays when choosing how to build a new Jamstack project is: do I need a frontend JavaScript framework or not? The static site generator ecosystem has a widening split between those that heavily depend upon a JavaScript framework (Gatsby, Next.js, Nuxt, Scully, etc.) and those that do not (Hugo, Eleventy, Jekyll, Bridgetown, etc.).
The JS framework SSGs offer a lot of powerful features including easy API integration, massive libraries of modules to accomodate complex needs, and even the ability to switch between server-side rendering and static rendering depending on the route. However, in many cases, this is more than an application needs, as Nicolas Goutay explains, while putting an unnecessary burden (i.e. a lot of JS) on your users. Having made this decision myself recently, I will admit it's not always an easy or obvious one.
|
|
|
Towards a Lightweight Jamstack
While the developer experience of JavaScript framework-based static site generators are great, this doesn’t necessarily benefit users, particularly on sites that don’t require the features of the full framework. Nic lays out lighter weight options, including his stack based on 11ty and Alpine.js.
Nicolas Goutay
|
|
Technology Radar
Clearly the buzz around 11ty is strong recently, with it even making ThoughtWorks’ influential Technology Radar under 'tools to assess'.
ThoughtWorks
|
As always, I welcome feedback or link suggestion via Twitter. Stay safe and healthy! — Brian
|
|
|