I really enjoyed reading Brad Frost's post, "front-of-the-front-end and back-of-the-front-end web development." I like the concept, especially having been someone who has intensely disliked the term "full stack" since the beginning. It got me thinking about how Jamstack development fits within this dichotomy.
Obviously, there is a front-of-the-frontend piece (every site needs a layout and design after all), but much of what we talk about as being distinctly Jamstack relates to the back-of-the-frontend - connecting to APIs, creating services, managing the deployment, etc. It's an interesting way to look at specific areas of expertise and dividing the work amongst teams building web apps - Jamstack or not...but of course Jamstack.
|
|
How to Secure API Routes for Jamstack Sites Serverless functions such as Netlify Functions aren’t protected from misuse by default as the endpoint URL is exposed. This posts looks at some strategies to add some basic security to these functions.
Carlos Eberhardt
|
Headless Shopify Shopify is traditionally used as an out-of-the-box coupled ecommerce solution, but it does offer a Storefront API, which can be used as a headless option. What are the pros and cons of using it?
Nebojsa Radakovic
|
gatsby-source-wordpress v4 Version 4 of this plugin recently launched and leverages the work Gatsby has done creating the WPGraphQL project which allows it to work well incremental builds, fast builds, and CMS previews.
Gatsby
|
Learn To Love Your Jamstack BFF There’s been some pushback on modern frontend development and Jamstack specifically from folks who see a return to the monolithic backend as a return to simplicity.
Brian Rinaldi
|
Integrating Sanity and Hugo with Netlify Plugins While this guide is Sanity-specific, it does show how you can leverage Netlify Build Plugins with a more traditional static site generator to pull content from a remote source at build time (a feature that has largely been lacking in tools like Hugo).
Sanity.io
|
Thanks for reading. Catch you next time — Brian
|
|
|