Static site generators are still relevant and continue to evolve. You may be able to evolve with them, without needing to jump into a new type of framework.
SSGs were revolutionary when they entered the scene around 2008. But they are still relevant. And they are still great. And for many of the same reasons they were compelling in 2008.
Jamstack began as an architectural approach for building websites. As a byproduct, it also promoted the simplicity of deploying those sites.
It’s difficult to choose a CMS today because there are so many options. But why are there so many options?
Netlify isn’t just for websites. Learn how you can use Netlify to serve your other sites with useful content, creating a single source of truth for your assets and data, as needed.
You can get to production faster by separating CI and build/deployment process. But there’s risk in it. Here are two approaches to help with the decision.
In exploring the artifacts of the early Jamstack movement, I’ve come to discover the best part of the Jamstack. This now guides how I describe Jamstack.
Four considerations when deciding to run continuous integrations with production builds or as a separate workflow.
At Stackbit, we're working to fill in this missing piece in the Jamstack. We believe we can build a healthy contract between developers and content creators.
The Jamstack may have been born out of pain, but it couldn't have existed without the convergence of a few key factors.