At last week's Moar Serverless event, Brian Leroux discussed a concept he called Functional Web Apps and how it differs from the Jamstack. The key difference, as I understand it, was in how it handles content that cannot be prerendered during the build.
In a typical Jamstack application, an API/serverless function would be called that would send back data and then the client would update, with JavaScript updating the DOM (often using a framework like React). Functional Web Apps would render the HTML on the server (also via a serverless function) and then hydrate the client using techniques like those built into Astro to do this without layering on a heavy JavaScript framework. It's an interesting concept that I am interested in exploring more and a sign of the continuing and rapid evolution in and around the Jamstack.
|
|
Static vs. Dynamic vs. Jamstack: Where's The Line? A really useful attempt to define the distinction between what is just a static site, what is a Jamstack site, and what is a dynamic site. I disagree with where he draws some of the lines (example on DPR) but I do agree with him that there’s no point in being dogmatic about it.
Mike Neumegen
|
✂︎ Tools and Resources
-
Architecting with Next.js – A free event from Netlify next week (August 25th) showcasing teams using Next.js in production, including architecture deep dives, best practices and challenges.
-
Headless Creator – Free, live and recorded lessons for those interested in or working with headless CMSs.
-
Tina is in Beta – Tina Cloud is a backend solution for TinaCMS that offers an inline content editing experience for Next.js sites.
-
Introducing Deploy Hooks for Cloudflare Pages – This allows you to trigger a build based upon things like an update to a headless CMS.
|
|
New Nuxt Features Past v2.10 Sarah covers newer features like Nuxt Content, Nuxt Components and Nuxt Image that were added in recent releases.
Sarah Drasner
|
Modular Code with Nunjucks and Eleventy Exploring some of the features offered by Nunjucks and Eleventy to modularize your code including template inheritance, filters, includes, macros and shortcodes.
Jérôme Coupé
|
Thank you for reading. I'll catch you next time — Brian
|
|
|