Performance has been one of Jamstack's selling points since the start, but one could argue we often took it for granted that Jamstack sites performed better. That assumption was based upon serving static assets from a CDN, but it often overlooked aspects such as rendering in the client's browser or, more from a developer experience (but also cost) perspective, build performance. Lately, both those aspects of performance have been garnering a lot of attention.
|
|
|
JAMstack Is Fast Only If You Make It So
Jamstack promotes performance as one of its main benefits but the author notes that this can sometimes be undermined by pushing too much JavaScript to the client. Instead of leading with JavaScript, he suggests thinking of it as just the glue between the APIs and markup.
Nicolas Hoizey
|
|
âď¸ Tools and Resources
-
Sitesauce - A new (paid) service that offers to automatically convert dynamic websites (e.g. WordPress, Ghost, Joomla, etc.) into static sites, and keeps content in sync.
-
Using Expo in Gatsby - A cool experiment for using React-Native-Web and Expo to embed React Native fully functional demos into posts in Gatsby using MDX.
-
Full Stack Radio 138: Tom Preston-Werner - Tom Preston-Werner talks about Redwood.js, a new full-stack JavaScript framework for building Jamstack applications.
-
The Changelog #393 - Kyle Matthews - Kyle shares the story of the 3 years it took making incremental builds possible.
|
|
|
Static Hoisting
Static hoisting is presented as a concept where the static assets of your site are âhoisted to the edgeâ (i.e. a CDN) for maximum speed and availability.
Guillermo Rauch
|
Yup, lots of Next.js in this issue due in part to some big recent releases. I hope you are all staying safe and healthy. If you have feedback on this newsletter or want to suggest an article, reach out on Twitter â Brian
|
|
|