The Jamstack 🍓
The Jamstack
Hello friends!
I hope you're enjoying this Serial Maker newsletter! You can now join me and other Serial Makers on Discord. Check out the past editions if you missed them. And if you know someone who might benefit from this newsletter, please forward this email to a friend 😀
Want better performance, higher security, and cheap and easy scaling for your next website? Build it on the Jamstack. 🍓
TL;DR
Build content right in Git
Use a static site generator
Deploy instantly to a CDN
What is the Jamstack?
A Jamstack site is a pre-rendered site, distributed over a CDN, with all server-side processes abstracted into micro-service APIs. There is no CMS, no backend, no database to manage. Deployment is as simple as pushing to a git repository. Any pre-rendered elements are enhanced with JavaScript and modern browser capabilities.
The Jamstack is a departure from monolithic server setups like WordPress or Ruby on Rails. There is no tight coupling between the client and the server. Anything server-side is considered separate and accessed via a headless CMS or API service.
Pick your static site generator
You can certainly build a Jamstack site by hand. However, there are plenty of static site generators available that make things easier. Pick your flavor:
Want to build your site in React? Check out Next.js or GatsbyJS.
Like markdown? Try Hugo.
Prefer Ruby, markdown, and Liquid templating? Take a look at Jekyll.
Love Vue.js? Build with NuxtJS.
All of these tools will get you up and running with a basic web framework quickly.
Content management
The Jamstack is built to access data through APIs. But many of the most popular static site generators enable developers to build their own content right in their code base. The templating is handled by the engine, and new content is as straightforward as creating a new file in the project. Publishing a new blog post is as simple as adding a new file, running a build script locally, and pushing your changes to your repository.
Instant deployment
A Jamstack site is served from a content delivery network (CDN). This is a geographically distributed group of servers that work together to deliver internet content super fast. A typical Jamstack site is pushed to a code repository. The CDN service then pulls in your latest changes from your repository and distributes your code throughout its network. Some popular CDN services are:
Vercel - makers of Next.js
Netlify - super simple deployment
Google Cloud Storage, AWS S3, Azure Storage - all major cloud providers. Some static site generators can deploy directly with a single command
GitHub Pages - built with Jekyll, but can host any static site
What else?
There are a myriad of Jamstack build tools out there, and this issue is only scratching the surface. Are you already building on the Jamstack? What tools are you using? Hit reply and let me know all about the hot new thing on the market.
Keep making, and thanks for reading! 🙌
Hit reply to tell me what you're making. I'm looking for anyone interested in talking about their own side-projects and maker journey, so speak up if you'd like to appear in Serial Maker. I'd also love to know what you thought of this issue, and what you want to hear about in the future. And don't forget to continue the conversation on Discord!
Until next week,
Craig