We picked the JAMStack because of it's huge upsides over traditional frameworks and platforms.
The biggest impact of migrating to JAMStack is performance. Because JAMStack sites are pre-rendered (instead of served to users on request), you get super high performance without expensive infrastructure.
Unlike older platforms where the hosting, database and code is coupled together, JAMStack sites are seperated. This means less moving parts and serving read-only assets, making it very difficult to hack.
JAMStack sites come automatically with smart caching of pages and resources, serving up everything from a CDN. Continuous deployments come by default with built-in redundancy and have incredible load capacity.
JAMStack sites are rendered during build time. This means all you need to host a JAMStack site is a static hosting service that can run a simple build command. We use Vercel, but you’re not locked in to any infrastructure.
Because JAMStack sites have almost no hosting complexity and all the hard work was done during the build stage, there’s no need for complex hosting maintenance or a team of support engineers to keep an eye on it.
Every JAMStack setup has three key components: a CMS, framework and hosting. Here are our preferred ones.
Our preferred content management systems are Prismic and GraphCMS. They both offer GraphQL and Rest APIs for us to use, as well as reliable content modelling, repeaters and an approachable pricing model.
Our favourite hosting providers are Vercel and Netlify. They both offer a global edge network to put you as close as possible to your customers, as well as free SSL encryption, asset compression and cache invalidation.
We’re partnered with some of our favourite tools and platforms that we use for JAMStack development.